openbox crashed with SIGABRT in client_configure()

Bug #1167675 reported by Benjamin
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openbox (Ubuntu)
New
Undecided
Unassigned

Bug Description

occured while I switched from filemanager PCManFM 0.9.10 to gnome-terminal

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: openbox 3.5.0-2ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-40.64-generic-pae 3.2.40
Uname: Linux 3.2.0-40-generic-pae i686
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: i386
Date: Thu Apr 11 04:34:08 2013
ExecutablePath: /usr/bin/openbox
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3)
MarkForUpload: True
ProcCmdline: openbox --config-file /home/username/.config/openbox/lubuntu-rc.xml
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: openbox
StacktraceTop:
 client_configure ()
 moveresize_end ()
 ?? ()
 ?? () from /usr/lib/libobt.so.0
 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: openbox crashed with SIGABRT in client_configure()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

Revision history for this message
Benjamin (nailartcenter) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #938379, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-i386-retrace
Revision history for this message
Benjamin (nailartcenter) wrote :

the duplicate status is wrong maybe wrong, because there is fixed but not for me.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.