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 374541 - crash in Computer:
crash in Computer:
Status: RESOLVED DUPLICATE of bug 373873
Product: nautilus
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-13 02:17 UTC by gsullivan1
Modified: 2006-11-14 10:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description gsullivan1 2006-11-13 02:17:20 UTC
Version: 2.16.2

What were you doing when the application crashed?



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.18-1.2849.fc6 #1 SMP Fri Nov 10 12:34:46 EST 2006 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled
----------- .xsession-errors ---------------------
Reading configuration from /home/Glenn/.tvtime/tvtime.xml
Loading "installonlyn" plugin
** Message: sqlite cache needs updating, reading in metadata
(gnome-power-preferences:467): Gtk-CRITICAL **: gtk_range_set_range: assertion `min < max' failed
(gnome-power-preferences:467): Gtk-CRITICAL **: gtk_range_set_range: assertion `min < max' failed
(gnome-power-preferences:467): Gtk-CRITICAL **: gtk_range_set_range: assertion `min < max' failed
(gnome-power-preferences:467): Gtk-CRITICAL **: gtk_range_set_range: assertion `min < max' failed
** (nautilus:29832): CRITICAL **: nautilus_directory_ref: assertion `NAUTILUS_IS_DIRECTORY (directory)' failed
** (bug-buddy:478): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------

Memory status: size: 517988352 vsize: 517988352 resident: 32522240 share: 13172736 rss: 32522240 rss_rlim: -1
CPU usage: start_time: 1163371924 rtime: 852 utime: 803 stime: 49 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496416736 (LWP 29832)]
(no debugging symbols found)
0x000000378e00d96f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496416736 (LWP 29832))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 nautilus_clipboard_monitor_emit_changed
  • #4 nautilus_clipboard_monitor_emit_changed
  • #5 nautilus_clipboard_monitor_emit_changed
  • #6 nautilus_directory_async_state_changed
  • #7 nautilus_directory_async_state_changed
  • #8 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #9 g_main_context_check
    from /lib64/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #12 POA_Nautilus_MetafileMonitor__init
  • #13 __libc_start_main
    from /lib64/libc.so.6
  • #14 g_cclosure_marshal_VOID__ENUM
  • #15 ??
  • #16 ??
  • #0 waitpid
    from /lib64/libpthread.so.0

Comment 1 Karsten Bräckelmann 2006-11-14 10:40:52 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 373873 ***