You are not logged in.
After installing Lithium I have a weird power management problem: after the screen goes blank (e.g. after 5' inactivity), I can't get back into the session. Typing, clicking, moving around the trackpad -- all of which worked on the same machine under Hydrogen -- do nothing. The only way to continue to reboot via the power button.
This problem doesn't appear to be machine specific; I've found it on both a Dell XPS 13 9360 and a Toshiba Portege Z30.
Has anyone else had this issue? Is there a bug/solution/workaround?
The only thing that occurs to me is to disable all power management, which doesn't seem wise.
Last edited by christopherisnow (2020-05-09 11:29:50)
Offline
After installing Lithium I have a weird power management problem
On my ASUS M4A88TD-V EVO/USB3, suspend/hibernate stopped working. The machine woke up immediately from suspend. When hibernating, the macine restarted when memory had been writen to disk (I had to let it restart and shut it of before booting again...)
After installing latest kernel from debian backports, hibernating/suspend worked ok.
Lenovo TP and old IBM TP not affected.
Last edited by rbh (2020-04-29 18:09:57)
// Regards rbh
Please read before requesting help: "Guide to getting help", "Introduction to the Bunsenlabs Lithium Desktop" and other help topics under "Help & Resources" on the BunsenLabs menu
Offline
Glad it's not only me...
After installing latest kernel from debian backports, hibernating/suspend worked ok.
Doesn't the bl-welcome script automatically update the kernel?
Or perhaps there's another tree to bark up?
Offline
Doesn't the bl-welcome script automatically update the kernel?
yes, it does. I think latest kernel in buster is 4.19.0-8
Or perhaps there's another tree to bark up?
Buster-backports, is repository of packages from testing and basckported to work with buster. Latest kernel in buster-backlports is 5.4.0-0.bpo.4.
Read about how to manage backports here: https://backports.debian.org/Instructions/
// Regards rbh
Please read before requesting help: "Guide to getting help", "Introduction to the Bunsenlabs Lithium Desktop" and other help topics under "Help & Resources" on the BunsenLabs menu
Offline
Thanks for the kernel tips.
Is that the culprit for certain, though? Maybe there's a default setting somewhere I don't know about?
Offline
Lightlocker issue? What happens, if you lock the screen with Super+L?
Instead of restarting, try
writing your password blind,
changing virtual terminal to and fro (Ctrl+Alt+F6-F7-F8) to see Lightdm login screen,
replacing light-locker with another screenlocker.
See https://forums.bunsenlabs.org/viewtopic … 869#p93869 onwards.
Last edited by nore (2020-04-30 04:17:34)
Offline
Is that the culprit for certain, though?
No. For mee to bee certain of that, I need more information. But installing kernel from backports, is no bad idea...
But yor problem is probabley cased by light-locker...
// Regards rbh
Please read before requesting help: "Guide to getting help", "Introduction to the Bunsenlabs Lithium Desktop" and other help topics under "Help & Resources" on the BunsenLabs menu
Offline
@nore thank you for the tips, at least writing the password blind works after locking the screen with <Super>+<L>.
I've removed light-locker and installed xscreensaver. Should I specify the keybinding change in ~/.xkeybindsrc as
# Lock Screen
"xscreensaver-command -lock"
Mod4 + l
or change the
bl-lock
command somewhere?
Last edited by christopherisnow (2020-04-30 13:17:41)
Offline
Openbox keybind settings are defined in ~/.config/openbox.rc.xml.
Offline
Openbox keybind settings are defined in ~/.config/openbox.rc.xml.
In Lithium, window commands are set in bl-rc.xml, but application commands are set using xbindkeys.
(The idea is to have run commands independent of the WM in use.)
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
Ok, then xbindkeys it is.
(Edit: I'm retard here, not on Lithium atm.)
Last edited by nore (2020-04-30 14:57:22)
Offline
@nore thank you for the tips, at least writing the password blind works after locking the screen with <Super>+<L>.
I've removed light-locker and installed xscreensaver. Should I specify the keybinding change in ~/.xkeybindsrc as
# Lock Screen "xscreensaver-command -lock" Mod4 + l
or change the
bl-lock
command somewhere?
Either would work, but if you're not using light-locker, then you could make a personal version of bl-lock:
cp /usr/bin/bl-lock ~/bin
chmod +x ~/bin/bl-lock
# check - it should return your local file
which bl-lock
# edit
bl-text-editor ~/bin/bl-lock
Now edit LOCK_COMMAND at the top to your taste. It's an array so just put in the whole command as-is, without any quotes.
ie in your case:
LOCK_COMMAND=(xscreensaver-command -lock)
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
I had this problem on my desktop machine, which has been reported with lightlocker in a number of distros.
In my case, a fix that worked was to switch to the intel driver by creating /etc/X11/xorg.conf.d/20-intel.conf with contents:
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "AccelMethod" "sna"
EndSection
Offline
^ I use the same file on my old Dell laptop, though not for a lightlocker issue. I also added this line before 'EndSection', it helped with scrolling and video glitches in my case...
Option "TearFree" "true"
Source...
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline