[Bug 63031] Re: /dev/null: Permission denied
My box runs U 10.10 i386; not Ubuntu 10.04 i386 as reported in the previous post -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/63031 Title: /dev/null: Permission denied -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
It happened today on my box too. It runs Ubuntu 10.04 i386 and the box was up an running for several days without issue. I cannot unlock GNOME screensaver this morning. I tried to login from text terminal and I was able to do it but I see many errors '-'-'-bash: /dev/null permision denied' I found that /dev/null device is just a file, not device: $ cd /dev; ls -l null -rw-r--r-- 1 root root 85 2011-02-22 09:23 null I fixed the issue with command (it creates standard devices) # cd /dev; MAKEDEV std $ cd /dev; ls -l null crw-rw-rw- 1 root root 1, 3 2011-02-22 09:31 null The issue is fixed, I can unlock screensaver and login to GNOME now. The key question is, 'who deleted /dev/null device??' That was not me and it happened during night... Some application installed on my desktop has a bug that removes /dev/null device. My guess is that it can be 'xz' or 'xzdec' or 'xz-utils' or 'epub-utils' or 'txt2pdb' or 'plucker' package; I installed these on my box yesterday. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/63031 Title: /dev/null: Permission denied -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
Ivaneide: have you read all the comments and checked whether they apply to you? If none of the comments apply to you, then you cannot possibly have this bug so should open a new one. If one or more of the comments apply to you, follow their recommendations -- /dev/null: Permission denied https://bugs.launchpad.net/bugs/63031 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
I can confirm this in a fresh install of Jaunty 32. Also /dev/urandom has wrong permissions and login to gnome via gdm fails because of this. Manually changing the permissions to 666 in /dev/null and /dev/urandom allows me to login in gnome but I still can't user gnome-terminal (it says there was an error in creating the child process). My machine is an HP Pavilion dv2000 (AMD Turion 64x2). Can I change the status or should I file another bug? -- /dev/null: Permission denied https://bugs.launchpad.net/bugs/63031 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
I just installed fresh 9.04 64-bit server version using ubuntu-9.04 -server-amd64.iso, under Virtualbox. After i login first time i get lots of /dev/null permission denied messages and looking its rights i can see only root can access it. -- /dev/null: Permission denied https://bugs.launchpad.net/bugs/63031 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
I had this problem occur to me when just installing 9.04 from DVD iso I downloaded a couple of days earlier. This problem did not occur when installing from the CD-ROM iso downloaded today. -- /dev/null: Permission denied https://bugs.launchpad.net/bugs/63031 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
Workaround for Jaunty: add the line: chmod 666 /dev/null to /etc/rc.local before the exit 0 line. -- /dev/null: Permission denied https://bugs.launchpad.net/bugs/63031 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
Nevermind. Still a whole host of problems with udev missing. now it isn't called at all. Relinked S10udev. error persists -- /dev/null: Permission denied https://bugs.launchpad.net/bugs/63031 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
I disabled ACPI 2 in the bios and deleted /etc/rcS.d/S10UDEV and all is well. Not sure which made the difference. -- /dev/null: Permission denied https://bugs.launchpad.net/bugs/63031 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
I also am experiencing this with 9.04. Clean install ubuntu 9.04 alternate on an asus board with an amd phenom ii 920. -- /dev/null: Permission denied https://bugs.launchpad.net/bugs/63031 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
I'm experiencing this issue with 9.04. Clean install and did a large update and cannot login to the graphical desktop now. Trying the above fix (adding the permissions line into /etc/rc.local) results in not being able to even get to the login screen. It starts to load, but never gets beyond a black screen with the cursor in the middle. I'm running ubuntu desktop 9.04 on a VIA Epia Nano-ITX board. -- /dev/null: Permission denied https://bugs.launchpad.net/bugs/63031 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
Also bug 53040 is quite the same! -- /dev/null: Permission denied https://bugs.launchpad.net/bugs/63031 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
I have this problem on ubuntu-server AND on ubuntu-desktop without KDE, so there is no KDE services editor. Can we join this bug with #53040 and #69516? -- /dev/null: Permission denied https://bugs.launchpad.net/bugs/63031 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 63031] Re: /dev/null: Permission denied
ah, we deturmined that to be the KDE services editor! also, maybe there should be a script that checks rc*.d for crud like this? Running something twice shouldn't screw it all up?! Our initscripts should have a bit of falt tollerance built in for stupid users like me who want an error message regarding what is acutally broken instead of not being able to log into the box. On 3/19/07, directhex <[EMAIL PROTECTED]> wrote: > Something unknown is causing bad entries in /etc/rc*.d > > Specifically, /etc/rc2.d/S*udev should not be there > > The bug isn't that /dev/null has permission denied, it's that > *something* is causing spurious init script entries > > -- > /dev/null: Permission denied > https://launchpad.net/bugs/63031 > -- /dev/null: Permission denied https://launchpad.net/bugs/63031 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
Something unknown is causing bad entries in /etc/rc*.d Specifically, /etc/rc2.d/S*udev should not be there The bug isn't that /dev/null has permission denied, it's that *something* is causing spurious init script entries -- /dev/null: Permission denied https://launchpad.net/bugs/63031 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
I'm experiencing this bug in Feisty every time udev is updated, the chmod workaround described above fix the problem; you should packetize udev chi 666 permisiion on /lib/udev/devices/null -- /dev/null: Permission denied https://launchpad.net/bugs/63031 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
I also get this on my new Thinkpad/Edgy 6/.10, however, the behaviour is as follows: 1)With kubuntu installed out of the box, the udev service is *not* set to start at boot. This strikes me as extremely odd, but that is definitely what the KDE control center (system->services) reported. In this configuration, the laptop works fine - it boots perfectly into X, and even USB keys are detected and automounted. 2)BUT, I needed to have my own udev rule (in /etc/udev/rules.d/10-local.rules), and so I set the udev service to start automatically at boot (again, using KDE's control center). 3)Now, when the system boots, I get dumped to a login prompt, and, when I log in, I get an endless stream of "/dev/null: permission denied" messages (fortunately, these stop when I hit Ctrl-C). 4)The workaround: (i) /etc/init.d/udev stop ; #By now, /dev/null has the right permissions. (ii) /etc/init.d/udev start ; #By now, the udev symlink which I initially wanted has been created. (iii) /etc/init.d/kdm restart #And X restarts contentedly. - My system: #udevtest /class/mem/null: main: looking at device '/class/mem/null' from subsystem 'mem' udev_rules_get_name: no node name set, will use kernel name 'null' udev_db_get_device: no db file to read /dev/.udev/db/[EMAIL PROTECTED]@null: No such file or directory udev_node_add: creating device node '/dev/null', major = '1', minor = '3', mode = '0666', uid = '0', gid = '0' main: run: 'socket:/org/freedesktop/hal/udev_event' main: run: 'socket:/org/kernel/udev/monitor' #The relevant bit of /var/log/udev (i.e. the ones referring to "null") UEVENT[1167754351.369243] add@/class/mem/null UDEV [1167754351.369243] add@/class/mem/mem UDEV_LOG=3 ACTION=add DEVPATH=/class/mem/mem SUBSYSTEM=mem SEQNUM=1536 MAJOR=1 MINOR=1 UDEVD_EVENT=1 DEVNAME=/dev/mem UEVENT[1167754351.369249] add@/class/mem/port UDEV [1167754351.369249] add@/class/mem/null UDEV_LOG=3 ACTION=add DEVPATH=/class/mem/null SUBSYSTEM=mem SEQNUM=1537 MAJOR=1 MINOR=3 UDEVD_EVENT=1 DEVNAME=/dev/null Hope that helps; if there are other any tests I can do, let me know. -- /dev/null: Permission denied https://launchpad.net/bugs/63031 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
Thank you. Yes, you're quite right - the root cause is trying to start udev when it is already running (although this really shouldn't have such symptoms). Perhaps the udev start script should check for udevd already running, and if so, it should just do a udevtrigger and exit. However, in the first place, why did I add udev to rc2.d? Answer: because I looked in KDEs system services GUI, and saw that udev was NOT marked as "start at boot". This is a bug in KDE, since it doesn't read rcS.d ! -- /dev/null: Permission denied https://launchpad.net/bugs/63031 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
See bug 69516, maybe that will help you. -- /dev/null: Permission denied https://launchpad.net/bugs/63031 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
I also noticed that if i do a "sudo vi ssh[tab-key]" I get the same error, but I only get it once.. I haven't change the permission of /dev/null, should I? -- /dev/null: Permission denied https://launchpad.net/bugs/63031 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
I just did a brand new install of the 6-10.iso server image and I am having this problem. So I am running edgy already and the problem is still there. Any suggestions? or anything that I can provide to help this bug be resolved? -- /dev/null: Permission denied https://launchpad.net/bugs/63031 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
I'm experiencing a similar thing. When I ssh to my server I get the same permission denied messages in my console. Checking the "/dev/null", I see "crw---" owned by root:root. After a "# /etc/init.d/udev restart" the permissions are "crw-rw-rw-". I'm running Edgy (2.6.17-10-386). Attached is my "/var/log/udev". "# udevtest /class/mem/null" gives: main: looking at device '/class/mem/null' from subsystem 'mem' udev_rules_get_name: no node name set, will use kernel name 'null' udev_db_get_device: no db file to read /dev/.udev/db/[EMAIL PROTECTED]@null: No such file or directory udev_node_add: creating device node '/dev/null', major = '1', minor = '3', mode = '0666', uid = '0', gid = '0' main: run: 'socket:/org/freedesktop/hal/udev_event' main: run: 'socket:/org/kernel/udev/monitor' ** Attachment added: "/var/log/udev" http://librarian.launchpad.net/4941037/udev.log -- /dev/null: Permission denied https://launchpad.net/bugs/63031 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
This has nothing to do with /lib/udev/devices/null - that should have 0600 permissions. If you have this problem on EDGY, please open a new bug and provide the information requested (/var/log/udev and output of "udevtest /class/mem/null") -- /dev/null: Permission denied https://launchpad.net/bugs/63031 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
Something VERY recent has triggered this behavior to reappear. My (Edgy) laptop suffered from the problem, and I've just checked my (Edgy) desktop, where it appears /lib/udev/devices/null also has bad permissions -- /dev/null: Permission denied https://launchpad.net/bugs/63031 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
hdparm is usually started by udev, no? -- /dev/null: Permission denied https://launchpad.net/bugs/63031 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
That's not all... The workaround works. But I don''t think the problem is related to udev. I installed a small testscript that runs during boot before udev starts. It sets permissions of /dev/null first to 0777, than loops in the background for while noting the /dev/null permissions and a list of processes to a file. I saw that after udev starts the permissions change correctly to 0666, but later somewhere when hdparm starts the permissions get changed to 0600. Couldn't figure out what exactly does change the permissions, just grepping for chmod and dev/null in /etc/init.d/* doesn't show any hints. Peter -- /dev/null: Permission denied https://launchpad.net/bugs/63031 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
You're running dapper? This should definitely be fixed in edgy. ** Changed in: udev (Ubuntu) Status: Needs Info => Fix Released -- /dev/null: Permission denied https://launchpad.net/bugs/63031 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
$ udevtest /class/mem/null main: Usage: udevtest Did you mean perhaps "udevtest /class/mem/null /dev/null" ? Also, would you like me to run this before I manually change the perms or is it okay if it's done after they are chmod'ed? -- /dev/null: Permission denied https://launchpad.net/bugs/63031 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63031] Re: /dev/null: Permission denied
** Summary changed: - "bash: /dev/null: Permission denied" on GNOME Login as Regular User... + /dev/null: Permission denied -- /dev/null: Permission denied https://launchpad.net/bugs/63031 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
