Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 51246 - Nautilus 2.6.1 crash
Summary: Nautilus 2.6.1 crash
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
Depends on:
Reported: 2004-05-16 22:17 UTC by Evan Langlois
Modified: 2004-05-25 09:33 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Evan Langlois 2004-05-16 22:17:50 UTC
Nautilus crashes when changing between views

Reproducible: Always
Steps to Reproduce:
1.Open nautilus to a directory with images
2.Select View->View As Image Collection
3.Browse some images
4.Select View->View As Icons
5.Wait for Nautilus to crash
Actual Results:  
Nautilus reloads

Expected Results:  
View should have returned back the way it was.  Also, there seems to be no way
to right click an image to open or edit it or select it as the background
picture when its in the Image Collection view.

Portage 2.0.50-r6 (default-x86-2004.0, gcc-3.3.3, glibc-2.3.3_pre20040420-r0,
System uname: 2.6.5-gentoo-r1 i686 Pentium III (Coppermine)
Gentoo Base System version 1.4.12
ccache version 2.3 [enabled]
Autoconf: sys-devel/autoconf-2.59-r3
Automake: sys-devel/automake-1.8.3
CFLAGS="-O3 -march=pentium3 -pipe -fforce-addr -falign-functions=4
-fprefetch-loop-arrays -ffast-math -mmmx -msse -fomit-frame-pointer"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref
/usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -march=pentium3 -pipe -fforce-addr -falign-functions=4
-fprefetch-loop-arrays -ffast-math -mmmx -msse -fomit-frame-pointer"
FEATURES="autoaddcvs ccache sandbox"
USE="X acpi adns aim alsa amd apm autofs avi berkdb bonobo bundled-libs cdr
chroot crypt cups dga directfb divx4linux dnd dnsdb doc dv dvb dvd dvdr encode
escreen esd ethereal etwin evms2 fam fastcgi fax fbcon fbdev ffmpeg fftw flac
flash foomaticdb freetds freetype fs gb gd gdbm ggi gif gimpprint glade gmp
gnome gnomedb gnutls gphoto2 gpm gps gstreamer gtk gtk2 gtkhtml guile hbci imlib
imlib2 innodb javascript jbig jpeg kde lcms ldap libg++ libgda libwww mad
maildir mdb memlimit mikmod mmap mmx mng mono motif mozilla mpeg mpeg4 msn music
mysql nagios-dns nagios-ntp nagios-ping nagios-ssh native ncurses nls odbc ofx
oggvorbis openal opengl opie oss pam pda pdflib perl physfs pic png postgres
ppds python qt quicktime readline roundrobin ruby samba scanner sdl skey slang
snmp socks5 sox speedo spell sqlite src sse ssl svg svga tcltk tcpd theora tiff
timidity transcode truetype type1 usb v4l v4l2 video_cards_sis videos wavelan
wifi wmf wolk-alsa wolk-bootsplash wolk-supermount wxwin wxwindows x86 xforms
xinerama xml xml2 xmms xosd xprint xv xvid yahoo yaz zlib zvbi"
Comment 1 foser (RETIRED) gentoo-dev 2004-05-18 08:54:51 UTC
first rule of bugreporting : tune down those freaking CFLAGS.

Comment 2 Evan Langlois 2004-05-18 17:54:31 UTC
The cflags were originally -O3 -fomit-frame-pointer -march=pentium3 -pipe
I highly doubt this is a CFLAG issue.  I'd be looking at the code.  If it is a CFLAG issue, then the compiler has a bug - either way there is a bug.  I will recompile nautilus with just -O2 and let you know.

Comment 3 Evan Langlois 2004-05-18 23:20:17 UTC
Seems to work with -O2.  So is this a compiler bug?  Should certain CFLAGS be removed by the nautilus ebuild?

Comment 4 foser (RETIRED) gentoo-dev 2004-05-25 01:49:53 UTC
no, your CFLAGS are your responsibility beyond reasonable defaults. You should just be aware that long lines of pretty crazy CFLAGS will get you in trouble at one point or the other.
Comment 5 Evan Langlois 2004-05-25 08:16:21 UTC
Or in cases like this one, it helps show bugs that exist in the code.  Changing optimization flags should not break the program - if it does, its a compiler bug or a bug in the program.  Even with -O2, I was able to repeat the problem once.  Adding tons of optimization flags makes the problem repeatable.
Comment 6 foser (RETIRED) gentoo-dev 2004-05-25 08:50:39 UTC
well obviously you compiled your whole system like that, so recompiling a few components may still prove instable at times. But i guess you build your system like that to expose bugs others wouldn't regularly encounter.

But you seem well versed in these things, so why don't you debug your crash and device us a fix ?

Certain optimizations certainly can & will break programs in our not so ideal world.
Comment 7 Evan Langlois 2004-05-25 09:12:30 UTC
Actually, most of the system was installed from the 2004.1 GRP CD, and then upgraded to current with -O3 -march=pentium3 -fomit-frame-pointer -pipe.  I do have ACCEPT_KEYWORDS="~x86" globally, so its pushing the leading edge a bit.  This is my typical set of CFLAGS.  

The extra cruft which was in the post was a recent change that I did for testing a few things (trying to see if I squeeze a bit more performance out of mplayer - didn't think it would help - but I wanted to try it).  I wasn't sure if nautilus had been upgraded again after I made that change so I left it.

I suppose I should just quit reporting bugs since you seem so quick to deny that there is a problem.  Reminds me of some horrible bugs I fixed at work, and even after it was fixed the original author still denied that there was anything wrong.

When I have the time to play with nautilus all day long changing the views to make it crash again, I'll let you know.  Until then, the next person who has this problem can find this bug number, but I hope they are ready to prove its a bug by recompiling there entire system with CFLAGS="-O" emerge -e world.

Because its so obvious that there isn't a bug in the program, nor its compiler, when a program locks up and dies.
Comment 8 foser (RETIRED) gentoo-dev 2004-05-25 09:33:36 UTC
mplayer resets all CFLAGS afaik, because it tends to bug about with anything but default CFLAGS (another one for your 'everything should work with all optimizations statement').

I'm quick to invalidize bugs we cannot possibly handle because it's plain asking for trouble to go to the edge of optimizations. And then complain if something crashes and cannot be reproduced consistently (not even by you). I could've predicated instability beforehand.

I don't say there's something wrong somewhere, but it is _FAR_ from realistic to expect us to debug your optimizations related problem for you. It's pretty much outrageous to ask that from us. But it's quite normal for bugreporters to feel offended and mistreated when their obviously self-inflicted problems tend to be dismissed, we've grown accustomed to it over the time. I guess we'll have to live with the disrespect we get for free.