baobab segfault on start after upgrade to 2.6.27.11

[Eric Morgan]

Binary package hint: baobab

Had to upgrade kernel because my log file were filling up the hard drive and now the Disk Usage Analyzer is crashing. Actually it crashes with the .9 Kernel also. Ubuntu Intrepid 8.10

Dec 19 20:13:09 legolas kernel: [ 332.025818] baobab[6711]: segfault at 1 ip 00007fb81a7c5110 sp 00007fff27cf2468 error 4 in libglib-2.0.so.0.1800.2[7fb81a75c000+c3000]

[Eric Morgan (gemorgan)]

Is there any additional information needed to help solve this? This tool is rather critical for those running on hard drive space constrained laptops...

[Eric Morgan (gemorgan)]

I do confirm the tool works on my desktop system running 2.6.27.9. I haven't updated the kernel there yet because of the hoops I have to jump through in order to get the graphics card working after a kernel update...

[Hew (hew)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

[Fabio Marzocca (thesaltydog)]

I don't believe the crash is due to kernel version. I am running 2.6.27-11 and everything is fine, so as in other users too. It could be useful to have a stack trace for that crash.

[Eric Morgan (gemorgan)]

Yes there is no crash report associated with the failure to start. I just installed a fresh system on another machine and it's working fine there. But still not working on my laptop. Something during the update that updated the kernel caused the failure not necessarily the kernel itself.

Please point me to instructions on how to do a stack trace so I can help out.

Thanks!
Eric

[sehrgut (sehrgut)]

Don't call it invalid just because no one's uploaded a full crash report.

[Hew (hew)]

The bug title mentions this is a segfault, so it should be possible to obtain an apport crash file for this bug. Marking the bug as invalid is reasonable in this case, as mentioned previously.

Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. It would also help if you tested with the Ubuntu development release, Jaunty Jackalope, which includes gnome-utils (baobab) 2.25.90-0ubuntu1. Thanks again for your report.

[Hew (hew)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!