When logging in on my AMD64 machine I receive the message: "I've detected a panel already running, and will now exit." I have to dismiss the dialog box by hand. If I do not dismiss it immediately then I have to (sometimes) dismiss it exactly 11 times. Reproducible: Always Steps to Reproduce: 1. Build Gnome on my AMD64 machine 2. Log in Actual Results: As above Expected Results: There is no message like this on any of my IA-32 machines so I assume it's some sort of AMD64 issue. There has been info in the Gentoo forums about people having this problem and more advanced folks than I solving it. Whatever the proper fix is it would be great if it moved to the stable (or even testing) branch one of these days. I couldn't find a similar bug in Bugzilla so I'm submitting this as a bug report, but I'm almost sure a duplicate has to be here somewhere. lightning ~ # emerge info Portage 2.0.51.22-r3 (default-linux/amd64/2005.1, gcc-3.4.4, glibc-2.3.5-r2, 2.6.14-rt13 x86_64) ================================================================= System uname: 2.6.14-rt13 x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.6.13 dev-lang/python: 2.3.5-r2, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.20 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=k8 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=k8 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://mirror.tucdemonic.org/gentoo/ ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo http://mirror.gentoo.gr.jp http://www.zentek-international.com/mirrors/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X alsa apache2 audiofile avi berkdb bitmap-fonts bzip2 cdb cdr crypt cups curl dvd dvdr dvdread eds emboss encode esd exif expat fam ffmpeg flac fluidsynth foomaticdb fortran gif gimp gimpprint glut gnome gpm gstreamer gtk gtk2 i8x0 idn imagemagick imlib ipv6 jack jack-tmpfs java jpeg kde ladspa lcms lirc lzw lzw-tiff mad mjpeg mng mp3 mpeg mysql mythtv ncurses nls nptl nptlonly ogg opengl pam pcre pdflib perl png ppds python qt quicktime radeon readline real sdl sndfile spell ssl tcltk tcpd tiff truetype truetype-fonts type1-fonts udev usb userlocales v4l v4l2 vorbis xine xml2 xpm xscreensaver xv xvid zlib video_cards_radeon userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS lightning ~ # lightning ~ # cat /var/lib/portage/world | grep gnome gnome-base/gconf gnome-base/gnome-applets gnome-base/gnome-light gnome-extra/gcalctool gnome-base/gdm net-analyzer/gnome-netstatus app-text/gnome-spell lightning ~ #
What version of gnome-session? This was fixed in gnome-session-2.10.0-r3 as per bug #98646
I seem to have the proper version installed. Possibly it didn't fix it for AMD64? Should I try the ~x86 version? mark@lightning ~ $ eix gnome-session * gnome-base/gnome-session Available versions: 2.10.0 2.10.0-r3 ~2.12.0 Installed: 2.10.0-r3 Homepage: http://www.gnome.org/ Description: Gnome session manager Found 1 matches mark@lightning ~ $
It definitely fixed it for me on amd64, so it's not an arch issue...
I emerged the newest testing version. Still not fixed. Note that I did not reboot to test. I just logged out. Possibly something was left hanging around in memory? mark@lightning ~ $ eix gnome-session * gnome-base/gnome-session Available versions: 2.10.0 2.10.0-r3 2.12.0 Installed: 2.12.0 Homepage: http://www.gnome.org/ Description: Gnome session manager Found 1 matches mark@lightning ~ $
are you still having this problem? do you save your session when you logout?
I am still having this problem and I do not generally save my setup when I exit. Should I?
Thanks you. I dismissed the dialog and saved my setup once on exit. I then logged in again and did not get the message. Thanks very much.