[gentoo-user] kconsole lost PTYs

[gentoo-user] kconsole lost PTYs

[James]

Hello,

Strange occurance this one. Booted up a laptop (kde) and got these error
messages, one for each terminal session:

" Kconsole is unable to open a PTY (pseudo teletype). It is likely that this
is due to an incorrect configuration of the PTY devices. Kconsole needs to
have read/write access to the PTY devices."

Upon acknowledgement of each error (popUP) my kconsole sessions disappeared....
I can ssh into the system to fix the problem, but, I'm not sure what would
have changed?

Any ideas on this one? Why did it show up now? I have recently upgraded 
xorg and migrated KDE from monolithic to kde-meta. But all worked fine
following these upgrades.


James

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: kconsole lost PTYs

[James]

James <wireless <at> tampabay.rr.com> writes:

More Info on this problem:

> " Kconsole is unable to open a PTY (pseudo teletype). It is likely that this
> is due to an incorrect configuration of the PTY devices. Kconsole needs to
> have read/write access to the PTY devices."

Well I found a temporary work around, but it does not solve
the problem.

When the system boots and gives me the kdm login screen, I have to
first ssh remotely and run these commands

chown root:tty /dev/pty*
chown root:tty /dev/tty*
chmod 666 /dev/null

I'd sure like to know what to remerge to fix this problem.
hal ? udev ?

/dev/null has been complaining for weeks, but I just ignored it.
It started complaining about the time I had problems with xrdb:

 x11-apps/xrdb
     Available versions:  ~1.0.1 ~1.0.2
     Installed:           none


NOW I cannot ignore this problem anymore.

idea?


James

James





-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: kconsole lost PTYs

[Willie Wong]

On Wed, Jun 28, 2006 at 12:57:30AM +0000, Penguin Lover James squawked:
> Well I found a temporary work around, but it does not solve
> the problem.
> 
> When the system boots and gives me the kdm login screen, I have to
> first ssh remotely and run these commands
> 
> chown root:tty /dev/pty*
> chown root:tty /dev/tty*
> chmod 666 /dev/null
> 
> I'd sure like to know what to remerge to fix this problem.
> hal ? udev ?
> 

If you are running udev, check
  /etc/udev/permissions.d/50-udev.permissions

it should have lines like 
  tty:root:tty:0666
  tty[0-9]*:root:tty:0660
and
  null:root:root:0666
  zero:root:root:0666

W
-- 
Will will will unless Will wills willingly. Maybe Willow
   ~tiredwired. Sunday Oct. 6. 6:00pm
Sortir en Pantoufles: up 18 days,  3:10
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: kconsole lost PTYs

[James]

Willie Wong <wwong <at> Princeton.EDU> writes:


> On Wed, Jun 28, 2006 at 12:57:30AM +0000, Penguin Lover James squawked:
> > Well I found a temporary work around, but it does not solve
> > the problem.

> > chown root:tty /dev/pty*
> > chown root:tty /dev/tty*
> > chmod 666 /dev/null

> > I'd sure like to know what to remerge to fix this problem.
> > hal ? udev ?


> If you are running udev, check
>   /etc/udev/permissions.d/50-udev.permissions

> it should have lines like 
>   tty:root:tty:0666
>   tty[0-9]*:root:tty:0660
> and
>   null:root:root:0666
>   zero:root:root:0666

Well I put udev in my /etc/portage/package.keyworks to get the latest
version, thinking that might fix the problem. It do not.



# egrep tty 50-udev.rules <shows these lines>

