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 552531 - crash in Home Folder: alt + f2, gksu nautilus
crash in Home Folder: alt + f2, gksu nautilus
Status: RESOLVED DUPLICATE of bug 552414
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-09-16 18:17 UTC by lajos-herpai
Modified: 2008-09-18 23:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description lajos-herpai 2008-09-16 18:17:00 UTC
What were you doing when the application crashed?
alt + f2, gksu nautilus


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: 56344576 vsize: 56344576 resident: 20246528 share: 14258176 rss: 20246528 rss_rlim: 4294967295
CPU usage: start_time: 1221588968 rtime: 131 utime: 110 stime: 21 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 0xb6b3b710 (LWP 8302)]
0xb7fa4424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6b3b710 (LWP 8302))

  • #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 (859993 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 A. Walton 2008-09-18 23:48:32 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 552414 ***