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 328677 - file roller crashes in the middle of opening an archive.
file roller crashes in the middle of opening an archive.
Status: RESOLVED DUPLICATE of bug 328331
Product: file-roller
Classification: Applications
Component: general
2.13.x
Other Linux
: Normal critical
: ---
Assigned To: Paolo Bacchilega
file-roller-maint
Depends on:
Blocks:
 
 
Reported: 2006-01-26 03:17 UTC by Brent Smith (smitten)
Modified: 2006-01-27 20:35 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Brent Smith (smitten) 2006-01-26 03:17:04 UTC
Archive was created with file-roller from 2.12, but extracted using 2.13.4

Here's the stack trace.

Backtrace was generated from '/opt/gnome2/bin/file-roller'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1227217216 (LWP 8859)]
[New Thread -1230427216 (LWP 8862)]
0xffffe410 in __kernel_vsyscall ()
  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 792
  • #3 <signal handler called>
  • #4 dir_contains_one_object
    at file-utils.c line 140
  • #5 extract__content_is_singleton
    at window.c line 4680
  • #6 check_child
    at fr-process.c line 765
  • #7 g_timeout_dispatch
    at gmain.c line 3292
  • #8 g_main_dispatch
    at gmain.c line 1916
  • #9 IA__g_main_context_dispatch
    at gmain.c line 2466
  • #10 g_main_context_iterate
    at gmain.c line 2547
  • #11 IA__g_main_loop_run
    at gmain.c line 2751
  • #12 IA__gtk_main
    at gtkmain.c line 991
  • #13 main
    at main.c line 220

Comment 1 Christian Kirbach 2006-01-26 19:01:39 UTC
path=0x0 looks suspicious

if you can reproduce, I guess you need to look up the locals in frame 5
Comment 2 Frank Arnold 2006-01-27 16:22:48 UTC
Duplicate of bug 328331. Already fixed in CVS.
Comment 3 Christian Kirbach 2006-01-27 20:35:22 UTC
looks like

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