| Summary: | Support GDM >= 2.19 | ||
|---|---|---|---|
| Product: | [Unmaintained] kdm | Reporter: | Frederik Himpe <fhimpe> |
| Component: | general | Assignee: | kdm bugs tracker <kdm-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | fdiaza, rdieter, tuju |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Use /var/run/gdm_socket instead of /tmp/.gdm_socket | ||
|
Description
Frederik Himpe
2007-08-20 23:52:44 UTC
Created attachment 21440 [details]
Use /var/run/gdm_socket instead of /tmp/.gdm_socket
*ping* It would be nice if someone could take a look at this, as GDM 2.20 stable is out in the wild now. This bug hit me in Debian unstable since a few days ago, when Gnome was updated to 2.20. The Ubuntu people took the short route to fixing it, see https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/64695 fixed for kde 4.0 and 3.5.9. |