GNOME Bugzilla – Bug 306862
file-roller crashes when beginning a drag'n drop
Last modified: 2005-06-11 16:19:36 UTC
Distribution: Debian 3.1 Package: file-roller Severity: normal Version: 2.8.4 Synopsis: file-roller crashes when beginning a drag'n drop Bugzilla-Product: file-roller Bugzilla-Component: general Bugzilla-Version: 2.8.4 BugBuddy-GnomeVersion: 2.0 (2.8.1) Description: Description of the crash: After opening a zip file, I clicked on a file in the archive to drag it elsewhere, but after the drag icon appeared and before I could even leave the file-roller window, this crash occured Steps to reproduce the crash: 1. open a given zip file (.tgz or other .zip aren't affected) 2. try to drag the first file Expected Results: I should have been able to drop the file onto another application (rox on xfce in my case) How often does this happen? always with this zip, never with others (tested 1 zip and 1 tgz) Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/file-roller' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 19858)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x40abbbe8 in waitpid () from /lib/libpthread.so.0
+ Trace 60696
Thread 1 (Thread 16384 (LWP 19858))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-06-08 10:33 UTC ------- Unknown version 2.8.4 in product file-roller. Setting version to "2.8.x".
I reproduced this crash when trying to extract this zip. When moving it to /tmp, I can then do anything I want. It appears that the path in which I had the .zip located wasn't UTF-8 compliant. I guess it is linked to this crash, hence it may not be file-roller specific but linked to vfs or whetever the name of the underlying filesystem unified lib.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 164894 ***