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 526030 - crash in Home Folder: I was tying to access a ...
crash in Home Folder: I was tying to access a ...
Status: RESOLVED DUPLICATE of bug 525181
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-04-03 18:47 UTC by noces14
Modified: 2008-04-04 10:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description noces14 2008-04-03 18:47:59 UTC
What were you doing when the application crashed?
I was tying to access a computer into my lan.


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 #1 SMP Mon Feb 11 14:37:45 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: 62894080 vsize: 62894080 resident: 28418048 share: 15081472 rss: 28418048 rss_rlim: 4294967295
CPU usage: start_time: 1207248411 rtime: 397 utime: 358 stime: 39 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)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b99720 (LWP 3596)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6b99720 (LWP 3596))

  • #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 (27 sec old) ---------------------
SFX q   gir     je-te          tossir
warning: incompatible stripping characters and condition:
SFX q   gir     je-vos         tossir
Aviso do gerenciador de janelas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2800054 (pacotes co)
Aviso do gerenciador de janelas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Aviso do gerenciador de janelas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x280208e (BrOffice.o)
Aviso do gerenciador de janelas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Aviso do gerenciador de janelas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x280208e (BrOffice.o)
Aviso do gerenciador de janelas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
Initializing gnome-mount extension
seahorse nautilus module initialized
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-04-04 10:19:05 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 525181 ***