Bug 1270747 - SDDM shows generic user profile picture in Login Screen regardless of the actual user profile picture that the user wants
Summary: SDDM shows generic user profile picture in Login Screen regardless of the act...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: sddm
Version: 22
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Martin Bříza
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1265231 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-12 09:52 UTC by Samuel Lee
Modified: 2016-03-12 02:18 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-12 02:18:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Samuel Lee 2015-10-12 09:52:06 UTC
User-Agent:       Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.101 Safari/537.36
Build Identifier: 

SDDM shows a generic face picture instead of the specific user profile picture in the login screen.

It is known to happen in both GNOME and KDE, as I did use both DEs.

This issue is about user profile picture is not synchronized between SDDM and other aspects of login features (Lock Screen, Start Menu etc). 

Reproducible: Always

Steps to Reproduce:
Any methods that shows the login screen. 2 of the most common path would be:

1. After reboot / switched on PC and it loads into login screen.

2. When user log off from the user account which returns to login screen.


This does NOT happen when:

1) For GNOME: 

Before logging off (As the user profile picture is shown after clicking the 'Battery icon' on the top right)

For KDE:

Whenever the "Start Menu" logo (Either a 'K' or Fedora icon) is clicked on the extreme bottom left because the "Start Menu" similar to Windows does show the username and the user profile picture.

2) When the screen is locked as the 'Unlock screen' prompts for password will show the username and the user display picture.

Actual Results:  
The theme is shown, and it shows a generic user profile picture despite user had specified a custom display picture and the correct username.

All other aspect of login / home settings are reflected as expected such as user profile picture is shown during lock screen or the "Start Menu" in KDE and its equivalent in GNOME.

Expected Results:  
The settings made from "User Account" with regards to User display picture must be consistent, even if the user is not logged in.

The specific user profile picture refers to a picture that is configured in 'User Account' settings.

For KDE, it would be "system-settings5"->"Account Details"....

For GNOME, it would be 'Activity' -> 'Settings' (That looks like System Preference in OSX) -> Users

The following command fixes the issue (Assuming the username is 'User' without quotes):

cd ~/

sudo cp .face.icon /usr/share/sddm/faces

cd /usr/share/sddm/faces

mv .faces.icon User.face.icon


Hence, the fix should be getting the user's display picture stored in Home directory to be moved into /usr/share/sddm/faces

Comment 1 Rex Dieter 2015-10-12 10:48:04 UTC
Using ~/.face.icon works for me

Perhaps your $HOME directory permissions don't allow sddm to read it?

Comment 2 Rex Dieter 2015-10-12 11:16:59 UTC
OK, I've confirmed that default $HOME permissions do not allow this to work, unfortunately.

For me, the default was (which didn't work):

$ ls -ld $HOME
drwx------. 34 rdieter1 rdieter1 4096 Oct 12 06:11 /home/rdieter1

But, 

$ chmod +x ~

$ ls -ld $HOME
drwx--x--x. 34 rdieter1 rdieter1 4096 Oct 12 06:11 /home/rdieter1

makes it (sddm) work right.


I'm not sure there's anything we can do about this ($HOME default permissions), other than documenting the workaround.

Comment 3 Rex Dieter 2016-03-12 02:17:31 UTC
*** Bug 1265231 has been marked as a duplicate of this bug. ***

Comment 4 Rex Dieter 2016-03-12 02:18:17 UTC
marking WORKSFORME, given comment #2


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