After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 362822 - crash in Archive Manager: Trying to extract files ...
crash in Archive Manager: Trying to extract files ...
Status: RESOLVED DUPLICATE of bug 357188
Product: file-roller
Classification: Applications
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
file-roller-maint
Depends on:
Blocks:
 
 
Reported: 2006-10-17 10:34 UTC by Laudeci Oliveira
Modified: 2006-10-17 20:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Laudeci Oliveira 2006-10-17 10:34:39 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Trying to extract files from a zip file


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 84074496 vsize: 0 resident: 84074496 share: 0 rss: 17715200 rss_rlim: 0
CPU usage: start_time: 1161081342 rtime: 0 utime: 94 stime: 0 cutime:88 cstime: 0 timeout: 6 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 -1225079120 (LWP 28670)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 76766

Thread 1 (Thread -1225079120 (LWP 28670))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_utf8_validate
    from /usr/lib/libglib-2.0.so.0
  • #5 g_filename_display_name
    from /usr/lib/libglib-2.0.so.0
  • #6 ??
  • #7 ??
  • #0 __kernel_vsyscall 






Comment 1


André Klapper





          2006-10-17 10:36:19 UTC
        



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!







Comment 2


Laudeci Oliveira





          2006-10-17 14:04:38 UTC
        



The problem was caused when i tried to extract files from a zip file to burncd folder. 

I cant remember URI this moment, but it looks like burncd://

Hope that helps!

Regards,

Laudeci Oliveira






Comment 3


Rob Bradford





          2006-10-17 20:52:09 UTC
        




*** This bug has been marked as a duplicate of 357188 ***






Comment 4


Rob Bradford





          2006-10-17 20:53:57 UTC
        



This is a duplicate of 357188 since in all three cases the user is trying to extract to a 'special' location. font://, burncd:// or smb://