Kubuntu System Settings crashes on exit

Bug #96703 reported by Diego Moya on 2007-03-26
4
Affects Status Importance Assigned to Milestone
libx11 (Ubuntu)
Undecided
Unassigned

Bug Description

Latest alpha version of Kubuntu 7.04, running from LiveCD

1) Open System Settings
2) Click Monitor & Display
3) Click Administrator mode
4) Click Hardware tab->Configure
5) Click Detect monitor (mine is a Iiyama VisionMaster Pro 410)
6) Hit OK
7) Hit Apply, Continue
8) Close the System Setting window
At this point, a KDE Crash Handler window appears, reporting a signal 6 (SIGABRT) in kcmshell.

My machine's Ubuntu hardware database entry : 3181d9b945bad71be9e66ab9294cfc58

This is the dump in the crash window:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233220912 (LWP 11018)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0xb7f50410 in __kernel_vsyscall ()
#7 0xb7d01df0 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb7d03641 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb7cfb43b in __assert_fail () from /lib/tls/i686/cmov/libc.so.6
#10 0xb682c6f4 in xcb_xlib_lock () from /usr/lib/libxcb-xlib.so.0
#11 0xb69fdc8c in ?? () from /usr/lib/libX11.so.6
#12 0x0805a9e8 in ?? ()
#13 0x0000011b in ?? ()
#14 0xb6ac9000 in ?? ()
#15 0x00804d1c in ?? ()
#16 0xb6aa2a4c in ?? () from /usr/lib/libX11.so.6
#17 0x0805a478 in ?? ()
#18 0xbfcbed6c in ?? ()
#19 0xb69da225 in XFreeCursor () from /usr/lib/libX11.so.6
Backtrace stopped: frame did not save the PC

Jamey Sharp (sharpone) wrote :

We believe this bug is fixed in current upstream libX11 git.

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

Other bug subscribers