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 530159 - crash in Home Folder: freigegebenen Ordner auf...
crash in Home Folder: freigegebenen Ordner auf...
Status: RESOLVED DUPLICATE of bug 522534
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-04-27 07:39 UTC by Michael Wolf
Modified: 2008-04-27 09:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Michael Wolf 2008-04-27 07:39:07 UTC 
What were you doing when the application crashed?
freigegebenen Ordner auf Windowscomputer im Netzwerk geöffnet


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-486 #1 Fri Apr 18 23:53:06 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 80568320 vsize: 80568320 resident: 26300416 share: 16207872 rss: 26300416 rss_rlim: 4294967295
CPU usage: start_time: 1209287781 rtime: 228 utime: 215 stime: 13 cutime:16 cstime: 2 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 0xb6c43720 (LWP 3194)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 196236

Thread 1 (Thread 0xb6c43720 (LWP 3194))

  • #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 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
    from /usr/lib/libglib-2.0.so.0
  • #15 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (7 sec old) ---------------------
Fenstermanager-Warnung:Gespeicherte Sitzungsdatei /home/michael/.metacity/sessions/default0.ms konnte nicht gelesen werden: Failed to open file '/home/michael/.metacity/sessions/default0.ms': Datei od
seahorse nautilus module initialized
Initializing gnome-mount extension
Fenstermanager-Warnung:Ungültiges WM_TRANSIENT_FOR-Fenster 0x52 festgelegt für 0x1000833 ().
** (gksu:3499): WARNING **: Lock taken by pid: 3492. Exiting.
/usr/lib/python2.4/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet
  warnings.warn("apt API not stable yet", FutureWarning)
Fenstermanager-Warnung:last_user_time (3075810352) is greater than comparison timestamp (2402574369).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET
Fenstermanager-Warnung:0x2400003 (Software U) appears to be one of the offending windows with a timestamp of 3075810352.  Working around...
current dist not found in meta-release file
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
--------------------------------------------------
Comment 1 Gianluca Borello 2008-04-27 09:20:22 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 522534 ***