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 499746 - crash in Open Folder:
crash in Open Folder:
Status: RESOLVED DUPLICATE of bug 465786
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-26 14:38 UTC by avsharyan
Modified: 2007-11-26 20:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description avsharyan 2007-11-26 14:38:27 UTC 
Version: 2.18.3

What were you doing when the application crashed?



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

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 102371328 vsize: 102371328 resident: 37367808 share: 18575360 rss: 37367808 rss_rlim: 4294967295
CPU usage: start_time: 1195999618 rtime: 33405 utime: 28330 stime: 5075 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 -1208928544 (LWP 2813)]
[New Thread -1242498160 (LWP 3905)]
(no debugging symbols found)
0x00846402 in __kernel_vsyscall ()

+ Trace 179694

Thread 1 (Thread -1208928544 (LWP 2813))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_str_hash
    from /lib/libglib-2.0.so.0
  • #5 g_hash_table_lookup
    from /lib/libglib-2.0.so.0
  • #6 ??
  • #7 nautilus_file_emit_changed
  • #8 nautilus_directory_emit_change_signals
  • #9 nautilus_file_changed
  • #10 ??
  • #11 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #12 ??
  • #13 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (6 sec old) ---------------------
munin-node
munin-node is stopped
munin-node
munin-node (pid 32061 31972) is running...
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x5d specified for 0x1091ca7 ().
--- Hash table keys for warning below:
--> file:///home/SSHAccounts/David
(nautilus:32372): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x5d specified for 0x10937e2 ().
(gnome-terminal:2930): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
** (nautilus:2813): CRITICAL **: nautilus_file_get_uri: assertion `NAUTILUS_IS_FILE (file)' failed
--------------------------------------------------
Comment 1 Susana 2007-11-26 20:18:58 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 465786 ***