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 552414 - crash in Home Folder:
crash in Home Folder:
Status: RESOLVED INCOMPLETE
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 552415 552531 554218 554220 554221 554351 563185 563915 564158 565185 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-09-15 20:25 UTC by lajos-herpai
Modified: 2009-02-06 15:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description lajos-herpai 2008-09-15 20:25:55 UTC
What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-686 #1 SMP Thu Aug 28 12:00:54 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 56217600 vsize: 56217600 resident: 20013056 share: 14127104 rss: 20013056 rss_rlim: 4294967295
CPU usage: start_time: 1221510334 rtime: 111 utime: 92 stime: 19 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6ad4710 (LWP 5976)]
0xb7f3d424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6ad4710 (LWP 5976))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.16.5/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.16.5/glib/gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 <signal handler called>
  • #7 oobs_share_smb_new
    at oobs-share-smb.c line 339
  • #8 oobs_smb_config_update
    at oobs-smbconfig.c line 250
  • #9 update_object_from_message
    at oobs-object.c line 359
  • #10 async_message_cb
    at oobs-object.c line 430
  • #11 ??
    from /usr/lib/libdbus-1.so.3
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
    from /usr/lib/libdbus-1.so.3
  • #16 ??
    from /usr/lib/libdbus-1.so.3
  • #17 ??
  • #18 ??
  • #19 ??
    from /usr/lib/libdbus-1.so.3
  • #20 ??
  • #21 ??
  • #22 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (781352 sec old) ---------------------
** Message: another SSH agent is running at: /tmp/ssh-mKHMKh5155/agent.5155
Shutdown failed or nothing to shut down.
** (gnome-settings-daemon:5206): WARNING **: Failed to open file '/etc/gnome/config/General.ad': Datei oder Verzeichnis nicht gefunden
Initializing gnome-mount extension
seahorse nautilus module initialized
Fenstermanager-Warnung:Gespeicherte Sitzungsdatei /root/.metacity/sessions/default0.ms konnte nicht gelesen werden: Failed to open file '/root/.metacity/sessions/default0.ms': Datei oder Verzeichnis n
** (gnome-panel:5220): WARNING **: Failed to establish a connection with GDM: Datei oder Verzeichnis nicht gefunden
** (gnome-panel:5220): WARNING **: Failed to establish a connection with GDM: Datei oder Verzeichnis nicht gefunden
Fenstermanager-Warnung:CurrentTime used to choose focus window; focus window may not be correct.
Fenstermanager-Warnung:Got a request to focus the no_focus_window with a timestamp of 0.  This shouldn't happen!
gnome-screensaver: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.0.
Xsession: X session started for root at Sa 6. Sep 21:23:17 CEST 2008
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-09-16 10:18:51 UTC
*** Bug 552415 has been marked as a duplicate of this bug. ***
Comment 2 Cosimo Cecchi 2008-09-16 10:19:19 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 3 A. Walton 2008-09-18 23:48:32 UTC
*** Bug 552531 has been marked as a duplicate of this bug. ***
Comment 4 Cosimo Cecchi 2008-09-29 20:04:38 UTC
*** Bug 554351 has been marked as a duplicate of this bug. ***
Comment 5 Cosimo Cecchi 2008-09-29 20:05:01 UTC
*** Bug 554221 has been marked as a duplicate of this bug. ***
Comment 6 Cosimo Cecchi 2008-09-29 20:07:44 UTC
*** Bug 554218 has been marked as a duplicate of this bug. ***
Comment 7 Cosimo Cecchi 2008-09-29 20:07:50 UTC
*** Bug 554220 has been marked as a duplicate of this bug. ***
Comment 8 A. Walton 2008-12-04 03:25:51 UTC
*** Bug 563185 has been marked as a duplicate of this bug. ***
Comment 9 André Klapper 2008-12-09 23:06:21 UTC
*** Bug 563915 has been marked as a duplicate of this bug. ***
Comment 10 Bruno Boaventura 2008-12-11 21:02:29 UTC
*** Bug 564158 has been marked as a duplicate of this bug. ***
Comment 11 palfrey 2008-12-21 01:47:53 UTC
*** Bug 565185 has been marked as a duplicate of this bug. ***
Comment 12 Pedro Villavicencio 2009-02-06 15:55:52 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!