in nautilus in a folder's properties, basic tab there is a button, the icon of the folder, i click it in an attempt to change it, i expect an icon browser or a file browser, so i can select an icon or an image from the filesystem for it. there nautilus crashes. it attempts to report it's crash, i fill the data in the bug reporting tool, but that presents an error when it reports the issue because my software is too old.
qlist -Iv nautilus gnome-base/nautilus-2.16.0 gnome-extra/nautilus-actions-1.2 gnome-extra/nautilus-cd-burner-2.16.0 gnome-extra/nautilus-image-converter-0.0.5 x11-themes/nautilus-themes-1.0 gnome-base/nautilus-2.16.0 USE="X gnome -beagle -debug" emerge --info Portage 2.1.2_pre1 (default-linux/x86/2006.0, gcc-4.1.1/vanilla, glibc-2.4-r3, 2.6.16-gentoo-r9 i686) ================================================================= System uname: 2.6.16-gentoo-r9 i686 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.12.5 Last Sync: Fri, 22 Sep 2006 08:30:01 +0000 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] app-admin/eselect-compiler: 2.0.0_rc2-r1 dev-java/java-config: [Not Present] dev-lang/python: 2.3.5-r2, 2.4.3-r3 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.60 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.13-r3 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=athlon -mtune=athlon -pipe -mno-tls-direct-seg-refs" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/X11/xkb" CONFIG_PROTECT_MASK="/etc/env.d /etc/eselect/compiler /etc/gconf /etc/revdep-rebuild /etc/splash /etc/terminfo" CXXFLAGS="-O2 -march=athlon -mtune=athlon -pipe -mno-tls-direct-seg-refs" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig confcache distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://adelie.polymtl.ca/ http://gentoo.arcticnetwork.ca/ http://gentoo.osuosl.org/ http://distro.ibiblio.org/pub/linux/distributions/gentoo/ http://www.gtlib.gatech.edu/pub/gentoo " LC_ALL="en_US.UTF-8" LINGUAS="en hu ro" MAKEOPTS="-s" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage /usr/portage/local/layman/portage-xgl /usr/portage/local/layman/portage-xgl" SYNC="rsync://gw/gentoo-portage" USE="x86 X aac acpi alsa apm avi bash-completion browserplugin bzip2 cairo cdparanoia cdr cluster css cups cursors dbus dga divx4linux dri dvd dvdr dvdread elibc_glibc encode erandom esd evolution exif fbsplash firefox flac foomaticdb fpu gd gdm gif gimp gimpprint glitz gmail gnome gnutls gpm gstreamer gtk gtk2 hal howl icons imap input_devices_keyboard input_devices_mouse ithreads jabber jpeg kernel_linux kqemu libnotify linguas_en linguas_hu linguas_ro live lm_sensors maildir mbox mbrola mime mmx mmxext mozdevelop mozilla mozmail moznocompose moznoirc moznoroaming mozsvg mp3 mpeg mplayer mtrr mysql nautilus ncurses nls nptl nptlonly nvidia ogg openal opengl oss pam pcre pdf pdflib perl png ppds python quicktime readline rtc screen sdl softmmu sox spell sse sse2 ssl startup-notification subtitles svg tcpd truetype udev unicode usb userland_GNU userlocales utf8 vcd video_cards_nv video_cards_nvidia video_cards_vesa vorbis win32codecs wma xine xml xorg xprint xscreensaver xv xvid xvmc zlib" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS
today i had a strange experience with this. first thing i did with my nautilus was that i wanted to check this bug. and i did not show up, but a file browser window appeared so i could choose an image. i clicked on cancel, that was not the folder i wanted to change image for. i clicked on another nautilus folder, i started navigating to a deeper one, and nautilus crashed then, before it opened anything. since then i can navigate in folders, but still can't change image for them.
I'm able to change icons for folders with no problems or crashes... Maybe you could try re-emerging nautilus?
did that, more than once, what i might try is to query all nautilus deps, and rebuild/upgrade them. btw i have this behavior on 3 machines, the only machines runing 2.16.
Created attachment 98955 [details] bug buddy report alright, this is what bug buddy would report:
That seems familiar. What gtk+ version do you have installed? A quick bug search doesn't find anything useful, tho...
Fri Sep 8 20:20:23 2006 <<< x11-libs/gtk+-2.8.20-r1 Fri Sep 8 20:20:23 2006 >>> x11-libs/gtk+-2.10.3 Fri Sep 22 15:45:57 2006 >>> x11-libs/gtk+-2.10.3 Mon Oct 2 17:43:51 2006 <<< x11-libs/gtk+-2.10.3 Mon Oct 2 17:43:51 2006 >>> x11-libs/gtk+-2.10.4 i would guess it's doing it since 2.10
Does it happen with gtk+-2.10.5 or newer too? That version fixed gtk_file_button_new related issues for other apps already, and had 85 duplicates on the upstream bug spread across reports against different apps caused by gtk+. You also want the latest libgnomeui if you are using the gnome-vfs filechooser backend.
i just upgraded to x11-libs/gtk+-2.10.6, the issue stands.
Fedora has a patch for this: http://cvs.fedora.redhat.com/viewcvs/*checkout*/devel/nautilus/nautilus-2.16.0-model-crash.patch?rev=1.1
Does nautilus-2.16.1 fix the problem? The patch applied in Fedora seems to be included in 2.16.1 tarball. http://bugzilla.gnome.org/show_bug.cgi?id=355242
confirming bug on 2.16.1
it's corrected. thanks
(In reply to comment #12) > confirming bug on 2.16.1 Remi, did you perhaps get the old versions session reused, or something of that sort? killall nautilus beforehand would probably be helpful (or one crash with this, for that matter)
Sorry for the confusion, the bug is fixed with 2.16.1 ... I thought I had already upgraded. Go ahead and close it :) (one not so small step for unmasking gnome 2.16)
Good :) Though I don't consider _all_ blockers of #132627 as unmasking blockers, but maybe just stabling blockers.
