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 511673 - crash in Home Folder: Ich habe einen usb stick...
crash in Home Folder: Ich habe einen usb stick...
Status: RESOLVED DUPLICATE of bug 355018
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-23 23:23 UTC by sboberg
Modified: 2008-01-24 23:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description sboberg 2008-01-23 23:23:59 UTC 
What were you doing when the application crashed?
Ich habe einen usb stick eingesteckt der sich gerade merkwürdig verhält. Er läßt sich auf fremden rechnern nicht beschreiben; daher wollte ich mir seine eigenschaften ansehen. Habe auch heute erst von etch auf lenny upgegradet.
viel erfolg,
stefan


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Smooth-Mech-1.1
Icon Theme: OpenWorld

Memory status: size: 74633216 vsize: 74633216 resident: 24518656 share: 15908864 rss: 24518656 rss_rlim: 4294967295
CPU usage: start_time: 1169593010 rtime: 1424 utime: 1272 stime: 152 cutime:178 cstime: 61 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6d416b0 (LWP 4030)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 186566

Thread 1 (Thread 0xb6d416b0 (LWP 4030))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 strcmp
    from /lib/i686/cmov/libc.so.6
  • #7 ??
  • #8 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (8 sec old) ---------------------
** (gnome-control-center:9928): WARNING **: Schlüssel »/apps/control-center/cc_actions_list« konnte nicht gefunden werden
Fenstermanager-Warnung:last_user_time (3075900464) is greater than comparison timestamp (1362445711).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET
Fenstermanager-Warnung:0x2400003 (Einstellun) appears to be one of the offending windows with a timestamp of 3075900464.  Working around...
Fenstermanager-Warnung:last_user_time (3076158512) is greater than comparison timestamp (1362513788).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET
Fenstermanager-Warnung:0x2400003 (Einstellun) appears to be one of the offending windows with a timestamp of 3076158512.  Working around...
** (update-notifier:4034): WARNING **: no cdrom: disk
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-24 23:10:27 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 355018 ***