Bug 1293078 - SDDM doesn't use .face.icon
SDDM doesn't use .face.icon
Status: CLOSED DEFERRED
Product: Fedora
Classification: Fedora
Component: sddm (Show other bugs)
rawhide
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Martin Bříza
Fedora Extras Quality Assurance
: FutureFeature
Depends On: plasma-user-manager
Blocks:
  Show dependency treegraph
 
Reported: 2015-12-19 18:39 EST by Bhaskar S. Manda
Modified: 2015-12-19 21:50 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-12-19 21:47:42 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Bhaskar S. Manda 2015-12-19 18:39:14 EST
Description of problem:
Login screen doesn't show user image (~/.face.icon). Lock screen does show it.

Version-Release number of selected component (if applicable):
Version     : 0.13.0
Release     : 4.fc23


How reproducible:
Always

Steps to Reproduce:
1. Reboot 


Actual results:
A placeholder image is shown for each user.


Expected results:
The image .face.icon should be shown.


Additional info:
Comment 1 Rex Dieter 2015-12-19 19:43:40 EST
It's (most likely) just a matter of permissions, fedora default permissions do not allow any (non-root) users to read your $HOME (including desktop managers like sddm).

If you want to allow this, do:
chmod a+X $HOME
Comment 2 Rex Dieter 2015-12-19 19:47:31 EST
Once plasma-user-manager is reviewed, we theoretically could add code to adjust permissions for you, once a face is set in the UI
Comment 3 Bhaskar S. Manda 2015-12-19 21:47:42 EST
Using chmod as specified fixes the issue.

That was my next bug - no user manager in settings - but you suggest the package will be added after review?

Thanks,
Comment 4 Rex Dieter 2015-12-19 21:50:47 EST
Yes, once it's reviewed

Note You need to log in before you can comment on or make changes to this bug.