You are not logged in.
Dear All,
I've been experiencing some problems with my openbox environment lately. After a while (10-60 min) the set of processes launched at xinit time by openbox enter status "T" which means "stopped, either by a job control signal or because it is being traced." (quotation from SO Topic) and, afterwards, most of the applications freeze. Nonetheless, I can always open new applications switching to another desktop of my openbox session.
Here's an htop screenshot taken immediately after the freeze:
I was not able to find any relevant information in the docs nor backtraces of dbus-launch in coredumpctl.
Can someone please help me identifying the problem?
Thanks,
Pietro
P.S.: memtest86+ reports that memory is fine.
Edit: removed large image and added thumbnails. Sorry about that.
Last edited by pie86 (2016-09-16 08:40:36)
Offline
Read the Code of Conduct and only post thumbnails http://wiki.archlinux.org/index.php/Cod … s_and_code
Offline
Since when I removed dbus-launch from my .xinitrc I haven't experienced new freezes.
My .xinitrc now reads:
exec openbox-session
Fingers crossed...
Offline
No need to cross your fingers; the move to dbus from libdbus deprecated dbus-launch.
Offline
Damn, I missed that in the news! Thank you!
Offline
I also missed the change that is needed when launching the window manager.
I was launching my xmonad with "exec dbus-launch --exit-with-session xmonad". I replaced it with "exec xmonad" and the issue is gone.
Here is another thread where we didn't figure out it was related to dbus.
Thanks.
Offline