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 532164 - crash in File Browser:
crash in File Browser:
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
: 532237 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-05-08 13:45 UTC by b.latorre
Modified: 2008-05-09 08:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description b.latorre 2008-05-08 13:45:18 UTC
Version: 2.20.0

What were you doing when the application crashed?



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

System: Linux 2.6.25 #1 SMP Mon Apr 28 10:16:32 CEST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 78811136 vsize: 78811136 resident: 31928320 share: 17592320 rss: 31928320 rss_rlim: 4294967295
CPU usage: start_time: 1210238544 rtime: 467 utime: 435 stime: 32 cutime:36 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 0xb6b9a720 (LWP 5289)]
0xffffe424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6b9a720 (LWP 5289))

  • #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 ---------------------
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
connection_message_func(): Callback
CALLBACK: save-authentication!!!
connection_message_func(): Callback
CALLBACK: save-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: fill-authentication!!!
--------------------------------------------------
Comment 1 Gianluca Borello 2008-05-08 15:26:22 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 A. Walton 2008-05-08 20:32:27 UTC
*** Bug 532237 has been marked as a duplicate of this bug. ***
Comment 3 Gianluca Borello 2008-05-08 20:53:44 UTC
all this bugs are duplicate of bug 523534, but I wait for a decent stacktrace or the magic keyword "samba share" before marking them as a duplicates ;-)
Comment 4 A. Walton 2008-05-08 20:58:31 UTC
Yeah, without seeing the word samba I usually just mark them as incomplete (as that's what they are). They most likely are duplicates of 523534, but of course there's no way to know...

Maybe one of these days Debian will fix this...
Comment 5 Cosimo Cecchi 2008-05-08 21:48:54 UTC
(In reply to comment #0)
> 
> ----------- .xsession-errors ---------------------
> CALLBACK: fill-authentication!!!
> connection_message_func(): Callback
> CALLBACK: full-authentication!!!
> connection_message_func(): Callback

Usually the presence of these strings in .xsession-errors mean that the bug is a dupe of bug #522534.
Comment 6 Cosimo Cecchi 2008-05-08 21:49:07 UTC

*** This bug has been marked as a duplicate of 522534 ***
Comment 7 Gianluca Borello 2008-05-09 08:38:07 UTC
@cosimo: thanks for the hint :-)