GNOME Bugzilla – Bug 357188
extract files to fonts:/// burn:/// etc.
Last modified: 2007-10-29 22:44:42 UTC
Version: 2.16.0 What were you doing when the application crashed? Just for your info, since I don't use the english locale, I can only try to translate my labels/entries. Hopefully it's understandable, though. 1.) open archive containing fonts 2.) press extract 3.) in combo box "extract to folder" choose "other" 4.) in the location edit field enter "fonts:///" 5.) press enter 6.) you're now back in file-roller's extract dialog - press enter and appreciate the crash... Unfortunately there's no debug package for file-roller, so I won't provide a stacktrace with debug-symbols. But the bug should be reproducable for you - at least I can do so every time. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 83001344 vsize: 0 resident: 83001344 share: 0 rss: 18751488 rss_rlim: 0 CPU usage: start_time: 1158929008 rtime: 0 utime: 140 stime: 0 cutime:126 cstime: 0 timeout: 14 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/file-roller' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1224972624 (LWP 12218)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 72987
Thread 1 (Thread -1224972624 (LWP 12218))
*** Bug 361505 has been marked as a duplicate of this bug. ***
*** Bug 362822 has been marked as a duplicate of this bug. ***
Commonality between these three duplicates: In all three cases the user is trying to extract to a 'special' location. font://, burncd:// or smb://
*** Bug 366366 has been marked as a duplicate of this bug. ***
*** Bug 366580 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
*** Bug 367332 has been marked as a duplicate of this bug. ***
*** Bug 374334 has been marked as a duplicate of this bug. ***
*** Bug 376880 has been marked as a duplicate of this bug. ***
Hi, I followed the description given by the reporter and got this stacktrace: Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 83988480 vsize: 0 resident: 83988480 share: 0 rss: 17174528 rss_rlim: 0 CPU usage: start_time: 1164232202 rtime: 0 utime: 108 stime: 0 cutime:104 cstime: 0 timeout: 4 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/file-roller' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1224833360 (LWP 9917)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 88611
Thread 1 (Thread -1224833360 (LWP 9917))
*** Bug 378113 has been marked as a duplicate of this bug. ***
confirming as per duplicates. nice trace, susana, thanks! :-)
*** Bug 378867 has been marked as a duplicate of this bug. ***
*** Bug 379901 has been marked as a duplicate of this bug. ***
*** Bug 380363 has been marked as a duplicate of this bug. ***
*** Bug 383563 has been marked as a duplicate of this bug. ***
*** Bug 390709 has been marked as a duplicate of this bug. ***
*** Bug 390909 has been marked as a duplicate of this bug. ***
*** Bug 392443 has been marked as a duplicate of this bug. ***
*** Bug 392044 has been marked as a duplicate of this bug. ***
*** Bug 397081 has been marked as a duplicate of this bug. ***
*** Bug 397741 has been marked as a duplicate of this bug. ***
*** Bug 393967 has been marked as a duplicate of this bug. ***
*** Bug 398480 has been marked as a duplicate of this bug. ***
*** Bug 398879 has been marked as a duplicate of this bug. ***
*** Bug 400965 has been marked as a duplicate of this bug. ***
*** Bug 401086 has been marked as a duplicate of this bug. ***
*** Bug 402155 has been marked as a duplicate of this bug. ***
*** Bug 402705 has been marked as a duplicate of this bug. ***
*** Bug 403289 has been marked as a duplicate of this bug. ***
*** Bug 400444 has been marked as a duplicate of this bug. ***
*** Bug 403269 has been marked as a duplicate of this bug. ***
*** Bug 404049 has been marked as a duplicate of this bug. ***
*** Bug 404296 has been marked as a duplicate of this bug. ***
*** Bug 404777 has been marked as a duplicate of this bug. ***
*** Bug 406869 has been marked as a duplicate of this bug. ***
*** Bug 407067 has been marked as a duplicate of this bug. ***
*** Bug 410532 has been marked as a duplicate of this bug. ***
*** Bug 411753 has been marked as a duplicate of this bug. ***
*** Bug 412631 has been marked as a duplicate of this bug. ***
*** Bug 398594 has been marked as a duplicate of this bug. ***
*** Bug 413874 has been marked as a duplicate of this bug. ***
*** Bug 416956 has been marked as a duplicate of this bug. ***
*** Bug 417269 has been marked as a duplicate of this bug. ***
*** Bug 420714 has been marked as a duplicate of this bug. ***
*** Bug 422749 has been marked as a duplicate of this bug. ***
*** Bug 423642 has been marked as a duplicate of this bug. ***
*** Bug 424785 has been marked as a duplicate of this bug. ***
*** Bug 423913 has been marked as a duplicate of this bug. ***
*** Bug 424919 has been marked as a duplicate of this bug. ***
*** Bug 426836 has been marked as a duplicate of this bug. ***
*** Bug 432744 has been marked as a duplicate of this bug. ***
*** Bug 436019 has been marked as a duplicate of this bug. ***
*** Bug 443050 has been marked as a duplicate of this bug. ***
*** Bug 450433 has been marked as a duplicate of this bug. ***
last duplicate is 2.18
*** Bug 452036 has been marked as a duplicate of this bug. ***
totally reproducible in 2.18. I've tried to reproduce it with file-roller from trunk and everything is working good, so probably this was already fixed. Can someone try to reproduce it with trunk too and confirm?, thanks.
gtk_file_chooser_get_uri (GTK_FILE_CHOOSER (data->dialog)) returned NULL when a special location like burn:/// was selected in the filechooser. Pedro, was this a gtk+ bug ?? Later g_filename_display_name (extract_to_dir) fails. I can reproduce the crash with 2.18 but a fairly recent svn build does not crash. since the file-roller code does not look like it was changed i guess some changes in gtk+ and/or glib fixed the crash. => I believe it has been fixed
Yes, agreed this is probably a gtk+/glib bug, marking it as fixed for now. If someone can reproduce this bug in 2.19.X or later, please re open the bug. Dear reporters the problem has been fixed in the development version. The fix will be available in the next major software release. Thanks.
Created attachment 90987 [details] [review] workaround for file-roller 2.18 this is a simple workaround I came up with, not needed for current development version other solution is to apply the appropriate gtk+/glib fix to the error that caused file-roller to crash
*** Bug 474153 has been marked as a duplicate of this bug. ***
*** Bug 483119 has been marked as a duplicate of this bug. ***