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 506363 - crash in Open Folder: I was attempting to look...
crash in Open Folder: I was attempting to look...
Status: RESOLVED DUPLICATE of bug 494487
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-12-30 03:44 UTC by 85dbm
Modified: 2007-12-30 11:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description 85dbm 2007-12-30 03:44:31 UTC
Version: 2.18.3

What were you doing when the application crashed?
I was attempting to look at the properties of a folder.  I simply did a right click and selected properties, at that time this bug report popup activated.  The folder "driver" from the ndiswrapper 1.51 download, was what I was working on.


Distribution: Debian lenny/sid
Gnome Release: 2.20.2 2007-11-29 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-amd64 #1 SMP Sun Nov 4 18:18:09 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 395780096 vsize: 395780096 resident: 29057024 share: 16666624 rss: 29057024 rss_rlim: 18446744073709551615
CPU usage: start_time: 1198983716 rtime: 1087 utime: 1004 stime: 83 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

(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 0x2b38bb2f4540 (LWP 3536)]
(no debugging symbols found)
0x00002b38b487a34f in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x2b38bb2f4540 (LWP 3536))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 ??
  • #6 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #7 ??
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #10 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #12 ??
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #15 gtk_list_store_remove
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gtk_list_store_clear
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 ??
  • #18 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #19 ??
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #22 nautilus_file_emit_changed
  • #23 nautilus_directory_emit_change_signals
  • #24 nautilus_file_changed
  • #25 ??
  • #26 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #27 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #28 ??
    from /usr/lib/libglib-2.0.so.0
  • #29 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #30 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 main
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
(nautilus:3536): GLib-CRITICAL **: g_strsplit: assertion `string != NULL' failed
--------------------------------------------------
Comment 1 Cosimo Cecchi 2007-12-30 11:30:35 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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