GNOME Bugzilla – Bug 356180
crash in Networking: Launching the control pa...
Last modified: 2007-07-29 14:50:19 UTC
Version: 2.15.4 What were you doing when the application crashed? Launching the control panel -- crash. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 60076032 vsize: 0 resident: 60076032 share: 0 rss: 12107776 rss_rlim: 0 CPU usage: start_time: 1158354392 rtime: 0 utime: 20 stime: 0 cutime:20 cstime: 0 timeout: 0 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 -1225374032 (LWP 19847)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 72433
Thread 1 (Thread -1225374032 (LWP 19847))
*** Bug 356185 has been marked as a duplicate of this bug. ***
*** Bug 356187 has been marked as a duplicate of this bug. ***
*** Bug 356188 has been marked as a duplicate of this bug. ***
*** Bug 359613 has been marked as a duplicate of this bug. ***
*** Bug 359612 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.
Created attachment 74345 [details] Stack Trace ClearLooks 091006 This bug was reproduced from: System-->Administration-->Networking
minarwan, thanks a lot! stacktrace looks good, reopening.
*** Bug 361005 has been marked as a duplicate of this bug. ***
I actually haven't had this crash in quite a while, and I don't remember what version I was running at the time. The only issue I've had since then is the "doesn't remember gateway", and that's been fixed. Though it's not part of this bug, I wish there were an option in this panel to "send hostname with DHCP request".
*** Bug 361475 has been marked as a duplicate of this bug. ***
*** Bug 361480 has been marked as a duplicate of this bug. ***
*** Bug 364167 has been marked as a duplicate of this bug. ***
*** Bug 367168 has been marked as a duplicate of this bug. ***
*** Bug 368557 has been marked as a duplicate of this bug. ***
*** Bug 368764 has been marked as a duplicate of this bug. ***
*** Bug 369056 has been marked as a duplicate of this bug. ***
What I have found with regards to this bug is that it specifically occurs on my computer when I add extra hosts to the etc/hosts file (Even when it was done through the control panel UI.) When I remove these hosts, the control panel opens fine again. Hope this helps.
Charl, maybe you could attach your /etc/hosts file to the bug?
Created attachment 75842 [details] Host file that causes control panel to crash
Bingo. I also had two hosts on my /etc/hosts and as I removed them it crashed. Since they had information I shouldn't disclose I didn't make a backup to send over here, but it stopped crashing on my Ubuntu Edgy box.
It doesn't crash on my box with that file, could you get a backtrace of the crash with libgtk2.0-0-dbg and libpango1.0-0-dbgsym installed? Maybe get a valgrind log (https://wiki.ubuntu.com/Valgrind) when you get the bug?
*** Bug 371476 has been marked as a duplicate of this bug. ***
*** Bug 371627 has been marked as a duplicate of this bug. ***
*** Bug 371710 has been marked as a duplicate of this bug. ***
*** Bug 372096 has been marked as a duplicate of this bug. ***
More (light) info, it doesn't matter how you do it, but add hosts as IP\t+name( name)* => crash IP +name( name)* => crash IP[\t ]+name( name)* => crash Through network-admin's GUI => crash It seems to die while *parsing* the hosts file, which it would need in order to fill the Hosts tab with the current contents of the hosts file.
Rui, could you get a debug backtrace and a valgrind log for it?
Created attachment 76175 [details] working /etc/hosts file
Created attachment 76176 [details] failing /etc/hosts file
Created attachment 76177 [details] stack trace using the "failing /etc/hosts file"
How do I use valgrind? I never did so before. Are the attachments I just made useful?
Ok, it was easy enough :)
Created attachment 76181 [details] valgrind run of network-admin with "failing /etc/hosts file" Also includes a little part that might be related to bug-buddy
Thank you for the work on that? Are you using Ubuntu edgy? Could you get a similar log with gnome-system-tools-dbgsym libglib2.0-0-dbg libpango1.0-0-dbgsym installed.
I'm sorry, I would if I could find them. Which repo are they living on?
That is, I only found libglib2.0-0-dbg libpango1.0-0-dbg, but not the first one....
Created attachment 76189 [details] stack trace repetition with libglib2.0-0-dbg libpango1.0-0-dbg
Created attachment 76190 [details] valgrind repetition with libglib2.0-0-dbg libpango1.0-0-dbg
Version: 2.15.5 What were you doing when the application crashed? 1.- Start network-admin as usual. 2.- Add some lan hosts at the "Hosts" tab. 3.- Close network-admin as usual. 4.- Start network-admin as usual. 5.- Crash $%&"@ Note: the problem can be solved deleting the folder ~/.gnome2/network-admin-locations http://bugzilla.gnome.org/show_bug.cgi?id=371476
Cedric: that solves the crash, but doesn't solve the problem, however it is a hint that the problem may be in a comparison between the hosts file and some profile? Does this happen on network-admin? And was the XML format config file abandoned?
having gnome-system-tools-dbgsym installed too would be nice, you can get it from "deb http://people.ubuntu.com/~pitti/ddebs edgy main universe" (http://live.gnome.org/GettingTraces/DistroSpecificInstructions has details about that)
Thanks! here they go!
Created attachment 76233 [details] new repetition of stack trace using the "failing /etc/hosts file"
Created attachment 76234 [details] new repetition of valgrind using the "failing /etc/hosts file"
*** Bug 373308 has been marked as a duplicate of this bug. ***
*** Bug 374417 has been marked as a duplicate of this bug. ***
*** Bug 374612 has been marked as a duplicate of this bug. ***
*** Bug 375124 has been marked as a duplicate of this bug. ***
*** Bug 375224 has been marked as a duplicate of this bug. ***
*** Bug 375247 has been marked as a duplicate of this bug. ***
*** Bug 375397 has been marked as a duplicate of this bug. ***
*** Bug 361647 has been marked as a duplicate of this bug. ***
*** Bug 363970 has been marked as a duplicate of this bug. ***
*** Bug 358994 has been marked as a duplicate of this bug. ***
*** Bug 363855 has been marked as a duplicate of this bug. ***
*** Bug 362698 has been marked as a duplicate of this bug. ***
*** Bug 363976 has been marked as a duplicate of this bug. ***
*** Bug 363988 has been marked as a duplicate of this bug. ***
*** Bug 367782 has been marked as a duplicate of this bug. ***
*** Bug 369051 has been marked as a duplicate of this bug. ***
*** Bug 370112 has been marked as a duplicate of this bug. ***
*** Bug 372597 has been marked as a duplicate of this bug. ***
*** Bug 373799 has been marked as a duplicate of this bug. ***
*** Bug 374501 has been marked as a duplicate of this bug. ***
*** Bug 374552 has been marked as a duplicate of this bug. ***
*** Bug 376008 has been marked as a duplicate of this bug. ***
Sorry for the spam, moving to pango, seems to be an issue there
*** Bug 376048 has been marked as a duplicate of this bug. ***
*** Bug 376242 has been marked as a duplicate of this bug. ***
*** Bug 376243 has been marked as a duplicate of this bug. ***
*** Bug 376910 has been marked as a duplicate of this bug. ***
*** Bug 377384 has been marked as a duplicate of this bug. ***
*** Bug 377970 has been marked as a duplicate of this bug. ***
*** Bug 378582 has been marked as a duplicate of this bug. ***
*** Bug 378906 has been marked as a duplicate of this bug. ***
*** Bug 379177 has been marked as a duplicate of this bug. ***
*** Bug 379186 has been marked as a duplicate of this bug. ***
*** Bug 378988 has been marked as a duplicate of this bug. ***
*** Bug 379720 has been marked as a duplicate of this bug. ***
*** Bug 380604 has been marked as a duplicate of this bug. ***
64 duplicates in 30 days, GNOME 2.16.x target blocker. we have several stacktraces and valgrind reports attached here.
*** Bug 381206 has been marked as a duplicate of this bug. ***
*** Bug 381076 has been marked as a duplicate of this bug. ***
*** Bug 381373 has been marked as a duplicate of this bug. ***
*** Bug 381491 has been marked as a duplicate of this bug. ***
*** Bug 381490 has been marked as a duplicate of this bug. ***
*** Bug 381481 has been marked as a duplicate of this bug. ***
*** Bug 378563 has been marked as a duplicate of this bug. ***
*** Bug 378236 has been marked as a duplicate of this bug. ***
*** Bug 383725 has been marked as a duplicate of this bug. ***
*** Bug 383938 has been marked as a duplicate of this bug. ***
*** Bug 385622 has been marked as a duplicate of this bug. ***
*** Bug 386060 has been marked as a duplicate of this bug. ***
*** Bug 386496 has been marked as a duplicate of this bug. ***
*** Bug 386529 has been marked as a duplicate of this bug. ***
*** Bug 381889 has been marked as a duplicate of this bug. ***
*** Bug 388457 has been marked as a duplicate of this bug. ***
*** Bug 388571 has been marked as a duplicate of this bug. ***
*** Bug 389180 has been marked as a duplicate of this bug. ***
*** Bug 389431 has been marked as a duplicate of this bug. ***
*** Bug 389436 has been marked as a duplicate of this bug. ***
*** Bug 390715 has been marked as a duplicate of this bug. ***
*** Bug 392143 has been marked as a duplicate of this bug. ***
*** Bug 392304 has been marked as a duplicate of this bug. ***
*** Bug 392305 has been marked as a duplicate of this bug. ***
*** Bug 392335 has been marked as a duplicate of this bug. ***
*** Bug 392694 has been marked as a duplicate of this bug. ***
*** Bug 392833 has been marked as a duplicate of this bug. ***
*** Bug 393434 has been marked as a duplicate of this bug. ***
*** Bug 393667 has been marked as a duplicate of this bug. ***
*** Bug 393806 has been marked as a duplicate of this bug. ***
*** Bug 393807 has been marked as a duplicate of this bug. ***
*** Bug 393653 has been marked as a duplicate of this bug. ***
*** Bug 394844 has been marked as a duplicate of this bug. ***
*** Bug 395175 has been marked as a duplicate of this bug. ***
*** Bug 395469 has been marked as a duplicate of this bug. ***
*** Bug 396024 has been marked as a duplicate of this bug. ***
*** Bug 396025 has been marked as a duplicate of this bug. ***
*** Bug 396038 has been marked as a duplicate of this bug. ***
*** Bug 396253 has been marked as a duplicate of this bug. ***
*** Bug 397209 has been marked as a duplicate of this bug. ***
*** Bug 397568 has been marked as a duplicate of this bug. ***
*** Bug 398087 has been marked as a duplicate of this bug. ***
*** Bug 398078 has been marked as a duplicate of this bug. ***
*** Bug 398167 has been marked as a duplicate of this bug. ***
*** Bug 399203 has been marked as a duplicate of this bug. ***
*** Bug 399420 has been marked as a duplicate of this bug. ***
*** Bug 388471 has been marked as a duplicate of this bug. ***
*** Bug 394659 has been marked as a duplicate of this bug. ***
*** Bug 400182 has been marked as a duplicate of this bug. ***
*** Bug 400447 has been marked as a duplicate of this bug. ***
*** Bug 403348 has been marked as a duplicate of this bug. ***
*** Bug 405644 has been marked as a duplicate of this bug. ***
*** Bug 405833 has been marked as a duplicate of this bug. ***
Thanks for the comments, juzging from the steps to reproduce the bug, I think this is the same than what I've fixed today in svn trunk, it turned out to be an invalid memory free, the bt doesn't look the same, but it's probably the memory corruption... Please reopen if it still happens with today's svn trunk, g-s-t 2.17.91 or older :) *** This bug has been marked as a duplicate of 354536 ***
*** Bug 407200 has been marked as a duplicate of this bug. ***
*** Bug 407383 has been marked as a duplicate of this bug. ***
*** Bug 407804 has been marked as a duplicate of this bug. ***
*** Bug 416416 has been marked as a duplicate of this bug. ***
*** Bug 417306 has been marked as a duplicate of this bug. ***
*** Bug 428168 has been marked as a duplicate of this bug. ***
*** Bug 432932 has been marked as a duplicate of this bug. ***
*** Bug 444025 has been marked as a duplicate of this bug. ***
*** Bug 394403 has been marked as a duplicate of this bug. ***
*** Bug 432488 has been marked as a duplicate of this bug. ***