** Summary changed: - /dev/toshiba created cmod 660 root:root + /dev/toshiba created chmod 660 root:root
** Description changed: Running wmtuxtime as myself produces the helpful error message about the kernel not having the necessary module, even though the toshiba module is shown by lsmod. (The documentation is also somewhat lacking here, as it only talks about "the kernel module" a lot, without mentioning the actual name of the module.) - It turns out that changing the owner of /dev/toshiba fixes the problem. - As a workaround, I changed the group for /dev/toshiba to admin, which - works for me (but is probably not a good general solution). + It turns out that the permissions of /dev/toshiba are too tight. + Changing the owner of /dev/toshiba fixes the problem; or, one could + change the permissions to be more relaxed. As a temporary workaround, I + changed the group for /dev/toshiba to admin, which works for me (but is + probably not a good general solution). At a minimum, if the actual ownership/permissions cannot be solved elegantly, the error message in this case should not be so misleading. Dapper "alt. server" install + x-window-system-core, xdm, and various other goodies. -- /dev/toshiba created chmod 660 root:root https://launchpad.net/bugs/57052 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
