SEO

#1 (**permalink**) 02-21-2008, 10:06 AM

I just emerged and installed kde as per the instructions on the
gentoo website.

I tried adding hal,dbus, and ivman. They all emerged but hal wouldn't
install via rc-update. (couldn't be found error)

I setup kdm as per the instructions.
I can only login as root. If I try to login using a user account
kdm starup stalls at either the 'system' or 'perphials' stage,
times out, and leaves me with a blank pale blue screen.
(I can ctrl-alt-bs to restart kdm).

Any ideas? If kde leaves a log file someplace, (i don't know where)
I can post it here.

Thanks.

#2 (**permalink**) 02-21-2008, 10:06 AM

ken wrote:
> I tried adding hal,dbus, and ivman. They all emerged but hal wouldn't
> install via rc-update. (couldn't be found error)

Look in /etc/init.d/ - it's hald rather than hal ("d" for "daemon",
probably). You can also run "rc-update show" to see the settings.

> I setup kdm as per the instructions.
> I can only login as root. If I try to login using a user account
> kdm starup stalls at either the 'system' or 'perphials' stage,
> times out, and leaves me with a blank pale blue screen.

This sounds very similar to
http://groups-beta.google.com/group/...a29f4e6bb9ec05

Try renaming your ~/.dmrc file.

#3 (**permalink**) 02-21-2008, 10:06 AM

Paul Bredbury wrote:

> ken wrote:
>> I tried adding hal,dbus, and ivman. They all emerged but hal wouldn't
>> install via rc-update. (couldn't be found error)
>
> Look in /etc/init.d/ - it's hald rather than hal ("d" for "daemon",
> probably). You can also run "rc-update show" to see the settings.
>
>> I setup kdm as per the instructions.
>> I can only login as root. If I try to login using a user account
>> kdm starup stalls at either the 'system' or 'perphials' stage,
>> times out, and leaves me with a blank pale blue screen.
>
> This sounds very similar to
>
http://groups-beta.google.com/group/...a29f4e6bb9ec05
>
> Try renaming your ~/.dmrc file.
I found a fix. I killed kdm and setup my ~/.xinitrc
to exec startkde since someone else said this allowed
him to start kde as a user.

Well it didn't help me except that when I
<crtl><alt><bs>'ed to kill my
stillborn kde session I got to see the error dump.
It was complaining about not being able to open /dev/null
Come to think of it, I got the same error when I log in
via command line as a user from the 'born' shell. So I
did a 'chmod a+rw /dev/null' and now it works.
But why? Is the /dev/null device entry supposed to be
world read/write?
After making this change I can now start kde as a user.
Comments?

#4 (**permalink**) 02-21-2008, 10:06 AM

Paul Bredbury wrote:

> ken wrote:
>> I tried adding hal,dbus, and ivman. They all emerged but hal wouldn't
>> install via rc-update. (couldn't be found error)
>
> Look in /etc/init.d/ - it's hald rather than hal ("d" for "daemon",
> probably). You can also run "rc-update show" to see the settings.
>
>> I setup kdm as per the instructions.
>> I can only login as root. If I try to login using a user account
>> kdm starup stalls at either the 'system' or 'perphials' stage,
>> times out, and leaves me with a blank pale blue screen.
>
> This sounds very similar to
>
http://groups-beta.google.com/group/...a29f4e6bb9ec05
>
> Try renaming your ~/.dmrc file.

Follow up to my last post
The fix of 'chmod a+rwx /dev/null' doesn't work since
udev is dynamic and the change goes away after rebooting.
I guess I need to put that line in an rc file someplace so
it happens automagicly (or log in as root on the cmd line
and do it by hand ... which does work!)

Ideas?

#5 (**permalink**) 02-21-2008, 10:06 AM

ken wrote:

> The fix of 'chmod a+rwx /dev/null'

First, don't make it executable, since that makes no sense.

> doesn't work since udev is dynamic and the change goes away after
> rebooting. I guess I need to put that line in an rc file someplace so
> it happens automagicly (or log in as root on the cmd line and do it
> by hand ... which does work!)
>
> Ideas?

You need to find out why your udev is broken. You should have a file
named /etc/udev/rules.d/50-udev.rules, and it should contain a line like
this:

KERNEL="null", NAME="%k", MODE="0666"

If it does have that, you need to find out what else might be messing
with it. It's definitely not a solution to have to manually fix
something at every boot!

--
PeKaJe

There's no saint like a reformed sinner.

#6 (**permalink**) 02-21-2008, 10:06 AM

ken wrote:

> Paul Bredbury wrote:
>
>> ken wrote:
>>> I tried adding hal,dbus, and ivman. They all emerged but hal wouldn't
>>> install via rc-update. (couldn't be found error)
>>
>> Look in /etc/init.d/ - it's hald rather than hal ("d" for "daemon",
>> probably). You can also run "rc-update show" to see the settings.
>>
>>> I setup kdm as per the instructions.
>>> I can only login as root. If I try to login using a user account
>>> kdm starup stalls at either the 'system' or 'perphials' stage,
>>> times out, and leaves me with a blank pale blue screen.
>>
>> This sounds very similar to
>>
>
http://groups-beta.google.com/group/...a29f4e6bb9ec05
>>
>> Try renaming your ~/.dmrc file.
>
>
> Follow up to my last post
> The fix of 'chmod a+rwx /dev/null' doesn't work since
> udev is dynamic and the change goes away after rebooting.
> I guess I need to put that line in an rc file someplace so
> it happens automagicly

I found that the Gentoo udev config sets /dev/null correctly, check

| /etc/udev/rules.d/50-udev.rules

for the line

| KERNEL="null", NAME="%k", MODE="0666"

But the Gentoo device-tarball thing somehow messes it up. Deactivating it
solved the issue for me

| /etc/conf.d/rc, :
| RC_DEVICE_TARBALL="no"

I hope that helps, however, YMMV, don't blame me if you're left with an
unbootable system, follow this advice at your own risk, no guarantees
expressed or implied given (this waiver void where prohibited), etc.

Anno.

#7 (**permalink**) 02-21-2008, 10:06 AM

ken wrote:

> Paul Bredbury wrote:
>
>> ken wrote:
>>> I tried adding hal,dbus, and ivman. They all emerged but hal wouldn't
>>> install via rc-update. (couldn't be found error)
>>
>> Look in /etc/init.d/ - it's hald rather than hal ("d" for "daemon",
>> probably). You can also run "rc-update show" to see the settings.
>>
>>> I setup kdm as per the instructions.
>>> I can only login as root. If I try to login using a user account
>>> kdm starup stalls at either the 'system' or 'perphials' stage,
>>> times out, and leaves me with a blank pale blue screen.
>>
>> This sounds very similar to
>>
>
http://groups-beta.google.com/group/...a29f4e6bb9ec05
>>
>> Try renaming your ~/.dmrc file.
> I found a fix. I killed kdm and setup my ~/.xinitrc
> to exec startkde since someone else said this allowed
> him to start kde as a user.
>
> Well it didn't help me except that when I
> <crtl><alt><bs>'ed to kill my
> stillborn kde session I got to see the error dump.
> It was complaining about not being able to open /dev/null
> Come to think of it, I got the same error when I log in
> via command line as a user from the 'born' shell. So I
> did a 'chmod a+rw /dev/null' and now it works.
> But why? Is the /dev/null device entry supposed to be
> world read/write?
> After making this change I can now start kde as a user.
> Comments?

More problems. After getting users to be able to log in
by fixing the /dev/null issue I see as a user I can't
open a Konsole (xterm) and get a bash prompt. I can
as root! What now?

#8 (**permalink**) 02-21-2008, 10:06 AM

Anno v. Heimburg wrote:

> ken wrote:
>
>> Paul Bredbury wrote:
>>
>>> ken wrote:
>>>> I tried adding hal,dbus, and ivman. They all emerged but hal wouldn't
>>>> install via rc-update. (couldn't be found error)
>>>
>>> Look in /etc/init.d/ - it's hald rather than hal ("d" for "daemon",
>>> probably). You can also run "rc-update show" to see the settings.
>>>
>>>> I setup kdm as per the instructions.
>>>> I can only login as root. If I try to login using a user account
>>>> kdm starup stalls at either the 'system' or 'perphials' stage,
>>>> times out, and leaves me with a blank pale blue screen.
>>>
>>> This sounds very similar to
>>>
>>
>
http://groups-beta.google.com/group/...a29f4e6bb9ec05
>>>
>>> Try renaming your ~/.dmrc file.
>>
>>
>> Follow up to my last post
>> The fix of 'chmod a+rwx /dev/null' doesn't work since
>> udev is dynamic and the change goes away after rebooting.
>> I guess I need to put that line in an rc file someplace so
>> it happens automagicly
>
> I found that the Gentoo udev config sets /dev/null correctly, check
>
> | /etc/udev/rules.d/50-udev.rules
>
> for the line
>
> | KERNEL="null", NAME="%k", MODE="0666"

The above line was missing. I added it.

>
> But the Gentoo device-tarball thing somehow messes it up. Deactivating it
> solved the issue for me
>
> | /etc/conf.d/rc, :
> | RC_DEVICE_TARBALL="no"
>
This line was already there.

Made the above change and removed my hack to do a chmod in xdm.
HOWEVER I still can't start an xterm (konsole) session and get
a bash prompt as a user. Works fine as root. UGG!
Any ideas?
Thanks for the /dev/null fix.

#9 (**permalink**) 02-21-2008, 10:07 AM

ken wrote:
> HOWEVER I still can't start an xterm (konsole) session and get
> a bash prompt as a user. Works fine as root. UGG!

Maybe a problem with /dev/pty. You should have the following in
/etc/udev/rules.d/50-udev.rules

# pty devices
KERNEL="ptmx", NAME="%k", GROUP="tty", MODE="0666"
KERNEL="pty[p-za-e][0-9a-f]*", NAME="pty/m%n", SYMLINK="%k", GROUP="tty"
KERNEL="tty[p-za-e][0-9a-f]*", NAME="pty/s%n", SYMLINK="%k", GROUP="tty"

Given your previous problem with udev, try "emerge udev" and see if it
fixes this file for you after an "etc-update" and reboot.

#10 (**permalink**) 02-21-2008, 10:08 AM

Paul Bredbury wrote:

> ken wrote:
>> HOWEVER I still can't start an xterm (konsole) session and get
>> a bash prompt as a user. Works fine as root. UGG!
>
> Maybe a problem with /dev/pty. You should have the following in
> /etc/udev/rules.d/50-udev.rules
>
> # pty devices
> KERNEL="ptmx", NAME="%k", GROUP="tty", MODE="0666"
> KERNEL="pty[p-za-e][0-9a-f]*", NAME="pty/m%n", SYMLINK="%k", GROUP="tty"
> KERNEL="tty[p-za-e][0-9a-f]*", NAME="pty/s%n", SYMLINK="%k", GROUP="tty"
>
> Given your previous problem with udev, try "emerge udev" and see if it
> fixes this file for you after an "etc-update" and reboot.
Actually there were some config issues with udev that etc-update fixed.
Probably with the above file, which included the fix for the /dev/null
problem.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Can only login to kde as root