Bug 715128

Summary:	no lxdm autologin for user with xfce4-panel-4.8.5-1.fc15
Product:	[Fedora] Fedora	Reporter:	Wolfgang Ulbrich <fedora>
Component:	xfce4-panel	Assignee:	Kevin Fenzi <kevin>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	15	CC:	cwickert, fedora, kevin, maxamillion
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-06-22 09:13:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Wolfgang Ulbrich 2011-06-21 22:54:06 UTC

Description of problem:
After updating to xfce4-panel-4.8.5-1.fc15  autologin from lxdm to xfce-desktop is not possible.

Version-Release number of selected component (if applicable):
xfce4-panel-4.8.5-1.fc15

How reproducible:


Steps to Reproduce:
1.Configure /etc/lxdm/lxdm.conf autologin for user
2.Boot stops in lxdm
3.You have to enter a password.
  
Actual results:
no autologin 

Expected results:

autologin without entering a password
Additional info:
Sorry, i don't have any logs about this isue and i don't know to give you more specific info.
If you need more info's let me know.

Comment 1 Christoph Wickert 2011-06-21 23:24:23 UTC

I don't think this has anything with xfce4-panel, but lets see.

Can you show me your /etc/lxdm.conf please? What happens if you run
'yum downgrade xfce4-panel'?

Comment 2 Wolfgang Ulbrich 2011-06-22 09:13:43 UTC

Today, i've tested xfce4-panel-4.8.5-1.fc15 again and I'm surprised because autologin works fine now.

Yesterday i had updated xfce4-panel, xfce-utils and xfce4-doc and the autolgin with lxdm doesn't work.
After downgrading to xfce4-panel-4.8.3-2.fc15 autologin works.
At this point i decided to write a bugreport.

I don't know why this happend yesterday.

But today everting is working fine, so i decided it's not a bug and i will closed this bugreport.

Thx for your quick response Christoph.

Wolfgang