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 506758 - crash in Open Folder: searching for files in n...
crash in Open Folder: searching for files in n...
Status: RESOLVED DUPLICATE of bug 454799
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-01 22:32 UTC by okuliar.a
Modified: 2008-01-02 20:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description okuliar.a 2008-01-01 22:32:28 UTC
Version: 2.18.3

What were you doing when the application crashed?
searching for files in nautilus file manager


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

System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: maryj2
Icon Theme: nuoveXT.2.2

Memory status: size: 135004160 vsize: 135004160 resident: 48914432 share: 27963392 rss: 48914432 rss_rlim: 4294967295
CPU usage: start_time: 1199190909 rtime: 3180 utime: 2803 stime: 377 cutime:698 cstime: 64 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 -1208465696 (LWP 30881)]
[New Thread -1372054640 (LWP 6733)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 2 (Thread -1372054640 (LWP 6733))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strstr
    from /lib/libc.so.6
  • #5 ??
  • #6 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #7 ??
  • #8 ??
  • #9 ??


----------- .xsession-errors ---------------------
/home/dekel/.themes/maryj2/gtk-2.0/panel_custom.rc:63: Background image options specified without filename
/home/dekel/.themes/maryj2/gtk-2.0/panel_custom.rc:71: Unable to locate image file in pixmap_path: "Panel/panelbutton_gray_1.png"
/home/dekel/.themes/maryj2/gtk-2.0/panel_custom.rc:77: Background image options specified without filename
/home/dekel/.themes/maryj2/gtk-2.0/panel_custom.rc:85: Unable to locate image file in pixmap_path: "Panel/panelbutton_gray_1.png"
/home/dekel/.themes/maryj2/gtk-2.0/panel_custom.rc:91: Background image options specified without filename
/home/dekel/.themes/maryj2/gtk-2.0/panel_custom.rc:98: Unable to locate image file in pixmap_path: "Panel/panelbutton_gray_1.png"
/home/dekel/.themes/maryj2/gtk-2.0/panel_custom.rc:101: Background image options specified without filename
/home/dekel/.themes/maryj2/gtk-2.0/panel_custom.rc:108: Unable to locate image file in pixmap_path: "Panel/panelbutton_gray_1.png"
/home/dekel/.themes/maryj2/gtk-2.0/panel_custom.rc:111: Background image options specified without filename
/home/dekel/.themes/maryj2/gtk-2.0/panel_black-plastic.rc:15: error: invalid string constant "panelbuttons-black", expected valid string constant
/home/dekel/.themes/maryj2/gtk-2.0/toolbar-custom.rc:19: error: invalid string constant "toolbar", expected valid string constant
/home/dekel/.themes/maryj2/gtk-2.0/gtkrc:249: Unable to locate image file in pixmap_path: "Toolbar/toolbar.png"
/home/dekel/.themes/maryj2/gtk-2.0/gtkrc:252: Background image options specified without filename
/home/dekel/.themes/maryj2/gtk-2.0/gtkrc:1616: Unable to locate image file in pixmap_path: "Buttons/gray_button.png"
/home/dekel/.themes/maryj2/gtk-2.0/gtkrc:1620: Background image options specified without filename
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-02 20:52:27 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 454799 ***