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 491944 - crash in Open Folder: I was right clicking on ...
crash in Open Folder: I was right clicking on ...
Status: RESOLVED DUPLICATE of bug 440988
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-31 04:14 UTC by tbryant87
Modified: 2007-11-05 07:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description tbryant87 2007-10-31 04:14:23 UTC 
Version: 2.18.3

What were you doing when the application crashed?
I was right clicking on a folder to view it's properties


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 127819776 vsize: 127819776 resident: 34828288 share: 21819392 rss: 34828288 rss_rlim: 4294967295
CPU usage: start_time: 1193789355 rtime: 620 utime: 406 stime: 214 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 -1208879392 (LWP 2828)]
[New Thread -1231959152 (LWP 4759)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 174076

Thread 1 (Thread -1208879392 (LWP 2828))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #10 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 ??
  • #12 ??
  • #13 g_sequence_sort_changed_iter
  • #14 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_list_store_set_valist
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gtk_list_store_set
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
    from /lib/libglib-2.0.so.0
  • #24 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #25 ??
    from /lib/libglib-2.0.so.0
  • #26 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #27 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (13646 sec old) ---------------------
(Banshee:3143): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1: Character reference '3' does not encode a permitted character
(Banshee:3143): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1: Character reference '3' does not encode a permitted character
(Banshee:3143): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1: Character reference '3' does not encode a permitted character
(Banshee:3143): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1: Character reference '3' does not encode a permitted character
(Banshee:3143): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1: Character reference '3' does not encode a permitted character
(Banshee:3143): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1: Character reference '3' does not encode a permitted character
GStreamer resource error: NotFound
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 André Klapper 2007-11-05 07:47:55 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 440988 ***