[Ubuntu-x-swat] [Bug 1885363] Re: Screen flickers after waking up from suspend
** Tags added: amdgpu ** Summary changed: - Screen flickers after waking up from suspend + [amdgpu] Screen flickers after waking up from suspend ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1885363 Title: [amdgpu] Screen flickers after waking up from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885363/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs
I have the same problem on Ubuntu 20.10 using 440.100 driver. VLC + Thunar on a single user system fills up the syslog. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1846374 Title: Having a video playing/paused when switched to another user generates gigabytes of error logs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1875189] Re: [amdgpu] Screen Flickers when it wakes from suspend/sleep.
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875189 Title: [amdgpu] Screen Flickers when it wakes from suspend/sleep. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875189/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1875189] Re: [amdgpu] Screen Flickers when it wakes from suspend/sleep.
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875189 Title: [amdgpu] Screen Flickers when it wakes from suspend/sleep. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875189/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1875189] Re: [amdgpu] Screen Flickers when it wakes from suspend/sleep.
[Expired for xserver-xorg-video-amdgpu (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875189 Title: [amdgpu] Screen Flickers when it wakes from suspend/sleep. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875189/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1885334] Re: Nvidia kernel crashes when running World of Warcrat with wine/vulkan
** Summary changed: - Crashes when running World of Warcrat with wine/vulkan + Nvidia kernel crashes when running World of Warcrat with wine/vulkan ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-440 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1885334 Title: Nvidia kernel crashes when running World of Warcrat with wine/vulkan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1885334/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1885463] Re: display and input freeze
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1885463 Title: display and input freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1885463/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1885463] [NEW] display and input freeze
You have been subscribed to a public bug: Newly installed Ubuntu on a Lenovo laptop - less than 24 hours old. Just now, I revived laptop from sleep or hibernate and the display was frozen and corrupted. The bottom 1/3 of display was a patchwork of small squares of junk in green, pink, blue; top 2/3 of screen was a slightly distorted version of the default orange/purple background and the clock. I couldn't interact with the computer with mouse or keyboard - no mouse pointer, no control-alt-delete, no control-backspace. I found alt-PrtSc- reisub on google and was able to reboot from the keyboard. I'm running 18.04.4 LTS, on 2017ish Lenovo E450 with AMD Carrizo graphics card ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18 Uname: Linux 4.15.0-108-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 28 18:33:57 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev cb) (prog-if 00 [VGA controller]) Subsystem: Lenovo Radeon R5 Graphics [17aa:5118] MachineType: LENOVO 20H4CTO1WW ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-108-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: LENOVO dmi.bios.version: R0EET41W (1.15) dmi.board.asset.tag: Not Available dmi.board.name: 20H4CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0EET41W(1.15):bd06/06/2017:svnLENOVO:pn20H4CTO1WW:pvrThinkPadE475:rvnLENOVO:rn20H4CTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E475 dmi.product.name: 20H4CTO1WW dmi.product.version: ThinkPad E475 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze ubuntu -- display and input freeze https://bugs.launchpad.net/bugs/1885463 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1885278] Re: Black screen after standby on Intel NUC
To help us confirm if this is a Xorg bug, please try selecting 'Ubuntu on Wayland' from the login screen. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1885278 Title: Black screen after standby on Intel NUC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1885278/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1885272] Re: Re-logging occurs continuously during ubuntu operation
*** This bug is a duplicate of bug 1878193 *** https://bugs.launchpad.net/bugs/1878193 ** This bug has been marked a duplicate of bug 1878193 Shell crashes and returns to the login screen -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1885272 Title: Re-logging occurs continuously during ubuntu operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1885272/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1885435] [NEW] The wrong sequence of mouse events can render the whole system unusable
Public bug reported: This is 100% reproducible with any window, I'll use a terminal window as an example. Steps to reproduce: - open a terminal window (again, this could be a Gedit, Nautilus window or any other window) - make sure the window is not maximized - Place the mouse cursor at the center of the right border of the window, press the mouse left button and don't release it, so as to resize the window by dragging its right border - While dragging the terminal window's right border, press and hold the mouse right button too (remember you're still holding the left button too) - While still holding both mouse buttons pressed, move the mouse cursor away from the border of the window fast. If you move it fast enough, at some point the border will stop following the mouse cursor (which wouldn't happen if you hadn't pressed both buttons). - While the mouse cursor is outside the terminal winow, release the right button and then the left button. Now you are no longer holding any mouse button pressed - move the mouse cursor to the left and to right "crossing" the terminal window border, that is, move the mouse inside and outside the terminal window. Notice how, whenever the cursor "crosses" the window's right border, the border nonsensically moves a little bit following the movements of the cursor for a fraction of a second, as if you were still dragging it, but then it stops following the cursor. This is the first sign that something has gone completely berserk, but it's still nothing compared to what is coming - while the mouse cursor is outside of the offending window (i.e. the terminal window in our example), click on something outside of it. For example, in my case that's a maximized Chrome window that's behind. Observed disaster: now you are unable to do anything with the mouse. Try clicking on any window to move, close, or resize it. Try to click on stuff to give it focus. Try to click on Launcher icons. None of this has any effect. It's as if your mouse buttons dead. Not even by trying to go back to the original window and press and release the mouse buttons in any particular order while the cursor is over the window border seems to allow you to "unlock" the system. There's no way to recover from this situation except by KILLING the offending window without using the mouse. For example, by using alt+tab as many time as needed to give it focus, and then, since in this case it is a terminal, typing "exit" and hitting Enter, so the window gets closed and normal functioning of the mouse gets restored. If the offending window is not a terminal window, then you can hit Ctrl+Alt+T to open a new terminal, and then use a "kill" or "killall" command to kill the process that owns the offending window. Both of these imply loss of any unsaved work. This is a fucking disaster and an incredibly stupid bug of the kind that you usually observe in "software" written by novice programmers (or rather, non-programmers such as web designers playing around with javascript) who write their first programs with mouse events (press, release, rollover, etc) and forget to take into account all possible sequences of events. Seriously, I hadn't seen such stupid mouse behavior bugs outside of the scope of amateur website UIs. Fucking unbelievable. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.12) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Jun 28 17:28:05 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2451 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-179-generic
