| rrq | bandali: .. here ? | 03:04 |
|---|---|---|
| cores | hi, i'm running Devuan 5 on a T470 type thinkpad. I closed my lid last night and this morning my desktop was frozen. i can move the mouse cursor but nothing else responds. | 15:05 |
| cores | this happened before and thought it was the nouveau driver, so i disabled that and rebooted but i guess that wasn't the problem becuase it still happened. i'm not sure what action i set for closing the lid in power settings | 15:06 |
| cores | Xorg, XFCE 4.18, xscreensaver | 15:06 |
| cores | it actually says 'xscreensaver-systemd' even though i'm on sysvinit. not sure what that's about yet | 15:06 |
| ted-ious | cores: Do any of your led's change when you hit caps or num lock? | 15:27 |
| cores | ted-ious: the caps lock led changes when i hit it. there's no num lock led | 15:31 |
| ted-ious | Well that's better than nothing. :) | 15:31 |
| cores | actually i closed the lid early this morning around 3 hours ago and i opened it about 45 minutes ago | 15:32 |
| ted-ious | Can you get to a console with ctrl-alt-f1? | 15:32 |
| cores | ted-ious: yes, i can | 15:32 |
| cores | thats how i looked through /var/log/syslog.1 and didn't see anything suspicious | 15:32 |
| cores | when i switch to a console then switch back to X the top panel with the time, battery, etc updates but when i just have X open, nothing changes | 15:33 |
| cores | when i try to launch an X app from the console like $ export DISPLAY=0.0 && xterm; nothing happens on X, no new window and xterm doesn't exit immediately | 15:36 |
| cores | i could just restart x from the console (once i figure out how) but i do also want to find the cause of this so i can prevent it in the future, if possible | 15:43 |
| rustyaxe | syslog.1 would be an old (logrotated) file | 15:52 |
| rustyaxe | so you wouldnt find recent messages there | 15:52 |
| cores | right, i wasn't looking for the most recent messages, i was looking for messages around the time when i closed the lid | 15:53 |
| gnarface | without finding any errors, it's difficult to make meaningful speculations, because it could be anything from a bios bug to a kernel bug to a faulty power supply, to hung sound effect | 15:55 |
| cores | yeah, you're right. i don't even see the lid close event in the syslog.1 file but according to the timestamps, it should be there | 15:56 |
| gnarface | some drivers just can't wake up from sleep well even to this day, and if it's actually a nvidia video card, not only will it not ever do that reliably without their non-free drivers, you will also have to edit some of the acpi scripts using examples from their docs | 15:56 |
| cores | i suspected nvidia, so i disabled the nouveau driver: $ lsmod | grep nouveau returns nothing | 15:59 |
| gnarface | logging is important, you might want to make sure you have rsyslog installed and verify that the /etc/rsyslog.conf is actually writing the stuff you want to the files you're expecting (i've noticed they've been stripping stuff out of it in recent updates, but if you add stuff back in there just make sure you also add the corresponding lines back into /etc/logrotate.d/rsyslog ) | 15:59 |
| cores | i basically followed this: https://docs.nvidia.com/ai-enterprise/deployment-guide-vmware/0.1.0/nouveau.html | 15:59 |
| gnarface | removing nouveau doesn't actually automatically add the non-free nvidia drivers | 16:00 |
| cores | i didn't want to do that either, i didn't want to run with the nvidia gpu at all | 16:00 |
| cores | i'll look into the rsyslog logger | 16:00 |
| gnarface | maybe it won't matter if you have two and it's not the primary, but i can't be sure of that | 16:01 |
| cores | first i wanted to disable the nvidia gpu in the bios, but that wasn't possible | 16:01 |
| gnarface | i wouldn't get tunnel vision on just the nvidia card though, it could still be just about anything at this point | 16:01 |
| cores | i do have a /usr/sbin/rsyslogd so that's a start | 16:02 |
| gnarface | installing perf then running "perf top" as root while it's hung might help | 16:02 |
| CueXXIII | cores: i have that bug, too… on my laptop it is the screen saver actually locking the display, but due to the closed lid not finding any output on which to display the unlock dialog. i can enter my pasword blind, though, unlock | 16:06 |
| cores | the first entry in "perf top" is "module_get_kallsym". it was about 20% Overhead for a few perf refresh iterations but now it's gone | 16:07 |
| CueXXIII | to unlock the session | 16:07 |
| CueXXIII | cores: you could try first killing all xscreensaver processes | 16:07 |
| cores | CueXXIII: oh ok, my screen was already unlocked. i think i set it to not lock the screen automatically | 16:07 |
| cores | it's not a security issue because i'm leaving this laptop at home | 16:08 |
| CueXXIII | cores: then your xsession might actuallylock the screen again when it receives a lid_closed event | 16:09 |
| cores | oh ok, so you're saying my X desktop might not look locked but it really is locked? | 16:09 |
| CueXXIII | that's the case with my laptop, yes | 16:09 |
| cores | wow you're right. i typed my password and now i'm back in | 16:10 |
| cores | CueXXIII: thanks! | 16:10 |
| cores | that's freaky... | 16:10 |
| gnarface | hard to know really what to do about something like this | 16:12 |
| gnarface | the typical fallout is: xscreensaver people will blame it on the video drivers, the video driver people will blame it on the window manager, and the window manager people will blame it on xscreensaver, nobody will fix it | 16:13 |
| gnarface | then meanwhile in a dark cubicle over at RedHat, some jerks cook up a plan to use it as an excuse to throw the lot of them out and start over from scratch with wayland | 16:14 |
| gnarface | and then nothing works | 16:14 |
| CueXXIII | gnarface: well, it is not THE video driver, i have intel hd graphics | 16:15 |
| ted-ious | cores: So was it screensaver that was messing up or some other locker? | 16:18 |
| ted-ious | Oops I meant xscreensaver. | 16:18 |
| al1r4d | https://github.com/systemd/systemd/issues/32028?fbclid=IwAR1D-KuggXJ96WpewK9ixUWKLZJ51za0VE6D6VDQZZewoQklm_cxxnZs69g | 16:20 |
| gnarface | with xscreensaver, i've noticed some of the screensavers are more stable than others. it varies depending on the drivers and hardware involved of course, but the worst ones are mostly opengl ones | 16:20 |
| gnarface | on older hardware that rotoscope one suffers too | 16:21 |
| gnarface | seems to require some hardware feature that is nearly ubiquitous today but was not always | 16:21 |
| CueXXIII | and xscreensaver is really still missing a "just display a random picture without additional effects" screensaver. | 16:22 |
| |cos| | slock from suckless is a good minimalistic screensaver imho | 16:22 |
| ted-ious | Can you kill it from a console and get control back? | 16:28 |
| ted-ious | I remember reading that xscreensaver didn't allow that for security reasons but unfortunately that means you can end up in a really bad situation if it crashes. | 16:29 |
| fsmithred | CueXXIII, you can edit a chosen screensaver and change the command to something that displays a static image. | 16:30 |
| |cos| | ted-ious: what does that even mean? xscreensaver is a process. if it gets killed, it dies and looses control. | 16:30 |
| ted-ious | I don't really know since I'm not a developer. | 16:31 |
| fsmithred | press a key or move the mouse to get control back. | 16:31 |
| fsmithred | if it's set to lock the screen, then you also need to enter a password | 16:31 |
| ted-ious | But I think I read that the author didn't like it being possible to kill the process and unlock the screen because somebody could get access to running x applications that way. | 16:31 |
| |cos| | sounds strange. | 16:32 |
| cores | ted-ious: i guess it was screensaver related | 16:33 |
| fsmithred | If the screensaver is running and the screen is locked, you can drop to console with ctrl-alt-Fn, log in as the user who started xscreensaver and kill it. | 16:39 |
| fsmithred | just tested. | 16:39 |
| fsmithred | if you're another user, you can't kill it. | 16:40 |
| cores | CueXXIII: what's your workaround? i'd like to be able to close the lid and not have to enter a password | 16:42 |
| CueXXIII | cores: then don't run xscreensaver. or configure your desktop to not lock the screen | 16:42 |
| cores | fsmithred: my problem was when i opened my lid again, it didn't look like xscreensaver was still running, i just saw my desktop as i left it last. CueXXIII told me about this problem they had so i typed my password and i was back in again | 16:43 |
| cores | CueXXIII: in the xscreensaver settings i unchecked "lock screen after ..." | 16:44 |
| cores | oh, it's a different setting | 16:46 |
| cores | in the power manager i had close lid set to lock screen | 16:46 |
| fsmithred | I have the screensaver turned off and use power manager to handle the lid. | 16:53 |
| fsmithred | no lock | 16:53 |
| ted-ious | cores: Does xfce have its own settings for screensaving? | 16:54 |
| CueXXIII | xfce has it's own settings for acpi events like lid close | 17:05 |
| cores | ted-ious: i'm not sure. i only see two options for screen lock, xscreensaver settings and power management settings | 17:07 |
| cores | i don't see a section in the xfce settings manager for screensaver | 17:07 |
| ted-ious | cores: You missed this. CueXXIII> xfce has it's own settings for acpi events like lid close | 17:17 |
| fsmithred | where? | 17:18 |
| fsmithred | CueXXIII, are those acpi settings somewhere other than the power manager settings? | 17:19 |
| CueXXIII | cores: does it still lock up without dialog? | 17:20 |
| CueXXIII | fsmithred: that should be those settings there | 17:20 |
| fsmithred | ok, thanks | 17:20 |
| CueXXIII | you could also put scipts in /etc/acpi/events/ | 17:21 |
| cores | CueXXIII: no, it does not lock up without dialog any more. i had already disabled lock in the xscreensaver settings and now i have disabled lock in the xfce power management settings | 18:42 |
| cores | CueXXIII: Xfce Applications menu->Settings->Power Manager->System tab->Security pane->Lock screen when system is going to sleep | 18:44 |
| cores | And I set "Laptop Lid" in Power Manager System settings to "When laptop lid is closed: Switch off display" | 18:44 |
| cores | With these settings, so far so good | 18:44 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!