Summary: | x11-misc/lightdm - "dm-tool lock" switches VT and stops locking after a while | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marc Joliet <marcec> |
Component: | Current packages | Assignee: | Marek Szuba <marecki> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | marcec |
Priority: | Normal | Keywords: | UPSTREAM |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugs.launchpad.net/lightdm/+bug/1060228 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Output of genlop -l --date 2013-09-26
The lightdm log The lightdm-greeter log from VT7 The lightdm-greeter log from VT8 |
Description
Marc Joliet
2013-09-04 11:51:01 UTC
Please don't manually CC maintainers. (In reply to Tom Wijsman (TomWij) from comment #1) > Please don't manually CC maintainers. OK, sorry about that. Ok thanks for the report. We will track the upstream bug. I got around to trying new versions of lightdm and found out that lightdm-1.7.16 does *not* show the bug. Neither "dm-tool lock" nor "dm-tool switch-to-greeter" exhibit the behaviour I described, lightdm-1.6.2 however still did. Therefore the yet-to-come stable series 1.8.x ought to be rid of this bug :) . Perhaps somebody with a launchpad account can add a comment to this effect to the upstream bug? (As an aside: lightdm >=1.6.2 (or maybe it was lightdm-gtk-greeter-1.6.0) fixed an issue where the greeter background was set to black instead of to the specified image on a borrowed laptop; in contrast, my desktop showed no problems in this regard.) Unfortunately I have not launchpad account. However, since this appears to be solved in the latest ~testing ebuild we can close this bug. Thanks for the report and for testing. (In reply to Markos Chandras from comment #5) > Unfortunately I have not launchpad account. However, since this appears to > be solved in the latest ~testing ebuild we can close this bug. > > Thanks for the report and for testing. Gladly! Just a FYI: I decided to just create a Launchpad account and have linked the upstream bug to this one and posted a comment there. Damn it, I spoke too soon. As of yesterday, I've started seeing this bug again. I noticed it when the screen simply went black after calling "dm-tool lock". I was able to get to the desktop session via Alt-F7 as per the original bug description and sure enough, "ps aux" showed lots of ligthdm session children. After quitting my desktop session (well, window manager), ligthdm just quit (no SEGFAULT, or anything else in syslog, the process apparently just exited). So I was left to restart the xdm service. After that, I verified that locking via dm-tool switches to a greeter on VT8, so that you can go back to the desktop session with a simple Alt-F7. That, again, shows new session children, but they disappeared after logging in again. I'm perplexed, because I was certain that I didn't see this bug anymore after the upgrade in comment #4. I'll attach the list of packages I've upgraded in case you can see anything that might be involved. I'll also attach a log file of me loggin in, locking, and unlocking the session. Created attachment 360572 [details] Output of genlop -l --date 2013-09-26 This is the list of packages I upgraded/installed after comment #4. Created attachment 360574 [details]
The lightdm log
Created attachment 360578 [details]
The lightdm-greeter log from VT7
Created attachment 360580 [details]
The lightdm-greeter log from VT8
I don't think there's anything interesting in the greeter's logs, but thought I would put them here for completions sake. Also, .xsession-errors doesn't contain anything pertaining to lightdm.
The upstream bug was closed as invalid in 2016, with no activity since then (i.e., no more "me too!"s), and I had switched to KDE4 about two years before that, so haven't really cared about this bug in the last 6 years. Hence: Is this bug still reproducible, or can it be closed now? Because I don't know about you, but I'd be glad to get it off of my open bug list ;-) . As far as I can tell this is MASSIVELY out of date. Definitely haven't ever seen this problem with 1.30.0, at least. |