[Bug 1639180] Re: no login possible after update to nvidia 304.132

I installed 304.135-0ubuntu0.16.04.1 on 16.04.2. Works flawlessly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notificati

[Bug 1639180] Re: no login possible after update to nvidia 304.132

Installing version 340 is not suitable for my graphics card. I need the 304 series. Downgrade from 304.132 to 304.131: - CTRL+ALT+1 to console - login - sudo apt-get remove nvidia* - sudo apt-get autoremove - sudo apt-get install nvidia-304=304.131-0ubuntu3 -- You received this bug notification

[Bug 1639180] Re: no login possible after update to nvidia 304.132

Sorry, there is a error in my comment 17. correction: Downgrade from 304.132 to 304.131: - CTRL+ALT+F1 to console - login - sudo apt-get remove nvidia* - sudo apt-get autoremove - sudo apt-get install nvidia-304=304.131-0ubuntu3 - reboot And prevent updates of the driver like shown in comment 18.

[Bug 1558768] [NEW] gvfsd-trash causing high CPU-load when try to empty trash with thousands of files

Public bug reported: - Ubuntu 16.04 (Xenial Xerus) Daily Build - AMD64 - Unity Steps to reproduce: - a folder with thousands of files (here about 15000 files with a overall size of 1.5 GB) - delete files to trash - right-click at the trash icon - click empty trash A dialog "Dateioperationen" sh

[Bug 1558768] Re: gvfsd-trash causing high CPU-load when try to empty trash with thousands of files

** Package changed: ubuntu => gvfs (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558768 Title: gvfsd-trash causing high CPU-load when try to empty trash with thousands of files To manag

[Bug 1639180] [NEW] no login possible after update to nvidia 304.132

Public bug reported: Ubuntu 16.04 LTS NVIDIA driver: - nvidia-graphics-drivers-304 - update to version 304.132 dpkg.log: upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2 - reboot - lightdm login screen - login - a few seconds some flickering - and the lightdm login scr

[Bug 1639180] Re: no login possible after update to nvidia 304.132

bug report created with sudo nvidia-bug-report.sh as suggested at comment 6 for bug 1639180 ** Attachment added: "nvidia-bug-report.log.gz" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+attachment/4772583/+files/nvidia-bug-report.log.gz -- You received t

[Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!

** Package changed: linux (Ubuntu) => linux-hwe-5.11 (Ubuntu) ** Changed in: linux-hwe-5.11 (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931001 Title

[Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!

I also have this problem. After the automatic update from kernel 5.8 to 5.11 this error occurs. The error only occurs during a cold boot. When rebooting the system, this error does not occur. Here an interesting thread about this problem: https://bbs.minisforum.com/threads/ubuntu-stuck-booting.1

[Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!

** Changed in: linux-hwe-5.13 (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu)