GNOME Bugzilla – Bug 360435
crash in Networking: Just clicked on the netw...
Last modified: 2007-04-08 17:29:15 UTC
Version: 2.15.5 What were you doing when the application crashed? Just clicked on the network manager applet on the toolbar (upper righ tside). application just updated with all standard packages now and restarted. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 31985664 vsize: 0 resident: 31985664 share: 0 rss: 8523776 rss_rlim: 0 CPU usage: start_time: 1160226624 rtime: 0 utime: 12 stime: 0 cutime:11 cstime: 0 timeout: 1 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/network-admin' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225746768 (LWP 4621)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 75103
Thread 1 (Thread -1225746768 (LWP 4621))
*** Bug 360436 has been marked as a duplicate of this bug. ***
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
*** Bug 360482 has been marked as a duplicate of this bug. ***
*** Bug 360483 has been marked as a duplicate of this bug. ***
*** Bug 360485 has been marked as a duplicate of this bug. ***
*** Bug 360493 has been marked as a duplicate of this bug. ***
*** Bug 360505 has been marked as a duplicate of this bug. ***
*** Bug 360548 has been marked as a duplicate of this bug. ***
*** Bug 360562 has been marked as a duplicate of this bug. ***
*** Bug 360564 has been marked as a duplicate of this bug. ***
*** Bug 360583 has been marked as a duplicate of this bug. ***
*** Bug 360587 has been marked as a duplicate of this bug. ***
*** Bug 360588 has been marked as a duplicate of this bug. ***
*** Bug 360609 has been marked as a duplicate of this bug. ***
*** Bug 360611 has been marked as a duplicate of this bug. ***
*** Bug 360637 has been marked as a duplicate of this bug. ***
*** Bug 360634 has been marked as a duplicate of this bug. ***
*** Bug 360740 has been marked as a duplicate of this bug. ***
*** Bug 360751 has been marked as a duplicate of this bug. ***
*** Bug 360753 has been marked as a duplicate of this bug. ***
*** Bug 360772 has been marked as a duplicate of this bug. ***
*** Bug 360777 has been marked as a duplicate of this bug. ***
*** Bug 360781 has been marked as a duplicate of this bug. ***
*** Bug 360806 has been marked as a duplicate of this bug. ***
Can somebody please help the developers to fix this bug by trying to reproduce this crash with debugging packages of at least gnome-system-tools/liboobs installed? See http://live.gnome.org/GettingTraces/DistroSpecificInstructions for more information. Thanks a lot in advance, your help is appreciated!
Could anybody get a backtrace with liboobs-1-2-dbg installed?
*** Bug 360925 has been marked as a duplicate of this bug. ***
*** Bug 360856 has been marked as a duplicate of this bug. ***
*** Bug 360952 has been marked as a duplicate of this bug. ***
*** Bug 361045 has been marked as a duplicate of this bug. ***
*** Bug 361050 has been marked as a duplicate of this bug. ***
Can somebody please help the developers to fix this bug by trying to reproduce this crash with debugging packages of at least gnome-system-tools/liboobs installed? Please get a stacktrace with liboobs-1-2-dbg installed. See http://live.gnome.org/GettingTraces/DistroSpecificInstructions for more information. Thanks a lot in advance, your help is appreciated!
*** Bug 361289 has been marked as a duplicate of this bug. ***
The interesting thing here, is that it was the GNOME bug buddy that popped up, instead of Ubuntu's apport. Does Bug Buddy save the core file anywhere afterwards so that it can be gone over retrospectively with the '-dbgsym.ddeb' packages instealled.
(In reply to comment #34) > The interesting thing here, is that it was the GNOME bug buddy that popped up, > instead of Ubuntu's apport. > > Does Bug Buddy save the core file anywhere afterwards so that it can be gone > over retrospectively with the '-dbgsym.ddeb' packages instealled. No, but there are plans along those lines (with the idea being to send the core file to some central server that hopefully already has debugging packages installed specific to your particular distro). It'll take a while to implement, though...
*** Bug 361527 has been marked as a duplicate of this bug. ***
*** Bug 361748 has been marked as a duplicate of this bug. ***
*** Bug 361779 has been marked as a duplicate of this bug. ***
The crash happens when trying to open a site that uses Macromedia flash with a color depth in X of 16 bits. Changing the depth to 24 bits solves the problem. In its wisdom, Macromedia has decided that no user should have to submit itself to the ugliness of a flash animation seen without the proper colors, so the flash plugin crashes in this kind of situation. I guess that's the cause of Firefox crash (except it's just sad that Firefox tries to keep company to the plugin by crashing too :) )
https://launchpad.net/distros/ubuntu/+source/flashplugin-nonfree/+bug/62988 and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=388169 Both provide backtraces. Let us know if it's not enough :) Thanks for your work, Loïc
loic: This bug has nothing to do with firefox or flash; it's a crash in the gnome-system-tools. Maybe gnome-system-tools perhaps crashed for you near the same time that firefox did when you reported bug 361779? Either way, neither of the debian or ubuntu bug reports you link to provide a stack trace for *this* problem.
Sorry for the mistake. Unfortunately, I wasn't trying to do anything gnome-related when bug buddy popped up, and gnome-system-tools covers different applications. If the crash report told us which of them crashed, we could maybe try to reproduce the bug. Else I guess it's going to be hard to provide a stack trace.
*** Bug 361908 has been marked as a duplicate of this bug. ***
*** Bug 362007 has been marked as a duplicate of this bug. ***
*** Bug 362073 has been marked as a duplicate of this bug. ***
*** Bug 362444 has been marked as a duplicate of this bug. ***
*** Bug 362495 has been marked as a duplicate of this bug. ***
*** Bug 362696 has been marked as a duplicate of this bug. ***
*** Bug 362719 has been marked as a duplicate of this bug. ***
*** Bug 362782 has been marked as a duplicate of this bug. ***
*** Bug 363040 has been marked as a duplicate of this bug. ***
here is a trace with liboobs-1-2-dbgsym : ----------- start of trace --------- Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 32739328 vsize: 0 resident: 32739328 share: 0 rss: 8941568 rss_rlim: 0 CPU usage: start_time: 1161181196 rtime: 0 utime: 7 stime: 0 cutime:6 cstime: 0 timeout: 1 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/network-admin' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1225501008 (LWP 17649)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 76979
Thread 1 (Thread -1225501008 (LWP 17649))
----------- end of trace ---------
Teddyber: Thanks! I'll reopen now...
44 duplicates in the 12 days - gnome 2.16 target, blocker. carlos, can you please take a look at this? thanks in advance!
*** Bug 359622 has been marked as a duplicate of this bug. ***
*** Bug 363295 has been marked as a duplicate of this bug. ***
*** Bug 363552 has been marked as a duplicate of this bug. ***
*** Bug 363774 has been marked as a duplicate of this bug. ***
the place where it crashes (according to the bt in comment #53) is a bit puzzling, that line is just a sanity check on a string contained in a DBusMessage (and thus, I assume its contents have travelled through the bus, been stored in the DBusMessage struct and so...), so I don't see why it points to invalid memory... Could someone attach here his /etc/network/interfaces file and the output of this program?: http://www.gnome.org/~carlosg/test-backends It would be run like: ./test-backends IfacesConfig > output Remove the wireless key if you want, but please don't remove the essid, network-admin seems to crash retrieving it.
thanks for taking a look at this. setting to NEEDINFO as per last comment.
*** Bug 364756 has been marked as a duplicate of this bug. ***
Created attachment 75542 [details] output of test-backends script output of test-backends script as requested. hope it helps spotting the bug.
Created attachment 75543 [details] related /etc/network/interfaces file as requested it is related to the previous attachment.
This is fixed for me in 2.16.1 (on Ubuntu Edgy). Can anyone else confirm?
*** Bug 367432 has been marked as a duplicate of this bug. ***
*** Bug 371165 has been marked as a duplicate of this bug. ***
*** Bug 371162 has been marked as a duplicate of this bug. ***
*** Bug 375434 has been marked as a duplicate of this bug. ***
no duplicates for two months, lowering the severity. Can anybody still reproduce this bug with a current GNOME version, or can this be closed?
(In reply to comment #70) > Can anybody still reproduce this bug with a current GNOME version, or can this > be closed? I'm running 2.17.5 and I don't see this problem anymore.
*** Bug 397478 has been marked as a duplicate of this bug. ***
I'm still getting this bug (I think it's the same) using 2.15.5 (Ubuntu Edgy). I've included a stack trace with debug symbols in attachment 3 [details] of 397478 (which I marked as a dup): http://bugzilla.gnome.org/attachment.cgi?id=80657
Just confirming that updating to 2.15.5-0ubuntu5~prop2 resolves the issue on my system. (Network-admin runs without crashing - only difference is that when running as normal user I can't set the location). Cheers.
*** Bug 411614 has been marked as a duplicate of this bug. ***
Closing as FIXED given the last comments (74 and 71 namely)
*** Bug 424746 has been marked as a duplicate of this bug. ***
*** Bug 424745 has been marked as a duplicate of this bug. ***