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 539419 - crash in Open Folder: Browsede en en mappe ove...
crash in Open Folder: Browsede en en mappe ove...
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-21 09:13 UTC by Nick Østergaard
Modified: 2008-06-23 12:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Nick Østergaard 2008-06-21 09:13:50 UTC 
Version: 2.20.0

What were you doing when the application crashed?
Browsede en en mappe over smb, gennem nautilus


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

System: Linux 2.6.24-1-amd64 #1 SMP Fri Apr 18 23:08:22 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 399302656 vsize: 399302656 resident: 34476032 share: 18313216 rss: 34476032 rss_rlim: 18446744073709551615
CPU usage: start_time: 1214035112 rtime: 614 utime: 561 stime: 53 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2ae077115240 (LWP 3272)]
(no debugging symbols found)
0x00002ae070a0cedf in waitpid () from /lib/libpthread.so.0

+ Trace 200996

Thread 1 (Thread 0x2ae077115240 (LWP 3272))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 ??
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 ??
  • #9 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #13 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
  • #15 __libc_start_main
    from /lib/libc.so.6
  • #16 ??
  • #17 ??
  • #18 ??
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (87 sec old) ---------------------
CALLBACK: fill-authentication!!!
Vindueshåndteringsadvarsel: Ugyldig WM_TRANSIENT_FOR vindue 0x1400771 specificeret for 0x1400984 (Brugerveri).
Vindueshåndteringsadvarsel: Ugyldig WM_TRANSIENT_FOR vindue 0x1400771 specificeret for 0x1400bb0 (Brugerveri).
Vindueshåndteringsadvarsel: Ugyldig WM_TRANSIENT_FOR vindue 0x1400771 specificeret for 0x1400d38 (Brugerveri).
Vindueshåndteringsadvarsel: Ugyldig WM_TRANSIENT_FOR vindue 0x1400771 specificeret for 0x1400fc1 (Brugerveri).
Vindueshåndteringsadvarsel: Ugyldig WM_TRANSIENT_FOR vindue 0x1400771 specificeret for 0x14012a0 (Brugerveri).
Vindueshåndteringsadvarsel: Ugyldig WM_TRANSIENT_FOR vindue 0x1400771 specificeret for 0x140153b (Brugerveri).
Vindueshåndteringsadvarsel: Ugyldig WM_TRANSIENT_FOR vindue 0x1400771 specificeret for 0x1401773 (Brugerveri).
Vindueshåndteringsadvarsel: Ugyldig WM_TRANSIENT_FOR vindue 0x1400771 specificeret for 0x14019e3 (Brugerveri).
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
** (nautilus:3272): WARNING **: Ingen beskrivelse fundet for MIME-typen "x-directory/smb-share" (filen er "download"), fortæl det venligst til Gnome VFS-postlisten.
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-06-21 10:01:36 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 Nick Østergaard 2008-06-23 12:19:11 UTC 
Great! :)