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 540433 - crash in File Browser: browsing folder with acl...
crash in File Browser: browsing folder with acl...
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-27 07:37 UTC by filederba
Modified: 2008-06-27 09:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description filederba 2008-06-27 07:37:50 UTC 
Version: 2.20.0

What were you doing when the application crashed?
browsing folder with acl on samba pdc


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

System: Linux 2.6.23.82.6.23 #2 PREEMPT Tue Feb 12 19:20:57 CET 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: Neu

Memory status: size: 423428096 vsize: 423428096 resident: 38297600 share: 20406272 rss: 38297600 rss_rlim: 18446744073709551615
CPU usage: start_time: 1214552184 rtime: 231 utime: 199 stime: 32 cutime:2 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2afdb8397b60 (LWP 3021)]
(no debugging symbols found)
0x00002afdb0f1e5ef in waitpid () from /lib/libpthread.so.0

+ Trace 201507

Thread 1 (Thread 0x2afdb8397b60 (LWP 3021))

  • #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 ??
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 ??
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors ---------------------
Nautilus-Share-Message: end of spawn args; SPAWNING
Nautilus-Share-Message: returned from spawn: SUCCESS: 
Nautilus-Share-Message: exit code 0
Nautilus-Share-Message: caller wants GKeyFile
Nautilus-Share-Message: success from calling net usershare and parsing its output
Nautilus-Share-Message: ------------------------------------------
** Message: Failed to close thumbnail pixbuf loader for /home/luigi/ciao.pnm: Formato del file di immagine non riconosciuto
** Message: Failed to close thumbnail pixbuf loader for /home/luigi/image.pnm: Formato del file di immagine non riconosciuto
** Message: Failed to close thumbnail pixbuf loader for /home/luigi/ciao.pnm: Formato del file di immagine non riconosciuto
** Message: Failed to close thumbnail pixbuf loader for /home/luigi/image.pnm: Formato del file di immagine non riconosciuto
** (nautilus:3021): WARNING **: Non è stata trovata alcuna descrizione per il tipo MIME «x-directory/smb-share» (relativa al file «ced»); avvisare cortesemente la mailing list di gnome-vfs.
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7ffffebfd000
--------------------------------------------------
Comment 1 Gianluca Borello 2008-06-27 09:36:53 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 ***