You are not logged in.
Pages: 1
I found that leaving dwm idle for too long turns the screen black with no way of restoring (although it never suspends, it's like theres just a black sheet over the screen) unless I switch to a virutal console and switch back. I found xautolock through searching and found this post, https://bbs.archlinux.org/viewtopic.php … 15#p785015, and follwed his directions. Unfortunately, it doesn't work. However, when I type 'xautolock' in the terminal, it spits out 'xautolock is already running (PID 918).' The corner function does not work either. What's going on?
Last edited by Haptic (2011-02-16 04:31:38)
Offline
If your machine has an intel graphics chip, you may be hitting this kernel bug which slipped through the cracks
https://bugzilla.kernel.org/show_bug.cgi?id=22672
Offline
It is running through virtualbox, so I'd assume it is using intel graphics. What's that command that shows you your hardware?
Offline
If its running in virtualbox then the bug I posted is not relevant
Offline
Is it normal for dwm to turn black after # minutes on default? If not, is this a virtualbox specific problem?
Offline
No - dwm only does what you tell it to
Is there anything in you xorg log?
Offline
I get this:
[ 26.596] (II) (unnamed): On.
[ 1973.594] (II) (unnamed): Off.
[ 1979.496] (II) VBoxVideo(0): Requested monitor count: 1
[ 1979.624] (II) (unnamed): On.
[ 3045.333] (II) (unnamed): Off.
[ 3053.282] (II) VBoxVideo(0): Requested monitor count: 1
[ 3053.414] (II) (unnamed): On.
[ 9971.785] (II) (unnamed): Off.
[ 9982.533] (II) VBoxVideo(0): Requested monitor count: 1
[ 9982.653] (II) (unnamed): On.
Offline
You do have slock installed, right?
Offline
You do have slock installed, right?
.....no. -_-;
Now I do and it locks fine, but how do I get it to show some text? By luck, I found out you just need to enter your password, but the screen is completely black.
Offline
Just start typing - it's suckless software
Please mark this thread [Solved]
Offline
Pages: 1