Summary: | gnome-extra/gnome-utils-2.24.1: baobab crashes at startup without error messages | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Luca Wehrstedt <luca.wehrstedt> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
URL: | http://bugzilla.gnome.org/show_bug.cgi?id=577060 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 238650 |
Description
Luca Wehrstedt
2009-01-25 19:57:59 UTC
could you try to provide a backtrace [1] of the problem ? [1] http://www.gentoo.org/proj/en/qa/backtraces.xml I've never done backtraces, but following the Italian version of the guide I think I've got something useful. The debug is full of (no debugging symbols found), with the exception of: - [Thread debugging using libthread_db enabled] - [New Thread 0x7fa5584f1780 (LWP 13823)] - Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fa5584f1780 (LWP 13823)] 0x00007fa553611beb in g_utf8_validate () from /usr/lib/libglib-2.0.so.0 I think the last is the problem, but I have no idea what it's related to this is a far from complete backtrace. You need to rebuild more packages with debugging symbols. Waiting for a good backtrace. Also, could you try to start it with another locale ? (In reply to comment #4) > Waiting for a good backtrace. Also, could you try to start it with another > locale ? I had the same problem. solution is simple, use the gconf-editor to reset the apps/baobab/properties/skip_scan_uri_list. The problem occurs if you want to scan some disk but not the root mounted partition. This set this property to file:/// which causes the crash (at the moment you start scanning or on next startup). Very easy to reproduce by just setting the property.... ok, reproduced and bug-buddy gave me a nice trace so I reported that upstream. Thanks for the instructions to help reproduce this issue. closing fixed since this is most likely in 2.26 that is now stable. Thanks for reporting. |