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 445763 - crash in Home Folder: open property. and selec...
crash in Home Folder: open property. and selec...
Status: RESOLVED DUPLICATE of bug 406462
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-09 14:12 UTC by m-koide
Modified: 2007-07-26 19:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description m-koide 2007-06-09 14:12:07 UTC
What were you doing when the application crashed?
open property. and select tabs.


Distribution: Fedora release 7.89 (Rawhide)
Gnome Release: 2.19.3 2007-06-04 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3213.fc8 #1 SMP Thu Jun 7 16:47:39 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 426299392 vsize: 426299392 resident: 41353216 share: 24137728 rss: 41353216 rss_rlim: 18446744073709551615
CPU usage: start_time: 1181397141 rtime: 125 utime: 95 stime: 30 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496347680 (LWP 2818)]
(no debugging symbols found)
0x00000031c200d89f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496347680 (LWP 2818))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gtk_widget_get_toplevel
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #4 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #5 gtk_widget_has_screen
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #6 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #7 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #8 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #9 g_cclosure_marshal_VOID__ENUM
    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 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors (192 sec old) ---------------------
Debug: Loading Beagle.Util.Conf+DaemonConfig from daemon.xml
Debug: Loading Beagle.Util.Conf+SearchingConfig from searching.xml
You can not run beagle as root.  Beagle is designed to run from your own
user account.  If you want to create multiuser or system-wide indexes, use
the beagle-build-index tool.
You can override this setting using the beagle-config or beagle-settings tools.
** Message: drive = 0
** Message: volume = 0
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
***MEMORY-WARNING***: gnome-terminal[2914]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this 
Loading "installonlyn" plugin
Loading "installonlyn" plugin
Loading "installonlyn" plugin
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-06-09 16:10:20 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 André Klapper 2007-07-26 19:10:48 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 406462 ***