KERNEL=="pty[pqrstuvwxyzabcdef][0123456789abcdef]", NAME="%k", GROUP="tty",    
OPTIONS="last_rule"
KERNEL=="tty[pqrstuvwxyzabcdef][0123456789abcdef]", NAME="%k", GROUP="tty",    
OPTIONS="last_rule"
KERNEL=="vcs*",                 NAME="%k", GROUP="tty",                
OPTIONS="last_rule"
KERNEL=="vcsa*",                NAME="%k", GROUP="tty",                
OPTIONS="last_rule"
KERNEL=="tty",                  NAME="%k", GROUP="tty", MODE="0666",   
OPTIONS="last_rule"
KERNEL=="tty[0-9]",             NAME="%k", GROUP="tty",                
OPTIONS="last_rule"
KERNEL=="tty[0-9][0-9]",        NAME="%k", GROUP="tty",                
OPTIONS="last_rule"
KERNEL=="console",              NAME="%k", GROUP="tty", MODE="0600"
KERNEL=="ptmx",                 NAME="%k", GROUP="tty", MODE="0666"
# tty devices
KERNEL=="ttyS[0-9]*",   NAME="%k", SYMLINK="tts/%n", GROUP="tty"
KERNEL=="ttyUSB[0-9]*", NAME="%k", SYMLINK="tts/USB%n", GROUP="tty", MODE="0660"
KERNEL=="ippp0",        NAME="%k", GROUP="tty"
KERNEL=="isdn*"         NAME="%k", GROUP="tty"
KERNEL=="dcbri*",       NAME="%k", GROUP="tty"
KERNEL=="ircomm*",      NAME="%k", GROUP="tty"
# alias pnp:dPNP0510 irtty-sir
# alias pnp:dPNP0511 irtty-sir


Likewise:

# egrep null 50-udev.rules
KERNEL=="null",         NAME="%k", MODE="0666"


Want to suggest specific changes to which lines?

It looks as though the (mode) permissions and groups are getting
set per the udev files?

James



-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: kconsole lost PTYs

[Willie Wong]

On Wed, Jun 28, 2006 at 03:04:55AM +0000, Penguin Lover James squawked:
> Well I put udev in my /etc/portage/package.keyworks to get the latest
> version, thinking that might fix the problem. It do not.

I don't think that's necessary. It works perfectly fine on my system
with udev-087. 

Could something else be setting the MODE/GROUP lines for those
devices? How'bout grepping for tty and null in other rule files?

What about /etc/conf.d/rc? Maybe you can toggle RC_DEVICES="udev" and
set RC_DEVICE_TARBALL="no"? (or maybe setting it to "yes" might give
you a work around?)
> 
> 
> 
> # egrep tty 50-udev.rules <shows these lines>
> 
<snip> 
> 
> Want to suggest specific changes to which lines?

The lines look the same as mine. Assuming you've been deligent about
updating the config files in /etc, I don't see a reason why the
default rule files provide by udev would be different. 

> It looks as though the (mode) permissions and groups are getting
> set per the udev files?

Are they? I thought your problem is that the permissions and groups
were set different from what was specified in the rule files...

Best, 

W
-- 
  Two people turned in problem set 12 without indicating their names!
  This is true scholarship, done for it's own sake and not for
 material advantage, like a grade.
  It is an honor to be associated with such nobility of soul.
       ~Prof. Kirk T. McDonald, DeathEM'03 
Sortir en Pantoufles: up 18 days,  6:34
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: kconsole lost PTYs

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 731 bytes --]

On Wed, 28 Jun 2006 00:57:30 +0000 (UTC), James wrote:

> When the system boots and gives me the kdm login screen, I have to
> first ssh remotely and run these commands
> 
> chown root:tty /dev/pty*
> chown root:tty /dev/tty*
> chmod 666 /dev/null
> 
> I'd sure like to know what to remerge to fix this problem.
> hal ? udev ?

It sounds like your udev rules are screwed. My defaults are

KERNEL=="pty[pqrstuvwxyzabcdef][0123456789abcdef]",NAME="%k", GROUP="tty",OPTIONS="last_rule"
KERNEL=="null",NAME="%k", MODE="0666"

Re-emerging udev should fix this, let etc-update/dispatch-conf replace
/etc/udev/rules.d/50-udev.rules.


-- 
Neil Bothwick

"You want us to do WHAT?" - Ancient Chinese wall engineer.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-user] Re: kconsole lost PTYs

[James]

Willie Wong <wwong <at> Princeton.EDU> writes:


> On Wed, Jun 28, 2006 at 03:04:55AM +0000, Penguin Lover James squawked:
> > Well I put udev in my /etc/portage/package.keyworks to get the latest
> > version, thinking that might fix the problem. It do not.

