Description of problem: LXDM doesn't create Consolekit Session after the user login with his/her non-root user account. This is the result of running the command ck-list-sessions through terminal: [fitlad@localhost ~]$ ck-list-sessions Session1: unix-user = '500' realname = 'fitlad' seat = 'Seat2' session-type = '' active = FALSE x11-display = ':0' x11-display-device = '/dev/tty7' display-device = '' remote-host-name = '' is-local = FALSE on-since = '2011-12-30T00:58:12.241353Z' login-session-id = '1' However, If the user changes his/her default Display Manager to GDM, the problem is solved; GDM will register the user as active and local. Thus, LXDM is a broken package! User cannot Shutdown, Reboot, Suspend, Hibernate nor even mount a removable media such as usb drives through PCManFM. If someone compares LXDM in the Mageia Repository with the ones available in other Distributions like Ubuntu, Fedora and openSUSE, he/she will notice that the other distributions get LXDM working perfectly. LXDM suppose to be the default DM for LXDE users not GDM. Thanks Version-Release number of selected component (if applicable): lxdm version 0.2.0-2 How reproducible: Every time the user attempts to login via LXDM Steps to Reproduce: 1.Make lXDM as your default Display Manager 2.Login with your non-root user-name 3.open terminal and run ck-list-sessions
CC: (none) => a.al_ahmed
Hi, thanks for reporting this bug. As there is no maintainer for this package I added the committers in CC. (Please set the status to 'assigned' if you are working on it)
CC: (none) => ennael1, fundawang, mageia
We do have a maintainer now :) Assigning
CC: (none) => marja11Assignee: bugsquad => oliver.bgr
I'm not sure, this can be fixed in old lxdm 0.2.x We are using 0.4.x in Cauldron since december and it's working there. I will look into it.
There is now lxdm-0.2.0-2.1 in core/updates_testing to validate --------------------------------------------------------------- This update solves a problem with the consolekit session, when starting lxde from lxdm in Mageia1. This issue was reported as Bug 3936 in Mageia bugzilla. --------------------------------------------------------------- Steps to reproduce: - Change dm in Mga1 to lxdm - start lxde session - open a terminal and type ck-list-sessions the value for is_local is given as false - Update the package - restart the dm (or better reboot) - start a lxde session - Do the above again and the value should be given as true.
Assignee: oliver.bgr => qa-bugs
CC: (none) => oliver.bgr
Tested myself on x86_64 and it was ok.
Created attachment 2191 [details] .xsession-errors In addition to the errors shown in the attachment, at the startup of gnome, I'm getting a popup with the message There is a problem with the configuration server. (/usr/lib/gconf-sanity-check-2 exited with status 256) Doesn't look like ~/.profile is getting sourced either, so the locale etc, is not being set properly.
ck-list-sessions output is ok, so the actual bug is fixed. I'll have to check to see if the problems I'm seeing are a regression or not.
CC: (none) => davidwhodgins
It also results in a resolution of 1280x960 instead of my chosen 1280x1024.
I've confirmed the bugs I'm finding are not regressions. Do you want to push this update as is and I'll open a new bug report, or do you want take a look at the problems first? I can't log in to kde, as it's trying to write to /root/tmp, and fails. With gnome, the resolution gets changed, and the locale is not set properly, causing problems for some programs.
Yes, please push it. I will have a look into the other things separately.
Ok. I'll open a separate bug report for the other problems. Could someone from the sysadmin team push the srpm lxdm-0.2.0-2.1.mga1.src.rpm from Core Updates Testing to Core Updates. Avisory: This update solves a problem with the consolekit session, when starting lxde from lxdm in Mageia1. https://bugs.mageia.org/show_bug.cgi?id=3936
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
Blocks: (none) => 5789
Update pushed.
Status: NEW => RESOLVEDCC: (none) => tmbResolution: (none) => FIXED