[Ubuntu-x-swat] [Bug 1845102] Re: Video flicker on triggering OSD in Xorg (but not Wayland)
*** This bug is a duplicate of bug 1828697 *** https://bugs.launchpad.net/bugs/1828697 OK, since we're back to just the flicker issue then we should use bug 1828697. Because it is older, but also because it is not confused by the tearing issue mentioned here. ** This bug has been marked a duplicate of bug 1828697 Volume and brightness OSD make full-screen video flicker once they disappear -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1845102 Title: Video flicker on triggering OSD in Xorg (but not Wayland) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-mpv/+bug/1845102/+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 1845102] Re: Video flicker on triggering OSD in Xorg (but not Wayland)
P.S. This might also be a security issue. I've noticed that the frame that's stuck inside the flicker reappears when I shut down / restart my computer. That's a potential security issue because you might not be the only person using your computer and all of a sudden this errant frame of video pops up. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1845102 Title: Video flicker on triggering OSD in Xorg (but not Wayland) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-mpv/+bug/1845102/+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 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken
Launchpad has imported 22 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1725499. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2019-06-30T22:05:33+00:00 ubizjak wrote: Created attachment 1586097 Xorg log file Description of problem: After update of xorg-x11-server-common and xorg-x11-server-Xorg packages to version 1.20.5-3.fc30, the tooltips got corrupted in KDE. Version-Release number of selected component (if applicable): xorg-x11-server-Xorg (1.20.5-3.fc30) xorg-x11-server-common (1.20.5-3.fc30) How reproducible: Always. Steps to Reproduce: 1. Hoover the mouse pointer over the tool. 2. 3. Actual results: Corrupted tooltip. Expected results: Additional info: $ uname -a Linux localhost.localdomain 5.1.15-300.fc30.x86_64 #1 SMP Tue Jun 25 14:07:22 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Extended renderer info (GLX_MESA_query_renderer): Vendor: X.Org (0x1002) Device: AMD CYPRESS (DRM 2.50.0 / 5.1.15-300.fc30.x86_64, LLVM 8.0.0) (0x6898) Version: 19.0.6 Accelerated: yes Video memory: 1024MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 4.3 Max compat profile version: 3.1 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.1 I have rolled back the above packages to 1.20.4-3.fc30, where everything works OK. Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841718/comments/0 On 2019-07-01T19:58:54+00:00 ubizjak wrote: Created attachment 1586435 Screenshot of the corrupted tooltip Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841718/comments/1 On 2019-07-04T02:00:09+00:00 robin.a.meade wrote: Corruption happens to me on Gnome on Fedora 30 after the update from: xorg-x11-server-Xorg-1.20.4-3.fc30 xorg-x11-server-common-1.20.4-3.fc30.x86_64 to: xorg-x11-server-Xorg-1.20.5-3.fc30.x86_64 xorg-x11-server-common-1.20.5-3.fc30.x86_64 I get corrupted icons in Gnome's top panel (specifically the Quake and Dropbox icons (I use the topicons-plus Gnome extension)). I also get corrupted tooltips in Firefox, e.g., hovering my mouse over my account circle in GMail produces corruption similar to the screenshot shown on this bug. As suggested by OP, downgrading xorg made the problem go away: $ glxinfo -B name of display: :0 display: :0 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: X.Org (0x1002) Device: AMD TURKS (DRM 2.50.0 / 5.1.15-300.fc30.x86_64, LLVM 8.0.0) (0x6740) Version: 19.0.8 Accelerated: yes Video memory: 1024MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 3.3 Max compat profile version: 3.1 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.1 ... A comment on a different bug describes a similar problem, and he has an AMD card as well: https://bugzilla.redhat.com/show_bug.cgi?id=1726419#c1 Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841718/comments/2 On 2019-07-04T06:52:18+00:00 ofourdan wrote: Can you please try if either of these two scratch (test) builds fix the issue: xorg-x11-server-1.20.5-3.1test.fc30 https://koji.fedoraproject.org/koji/taskinfo?taskID=36015101 or: xorg-x11-server-1.20.5-3.2test.fc30 https://koji.fedoraproject.org/koji/taskinfo?taskID=36027647 And report if either fix the corruption issue? Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841718/comments/3 On 2019-07-04T10:26:05+00:00 ubizjak wrote: (In reply to Olivier Fourdan from comment #3) > Can you please try if either of these two scratch (test) builds fix the I will be away from the keyboard today, but will report tomorrow (friday) afternoon. Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841718/comments/4 On 2019-07-04T18:19:26+00:00 bugzilla_acct_1959 wrote: (In reply to Olivier Fourdan from comment #3) > Can you please try if either of these two scratch (test) builds fix the > issue: > > xorg-x11-server-1.20.5-3.1test.fc30 > https://koji.fedoraproject.org/koji/taskinfo?taskID=36015101 > > or: > > xorg-x11-server-1.20.5-3.2test.fc30 > https://koji.fedoraproject.org/koji/taskinfo?taskID=36027647 > > And report if either fix the corruption issue? I have the same tooltip corruption issues under cinnamon. xorg-x11-server-1.20.5-3.1test.fc30 DOES fix
[Ubuntu-x-swat] [Bug 1845102] Re: Video flicker on triggering OSD in Xorg (but not Wayland)
@vanvugt The tearing's a nonissue now so it makes sense to refashion this report to deal with the flicker only. I'd really rather not shirk this report with the traction it's received. Re #19, just the one screen. But that makes no difference either. I have a multiple screen setup on a different computer and this happens there too. It happens everywhere, regardless of hardware. It also happens with all the extensions and modes are pulled out. It happens regardless of what theme or what shell theme I use. And I haven't been able to reproduce this issue on Arch, Fedora Rawhide or Manjaro. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1845102 Title: Video flicker on triggering OSD in Xorg (but not Wayland) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-mpv/+bug/1845102/+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 1694367] Re: Screen tearing in 16.10 onwards
Launchpad has imported 20 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=101229. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2017-05-30T06:31:18+00:00 Paul wrote: Created attachment 131571 glxinfo System exhibits uncontrolled screen-tearing that can be seen when moving windows, watching videos or playing games, or any graphical movement in general. The tearing gradually shifts up or down the screen, suggesting its a cycle frequency miss-match (or floating-point error). Has affected mesa 12 and kernel 4.8 onwards. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1694367/comments/1 On 2017-05-30T07:47:20+00:00 Michel Dänzer wrote: Please attach the Xorg log file and the output of xrandr and dmesg corresponding to the problem. Can you create a video demonstrating the problem when moving windows? If not, please describe which desktop environment / window manager / compositing manager you're using. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1694367/comments/2 On 2017-05-30T22:27:27+00:00 Paul wrote: Created attachment 131583 xorg Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1694367/comments/3 On 2017-05-30T22:28:00+00:00 Paul wrote: Created attachment 131584 display modes Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1694367/comments/4 On 2017-05-30T22:28:47+00:00 Paul wrote: Created attachment 131585 dmesg | radeon Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1694367/comments/5 On 2017-05-30T22:41:49+00:00 Paul wrote: (In reply to Michel Dänzer from comment #1) > Can you create a video demonstrating the problem when moving windows? If > not, please describe which desktop environment / window manager / > compositing manager you're using. Don't think I can show a video as I don't have a high-end camera or capture card, but it affects vanilla Kubuntu 16.10 and 17.04 at least. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1694367/comments/6 On 2017-05-31T03:30:20+00:00 Michel Dänzer wrote: Which rendering backend and tearing prevention method are selected in the kwin settings? Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1694367/comments/7 On 2017-05-31T22:16:36+00:00 Paul wrote: (In reply to Michel Dänzer from comment #6) > Which rendering backend and tearing prevention method are selected in the > kwin settings? XRender and auto, I have tried the full-repaint but it didn't seem to have an effect. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1694367/comments/8 On 2017-06-01T03:13:38+00:00 Michel Dänzer wrote: To prevent tearing, you need to either choose OpenGL instead of XRender and an appropriate tearing prevention setting, or enable TearFree with xrandr --output eDP --set TearFree on Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1694367/comments/9 On 2017-06-06T01:06:57+00:00 Paul wrote: (In reply to Michel Dänzer from comment #8) > To prevent tearing, you need to either choose OpenGL instead of XRender and > an appropriate tearing prevention setting, or enable TearFree with > > xrandr --output eDP --set TearFree on it's less obvious, but there still appears to be screen tearing when running via openGL 3.1 using full-screen-repaints. It's also reasonably obvious that for some GUIs their buttons will update their two triangles across two frames instead of one, this seems to be a much rarer occurrence with the above settings however. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1694367/comments/10 On 2017-06-06T01:19:30+00:00 Michel Dänzer wrote: (In reply to Paul from comment #9) > it's less obvious, but there still appears to be screen tearing How does that manifest, and when you do what? > when running via openGL 3.1 using full-screen-repaints. FWIW, since DRI3 is enabled, "Re-use screen content" is the most efficient setting. > It's also reasonably obvious that for some GUIs their buttons will update > the
[Ubuntu-x-swat] [Bug 1813162] Re: package libomp5-7 1:7.0.1-4 failed to install/upgrade: trying to overwrite shared '/usr/lib/llvm-7/lib/libomp-7.so.5', which is different from other instances of pack
[Expired for llvm-toolchain-7 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: llvm-toolchain-7 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to llvm-toolchain-7 in Ubuntu. https://bugs.launchpad.net/bugs/1813162 Title: package libomp5-7 1:7.0.1-4 failed to install/upgrade: trying to overwrite shared '/usr/lib/llvm-7/lib/libomp-7.so.5', which is different from other instances of package libomp5-7:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-7/+bug/1813162/+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 1821120] Re: package libllvm7 (not installed) failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/lib/x86_64-linux-gnu/libLLVM-7.so.1' a '/usr/lib/x86_6
[Expired for llvm-toolchain-7 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: llvm-toolchain-7 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to llvm-toolchain-7 in Ubuntu. https://bugs.launchpad.net/bugs/1821120 Title: package libllvm7 (not installed) failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/lib/x86_64-linux- gnu/libLLVM-7.so.1' a '/usr/lib/x86_64-linux-gnu/libLLVM-7.so.1.dpkg- new': fin de fichero o de flujo inesperado To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-7/+bug/1821120/+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 1846090] Re: GDX1505:00 27C6:01F1 Touchpad Screenpad support
Do you mean the screen doesn't light up, or the touchpad is unresponsive? Certainly the attached files suggest the second screen is not seen as connected or powered on. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - GDX1505:00 27C6:01F1 Touchpad Screenpad support + Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad Screenpad support -- 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/1846090 Title: Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad Screenpad support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846090/+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 1846090] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1846090 Title: Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad Screenpad support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846090/+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 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken
** Bug watch added: Red Hat Bugzilla #1725499 https://bugzilla.redhat.com/show_bug.cgi?id=1725499 ** Also affects: xserver-xorg-video-ati (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1725499 Importance: Unknown Status: Unknown ** Also affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New ** No longer affects: gtk+3.0 (Ubuntu Eoan) ** No longer affects: gtk+3.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1841718 Title: [radeon] Rendering of combo boxes and tooltips is broken To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1841718/+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 1845102] Re: Video flicker on triggering OSD in Xorg (but not Wayland)
Wait a minute... How many monitors are you running? Just one or multiple? ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Changed in: mpv (Ubuntu) Status: Confirmed => Incomplete ** Changed in: vlc (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1845102 Title: Video flicker on triggering OSD in Xorg (but not Wayland) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-mpv/+bug/1845102/+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 1792167] Re: Display size detected incorrectly
To be absolutely sure you would need to: 1. Convert the display's EDID into binary from hex: 00004c2d09050100 30120103801009780aee91a3544c9926 0f5054bdef80714f8100814081809500 950fb3000101023a801871382d40582c 4500a05a001e662150b051001b30 40703600a05a001e00fd0018 4b1a5117000a20202020202000fc 0053414d53554e470a2020202020016f 020327f14b901f041305140312202122 230907078301e2000fe305030167 030c001000b82d011d007251d01e206e 285500a05a001e011d00bc52d01e 20b8285540a05a001e011d801871 1c1620582c2500a05a009e011d80 d0721c1620102c2580a05a009e00 001d 2. Use an EDID decoding tool to verify it yourself. Some are available in the Ubuntu archive, but also you can google for online EDID decoders. ** No longer affects: xrandr (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xrandr in Ubuntu. https://bugs.launchpad.net/bugs/1792167 Title: Display size detected incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+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 1257612] Re: divide by zero error in radeon_surface.c when opening chrome with WebGL enabled
** Changed in: nouveau Status: Confirmed => Unknown ** Bug watch added: gitlab.freedesktop.org/mesa/drm/issues #12 https://gitlab.freedesktop.org/mesa/drm/issues/12 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1257612 Title: divide by zero error in radeon_surface.c when opening chrome with WebGL enabled To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1257612/+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 1257612]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/drm/issues/12. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1257612 Title: divide by zero error in radeon_surface.c when opening chrome with WebGL enabled To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1257612/+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 1846113] Re: Xwayland crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1843987 *** https://bugs.launchpad.net/bugs/1843987 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1843987, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1846113/+attachment/5292937/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1846113/+attachment/5292940/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1846113/+attachment/5292948/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1846113/+attachment/5292950/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1846113/+attachment/5292951/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1846113/+attachment/5292952/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1846113/+attachment/5292953/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1843987 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1846113 Title: Xwayland crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1846113/+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 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa
This bug was fixed in the package linux - 4.15.0-65.74 --- linux (4.15.0-65.74) bionic; urgency=medium * bionic/linux: 4.15.0-65.74 -proposed tracker (LP: #1844403) * arm64: large modules fail to load (LP: #1841109) - arm64/kernel: kaslr: reduce module randomization range to 4 GB - arm64/kernel: don't ban ADRP to work around Cortex-A53 erratum #843419 - arm64: fix undefined reference to 'printk' - arm64/kernel: rename module_emit_adrp_veneer->module_emit_veneer_for_adrp - [config] Remove CONFIG_ARM64_MODULE_CMODEL_LARGE * CVE-2018-20976 - xfs: clear sb->s_fs_info on mount failure * br_netfilter: namespace sysctl operations (LP: #1836910) - net: bridge: add bitfield for options and convert vlan opts - net: bridge: convert nf call options to bits - netfilter: bridge: port sysctls to use brnf_net - netfilter: bridge: namespace bridge netfilter sysctls - netfilter: bridge: prevent UAF in brnf_exit_net() * tuntap: correctly set SOCKWQ_ASYNC_NOSPACE (LP: #1830756) - tuntap: correctly set SOCKWQ_ASYNC_NOSPACE * Bionic update: upstream stable patchset 2019-08-30 (LP: #1842114) - HID: Add 044f:b320 ThrustMaster, Inc. 2 in 1 DT - MIPS: kernel: only use i8253 clocksource with periodic clockevent - mips: fix cacheinfo - netfilter: ebtables: fix a memory leak bug in compat - ASoC: dapm: Fix handling of custom_stop_condition on DAPM graph walks - bonding: Force slave speed check after link state recovery for 802.3ad - can: dev: call netif_carrier_off() in register_candev() - ASoC: Fail card instantiation if DAI format setup fails - st21nfca_connectivity_event_received: null check the allocation - st_nci_hci_connectivity_event_received: null check the allocation - ASoC: ti: davinci-mcasp: Correct slot_width posed constraint - net: usb: qmi_wwan: Add the BroadMobi BM818 card - qed: RDMA - Fix the hw_ver returned in device attributes - isdn: mISDN: hfcsusb: Fix possible null-pointer dereferences in start_isoc_chain() - netfilter: ipset: Fix rename concurrency with listing - isdn: hfcsusb: Fix mISDN driver crash caused by transfer buffer on the stack - perf bench numa: Fix cpu0 binding - can: sja1000: force the string buffer NULL-terminated - can: peak_usb: force the string buffer NULL-terminated - net/ethernet/qlogic/qed: force the string buffer NULL-terminated - NFSv4: Fix a potential sleep while atomic in nfs4_do_reclaim() - HID: input: fix a4tech horizontal wheel custom usage - SMB3: Kernel oops mounting a encryptData share with CONFIG_DEBUG_VIRTUAL - net: cxgb3_main: Fix a resource leak in a error path in 'init_one()' - net: hisilicon: make hip04_tx_reclaim non-reentrant - net: hisilicon: fix hip04-xmit never return TX_BUSY - net: hisilicon: Fix dma_map_single failed on arm64 - libata: have ata_scsi_rw_xlat() fail invalid passthrough requests - libata: add SG safety checks in SFF pio transfers - x86/lib/cpu: Address missing prototypes warning - drm/vmwgfx: fix memory leak when too many retries have occurred - perf ftrace: Fix failure to set cpumask when only one cpu is present - perf cpumap: Fix writing to illegal memory in handling cpumap mask - perf pmu-events: Fix missing "cpu_clk_unhalted.core" event - selftests: kvm: Adding config fragments - HID: wacom: correct misreported EKR ring values - HID: wacom: Correct distance scale for 2nd-gen Intuos devices - Revert "dm bufio: fix deadlock with loop device" - ceph: don't try fill file_lock on unsuccessful GETFILELOCK reply - libceph: fix PG split vs OSD (re)connect race - drm/nouveau: Don't retry infinitely when receiving no data on i2c over AUX - gpiolib: never report open-drain/source lines as 'input' to user-space - userfaultfd_release: always remove uffd flags and clear vm_userfaultfd_ctx - x86/retpoline: Don't clobber RFLAGS during CALL_NOSPEC on i386 - x86/apic: Handle missing global clockevent gracefully - x86/CPU/AMD: Clear RDRAND CPUID bit on AMD family 15h/16h - x86/boot: Save fields explicitly, zero out everything else - x86/boot: Fix boot regression caused by bootparam sanitizing - dm kcopyd: always complete failed jobs - dm btree: fix order of block initialization in btree_split_beneath - dm space map metadata: fix missing store of apply_bops() return value - dm table: fix invalid memory accesses with too high sector number - dm zoned: improve error handling in reclaim - dm zoned: improve error handling in i/o map code - dm zoned: properly handle backing device failure - genirq: Properly pair kobject_del() with kobject_add() - mm, page_owner: handle THP splits correctly - mm/zsmalloc.c: migration can leave pages in ZS_EMPTY indefinitely - mm/zsmalloc.c: fix race condition in zs_destroy_pool - xfs: fix missing ILOCK unlock when xfs_setat
[Ubuntu-x-swat] [Bug 1846090] [NEW] GDX1505:00 27C6:01F1 Touchpad Screenpad support
Public bug reported: Ubuntu does not support asus zenbook pro UX580GD screenpad (touchpad and screen - all in one) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset 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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Oct 1 00:53:26 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.0.0-29-generic, x86_64: installed virtualbox, 5.2.32, 5.0.0-29-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1021] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:180e] InstallationDate: Installed on 2019-09-27 (3 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:5755 IMC Networks Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 003: ID 04f3:2544 Elan Microelectronics Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook Pro 15 UX550GDX_UX580GD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=4fba8275-1f29-4ddc-8a1c-e239d3b76c14 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550GDX.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550GDX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX550GDX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GDX_UX580GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook Pro dmi.product.name: ZenBook Pro 15 UX550GDX_UX580GD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages 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/1846090 Title: GDX1505:00 27C6:01F1 Touchpad Screenpad support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1846090/+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 1846094] [NEW] package nvidia-dkms-430 430.50-0ubuntu1 failed to install/upgrade: »installiertes nvidia-dkms-430-Skript des Paketes post-installation«-Unterprozess gab den Fehlerw
Public bug reported: E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 3989 (apt) - open (11: Die Ressource ist zur Zeit nicht verfügbar) N: Be aware that removing the lock file is not a solution and may break your system. E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-430 430.50-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Sep 30 20:56:20 2019 ErrorMessage: »installiertes nvidia-dkms-430-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 10 zurück InstallationDate: Installed on 2019-08-14 (47 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Python3Details: /usr/bin/python3.7, Python 3.7.4+, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: nvidia-graphics-drivers-430 Title: package nvidia-dkms-430 430.50-0ubuntu1 failed to install/upgrade: »installiertes nvidia-dkms-430-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 10 zurück UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-430 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1846094 Title: package nvidia-dkms-430 430.50-0ubuntu1 failed to install/upgrade: »installiertes nvidia-dkms-430-Skript des Paketes post- installation«-Unterprozess gab den Fehlerwert 10 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1846094/+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 1503426] Re: package libgl1-mesa-glx 10.1.3-0ubuntu0.5 failed to install/upgrade: 73.3516:subprocess installed post-installation script returned error exit status 2
best to close then ** Changed in: mesa (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1503426 Title: package libgl1-mesa-glx 10.1.3-0ubuntu0.5 failed to install/upgrade: 73.3516:subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1503426/+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 1751407] Re: package libegl1-mesa:amd64 17.2.8-0ubuntu0~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Setting up libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1) ... update-alternatives: error: cannot stat file '/usr/bin/java/jdk-9.0.4/bin/jar': Not a directory dpkg: error processing package libegl1-mesa:amd64 (--configure): subprocess installed post-installation script returned error exit status 2 ** Changed in: mesa (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1751407 Title: package libegl1-mesa:amd64 17.2.8-0ubuntu0~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1751407/+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 1770268] Re: [GeForce GTX 1080] 18.04 DisplayPort 15m cable no display
still the same with 18.04.3/19.04? ** Package changed: mesa (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1770268 Title: [GeForce GTX 1080] 18.04 DisplayPort 15m cable no display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770268/+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 881526] Re: AMD graphics hardware hangs with an homogeneous coloured screen or blank screen, and with chirp coming from the graphics card
closing as it's reported to be caused by overheating ** Changed in: mesa (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/881526 Title: AMD graphics hardware hangs with an homogeneous coloured screen or blank screen, and with chirp coming from the graphics card To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/881526/+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 1780842] Re: package libglx-mesa0 18.0.0~rc5-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLX_indirect.so.0', which is also in package nvi
*** This bug is a duplicate of bug 1753796 *** https://bugs.launchpad.net/bugs/1753796 ** This bug has been marked a duplicate of bug 1753796 Conflict between libglx-mesa and nvidia-390 on Ubuntu 18.04 (pre-release) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780842 Title: package libglx-mesa0 18.0.0~rc5-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLX_indirect.so.0', which is also in package nvidia-396 396.26-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1780842/+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 1846053] [NEW] Use llvm 9 or even llvm-10
Public bug reported: 1. llvm 9 has been released, but mesa in the repo still uses llvm 8. 2. llvm 9 bitcode libs for OpenCL cause llvm-8-based mesa to fail because their file format has changed 3. There was a bug in llvm-8-based mesa in disco that caused the OpenCL compiler to hang on the kernels combining hyperbolic and circular functions. There were no hang after I have rebuilt mesa and dri against llvm-10. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1846053 Title: Use llvm 9 or even llvm-10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1846053/+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 958891] Re: no tty, only blank screen with nvidia driver
https://askubuntu.com/q/1177674/21005 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/958891 Title: no tty, only blank screen with nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/958891/+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 1836630] Re: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend
Can you try the 430 driver from this PPA, please? (I have uploaded a fix for 18.04 and for 19.10) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1836630/+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 1836630] Re: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend
https://launchpad.net/~oem-solutions-group/+archive/ubuntu/nvidia- driver-staging -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1836630/+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 958891] Re: no tty, only blank screen with nvidia driver
I have the same problem with Xubuntu 18.04. Bug #1811402 The system boots using EFI v1.10 by Apple, but Grub is used, too. I wonder, how to switch to BIOS boot? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/958891 Title: no tty, only blank screen with nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/958891/+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 1792167] Re: Display size detected incorrectly
How can I check if the hardware is really sending faulty data or if it is just incorrectly parsed? ** Also affects: xrandr (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xrandr in Ubuntu. https://bugs.launchpad.net/bugs/1792167 Title: Display size detected incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+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 1844934] Re: screen jitter after long idle
atomic modesetting is disabled in eoan, btw -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1844934 Title: screen jitter after long idle To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1844934/+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 1844934] Re: screen jitter after long idle
Actually, the XorgLog.txt shows more definite problems: [181434.889] (WW) modeset(0): flip queue failed: Device or resource busy [181434.889] (WW) modeset(0): Page flip failed: Device or resource busy [181434.889] (EE) modeset(0): present flip failed [181434.989] (WW) modeset(0): flip queue failed: Device or resource busy [181434.989] (WW) modeset(0): Page flip failed: Device or resource busy [181434.989] (EE) modeset(0): present flip failed [181435.105] (WW) modeset(0): flip queue failed: Device or resource busy [181435.105] (WW) modeset(0): Page flip failed: Device or resource busy [181435.106] (EE) modeset(0): present flip failed [181435.205] (WW) modeset(0): flip queue failed: Device or resource busy [181435.205] (WW) modeset(0): Page flip failed: Device or resource busy [181435.205] (EE) modeset(0): present flip failed That might be Xorg's fault (comment #8) or it might be the kernel's fault. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1844934 Title: screen jitter after long idle To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1844934/+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 1844934] Re: screen jitter after long idle
Or it could be the framebuffer compression or other power saving things. Since the last relevant kernel message is: [180893.945295] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Does TLP tweak anything in that area? And does the bug occur without TLP? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1844934 Title: screen jitter after long idle To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1844934/+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 1844609] Re: my screen flickering
Yes the kernel log (CurrentDmesg.txt) suggests a disk is faulty so you should replace that before doing anything else... Then if the screen flickering persists please attach a video of the problem here so we can better understand what you mean. ** Package changed: xorg (Ubuntu) => 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/1844609 Title: my screen flickering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1844609/+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 1697373] Re: [screensaver] Screen blanks during video playback in Chrome and Firefox under Xwayland
its problem with vlc as well; I'm neither using wayland. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1697373 Title: [screensaver] Screen blanks during video playback in Chrome and Firefox under Xwayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1697373/+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 1844860] Re: Freezing system
The kernel log suggests the nouveau kernel driver is having trouble: [ 5703.539644] nouveau :00:0d.0: bus: MMIO write of 052a0001 FAULT at 00b000 [ 5704.875835] nouveau :00:0d.0: bus: MMIO write of 05270001 FAULT at 00b010 [ 5705.738769] nouveau :00:0d.0: bus: MMIO write of 05270001 FAULT at 00b010 [ 5705.740773] nouveau :00:0d.0: bus: MMIO write of 05270001 FAULT at 00b010 [ 5712.157743] rfkill: input handler disabled [ 5713.532579] nouveau :00:0d.0: bus: MMIO write of 08c70001 FAULT at 00b020 [ 5723.226473] nouveau :00:0d.0: bus: MMIO write of 0a4c0001 FAULT at 00b030 [ 5723.241081] nouveau :00:0d.0: bus: MMIO write of FAULT at 00b030 [ 5763.349926] nouveau :00:0d.0: bus: MMIO write of 0c450001 FAULT at 00b030 [ 5767.257346] nouveau :00:0d.0: bus: MMIO write of FAULT at 00b030 [ 5860.400801] nouveau :00:0d.0: bus: MMIO write of 0a4e0001 FAULT at 00b030 [ 5860.462603] nouveau :00:0d.0: bus: MMIO write of FAULT at 00b030 [ 5877.109887] nouveau :00:0d.0: bus: MMIO write of 0a4e0001 FAULT at 00b030 [ 5877.130526] nouveau :00:0d.0: bus: MMIO write of FAULT at 00b030 To verify if that is the main problem, please try installing the proprietary Nvidia driver instead via: Software & Updates > Additional Drivers > ... ** Tags added: nouveau ** Summary changed: - Freezing system + [nouveau] Freezing system ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: 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/1844860 Title: [nouveau] Freezing system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1844860/+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 1772512] Re: Unable to install i386 and amd64 arch at the same time
https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1772512/comments/6 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1772512 Title: Unable to install i386 and amd64 arch at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1772512/+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 1844934] Re: screen jitter after long idle
This looks like another atomic mode setting problem. To test this theory, please try 'Ubuntu on Wayland' and tell us if it avoids the jitter. If so, then this Xorg fix from Intel is probably what we want to keep an eye on: https://gitlab.freedesktop.org/xorg/xserver/merge_requests/180 I keep seeing bug reports like this from time to time. Not too often, and I think Xorg's buggy atomic modesetting implementation could be the cause. ** 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/1844934 Title: screen jitter after long idle To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1844934/+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 1845076] Re: Gnome shell/Xorg freeze after remote connection with monitor unplugged
It appears the freeze was due to a crash mentioned in your kernel: [ 551.339814] gnome-shell[1798]: segfault at 4400 ip 7f29b593b9e1 sp 7ffe617a1710 error 4 in libmutter-2.so.0.0.0[7f29b58b+158000] [ 551.339837] Code: 00 4c 89 e2 48 89 ee 48 89 df e8 fa 04 fc ff 85 c0 74 5e 4c 8b 74 24 18 e8 4c b0 01 00 4d 85 f6 74 df 49 8b 0e 48 85 c9 74 05 <48> 39 01 74 0f 48 89 c6 4c 89 f7 e8 4f 14 fc ff 85 c0 74 c3 41 f6 therefore... Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags added: nouveau ** Summary changed: - Gnome shell/Xorg freeze after remote connection with monitor unplugged + [nouveau] Gnome shell/Xorg freeze after remote connection with monitor unplugged ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: mutter (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/1845076 Title: [nouveau] Gnome shell/Xorg freeze after remote connection with monitor unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845076/+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 1845373] Re: Problem with wine
** Package changed: xorg (Ubuntu) => wine (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/1845373 Title: Problem with wine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1845373/+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 1845356] Re: decolorisation on my laptop display
Could you describe the problem in more detail? Can you please attach a photo of the problem? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: 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/1845356 Title: decolorisation on my laptop display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1845356/+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 1845541] Re: OS becomes unresponsive when power is plugged in and battery is low
Please open a terminal and run 'top' in it to find out if any process is hogging the CPU when this happens. Tip: DON'T run gnome-system-monitor because it uses too many resources itself :) If no offending process is found then the next thing to check is for over-aggressive power management: 1. Make sure you don't have 'tlp' installed. 2. Install and run 'powetop' as root to see if your machine is being throttled to low frequency. ** Package changed: xorg-server (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1845541 Title: OS becomes unresponsive when power is plugged in and battery is low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1845541/+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
