Update: It seems that the /etc/devfs/conf.d/ directory isn't used by anyone at all (at least not my system) and therefore /etc/devfs/conf.d/tpb has no effect. How did it even get into the release? From what I can tell (and I repeat that I'm very new at this and welcome correction) the Ubuntish way to set the permissions of /dev/nvram is: add a file named /etc/udev/rules.d/80-tpb-nvram.rules containing:
KERNEL=="nvram", GROUP="nvram", MODE="0640" Now, add your user to the nvram group. This group is created by tpb installation script. Now you /dev/nvram is readable by you, and tpb loads successfully from Xsession.d. Does this work for everyone else? However, I'm not sure if this is still important, since there seem to be other solutions in the works to get OSD on laptops, for example, see bug 357673. Does anyone know what the relationship is between that and this? -- tpb init script doesn't launch tpb https://bugs.launchpad.net/bugs/146987 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs -- universe-bugs mailing list universe-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/universe-bugs