> I don't think that's necessary. It works perfectly fine on my system
> with udev-087. 

Agreed. Since it did not fix the problem, I remerged udev-087-r1.

> Could something else be setting the MODE/GROUP lines for those
> devices? How'bout grepping for tty and null in other rule files?

Good question. Nothing I have intentionally done.
None of the other rules files in /etc/udev/rules.d contain any string
matches as you suggest, except those listed in the previous resonse,
found in 50-udev.rules.



> What about /etc/conf.d/rc? Maybe you can toggle RC_DEVICES="udev" and
> set RC_DEVICE_TARBALL="no"? (or maybe setting it to "yes" might give
> you a work around?)

Here's what I found:
RC_DEVICES="auto"
RC_DEVICE_TARBALL="no"

I'm going to play around with these and test; results to follow.

> > # egrep tty 50-udev.rules <shows these lines>

> The lines look the same as mine. Assuming you've been deligent about
> updating the config files in /etc, I don't see a reason why the
> default rule files provide by udev would be different. 

yes, I rsync emerge and update regularly (daily) almost.

> > It looks as though the (mode) permissions and groups are getting
> > set per the udev files?

> Are they? I thought your problem is that the permissions and groups
> were set different from what was specified in the rule files...

It was a rethorical question. I should have stated:
It looks as though the (mode) permissions and groups are not
getting set per the udev files, or did I miss something?

James




James



-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: kconsole lost PTYs

[James]

Neil Bothwick <neil <at> digimed.co.uk> writes:


> > chown root:tty /dev/pty*
> > chown root:tty /dev/tty*
> > chmod 666 /dev/null


> It sounds like your udev rules are screwed. My defaults are

KERNEL=="pty[pqrstuvwxyzabcdef][0123456789abcdef]",NAME="%k",
GROUP="tty",OPTIONS="last_rule"
KERNEL=="null",NAME="%k", MODE="0666"

> Re-emerging udev should fix this, let etc-update/dispatch-conf replace
> /etc/udev/rules.d/50-udev.rules.

OK, I reverted (re emerged) udev-087-r1

Now my rules look like this:

# egrep tty 50-udev.rules 

KERNEL=="pty[pqrstuvwxyzabcdef][0123456789abcdef]", NAME="%k", GROUP="tty",    
  OPTIONS="last_rule"
KERNEL=="tty[pqrstuvwxyzabcdef][0123456789abcdef]", NAME="%k", GROUP="tty",    
  OPTIONS="last_rule"
KERNEL=="vcs*",                 NAME="%k", GROUP="tty",                
OPTIONS="last_rule"
KERNEL=="vcsa*",                NAME="%k", GROUP="tty",                
OPTIONS="last_rule"
KERNEL=="tty",                  NAME="%k", GROUP="tty", MODE="0666",   
OPTIONS="last_rule"
KERNEL=="tty[0-9]",             NAME="%k", GROUP="tty",                
OPTIONS="last_rule"
KERNEL=="tty[0-9][0-9]",        NAME="%k", GROUP="tty",                
OPTIONS="last_rule"
KERNEL=="console",              NAME="%k", GROUP="tty", MODE="0600"
KERNEL=="ptmx",                 NAME="%k", GROUP="tty", MODE="0666"
# tty devices
KERNEL=="ttyS[0-9]*",   NAME="%k", SYMLINK="tts/%n", GROUP="tty"
KERNEL=="ttyUSB[0-9]*", NAME="%k", SYMLINK="tts/USB%n", GROUP="tty", MODE="0660"
KERNEL=="ippp0",        NAME="%k", GROUP="tty"
KERNEL=="isdn*"         NAME="%k", GROUP="tty"
KERNEL=="dcbri*",       NAME="%k", GROUP="tty"
KERNEL=="ircomm*",      NAME="%k", GROUP="tty"

# egrep null 50-udev.rules
KERNEL=="null",         NAME="%k", MODE="0666"

Why is /dev/null getting repeatedly set to more restrictive
permission than 666?

