GNOME Bugzilla – Bug 136011
panel crash, problem with gnome-vfs / panel / fam
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Debian testing/unstable Package: gnome-vfs Severity: normal Version: GNOME2.4.1 2.4.x Gnome-Distributor: Debian Synopsis: panel crash, problem with gnome-vfs / panel / fam Bugzilla-Product: gnome-vfs Bugzilla-Component: URI handling Bugzilla-Version: 2.4.x BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: The panel crash with some .recently-used files. I've discuted about this with teuf and vuntz, seems to be due to bad support of incorrect URI (example: <URI>action=view</URI> or <uri>file:$HOME</uri>) Steps to reproduce the crash: 1. use a bad URI in a .recently-used file 2. having fam running 3. the panel crashs immediatly Expected Results: should not crash How often does this happen? always Additional Information: There is a lot of dup of this problem but information are missings in most of them, please let this one open, the backtrace is complete and we can reproduce it. The bug doesn't happen in CVS Head apparently due at this hack in the panel code: --- gnome-panel/egg-recent-model.c.orig 2004-03-02 22:44:31.000000000 +0100 +++ gnome-panel/egg-recent-model.c 2004-03-02 22:45:09.000000000 +0100 @@ -1642,7 +1642,7 @@ if (model->priv->limit > 0) { list = egg_recent_model_get_list (model); - egg_recent_model_monitor_list (model, list); + /*egg_recent_model_monitor_list (model, list);*/ g_signal_emit (G_OBJECT (model), model_signals[CHANGED], 0, list); Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' [New Thread 1087553376 (LWP 14113)] 0x4094f3ee in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 44746
Thread 1 (Thread 1087553376 (LWP 14113))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-03-02 17:38 ------- Reassigning to the default owner of the component, gnome-vfs-maint@bugzilla.gnome.org.
I fixed this on HEAD. We should probably do a 2.4 release with it too, since this is a common issue.
Created attachment 25086 [details] [review] The fix commited to HEAD.
seb128 (the reporter) tested it on his 2.4 system and confirmed it was fixing his problem. Closing it now, I'll apply the patch to the stable branch.
*** Bug 136220 has been marked as a duplicate of this bug. ***
*** Bug 136607 has been marked as a duplicate of this bug. ***
*** Bug 136550 has been marked as a duplicate of this bug. ***
*** Bug 136825 has been marked as a duplicate of this bug. ***
*** Bug 133674 has been marked as a duplicate of this bug. ***
*** Bug 137835 has been marked as a duplicate of this bug. ***
*** Bug 137970 has been marked as a duplicate of this bug. ***
*** Bug 138133 has been marked as a duplicate of this bug. ***
*** Bug 147791 has been marked as a duplicate of this bug. ***
*** Bug 139319 has been marked as a duplicate of this bug. ***