Le 10/05/2017 à 08:07, 4tro a écrit : > be advised, Precise Pangolin is EOL. > > As such, maybe close this bug to reduce clutter? > Thanks you to contact me.
I suggest to close this bug. I thought first, that at this time, it was certenly due to a successions of installations without update after each one. I didn't mention that I worked first without ability to connect this machine on the net, in a school in French Guyana, near the forest. So I had connected it at home for an new update. The last 14.04 LTs version of Lubuntu din't have these bugs. I think with a lot of friends that every body could constated along his life, that some systems or applications in a beta version could create a few repertory with restrictions of rights on a group user or for an user. In this case I just sugest to remember to verify the part of the bios controller of the hard disk, or hards disks themselves with a fsdisk (in hards situations) . Try to reinstall or last to update frequently as you can. Some of us sometimes reuse unit created with an Ms-dos like system, and after that, put a double boot on it. Don't have any hesitation to replace with sudo 755 rights by hands for home user directory concerned. Rember that, in my case, this old unit can't accept double boot, so I was obliged to work as a light embeded system, just trying to recycle it for my little classroom. Thanks for all. Didalter -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/987003 Title: In Pangolin, a new administrator profile was not registred in the sudoer group (Lubuntu /Gnome environment) Status in sudo package in Ubuntu: New Bug description: I recently installed Lubuntu 12.04 cause my old computer wasn't completly accepted by unfinity live-dvd due to its cd limit. So I installed Lubuntu-desktop-cd first quitly fine, with no matter. After that I installed Gnome 3. (perhaps this anomaly was in the lubuntu-sudo first ?) My first administrator was fine accepted as Sudoer. So I installed two new users and an another admin in the Gnome environment . But , when I tried a "sudo aptitude" with this new "adm" profile, I discovered that the new administrator was not registred as sudoer : the message was "you are not a sudoer and I will make a report " and twice in synaptic or any command for admninistrator. So, I came back to verify these news status in the first admin's deskotp. In effect, the new admin was not registred in the "sudoer" group, but was registred in the "adm" group. First I put on the case for this new one in sudo and adm group. At the first try, the new admin sudoer registration "by hand" didn't took effect. I quitted and shutdown (as if in a simple ms boot-on system ;-) . And after reeboot, the new second admin was accepted as sudoer. So I thought I had to report this little anomaly before we have some newbes in trouble the D day. Perhaps wasn't due to succession of my manipulations or not ?.... So you have a part of answer, if it is. Good luck and long life for the Pangolin ! Alter.md To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/987003/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
