Bug 1282047

Summary: sddm package update forgets last session setting
Product: [Fedora] Fedora Reporter: Corinna Vinschen <vinschen>
Component: sddmAssignee: Martin Bříza <mbriza>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: jgrulich, ltinkl, mbriza, me, pierluigi.fiorini, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-11 20:39:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Corinna Vinschen 2015-11-14 15:45:12 UTC
Description of problem:

  When upgrading sddm from 0.10.0-4 to 0.12.0-5, I noticed that, while
  my last user account was still present by default, my previous session
  setting ("Plasma") has been forgotten, and the session menu presented
  the first entry in the session menu ("MATE" in my case) again.  After
  setting this back to "Plasma", the setting was stable even over multiple
  logout and login.

  After that, downgrading to sddm-0.10.0-4, the same occured.  The session
  menu showed "MATE" again and I had to change this manually back to "Plasma".

  Rinse and repeat.

  So, while the sddm package update preserves the last logged in user
  account (no problem there), for some reason it misses to preserve
  the last session setting. 

Version-Release number of selected component (if applicable):

  Any?  During testing: 0.10.0-4 and 0.12.0-5.

How reproducible:

  Up- or downgrade the sddm package.

Actual results:

  Last session setting is forgotten on package update.

Expected results:

  Last session setting is preserved.


Thanks,
Corinna

Comment 1 Rex Dieter 2016-03-11 20:39:37 UTC

*** This bug has been marked as a duplicate of bug 1240749 ***