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 358412 - crash in Archive Manager: Opening a mail attachmen...
crash in Archive Manager: Opening a mail attachmen...
Status: RESOLVED DUPLICATE of bug 358405
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-09-30 02:10 UTC by charlesr.harris
Modified: 2006-09-30 08:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description charlesr.harris 2006-09-30 02:10:23 UTC 
Version: 2.16.0

What were you doing when the application crashed?
Opening a mail attachment in a gmail account.


Distribution: Fedora Core release 5.92 (FC6 Test3)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 179838976 vsize: 0 resident: 179838976 share: 0 rss: 14483456 rss_rlim: 0
CPU usage: start_time: 1159582093 rtime: 0 utime: 33 stime: 0 cutime:26 cstime: 0 timeout: 7 it_real_value: 0 frequency: 0

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)
[Thread debugging using libthread_db enabled]
[New Thread -1208924464 (LWP 19296)]
(no debugging symbols found)
0xb7f3f402 in __kernel_vsyscall ()

+ Trace 73639

Thread 1 (Thread -1208924464 (LWP 19296))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 ??
  • #5 ??
  • #0 __kernel_vsyscall 






Comment 1


Karsten Bräckelmann





          2006-09-30 02:51:01 UTC
        



Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.







Comment 2


charlesr.harris





          2006-09-30 05:03:54 UTC
        



Here is a more complete stack trace. If you need more I can install more debuginfo, the error is quite repeatable. It happens when I hit the extract button in file-roller and has persisted for quite a while. Makes me wonder about the gtk_file_chooser_button_new () entry below...Chuck

Distribution: Fedora Core release 5.92 (FC6 Test3)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 179826688 vsize: 0 resident: 179826688 share: 0 rss: 15548416 rss_rlim: 0
CPU usage: start_time: 1159591748 rtime: 0 utime: 39 stime: 0 cutime:30 cstime: 0 timeout: 9 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/file-roller'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208310064 (LWP 21202)]
0xb7fd5402 in __kernel_vsyscall ()




+
Trace
    73653






Thread 1
          (Thread -1208310064 (LWP 21202))


    

  • 
#0
__kernel_vsyscall

    • 

  • 
#1
__waitpid_nocancel

    
                from
                /lib/libpthread.so.0

    

    • 

  • 
#2
libgnomeui_segv_handle

    
                at gnome-ui-init.c
                  line
                  870

    

    • 

  • 
#3
<signal handler called>

    • 

  • 
#4
strcmp

    
                from
                /lib/libc.so.6

    

    • 

  • 
#5
gtk_file_chooser_button_new

    
                from
                /usr/lib/libgtk-x11-2.0.so.0

    

    • 

  • 
#6
??

    • 

  • 
#0
__kernel_vsyscall

    • 













Comment 3


André Klapper





          2006-09-30 08:42:27 UTC
        



charles, thanks a lot for the new stacktrace. this looks like a duplicate of bug 358405.

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