when try to create zip archite this is what happen (running on gdb) (gdb) run Starting program: /usr/bin/file-roller [Thread debugging using libthread_db enabled] Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2200.4-gdb.py", line 9, in <module> from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module> import gdb.backtrace ImportError: No module named backtrace [New Thread 0x7fffee79a910 (LWP 6683)] [New Thread 0x7fffedf99910 (LWP 6684)] [Thread 0x7fffedf99910 (LWP 6684) exited] [Thread 0x7fffee79a910 (LWP 6683) exited] [New Thread 0x7fffee79a910 (LWP 6689)] [New Thread 0x7fffedf99910 (LWP 6690)] [Thread 0x7fffee79a910 (LWP 6689) exited] [New Thread 0x7fffee79a910 (LWP 6691)] [Thread 0x7fffee79a910 (LWP 6691) exited] [New Thread 0x7fffee79a910 (LWP 6692)] [Thread 0x7fffedf99910 (LWP 6690) exited] [Thread 0x7fffee79a910 (LWP 6692) exited] [New Thread 0x7fffee79a910 (LWP 6693)] [New Thread 0x7fffedf99910 (LWP 6694)] [New Thread 0x7fffed705910 (LWP 6695)] Program received signal SIGSEGV, Segmentation fault. 0x00007ffff2c73b90 in memmove () from /lib/libc.so.6 Reproducible: Always
Created attachment 225011 [details] emerge --info
Please provide a useful backtrace: http://www.gentoo.org/proj/en/qa/backtraces.xml
I've been experiencing this issue for months, and I finally got annoyed enough to find out what's going on. Some basic Googling found me some bug reports: https://bugs.edge.launchpad.net/ubuntu/+source/file-roller/+bug/399172 which led me to: https://bugzilla.gnome.org/show_bug.cgi?id=589920 This has been fixed in 2.27.x, so 2.28.x naturally has the fix. Upgrading to file-roller 2.28.2 (which thankfully works with currently stable GNOME 2.26) fixes the issue. The patch appears to be the following commit: http://git.gnome.org/browse/file-roller/commit/?id=1e38c5df005ec2d54ac05b3028ab7c56a09ad082 Not sure if you guys want to go anywhere with this patch, or if you just want to focus on getting 2.28 stabilized. (I think there's a good enough workaround while we wait for 2.28, imo.)
Could you provide a understandable backtrace anyway ? Then could you downgrade to file-roller-2.26.3 and apply this patch to confirm if it fixes the problem or not ? Thanks in advance
Fwiw, I will not get around to this for a while, due to school, and since getting back-traces will require an 'emerge -eav =app-arch/file-roller-2.26.3'. This will remain on my todo list, however, so I will not forget.
Created attachment 227641 [details] gdb log file After lots of tears, sweat, and CPU cycles, I've gotten file-roller and its deps compiled with the "debug" USE flag. I've logged all changes made to get to this point, so I'm going to revert them as soon as you say I don't need to debug anything anymore. :P
Created attachment 227643 [details] gdb log file (after patch) Interestingly enough, when I apply the patch at <http://git.gnome.org/browse/file-roller/patch/?id=1e38c5df005ec2d54ac05b3028ab7c56a09ad082> I still get the same error. Another backtrace attached.
Thanks, but I think that will be better to wait a bit for getting 2.28 version stabilized (see bug 314899)
In case you still want to fix this, the two correct patches (which fixed it for me) are: http://git.gnome.org/browse/file-roller/commit/?id=07690b388a856ae495716e972c5f59a3d06c7ecf http://git.gnome.org/browse/file-roller/commit/?id=ac8cd7995fbfc85b0c2f139ff2d264deb7cbd251 They apply cleanly to 2.26.3 in my local ebuild overlay.
(In reply to comment #9) > In case you still want to fix this, the two correct patches (which fixed it for > me) are: > http://git.gnome.org/browse/file-roller/commit/?id=07690b388a856ae495716e972c5f59a3d06c7ecf > http://git.gnome.org/browse/file-roller/commit/?id=ac8cd7995fbfc85b0c2f139ff2d264deb7cbd251 > > They apply cleanly to 2.26.3 in my local ebuild overlay. > Thanks a lot for your investigation
Yes, thanks from me too, I tried to investigate alone, but I failed miserably
I just asked GNOME devs to help me out. I didn't do this on my own: https://bugzilla.gnome.org/show_bug.cgi?id=589920
i confirm this bug!!!
problem seems to be solved in file-roller-2.28.2 (on my amd64 stable system)
Closing this as fixed since it's already solved in testing and that version is already going to stable
