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 426156 - crash in Archive Manager: opening sgd_0.9588.iso I...
crash in Archive Manager: opening sgd_0.9588.iso I...
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-04-04 07:44 UTC by mcella
Modified: 2007-07-15 15:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description mcella 2007-04-04 07:44:54 UTC 
Version: 2.16.1

What were you doing when the application crashed?
opening sgd_0.9588.iso I said extract here



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

Memory status: size: 32337920 vsize: 0 resident: 32337920 share: 0 rss: 9654272 rss_rlim: 0
CPU usage: start_time: 1175672646 rtime: 0 utime: 14 stime: 0 cutime:12 cstime: 0 timeout: 2 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 -1224796496 (LWP 7368)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 124874

Thread 1 (Thread -1224796496 (LWP 7368))

  • #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 strlen
    from /lib/tls/i686/cmov/libc.so.6
  • #5 ??
  • #6 ??
  • #7 ??
  • #0 __kernel_vsyscall 






Comment 1


Paolo Bacchilega





          2007-07-15 15:45:37 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 2.18.0 software version or higher. You may want to check for a software upgrade.

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