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 539932 - crash in Home Folder: Tentei acessar um compar...
crash in Home Folder: Tentei acessar um compar...
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-06-24 12:00 UTC by rrvirtual
Modified: 2008-06-24 23:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description rrvirtual 2008-06-24 12:00:48 UTC 
What were you doing when the application crashed?
Tentei acessar um compartilhamento samba do windows 98 sem senha.


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: nuoveXT-1.6

Memory status: size: 134639616 vsize: 134639616 resident: 29794304 share: 19308544 rss: 29794304 rss_rlim: 4294967295
CPU usage: start_time: 1214307122 rtime: 628 utime: 598 stime: 30 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 0xb6bea940 (LWP 6632)]
[New Thread 0xb181db90 (LWP 7836)]
[New Thread 0xb281fb90 (LWP 7829)]
[New Thread 0xb6351b90 (LWP 7816)]
[New Thread 0xb5b50b90 (LWP 7742)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 201252

Thread 1 (Thread 0xb6bea940 (LWP 6632))

  • #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 (286 sec old) ---------------------
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
** (nautilus:6632): WARNING **: Hit unhandled case 31 (Operação cancelada) in fm_report_error_loading_directory
Aviso do gerenciador de janelas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00003 (Visualizad)
Aviso do gerenciador de janelas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-06-24 13:00:45 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 522534 ***
Comment 2 rrvirtual 2008-06-24 23:29:26 UTC 
Ok Thank you for your attention. I look forward next software version.