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 457409 - crash in Home Folder: I just built Gnome 2.19....
crash in Home Folder: I just built Gnome 2.19....
Status: RESOLVED DUPLICATE of bug 449488
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-16 17:00 UTC by Richard Schwarting
Modified: 2007-07-26 13:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Richard Schwarting 2007-07-16 17:00:33 UTC 
What were you doing when the application crashed?
I just built Gnome 2.19.4 (maybe .5) using Garnome.  I followed their instructions for setting up a Gnome Session in GDM.  I then logged in.  The panel appears correctly, as does this window.  However, Nautilus appears to have failed.

Sorry that I cannot provide more details yet, but Bug Buddy asks, so here I am.  I think there might have been a problem with their suggested steps for dbus+hal. 

Cheers


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.19.4 2007-07-11 (GARNOME)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Enabled
GTK+ Theme: Bluecurve-Tangerine
Icon Theme: Bluecurve

Memory status: size: 345321472 vsize: 345321472 resident: 13418496 share: 10682368 rss: 13418496 rss_rlim: 18446744073709551615
CPU usage: start_time: 1184604888 rtime: 21 utime: 17 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/home/slappy/garnome/bin/nautilus'

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912614728400 (LWP 6327)]
0x000000361140d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 148395

Thread 1 (Thread 46912614728400 (LWP 6327))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 865
  • #2 <signal handler called>
  • #3 IA__g_logv
    at gmessages.c line 503
  • #4 IA__g_log
    at gmessages.c line 517
  • #5 IA__g_object_new
    at gobject.c line 792
  • #6 nautilus_module_add_type
    at nautilus-module.c line 253
  • #7 nautilus_module_init
    at nautilus-module.c line 160
  • #8 nautilus_application_startup
    at nautilus-application.c line 400
  • #9 main
    at nautilus-main.c line 533
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors (17 sec old) ---------------------
(nautilus:6327): Liboobs-WARNING **: Failed to connect to socket /home/slappy/garnome/var/run/dbus/system_bus_socket: Datei oder Verzeichnis nicht gefunden
Initializing gnome-mount extension
** (nautilus:6327): WARNING **: Cannot connect to system bus: org.freedesktop.DBus.Error.FileNotFound : Failed to connect to socket /home/slappy/garnome/var/run/dbus/system_bus_socket: Datei oder Verz
** (nautilus:6327): WARNING **: Could not initialize hal context
GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
aborting...
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
--------------------------------------------------
Comment 1 André Klapper 2007-07-26 13:16: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 449488 ***