[06:06] <glitchd> can anyone possibly answer a pcmanfm question?
[08:20] <khampf> if that was the question, yeah I could
[10:33] <thunder011> hi
[10:34] <thunder011> hello here is one problem when i tried to become root by sudo -i and typed password the result showed          """meet is not in the sudoers file.  This incident will be reported"""  where meet is my pc name. sorry for my english
[10:35] <cfhowlett> the user meet is not a sudo level account.
[10:36] <thunder011> it is i am admin i alwase use sudo for root only this time it is not working
[10:38] <khampf> thunder011: and /etc/sudoers looks sane?
[10:38] <thunder011> what ??
[10:38] <thunder011> when i type id it shows  uid=1000(meet) gid=1000 groups=1000,4,24,27,30,46,113,128
[10:40] <diogenes_> thunder011, is it allowing you to run sudo apt update?
[10:40] <thunder011> no its not working
[10:41] <thunder011>  sudo apt update
[10:41] <thunder011> [sudo] password for meet:
[10:41] <thunder011> meet is not in the sudoers file.  This incident will be reported.
[10:41] <diogenes_> thunder011, can you run: su
[10:42] <diogenes_> and enter password
[10:42] <thunder011> nope                               su: Authentication failure
[10:43] <diogenes_> ok wait,
[10:49] <diogenes_> thunder011, you can try go to recovery mode and run: usermod -a -G sudo yourusername
[10:50] <thunder011> gow to go in recovery mod
[10:50] <thunder011> how to
[10:51] <diogenes_> thunder011, read this: https://wiki.ubuntu.com/RecoveryMode
[10:52] <thunder011> okay thanks brother i will report  after while my phones bettery is disccarged so i cant coonect to ethernet
[10:52] <thunder011> thanks
[10:52] <thunder011> bye
[10:52] <diogenes_> nye
[11:40] <thunder011> nothing works
[11:40] <diogenes_> thunder011, what error did you get?
[11:41] <thunder011> meet is not in the sudoers file.  This incident will be reported.
[11:41] <diogenes_> what command did you run?
[11:41] <thunder011> i tried visudo
[11:42] <diogenes_> did you boot into recovery mode and run the command I gave you?
[11:42] <thunder011> and also sudo gpasswd -a username sudo
[11:42] <thunder011> is  it this command ??
[11:43] <diogenes_> in the recovery mode you have to run: usermod -a -G sudo yourusername
[11:43] <thunder011> yeah but i found that    This does not work in Debian 8.5. or later
[11:43] <thunder011> https://unix.stackexchange.com/questions/179954/username-is-not-in-the-sudoers-file-this-incident-will-be-reported
[11:44] <diogenes_> can you run cat /etc/sudoers?
[11:45] <thunder011> cat: /etc/sudoers: Permission denied
[11:46] <thunder011> nope, but i can login in my account with my password
[11:47] <diogenes_> then here is my advice, get a bootable usb, boot into the live session and go to your /etc/sudoers open it and see if it looks like this: http://susepaste.org/23609402
[11:47] <diogenes_> if you see anything else added to the sudoers
[11:48] <diogenes_> remove those lines and reboot
[11:48] <thunder011> link is not working
[11:48] <thunder011> 404 page not found
[11:50] <diogenes_> here: http://dpaste.com/0DNDWXP
[11:53] <thunder011> is it possible to delete sudoers file and make new root account  insted??????
[12:48] <thunder011> thanks community, root access problem is now solved
[12:48] <thunder011> :):):)
[12:49] <diogenes_> thunder011, how did you solve it?
[12:52] <thunder011> in recovery mod when i tried to run all command with sudo word error showed "sudo group" is not exit so  tried addgroup sudo and then changed group  id to 1000 than update my current account with sudo privilege and problem fixed
[12:52] <diogenes_> cool
[12:53] <thunder011> Lol
[14:14] <JrWebDev> im trying to change the date on my virtual machine.  my vm guest is Xubuntu 16.04.2  i tried using timedatectl to set the time and sudo date --set="" and even tried modifying the vm bios time (virtualbox) ,  i also disconnected the network adapter and yet it still goes back to todays current date...when i change it only last for 5 seconds and switches how da heck do i stop it?
[16:42] <Cursarion> so, err, on 16.04 the weather plugin will remain broken forever?
[16:43] <Cursarion> even though it's LTS?
[16:45] <frozenrouter> I am having an odd problem with cpu frequency while using multithreaded games on xubuntu 17.04. After a short time playing the game, the frequency on all cores drops to 800MHz, limiting gpu usage, and dropping framerate significantly. I can confirm that the system can maintain a respectable core clock alongside gpu load. Any Advice?
[16:47] <flocculant> Cursarion: no not at all - there is a package in proposed to test - when people have done that - it will eventually move from proposed to updates, see bug 1688056
[17:04] <xubuntu09i> hello everybody : I hope with installing 17.04 instead of old 16.04 I will not have anymore this "assuming cache write through"
[17:05] <xubuntu09i> because each time I reinstall to ensure that empty space of disk has been overwritten as the installation option says
[17:06] <xubuntu09i> in a few minutes it will have finished installing 17.04
[17:07] <xubuntu09i> I hope this will work this time
[17:07] <xubuntu09i> in a few seconds, rather
[17:09] <xubuntu09i> still there, the progression bar has gone back
[17:10] <xubuntu09i> and the installation bar now has gone forward, i will restart
[17:38] <xubuntu22i> hello it's still me. ubuntu is against me today
[17:39] <xubuntu22i> it don't say to remove the installation media after ubuntu installation
[17:39] <xubuntu22i> instead it says
[17:40] <xubuntu22i> assuming cache : write through
[17:40] <xubuntu22i> I'm trying with another place to plug the usb stick
[17:40] <xubuntu22i> another place on the computer
[17:42] <xubuntu22i> Maybe I will receive an answer ... I go eat because this is the 5th time I 'm trying to install xubuntu since two hours ago
[17:47] <Cursarion> flocculant: hmmmkay
[18:03] <diogenes_> xubuntu22i, what is the exact issue? it installs but doesn't boot or it doesn't install at all?
[18:10] <xubuntu22i> so :
[18:11] <xubuntu22i> it installs, but not reboot : on the shut down process it says "assuming cache : write through"
[18:12] <xubuntu22i> thank you for answering
[18:12] <diogenes_> xubuntu22i, so everything works except reboot?
[18:12] <xubuntu22i> yes
[18:13] <diogenes_> have you tried: sudo reboot now?
[18:14] <xubuntu22i> and I fear the "delete empty space" installation option (when crypting the hard disk) have not been taken in account, especially
[18:14] <xubuntu22i> no
[18:14] <xubuntu22i> I have not tried
[18:14] <xubuntu22i> I just put "continue to test"
[18:16] <diogenes_> xubuntu22i, try in terminal: sudo systemctl reboot
[18:16] <diogenes_> and see if it reboots
[18:16] <xubuntu22i> ok thank you
[18:17] <diogenes_> yw
[18:30] <pierre_> hello
[18:30] <pierre_> who has just helped me with installing xubuntu ?
[18:31] <pierre_> I want to say thank you
[18:31] <pierre_> I'm now sure that my disk is securely encypted
[18:31] <diogenes_> pierre_, what was your issue?\
[18:32] <pierre_> I have done what you have said me and it has worked
[18:33] <pierre_> the reboot has been correctly executed
[18:33] <diogenes_> good
[18:33] <diogenes_> I'm glad
[18:33] <pierre_> the installation medium has been asked for unplugging
[18:33] <pierre_> as I wished for
[18:34] <pierre_> Thank you
[18:34] <diogenes_> you're welcome
[18:35] <pierre_> I think I will write on paper what you have said :
[18:35] <pierre_> it was "sudo systemcl reboot"
[18:35] <pierre_> ?
[18:35] <diogenes_> yes
[18:35] <diogenes_> that's a good habit to write the working commands
[18:35] <diogenes_> always do so
[18:36] <diogenes_> pierre_, you made a mistake
[18:37] <diogenes_> it's: sudo systemctl reboot
[18:37] <diogenes_> not systemcl*
[18:37] <pierre_> ah thank you so
[18:38] <pierre_> I will think about taking a notepad near my computer :)
[18:38] <diogenes_> :)