Version: unspecified (using KDE 4.4.4) OS: Linux I have gdm3 managing displays on my Debian testing (i386) system. If kscreensaver has locked the screen there is no option to switch user. The "Switch user" option on the K menu only locks my display, and does not start a new session with a gdm3 greeter. There is no option to turn off or reboot from the K menu. All of theese are functional when kdm manages displays for me. There appears to be a patch for this in Fedora. A bug repport in Debian BTS refers to this patch. I am reporting upstream. Please see Debian bug #581841 for a reference. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581841 Regards ;)Frode Reproducible: Always Steps to Reproduce: Let gdm3 manage displays. Try to switch user form K menu, lock screen with kscreeensaver and switch user, shut down system or reboot from K menu. Actual Results: Unable to start new gdm3 greeter, shut down or reboot. Expected Results: Should integrate into gdm3 the same way as it does with kdm.
ossi, could you take a look to the Fedora patch (see Debian bug report) ?
*** This bug has been marked as a duplicate of bug 186198 ***
This bug is not a duplicate of bug #186198 https://bugs.kde.org/show_bug.cgi?id=186198 My bug report is against gdm3 integration. Bug #186198 is against gdm2 integration. gdm2 integrates nicely with KDE 4 on my Debian Squeeze/Sid. gdm3 does not. There exists a patch towards KDE for Debian. http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=12;filename=0001-Use-ConsoleKit-fur-shutdown-with-gdm3.patch;att=1;bug=581841 Please, can you examine further? Regards ;)Frode
the numerical suffix in the debian package name is only there to have two separate packages for the interface-incompatible gdm versions (both configuration and remote control). the gdm3 package version is 2.30, as opposed to 2.20 for the old gdm package - which is exactly in line with what i have written in the other report. i suggest you do some slightly more thorough research before revising a maintainer's action next time. *** This bug has been marked as a duplicate of bug 186198 ***
I am sorry that I did not do my homework. Please forgive me. Regards ;)Frode
This bug is marked as resolved, I assume also because it has been marked as a duplicate. This is not a duplicate of bug #186198 as that bug has been specifically reported against solaris. I experience this bug (exactly as it is described here) on Ubuntu 10.04. Also. Can I do anything to help move this bug along? (I am a developer)
(In reply to comment #6) > Also. Can I do anything to help move this bug along? (I am a developer) > once you accept that this *is* a duplicate, you can start following the instructions from one of the other duplicates.