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 574313 - crash in Home Folder: closed last window
crash in Home Folder: closed last window
Status: RESOLVED DUPLICATE of bug 480179
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-05 22:12 UTC by meier
Modified: 2009-03-05 22:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description meier 2009-03-05 22:12:39 UTC
What were you doing when the application crashed?
closed last window


Distribution: Debian squeeze/sid
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 79753216 vsize: 79753216 resident: 22405120 share: 16719872 rss: 22405120 rss_rlim: 4294967295
CPU usage: start_time: 1236291080 rtime: 106 utime: 96 stime: 10 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 0xb698f750 (LWP 26336)]
0xb7f42424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb698f750 (LWP 26336))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.18.4/glib/gspawn.c line 382
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.18.4/glib/gspawn.c line 694
  • #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 gconf_client_remove_dir
    from /usr/lib/libgconf-2.so.4
  • #8 ??
    from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
  • #9 ??
  • #10 ??
    from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
  • #11 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (34 sec old) ---------------------
Unknown ClientMessageEvent 259
The program 'gnome-terminal' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 58548 error_code 11 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Unknown ClientMessageEvent 259
Unknown ClientMessageEvent 584
(gnome-terminal:26076): Vte-WARNING **: Kein Handler für Kontrollsequenz »device-control-string« festgelegt.
Unknown ClientMessageEvent 584
--------------------------------------------------
Comment 1 Fabio Durán Verdugo 2009-03-05 22:59:45 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 480179 ***