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 569137 - crash in File Browser:
crash in File Browser:
Status: RESOLVED DUPLICATE of bug 480179
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-01-25 23:08 UTC by jkjfh
Modified: 2009-01-26 11:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description jkjfh 2009-01-25 23:08:17 UTC 
Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian 5.0
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.27-8-eeepc-lean #1 SMP Sun Nov 16 12:45:01 MST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mac4Lin_GTK_v1.0_RC
Icon Theme: hydroxygen

Memory status: size: 43114496 vsize: 43114496 resident: 22183936 share: 12255232 rss: 22183936 rss_rlim: 4294967295
CPU usage: start_time: 1232924827 rtime: 132 utime: 92 stime: 40 cutime:0 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 0xb790c9a0 (LWP 3617)]
(no debugging symbols found)
0xb7ff2424 in __kernel_vsyscall ()

+ Trace 211867

Thread 1 (Thread 0xb790c9a0 (LWP 3617))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    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 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 <signal handler called>
  • #7 gconf_client_remove_dir
    from /usr/lib/libgconf-2.so.4
  • #8 ??
    from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
  • #9 ??
  • #10 ??
    from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
  • #11 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
(bug-buddy:3935): Gtk-WARNING **: Impossibile trovare il motore del tema in module_path: «pixmap»,
(bug-buddy:3935): Gtk-WARNING **: Impossibile trovare il motore del tema in module_path: «pixmap»,
(bug-buddy:3935): Gtk-WARNING **: Impossibile trovare il motore del tema in module_path: «pixmap»,
(bug-buddy:3935): Gtk-WARNING **: Impossibile trovare il motore del tema in module_path: «pixmap»,
(bug-buddy:3935): Gtk-WARNING **: Impossibile trovare il motore del tema in module_path: «pixmap»,
(bug-buddy:3935): Gtk-WARNING **: Impossibile trovare il motore del tema in module_path: «pixmap»,
nouvelle icone d'appli (18874371)
 insertion de Bug Buddy apres Pidgin Internet Messenger -> iSeparatorType : 1
OK
--------------------------------------------------
Comment 1 palfrey 2009-01-26 11:37:29 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 480179 ***