GNOME Bugzilla – Bug 647586
Crash on start in egg_tree_multi_drag_button_release_event()
Last modified: 2020-11-11 19:14:51 UTC
As reported on Launchpad (https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/723841), file-roller in Ubuntu crashes when opening some archives, but not others. Originally, I had suspected that the problem was specific to .7z archives, and that suspicions is reflected in the original bug report, but subsequent duplicate bug reports have shown that this is not the case--the crash occurs with multiple archive types, but does not always occur with any particular archive type, at least not on all systems. Please see the original bug report and its stack trace for details.
This has been reported to happen with file-roller 2.32.0-0ubuntu1 on Ubuntu 10.10 Maverick (this is the version for the original, linked-to bug report), file-roller 2.32.1-0ubuntu3 and 2.32.1-0ubuntu4 on Ubuntu 11.04 Natty, and possibly also with file-roller 188.8.131.52-0ubuntu2 on Ubuntu 10.04 Lucid. Thus far, no one has reported this crash occurring on the i386 architecture--only on amd64.
This bug's stack trace somewhat resembles the trace in https://bugzilla.gnome.org/show_bug.cgi?id=614499, so perhaps these bugs are related and/or this bug reflects a problem in GTK+ itself.
Pasting stacktrace from downstream bug
*** Bug 655808 has been marked as a duplicate of this bug. ***
*** Bug 657868 has been marked as a duplicate of this bug. ***
That's still an issue in GNOME 3.4 and quite a frequent one, the ubuntu bugs has 21 duplicates
the stacktrace doesn't help very much
has Sebastien Bacher on 2012-04-10 attached a new stacktrace for fileroller 3.4.0.
I attach this here. It shows the starting point of the crash instaed of ??.
This crash is also observed on file-roller3.6.3 in Ubuntu13.04 developer branch. Unfortunately to this date there is no stacktrace available for this version, but the crasher is identified by apport as the same.
I also attach the ThreadStacktrace.txt
(Thread 0xb67bf840 (LWP 5044))
So, with the new stacktrace it is
file-roller crashed with SIGSEGV in egg_tree_multi_drag_button_release_event()
The crash occures the first time in file-roller 2.32.0 and is observable through the version history up to the actual file-roller 3.6.3
*** Bug 725379 has been marked as a duplicate of this bug. ***
Confirmed on Fedora for 3.4, 3.6, 3.8 and 3.10. See Bug 725379 for another stacktrace and links to duplicate reports.
I think the cause may be that the user double clicks on a directory in the
archive too fast on start. I experienced the crash a few times when my system
was under memory pressure and file-roller was a little slow to start. Just a
All crashes are severity -> critical
(In reply to comment #13)
> Confirmed on Fedora for 3.4, 3.6, 3.8 and 3.10. See Bug 725379 for another
> stacktrace and links to duplicate reports.
> I think the cause may be that the user double clicks on a directory in the
> archive too fast on start. I experienced the crash a few times when my system
> was under memory pressure and file-roller was a little slow to start. Just a
Yes, it definitely seems to happen more often if you double-click on a directory just after it starts.
*** Bug 773027 has been marked as a duplicate of this bug. ***
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time.
If you still use file-roller and if you still see this bug / want this feature in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/file-roller/-/issues/
Thank you for creating this report and we are sorry it could not be implemented (volunteer workforce and time is limited).