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 512644 - crash in Open Folder: New Nautilus 2.21.6 afte...
crash in Open Folder: New Nautilus 2.21.6 afte...
Status: RESOLVED DUPLICATE of bug 512040
Product: nautilus
Classification: Core
Component: general
2.21.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-28 20:17 UTC by nemes.sorin
Modified: 2008-01-29 00:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description nemes.sorin 2008-01-28 20:17:12 UTC
Version: 2.21.6

What were you doing when the application crashed?
New Nautilus 2.21.6 after upgrade broke all my desktop customisations (icon sizes, custom icons, etc) as I see there is a patch for that. Until then he like to frequently crash - from vary reasons. This time I want to open a .desktop file (I need to create Aplication launchers for some old links to work - on this new situation). SO I wanna open /opt/lampp/htdocs with one Application launcher with this command : nautilus /opt/lampp/htdocs - that works until now when Nautilus crash. I hope you can use this report for something.


Distribution: Ubuntu 8.04 (hardy)
Gnome Release: 2.21.5 2008-01-15 (Ubuntu)
BugBuddy Version: 2.20.1

System: Linux 2.6.24-5-generic #1 SMP Thu Jan 24 19:45:21 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Aurora-looks
Icon Theme: nuoveXT.2.2

Memory status: size: 171360256 vsize: 171360256 resident: 83697664 share: 29192192 rss: 83697664 rss_rlim: 4294967295
CPU usage: start_time: 1201548628 rtime: 4796 utime: 3759 stime: 1037 cutime:0 cstime: 0 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/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b466c0 (LWP 5853)]
[New Thread 0xb3787b90 (LWP 10313)]
(no debugging symbols found)
0xb7fe3410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6b466c0 (LWP 5853))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 __kernel_vsyscall
  • #7 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #8 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #9 g_assertion_message
    from /usr/lib/libglib-2.0.so.0
  • #10 g_assertion_message_expr
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
  • #12 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
Error: eval: unbound variable: <!DOCTYPE 
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00003 (Export Fil)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00003 (Export Fil)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
(synaptic:6032): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
(synaptic:6032): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed
(synaptic:6032): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed
**
** ERROR:(fm-tree-model.c:1563):fm_tree_model_unref_node: assertion failed: (parent->dummy_child_ref_count > 0)
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-29 00:27:28 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 512040 ***