Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#12290 - gnome crashes when trying to open an EXE file
Attached to Project:
Arch Linux
Opened by Lior David (liorda) - Sunday, 30 November 2008, 18:03 GMT
Last edited by Jan de Groot (JGC) - Sunday, 30 November 2008, 19:39 GMT
Opened by Lior David (liorda) - Sunday, 30 November 2008, 18:03 GMT
Last edited by Jan de Groot (JGC) - Sunday, 30 November 2008, 19:39 GMT
|
DetailsOn my up-to-date arch gnome desktop, when double-clicking an .EXE file, it opens in file-roller.
File-roller then says it could not find unzip. when closing the unzip-error-msgbox, and then closing the file-roller window, X crashes. Steps to reproduce: 1. download an exe file from the internet (I can reproduce this bug using the latest putty.exe) 2. firefox will save it to the desktop 3. double-click the newly downloaded exe 4. file-roller (the "Archive Manager" titled window) will complain it couldn't find unzip 5. close file-roller 6. X crashes and you'll need to relogin in the GDM screen |
This task depends upon
Closed by Jan de Groot (JGC)
Sunday, 30 November 2008, 19:39 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 2.24.2-2.
Sunday, 30 November 2008, 19:39 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 2.24.2-2.
http://bugzilla.gnome.org/show_bug.cgi?id=503240
I'm building a patched file-roller that will only kill processes if their PID is not set to 0. When file-roller can't launch a process, the PID is set to the initial value of 0. Feeding this PID to kill, kill sends SIGTERM to every process in the same process group, which includes gnome-session and all your applications. When running file-roller from a terminal, the killing spree stops at your shell because it ignores SIGTERM.