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 528185 - crash in Home Folder: I opened a folder on a s...
crash in Home Folder: I opened a folder on a s...
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-15 10:17 UTC by christoph.goesgens
Modified: 2008-04-15 12:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description christoph.goesgens 2008-04-15 10:17:10 UTC 
What were you doing when the application crashed?
I opened a folder on a samba share (samba server version 3.0.9-1.3E.9 on RHEL3).  This worked just a few minutes ago (for a different folder on the same share). Right now it crashed several times in a row.


Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686-bigmem #1 SMP Thu Mar 27 18:30:25 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: 85245952 vsize: 85245952 resident: 33554432 share: 15429632 rss: 33554432 rss_rlim: 4294967295
CPU usage: start_time: 1208254294 rtime: 150 utime: 136 stime: 14 cutime:0 cstime: 0 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)

<snip> Message repeated 25 times </snip>

[Thread debugging using libthread_db enabled]
[New Thread 0xb6c05720 (LWP 23162)]
(no debugging symbols found)

<snip> Message repeated 95 times </snip>

0xffffe410 in __kernel_vsyscall ()

+ Trace 195277

Thread 1 (Thread 0xb6c05720 (LWP 23162))

  • #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 (10 sec old) ---------------------
** (gnome-panel:4218): WARNING **: Could not load source 'Personal' from 'system'
** (gnome-panel:4218): WARNING **: Could not load source 'Personal' from 'system'
javaldx failed! 
Fenstermanager-Warnung:Received a _NET_WM_MOVERESIZE message for 0x4200020 (Liquid Dre); these messages lack timestamps and therefore suck.
** (gnome-panel:4218): WARNING **: Could not load source 'Personal' from 'system'
** (gnome-panel:4218): WARNING **: Could not load source 'Personal' from 'system'
Initializing gnome-mount extension
Initializing gnome-mount extension
--------------------------------------------------
Comment 1 Gianluca Borello 2008-04-15 12:53:54 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 ***