This is probably because I haven't finished porting it to GTK/GNOME3.
** Bug watch added: code.google.com/p/gnome-menu-file-browser-applet/issues #88
http://code.google.com/p/gnome-menu-file-browser-applet/issues/detail?id=88
--
You received this bug notification because you are a member of
See http://code.google.com/p/gnome-menu-file-browser-
applet/issues/detail?id=88
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/760415
Title:
disappears after first use on natty
--
ubuntu-bugs
Is this the same as Bug #259292?
Also, the bugs listed here for File Browser Applet don't appear in
https://bugs.launchpad.net/file-browser-applet. Should they?
--
file-browser-applet crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/337481
You received this bug
OK, I think(hope) I found and fixed the problem. I was defining the new
signal as follows:
applet_preferences_signals [PREFS_CHANGED] =
g_signal_new (prefs_changed,
G_TYPE_FROM_CLASS (gobject_class),
G_SIGNAL_RUN_LAST,
Sigh! I hate real bugs...
Like last time, it seems to happen when the prefs_changed signal is
emitted. That's a signal I create, so the problem may be in how I either
create or invoke that signal. I'll have a look at that and report back
if i find anything odd.
a.
--
file-browser-applet
