abrt version: 1.1.14 architecture: i686 Attached file: backtrace cmdline: file-roller /home/srlunar/la_venta.tar component: file-roller crash_function: egg_tree_multi_drag_button_release_event executable: /usr/bin/file-roller kernel: 2.6.35.6-48.fc14.i686 package: file-roller-2.32.0-2.fc14 rating: 4 reason: Process /usr/bin/file-roller was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1290611715 uid: 500 How to reproduce ----- 1.Eliminar un archivo contenido en un .tar.gz 2. 3.
Created attachment 462712 [details] File: backtrace
Package: file-roller-2.32.0-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Navigate trough http://software.internet2.edu/sources/ndt/ndt-3.6.4.tar.gz 2. 3.
Package: file-roller-2.32.0-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Clicked on a folder in a zip file to open it 2. 3.
Package: file-roller-2.32.0-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Tried to peek into the 7-zip file that I downloaded via Chromium in file-roller; it prompted me to download the 7-zip archive tool 2. After installing the 7-zip archive tool via the yum-my GUI, file-roller showed me the subdirectory that the archive contained 3. Double-clicked on the subdirectory to view the 40,000 files / 4,000 directories that it apparently contains - crash Comment ----- Running "7za x content_archive.7z" works fine from the command line, so I'm guessing there's a limit to how many files file-roller can handle in a single archive.
Package: file-roller-2.32.0-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.sorry! 2.I don't know! 3.
Package: file-roller-2.32.0-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. i try to open .7z
Package: file-roller-2.32.0-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. .
Package: file-roller-2.32.0-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Open password protected RAR file 2. Enter folder in RAR file 3.
Package: file-roller-2.32.0-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. just opened an zipped attachement from Lotus Notes
Package: file-roller-2.32.0-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Every day I do the yum update my system 2. I download the wine-qq from code.google.com 3. Open the tar source code and go on the directory 4. it's exit automatic (Express the tar code and totalling 47.9 MB )
Package: file-roller-2.32.0-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. open arhive SugarCE-6.1.1.zim from https://www.sugarcrm.com/crm/
Package: file-roller-2.32.0-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Open an archive file named usb-modeswitch-data-20101222.tar.bz2 2.Open the only folder in the archive file 3. It crashed once, yet I cannot repeat it
Package: file-roller-2.32.0-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Download wxWidgets-docs-html-2.9.1.tar.bz2 file from wxwidgets.org site 2.Double click file. 3.Double click wxWidgets-2.9.1 folder and it crashed. Comment ----- This bug is not reproducible everytime. I had no other archive file open.
Package: file-roller-2.32.0-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I click the file to open. 2. 3.
Package: file-roller-2.32.0-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I was opening a subdirectory of a tar.gz file. 2. 3.
Package: file-roller-2.32.0-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Download http://caesar.acc.umu.se/pub/GNOME/sources/gtk+/3.0/gtk+-3.0.0.tar.bz2 2.Open file in Nautilus 3. Crash.
Package: file-roller-2.32.0-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Download http://www.portaudio.com/archives/pa_snapshot.tgz 2. Double-click to open the file.
Package: file-roller-2.32.0-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Clicked on a gzip file from nautilus 2. 3.
Package: file-roller-2.32.0-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Try to open folder...
Package: file-roller-2.32.0-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Opened a tgz-archive with file roller 2. Double clicked on folder inside the archive Comment ----- I am not able to reproduce the problem. The archive was on an external usb device, with ext3 file system.
Package: file-roller-2.32.0-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Opened a zip file 2. 3.
Package: file-roller-2.32.0-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Open an rar file 2.Double-click on a folder and it crashed 3.
My observation is : The compressed file (zip, gz etc.) has a folder with huge number of files and overall zip/gz is also big. Then, after opening the window, if I immediately click on the folder inside of zip/gz before it actually loads all files, it crashes.
Package: file-roller-2.32.0-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.. 2. 3.
Package: file-roller-2.32.0-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Open a large archive file 2. Try to open folders inside it
Package: file-roller-2.32.0-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Browsing a .zip file 2. 3.
Package: file-roller-2.32.0-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. opened tar.gz file 2. 3.
Package: file-roller-2.32.0-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Open file firefox-4.0.tar.bz2 2.Try to open root folder. 3. Crash!!!
Package: file-roller-2.32.0-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Open 7zip archive
Package: file-roller-2.32.0-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Double clicked on a zip file 2. 3.
Package: file-roller-2.32.0-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 打开一个压缩文件里面的目录 2. 3. Comment ----- （奇怪的是，我重新试了一下又好了）
Package: file-roller-2.32.0-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Open .tar.gz file on Desktop 2. 3. Comment ----- Open .tar.gz file on Desktop
Package: file-roller-2.32.0-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Downloaded tar.gz file 2. Double-clicked in nautilus to open with file-roller 3. file-roller opened briefly, before crashing. Comment ----- Simply tried to open an archive.
*** Bug 675384 has been marked as a duplicate of this bug. ***
*** Bug 645589 has been marked as a duplicate of this bug. ***
*** Bug 703619 has been marked as a duplicate of this bug. ***
Backtrace analysis of bugs across components suggests the actual bug is in component gtk2 instead of component file-roller, reassigning to gtk2. Bugs which were found to be similar to this bug: claws-mail: bug #748384 epiphany: bug #629771, bug #655585, bug #704361 evolution: bug #600838, bug #617151, bug #620849, bug #634101, bug #641235 file-roller: bug #526579, bug #538311, bug #539338, bug #542425, bug #546908, bug #554083, bug #561279, bug #586520, bug #586524, bug #592594, bug #598337, bug #609805, bug #622722, bug #628055, bug #629690, bug #645589, bug #650730, bug #673031, bug #675384, bug #677573, bug #680400, bug #703619 grig: bug #611947 kazehakase: bug #723101 nautilus: bug #602601 pcmanfm: bug #597392 pidgin: bug #613962, bug #616789, bug #714022 tangogps: bug #690049 wireshark: bug #559152 xournal: bug #665762 This comment is automatically generated.
*** Bug 723101 has been marked as a duplicate of this bug. ***
*** Bug 704361 has been marked as a duplicate of this bug. ***
*** Bug 714022 has been marked as a duplicate of this bug. ***
*** Bug 690049 has been marked as a duplicate of this bug. ***
*** Bug 665762 has been marked as a duplicate of this bug. ***
The same error is thrown on Redhat Enterprise 6.2 (perhaps EL6.1 also) file-roller-2.28.2-6.el6.x86_64.rpm "/usr/bin/file-roller was killed by signal 11 (SIGSEGV)" This bug occurs when opening a (large) zip file for the first time. When opening the zip file immediately afterwards the bug is not triggered. This should be marked as medium-high priority.
NB xulrunner 10.0.3 -> 10.0.5 may be throwing the same error. "/usr/lib64/xulrunner-2/plugin-container was killed by signal 11 (SIGSEGV)" These crashes seems to be occuring on EL6.2 only, and since approximately 10 April 2012. (gnome-applets/drivemount_applet2 might also be affected).
Confirm crash still occuring on EL6.3 (same error message)
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping