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 399551 - crash in Archive Manager: pulling tikiwiki files o...
crash in Archive Manager: pulling tikiwiki files o...
Status: RESOLVED DUPLICATE of bug 373231
Product: file-roller
Classification: Applications
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
file-roller-maint
: 393940 401659 411992 445009 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-01-22 21:20 UTC by cs155503
Modified: 2007-06-07 22:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description cs155503 2007-01-22 21:20:34 UTC
Version: 2.16.0

What were you doing when the application crashed?
pulling tikiwiki files onto the desktop 


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

System: Linux 2.6.19-1.2895.fc6 #1 SMP Wed Jan 10 19:28:18 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled
----------- .xsession-errors (111 sec old) ---------------------
(nautilus:2587): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:2587): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:2587): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:2587): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:2587): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:2587): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:2587): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:2587): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
--------------------------------------------------

Memory status: size: 107622400 vsize: 0 resident: 107622400 share: 0 rss: 16826368 rss_rlim: 0
CPU usage: start_time: 1169499933 rtime: 0 utime: 1619 stime: 0 cutime:1257 cstime: 0 timeout: 362 it_real_value: 0 frequency: 2199

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 -1208400176 (LWP 2815)]
(no debugging symbols found)
0x009c9402 in __kernel_vsyscall ()

Thread 1 (Thread -1208400176 (LWP 2815))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gtk_drag_dest_unset
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 gtk_drag_set_icon_pixmap
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 g_source_is_destroyed
    from /lib/libglib-2.0.so.0
  • #7 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #8 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #9 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #10 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 g_cclosure_marshal_VOID__BOOLEAN
  • #12 __libc_start_main
    from /lib/libc.so.6
  • #13 g_cclosure_marshal_VOID__BOOLEAN
  • #0 __kernel_vsyscall

Comment 1 Mariano Suárez-Alvarez 2007-01-23 08:59:33 UTC
This is a dup of 373231, but that got closed as INCOMPLETE. 

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 Susana 2007-01-28 13:45:11 UTC
*** Bug 401659 has been marked as a duplicate of this bug. ***
Comment 3 palfrey 2007-02-04 21:02:45 UTC
*** Bug 393940 has been marked as a duplicate of this bug. ***
Comment 4 André Klapper 2007-02-24 14:51:16 UTC
Dear reporters,
could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here.

Thanks in advance for helping to get this fixed!

[1] Please install debug packages for glib2 and gtk2.
  Ubuntu 6.10: libglib2.0-0-dbg, libgtk2.0-0-dbg
  Fedora Core 6 or OpenSuSE 10.2: glib2-debuginfo, gtk2-debuginfo

More details can be found here: http://live.gnome.org/GettingTraces
Comment 5 Susana 2007-02-26 18:07:17 UTC
*** Bug 411992 has been marked as a duplicate of this bug. ***
Comment 6 André Klapper 2007-04-01 14:33:25 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 373231 ***
Comment 7 Susana 2007-06-07 22:20:06 UTC
*** Bug 445009 has been marked as a duplicate of this bug. ***