GNOME Bugzilla – Bug 323331
Baobab crash on startup
Last modified: 2006-07-28 11:15:26 UTC
From: Albert Wagner <albertwagner@cox.net> To: submit@bugs.gnome.org X-Mailer: bug-buddy 2.12.1 Subject: Baobab crash on startup Distribution: Ubuntu 5.10 (breezy) Package: baobab Severity: Normal Version: GNOME2.12.1 2.2.0 Gnome-Distributor: Ubuntu Synopsis: Baobab crash on startup Bugzilla-Product: baobab Bugzilla-Component: general Bugzilla-Version: 2.2.0 BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash:Baobab pops up and is immediately followed by an error dialog. Steps to reproduce the crash: 1. Invoke Baobab from the menu 2. deselect one of the 2 disk volumes for scan 3. Invoke Baobab Expected Results: No crash How often does this happen? Everytime Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/baobab' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (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) [Thread debugging using libthread_db enabled] [New Thread -1223170368 (LWP 15291)] [New Thread -1224889424 (LWP 15294)] (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) 0xffffe410 in __kernel_vsyscall ()
+ Trace 64442
Thread 1 (Thread -1223170368 (LWP 15291))
------- Bug moved to this database by unknown@gnome.bugs 2005-12-06 01:43 UTC ------- Unknown version 2.2.0 in product baobab. Setting version to "unspecified". The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was albertwagner@cox.net.
Fixed in current CVS version
*** Bug 326223 has been marked as a duplicate of this bug. ***
*** Bug 339862 has been marked as a duplicate of this bug. ***
*** Bug 348960 has been marked as a duplicate of this bug. ***
After being poked by Emmanual (see bug 348960 comment 7) I just had a close look at the code and CVS. Seems, when initially importing baobab into gnome-utils, some code was missed. (Note: This probably does not only apply here!) > 2005-12-06 Fabio Marzocca <thesaltydog@gmail.com> > > * src/bbthread.c: (bb_scan_is_local): > * src/props.c: (check_toggled): > > Fixes bug #323331 According to that ChangeLog entry and the old baobab module in CVS, [1] is the relevant change. See the files mentioned above in the baobab module in CVS. The file names changed since, bbthread.c is not part of the baobab code in gnome-utils at all (debug change only anyway), but the check_toggled() function still looks the same, now in baobab-prefs.c. Obviously, the patch for this bug did not make it into this module. REOPENing. Checked against gnome-utils 2.15.90. [1] http://cvs.gnome.org/viewcvs/baobab/src/props.c?hideattic=0&r1=1.8&r2=1.9&makepatch=1&diff_format=h
Confirming as per duplicates and previously applied patch.
Karsten, sorry to reply just now, but I should confirm that THIS bug 323331 has been fixed with the patch on 2005-12-06. Then, the application has been merged in gnome-utils and several modules has been reworked and changed name. For instance, bbthread.c has been completely merged into other modules. I can confirm that the current check_toggled() function is the one that has fixed this bug, as now the main root disk cannot be un-checked. Currently, baobab inherits gnome-utils version. The CVS HEAD version is 2.15.1