[gentoo-amd64] unsubscribe

[redspot]

On Wed, Nov 5, 2008 at 7:00 PM,  <gentoo-amd64+help@l.g.o> wrote:
> Topics (messages 10055 through 10074):
>
> [gentoo-amd64] mplayerplug-in update bombs
>      10055 - "Mark Haney" <mhaney@××××××××××××.org>
>
> [gentoo-amd64] mplayerplug-in update bombs
>      10056 - Beso <givemesugarr@×××××.com>
>
> [gentoo-amd64] Re: Fwd: [install] emerge gentoo-sources fails
>      10057 - "Martin Herrman" <martin@×××××××.nl>
>
> [gentoo-amd64] Still unable to unmask KDE4.1.2
>      10058 - "Mark Haney" <mhaney@××××××××××××.org>
>
> [gentoo-amd64] Re: Fwd: [install] emerge gentoo-sources fails
>      10059 - Michael Moore <mikem.unet@×××××.com>
>
> [gentoo-amd64] Still unable to unmask KDE4.1.2
>      10060 - Richard Freeman <rich0@g.o>
>
> [gentoo-amd64] Still unable to unmask KDE4.1.2
>      10061 - Barry Schwartz <chemoelectric@×××××××××××××.org>
>
> [gentoo-amd64] Still unable to unmask KDE4.1.2
>      10062 - "Mark Haney" <mhaney@××××××××××××.org>
>
> [gentoo-amd64] Still unable to unmask KDE4.1.2
>      10063 - "Mark Haney" <mhaney@××××××××××××.org>
>
> [gentoo-amd64] Still unable to unmask KDE4.1.2
>      10064 - "Mark Haney" <mhaney@××××××××××××.org>
>
> [gentoo-amd64] Still unable to unmask KDE4.1.2 -- Solved
>      10065 - "Mark Haney" <mhaney@××××××××××××.org>
>
> [gentoo-amd64] KDE 4.1.2 issues
>      10066 - "Mark Haney" <mhaney@××××××××××××.org>
>
> [gentoo-amd64] KDE 4.1.2 issues - updated
>      10067 - "Mark Haney" <mhaney@××××××××××××.org>
>
> [gentoo-amd64] KDE 4.1.2 issues - updated
>      10068 - Beso <givemesugarr@×××××.com>
>
> [gentoo-amd64] KDE 4.1.2 issues - updated
>      10069 - "Till Schwalbe (Gentoo)" <gentoo@×××××××.de>
>
> [gentoo-amd64] KDE 4.1.2 issues - updated
>      10070 - "Mark Haney" <mhaney@××××××××××××.org>
>
> [gentoo-amd64] KDE 4.1.2 issues - updated
>      10071 - "Mark Haney" <mhaney@××××××××××××.org>
>
> [gentoo-amd64] KDE 4.1.2 issues - updated
>      10072 - Beso <givemesugarr@×××××.com>
>
> [gentoo-amd64] Re: KDE 4.1.2 issues - updated
>      10073 - Duncan <1i5t5.duncan@×××.net>
>
> [gentoo-amd64] KDE 4.1.2 issues - updated -- SOLVED
>      10074 - "Mark Haney" <mhaney@××××××××××××.org>
>
>
>
> I just tried to update mplayerplug-in and this is what I get:
>
> configure: Determining mozilla/firefox packages to build against
> checking for MOZPLUG... no
> configure: WARNING: firefox-plugin not found
> checking for MOZPLUG... no
> configure: WARNING: seamonkey-plugin not found
> checking for MOZPLUG... no
> configure: WARNING: xulrunner-plugin not found
> checking for MOZPLUG... no
> configure: WARNING: iceape-plugin not found
> configure: error: Unable to find mozilla or firefox development files
>
>
>
> I've never seen that with previous builds, so I'm not sure how to proceed.  Any ideas?
>
>
> --
> Frustra laborant quotquot se calculationibus fatigant pro inventione quadraturae circuli
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> [phone]
>
> Call (866) ERC-7110 for after hours support
>
> 2008/10/31 Mark Haney <mhaney@××××××××××××.org>:
>> I just tried to update mplayerplug-in and this is what I get:
>>
>> configure: Determining mozilla/firefox packages to build against
>> checking for MOZPLUG... no
>> configure: WARNING: firefox-plugin not found
>> checking for MOZPLUG... no
>> configure: WARNING: seamonkey-plugin not found
>> checking for MOZPLUG... no
>> configure: WARNING: xulrunner-plugin not found
>> checking for MOZPLUG... no
>> configure: WARNING: iceape-plugin not found
>> configure: error: Unable to find mozilla or firefox development files
>>
>>
>>
>> I've never seen that with previous builds, so I'm not sure how to proceed.
>>  Any ideas?
>>
>>
>
>
> install mozilla-firefox and not only mozilla-firefox-bin. then you
> should have both working on a multilib profile. the latest
> mplayerplug-in versions have a multilib profile set by default and
> build for both firefoxes. also you'll need both mplayer-bin and
> mplayer installed.
>
> --
> dott. ing. beso
>
> Hi Michael and Duncan,
>
> you two had send me a reply some time ago, but I didn't had the time
> to reply. Well, here it is :-)
>
> In the mean time my desktop is 'fully' functional, at least I can do
> my usual stuff on it.
>
> Of course I have had some issues that needed to be solved:
> - forgot to include USB HID support in my kernel :-)
> - network-adapter driver is broken is current gentoo sources, so I had
> to take kernel.org's 2.6.27.4
> - radeon driver didn't recognise video-chip (yeah, had to unmask
> radeonhd driver..)
> - wireless card required firmware in /lib/firmware
> - ... lots I already forgot..
> But it could all be solved within minutes or in some cases within a
> small couple of hours!
>
> That takes me to the issues I have experienced with FreeBSD: although
> it looks like a very well-documented (and centralised!) system, I had
> problems understanding e.g. the ports way of installing software. I
> had lot's of errors, which I couldn't solve. I think that Gentoo's
> user-base is much larger, which makes it easier to find solutions and
> bug-reports online. But also the messages shown at e.g. the output of
> emerge help a lot. In FreeBSD I also had trouble to do a full system
> upgrade: what are the command's you should use in what sequence? I had
> that information avaialble for gentoo in minutes.
> Maybe I do not have an objective view, because I know Linux quite well
> and FreeBSD is totally new to me.
>
> Best regards,
>
> Martin
>
> On Tue, Oct 21, 2008 at 4:14 AM, Michael Moore <mikem.unet@×××××.com> wrote:
>> On 19:37 Mon 20 Oct     , Martin Herrman wrote:
>>> I have used slackware, redhat, mandrake and debian before (in that
>>> order) and about 2 years ago switched to Ubuntu because it was so easy
>>> to use. But it's also bloated (it is even hard to compile your own
>>> kernel) and that's why I started to use Gentoo 2 months ago on my
>>> notebook. I liked it (compared to FreeBSD: that ports system is
>>> documented so badly..)!
>>
>> Surprised to hear that, because quite a lot of people (including yours
>> truly) find FreeBSD and Gentoo to be couple of the most well documented
>> systems.
>>
>> So, what was the exact problem you had with the ports documentation?
>>
>> --
>>
>> Regards,
>> Michael Moore <mikem.unet(at)gmail.com>
>> About *NIX: If its not fun, why do it?
>>
>>
>
> Well, after 2 weeks of fumbling and fidgeting, I still am unable to unmask KDE4.1.2.  I really do not know now where to go from this point. Here's what I"ve done.
>
> I've removed all KDE4.0.X packages.
>
> I've keyworded the KDE:4 packages (per the documentation) and I still do not see any KDE4.1.2 packages listed in emerge -upD world.
>
> I thought, at one time that I needed to also unmask the KDE4.1.2 files since I"m not running ~amd64, but that didn't change anything.
>
> I'm at a complete loss for where to go now.
>
> --
> Frustra laborant quotquot se calculationibus fatigant pro inventione quadraturae circuli
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> [phone]
>
> Call (866) ERC-7110 for after hours support
>
> On 19:51 Sun 02 Nov     , Martin Herrman wrote:
>> That takes me to the issues I have experienced with FreeBSD: although
>> it looks like a very well-documented (and centralised!) system, I had
>> problems understanding e.g. the ports way of installing software. I
>> had lot's of errors, which I couldn't solve. I think that Gentoo's
>> user-base is much larger, which makes it easier to find solutions and
>> bug-reports online. But also the messages shown at e.g. the output of
>> emerge help a lot. In FreeBSD I also had trouble to do a full system
>> upgrade: what are the command's you should use in what sequence? I had
>> that information avaialble for gentoo in minutes.
>> Maybe I do not have an objective view, because I know Linux quite well
>> and FreeBSD is totally new to me.
>>
>> Best regards,
>>
>> Martin
>>
> Hi Martin,
>
> In a nutshell you could say that Gentoo Linux has a highly refined
> implementation of the methods of FreeBSD (though at the core they
> are two totally different systems- technically & philosophically).
> It includes an excellent package manager and a lot of well polished
> tools (eselect et al.) which make system administration less of a
> chore and infact a highly easy job (contrary to popular belief).
> This is one of the reasons i love Gentoo Linux -- it provides the
> power without putting you into too much of an inconvenience. But
> that doesn't take anything away from FreeBSD, which has managed to
> still follow the KISS Principle and keep things fairly well integrated.
>
> As regards the emerge output, you would realise that the make output of
> the ports system isn't different. And as for the update just read the
> docs. You would find out that a world update in FreeBSD is quite similar
> to others, provided if you get the knowhow about userland and system.
>
> But, anyways both are quite different systems so, please don't view
> anyone with any kind of prejudice. I am not trying to profess any particular
> system but, you should only criticise something once you are fairly well versed
> with it.
>
> --
>
> Michael Moore <mikem.unet(at)gmail.com>
> About *NIX: If its not fun, why do it?
>
> Mark Haney wrote:
>>
>> Well, after 2 weeks of fumbling and fidgeting, I still am unable to unmask KDE4.1.2.  I really do not know now where to go from this point. Here's what I"ve done.
>>
>> I've removed all KDE4.0.X packages.
>>
>> I've keyworded the KDE:4 packages (per the documentation) and I still do not see any KDE4.1.2 packages listed in emerge -upD world.
>>
>> I thought, at one time that I needed to also unmask the KDE4.1.2 files since I"m not running ~amd64, but that didn't change anything.
>>
>> I'm at a complete loss for where to go now.
>>
>
> Are you using a package manager that supports EAPI 2?  I suspect that this is only supported by portage v2.2 or newer versions of paludis - and the unstable kde ebuilds use EAPI 2 so they would be masked by older versions of either package manager.
>
> Mark Haney <mhaney@××××××××××××.org> skribis:
>> I've keyworded the KDE:4 packages (per the documentation) and I still do
>> not see any KDE4.1.2 packages listed in emerge -upD world.
>
> I haven't looked at the docs lately, or followed this conversation,
> but :4 was changed to :4.1
>
>
> Richard Freeman wrote:
>
>>
>> Are you using a package manager that supports EAPI 2?  I suspect that this is only supported by portage v2.2 or newer versions of paludis - and the unstable kde ebuilds use EAPI 2 so they would be masked by older versions of either package manager.
>>
>
> I was under the impression, especially based on the documentation, that the latest version of portage and associated tools supported that.  I'm using portage 2.1.4.5 and based on what I've read, this should be fine.
>
>
>
> --
> Frustra laborant quotquot se calculationibus fatigant pro inventione quadraturae circuli
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> [phone]
>
> Call (866) ERC-7110 for after hours support
>
> Barry Schwartz wrote:
>>
>> Mark Haney <mhaney@××××××××××××.org> skribis:
>>>
>>> I've keyworded the KDE:4 packages (per the documentation) and I still do not see any KDE4.1.2 packages listed in emerge -upD world.
>>
>> I haven't looked at the docs lately, or followed this conversation,
>> but :4 was changed to :4.1
>>
>>
>
> That may be true, but in the documentation, there's no mention of what to unmask.  There's mention of what to keyword, but not unmask.  I've tried everything I can think of to unmask the files, and nothing has worked.
>
>
>
> --
> Frustra laborant quotquot se calculationibus fatigant pro inventione quadraturae circuli
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> [phone]
>
> Call (866) ERC-7110 for after hours support
>
> Mark Haney wrote:
>>
>> Richard Freeman wrote:
>>
>
>>
>> I was under the impression, especially based on the documentation, that the latest version of portage and associated tools supported that.  I'm using portage 2.1.4.5 and based on what I've read, this should be fine.
>>
>>
>>
>
> You know, that might actually be my problem, somehow portage got downgraded here to 2.1.4.5 instead of 2.2.0_rc11 that I KNOW was on their before.
>
> So, I'm throwing 2.2.0_rc13 on here and we'll see how it goes from there.
>
>
>
> --
> Frustra laborant quotquot se calculationibus fatigant pro inventione quadraturae circuli
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> [phone]
>
> Call (866) ERC-7110 for after hours support
>
> Mark Haney wrote:
>>
>> You know, that might actually be my problem, somehow portage got downgraded here to 2.1.4.5 instead of 2.2.0_rc11 that I KNOW was on their before.
>>
>> So, I'm throwing 2.2.0_rc13 on here and we'll see how it goes from there.
>>
>>
>>
>
>
> Yep, that did it. I can't believe I didn't catch that earlier. I was /certain/ portage was the right version.  Oh well.
>
> Thanks for all the help.
>
>
> --
> Frustra laborant quotquot se calculationibus fatigant pro inventione quadraturae circuli
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> [phone]
>
> Call (866) ERC-7110 for after hours support
>
> Well, I've got kdebase installed (and I must say the new sets are awesome. I love it.) but I'm stumped on a problem.
>
> Instead of the KDE4.1 greeter, I'm getting the generic X Windows greeter login screen. I've checked /etc/conf.d/xdm and it says 'DISPLAYMANAGER=kde-4.1', and I've changed /etc/rc.conf to be kde-4.1, but still I get the X login.
>
> What am I missing?
>
>
>
> --
> Frustra laborant quotquot se calculationibus fatigant pro inventione quadraturae circuli
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> [phone]
>
> Call (866) ERC-7110 for after hours support
>
> Well, I've got kdebase installed (and I must say the new sets are
> awesome. I love it.) but I'm stumped on a problem.
>
> Instead of the KDE4.1 greeter, I'm getting the generic X Windows greeter
> login screen. I've checked /etc/conf.d/xdm and it says
> 'DISPLAYMANAGER=kde-4.1', and I've changed /etc/rc.conf to be kde-4.1,
> but still I get the X login.
>
> What am I missing?
>
>
> One other thing, when I logged back in to KDE4, I lost all my desktop settings.  Is this supposed to happen?  I've set /etc/make.conf for 'kdeprefix' so I thought I would keep most of my desktop customizations.  They weren't real complex changes, just setting up a quick link on the task bar for Konsole and such.
>
>
>
>
> --
> Frustra laborant quotquot se calculationibus fatigant pro inventione
> quadraturae circuli
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> [phone]
>
> Call (866) ERC-7110 for after hours support
>
>
> 2008/11/4 Mark Haney <mhaney@××××××××××××.org>:
>> Well, I've got kdebase installed (and I must say the new sets are
>> awesome. I love it.) but I'm stumped on a problem.
>>
>> Instead of the KDE4.1 greeter, I'm getting the generic X Windows greeter
>> login screen. I've checked /etc/conf.d/xdm and it says
>> 'DISPLAYMANAGER=kde-4.1', and I've changed /etc/rc.conf to be kde-4.1,
>> but still I get the X login.
>>
>> What am I missing?
>>
>>
>> One other thing, when I logged back in to KDE4, I lost all my desktop
>> settings.  Is this supposed to happen?  I've set /etc/make.conf for
>> 'kdeprefix' so I thought I would keep most of my desktop customizations.
>>  They weren't real complex changes, just setting up a quick link on the task
>> bar for Konsole and such.
>>
> usually that stuff isn't necessary. the kdebase-startkde package
> installs the right scripts. so that you don't need kde-4.1 as
> displaymanager. try using just kdm or kde instead of kde-4.1. also
> having a look inside the qlist kdebase-startkde files might be of help
> on how to set right the displaymanager.
>
> --
> dott. ing. beso
>
> Hi Mark,
>
> Am Dienstag, 4. November 2008 14:16:25 schrieb Mark Haney:
>> Well, I've got kdebase installed (and I must say the new sets are
>> awesome. I love it.) but I'm stumped on a problem.
>>
>> Instead of the KDE4.1 greeter, I'm getting the generic X Windows greeter
>> login screen. I've checked /etc/conf.d/xdm and it says
>> 'DISPLAYMANAGER=kde-4.1', and I've changed /etc/rc.conf to be kde-4.1,
>> but still I get the X login.
>>
>> What am I missing?
>
> A few days ago I had the same problem. Then I changed the entries in both
> rc.conf and conf.d/xdm to "kdm" without any extension, and now it works.
>
> Maybe the "4.1" is only functional if one sets the kdeprefix useflag.
>
> HTH.
>
> Have a nice day.
> Till
>
> Till Schwalbe (Gentoo) wrote:
>>
>> Hi Mark,
>>
>> Am Dienstag, 4. November 2008 14:16:25 schrieb Mark Haney:
>>>
>>> Well, I've got kdebase installed (and I must say the new sets are
>>> awesome. I love it.) but I'm stumped on a problem.
>>>
>>> Instead of the KDE4.1 greeter, I'm getting the generic X Windows greeter
>>> login screen. I've checked /etc/conf.d/xdm and it says
>>> 'DISPLAYMANAGER=kde-4.1', and I've changed /etc/rc.conf to be kde-4.1,
>>> but still I get the X login.
>>>
>>> What am I missing?
>>
>> A few days ago I had the same problem. Then I changed the entries in both rc.conf and conf.d/xdm to "kdm" without any extension, and now it works.
>>
>> Maybe the "4.1" is only functional if one sets the kdeprefix useflag.
>>
>> HTH.
>>
>> Have a nice day.
>> Till
>>
>
> Well, maybe, but I can say it doesn't work in this case, as I use the kdeprefix flag.
>
>
>
> --
> Frustra laborant quotquot se calculationibus fatigant pro inventione quadraturae circuli
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> [phone]
>
> Call (866) ERC-7110 for after hours support
>
> Beso wrote:
>
>>>
>> usually that stuff isn't necessary. the kdebase-startkde package
>> installs the right scripts. so that you don't need kde-4.1 as
>> displaymanager. try using just kdm or kde instead of kde-4.1. also
>> having a look inside the qlist kdebase-startkde files might be of help
>> on how to set right the displaymanager.
>>
>
> Well, I took a look with qlist and this is what's in there:
>
> octavian kdebase-startkde-4.1.2-r1 # qlist kdebase-startkde
> /usr/kde/3.5/bin/startkde
> /usr/kde/3.5/env/agent-startup.sh
> /usr/kde/3.5/env/xdg.sh
> /usr/kde/3.5/shutdown/agent-shutdown.sh
> /usr/share/xsessions/kde-3.5.desktop
> /etc/X11/Sessions/kde-3.5
> /usr/share/doc/kde/kdebase-startkde-4.1.2-r1/README.bz2
> /usr/share/xsessions/KDE-4.desktop
> /usr/bin/startkde
> /usr/bin/safestartkde
> /etc/kde/startup/agent-startup.sh
> /etc/kde/startup/xdg.sh
> /etc/kde/shutdown/agent-shutdown.sh
> /etc/X11/Sessions/kde-4.1
>
>
> So, based on this, I don't see a KDM listed, but I do see a kde-4.1 in /etc/X11/Sessions/
>
> Still not sure where this leaves me though.
>
>
> --
> Frustra laborant quotquot se calculationibus fatigant pro inventione quadraturae circuli
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> [phone]
>
> Call (866) ERC-7110 for after hours support
>
> 2008/11/4 Mark Haney <mhaney@××××××××××××.org>:
>> Beso wrote:
>>
>>>>
>>> usually that stuff isn't necessary. the kdebase-startkde package
>>> installs the right scripts. so that you don't need kde-4.1 as
>>> displaymanager. try using just kdm or kde instead of kde-4.1. also
>>> having a look inside the qlist kdebase-startkde files might be of help
>>> on how to set right the displaymanager.
>>>
>>
>> Well, I took a look with qlist and this is what's in there:
>>
>> octavian kdebase-startkde-4.1.2-r1 # qlist kdebase-startkde
>> /usr/kde/3.5/bin/startkde
>> /usr/kde/3.5/env/agent-startup.sh
>> /usr/kde/3.5/env/xdg.sh
>> /usr/kde/3.5/shutdown/agent-shutdown.sh
>> /usr/share/xsessions/kde-3.5.desktop
>> /etc/X11/Sessions/kde-3.5
>> /usr/share/doc/kde/kdebase-startkde-4.1.2-r1/README.bz2
>> /usr/share/xsessions/KDE-4.desktop
>> /usr/bin/startkde
>> /usr/bin/safestartkde
>> /etc/kde/startup/agent-startup.sh
>> /etc/kde/startup/xdg.sh
>> /etc/kde/shutdown/agent-shutdown.sh
>> /etc/X11/Sessions/kde-4.1
>>
>>
>> So, based on this, I don't see a KDM listed, but I do see a kde-4.1 in
>> /etc/X11/Sessions/
>>
>> Still not sure where this leaves me though.
>>
>>
>> --
>> Frustra laborant quotquot se calculationibus fatigant pro inventione
>> quadraturae circuli
>>
>> Mark Haney
>> Sr. Systems Administrator
>> ERC Broadband
>> [phone]
>>
>> Call (866) ERC-7110 for after hours support
>>
>>
>
> as displaymanager i have just 4.0 (i should correct it to the newer
> one but it seems that for me it automatically detects changes).
> usually this shouldn't be necessary as the new /etc/init.d/xdm file
> should already point to the right location (i have different voices
> for kde3.5 kde4 and gnome that go and see the kdm in the {MY_KDE}
> directory under /usr/kde/. so if you have a look at that the
> DISPLAYMANAGER should point just to the right dir. if you have
> /usr/kde/4.1 point it to 4.1. also you should remember to install the
> kdebase-startkde-4.1.2 package or you won't be able to select that
> session.
>
> --
> dott. ing. beso
>
> Beso <givemesugarr@×××××.com> posted
> d257c3560811041417h16cfc3bby1eed7cb0e4b002ef@××××××××××.com, excerpted
> below, on  Tue, 04 Nov 2008 22:17:09 +0000:
>
>>> So, based on this, I don't see a KDM listed, but I do see a kde-4.1 in
>>> /etc/X11/Sessions/
>
> FWIW, I don't use a *dm at all.  I boot to a virtual terminal in text
> mode, login there, and start X/KDE from there.  The /etc/X11/Sessions/*
> entries are for doing that.  You set and export XSESSION=<name>, where
> <name> is the name of one of those files, run startx, and it should do
> just that (start X), with the appropriate environment based on whichever
> one you set/exported, logged in as the user you ran startx as.  Note that
> formerly the XSESSION variable was set system-wide in some rc file, IDR
> which but something like /etc/conf.d/rc or some such, but at least with
> baselayout-2 and openrc, that's no longer the case.  Individual logins
> could always overrule it; now they set it, period, in their bashrc or
> individual scripts they create or whatever.
>
> Of course the KDE X11/Sessions files don't do much, only call startkde
> (of the appropriate version) at the appropriate time as X starts.  It's
> the startkde scripts that do the real work.
>
> But since I've customized the locations of a number of files, due to
> running /tmp on tmpfs and /var/tmp as a symlink pointed at it, plus
> customized the menu and etc for both kde3 and kde4, I have customized KDE
> start scripts as well.  These set various critical variables to point
> stuff at my customized locations, do a few more symlinks beyond what
> startkde does to keep the kde3 and kde4 user configs from stepping on
> each other, etc.
>
> But the point is, no dm is necessary.  KDE (or other environments as
> merged) can be started from the console login, provided (1) XSESSION is
> set correctly, and (2) the appropriate start scripts, for kde, the
> startkde package, is merged.  I have both the 3.5.10-r4 and 4.1.2-r1
> versions of kdebase-startkde merged, and can start either one from my
> virtual terminal login.
>
>> as displaymanager i have just 4.0 (i should correct it to the newer one
>> but it seems that for me it automatically detects changes). usually this
>> shouldn't be necessary as the new /etc/init.d/xdm file should already
>> point to the right location (i have different voices for kde3.5 kde4 and
>> gnome that go and see the kdm in the {MY_KDE} directory under /usr/kde/.
>> so if you have a look at that the DISPLAYMANAGER should point just to
>> the right dir. if you have /usr/kde/4.1 point it to 4.1. also you should
>> remember to install the kdebase-startkde-4.1.2 package or you won't be
>> able to select that session.
>
> Now, if you are running a display manager, with a graphical login, then
> the above applies.  However, it's not necessary, and I long ago (2003-
> ish, Mandrake 8.x) quit doing so, after Mandrake broke their DM login in
> whatever cooker version I was running at the time.  IIRC I had already
> been running KDE from text mode part of the time (having decided before
> that that I preferred KDE to GNOME or whatever), but after that, I got in
> the habit of doing it all the time, and I've never used whatever *DM at
> all on Gentoo, and haven't even had one merged since Gentoo/KDE started
> the split packages thing.  I just prefer logging in in text mode, I
> guess, and running X/KDE like I would any other application, from there.
>
> --
> Duncan - List replies preferred.   No HTML msgs.
> "Every nonfree program has a lord, a master --
> and if you use the program, he is your master."  Richard Stallman
>
>
> Beso wrote:
>
>>
>> as displaymanager i have just 4.0 (i should correct it to the newer
>> one but it seems that for me it automatically detects changes).
>> usually this shouldn't be necessary as the new /etc/init.d/xdm file
>> should already point to the right location (i have different voices
>> for kde3.5 kde4 and gnome that go and see the kdm in the {MY_KDE}
>> directory under /usr/kde/. so if you have a look at that the
>> DISPLAYMANAGER should point just to the right dir. if you have
>> /usr/kde/4.1 point it to 4.1. also you should remember to install the
>> kdebase-startkde-4.1.2 package or you won't be able to select that
>> session.
>>
>
> Interesatingly enough the fix was rather simple.  In /etc/conf.d/xdm, I changed 'kde-4.1' to 'kdm' and voila, problem solved.
>
>
> --
> Frustra laborant quotquot se calculationibus fatigant pro inventione quadraturae circuli
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> [phone]
>
> Call (866) ERC-7110 for after hours support
>
>