Installing software

DavePM

Member
Joined
May 2, 2023
Messages
96
Reaction score
37
Credits
781
Well as of today I am unable to install software on my Ubuntu installation. I only have the one user on the system and I log onto Ubuntu using my password with no issues at all. When I try and install new software from the Snap Store and it asked me to Authenticate so I use my logon password like before. It then just goes back to the Authenticate box until it tells me cannot install software.
 


Well as of today I am unable to install software on my Ubuntu installation. I only have the one user on the system and I log onto Ubuntu using my password with no issues at all. When I try and install new software from the Snap Store and it asked me to Authenticate so I use my logon password like before. It then just goes back to the Authenticate box until it tells me cannot install software.
It sounds like there may be an issue with your user's sudo privileges. You can try running the following command to add your user to the sudo group if it isn't already:

Code:
sudo usermod -aG sudo username

Replace "username" with your actual username. After running this command, try installing software again and see if the issue persists. If it does, you can try checking the system logs for any error messages that might shed some light on the problem. You can do this by running the following command:

Code:
journalctl -xe

Hopefully, one of these solutions will help you resolve the issue.
 
Tried those and got the following back.

Code:
dave@dave-Vostro-3558:~$ sudo usermod -aG sudo dave
[sudo] password for dave:
dave is not in the sudoers file.  This incident will be reported.
dave@dave-Vostro-3558:~$ journalctl -xe
Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal' can see all messages.
      Pass -q to turn off this notice.
░░ The job identifier is 442.
Jun 16 16:24:49 dave-Vostro-3558 dbus-daemon[2066]: [session uid=1000 pid=2066]>
Jun 16 16:24:49 dave-Vostro-3558 systemd[2044]: Started GNOME Terminal Server.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 442.
Jun 16 16:24:49 dave-Vostro-3558 systemd[2044]: Started VTE child process 3935 >
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 461.
Jun 16 16:24:50 dave-Vostro-3558 dbus-daemon[2066]: [session uid=1000 pid=2066]>
Jun 16 16:24:50 dave-Vostro-3558 dbus-daemon[2066]: [session uid=1000 pid=2066]>
Jun 16 16:24:50 dave-Vostro-3558 io.snapcraft.Settings[3951]: userd.go:93: Star>
Jun 16 16:24:52 dave-Vostro-3558 cinnamon[2709]: JS LOG: [LookingGlass/info] Ad>
Jun 16 16:25:52 dave-Vostro-3558 sudo[4711]:     dave : user NOT in sudoers ; T>
lines 2115-2137/2137 (END)
░░ The job identifier is 442.
Jun 16 16:24:49 dave-Vostro-3558 dbus-daemon[2066]: [session uid=1000 pid=2066] Successfully activated service 'org.gnome.Terminal'
Jun 16 16:24:49 dave-Vostro-3558 systemd[2044]: Started GNOME Terminal Server.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 442.
Jun 16 16:24:49 dave-Vostro-3558 systemd[2044]: Started VTE child process 3935 launched by gnome-terminal-server process 3898.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 461.
Jun 16 16:24:50 dave-Vostro-3558 dbus-daemon[2066]: [session uid=1000 pid=2066] Activating service name='io.snapcraft.Settings' requested by ':1.106'>
Jun 16 16:24:50 dave-Vostro-3558 dbus-daemon[2066]: [session uid=1000 pid=2066] Successfully activated service 'io.snapcraft.Settings'
Jun 16 16:24:50 dave-Vostro-3558 io.snapcraft.Settings[3951]: userd.go:93: Starting snap userd
Jun 16 16:24:52 dave-Vostro-3558 cinnamon[2709]: JS LOG: [LookingGlass/info] Adding XAppStatusIcon:  (:1.69/org/x/StatusIcon/Icon_2)
Jun 16 16:25:52 dave-Vostro-3558 sudo[4711]:     dave : user NOT in sudoers ; TTY=pts/0 ; PWD=/home/dave ; USER=root ; COMMAND=/usr/sbin/usermod -aG >
~
~
~
~
~
~
~
~
~
~
~
~
~
 
Tried those and got the following back.

Code:
dave@dave-Vostro-3558:~$ sudo usermod -aG sudo dave
[sudo] password for dave:
dave is not in the sudoers file.  This incident will be reported.
dave@dave-Vostro-3558:~$ journalctl -xe
Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal' can see all messages.
      Pass -q to turn off this notice.
░░ The job identifier is 442.
Jun 16 16:24:49 dave-Vostro-3558 dbus-daemon[2066]: [session uid=1000 pid=2066]>
Jun 16 16:24:49 dave-Vostro-3558 systemd[2044]: Started GNOME Terminal Server.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 442.
Jun 16 16:24:49 dave-Vostro-3558 systemd[2044]: Started VTE child process 3935 >
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 461.
Jun 16 16:24:50 dave-Vostro-3558 dbus-daemon[2066]: [session uid=1000 pid=2066]>
Jun 16 16:24:50 dave-Vostro-3558 dbus-daemon[2066]: [session uid=1000 pid=2066]>
Jun 16 16:24:50 dave-Vostro-3558 io.snapcraft.Settings[3951]: userd.go:93: Star>
Jun 16 16:24:52 dave-Vostro-3558 cinnamon[2709]: JS LOG: [LookingGlass/info] Ad>
Jun 16 16:25:52 dave-Vostro-3558 sudo[4711]:     dave : user NOT in sudoers ; T>
lines 2115-2137/2137 (END)
░░ The job identifier is 442.
Jun 16 16:24:49 dave-Vostro-3558 dbus-daemon[2066]: [session uid=1000 pid=2066] Successfully activated service 'org.gnome.Terminal'
Jun 16 16:24:49 dave-Vostro-3558 systemd[2044]: Started GNOME Terminal Server.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 442.
Jun 16 16:24:49 dave-Vostro-3558 systemd[2044]: Started VTE child process 3935 launched by gnome-terminal-server process 3898.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 461.
Jun 16 16:24:50 dave-Vostro-3558 dbus-daemon[2066]: [session uid=1000 pid=2066] Activating service name='io.snapcraft.Settings' requested by ':1.106'>
Jun 16 16:24:50 dave-Vostro-3558 dbus-daemon[2066]: [session uid=1000 pid=2066] Successfully activated service 'io.snapcraft.Settings'
Jun 16 16:24:50 dave-Vostro-3558 io.snapcraft.Settings[3951]: userd.go:93: Starting snap userd
Jun 16 16:24:52 dave-Vostro-3558 cinnamon[2709]: JS LOG: [LookingGlass/info] Adding XAppStatusIcon:  (:1.69/org/x/StatusIcon/Icon_2)
Jun 16 16:25:52 dave-Vostro-3558 sudo[4711]:     dave : user NOT in sudoers ; TTY=pts/0 ; PWD=/home/dave ; USER=root ; COMMAND=/usr/sbin/usermod -aG >
~
~
~
~
~
~
~
~
~
~
~
~
~
It looks like your user does not have sudo privileges. You can try logging in as the root user or another user with sudo privileges and then add your user to the sudo group.

Alternatively, you can try adding your user to the sudo group manually by booting into recovery mode. Here are the steps to do this:

1. Reboot your system and press the Shift key at boot to access the GRUB menu.
2. Select the option to boot into recovery mode.
3. Select the option to drop into a root shell prompt.
4. Run the command:

Code:
mount -o remount,rw /

This will remount your filesystem as read-write.
5. Then run the command:

Code:
usermod -aG sudo username

Replace "username" with your actual username.
6. Reboot your system.

After rebooting, try installing software again and see if the issue is resolved.
 


Top