GNOME Bugzilla – Bug 608414
crash BadDrawable when closing Ekiga
Last modified: 2013-02-12 08:35:11 UTC
Version: 3.2.5 What were you doing when the application crashed? Closed Ekiga Distribution: Fedora release 9 (Sulphur) Gnome Release: 2.26.3 2009-09-21 (ASPLinux) BugBuddy Version: 2.26.0 System: Linux 2.6.30.9-102.0.140asp.i686 #1 SMP Thu Dec 17 00:24:19 EET 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10603901 Selinux: No Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora GTK+ Modules: canberra-gtk-module, pk-gtk-module, gnomebreakpad Memory status: size: 202059776 vsize: 202059776 resident: 30666752 share: 21155840 rss: 30666752 rss_rlim: 18446744073709551615 CPU usage: start_time: 1264744903 rtime: 4411 utime: 3777 stime: 634 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/ekiga' (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 0xb77ab740 (LWP 2111)] [New Thread 0xb44b6b90 (LWP 2307)] [New Thread 0xb46ccb90 (LWP 2248)] [New Thread 0xb468bb90 (LWP 2247)] [New Thread 0xb7293b90 (LWP 2239)] [New Thread 0xb72d4b90 (LWP 2238)] [New Thread 0xb7252b90 (LWP 2212)] [New Thread 0xb720db90 (LWP 2162)] [New Thread 0xb7315b90 (LWP 2156)] [New Thread 0xb7356b90 (LWP 2155)] [New Thread 0xb7397b90 (LWP 2154)] [New Thread 0xb73d8b90 (LWP 2153)] [New Thread 0xb745ab90 (LWP 2151)] 0x00729422 in __kernel_vsyscall ()
+ Trace 220291
Thread 12 (Thread 0xb73d8b90 (LWP 2153))
The program is running. Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** Gdk **: The program 'ekiga' received an X Window System error. This probably reflects a bug in the program. The error was 'BadDrawable (invalid Pixmap or Window parameter)'. (Details: serial 14881 error_code 9 request_code 132 minor_code 19) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) ----------- .xsession-errors --------------------- The error was 'BadDrawable (invalid Pixmap or Window parameter)'. (Details: serial 14881 error_code 9 request_code 132 minor_code 19) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) aborting... Could not find the frame base for "OpalManager::GarbageMain_PNotifier::Call(PObject&, int) const". Could not find the frame base for "PSimpleThread::Main()". Could not find the frame base for "OpalListener::ListenForConnections_PNotifier::Call(PObject&, int) const". Could not find the frame base for "PSimpleThread::Main()". Could not find the frame base for "PSocket::os_accept(PSocket&, sockaddr*, int*)". Could not find the frame base for "OpalListener::ListenForConnections_PNotifier::Call(PObject&, int) const". Could not find the frame base for "PSimpleThread::Main()". --------------------------------------------------
*** Bug 603046 has been marked as a duplicate of this bug. ***
Can you please check again whether this issue still happens in ekiga 3.2.7 or 3.3.2 and update this report by adding a comment and changing the "Version" field? Thanks a lot.
Does this still appear with ekiga >= 3.9.90? If yes, please report a -d 4 output.
Let's assume this to be OBSOLETE. Please reopen if this is exists.