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 539104 - crash in File Browser: when I browse in my samb...
crash in File Browser: when I browse in my samb...
Status: RESOLVED DUPLICATE of bug 522534
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-19 09:52 UTC by pippotauro
Modified: 2008-06-19 13:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description pippotauro 2008-06-19 09:52:09 UTC 
Version: 2.20.0

What were you doing when the application crashed?
when I browse in my samba server I have always this crash


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: Glossy
Icon Theme: SnowIsh-1.0_PNG

Memory status: size: 92037120 vsize: 92037120 resident: 31223808 share: 18657280 rss: 31223808 rss_rlim: 4294967295
CPU usage: start_time: 1213866749 rtime: 588 utime: 530 stime: 58 cutime:5 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 0xb6c25720 (LWP 24897)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 200838

Thread 1 (Thread 0xb6c25720 (LWP 24897))

  • #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 (1822 sec old) ---------------------
(evolution:25015): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:25015): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:25015): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:25015): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:25015): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:25015): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:25015): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Gianluca Borello 2008-06-19 13:01:13 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 ***