Bug 1445705

Summary:	User listed twice on Login screen
Product:	[Fedora] Fedora	Reporter:	Michal Schorm <mschorm>
Component:	lxqt-session	Assignee:	Helio Chissini de Castro <helio>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	26	CC:	helio, jylo06g, lxqt-sig, projects.rg, rdieter, ti.eugene
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-12 07:39:41 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 Michal Schorm 2017-04-26 10:47:05 UTC

System version:
  Fedora 26 Alpha LXQT
  Linux version 4.11.0-0.rc3.git0.2.fc26.x86_64

Fresh installation, 1 user created.

On Login screen (acesed via 'logout' option, not 'lock screen'), same user is listed twice.
Both selection are accessible with the same password, no difference spotted.
Just listed twice.

Comment 1 Jia Yuan Lo 2017-05-27 03:48:07 UTC

https://www.reddit.com/r/Fedora/comments/6cu81w/think_i_made_a_minor_boo_boo_on_install/

I also want to point out that on a live image (NOT INSTALLED), the users and groups already have duplicated entries.

This maybe a bigger problem than just duplicated real user accounts after installation...

Comment 2 Jia Yuan Lo 2017-06-01 16:00:24 UTC

KDE is having the same problem...

https://bugzilla.redhat.com/show_bug.cgi?id=1446782

Comment 3 Raphael Groner 2017-06-09 08:56:57 UTC

Upstream fixed it for lxqt-admin, see bug #1459642.

Comment 4 Jia Yuan Lo 2017-06-12 02:48:02 UTC

Please mark this as duplicate of bug #1446782 and a bug for sddm instead of lxqt-session

A patch is available, see https://bugzilla.redhat.com/show_bug.cgi?id=1446782#c9

Comment 5 Michal Schorm 2017-06-12 07:39:41 UTC


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