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 456243 - crash in Open Folder: I believe I was hovering...
crash in Open Folder: I believe I was hovering...
Status: RESOLVED DUPLICATE of bug 429586
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-12 13:47 UTC by haig-web
Modified: 2007-09-11 13:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description haig-web 2007-07-12 13:47:11 UTC
Version: 2.18.3

What were you doing when the application crashed?
I believe I was hovering over my home folder on the desktop when it crashed.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 150953984 vsize: 150953984 resident: 68898816 share: 35823616 rss: 68898816 rss_rlim: 4294967295
CPU usage: start_time: 1184246654 rtime: 3327 utime: 2956 stime: 371 cutime:0 cstime: 1 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 -1209014560 (LWP 2735)]
0x00b64402 in __kernel_vsyscall ()

Thread 1 (Thread -1209014560 (LWP 2735))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 g_cclosure_marshal_VOID__ENUM
    at gmarshal.c line 334
  • #3 <signal handler called>
  • #4 ??
  • #5 IA__gtk_action_connect_proxy
    at gtkaction.c line 967
  • #6 update_node
    at gtkuimanager.c line 2444
  • #7 update_node
    at gtkuimanager.c line 2599
  • #8 update_node
    at gtkuimanager.c line 2599
  • #9 update_node
    at gtkuimanager.c line 2599
  • #10 update_node
    at gtkuimanager.c line 2599
  • #11 do_updates
    at gtkuimanager.c line 2641
  • #12 do_updates_idle
    at gtkuimanager.c line 2652
  • #13 g_idle_dispatch
    at gmain.c line 3928
  • #14 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #15 g_main_context_iterate
    at gmain.c line 2677
  • #16 IA__g_main_loop_run
    at gmain.c line 2881
  • #17 IA__gtk_main
    at gtkmain.c line 1154
  • #18 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (15 sec old) ---------------------
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
INFO:flickrest:Calling flickr.people.getUploadStatus
INFO:flickrest:Calling flickr.photosets.getList
INFO:flickrest:flickr.people.getUploadStatus returned
INFO:flickrest:flickr.photosets.getList returned
sys:1: GtkWarning: You must override the default 'drag_data_delete' handler on GtkTreeView when using models that don't support the GtkTreeDragSource interface and enabling drag-and-drop. The simplest
INFO:flickrest:Calling upload
INFO:flickrest:upload returned
INFO:flickrest:Calling upload
INFO:flickrest:upload returned
INFO:flickrest:Calling flickr.people.getUploadStatus
INFO:flickrest:flickr.people.getUploadStatus returned
sys:1: Warning: IA__g_object_weak_unref: couldn't find weak ref 0x4da39090(0x9146cd8)
sys:1: Warning: instance of invalid non-instantiatable type `(null)'
sys:1: Warning: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
--------------------------------------------------
Comment 1 André Klapper 2007-09-11 13:39:40 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 429586 ***