Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 45050 - GDM 2.4.4.7 will not load kde-3.2.1 - missing .desktop file in /usr/share/xsessions
Summary: GDM 2.4.4.7 will not load kde-3.2.1 - missing .desktop file in /usr/share/xse...
Status: RESOLVED DUPLICATE of bug 40711
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-18 11:31 UTC by Phil Walsh
Modified: 2005-07-17 13:06 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Phil Walsh 2004-03-18 11:31:29 UTC
I can't get GDM 2.4.4.7 to load kde 3.2.1. 

Just after emergeing GDM when I try to log in, it tells me that my default session is kde-3.2.1 and it can't be found. It then loads the failsafe.

After this, GDM defaults to the failsafe. I cannot select kde from the sessions menu in GDM. 

I looked through /etc/X11 and /usr/share/xsessions and there is no .desktop file for kde. I don't know if this is a KDE or GDM bug, but I'm sure if its listed in the wrong place it can be moved :)

Reproducible: Always
Steps to Reproduce:
1. emerge kde3.2.1 - set kde as default session in /etc/rc.conf
2. emerge GDM
3. try to use GDM to start a kde session

Actual Results:  
GDM loads the failsafe session. This is the GNOME failsafe session, not the
failsafe twm session from /etc/X11/Sessions/Xsession

Expected Results:  
GDM should have loaded kde

Gentoo Base System version 1.4.3.13p1
Portage 2.0.50-r1 (default-x86-2004.0, gcc-3.3.2, glibc-2.3.2-r9, 2.6.4-love2)
=================================================================
System uname: 2.6.4-love2 i686 AMD Duron(tm) Processor
Autoconf: sys-devel/autoconf-2.58-r1
Automake: sys-devel/automake-1.8.2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -mcpu=athlon-xp -march=athlon-xp -pipe -msse -mmmx -m3dnow
-mfpmath=sse -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
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/share/config
/var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -mcpu=athlon-xp -march=athlon-xp -pipe -msse -mmmx -m3dnow
-mfpmath=sse -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="http://gentoo.oregonstate.edu
http://distro.ibiblio.org/pub/Linux/distributions/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="3dnow X alsa apm arts avi berkdb crypt cups doc encode esd foomaticdb gdbm
gif gpm gtk gtk2 imlib java jpeg kde libg++ libwww mad mikmod mmx motif mpeg
ncurses nls nptl oggvorbis opengl oss pam pdflib perl png ppds python qt
quicktime readline samba sdl slang spell sse ssl svga tcpd truetype usb x86 xml
xml2 xmms xv zlib"
Comment 1 foser (RETIRED) gentoo-dev 2004-03-18 12:45:47 UTC
kde team ?

*** This bug has been marked as a duplicate of 40711 ***
Comment 2 Andy Wang 2004-07-22 18:46:10 UTC
Why is this resolved as a duplicate of 40711.  40711 is closed, but as far as I can tell this is still not fixed in KDE-3.2.3 ebuilds.  40711 is specifically about a new gdm ebuild version bump.  Doesn't it make sense to reopen this bug and assign it to the KDE folks to get them to update their ebuild to include a .desktop file in the appropriate place?
Comment 3 foser (RETIRED) gentoo-dev 2004-08-08 04:29:36 UTC
they are on CC, this is not our bug anymore & i can't force them to fix it. It has actually nothing todo with gdm. If this is still a problem, file a bug with the kde team they have had plenty of time in advance to get it fixed.
Comment 4 Andy Wang 2004-08-19 23:01:25 UTC
I guess my point was, why wasn't this bug just assigned to the KDE people to begin with?  I'll file a newone against them if it doesn't already exist but I'm sort of surprised this one just didn't get reassigned.