You are not logged in.
I just experienced a crash in openbox due to java. This fix works (scroll to last reply):
https://bbs.archlinux.org/viewtopic.php?id=130654
I just realized that when I updated to "3.5.0-5" a while back this had still not gotten fixed. I tested the same fix and it works. Not sure how to implement a patch or if this can be done so that other people do not have to experience this. Not sure why it never got fixed as the fix was found on their bug tracker before this last release. I know that a lot of our packages are pretty vanilla so I am not sure what the official policy is on this is or if an alternate PKGBUILD would have to be created. I am interested in any feedback on this. Thanks.
Last edited by dodo3773 (2012-03-31 05:13:34)
Offline
The patch in that bug report was submitted by the bug reporter in October 2011, and the status is still "ASSIGNED" i.e. no fix has been applied yet, despite the patch submission. Also, Openbox 3.5.0 was released in August 2011, so clearly it does not include this patch.
Arch policy here is to continue to provide the current stable upstream release. You should contact the Openbox developers regarding the fix for this problem.
Offline
The patch in that bug report was submitted by the bug reporter in October 2011, and the status is still "ASSIGNED" i.e. no fix has been applied yet, despite the patch submission. Also, Openbox 3.5.0 was released in August 2011, so clearly it does not include this patch.
Arch policy here is to continue to provide the current stable upstream release. You should contact the Openbox developers regarding the fix for this problem.
Thanks for the clarification. The reason I was confused is that sometimes in a PKGBUILD I see patch files. Marking thread as solved. I hope they fix this in the next major release / before we get another version update to 3.5.0-6.
Offline
The new openbox does contain a patch for gtk3
https://projects.archlinux.org/svntogit … fed830d5c3
That is not vanilla like you say. What is the difference?
Offline
Hmm... the difference seems to be that one was reported on the Arch bugtracker, and the other wasn't.
Post an Arch report for your title matching bug, referring to the related Openbox report - that's what the gtk bug reporter did.
More generally - either my understanding of Arch's patching policy is flawed, or the policy is not applied as rigorously as I thought. ![]()
Offline
Hmm... the difference seems to be that one was reported on the Arch bugtracker, and the other wasn't.
Post an Arch report for your title matching bug, referring to the related Openbox report - that's what the gtk bug reporter did.
More generally - either my understanding of Arch's patching policy is flawed, or the policy is not applied as rigorously as I thought.
Nope. You are exactly right. I contacted the maintainer and it is being fixed now. I guess I should have filed a bug instead of whining on a forum hahaha.
Offline
As I replied to dodo3773's e-mail - I don't see reason to not apply patch from the official bugtracker, if it can fix serious or annoying bug.
Offline
Sure - I just thought Arch devs (and TUs) only used patches that had been accepted and merged by upstream devs, that's all.
Offline
Just updated to 3.5.0-7 All problems fixed and it's working great. Thanks Barthalion.
Offline