Which ruled do I edit? Explicit suggestions are most welcome.
And educate me as to why this portable has this issue, and
the other workstations do not?

Udev seems to be a 'moving target' as much of what I've read seems
dated, so any  current documents to reference would be appreciated.
The man pages are short on examples....i.e. I cannot find
/etc/udev/rules.d/udev.examples....

http://gentoo-wiki.com/UDEV   definately needs more detail....


James




-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: kconsole lost PTYs

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 376 bytes --]

On Wed, 28 Jun 2006 13:57:28 +0000 (UTC), James wrote:

> # egrep null 50-udev.rules
> KERNEL=="null",         NAME="%k", MODE="0666"
> 
> Why is /dev/null getting repeatedly set to more restrictive
> permission than 666?

Is another rule overriding this one? Try
grep null /etc/udev/rules.d/*.rules


-- 
Neil Bothwick

Who messed with my anti-paranoia shot?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-user] Re: kconsole lost PTYs

[James]

Neil Bothwick <neil <at> digimed.co.uk> writes:

> > # egrep null 50-udev.rules
> > KERNEL=="null",         NAME="%k", MODE="0666"

> > Why is /dev/null getting repeatedly set to more restrictive
> > permission than 666?

> Is another rule overriding this one? Try
> grep null /etc/udev/rules.d/*.rules

<shows>
/etc/udev/rules.d/50-udev.rules:KERNEL=="null",         NAME="%k", MODE="0666"


And the other edits I make seem to be still in place:

KERNEL=="console",              NAME="%k", GROUP="tty", MODE="0666"

which was the line I edited in '50-udev.rules'.

etc/group <shows>
tty::5:allen,james,mythtv,allie

Still I have to ssh in and issue:
chmod 666 /dev/null
chown root:tty /dev/pty*
chown root:tty /dev/tty*

Before I make these changes, root:root owns the ptys/ttys and 
the /dev/null permissions are 600 (crw).

Any other ideas as to what can be setting/corrupting these 
file permission/ownership?

I can always use a custom script to patch this until a permanent
fix is discovered. Any ideas what's the best place to do this?
After bootup but before loging via the kdm session manager?





James



-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: kconsole lost PTYs

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 319 bytes --]

On Wed, 28 Jun 2006 17:37:52 +0000 (UTC), James wrote:

> which was the line I edited in '50-udev.rules'.

Don't edit this file, put your own settings in 10-udev.rules and use :=
for any assignments to prevent a later rule overwriting them.


-- 
Neil Bothwick

Help put the "fun" back in "dysfunctional" !

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-user] Re: kconsole lost PTYs

[James]

Willie Wong <wwong <at> Princeton.EDU> writes:

>
Sorry about the delayed resonse, Gmane has been down since yesterday.....

> What about /etc/conf.d/rc? Maybe you can toggle RC_DEVICES="udev" and
> set RC_DEVICE_TARBALL="no"? (or maybe setting it to "yes" might give
> you a work around?)


I edited  /etc/conf.d/rc:

RC_DEVICES="udev"

Which did not fix my problem of ownership of /dev/tty* and /dev/pty*

Any other ideas? This one did not make any difference.


James



-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: kconsole lost PTYs

[James]

Neil Bothwick <neil <at> digimed.co.uk> writes:

>
Sorry about the delayed respone; problems with
http://thread.gmane.org/gmane.linux.gentoo.user
being down and losing emails. If fact I had to copy
your latest respone from netnews: linux.gentoo.user.



<snipped from netnews>

> Don't edit this file, put your own settings in 
> 10-udev.rules and use := for any assignments to prevent 
> a later rule overwriting them.

Tried this but it does not correctly set the permission
upon reboot. In fact I put these entries in both
10-local.rules and 10-udev.rules


KERNEL:="console",      NAME="%k", GROUP="tty", MODE="0666"
KERNEL:="null",         NAME="%k", MODE="0666"

Looking around at /dev and /etc/udev/rules.d/

It seem as though the other devices are getting permissions
correctly set. I did notice something very peculiar about dev/null
Here is dev /null before I correct it:
crw-rw-rw- 1 root root 1, 3 Oct 22  2000 /dev/null
What's up with the date?

Also, I do not have to change permission on /dev/null to get the
kconsole sessions to run correctly. But I do want 666 on dev/null
upon reboot, as I use it extensively (old unix habits).....

Any other ideas?


James







-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: kconsole lost PTYs

[Willie Wong]

On Thu, Jun 29, 2006 at 07:19:29PM +0000, Penguin Lover James squawked:
> > What about /etc/conf.d/rc? Maybe you can toggle RC_DEVICES="udev" and
> > set RC_DEVICE_TARBALL="no"? (or maybe setting it to "yes" might give
> > you a work around?)
> 
> 
> I edited  /etc/conf.d/rc:
> 
> RC_DEVICES="udev"
> 
> Which did not fix my problem of ownership of /dev/tty* and /dev/pty*
> 
> Any other ideas? This one did not make any difference.
> 

Hum, I am pretty much out of ideas. What about editing
/etc/udev/udev.conf to have udev_log="debug"
reboot, and check your system logs?

A warning: this will generate A LOT of logs. 

W

-- 
Two college graduates are peeing in a bathroom. 

The Harvard grad finishes, goes over and washes his hands very well
using lots of soap and water, and says "at Harvard, they teach us to
be clean."

The Yale grad finishes, and washes his hands with a very small amount
of soap and water and says "at Yale they teach us to conserve
resources."

Right then, a Princeton grad walks in, washes his hands thoroughly,
and goes to the urinal, saying "At Princeton, they teach us to wash
our hands before handling a sacred object."
Sortir en Pantoufles: up 19 days, 21:37
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: kconsole lost PTYs

[James]

Willie Wong <wwong <at> Princeton.EDU> writes:

> Hum, I am pretty much out of ideas. What about editing
> /etc/udev/udev.conf to have udev_log="debug"
> reboot, and check your system logs?


Well, upon rebooting, I'm seeing udev complain about
quite a lot of things. Nothing is viewable via dmesg.
One of the problems it complained about is that '%e' is 
deprecated and donot use it.

The screen rolls by very fast (P4 with HT) so 
I need a way to capture this information that 
is not in the /var/log/dmesg file.

ideas?


James

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: kconsole lost PTYs

[James]

Willie Wong <wwong <at> Princeton.EDU> writes:


> Hum, I am pretty much out of ideas. What about editing
> /etc/udev/udev.conf to have udev_log="debug"
> reboot, and check your system logs?


Well, for now I'm just going to patch this up until I can 
spend more time on it.

All I need to so is issue these commands during the boot cycle,
before I login in


chown root:tty /dev/pty*
 chown root:tty /dev/tty*


Any suggestions as the best place to insert/script these modifications
to the boot sequence are most welcome.


James



-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] PATCHED: kconsole lost PTYs

[James]

James <wireless <at> tampabay.rr.com> writes:

 
> Willie Wong <wwong <at> Princeton.EDU> writes:

> > Hum, I am pretty much out of ideas.
> Well, for now I'm just going to patch this up until I can 
> spend more time on it.
> 
> All I need to so is issue these commands during the boot cycle,
> before I login in
> chown root:tty /dev/pty*
>  chown root:tty /dev/tty*

Easy fix:

I edited /etc/conf.d/rc 


#RC_DEVICE_TARBALL="no"
RC_DEVICE_TARBALL="yes"

This get's the portable working again, until I have a chance to reinstall it.

thanks for the help (Willie && Niel)


James




-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: kconsole lost PTYs

[Willie Wong]

On Fri, Jun 30, 2006 at 03:53:50PM +0000, Penguin Lover James squawked:
> All I need to so is issue these commands during the boot cycle,
> before I login in
> 
> 
> chown root:tty /dev/pty*
>  chown root:tty /dev/tty*
> 
> 
> Any suggestions as the best place to insert/script these modifications
> to the boot sequence are most welcome.

/etc/conf.d/local.start

W
-- 
Physics: a liberal arts on steroids.
       ~Prof. Peter Meyers.
Sortir en Pantoufles: up 20 days, 21:15
-- 
gentoo-user@gentoo.org mailing list