Summary: | KDE does not know how to shut down or switch user when gdm3 is managing displays | ||
---|---|---|---|
Product: | [Plasma] ksmserver | Reporter: | Frode Hatlevik <frodeseverin> |
Component: | general | Assignee: | Lubos Lunak <l.lunak> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | acb, fabo, ossi |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Frode Hatlevik
2010-07-20 05:24:31 UTC
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. |