openbox crashed with SIGABRT after closing context menu

Bug #938379 reported by karl anliot
554
This bug affects 80 people
Affects Status Importance Assigned to Milestone
OpenBox
Fix Released
High
openbox (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

was using mplayer-gnome was closing a context menu when openbox crashed.
this is the first time it has crashed like this.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: openbox 3.5.0-2ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3
Uname: Linux 3.2.0-14-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.92-0ubuntu1
Architecture: amd64
Date: Tue Feb 21 22:42:38 2012
ExecutablePath: /usr/bin/openbox
InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Alpha amd64 (20120205)
ProcCmdline: openbox --config-file /home/username/.config/openbox/lubuntu-rc.xml
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: openbox
StacktraceTop:
 client_configure ()
 moveresize_end ()
 ?? ()
 ?? () from /usr/lib/libobt.so.0
 g_main_dispatch (context=0x117f300) at /build/buildd/glib2.0-2.31.18/./glib/gmain.c:2510
Title: openbox crashed with SIGABRT in client_configure()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
karl anliot (kanliot) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 client_configure (self=0x0, x=70, y=39, w=911, h=787, user=1, final=1, force_reply=0) at openbox/client.c:3057
 moveresize_end (cancel=<optimized out>) at openbox/moveresize.c:333
 event_handle_client (e=0x7fff9690f750, client=0x11fab00) at openbox/event.c:1491
 event_process (ec=<optimized out>, data=<optimized out>) at openbox/event.c:625
 event_read (source=<optimized out>, callback=<optimized out>, data=<optimized out>) at obt/xqueue.c:338

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in openbox (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
karl anliot (kanliot)
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in openbox (Ubuntu):
status: New → Confirmed
Revision history for this message
karl anliot (kanliot) wrote :

anyone get this bug not running ATI drivers?

Revision history for this message
Stenten (stenten) wrote : Re: [Bug 938379] Re: openbox crashed with SIGABRT after closing context menu

>
> anyone get this bug not running ATI drivers?

Yep, Intel over here....

Revision history for this message
karl anliot (kanliot) wrote :

seems to occur when watching video
managed to get a stack trace during the frequent crashes

#0 client_configure (self=0x0, x=140, y=0, w=1248, h=744, user=1, final=1, force_reply=0) at openbox/client.c:3057
#1 0x00000000004371ec in moveresize_end (cancel=1) at openbox/moveresize.c:333
#2 0x00000000004282b1 in event_handle_client (e=0x7fffffffe130, client=0x6d5460) at openbox/event.c:1491
#3 event_process (ec=<optimized out>, data=<optimized out>) at openbox/event.c:625
#4 0x00007ffff61e3d91 in ?? () from /usr/lib/libobt.so.0
Dwarf Error: Can't read DWARF data from '/usr/lib/debug/lib/x86_64-linux-gnu/libglib-2.0.so.0.3118.0'
#0 client_configure (self=0x0, x=140, y=0, w=1248, h=744, user=1, final=1, force_reply=0) at openbox/client.c:3057

frame output:3057 guint fdecor = self->frame->decorations;

Revision history for this message
karl anliot (kanliot) wrote :

so i'm using mplayer-gnome to get the crashes, seems to happen when I'm clicking on the context menus. Using GL video output. FYI.

I have tried to reproduce just by moving and closing windows, but I cant reproduce. I ahve to wait for openbox to crash, and it usually takes a few hours.

Revision history for this message
karl anliot (kanliot) wrote :

more crashes when closing windows. this time I was clicking a dialog button

Program received signal SIGSEGV, Segmentation fault.
client_configure (self=0x0, x=765, y=326, w=389, h=451, user=1, final=1, force_reply=0) at openbox/client.c:3057
3057 guint fdecor = self->frame->decorations;
#0 client_configure (self=0x0, x=765, y=326, w=389, h=451, user=1, final=1, force_reply=0) at openbox/client.c:3057
#1 0x00000000004371ec in moveresize_end (cancel=1) at openbox/moveresize.c:333
#2 0x00000000004282b1 in event_handle_client (e=0x7fffffffe130, client=0x6d5900) at openbox/event.c:1491
#3 event_process (ec=<optimized out>, data=<optimized out>) at openbox/event.c:625
#4 0x00007ffff61e20d1 in event_read (source=<optimized out>, callback=<optimized out>, data=<optimized out>) at obt/xqueue.c:338
#5 0x00007ffff750fdda in g_main_dispatch (context=0x656300) at /build/buildd/glib2.0-2.31.20/./glib/gmain.c:2510
#6 g_main_context_dispatch (context=0x656300) at /build/buildd/glib2.0-2.31.20/./glib/gmain.c:3047
#7 0x00007ffff75101a0 in g_main_context_iterate (dispatch=1, block=<optimized out>, context=0x656300, self=<optimized out>)
    at /build/buildd/glib2.0-2.31.20/./glib/gmain.c:3118
#8 g_main_context_iterate (context=0x656300, block=<optimized out>, dispatch=1, self=<optimized out>) at /build/buildd/glib2.0-2.31.20/./glib/gmain.c:3055
#9 0x00007ffff751059a in g_main_loop_run (loop=0x669150) at /build/buildd/glib2.0-2.31.20/./glib/gmain.c:3312
#10 0x000000000040f3df in main (argc=3, argv=0x7fffffffe638) at openbox/openbox.c:378

Revision history for this message
karl anliot (kanliot) wrote :

also this time wasn't running gnome player, so disregard earlier comment

Revision history for this message
Sven Romeike (lun4tic) wrote :

Nvidia drivers here and same Problem. using 12.04 32Bit on a Samsung R560 on a normal Ubuntu install with additional lubuntu-desktop. could not reproduce it yet.

I had nothing running just 2 lubuntu filemanagers after login. I clicked a little bit around in the filemanager and the bar on the bottom when suddenly the bug occured.

Revision history for this message
Elthommo (elthommo) wrote :

had this using lubuntu 12.04 lubutu software centre

tags: added: bugpattern-needed
Revision history for this message
Zack Sjoden (zackss) wrote :

On a MacBook Pro 13", 8.1. Running Openbox. After doing an upgrade today I can no longer right click(two finger gesture click) on the desktop to bring the Openbox menu up.

Revision history for this message
Redwolf (viking.redwolf) wrote :

It happened to me SIX consecutive times while trying to move a folder between two PCManFM windows. PCManFM crashed too.

Revision history for this message
Chris Wyatt (wyattmeister) wrote :

This happened to me when I was playing Swell Foop. I was pressing the New button, I may have pressed the button twice in quick succession, but I'm not sure.

Revision history for this message
Qball Cow (qball-qballcow) wrote :

Why is importance medium? This allready caused loss of data for me. (openbox crashes, X restarts to lightdm, open programs loose X connection and crash)

Revision history for this message
ike (igor-kolar) wrote :

Happens to me a lot.
 - when launching wine
 - when the screensaver engages (or when I try to cancel it)
 - sometimes spontaniously

Seen it at least 5x today, including waking up to it (the comp was on during the night). Only started happening with the 12.04 update, never ever once before

Openbox crashes with SIGABRT in client_configure(), just like the initial post says.

I second the motion of #17 that this needs to be upped to high priority. I have lost data to this.

Revision history for this message
NoWiS (qpaydhdt-simon-44ecklps) wrote :
Revision history for this message
Julien Lavergne (gilir) wrote :

Thanks for the link, I uploaded a version of the package including the workaround on the bug tracker, it will be available on Lubuntu-dev staging PPA : https://launchpad.net/~lubuntu-dev/+archive/staging

Could people affected by this bug try to installed the update (be sure to have version 3.5.0-2ubuntu2.1~ppa1), reboot or restart openbox, and try to reproduce the bug ? Thanks.

Revision history for this message
ATIpro (somebody2112) wrote :

Fixed version works great. Can you push it to official updates? This bug is really annoying.

Revision history for this message
Julien Lavergne (gilir) wrote :

It should be fixed in 3.5.0-4 (in 12.10), since the upstream fix is included.

Changed in openbox (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
tobydeemer (tobydeemer) wrote :

Is there any chance this will be back-ported? I don't want to have to upgrade to a non-LTS release to fix this. Or is the staging PPA the only option at this point, aside from installing directly from upstream project?

Thanks.

Revision history for this message
Silviu C. (silviucc) wrote :

Yes, please release a package that contains the fix for us 12.04 users. It's really annoying :/

Changed in openbox:
importance: Unknown → High
status: Unknown → Fix Released
To post a comment you must log in.