You are not logged in.
This is a very interesting behavior. I remember this happening before and i just ignored it but it happened again.
So, basically when i run a print the volume using dzen and at that point i reload xmonad "mod-q", i get logged out of my session and sent to the login screen (lxdm). This is what i mean when i show the volume using dzen: http://dmwit.com/volume/
Also noticed this behavior when i printed the WS name using "ShowWName" Layout. At the time the WS name is showing and i reload xmonad, i get logged out.
I really dont know who to blame for this behavior or where to begin looking.
Does this happen to anyone else?
.o+` dvmacias@ARCH
`ooo/ OS: Arch Linux
`+oooo: Kernel: x86_64 Linux 3.18.6-1-ARCH
`+oooooo: Uptime: 3d 22h 7m
-+oooooo+: Packages: 815
`/:-:++oooo+: Shell: bash 4.3.33
`/++++/+++++++: Resolution: 3360x1050
`/++++++++++++++: WM: Xmonad
`/+++ooooooooooooo/` GTK Theme: Adwaita [GTK2], Adwaita [GTK3]
./ooosssso++osssssso+` Icon Theme: gnome
.oossssso-````/ossssss+` Font: Cantarell 11
-osssssso. :ssssssso. CPU: Intel Core i5-3470 CPU @ 3.6GHz
:osssssss/ osssso+++. RAM: 663MB / 3832MB
/ossssssss/ +ssssooo/-
`/ossssso+/:- -:/+osssso+-
`+sso+:-` `.-/+oso:
`++:. `-/+/
.` `/
Any ideas?
Thanks
Last edited by davama (2016-10-21 15:00:51)
Offline
Since no one has replied it is either because no one has experienced it or i have not provided understandable info.
Regardless i have more info:
So when i cause an urgency hint:
sleep 2; echo -e "\a"
I can't just reload xmonad "mod-q" or "xmonad --restart" without first clearing the urgencyhint because my screens blackout and i go back to my lxdm screen.
Why could this be happening?
Offline
Read your journal and Xorg's log immediately after you are kicked out.
Offline
Thank you for the reply.
I looked at it and it had nothing helpfull. ~/.xsessions-error was empty.
I went to the xmonad irc and it sort of narrowed it down a bit. So here are my results:
When i evoke an urgency hint and "mod-q" that is when it crashes.
from xmonad.hs file
myUrgentHook = dzenUrgencyHook
{ args =
[ "-fg", (colorLook Orange 0)
, "-bg", (colorLook Green 1)
, "-title-name", "UrgentDzen"
, "-xs", "1"
, "-fn", myFont] }
myUrgencyConfig = urgencyConfig {suppressWhen= Visible, remindWhen = (Every (minutes 1.0))}
......
main = do
.....
xmonad $ withUrgencyHookC myUrgentHook myUrgencyConfig
--xmonad $ withUrgencyHook myUrgentHook
I was told that the suspect is the timer for dzen. So i tested as to when it crashes:
With dzen timer on:
dzen bar showing + pplog on, then "mod-q" = crash and log out
pplog on, then "mod-q" = crash and log out
Without dzen timer:
dzen bar showing + pplog on, then "mod-q" = crash and log out
pplog on, then "mod-q" = successfull xmonad restart with urgency hint still on my pplog
Using xmonad 0.11.1
Hope this makes sense.
Thanks
Dave
Offline