You are not logged in.
Today's upgrade of Openbox to 3.5.0-6 seems to have stabilized that platform immensely. The underlying bug may still exist in Gtk3, but now Openbox now seems to defend itself and is as stable as a rock. I've tested my code, gnome-disk-utility, Nautilus, and Gtk3-demo.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Today's upgrade of Openbox to 3.5.0-6 seems to have stabilized that platform immensely.
Pretty sure it is the exact same patch that was mentioned earlier in this thread. Off-topic: I talked to the maintainer about including a patch for java crashing X in openbox and it is being worked on right now. So, expect an Openbox 3.5.0-7 soon hopefully.
Offline
ewaller wrote:Today's upgrade of Openbox to 3.5.0-6 seems to have stabilized that platform immensely.
Pretty sure it is the exact same patch that was mentioned earlier in this thread.
Yeah, I would bet real money on that. I did not implement that patch figuring I would wait this one out (I've been busy installing dd-wrt on my router -- very cool, BTW). When I saw OB pop up on the change list, I was hopeful -- and then happy
Last edited by ewaller (2012-05-12 00:45:52)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Update to 3.5.0-7 All problems fixed now.
Offline
Sorry to take up this "old" discussion. It seems the problem still persists. I'm linking to another thread in which most likely the same problem is described.
Offline
Hey, one of the updates fixed the problem for me. I think it was an Openbox update. Maybe this happens in some other window manager then? Or are you using Openbox?
Offline