[Ubuntu-x-swat] [Bug 1855402] [NEW] [TGL] mesa support
Public bug reported: Description: this feature tracks the updates of mesa 3d for TGL support. We will update the commitid list as necessary Target Release: 20.10 Target version: TBD ** Affects: intel Importance: Undecided Status: New ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: intel-upkg-20.10 ** Also 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/1855402 Title: [TGL] mesa support To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1855402/+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 1853266] Re: xserver segfaults on GL_OUT_OF_MEMORY in libglamoregl
Launchpad has imported 24 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1648475. 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 2018-11-09T20:10:34+00:00 ikixxx wrote: Version-Release number of selected component: xorg-x11-server-Xwayland-1.20.3-1.fc29 Additional info: reporter: libreport-2.9.6 crash_function: OsLookupColor executable: /usr/bin/Xwayland kernel: 4.18.17-300.fc29.x86_64 runlevel: N 5 type: xorg uid:0 Truncated backtrace: 0: /usr/bin/Xwayland (OsLookupColor+0x13d) [0x55c99a7191ed] 1: /lib64/libpthread.so.0 (funlockfile+0x50) [0x7f89f9d7bfbf] 2: /usr/bin/Xwayland (glamor_get_pixmap_texture+0x81) [0x55c99a5c3f91] 3: /usr/bin/Xwayland (glamor_create_gc+0x70c8) [0x55c99a5d5068] 4: /usr/bin/Xwayland (glamor_create_gc+0x74fc) [0x55c99a5d580c] 5: /usr/bin/Xwayland (glamor_create_gc+0x7b0e) [0x55c99a5d5fae] 6: /usr/bin/Xwayland (glamor_create_gc+0x9b0c) [0x55c99a5d9c0c] 7: /usr/bin/Xwayland (DamageRegionAppend+0x6af) [0x55c99a686f3f] 8: /usr/bin/Xwayland (glamor_create_gc+0x10a02) [0x55c99a5e80e2] 9: /usr/bin/Xwayland (AddTraps+0x4275) [0x55c99a67c855] 10: /usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55c99a6e321e] 11: /usr/bin/Xwayland (InitFonts+0x3c6) [0x55c99a6e7246] 12: /lib64/libc.so.6 (__libc_start_main+0xf3) [0x7f89f9bc7413] 13: /usr/bin/Xwayland (_start+0x2e) [0x55c99a5b535e] Potential duplicate: bug 1617885 Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1853266/comments/0 On 2018-11-09T20:10:39+00:00 ikixxx wrote: Created attachment 1503848 File: backtrace Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1853266/comments/1 On 2018-11-09T20:10:40+00:00 ikixxx wrote: Created attachment 1503849 File: cpuinfo Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1853266/comments/2 On 2018-11-09T20:10:42+00:00 ikixxx wrote: Created attachment 1503850 File: dmesg Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1853266/comments/3 On 2018-11-09T20:10:43+00:00 ikixxx wrote: Created attachment 1503851 File: dso_list Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1853266/comments/4 On 2018-11-09T20:10:45+00:00 ikixxx wrote: Created attachment 1503852 File: etc_X11_xorg_conf_d.tar.gz Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1853266/comments/5 On 2018-11-09T20:10:46+00:00 ikixxx wrote: Created attachment 1503853 File: usr_share_xorg_conf_d.tar.gz Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1853266/comments/6 On 2019-02-05T12:42:38+00:00 harvos.arsen wrote: Description of problem: x11-server crushes from time to time without any obvious reason. I have single monitor. Version-Release number of selected component: xorg-x11-server-Xwayland-1.20.3-3.fc29 Additional info: reporter: libreport-2.9.7 crash_function: OsLookupColor executable: /usr/bin/Xwayland kernel: 4.18.16-300.fc29.x86_64 runlevel: N 5 type: xorg uid:0 Truncated backtrace: 0: /usr/bin/Xwayland (OsLookupColor+0x13d) [0x55ca3afbb26d] 1: /lib64/libpthread.so.0 (funlockfile+0x50) [0x7fef6568b07f] 2: /usr/bin/Xwayland (glamor_get_pixmap_texture+0x81) [0x55ca3ae66041] 3: /usr/bin/Xwayland (glamor_create_gc+0x70c8) [0x55ca3ae77118] 4: /usr/bin/Xwayland (glamor_create_gc+0x74fc) [0x55ca3ae778bc] 5: /usr/bin/Xwayland (glamor_create_gc+0x7b0e) [0x55ca3ae7805e] 6: /usr/bin/Xwayland (glamor_create_gc+0x9b0c) [0x55ca3ae7bcbc] 7: /usr/bin/Xwayland (DamageRegionAppend+0x6af) [0x55ca3af28fef] 8: /usr/bin/Xwayland (glamor_create_gc+0x10a02) [0x55ca3ae8a192] 9: /usr/bin/Xwayland (AddTraps+0x4275) [0x55ca3af1e915] 10: /usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55ca3af852ae] 11: /usr/bin/Xwayland (InitFonts+0x3c6) [0x55ca3af892e6] 12: /lib64/libc.so.6 (__libc_start_main+0xf3) [0x7fef654d6413] 13: /usr/bin/Xwayland (_start+0x2e) [0x55ca3ae5735e] Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1853266/comments/7 On 2019-02-05T13:13:19+00:00 ofourdan wrote: Can you please atthach the journalctl logs for
[Ubuntu-x-swat] [Bug 1853221] Re: Two monitors displaying same image
Your Xorg logs are showing: [ 4864.686] (WW) modeset(0): hotplug event: connector 93's link-state is BAD, tried resetting the current mode. You may be leftwith a black screen if this fails... where connector 93 is the DisplayPort. Please try a different monitor cable, or just replugging it. ** 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/1853221 Title: Two monitors displaying same image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853221/+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 1853328] Re: gdm-x-session loops printing its mode lines to syslog
** Package changed: gdm3 (Ubuntu) => xorg-server (Ubuntu) -- 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/1853328 Title: gdm-x-session loops printing its mode lines to syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853328/+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 1853266] Re: xserver segfaults on GL_OUT_OF_MEMORY in libglamoregl
[775834.395] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage [775834.395] (WW) glamor: Failed to allocate 5x5 FBO due to GL_OUT_OF_MEMORY. [775834.395] (WW) glamor: Expect reduced performance. [776320.877] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage [776320.877] (EE) [776320.877] (EE) Backtrace: [776320.878] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55fb3d66d889] [776320.878] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f1c7b03ef8f] [776320.878] (EE) 2: /usr/lib/xorg/modules/libglamoregl.so (glamor_get_pixmap_texture+0x7d) [0x7f1c7a61947d] [776320.879] (EE) 3: /usr/lib/xorg/modules/libglamoregl.so (glamor_create_gc+0x7bc8) [0x7f1c7a62bb28] [776320.879] (EE) 4: /usr/lib/xorg/modules/libglamoregl.so (glamor_create_gc+0x7fc8) [0x7f1c7a62c298] [776320.879] (EE) 5: /usr/lib/xorg/modules/libglamoregl.so (glamor_create_gc+0x860e) [0x7f1c7a62ca6e] [776320.879] (EE) 6: /usr/lib/xorg/modules/libglamoregl.so (glamor_create_gc+0xa656) [0x7f1c7a630766] [776320.879] (EE) 7: /usr/lib/xorg/Xorg (DamageRegionAppend+0x6af) [0x55fb3d5efaef] [776320.879] (EE) 8: /usr/lib/xorg/Xorg (AddTraps+0x3440) [0x55fb3d5e6950] [776320.879] (EE) 9: /usr/lib/xorg/Xorg (SendErrorToClient+0x35e) [0x55fb3d50e9fe] [776320.879] (EE) 10: /usr/lib/xorg/Xorg (InitFonts+0x3b6) [0x55fb3d5129c6] [776320.880] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f1c7ae64b6b] [776320.880] (EE) 12: /usr/lib/xorg/Xorg (_start+0x2a) [0x55fb3d4fc67a] [776320.880] (EE) [776320.880] (EE) Segmentation fault at address 0x0 [776320.880] (EE) Fatal server error: [776320.880] (EE) Caught signal 11 (Segmentation fault). Server aborting ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Tags added: disco ** Bug watch added: Red Hat Bugzilla #1648475 https://bugzilla.redhat.com/show_bug.cgi?id=1648475 ** Also affects: xorg-server (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1648475 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #647 https://gitlab.freedesktop.org/xorg/xserver/issues/647 ** Also affects: xorg-server via https://gitlab.freedesktop.org/xorg/xserver/issues/647 Importance: Unknown Status: Unknown -- 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/1853266 Title: xserver segfaults on GL_OUT_OF_MEMORY in libglamoregl To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1853266/+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 1853221] Re: Two monitors displaying same image
If a different monitor cable does not work then please try a different monitor if you can. There is some kind of hardware fault here. ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Invalid -- 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/1853221 Title: Two monitors displaying same image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853221/+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 1853221] Re: Two monitors displaying same image
Your kernel log also mentions problems with the same hardware: [ 1723.813855] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training [ 2612.326756] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training -- 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/1853221 Title: Two monitors displaying same image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853221/+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 1853328] [NEW] gdm-x-session loops printing its mode lines to syslog
You have been subscribed to a public bug: On waking from, generally a long sleep, my laptop loops in gdm. I get a continuous stream of: Nov 20 15:34:15 X1 /usr/lib/gdm3/gdm-x-session[2674]: (--) modeset(0): HDMI max TMDS frequency 31KHz Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): EDID vendor "HPN", prod id 13450 Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Using hsync ranges from config file Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Using vrefresh ranges from config file Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Printing DDC gathered Modelines: Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "2560x1440"x0.0 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync (88.8 kHz eP) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1920x1080"x0.0 148.35 1920 1936 1980 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "2560x1440"x0.0 304.25 2560 2608 2640 2720 1440 1443 1448 1492 +hsync -vsync (111.9 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1600x900"x60.0 119.00 1600 1696 1864 2128 900 901 904 932 -hsync +vsync (55.9 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1280x720"x60.0 74.48 1280 1336 1472 1664 720 721 724 746 -hsync +vsync (44.8 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1920x1200"x0.0 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync (74.0 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1440x900"x0.0 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1280x800"x0.0 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]:
[Ubuntu-x-swat] [Bug 1853120] Re: Xorg crashes with SIGBUS in drmmode_load_cursor_argb_check
Tracking in:
https://errors.ubuntu.com/problem/af88d9cd45acf4632e47789e4661be6a47b4dbf1
** Tags added: bionic disco xenial
** Description changed:
+ https://errors.ubuntu.com/problem/af88d9cd45acf4632e47789e4661be6a47b4dbf1
+
+ ---
+
I'm using a Dell XPS 9380 ("developer edition") connected to an external
monitor via USB C.
I've been running Ubuntu 19.04 for months with an external monitor with
no issues. On upgrading to 19.10 xorg crashes with a bus error within a
few seconds or minutes of using the external monitor.
The xorg package installed is 1:7.7+19ubuntu12
The system is stable without the external monitor.
The crash is consistently repeatable and the stack trace looks very
similar each time.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Nov 19 09:50:40 2019
DistUpgraded: 2019-11-17 14:04:28,024 ERROR got error from PostInstallScript
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
- Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00
[VGA controller])
-Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
+ Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00
[VGA controller])
+ Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
InstallationDate: Installed on 2019-07-09 (132 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
MachineType: Dell Inc. XPS 13 9380
ProcEnviron:
- LANGUAGE=en_IE:en
- TERM=xterm-256color
- PATH=(custom, no user)
- LANG=en_IE.UTF-8
- SHELL=/bin/bash
+ LANGUAGE=en_IE:en
+ TERM=xterm-256color
+ PATH=(custom, no user)
+ LANG=en_IE.UTF-8
+ SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic
root=UUID=6b08154b-c421-45b7-bc75-c4feccc18654 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to eoan on 2019-11-17 (1 days ago)
dmi.bios.date: 10/01/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.0
dmi.board.name: 088MRW
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.8.0:bd10/01/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn088MRW:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9380
dmi.product.sku: 08AF
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
--
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/1853120
Title:
Xorg crashes with SIGBUS in drmmode_load_cursor_argb_check
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853120/+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 1855388] Re: /usr/lib/xorg/Xorg:6:drmmode_load_cursor_argb:drmmode_load_cursor_argb_check:xf86_driver_load_cursor_argb:xf86_crtc_load_cursor_argb:xf86_load_cursor_argb
*** This bug is a duplicate of bug 1853120 *** https://bugs.launchpad.net/bugs/1853120 ** This bug has been marked a duplicate of bug 1853120 Xorg crashes with SIGBUS in drmmode_load_cursor_argb_check -- 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/1855388 Title: /usr/lib/xorg/Xorg:6:drmmode_load_cursor_argb:drmmode_load_cursor_argb_check:xf86_driver_load_cursor_argb:xf86_crtc_load_cursor_argb:xf86_load_cursor_argb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1855388/+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 1853120] Re: Xorg crashes with SIGBUS in drmmode_load_cursor_argb_check
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (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/1853120 Title: Xorg crashes with SIGBUS in drmmode_load_cursor_argb_check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853120/+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 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session
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. A duplicate -- 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/1853199 Title: Ctrl + c (copy) anywhere some times crashes gnome session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1853199/+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 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session
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) => 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/1853199 Title: Ctrl + c (copy) anywhere some times crashes gnome session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1853199/+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 1855388] [NEW] /usr/lib/xorg/Xorg:6:drmmode_load_cursor_argb:drmmode_load_cursor_argb_check:xf86_driver_load_cursor_argb:xf86_crtc_load_cursor_argb:xf86_load_cursor_argb
*** This bug is a duplicate of bug 1853120 *** https://bugs.launchpad.net/bugs/1853120 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.5+git20191008-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/af88d9cd45acf4632e47789e4661be6a47b4dbf1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic disco eoan xenial yakkety zesty -- 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/1855388 Title: /usr/lib/xorg/Xorg:6:drmmode_load_cursor_argb:drmmode_load_cursor_argb_check:xf86_driver_load_cursor_argb:xf86_crtc_load_cursor_argb:xf86_load_cursor_argb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1855388/+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 1846398] Re: Fractional scaling has significant visible tearing in Xorg sessions
** Summary changed: - Fractional scaling has significant visible tearing on a 4k display in Xorg sessions + Fractional scaling has significant visible tearing in Xorg sessions -- 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/1846398 Title: Fractional scaling has significant visible tearing in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1846398/+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 1852752] 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/1852752 Title: DPMS does not switch off the monitor back light on Raspberry Pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852752/+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 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock
*** This bug is a duplicate of bug 1846398 *** https://bugs.launchpad.net/bugs/1846398 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1846398, so it 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. Feel free to continue to report any other bugs you may find. ** Package changed: mutter (Ubuntu) => xorg-server (Ubuntu) ** Tags added: xrandr-scaling ** This bug has been marked a duplicate of bug 1846398 Fractional scaling has significant visible tearing in Xorg sessions -- 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/1853094 Title: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853094/+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 1853120] Re: Xorg crashes with SIGBUS in drmmode_load_cursor_argb_check
** Summary changed: - Xorg crashes with a bus error in OsLookupColor when using a second display + Xorg crashes with SIGBUS in drmmode_load_cursor_argb_check ** Package changed: xorg (Ubuntu) => xorg-server (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/1853120 Title: Xorg crashes with SIGBUS in drmmode_load_cursor_argb_check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853120/+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 1852863] Re: Don't know
Sounds like you're not getting a login screen, is that right? It wouldn't be surprising given it's a rare and not well tested: Intel(R) Core(TM) i5 CPU M 460 @ 2.53GHz Please try editing /etc/gdm3/custom.conf and uncomment: #WaylandEnable=false then reboot. ** Package changed: xorg (Ubuntu) => mutter (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/1852863 Title: Don't know To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1852863/+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 1853094] [NEW] Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock
You have been subscribed to a public bug: I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480 laptop with two external displays. The laptop itself is closed (internal display is not used). In a gnome xorg session, there is severe tearing on parts of the screen when dragging windows or scrolling content. Under a wayland session there is no screen tearing, but I have keyboard key repetition problems which make this mostly unusable day-to-day (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405). I can supply short phone videos of tearing occurring on the screens if required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 19 14:02:09 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock https://bugs.launchpad.net/bugs/1853094 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server 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 1852752] Re: DPMS does not switch off the monitor back light
Since Xorg is using the modeset driver here I think this might be an issue with the Raspberry Pi kernel driver(s) ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Summary changed: - DPMS does not switch off the monitor back light + DPMS does not switch off the monitor back light on Raspberry Pi 4 ** 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-server in Ubuntu. https://bugs.launchpad.net/bugs/1852752 Title: DPMS does not switch off the monitor back light on Raspberry Pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852752/+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 1852166] Re: [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works
I can see a couple of pixel-layout-related settings here: dithering depth: auto supported: auto, 6 bpc, 8 bpc dithering mode: auto supported: auto, off, static 2x2, dynamic 2x2, temporal The nouveau kernel driver provides them regardless of the attached monitor. You can tweak them with: xrandr --output DP-1 --set or similar. Though that might not help... What might help is installing the proprietary Nvidia driver instead. Have a look in: Software & Updates > Additional Drivers to install the Nvidia driver. -- 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/1852166 Title: [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852166/+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 1852166] Re: [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works
Does the problem occur if you log into 'Ubuntu on Wayland' ? ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** 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-server in Ubuntu. https://bugs.launchpad.net/bugs/1852166 Title: [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852166/+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 1855380] Re: Dell Inspiron 3558 touchpad stopped working in kernel 4.15.0-72 (but 4.15.0-70 is OK)
** Summary changed: - Touchpad not working + Dell Inspiron 3558 touchpad stopped working in kernel 4.15.0-72 (but 4.15.0-70 is OK) ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Tags added: regression-update -- 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/1855380 Title: Dell Inspiron 3558 touchpad stopped working in kernel 4.15.0-72 (but 4.15.0-70 is OK) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855380/+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 1855380] [NEW] Touchpad not working
Public bug reported: The touchpad is not detected by my Dell Inspiron 3000 series laptop, this happened after my kernel was updated from 4.15.0-70 to 4.15.0-72. If I enter Ubuntu Advanced Options to my previous kernel (4.15.0-70) my touchpad works correctly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 5 21:54:06 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:06b0] InstallationDate: Installed on 2019-07-01 (158 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 3558 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ipv6.disable vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0XNXCC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/31/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XNXCC:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell 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.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 ubuntu ** Attachment added: "Info about devices xinput evtest and Xorg.log" https://bugs.launchpad.net/bugs/1855380/+attachment/5310123/+files/devicesxinputEvtestXorg.log -- 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/1855380 Title: Touchpad not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1855380/+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 1846807] Re: Xorg crash
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- 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/1846807 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1846807/+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 1852170] Re: Severe screen corruption
*** This bug is a duplicate of bug 1848741 *** https://bugs.launchpad.net/bugs/1848741 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1848741, so it 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. Feel free to continue to report any other bugs you may find. ** Tags added: amdgpu ** Summary changed: - Severe screen corruption + [amdgpu] Severe screen corruption ** This bug has been marked a duplicate of bug 1848741 [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge) -- 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/1852170 Title: [amdgpu] Severe screen corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1852170/+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 1852166] Re: Pixel pattern error in over
Sorry I can't see a problem in that screenshot. Can you provide more? ** Tags added: nouveai ** Tags removed: nouveai ** Tags added: nouveau ** Summary changed: - Pixel pattern error in over + [nouveau] Pixel pattern error in over ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Summary changed: - [nouveau] Pixel pattern error in over + [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works -- 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/1852166 Title: [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852166/+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 1852117] Re: non appare nessuna applicazione
** 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/1852117 Title: non appare nessuna applicazione To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1852117/+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 1852158] Re: Xorg black screen on resume, and VT switch crashes with "EnterVT failed for screen 0"
*** This bug is a duplicate of bug 1421808 ***
https://bugs.launchpad.net/bugs/1421808
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1421808 / bug 1787332 / bug 1787338, so it 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. Feel free to continue to
report any other bugs you may find.
** This bug has been marked a duplicate of bug 1421808
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from
WakeupHandler()
--
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/1852158
Title:
Xorg black screen on resume, and VT switch crashes with "EnterVT
failed for screen 0"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1852158/+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 1852071] Re: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys
** Package changed: xorg (Ubuntu) => linux (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/1852071 Title: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852071/+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 1852083] Re: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS, bluetooth mouse] Choppy/laggy bluetooth mouse cursor movement
** Package changed: xorg (Ubuntu) => linux (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/1852083 Title: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS, bluetooth mouse] Choppy/laggy bluetooth mouse cursor movement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852083/+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 1852023] Re: Wayland doesn't work in GMA500
Although you are completely right about "I guess an udev rule to disable Wayland for GMA500 is all that is needed." ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Importance: Undecided => Low ** Changed in: mutter (Ubuntu) Status: New => Triaged -- 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/1852023 Title: Wayland doesn't work in GMA500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1852023/+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 1852023] Re: Wayland doesn't work in GMA500
It appears GMA500 is the infamous Poulsbo with PowerVR GPU: https://en.wikipedia.org/wiki/Intel_GMA#GMA_500 This means it is closed source and we can't support it :( -- 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/1852023 Title: Wayland doesn't work in GMA500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1852023/+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 1852023] Re: Wayland doesn't work in GMA500
Although you are complete right about "I guess an udev rule to disable Wayland for GMA500 is all that is needed." -- 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/1852023 Title: Wayland doesn't work in GMA500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1852023/+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 653714]
-- 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/xorg/driver/xf86-video-nouveau/issues/29. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
(In reply to nv28m from comment #71) > nouveau.agpmode=0 seems to work here too, also after comming back from > suspend. > > Still I think I'm stuck with the modesetting driver with the bit 24 hack in > boot/suspend scripts. The scrolling and rxvt performance is just better. The parameter name seems to be changed. nouveau.modeset=0 is what worked for me. I add my thanks for the hard work done by Mr. nv28m. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
I also have this problem. Everything unaccelerated comes up as trash, even on the kernel framebuffer (if acceleration was switched off). Or for example I can see most of the graphics ok, but if I use ShadowFB then the whole screen is unusable. And the cursor is garbage too most of the time. This is nothing new, but I found a way to make it work. I have two systems installed (latest debian/testing). I boot the first one to X with the nvidia drivers. Then I use kexec to boot into the second system (also debian/testing), which is using nouveau. And at this time, all the graphics are fine! So something is initialized by the nvidia driver, which is not touched by nouveau but is required for correct operation. Is there a way I could help? Like dumping register states with/without the nvidia init? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
I reached to retreive my video bios version*: cat /proc/driver/nvidia/cards/0 Model: GeForce4 4200 Go IRQ: 11 Video BIOS: 04.28.20.31.c1 Card Type: AGP DMA Size: 32 bits DMA Mask: 0x Maybe you will like to check against your own and tell me you need something else from me. * not that difficult, but I'm unskilled where/what to dig in. Bye bye -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
nouveau.agpmode=0 seems to work here too, also after comming back from suspend. Still I think I'm stuck with the modesetting driver with the bit 24 hack in boot/suspend scripts. The scrolling and rxvt performance is just better. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
Guys, if I can help in any maneer I'd be glad. I want you to know my video adapter is flashed with a bios update I found long time ago on dell's site (in my memory, this was a bios update for Windows). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
I ended in Ubuntu 12.04 with latest nvidia-96(-updates maybe). The Laptop sleeps now for weeks and I won't wake it up. I Just can say that once I admitted that vino won't work with desktop effects, I decided to use this laptop with gnome-shell no-effects only, and with the latest drivers state above the laptop now can be used. I'm not a coder so I can't help further and I see we are only two who subscribed this thread. My single company surely won't help you to go further, emgaron. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
Hi, I do not know if it may be still relevant after nv28m dicoveries but here's some quick info (with a debian testing fully updated a month ago). Booting with plain nouveau (agp v2 4x): distorted mouse, nothing new here :( I tried to boot the following kernel command lines: * nouveau.vram_pushbuf=1 TTY and X screwed up. * nouveau.agpmode=2 -->distorted mouse * nouveau.agpmode=1 mouse OK, NO apparent problems. Then I tried then a glxgears that gave a GPU lockup, alas. * nouveau.agpmode=0 mouse OK, NO apparent problems (yet). cheers ric -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
(In reply to Ilia Mirkin from comment #64) > (In reply to comment #63) > > > > Option 3 could definately tell if it's only used for a particular memory > > configuration of this chip, or it's more general (e.g. first 2 options). > > I've fired off a question to NVIDIA, hopefully they'll respond. Sometimes > they respond ~immediately, other times it takes two months, but so far they > haven't dropped anything on the floor. Well, now that it's more than a year, I think the floor can be considered the likely destination. It would be nice to have an answer, but it's no longer likely. I think a fall-back to #2 (set the bit for N28 chips) is the most reasonable. If all the other chips needed it, we'd have seen a flood of bug reports by now. It's not as if this bug isn't obvious. X is unusable until it's fixed. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
(In reply to AndrewK from comment #73) > (In reply to nv28m from comment #71) > > nouveau.agpmode=0 seems to work here too, also after comming back from > > suspend. > > > > Still I think I'm stuck with the modesetting driver with the bit 24 hack in > > boot/suspend scripts. The scrolling and rxvt performance is just better. > > The parameter name seems to be changed. nouveau.modeset=0 is what worked > for me. > > I add my thanks for the hard work done by Mr. nv28m. nouveau.modeset=0 just disables nouveau entirely. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
agpmode and modeset are not even remotely related I'm afraid. With 4.3 onward one should be using nouveau.config="NvAGP=0" as documented [1] [1] http://nouveau.freedesktop.org/wiki/KernelModuleParameters/#config -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
Yes, it was taken after several attempts, that's why it was already set. I've made a better dump and sent it in e-mail now. According to this it's set the first time it's written to. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
(In reply to Ilia Mirkin from comment #75) > (In reply to AndrewK from comment #73) > > (In reply to nv28m from comment #71) > > > nouveau.agpmode=0 seems to work here too, also after comming back from > > > suspend. > > > > > The parameter name seems to be changed. nouveau.modeset=0 is what worked > > for me. > > > > nouveau.modeset=0 just disables nouveau entirely. Without modeset=0 the screen gets scrambled. With it, it is correct. That's at least minimum functionality. I tried agpmode=0 but it didn't work. Also, modinfo didn't list a parameter by that name, so I chose the one that looked closest. I don't really know what happened, but I'm not demanding w.r.t. high-speed rendering, so I'm content. As other posters have mentioned, I'll be glad to do any tests you'd like, since I have the hardware. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
(In reply to Emil Velikov from comment #77) > agpmode and modeset are not even remotely related I'm afraid. With 4.3 > onward one should be using nouveau.config="NvAGP=0" as documented [1] > > [1] http://nouveau.freedesktop.org/wiki/KernelModuleParameters/#config Yes. The syntax given seems to do the trick. Thanks much. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
On Lubuntu 14.04.3 (I think it's Kernel 3.19.x) "nouveau.agpmode=0" also works, although standby still doesn't seem to work. What I want to note though, is, that activating the Shadow Framebuffer in /etc/X11/xorg.conf.d/20-nouveau.conf results in a substantial performance increase regarding scrolling and so on. Maybe this should be considered for the nv28m-cards. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
I've wasted a lot of time with the mmio registers to find out why things go slow. But it seems it's something else. Just loading the nvidia kernel module without starting X is enough to make nouveau go fast after kexec. I did an mmio trace while loading the module, but it only wrote 140 to 0, and that was all. I've checked the PCI config space, also nothing interesting. Any tips how to find out what happens? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
Even more interesting, your trace actually has [0] 1012.956817 MMIO32 R 0x100080 0xe100 PFB+0x80 => 0xe100 [0] 1012.956820 MMIO32 W 0x100080 0xe100 PFB+0x80 <= 0xe100 Which means that it _starts out_ at 0xe100. Was this trace done on a clean boot, or had the nvidia module already been loaded? The latter makes more sense... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
BTW, interesting. In your VBIOS, it tells us to do 0xcbf2: 7a 80 00 10 00 00 00 00 e0 ZM_REG R[0x100080] = 0xe000 Which is why that bit gets lost on resume (but not on kexec, since init scripts don't run, since the adapter is already init'd). Good to know, that means that any fixup would have to be made _after_ the bios gets executed... or more likely, as part of the COMPUTE_MEM thing (meminit in core/subdev/devinit/nv20.c), which gets executed in "init script 5", which happens after that "init script 1" which contains the 0x100080 = 0xe000 command. Although then it wouldn't happen on boot, so nevermind. Has to happen after the vbios executes. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
(In reply to comment #63) > For the first two options I think it could be useful to grep through all > those dumps collected over the years and check which cards have this set. Yeah, I'll try to have a look later on. > > Option 3 could definately tell if it's only used for a particular memory > configuration of this chip, or it's more general (e.g. first 2 options). I've fired off a question to NVIDIA, hopefully they'll respond. Sometimes they respond ~immediately, other times it takes two months, but so far they haven't dropped anything on the floor. > > By the way I've checked again my earlier claim about being slower after > suspend, and it's definately like that. Scrolling is more or less smooth > (considering the age of hardware and the resolution used) after kexec-ing > from nvidia to nouveau. > > But after a suspend it's really "choppy" (same software still running, > nothing was changed). The speed is similarly slow after a clean boot too, so > it's not a suspend problem. Somewhere the handbrake needs to be released I > guess... Well, you may have just become the resident expert on NV2x cards. You have all the tools we have, and you also have the hardware, which is very hard to come by (a mobile NV2x). Poke around, let us know :) We hang out on #nouveau on irc.freenode.net if you have any questions. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
For the first two options I think it could be useful to grep through all those dumps collected over the years and check which cards have this set. Option 3 could definately tell if it's only used for a particular memory configuration of this chip, or it's more general (e.g. first 2 options). By the way I've checked again my earlier claim about being slower after suspend, and it's definately like that. Scrolling is more or less smooth (considering the age of hardware and the resolution used) after kexec- ing from nvidia to nouveau. But after a suspend it's really "choppy" (same software still running, nothing was changed). The speed is similarly slow after a clean boot too, so it's not a suspend problem. Somewhere the handbrake needs to be released I guess... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
I ignore if it's related, but my Dell D800 with nv28 burts many-many-many beeps on boot until the grub menu displays. Feel free to ask any thing. Regards -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
(In reply to comment #61) > At the end I got what I wanted. The winner is: > nvapoke 00100080 e100 > > This register is e000 after suspend or after clean boot. So all this > trouble only because of a single bit was not set ;( Fantastic! I was secretly hoping that by ignoring the issue for a short while, one of the hardware owners would step up and work it out :) Looks like register 100080 isn't documented in rnndb. In the linux source it's referred to as NV04_PFB_DEBUG_0. Unfortunately on a quick grep of the code, nothing ever touches bit 24 of that register. There are three ways forward: 1. Set it for all nv04:nv50 cards 2. Set it for nv28 cards 3. Reach out to nvidia and see if they'll be kind enough to let us know the meaning of that bit, and when we should be setting it. They've been fielding some questions of late, and this seems likely to be one that they'd answer. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
I've e-mailed the dump file. I've put in 3 markers, one before starting xinit /usr/bin/urxvt, one in urxvt before quiting, and one after xinit returned. I hope it's useful. Thanks! I can try to repeat the same thing using the nouveau driver, if needed. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
I had the feeling that there's not much chance that the dump alone will help. So I did some debugging on my own, after all it can't be that hard if I have the hardware at hand to play with ;) First I've collected all writes locations out from the dump, and ignored the part which looked like a frame buffer. I got around 260 locations, I guess most of these must be mapped registers. Then I did the nvidia boot and kexec to nouveau, when everything works except that the GPU locks after a while. Anyway, it's stable enough to dump of those 260 registers. Then I made a suspend to RAM, and back. Screen trashing is back of course, but let's dump those registers again. Comparing the dumps reveals that 30 locations are different now. I wrote all those registers back as they were before the suspend. Of course console went immediately blank. But I can still start X blindly, which hangs of course, but at least I can move a flawless cursor around. (normally it's trashed as well) So it must be one of these. I resorted to normal bisecting from here to find transhing/non-trashing set of registers. There were plenty of hangs and reboots ;) At the end I got what I wanted. The winner is: nvapoke 00100080 e100 This register is e000 after suspend or after clean boot. So all this trouble only because of a single bit was not set ;( The earlier GPU lockup (with kexec nouveau after nvidia driver init) does not happen anymore when I only set this bit, but nothing else. It probably must be due to some other uninitialized state, but I'm not sure if it's worth to find out what it is, after all the default state on boot is ok. >From here I pass the ball back. Please, with this knowledge could someone fix up the driver? Most likely it would be better done on the kernel side as the KMS frame buffer is affected too. Of course testing patches should be no problem ;) Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
Doing a suspend to RAM restores the original trashing behaviour. I'm not sure, but maybe the screen update is slower as well now. This is a Dell D800: 01:00.0 VGA compatible controller: NVIDIA Corporation NV28M [GeForce4 Ti 4200 Go AGP 8x] (rev a1) X.Org X Server 1.15.1 Release Date: 2014-04-13 [ 263.867] X Protocol Version 11, Revision 0 [ 263.867] Build Operating System: Linux 3.2.0-4-amd64 i686 Debian [ 263.867] Current Operating System: Linux dell 3.13-1-686-pae #1 SMP Debian 3.13.7-1 (2014-03-25) i686 [ 263.867] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13-1-686-pae-mine2 root=/dev/mapper/root ro processor.ignore_ppc=1 quiet [ 263.867] Build Date: 15 April 2014 07:46:36PM [ 263.867] xorg-server 2:1.15.1-1 (http://www.debian.org/support) [ 263.873] (II) NOUVEAU driver Date: Thu Nov 7 14:56:48 2013 +1000 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
(In reply to comment #55) > So something is initialized by the nvidia driver, which is not touched by > nouveau but is required for correct operation. > > Is there a way I could help? Like dumping register states with/without the > nvidia init? You could do a mmiotrace of the nvidia driver. It's likely that we're missing some bit of init. The resulting file will probably be quite large (50-100MB)... xz -9 it and email to mmio.du...@gmail.com. (Also wouldn't hurt to upload your vbios from /sys/kernel/debug/dri/0/vbios.rom to this bug, and also attach it in the email while you're at it.) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
The default Debian kernel is not very debug friendly, so I've dumped the ROMs with nvagetbios. There are two versions, as I made a firmware update later to see if it helps. (e-mailed) The MMIO dumps are comming soon, tomorrow or so. This is a slow machine and the kernel compile takes a while even after I've reduced the config file (and set CONFIG_MMIOTRACE). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714]
I just discovered this bug as I acquired a Dell Inspiron 8500 a few weeks back and ran into the same problem. In fact, on my machine (same nVidia graphics), the problem even seems worse: Any attempt at using the nouveau driver so far has not only produced the distortions described by the original poster, but also ended with a GPU lock-up after a few minutes maximum. For that reason, I'm now running Xubuntu 12.04 on that machine, as this distribution still provides the older nvidia-96 proprietary driver - newer distros apparently dropped this version. With the proprietary driver, the laptop runs fine and actually quite smooth (considering the age and specs). As it would be nice to be able to run newer Linux distros on this machine, I'd be happy to help with experimenting/testing. I could install a newer distro (and hence - presumably - newer nouveau driver) on a second hard drive or on an external drive so I can test stuff. Any preferences which distro would be most helpful for you? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 653714] Re: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28])
** Changed in: nouveau Status: Confirmed => Unknown ** Bug watch added: gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues #29 https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/29 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+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 1851715] Re: Screen brightness adjustment delay in Xorg sessions only
** Summary changed: - Screen brightness adjustment delay + Screen brightness adjustment delay in Xorg sessions only ** Package changed: linux (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: Confirmed => New ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- 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/1851715 Title: Screen brightness adjustment delay in Xorg sessions only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1851715/+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 1467595] Re: cursor sometimes disappears on XPS 13 9343 and external monitor
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: unity (Ubuntu) Status: Incomplete => Won't Fix -- 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/1467595 Title: cursor sometimes disappears on XPS 13 9343 and external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1467595/+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 1853412] Re: Xorg freeze
Please avoid reporting multiple issues in a single bug. The tearing issue is bug 1846398 already so the remaining issues are "Ubuntu operates slow with system apps and 3rd party apps; system hangs and crashes; and more". Are you saying Ubuntu is only slow when you are using fractional scaling? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Summary changed: - Xorg freeze + Poor performance with fractional scaling factors in Xorg ** Package changed: ubuntu => mutter (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/1853412 Title: Poor performance with fractional scaling factors in Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853412/+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 1852001] Re: GUI freeze on high disk or CPU load, but disabling swap fixes it
Which GUI are you using that exhibits the problem? ** Summary changed: - Xorg freeze on high disk or cpu load or random + GUI freeze on high disk or CPU load, but disabling swap fixes it ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Summary changed: - GUI freeze on high disk or CPU load, but disabling swap fixes it + GUI freeze on high disk IO, but disabling swap fixes it -- 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/1852001 Title: GUI freeze on high disk IO, but disabling swap fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852001/+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 1850874] Re: gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just to update the screen (on Wayland only)
Thanks. I've now added this bug to the performance tracking list: https://trello.com/c/pe5mRmx7 ** Summary changed: - gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just to update the screen + gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just to update the screen (on Wayland only) ** Tags added: wayland wayland-session ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: mesa (Ubuntu) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Changed in: mesa (Ubuntu) Status: Incomplete => New ** Changed in: mutter (Ubuntu) Status: Incomplete => 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/1850874 Title: gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just to update the screen (on Wayland only) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850874/+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 1378744] Re: nVidia GK106GLM [Quadro K2100M] [10de:11fc] Connect to HDMI / DP port with open-source driver will cause Xorg crash
** Changed in: nouveau Status: Confirmed => Unknown ** Bug watch added: gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues #100 https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/100 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1378744 Title: nVidia GK106GLM [Quadro K2100M] [10de:11fc] Connect to HDMI / DP port with open-source driver will cause Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1378744/+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 1378744]
-- 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/xorg/driver/xf86-video- nouveau/issues/100. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1378744 Title: nVidia GK106GLM [Quadro K2100M] [10de:11fc] Connect to HDMI / DP port with open-source driver will cause Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1378744/+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 1855220] Re: xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry)
I downloading & booted Xubuntu 20.04 daily and played there. same hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) on same box. adding xscreensaver & using 'flurry', I got the same jerky/choppy response here once packages added & running. I could see the xscreensaver dialog box where I click 'preview' (approx correct position on screen but on wrong display??!!) when it jerked (or I described as black-white-blocky-bad-signal in original post; I'd not use those words now). Yes it's somewhat like a bad signal on tv, but I do get the same response here on Xubuntu 20.04 daily. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1855220 Title: xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1855220/+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 1850874] Re: gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just to update the screen
This bug only is present on Wayland. -- 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/1850874 Title: gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just to update the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850874/+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 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G
** Changed in: linux Status: Unknown => New -- 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/1848900 Title: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1848900/+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 1851910] Re: [nvidia] Display does not show up (short flashes)
This might be bug 1798790. -- 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/1851910 Title: [nvidia] Display does not show up (short flashes) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1851910/+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 1851910] Re: Display does not show up (short flashes)
Please try editing /etc/gdm3/custom.conf and then uncomment: #WaylandEnable=false And then reboot. ** Tags added: nvidia ** Summary changed: - Display does not show up (short flashes) + [nvidia] Display does not show up (short flashes) ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-430 (Ubuntu) ** Changed in: nvidia-graphics-drivers-430 (Ubuntu) Status: New => Incomplete ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Changed in: gdm3 (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/1851910 Title: [nvidia] Display does not show up (short flashes) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1851910/+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 1851789] Re: Xorg freeze
Please also tell us exactly which browsers exhibit the bug. ** Package changed: xorg (Ubuntu) => ubuntu ** Summary changed: - Xorg freeze + GUI freeze -- 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/1851789 Title: GUI freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1851789/+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 1851649] Re: Package bug
** 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/1851649 Title: Package bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1851649/+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 1851349] Re: Xorg freeze
** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Summary changed: - Xorg freeze + GUI freeze -- 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/1851349 Title: GUI freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1851349/+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 1851349] Re: Xorg freeze
Please open two Terminal windows. In one run: dmesg -w In the other run: journalctl -f Now wait and reproduce the freeze a few times. Each time look at those two Terminal windows and tell us if you see any particular messages just after each freeze. -- 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/1851349 Title: GUI freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1851349/+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 1851018] Re: xorg have some bugs.
** 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/1851018 Title: xorg have some bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1851018/+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 1850931] Re: screen corruption after sleep mode
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1850931 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: disco ** Package changed: xorg (Ubuntu) => xorg-server (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/1850931 Title: screen corruption after sleep mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1850931/+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 1850931] Re: screen corruption after sleep mode
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 Actually this sounds like bug 1809407 so let's just assume it is unless proven otherwise. ** This bug has been marked a duplicate of bug 1809407 [nvidia] Corrupted wallpaper after resuming from suspend or hibernation -- 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/1850931 Title: screen corruption after sleep mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1850931/+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 1850874] Re: gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just to update the screen
I think the Gnome Shell developers have been working on how that code (efficient screen updates for VMs) works in Wayland sessions. But I don't know the details. Let's hope mutter 3.36 performs better in that area. -- 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/1850874 Title: gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just to update the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850874/+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 1850917] Re: QT apps have differing scaling on dual monitor setup
*** This bug is a duplicate of bug 1824753 *** https://bugs.launchpad.net/bugs/1824753 Sounds like Qt bug 1824753 ** This bug has been marked a duplicate of bug 1824753 When I pass the Qt application to the secondary monitor the characters of the application increase -- 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/1850917 Title: QT apps have differing scaling on dual monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1850917/+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 1850874] Re: gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just to update the screen
Comment #16 is confusing because it sounds like you're now talking about multiple unrelated issues. It is also confusing because comment #16 suggests this bug occurs in Wayland only but comment #13 looks like it's from Xorg. Is this bug affecting Wayland sessions only? ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Incomplete ** Changed in: mesa (Ubuntu) Status: Triaged => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Changed in: mesa (Ubuntu) Importance: Low => Undecided ** Changed in: gnome-shell (Ubuntu) Importance: Low => Undecided -- 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/1850874 Title: gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just to update the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850874/+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 1684123]
-- 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/xorg/driver/xf86-video- nouveau/issues/335. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1684123 Title: bus: MMIO read of FAULT at 3e6684 [ IBUS ] To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1684123/+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 1684123] Re: bus: MMIO read of 00000000 FAULT at 3e6684 [ IBUS ]
** Changed in: nouveau Status: Confirmed => Unknown ** Bug watch added: gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues #335 https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/335 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1684123 Title: bus: MMIO read of FAULT at 3e6684 [ IBUS ] To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1684123/+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 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G
** Bug watch added: gitlab.freedesktop.org/drm/amd/issues #956 https://gitlab.freedesktop.org/drm/amd/issues/956 ** Also affects: linux via https://gitlab.freedesktop.org/drm/amd/issues/956 Importance: Unknown Status: Unknown -- 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/1848900 Title: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1848900/+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
