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 506825 - crash in Open Folder: I run the properties win...
crash in Open Folder: I run the properties win...
Status: RESOLVED DUPLICATE of bug 355018
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-02 09:50 UTC by Vladimír Čunát
Modified: 2008-01-02 20:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Vladimír Čunát 2008-01-02 09:50:31 UTC 
Version: 2.18.3

What were you doing when the application crashed?
I run the properties window of removable disc icon on my desktop.


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.18.3 2007-11-10 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-gentoo-r9 #10 Mon Nov 19 21:50:29 CET 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 67305472 vsize: 67305472 resident: 22085632 share: 17879040 rss: 22085632 rss_rlim: 4294967295
CPU usage: start_time: 1195672555 rtime: 210 utime: 197 stime: 13 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1228941632 (LWP 5747)]
0xb7f03410 in __kernel_vsyscall ()

+ Trace 183782

Thread 1 (Thread -1228941632 (LWP 5747))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/libc.so.6
  • #5 changed_group_callback
    at fm-properties-window.c line 1646
  • #6 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #7 IA__g_closure_invoke
    at gclosure.c line 490
  • #8 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #9 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #10 IA__g_signal_emit
    at gsignal.c line 2243
  • #11 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 ??
  • #13 ??
  • #14 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (37 sec old) ---------------------
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
krusader: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file krviewer.rc
krusader: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file krviewer.rc
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-02 20:57:36 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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