...otherwise "mesg y" warns about that. If mesg is wrong, please reassign this bug to the sysvinit-tools component.
hmm, I can't reproduce that... how did you end up with /dev/console?? normally you have /dev/tty[123456..] or /dev/pts/[123456..]
(In reply to comment #1) > hmm, I can't reproduce that... how did you end up with /dev/console?? normally > you have /dev/tty[123456..] or /dev/pts/[123456..] Oh, gosh. It only happens when you boot in single user mode.
Hi Harald, I believe I see what Bernie mentioned (although I don't think /dev/console is the problem). F10 works correctly: $ mesg y $ mesg is y $ tty /dev/pts/1 $ ls -l /dev/pts/1 crw--w---- 1 emcnabb tty 136, 1 2009-04-07 22:08 /dev/pts/1 However, the latest Rawhide (20090407) shows: $ mesg y mesg: error: tty device is not owned by group `tty' $ mesg is n $ tty /dev/pts/8 $ ls -l /dev/pts/8 crw--w---- 1 emcnabb emcnabb 136, 8 2009-04-07 22:09 /dev/pts/8 This only happens on locally opened terminals. If I ssh in it does set the tty group correctly. For example, pts/0 and pts/1 are gnome-terminal sessions, and pts/10 is a ssh connection: $ ls -l /dev/pts/* crw--w---- 1 emcnabb emcnabb 136, 0 2009-04-07 22:05 /dev/pts/0 crw--w---- 1 emcnabb emcnabb 136, 1 2009-04-07 18:14 /dev/pts/1 crw--w---- 1 emcnabb tty 136, 10 2009-04-07 22:09 /dev/pts/10 ... I hope this helps.
udev never sets the permission to the user... it's login or consolehelper which does this.
Ah, ok - I didn't realize that. Can you reassign this to the correct component? (ConsoleKit I assume)
Done.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Any idea how to fix this? Since it worked in F10, I can't imagine it's a tough problem. Hell, it's probably a one-liner. I'd even look at it if someone could point me at the source.
(In reply to comment #8) > Any idea how to fix this? Since it worked in F10, I can't imagine it's a tough > problem. Hell, it's probably a one-liner. > > I'd even look at it if someone could point me at the source. Are you the same Randell Jesup who wrote substantial parts of AmigaOS? /me bows (sorry for the offtopic)
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.