You are not logged in.
gfAfter upgrading to awesome 3.5 I'm experiencing random X crashes (with SLIM, if that matters).
/var/log/slim.conf sports repeated "unexpected signal 15", but I don't know if it is related.
Problem seems related to this thread, but doesn't contain a working solution. Are there other logs I should check?
Last edited by Bladtman242 (2013-01-13 21:34:31)
Offline
Check the upstream tracker. There's something similar already reported.
Offline
Now is this similar to the issue as where (I'm using startx from the terminal and not slim/gdm/xdm/kdm) and quitting from awesome locks up the screen? I have tested that I can still reach it by network application and if I have sshd running I should be able to break out somehow. It still responds to power switch when I press it, by running systemd shutdown sequence.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
AndyRTR: I guess you're referring to the thread/task I linked in the first post?
I was hoping the archers might have had a solution ![]()
I'm growing fairly tired of awesome wm's ever changing syntax and api..
nomorewindows I don't know if it is related but it doesn't sound like the issue I have ![]()
EDIT:
Bug report/thread seems to fit my problem. Marking this thread as solved, and waiting impatiently.
Last edited by Bladtman242 (2013-01-13 21:34:12)
Offline
Pardon, I found that awesome wasn't failing everytime or that it actually had anything to do with awesome, it seems to be something with X is stalling when I exit any WM/DE part of the time.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
No pardon necessary.
While I can't help you, I hope you find a solution.
I'd suggest starting your own thread about it though.
Being marked as solved, I doubt this thread will receive much further attention.
Offline