It includes most of upstream patches already applied in 2.28.4-r1 and also seems to fix upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=626362 (that I start to suffer a few days ago :-( ). I think that upstream bug is important enough to also request its fast stabilization. Thanks a lot Reproducible: Always
+*nautilus-sendto-2.28.5 (01 Sep 2010) + + 01 Sep 2010; Pacho Ramos <pacho@gentoo.org> + +nautilus-sendto-2.28.5.ebuild, + +files/nautilus-sendto-2.28.5-commandline-help.patch, + +files/nautilus-sendto-2.28.5-fix-memleaks.patch: + Version bump with most of fixes already included in 2.28.4-r1 and updated + translations. This also fixes important segfaults suffered by me with + gnome-bluetooth and empathy plugins (upstream bug #626362). + Arches, please test and stabilize this version since it solves an important segfault, to test simply install it with net-wireless/gnome-bluetooth-2.30.0 and net-im/empathy-2.30.2, then, restart nautilus and right click on a file for using affected plugins. If nautilus-sendto window is opened, upstream bug #626362 is solved (it works for me... but better test it yourself also ;-)) Thanks
amd64 done
amd64 here, having segfault in both 2.28.4-r1 and 2.28.5
In my case the segfault is fixed in 2.28.5 on, for now, the two machines I have checked If you are still suffering a segfault with 2.28.5, I suggest you to try to get a backtrace with bug-buddy and, then, opening a new bug upstream (and please, let us know about that bug report ;-)) Thanks Remaining arches: please stabilize anyway as explained along this comment -> works for me and, in the worst possible scenario, it's "as bad as current stable"
I tried to create a backtrace using gdb, but all I got is this, altough I enabled debug-useflag and compiled both nautilus and nautilus-sendto with -ggdb $ gdb nautilus-sendto warning: Can not parse XML syscalls information; XML support was disabled at compile time. GNU gdb (Gentoo 7.0.1 p1) 7.0.1 Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". For bug reporting instructions, please see: <http://bugs.gentoo.org/>... Reading symbols from /usr/bin/nautilus-sendto...(no debugging symbols found)...done. (gdb) run test.pdf Starting program: /usr/bin/nautilus-sendto test.pdf [Thread debugging using libthread_db enabled] Init nautilus burn plugin Init pidgin plugin Init removable-devices plugin Init evolution plugin Program received signal SIGSEGV, Segmentation fault. 0x0000000000000000 in ?? () (gdb) quit A debugging session is active. Inferior 1 [process 11539] will be killed. Quit anyway? (y or n) y
I am sure bug-buddy should catch it simply making nautilus-sendto crash, but you will probably need to recompile with debug symbols more pieces like gtk+, glib, nautilus and gconf
just installed bug-buddy and it doesn't catch anything (actually, I don't know how to do that) ... does anybody know how to get a "true" backtrace (I still prefer gdb)?
(In reply to comment #6) > I am sure bug-buddy should catch it simply making nautilus-sendto crash, but > you will probably need to recompile with debug symbols more pieces like gtk+, > glib, nautilus and gconf > After installing bug-buddy (that will use gdb to get backtrace) try: FEATURES="$FEATURES splitdebug" CFLAGS="-O2 -pipe -ggdb" CXXFLAGS="-O2 -pipe -ggdb" emerge -1 nautilus-sendto gtk+ glib nautilus gconf gnome-bluetooth And, then, "killall nautilus" or log out and log in again to run recompiled nautilus.
Well, after recompiling all that stuff, the bug does not appear any more ...
Tested on x86 fails here with USE='bluetooth' FEATURES='test' USE='nautilus ' emerge -1v net-wireless/gnome-bluetooth succeeded USE='-bluetooth -cdr -doc -gajim -mail -pidgin -upnp' succeeded for =gnome-extra/nautilus-sendto-2.28.5 USE='-bluetooth -cdr doc gajim -mail -pidgin -upnp' succeeded for =gnome-extra/nautilus-sendto-2.28.5 USE='bluetooth -cdr -doc -gajim mail -pidgin -upnp' failed for =gnome-extra/nautilus-sendto-2.28.5 USE='-bluetooth -cdr doc -gajim mail -pidgin -upnp' succeeded for =gnome-extra/nautilus-sendto-2.28.5 USE='bluetooth -cdr -doc gajim mail pidgin -upnp' failed for =gnome-extra/nautilus-sendto-2.28.5 USE='-bluetooth cdr -doc gajim mail pidgin -upnp' succeeded for =gnome-extra/nautilus-sendto-2.28.5 USE='-bluetooth -cdr -doc -gajim -mail -pidgin upnp' succeeded for =gnome-extra/nautilus-sendto-2.28.5 USE='-bluetooth cdr doc gajim -mail -pidgin upnp' succeeded for =gnome-extra/nautilus-sendto-2.28.5 USE='-bluetooth -cdr -doc -gajim mail -pidgin upnp' succeeded for =gnome-extra/nautilus-sendto-2.28.5 USE='-bluetooth cdr -doc -gajim -mail pidgin upnp' succeeded for =gnome-extra/nautilus-sendto-2.28.5 USE='bluetooth cdr -doc -gajim -mail pidgin upnp' failed for =gnome-extra/nautilus-sendto-2.28.5 USE='-bluetooth -cdr -doc gajim -mail pidgin upnp' succeeded for =gnome-extra/nautilus-sendto-2.28.5 USE='bluetooth cdr doc gajim -mail pidgin upnp' failed for =gnome-extra/nautilus-sendto-2.28.5 USE='bluetooth -cdr -doc -gajim mail pidgin upnp' failed for =gnome-extra/nautilus-sendto-2.28.5 USE='-bluetooth cdr doc gajim mail pidgin upnp' succeeded for =gnome-extra/nautilus-sendto-2.28.5 USE='bluetooth cdr doc gajim mail pidgin upnp' failed for =gnome-extra/nautilus-sendto-2.28.5
(In reply to comment #10) > Tested on x86 fails here with USE='bluetooth' What is exactly failing? "tests" or building with some USE flags? In that case, could you open a separate bug report (even if it would probably be an upstream problem). Anyway, I really doubt it's a regression over current stable and I think it can go stable anyway...
(In reply to comment #11) > (In reply to comment #10) > > Tested on x86 fails here with USE='bluetooth' > > What is exactly failing? "tests" or building with some USE flags? In that case, > could you open a separate bug report (even if it would probably be an upstream > problem). Anyway, I really doubt it's a regression over current stable and I > think it can go stable anyway... > Opened bug 340429 With USE="bluetooth" fails with file collisions. * Detected file collision(s): * * /usr/lib/nautilus-sendto/plugins/libnstbluetooth.la * /usr/lib/nautilus-sendto/plugins/libnstbluetooth.so * /usr/lib/debug/usr/lib/nautilus-sendto/plugins/libnstbluetooth.so.debug
stable x86, thanks David
Tested as OK on SPARC64, please stabilise.
sparc done
Remaining arches, please go to bug 353436 directly
