1. 25 Feb, 2021 7 commits
  2. 24 Feb, 2021 5 commits
  3. 23 Feb, 2021 3 commits
  4. 22 Feb, 2021 19 commits
  5. 19 Feb, 2021 1 commit
    • David Edmundson's avatar
      Enforce SESSION_MANAGER is exported before plasmashell is started · 19ba5f1c
      David Edmundson authored
      Wants says we should bring ksmserver up, but by default that could be in
      any order, we need to define it. kcminit also potentially exports
      environment variables.
      
      This was written with the correct order in-mind but the wrong keyword
      used.  We don't need "Wants" as plasma-core.target already defines that
      we will be loading them along with plasmashell.
      
      It is important that ksmserver is up and has completed exporting the
      SESSION_MANAGER env, otherwise plasmashell will not propogate it so
      applications it launches introducing an X session regression
      19ba5f1c
  6. 18 Feb, 2021 1 commit
  7. 17 Feb, 2021 2 commits
    • David Edmundson's avatar
      Move ksmserver's ksplash notifying to ksmserver · e7e49916
      David Edmundson authored and Henri Chain's avatar Henri Chain committed
      Previously the call to ksplash was being emitted by plasma-session. This
      isn't used in the systemd startup so it was introduced in a somewhat
      messy script.
      
      This script has an issue:
      
      If ksplash is disabled the bus name won't be registered. Typically this
      isn't an issue. However to avoid a race condition ksplash registers
      itself as being DBus activatable, so that the dbus server holds
      dispatching the message.
      
      This combo means ksmserver our unit is considered as not running until
      our script times out. This then defers other things in the chain that
      depend on ksmserver.
      
      Moving the call into the relevant piece of code into ksmserver unifies
      things into a single path and gives us more control.
      
      BUG: 432364
      e7e49916
    • David Edmundson's avatar
      Handle closeSession being called concurrently · 3754967b
      David Edmundson authored
      Currently if hypothetically closeSession was called multiple times
      before the async operation completed the first caller would never get a
      reply and then be left hanging potentially forever.
      
      This is unlikely to happen in real life given only the plasma shutdown
      binary should be calling this and that's a unique application.
      3754967b
  8. 16 Feb, 2021 2 commits