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 416404 - crash in Archive Manager: try to extract mandriva-...
crash in Archive Manager: try to extract mandriva-...
Status: RESOLVED DUPLICATE of bug 376848
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: 2007-03-09 11:32 UTC by Norbert Sebők
Modified: 2007-03-09 12:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Norbert Sebők 2007-03-09 11:32:58 UTC 
Version: 2.16.1

What were you doing when the application crashed?
try to extract mandriva-one-2007.0-metisse.i586.iso
with Nautilus, 'extract here'


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

Memory status: size: 49524736 vsize: 0 resident: 49524736 share: 0 rss: 10629120 rss_rlim: 0
CPU usage: start_time: 1173439889 rtime: 0 utime: 29 stime: 0 cutime:24 cstime: 0 timeout: 5 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 -1225042256 (LWP 5199)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 117153

Thread 1 (Thread -1225042256 (LWP 5199))

  • #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_main_context_find_source_by_id
    from /usr/lib/libglib-2.0.so.0
  • #5 g_source_remove
    from /usr/lib/libglib-2.0.so.0
  • #6 ??
  • #7 ??
  • #8 _IO_stdin_used
  • #9 ??
  • #0 __kernel_vsyscall 






Comment 1


Susana





          2007-03-09 12:10:44 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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