I just upgraded my distribution to 19.04 – things apparently went well except I got a message that 'install-info' couldn't be updated. This message I have ignored so far. It seemed OK until I restarted the system and tried to log in. Now it won't accept my password any more and after maybe 10 seconds I end up at the login question again. And again. I know the password is still there, since logging in via ssh from another computer works like a charm. It is also NOT a capslock problem, I have tried enough times to eliminate that. Since I have an ssh connection, I can reproduce any log or system files if someone asks me.  But I'm flabbergasted - what on earth is the problem here? I have always upgraded as soon as a new Ubuntu has been out, but this is the first time I experience problems with it.  A little update: I just tried to reboot the machine via the ssh connection, and now the screen just shows the ubuntu logo with the five blinking dots under it. Nothing has happened for half an hour now, so I guess it's really stuck there. Seems serious this - is there anyone here who understands and possibly can assist me a bit?  Update again 13may19! I just upgraded my third (old-ish) laptop to Ubuntu 19.04, and couldn't log in there either. A bit of research showed that the problem was incompatible Gnome shell extensions. I insist on the Gnome shell (gives me the desktop I want), and disabling these extensions one-by-one finally gave me a working system. Learning? Yes indeed! This was a long process, and I'm happy I'm finally there!
1378
My Ubuntu is stuck in a login loop when trying to enter my desktop. When I login, the screen gets black and soon after that the login screen comes back.   I've read that the problem might be caused by an error depending on the graphics, here's my graphics card: ATI Radeon 7670M
84019
I am having a problem where when I try to run say GParted, when I am prompted for a password, it says "Incorrect Password"  But when I enter the same password using terminal sudo gparted for example, it works. Why is that?  UPDATE  I noticed that theres a difference between using sudo and gksu. The later will fail with incorrect password ...
106561
I'm subscribed to the Ubuntu Security Notes, so everytime that I receive an e-mail, a new update is avalable.  But in the last update, they wrote something in the end that I coudn't undertand much, so can anyone please tell me what does that means?  ATTENTION: Due to an unavoidable ABI change the kernel updates have been given a new version number, which requires you to recompile and reinstall all third party kernel modules you might have installed. If you use linux-restricted-modules, you have to update that package as well to get modules which work with the new kernel version. Unless you manually uninstalled the standard kernel metapackages (e.g. linux-generic, linux-server, linux-powerpc), a standard system upgrade will automatically perform this as well.   I tried to ask to my friend (who also uses Linux), but he don't know much about kernel.
59531
I upgraded to Ubuntu 19.04 from 17.10 and now I do not have anything on my desktop at all. I am running this on Virtual Box 6. I know enough about Unix to be dangerous, I just use it for developing websites.    From looking around various articles I have tried these commands as suggested but nothing has worked, any ideas?  From SSH I have tried these:  sudo apt-get install --reinstall ubuntu-desktop sudo apt install --reinstall gnome-shell-extension-desktop-icons sudo apt install --reinstall gnome
79995
The screen lock is not working, it does not lock the screen (no password required).  I would like it to prompt for a password every time the screen locks (clock screen).  All instructions tells me to enable this in privacy but I can not enable or disable as it's grey (gray).  Ubuntu 17.10 upgraded from Ubuntu 17.04, upgraded from Ubuntu 16.10.    Any help or advise would be great as I already tried many setting and installs and removes suggested on online.
63102
I'm not sure what's caused it. I haven't changed any system settings. The only thing I've done that may have broken something is updating my software. My update was: upgrade linux-generic-hwe-20.04:amd64 5.8.0.48.54~20.04.32 5.8.0.49.55~20.04.33 upgrade linux-image-generic-hwe-20.04:amd64 5.8.0.48.54~20.04.32  upgrade linux-headers-generic-hwe-20.04:amd64 5.8.0.48.54~20.04.32  upgrade linux-image-extra-virtual:amd64 5.4.0.70.73 5.4.0.71.74 upgrade linux-image-generic:amd64 5.4.0.70.73 5.4.0.71.74 upgrade linux-libc-dev:amd64 5.4.0-70.78 5.4.0-71.79 upgrade libseccomp2:amd64 2.4.3-1ubuntu3.20.04.3 2.5.1-1ubuntu1~20.04.1 upgrade nomachine:amd64 7.3.2-3 7.4.1-3```  Removing nomachine did not solve the problem. It was far worse before, I'm not sure how to describe exactly, but my entire screen's UI was glitching out. So I rebooted and that stopped, but now the terminal text looks like this:  I haven't changed any terminal settings. This seems to be occurring in the entire OS. Here is another example:  Not sure how to go about troubleshooting this? I don't have the time to reinstall the OS, nor do I think I should have to because this is just ridiculous and shouldn't happen. I'm not aware of anything I've done to make the system unstable. Edit Earlier I also tried booting the PC. It failed and got stuck on some command in a terminal (didn't manage to take a photo of what it said). So I rebooted into recovery mode with both available kernels. I was getting strange glitches like this:  That didn't work. So I rebooted the PC normally, and now I somehow logged in fine. Now I'm getting popups saying to report a system error. It says this:  Environment  Ubuntu 20.04.2 LTS GNOME 3.36.8  sudo lshw -class display   *-display        description: VGA compatible controller        product: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller        vendor: Intel Corporation        physical id: 2        bus info: pci@0000:00:02.0        version: 06        width: 64 bits        clock: 33MHz        capabilities: msi pm vga_controller bus_master cap_list rom        configuration: driver=i915 latency=0        resources: irq:33 memory:f7800000-f7bfffff memory:e0000000-efffffff ioport:f000(size=64) memory:c0000-dffff  I also did , which passed with 0 errors. Let me know if more details are required.
115352
Here is what I'm looking at. This isn't my computer. I repair PC's and I had an end user with this low powered laptop running XP so I decided to let him try out lubuntu. The install went smoothly with the non-PAE boot switch, but now I can't update anything. I'd rather not have to format and start over since he's spent time configuring his system. Any tips would be appreciated. I tried sudo apt-get clean, sudo apt-get install -f, sudo apt-get update. No go.  Also his touchpad stopped working, the wireless stopped working, the keyboard works in firefox but not chrome, and in firefox the address bar sometimes turns black and gray for some reason. I was hoping the update would help address some of this stuff.  Here's the message I get trying to update:  Get:1 http://us.archive.ubuntu.com/ubuntu/ trusty-proposed/main linux-image-3.13.0-26-generic i386 3.13.0-26.48 [14.6 MB] Get:2 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main linux-image-3.13.0-24-generic i386 3.13.0-24.47 [14.6 MB] Fetched 29.2 MB in 2min 19s (208 kB/s)                                          (Reading database ... 169286 files and directories currently installed.) Preparing to unpack .../linux-image-3.13.0-26-generic_3.13.0-26.48_i386.deb ... This kernel does not support a non-PAE CPU. dpkg: error processing archive /var/cache/apt/archives/linux-image-3.13.0-26-generic_3.13.0-26.48_i386.deb (--unpack):  subprocess new pre-installation script returned error exit status 1 Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.13.0-26-generic /boot/vmlinuz-3.13.0-26-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.13.0-26-generic /boot/vmlinuz-3.13.0-26-generic Preparing to unpack .../linux-image-3.13.0-24-generic_3.13.0-24.47_i386.deb ... This kernel does not support a non-PAE CPU. dpkg: error processing archive /var/cache/apt/archives/linux-image-3.13.0-24-generic_3.13.0-24.47_i386.deb (--unpack):  subprocess new pre-installation script returned error exit status 1 Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.13.0-24-generic /boot/vmlinuz-3.13.0-24-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.13.0-24-generic /boot/vmlinuz-3.13.0-24-generic Errors were encountered while processing:  /var/cache/apt/archives/linux-image-3.13.0-26-generic_3.13.0-26.48_i386.deb  /var/cache/apt/archives/linux-image-3.13.0-24-generic_3.13.0-24.47_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1)
48613
On login the password is accepted but I'm returned to the login screen. Tried multiple times even after reboot... same behavior.  I left my laptop (Lenovo Ideapad z510) in suspend mode (lid down) last night, but it did not resume this morning, as it usually does. It had shutdown or crashed, and on booting with Ubuntu the login failure mentioned above started.  cat ~/.xsession-errors /usr/sbin/lightdm-session: 1: /usr/sbin/lightdm-session: ls: not found /usr/sbin/lightdm-session: 104: exec: gnome-session: not found   Okay. I've tried a bunch of suggestions from    Changed id to /usr/sbin/id in /etc/profile removed .Xauthority removed /tmp removed,  purged and re-installed lightdm checked .profile for syntax errors (source .profile worked fine, so I guess no syntax errors)   Nothing worked. My guest login is working fine, so another user should also work. I'm now going to create another user and continue working, but a solution to this problem is still warranted... it's likely going to repeat in future.  Installing and reconfiguring gdm also did not work.  sudo apt-get install gdm
113624
I have just upgraded from Ubuntu 17.04 (Gnome flavor) to Ubuntu 17.10. All appears to have gone well in the upgrade, but I find after logging into either a gnome (wayland) gnome on xorg, ubuntu (wayland) or ubuntu on xorg, I lose all keyboard input. The mouse works fine, but keyboard fails to work at all. If I then logout of the session and return to gdm, the keyboard no longer works and so I cannot login to another session as I cannot enter any password.   I installed MATE and that works fine. I can login and the keyboard works fine. I also have stumpwm installed and that appears to work fine. So the problem seems to be Gnome specific either 'standard' gnome or Ubuntu flavoured gnome. Note that it was gnome I was using previously.   One other 'odd' bit of behaviour is that the main account I was using seems to have an additional session issue - when I try to log into this account, the desktop screen flashes up and then I'm returned straight back to the GDM login screen. This may be related to the fact I use zsh rather than bash as my shell on that account. I also see the same issue with keyboard e.g. once I have tried to login to that account and am returned to the gdm screen, I can no longer enter anything using the keyboard. Mouse works fine.   keyboard and mouse are both USB. This would appear to be something specific to Gnome and not related to the X server (or wayland) as other environments (stumpwm and MATE) work fine.   I did notice one other minor 'oddity'. I tried to use the on-screen keyboard. At first this seemed to be working, but then I noticed that when I tried to enter an '@' symbol, I just got a '2'. Something seems to be screwed up with input methods, but I quickly get out of my depth in this area. My region is set to English (Australia) with English (US) and English as fallbacks.   My next step will be to create a completely new/fresh account and see if that has any issues (in case the problem is due to some old gnome setting in .local, .cache .gnome etc.   Where to start to diagnose this issue?   UPDATE: I tried using a different keyboard and that seems to have resolved one problem. I can now login to a new account without loosing keyboard input for gnome or ubuntu sessions (wayland or xorg). So for some reason, the Logitech gaming keyboard I was using is not compatible with new versions of gnome (but still works fine under MATE). The replacement keyboard is an Apple aluminium USB, which seems to be working fine so far (though I have to yet verify alt/hyper etc all map correctly).   I still cannot login to accounts which existed previously with gnome or ubuntu sessions. I can login using MATE. This would seem to indicate there is something incompatible in the gnome environment beetween the gnome setup from 17.04 and 17.10. Still trying to work out what that might be.
41600
When updating I got the following message:  W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://dl.google.com/linux/chrome/deb stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6494C6D6997C215E W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6494C6D6997C215E W: Some index files failed to download. They have been ignored, or old ones used instead. Reading package lists... Done Building dependency tree        Reading state information... Done Calculating upgrade... Done   I'm on Ubuntu 16.04 and currently using Chrome 60.0.3112.90. Any suggestions? I'm also trying to install libimobiledevice but apparently the system is not reading the repository where I just added the PPA as I can't install it. Thanks in advance for any help.
72091
Yesterday (Jan. 3, 2018), I installed an OS update (Ubuntu 16.04), using the Software Center. My system isn't working correctly now. When my mouse rolls over the Launch bar, it disappears, then any open window disappears, leaving me with only the desktop screensaver showing. I can't even shut the computer off using the settings button on the top.  I went into the Terminal and attempted to fix it using the following commands:  sudo apt-get dist-upgrade sudo apt-get autoremove   But I'm still having the same problem.  I have reinstalled Ubuntu 16.04 and when I accepted the update on install had the same problem.  I have reinstalled it a second time but have not done an OS update and everything seems to be working fine.    Found another user with the same problem:    Is it possible that the Meltdown security update is at fault?  I've read the update has been issued for 64-bit x86 architecture ();  I'm running a 32 bit i386 architecture.  Could that be an issue and is there a way to correct it?
111788
I'm pretty new to running linux, but I know that 19.04 was released today and I wanted to upgrade from my current 18.10. However, when I follow the release notes here:  I get the message "The software on this computer is up to date". I made sure that my update settings are set to "any new version" and "normal" in the /etc/update-manager/release-upgrades file.   What am I doing wrong?  Thanks for the help!  Side note: I had to disable this PPA:  because it would cause errors in apt updating. Do I need to re-add it? If so how do I do so without it giving me an error?  Edit: I have followed the procedure recommended in the documentation which is identical to the suggested duplicate, but I am not given the option to upgrade. I have not yet tried the   do-release-upgrade -d    option as I don't want to upgrade to the developer version.
115920
I can boot into Ubuntu just fine as a guest but it refuses to accept my login name and password that were set during the Wubi install. I reinstalled it again with basic login and password just to make sure and it still won't let me in.
44478
I have upgraded Ubuntu to 12.04 and now I have a problem in logging in after locking the screen: it says the password is incorrect even though I provide the valid password. I found a temporary solution by switching users and logging in again with the same user.
9907
When I log into my Ubuntu terminal tty1, I get a message failed to connect to http://changelogs.ubuntu.com/meta-release  I try various things, then I get an error message telling me could not resolve us.archive.ubuntu.com  If I ping us.archive.ubuntu.com -c 4: ping: archive.ubuntu.com: name  or service not known  And the same message for sudo apt-get update. I did not set any proxy; I left it blank during install. My internet connectivity is apparently disabled and I could not configure it. I tried rebooting but nothing changed.
112556
I just put Ubuntu 15.04 on a flash drive using pendrivelinux, and when attempting to install it on my computer, it asks for a username and password.  What is the default username and password?  I haven't been able to find it anywhere on the web.  Thanks!
77770
When I connect via ssh to certain servers, it timeouts and "freezes" the terminal (doesn't accept input, doesn't disconnect, can't Ctrl-C to kill the ssh process or anything).  This is in Ubuntu's gnome-terminal though it seems to be pausing the terminal input/output, and doesn't affect the operation of the GNOME Terminal software itself.  So less a bug with gnome-terminal than an annoying inconsistency with ssh.  So, is there a way to prevent/regain the terminal from ssh connections that have timed out?