[Ubuntu-x-swat] [Bug 2063503] Re: NVidia drivers won't install completely
This appears to be the issue. DRM_UNLOCKED does not exist for nvidia- drm-drv.c to compile. Missing ot changed kernel header? # CC [M] /var/lib/dkms/nvidia/545.29.06/build/nvidia-drm/nvidia-drm-gem-nvkms-memory.o cc -Wp,-MMD,/var/lib/dkms/nvidia/545.29.06/build/nvidia-drm/.nvidia-drm-gem-nvkms-memory.o.d -nostdinc -I./arch/x86/include -I./arch/x86/include/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/compiler-version.h -include ./include/linux/kconfig.h -I./ubuntu/include -include ./include/linux/compiler_types.h -D__KERNEL__ -fmacro-prefix-map=./= -std=gnu11 -fshort-wchar -funsigned-char -fno-common -fno-PIE -fno-strict-aliasing -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -fcf-protection=none -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -mindirect-branch-cs-prefix -mfunction-return=thunk-extern -fno-jump-tables -mharden-sls=all -fpatchable-function-entry=16,16 -fno-delete-null-pointer-checks -O2 -fno-allow-store-data-races -fstack-protector-strong -fno-omit-frame-pointer -fno-optimize-sibling-calls -ftrivial-auto-var-init=zero -fno-stack-clash-protection -fzero-call-used-regs=used-gpr -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY -falign-functions=16 -fstrict-flex-arrays=3 -fno-strict-overflow -fno-stack-check -fconserve-stack -Wall -Wundef -Werror=implicit-function-declaration -Werror=implicit-int -Werror=return-type -Werror=strict-prototypes -Wno-format-security -Wno-trigraphs -Wno-frame-address -Wno-address-of-packed-member -Wmissing-declarations -Wmissing-prototypes -Wframe-larger-than=1024 -Wno-main -Wno-unused-but-set-variable -Wno-unused-const-variable -Wno-dangling-pointer -Wvla -Wno-pointer-sign -Wcast-function-type -Wno-stringop-overflow -Wno-array-bounds -Wno-alloc-size-larger-than -Wimplicit-fallthrough=5 -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -Wenum-conversion -Wno-unused-but-set-variable -Wno-unused-const-variable -Wno-restrict -Wno-packed-not-aligned -Wno-format-overflow -Wno-format-truncation -Wno-stringop-truncation -Wno-missing-field-initializers -Wno-type-limits -Wno-shift-negative-value -Wno-maybe-uninitialized -Wno-sign-compare -g -gdwarf-5 -I/var/lib/dkms/nvidia/545.29.06/build/common/inc -I/var/lib/dkms/nvidia/545.29.06/build -Wall -Wno-cast-qual -Wno-error -Wno-format-extra-args -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=\"545.29.06\" -DNV_FILESYSTEM_ACCESS_AVAILABLE=1 -Wno-unused-function -Wuninitialized -fno-strict-aliasing -ffreestanding -mno-red-zone -mcmodel=kernel -DNV_UVM_ENABLE -Werror=undef -DNV_SPECTRE_V2=0 -DNV_KERNEL_INTERFACE_LAYER -I/var/lib/dkms/nvidia/545.29.06/build/nvidia-drm -UDEBUG -U_DEBUG -DNDEBUG -DNV_BUILD_MODULE_INSTANCES=0 -fsanitize=bounds-strict -fsanitize=shift -fsanitize=bool -fsanitize=enum -DMODULE -DKBUILD_BASENAME='"nvidia_drm_gem_nvkms_memory"' -DKBUILD_MODNAME='"nvidia_drm"' -D__KBUILD_MODNAME=kmod_nvidia_drm -c -o /var/lib/dkms/nvidia/545.29.06/build/nvidia-drm/nvidia-drm-gem-nvkms-memory.o /var/lib/dkms/nvidia/545.29.06/build/nvidia-drm/nvidia-drm-gem-nvkms-memory.c ; ./tools/objtool/objtool --hacks=jump_label --hacks=noinstr --hacks=skylake --retpoline --rethunk --sls --stackval --static-call --uaccess --prefix=16 --module /var/lib/dkms/nvidia/545.29.06/build/nvidia-drm/nvidia-drm-gem-nvkms-memory.o In file included from /var/lib/dkms/nvidia/545.29.06/build/nvidia-drm/nvidia-drm-drv.c:64: /var/lib/dkms/nvidia/545.29.06/build/nvidia-drm/nvidia-drm-drv.c:1489:40: error: ‘DRM_UNLOCKED’ undeclared here (not in a function); did you mean ‘VM_LOCKED’? 1489 | DRM_RENDER_ALLOW|DRM_UNLOCKED), |^~~~ ./include/drm/drm_ioctl.h:155:26: note: in definition of macro ‘DRM_IOCTL_DEF_DRV’ 155 | .flags = _flags, \ | ^~ -- 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/2063503 Title: NVidia drivers won't install completely To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2063503/+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 2063503] Re: NVidia drivers won't install completely
** Attachment added: "The make.log referred to in my comment above" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2063503/+attachment/5770654/+files/make.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/2063503 Title: NVidia drivers won't install completely To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2063503/+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 2063503] Re: NVidia drivers won't install completely
Tried again after purging all things NVidia and rebooting. :~$ sudo ubuntu-drivers install --recommended udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-545 libnvidia-common-545 libnvidia-compute-545 libnvidia-decode-545 libnvidia-encode-545 libnvidia-extra-545 libnvidia-fbc1-545 libnvidia-gl-545 libnvidia-gl-545:i386 nvidia-compute-utils-545 nvidia-firmware-545-545.29.06 nvidia-kernel-common-545 nvidia-kernel-source-545 nvidia-prime nvidia-settings nvidia-utils-545 xserver-xorg-video-nvidia-545 The following NEW packages will be installed: libnvidia-cfg1-545 libnvidia-common-545 libnvidia-compute-545 libnvidia-decode-545 libnvidia-encode-545 libnvidia-extra-545 libnvidia-fbc1-545 libnvidia-gl-545 libnvidia-gl-545:i386 nvidia-compute-utils-545 nvidia-dkms-545 nvidia-driver-545 nvidia-firmware-545-545.29.06 nvidia-kernel-common-545 nvidia-kernel-source-545 nvidia-prime nvidia-settings nvidia-utils-545 xserver-xorg-video-nvidia-545 0 upgraded, 19 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/338 MB of archives. After this operation, 908 MB of additional disk space will be used. Selecting previously unselected package libnvidia-cfg1-545:amd64. (Reading database ... 339019 files and directories currently installed.) Preparing to unpack .../00-libnvidia-cfg1-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking libnvidia-cfg1-545:amd64 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package libnvidia-common-545. Preparing to unpack .../01-libnvidia-common-545_545.29.06-0ubuntu0~gpu24.04.1_all.deb ... Unpacking libnvidia-common-545 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package libnvidia-compute-545:amd64. Preparing to unpack .../02-libnvidia-compute-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking libnvidia-compute-545:amd64 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package libnvidia-decode-545:amd64. Preparing to unpack .../03-libnvidia-decode-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking libnvidia-decode-545:amd64 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package libnvidia-encode-545:amd64. Preparing to unpack .../04-libnvidia-encode-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking libnvidia-encode-545:amd64 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package libnvidia-extra-545:amd64. Preparing to unpack .../05-libnvidia-extra-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking libnvidia-extra-545:amd64 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package libnvidia-fbc1-545:amd64. Preparing to unpack .../06-libnvidia-fbc1-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking libnvidia-fbc1-545:amd64 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package libnvidia-gl-545:i386. Preparing to unpack .../07-libnvidia-gl-545_545.29.06-0ubuntu0~gpu24.04.1_i386.deb ... dpkg-query: no packages found matching libnvidia-gl-535 Unpacking libnvidia-gl-545:i386 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package libnvidia-gl-545:amd64. Preparing to unpack .../08-libnvidia-gl-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... dpkg-query: no packages found matching libnvidia-gl-535 Unpacking libnvidia-gl-545:amd64 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package nvidia-compute-utils-545. Preparing to unpack .../09-nvidia-compute-utils-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking nvidia-compute-utils-545 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package nvidia-kernel-source-545. Preparing to unpack .../10-nvidia-kernel-source-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking nvidia-kernel-source-545 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package nvidia-firmware-545-545.29.06. Preparing to unpack .../11-nvidia-firmware-545-545.29.06_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking nvidia-firmware-545-545.29.06 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package nvidia-kernel-common-545. Preparing to unpack .../12-nvidia-kernel-common-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking nvidia-kernel-common-545 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package nvidia-dkms-545. Preparing to unpack .../13-nvidia-dkms-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking nvidia-dkms-545 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously
[Ubuntu-x-swat] [Bug 2063503] [NEW] NVidia drivers won't install completely
Public bug reported: ll versions of the nvidia driver fail to install no matter what. Including the one downloaded from Nvidia. It doesn't matter the version. :~$ sudo apt install nvidia-driver-550 [sudo] password for jim: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following package was automatically installed and is no longer required: nvidia-firmware-545-545.29.06 Use 'sudo apt autoremove' to remove it. The following additional packages will be installed: libnvidia-cfg1-550 libnvidia-common-550 libnvidia-compute-550 libnvidia-compute-550:i386 libnvidia-decode-550 libnvidia-decode-550:i386 libnvidia-encode-550 libnvidia-encode-550:i386 libnvidia-extra-550 libnvidia-fbc1-550 libnvidia-fbc1-550:i386 libnvidia-gl-550 libnvidia-gl-550:i386 nvidia-compute-utils-550 nvidia-dkms-550 nvidia-firmware-550-550.67 nvidia-kernel-common-550 nvidia-kernel-source-550 nvidia-utils-550 xserver-xorg-video-nvidia-550 The following packages will be REMOVED: libnvidia-cfg1-545 libnvidia-common-545 libnvidia-compute-545 libnvidia-compute-545:i386 libnvidia-decode-545 libnvidia-decode-545:i386 libnvidia-encode-545 libnvidia-encode-545:i386 libnvidia-extra-545 libnvidia-fbc1-545 libnvidia-fbc1-545:i386 libnvidia-gl-545 libnvidia-gl-545:i386 nvidia-compute-utils-545 nvidia-dkms-545 nvidia-driver-545 nvidia-kernel-common-545 nvidia-kernel-source-545 nvidia-utils-545 xserver-xorg-video-nvidia-545 The following NEW packages will be installed: libnvidia-cfg1-550 libnvidia-common-550 libnvidia-compute-550 libnvidia-compute-550:i386 libnvidia-decode-550 libnvidia-decode-550:i386 libnvidia-encode-550 libnvidia-encode-550:i386 libnvidia-extra-550 libnvidia-fbc1-550 libnvidia-fbc1-550:i386 libnvidia-gl-550 libnvidia-gl-550:i386 nvidia-compute-utils-550 nvidia-dkms-550 nvidia-driver-550 nvidia-firmware-550-550.67 nvidia-kernel-common-550 nvidia-kernel-source-550 nvidia-utils-550 xserver-xorg-video-nvidia-550 0 upgraded, 21 newly installed, 20 to remove and 15 not upgraded. 2 not fully installed or removed. Need to get 360 MB of archives. After this operation, 14.7 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu noble/multiverse amd64 nvidia-dkms-550 amd64 550.67-0ubuntu3 [35.8 kB] Get:2 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-cfg1-550 amd64 550.67-0ubuntu3 [155 kB] Get:3 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-common-550 all 550.67-0ubuntu3 [14.8 kB] Get:4 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-compute-550 amd64 550.67-0ubuntu3 [41.3 MB] Get:5 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-compute-550 i386 550.67-0ubuntu3 [41.2 MB] Get:6 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-decode-550 amd64 550.67-0ubuntu3 [2,028 kB] Get:7 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-decode-550 i386 550.67-0ubuntu3 [2,470 kB] Get:8 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-encode-550 i386 550.67-0ubuntu3 [115 kB] Get:9 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-encode-550 amd64 550.67-0ubuntu3 [105 kB] Get:10 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-extra-550 amd64 550.67-0ubuntu3 [72.9 kB] Get:11 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-fbc1-550 amd64 550.67-0ubuntu3 [56.4 kB] Get:12 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-fbc1-550 i386 550.67-0ubuntu3 [61.9 kB] Get:13 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-gl-550 amd64 550.67-0ubuntu3 [155 MB] Get:14 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-gl-550 i386 550.67-0ubuntu3 [33.8 MB] Get:15 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-compute-utils-550 amd64 550.67-0ubuntu3 [123 kB] Get:16 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-kernel-source-550 amd64 550.67-0ubuntu3 [41.7 MB] Get:17 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-firmware-550-550.67 amd64 550.67-0ubuntu3 [38.1 MB] Get:18 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-kernel-common-550 amd64 550.67-0ubuntu3 [120 kB] Get:19 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-utils-550 amd64 550.67-0ubuntu3 [521 kB] Get:20 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 xserver-xorg-video-nvidia-550 amd64 550.67-0ubuntu3 [1,616 kB] Get:21 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-driver-550 amd64 550.67-0ubuntu3 [486 kB] Fetched 360 MB in 30s (11.8 MB/s) (Reading database ... 339762 files and directories currently installed.) Removing nvidia-driver-545 (545.29.06-0ubuntu0~gpu24.04.1) ... Removing nvidia-dkms-545
[Ubuntu-x-swat] [Bug 2049976] [NEW] multiscreen one display goes black on resume
Public bug reported: Starting a few weeks ago after applying regular maintenance to 22.04.3 LTS one of my two displays, an LG 22MP47HQ-P connected to my tower by a D-Sub cable, blinked multiple times immediately on resume from suspend. My second display which is connected using HDMI works normally. This, of course, was merely a mild annoyance because after a few seconds it stopped. However in the past week that same display flashes on, and then goes black. I power the display off and back on and again it flashes on for a fraction of a second and then goes black. After several power cycles of the display it stays on, so again this is only a mild annoyance. Is this a known issue with a recent update? Specifically this is after a deep suspend, one where on unlock you need to press a key to get the login prompt. I tried updating to 23.10 but the problem is there as well. This bug tool does not permit reporting a problem against Wayland. lshw -C video *-display description: VGA compatible controller product: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 logical name: /dev/fb0 version: 06 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom fb configuration: depth=32 driver=i915 latency=0 resolution=1920,1080 resources: irq:31 memory:f780-f7bf memory:e000-efff ioport:f000(size=64) memory:c-d /var/log/apt/history.log taken immediately after encountering the issue on 22.04 Start-Date: 2024-01-02 16:01:30 Commandline: aptdaemon role='role-commit-packages' sender=':1.7295' Upgrade: thunderbird:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1), thunderbird-locale-en:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1), thunderbird-locale-en-gb:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1), thunderbird-locale-en-us:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1), thunderbird-gnome-support:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1) End-Date: 2024-01-02 16:01:33 Start-Date: 2024-01-03 16:57:04 Commandline: /usr/bin/unattended-upgrade Upgrade: libsqlite3-dev:amd64 (3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3), libsqlite3-0:amd64 (3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3), sqlite3:amd64 (3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3) End-Date: 2024-01-03 16:57:05 Start-Date: 2024-01-03 16:57:08 Commandline: /usr/bin/unattended-upgrade Upgrade: openssh-client:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6), openssh-server:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6), openssh-sftp-server:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6) End-Date: 2024-01-03 16:57:10 Start-Date: 2024-01-03 16:57:13 Commandline: /usr/bin/unattended-upgrade Upgrade: libnode72:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3), nodejs:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3), libnode-dev:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3) End-Date: 2024-01-03 16:57:14 Start-Date: 2024-01-03 16:57:16 Commandline: /usr/bin/unattended-upgrade Upgrade: nodejs-doc:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3) End-Date: 2024-01-03 16:57:17 Start-Date: 2024-01-09 20:43:19 Commandline: aptdaemon role='role-commit-packages' sender=':1.9514' Install: php8.3-xml:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), php8.3-mbstring:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), php8.3-common:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), php8.3-intl:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic) Upgrade: php-common:amd64 (2:93+ubuntu22.04.1+deb.sury.org+3, 2:94+ubuntu22.04.1+deb.sury.org+1), software-properties-common:amd64 (0.99.22.8, 0.99.22.9), python3-software-properties:amd64 (0.99.22.8, 0.99.22.9), php-intl:amd64 (2:8.2+93+ubuntu22.04.1+deb.sury.org+3, 2:8.3+94+ubuntu22.04.1+deb.sury.org+1), php-mbstring:amd64 (2:8.2+93+ubuntu22.04.1+deb.sury.org+3, 2:8.3+94+ubuntu22.04.1+deb.sury.org+1), software-properties-gtk:amd64 (0.99.22.8, 0.99.22.9), python3-distro-info:amd64 (1.1ubuntu0.1, 1.1ubuntu0.2), distro-info-data:amd64 (0.52ubuntu0.5, 0.52ubuntu0.6), linux-firmware:amd64 (20220329.git681281e4-0ubuntu3.23, 20220329.git681281e4-0ubuntu3.24), php-xml:amd64 (2:8.2+93+ubuntu22.04.1+deb.sury.org+3, 2:8.3+94+ubuntu22.04.1+deb.sury.org+1), distro-info:amd64 (1.1ubuntu0.1, 1.1ubuntu0.2) End-Date: 2024-01-09 20:45:50 Start-Date: 2024-01-10 21:58:10 Commandline: /usr/bin/unattended-upgrade Upgrade: libc6:amd64 (2.35-0ubuntu3.5, 2.35-0ubuntu3.6), libc6:i386 (2.35-0ubuntu3.5, 2.35-0ubuntu3.6), libc-dev-bin:amd64 (2.35-0ubuntu3.5, 2.35-0ubuntu3.6), libc6-dbg:amd64 (2.35-0ubuntu3.5, 2.35-0ubuntu3.6), libc6-dev:amd64 (2.35-0ubuntu3.5, 2.35-0ubuntu3.6) End-Date: 2024-01-10 21:58:28 Start-Date: 2024-01-10 21:58:35 Commandline: /usr/bin/unattended-upgrade Upgrade: libc-bin:amd64
[Ubuntu-x-swat] [Bug 2037497]
(In reply to Adam Williamson from comment #20) > Scratch build is done for x86_64: > https://koji.fedoraproject.org/koji/taskinfo?taskID=107101328 > > can folks test that and see if it helps? Thanks! Works after updating to the packages in that Koji task. -- 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/2037497 Title: gnome-shell crashes on Intel Ice Lake with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2037497/+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 2037497]
(In reply to Adam Williamson from comment #14) > Can reporters please test downgrading packages to figure out what actually > fixes this? I'd suggest this order: > > 1. Downgrade mesa to > https://koji.fedoraproject.org/koji/buildinfo?buildID=2274339 > 2. If that doesn't fix it, downgrade mutter and gnome-shell to > https://koji.fedoraproject.org/koji/buildinfo?buildID=2284675 and > https://koji.fedoraproject.org/koji/buildinfo?buildID=2284676 > > if that doesn't fix it, report back and we'll try something else, I guess. :D > > Instructions for downgrading: `dnf -y install koji`, then make a scratch dir > somewhere (in your home dir or /var/tmp or something), and do `koji > download-build --arch=x86_64 --arch=noarch (buildid)` , where (buildid) is > the build ID from the URL, so 2274339 for mesa. Then do `dnf downgrade > *.rpm`. None of this worked, nor mesa-23.2.0~rc2-1.fc39. I was able to get it working again by downgrading to mesa-23.1.5-1.fc39 (build 2268808). Will try to bisect. -- 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/2037497 Title: gnome-shell crashed with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2037497/+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 2019917] Re: No VA-API VAEntrypointVideoProc on Kaby Lake with the (free) intel-media-driver
** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer/-/issues #2580 https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/2580 ** Also affects: gstreamer via https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/2580 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-media-driver in Ubuntu. https://bugs.launchpad.net/bugs/2019917 Title: No VA-API VAEntrypointVideoProc on Kaby Lake with the (free) intel- media-driver To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/2019917/+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 2019917] Re: No VA-API VAEntrypointVideoProc on Kaby Lake with the (free) intel-media-driver
The use of vaapipostproc in Totem appears to be through vaapidecodebin: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/blob/main/subprojects/gstreamer- vaapi/gst/vaapi/gstvaapidecodebin.c#L326-329 The error path there calls post_missing_element_message(), which would trigger Totem's message. It seems like an odd choice though, since the two elements come from the same plugin: if it is missing, there's no other plugins you could install to fix it. The creation of the postprocessing element is controlled by the "disable-vpp" GObject property, and defaults to true if the GST_VAAPI_DISABLE_VPP environment variable is set: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/blob/main/subprojects/gstreamer- vaapi/gst/vaapi/gstvaapidecodebin.c#L406 And running "GST_VAAPI_DISABLE_VPP=1 totem filename.mp4" does seem to work. I also gave the i965 driver a try with "LIBVA_DRIVER_NAME=i965 totem filename.mp4", which played the video but with corrupted video (maybe tiling related?). i965 with DISABLE_VPP=1 plays fine though, so is not necessarily a better choice for this generation of hardware. On the GStreamer side, the best option would probably be to stop posting the missing element message and just disable VPP automatically if it can't create the element. I'll look at putting together an upstream bug for that. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-media-driver in Ubuntu. https://bugs.launchpad.net/bugs/2019917 Title: No VA-API VAEntrypointVideoProc on Kaby Lake with the (free) intel- media-driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/2019917/+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 2019917] Re: No VA-API VAEntrypointVideoProc on Kaby Lake
It looks like this isn't related to the other bug report. I hadn't fully understood the table at the bottom of this readme file: https://github.com/intel/media-driver/blob/master/README.md Looks like my CPU is one year too old to support post-processing with the free shaders. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-media-driver in Ubuntu. https://bugs.launchpad.net/bugs/2019917 Title: No VA-API VAEntrypointVideoProc on Kaby Lake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/2019917/+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 2019831] Re: intel-media-va-driver VPP broken until 22.6.5
I also ran into a problem with missing VA-API post processing support on Lunar. I filed it as bug 2019917 since Lunar ships a version that includes the purported fix mentioned in the Github issue, and I'm unsure if it is actually the same problem. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-media-driver in Ubuntu. https://bugs.launchpad.net/bugs/2019831 Title: intel-media-va-driver VPP broken until 22.6.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/2019831/+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 2019917] [NEW] No VA-API VAEntrypointVideoProc on Lunar
Public bug reported: On my laptop with an Intel Core i7-7500U CPU (Kaby Lake), the iHD VA-API driver does not report VAEntrypointVideoProc support in the output of vainfo: libva info: VA-API version 1.17.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_17 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.17 (libva 2.12.0) vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 23.1.2 () vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSliceLP VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileVP9Profile0: VAEntrypointVLD VAProfileVP9Profile2: VAEntrypointVLD Normally I'd expect to also see a line like: VAProfileNone : VAEntrypointVideoProc Among other things, this causes Totem to malfunction with the error "GStreamer element vaapipostproc is required to play the file, but it is not installed". Presumably it assumes that if hardware accelerated decoders are available, so is post processing. This seems like it might possibly be related to bug 2019831, but that was about problems in Jammy and the version it suggests should fix the problem is older than what's shipped in Lunar. Either they reintroduced the problems, or it wasn't really fixed. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: intel-media-va-driver 23.1.2+dfsg1-1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed May 17 12:39:40 2023 InstallationDate: Installed on 2017-09-02 (2082 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901) SourcePackage: intel-media-driver UpgradeStatus: Upgraded to lunar on 2023-03-29 (49 days ago) ** Affects: intel-media-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-media-driver in Ubuntu. https://bugs.launchpad.net/bugs/2019917 Title: No VA-API VAEntrypointVideoProc on Lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/2019917/+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 1677050] GOOD DAY!
Hope this email finds you well! Been thinking of you lately. Please let me know when you get this, I'd like to ask you something. Stay safe and healthy, Jim -- 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/1677050 Title: Youtube video will not run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1677050/+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 1967064] ProcInterrupts.txt
*** This bug is a duplicate of bug 1964037 *** https://bugs.launchpad.net/bugs/1964037 apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1967064/+attachment/5574624/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1967064 Title: wayland crash when plugging in external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967064/+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 1967064] ProcCpuinfoMinimal.txt
*** This bug is a duplicate of bug 1964037 *** https://bugs.launchpad.net/bugs/1964037 apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1967064/+attachment/5574622/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1967064 Title: wayland crash when plugging in external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967064/+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 1967064] Lsusb.txt
*** This bug is a duplicate of bug 1964037 *** https://bugs.launchpad.net/bugs/1964037 apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1967064/+attachment/5574617/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1967064 Title: wayland crash when plugging in external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967064/+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 1967064] acpidump.txt
*** This bug is a duplicate of bug 1964037 *** https://bugs.launchpad.net/bugs/1964037 apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1967064/+attachment/5574628/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1967064 Title: wayland crash when plugging in external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967064/+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 1967064] xdpyinfo.txt
*** This bug is a duplicate of bug 1964037 *** https://bugs.launchpad.net/bugs/1964037 apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1967064/+attachment/5574630/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1967064 Title: wayland crash when plugging in external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967064/+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 1967064] Xrandr.txt
*** This bug is a duplicate of bug 1964037 *** https://bugs.launchpad.net/bugs/1964037 apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1967064/+attachment/5574627/+files/Xrandr.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1967064 Title: wayland crash when plugging in external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967064/+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 1967064] nvidia-settings.txt
*** This bug is a duplicate of bug 1964037 *** https://bugs.launchpad.net/bugs/1964037 apport information ** Attachment added: "nvidia-settings.txt" https://bugs.launchpad.net/bugs/1967064/+attachment/5574629/+files/nvidia-settings.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1967064 Title: wayland crash when plugging in external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967064/+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 1967064] UdevDb.txt
*** This bug is a duplicate of bug 1964037 *** https://bugs.launchpad.net/bugs/1964037 apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1967064/+attachment/5574626/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1967064 Title: wayland crash when plugging in external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967064/+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 1967064] ProcModules.txt
*** This bug is a duplicate of bug 1964037 *** https://bugs.launchpad.net/bugs/1964037 apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1967064/+attachment/5574625/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1967064 Title: wayland crash when plugging in external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967064/+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 1967064] ProcEnviron.txt
*** This bug is a duplicate of bug 1964037 *** https://bugs.launchpad.net/bugs/1964037 apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1967064/+attachment/5574623/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1967064 Title: wayland crash when plugging in external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967064/+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 1967064] ProcCpuinfo.txt
*** This bug is a duplicate of bug 1964037 *** https://bugs.launchpad.net/bugs/1964037 apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1967064/+attachment/5574621/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1967064 Title: wayland crash when plugging in external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967064/+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 1967064] NvidiaBugReportLog.txt
*** This bug is a duplicate of bug 1964037 *** https://bugs.launchpad.net/bugs/1964037 apport information ** Attachment added: "NvidiaBugReportLog.txt" https://bugs.launchpad.net/bugs/1967064/+attachment/5574620/+files/NvidiaBugReportLog.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1967064 Title: wayland crash when plugging in external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967064/+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 1967064] Lspci-vt.txt
*** This bug is a duplicate of bug 1964037 *** https://bugs.launchpad.net/bugs/1964037 apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1967064/+attachment/5574616/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1967064 Title: wayland crash when plugging in external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967064/+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 1967064] Lsusb-v.txt
*** This bug is a duplicate of bug 1964037 *** https://bugs.launchpad.net/bugs/1964037 apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1967064/+attachment/5574619/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1967064 Title: wayland crash when plugging in external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967064/+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 1967064] Lsusb-t.txt
*** This bug is a duplicate of bug 1964037 *** https://bugs.launchpad.net/bugs/1964037 apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1967064/+attachment/5574618/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1967064 Title: wayland crash when plugging in external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967064/+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 1967064] CurrentDmesg.txt
*** This bug is a duplicate of bug 1964037 *** https://bugs.launchpad.net/bugs/1964037 apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1967064/+attachment/5574613/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1967064 Title: wayland crash when plugging in external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967064/+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 1967064] Lspci.txt
*** This bug is a duplicate of bug 1964037 *** https://bugs.launchpad.net/bugs/1964037 apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1967064/+attachment/5574615/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1967064 Title: wayland crash when plugging in external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967064/+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 1967064] DpkgLog.txt
*** This bug is a duplicate of bug 1964037 *** https://bugs.launchpad.net/bugs/1964037 apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1967064/+attachment/5574614/+files/DpkgLog.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1967064 Title: wayland crash when plugging in external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967064/+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 1967064] Re: wayland crash when plugging in external monitor
*** This bug is a duplicate of bug 1964037 *** https://bugs.launchpad.net/bugs/1964037 apport information ** Tags added: apport-collected jammy ubuntu wayland-session ** Description changed: - When I plug in an external monitor via usb-c thunderbolt port wayland - crashes and returns to the login screen. + When I plug in an external monitor via usb-c thunderbolt port wayland crashes and returns to the login screen. + --- + ProblemType: Bug + .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. + .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. + .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. + .proc.driver.nvidia.registry: Binary: "" + .proc.driver.nvidia.suspend: suspend hibernate resume + .proc.driver.nvidia.suspend_depth: default modeset uvm + .proc.driver.nvidia.version: + NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.54 Tue Feb 8 04:42:21 UTC 2022 + GCC version: + ApportVersion: 2.20.11-0ubuntu79 + Architecture: amd64 + BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' + CasperMD5CheckResult: pass + CompositorRunning: None + CurrentDesktop: ubuntu:GNOME + DistUpgraded: Fresh install + DistroCodename: jammy + DistroRelease: Ubuntu 22.04 + DistroVariant: ubuntu + DkmsStatus: openrazer-driver/3.2.0, 5.15.0-23-generic, x86_64: installed + GraphicsCard: + Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) (prog-if 00 [VGA controller]) +Subsystem: Razer USA Ltd. TigerLake-H GT1 [UHD Graphics] [1a58:2018] + NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [10de:249c] (rev a1) (prog-if 00 [VGA controller]) +Subsystem: Razer USA Ltd. GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [1a58:2018] + InstallationDate: Installed on 2022-03-26 (4 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325) + MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409 + NonfreeKernelModules: nvidia_modeset nvidia + Package: wayland (not installed) + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 + Tags: wayland-session jammy ubuntu + Uname: Linux 5.15.0-23-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/12/2021 + dmi.bios.release: 2.2 + dmi.bios.vendor: Razer + dmi.bios.version: 2.02 + dmi.board.name: CH570 + dmi.board.vendor: Razer + dmi.board.version: 4 + dmi.chassis.type: 10 + dmi.chassis.vendor: Razer + dmi.ec.firmware.release: 1.2 + dmi.modalias: dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3: + dmi.product.family: 1A582018 Razer Blade + dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409 + dmi.product.sku: RZ09-0409CEC3 + dmi.product.version: 7.04 + dmi.sys.vendor: Razer + version.compiz: compiz N/A + version.libdrm2: libdrm2 2.4.110-1ubuntu1 + version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2 + version.libgl1-mesa-glx: libgl1-mesa-glx N/A + version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A + version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 + version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A + version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 + version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 + version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Attachment added: ".proc.driver.nvidia.params.txt" https://bugs.launchpad.net/bugs/1967064/+attachment/5574612/+files/.proc.driver.nvidia.params.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1967064 Title: wayland crash when plugging in external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967064/+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 1967064] [NEW] wayland crash when plugging in external monitor
Public bug reported: When I plug in an external monitor via usb-c thunderbolt port wayland crashes and returns to the login screen. ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: nvidia wayland -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1967064 Title: wayland crash when plugging in external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1967064/+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 1962237] Re: blue tooth/wireless mouse not working
never mind. Batteries replaced work wonders. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1962237 Title: blue tooth/wireless mouse not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1962237/+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 1962237] Re: blue tooth/wireless mouse not working
Ran this hack: https://www.youtube.com/watch?v=I2rHRi2ll9Q and rebooted in recovery mode and mouse is at least temporarily functional. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1962237 Title: blue tooth/wireless mouse not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1962237/+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 1962237] Re: blue tooth/wireless mouse not working
I left a comment about how my system on re-launch appears to revert to 2-22-22 which, I assume is when I attempted to install the update. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1962237 Title: blue tooth/wireless mouse not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1962237/+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 1962237] Re: blue tooth/wireless mouse not working
It appears that on launch, my system is reverting to 2-22-22 which, I assume, is when the update was autoloaded and attempted to run. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1962237 Title: blue tooth/wireless mouse not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1962237/+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 1962237] [NEW] blue tooth/wireless mouse not working
Public bug reported: The mouse can occasionally be made to work by going back through settings, etc. but then very shortly stops again. I recently updated the system and had to interrupt the update as it was in an infinite loop while install was running. I am also running a bitcoin node that is not remembering where I was on the last run of bitcoin core. ** Affects: xdiagnose (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1962237 Title: blue tooth/wireless mouse not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1962237/+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 1960569] Re: Screen goes dim
@Daniel .. Thanks. * I think brightness-controller is a thin UI around xrandr. If something in Ubuntu is improperly changing "Brightness" and xrandr is the only cure, why remove brightness-controller? Or, do your comments about it apply equally to xrandr -- namely that I should avoid xrandr, too? * I rebooted and chose "GNOME" (one of two identically-named options); I'll report back when (if) the screens go dim again. If things stay stable, I will report back later to help close (and blame MATE). I did not notice whether one login option said "on Xorg"; I'll look for that next time. * Thinking back, I wonder if a screensaver was implicated in the problem. * (Unrelated) I liked the GNOME UI on 20.10; MATE 21.10 has some annoying differences, so I am happy to learn how to go back to GNOME while staying with the same version 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/1960569 Title: Screen goes dim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1960569/+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
Re: [Ubuntu-x-swat] [Bug 1734500] Re: Ubuntu Web Browser content upside down on rotated screen
Please feel free to let the bug expire unsolved. While I still use two monitors arranged as described in the bug report, I don't have software available to test whether the bug still exists. On my Ubuntu 20.04systemI don't have an Amazon icon on a launcher screen, and "webbrowser-app" is not installed. An attempt to install it perhowtoinstall.co/en/webbrowser-app directionsgives "E: Unable to locate package webbrowser-app". On 1/21/22 4:17 AM, Paul White wrote: > We are sorry that we do not always have the capacity to review all > reported bugs in a timely manner. You reported this bug some time ago > and there have been many changes in Ubuntu since that time. > > Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021. > > Do you still see a problem related to the one that you reported when > using a currently supported version of Ubuntu? Please let us know if you > do otherwise this report can be left to expire in approximately 60 days > time. > > Thank you for helping make Ubuntu better. > > > ** Changed in: xorg (Ubuntu) > Status: Confirmed => 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/1734500 Title: Ubuntu Web Browser content upside down on rotated screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1734500/+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 1956193] [NEW] package libnvidia-compute-390 (not installed) failed to install/upgrade: 共有されている '/etc/OpenCL/vendors/nvidia.icd' を上書きしようとしています。これはパッケージ libnvidia-compute-390:i386
Public bug reported: An attempt to do a clean install of NVIDIA drivers resulted in errors. I was doing so as a program I was intending to use detected that the pre- installed drivers did not let me use CUDA. Running a somewhat newly installed Ubuntu 20.04 I expected it to load the drivers as normal but it just gave me errors, ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-compute-390 (not installed) ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jan 2 16:36:13 2022 ErrorMessage: 共有されている '/etc/OpenCL/vendors/nvidia.icd' を上書きしようとしています。これはパッケージ libnvidia-compute-390:i386 の他の実体と異なります InstallationDate: Installed on 2021-12-26 (7 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-compute-390 (not installed) failed to install/upgrade: 共有されている '/etc/OpenCL/vendors/nvidia.icd' を上書きしようとしています。これはパッケージ libnvidia-compute-390:i386 の他の実体と異なります UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal ** Attachment added: "Picture of additional drivers" https://bugs.launchpad.net/bugs/1956193/+attachment/5550702/+files/Screenshot%20from%202022-01-02%2016-44-06.png -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1956193 Title: package libnvidia-compute-390 (not installed) failed to install/upgrade: 共有されている '/etc/OpenCL/vendors/nvidia.icd' を上書きしようとしています。これはパッケージ libnvidia-compute-390:i386 の他の実体と異なります To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1956193/+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 1217585] Re: System hangs after some time with nouveau and GT240
It appears the same crash symptoms are still happening on Ubuntu 20.04 with xserver-xorg-video-nouveau package and Nvidia GT240 chipset. Details in Launchpad bug #1954335 - https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- nouveau/+bug/1954335 Package version: $ dpkg -l xserver-xorg-video-nouveau | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==--- ii xserver-xorg-video-nouveau 1:1.0.16-1 amd64X.Org X server -- Nouveau display driver See linked duplicate bug #1954335 for journalctl crash logs, lspci & lshw output. -- 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/1217585 Title: System hangs after some time with nouveau and GT240 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1217585/+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 1954335] Re: nouveau driver frequently freezing / crashing kernel on fresh 20.04 install
*** This bug is a duplicate of bug 1217585 *** https://bugs.launchpad.net/bugs/1217585 ** This bug has been marked a duplicate of bug 1217585 System hangs after some time with nouveau and GT240 ** Tags added: amd64 ** Tags added: focal -- 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/1954335 Title: nouveau driver frequently freezing / crashing kernel on fresh 20.04 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1954335/+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 1954335] [NEW] nouveau driver frequently freezing / crashing kernel on fresh 20.04 install
*** This bug is a duplicate of bug 1217585 *** https://bugs.launchpad.net/bugs/1217585 Public bug reported: Hello, I'm experiencing frequent crashes that hard-lock the system and kernel completely. Symptoms are: - Frozen screen - No Keyboard or Mouse input accepted - Remote SSH times out as if system is not responding - Kernel does not respond to the "Alt + SysRq + REISUB" key sequence to force a reboot. (kernel was compiled with CONFIG_MAGIC_SYSRQ=y) I tracked down the issue to the nouveau driver (see attached journalctl logs for crash dump) The primary and only PCI Video card in the system is quite old and thus should be well supported: - 01:00.0 VGA compatible controller: NVIDIA Corporation GT215 [GeForce GT 240] (rev a2) lshw output: $ sudo lshw -class display *-display description: VGA compatible controller product: GT215 [GeForce GT 240] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a2 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:166 memory:ee00-eeff memory:d000-dfff memory:e000-e1ff ioport:e000(size=128) memory:c-d ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Attachment added: "journalctl logs from last nouveau crash" https://bugs.launchpad.net/bugs/1954335/+attachment/5546522/+files/2021-12-09-nouveau-kernel-crashbug.log -- 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/1954335 Title: nouveau driver frequently freezing / crashing kernel on fresh 20.04 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1954335/+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 1926248] [NEW] display scrambled - all packages
Public bug reported: shortly after switching to kernel 5.8.0-50 on Apr 16, I got progressively worse display scrambling on all programs. Wrote to ubuntuforums.org Apr 19 but found no resolution. Thinking it was that kernel, I ran on 5.8.0-49 for a day without problem, then it too started the same display glitches. The problem progressed so far that I did a fresh system re-install on Apr 23. After, with the default kernel, 5.8.0-50, scrambling was worse than ever, almost unusable. Fortunately, the second kernel offered was 5.8.0-43. I have run on that kernel for 3 days now with no sign of the scrambling issue. The attached png shows static image corruption examples. The more dramatic strobing, spontaneous jumping from window to window, window re-mapping, video corruption etc., I was unable to capture. Running Ubuntu 20.04.2 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 21:48:37 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1028:0622] InstallationDate: Installed on 2021-04-23 (3 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Inspiron 3847 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=0fa2ade9-fdd6-4cfa-a153-0de2be1f39ae ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/29/2015 dmi.bios.release: 65.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 088DT1 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd06/29/2015:br65.8:svnDellInc.:pnInspiron3847:pvr:rvnDellInc.:rn088DT1:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: Inspiron 3847 dmi.product.sku: 0622 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu ** Attachment added: "static corruption examples" https://bugs.launchpad.net/bugs/1926248/+attachment/5492641/+files/joint%20scramble%20examples.png -- 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/1926248 Title: display scrambled - all packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926248/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
The solution has been found and should have been rather obvious in the first place... Just try a different distribution. I decided to try out Linux Mint 20.1 and have been testing it for the past ~6 hours, completely stock (except for all updates installed), no kernel modifications or GRUB options and it works every time on bootup with the touchpad. I am rather surprised that such a relatively old kernel (5.4) works with this new-ish laptop. Perhaps this was why I was so falsely focused on having newer kernels available in a distribution in the first place. I even tried 40 consecutive reboots whilst messing with the touchpad as the machine was booting and it still worked every time. Let it be known that the fix for the Lenovo IdeaPad 3 14ADA05 is to simply install Linux Mint. I have to imagine that other Ubuntu-based installs also work with this particular laptop, especially since it says "Fix Released" under Ubuntu and Ubuntu-related distributions. As far as Manjaro goes, also let it be known that something was introduced after Kernel 5.9.16-1 which breaks the ability for the touchpad to reliably work with this laptop. My best educated guess is that something is loaded too early or too late during bootup which gets jumbled up at random. No idea what that could possibly be, but I hope that Manjaro devs might take note. I know that at least @Helmut Stult might still be looking in this thread. I consider this fixed for my laptop :) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Well, I spent the past few hours pouring over the entirety of this thread and I didn't try the patches to pinctrl-amd.c provided by @Helmut Stult in post #317. These were downloaded and placed in the same source directory as the other patches for Manjaro kernel 5.11.13-1 and lines were added to the PKGBUILD file for the patches. - 0303-pinctrl-amd2.patch fails to apply with error "Hunk #1 FAILED at 472". This is presumably because the code that the patch is trying to change is not present in 5.11.13-1, if I am right in my interpretation of it. - 0303-revert-pinctrl_amd_remove_debounce_filter_setting_in_IRQ_type_setting.patch - Successfully validates, applies and I was able to compile and install 5.11.13-1 and the kernel functions on bootup. However, this too did not resolve the issue. The touchpad failed on bootup in the expected 1-30 reboot range (Got to 9 reboots), just as if no patch were applied. I am out of ideas and need some help from an expert, @Coiby Xu. There is nothing else for me to try and I'm not a programmer so I don't know how to create a solution from scratch. Thanks for any help moving forward. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Hey there @Coiby Xu thank you, I think I understand what you mean, basically use your Github for this, standalone_i2c_hid, but copy the i2c drivers from the cloned Manjaro kernel 5.9.16-1 ../src/linux-5.9/drivers/hid/i2c-hid/ directory into the ../i2c-hid_standalone/ directory in your project (replacing all 3 source files without the Makefile), then compile it and replace the according module in my running system. Just as a reference, directly dropping in /lib/modules/5.9.16-1-MANJARO/kernel/drivers/hid/i2c-hid/i2c-hid.ko.xz into the respective 5.11.6-1-MANJARO ../i2c-hid/ directory, then running "mkinitcpio -P linux511" (to use the new module.. if this is how to do it?) does not work, in case anyone was wondering. Touchpad immediately froze on bootup. ** I was able to compile the Manjaro 5.9.16-1 source files into a module (on 5.11.6-1 using linux511-headers) using your provided Makefile and followed the instructions to copy the compiled module into the 5.11.6-1-MANJARO ../i2c-hid/ directory. Also added the GRUB options and ran "sudo update-grub". It functioned, but did not fix the issue. Froze after 2 reboots. I also tried compiling the Github project as it is, using the provided source files (on 5.11.6-1 using linux511-headers) and it spit out: ERROR: modpost "irq_to_desc" (in ../i2c-hid-standalone/i2c-hid.ko) undefined ! ../i2c-hid-standalone/Module.symvers Error 1 Also I wanted to point out in your README the instruction to append "i2c_hid.polling_mode=1" to GRUB_CMDLINE_LINUX. Shouldn't this be appended to GRUB_CMDLINE_LINUX_DEFAULT? I don't really know, I've just never seen the non-_DEFAULT line used before. In either case, produces same results. Thanks for all your help, it was worth a shot. Maybe your code needs to be updated for recent kernels? I am still trying to play with the idea of focusing on the pinctrl-amd.c driver, but really need some help with what to do with that driver. I am not sure the culprit is the i2c_hid driver, but rather this driver. Maybe I'm wrong, but it certainly is the next place to look... Fun things to try! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
I don't know what I was comparing before, but I was wrong. The pinctrl- amd.c drivers are different between the two kernels. Apologies. I wonder if just dropping in the 5.9 pinctrl-amd.c driver (+possibly other related needed ones?) into 5.10 (or later) would work? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Since this is the main thread on the Internet about this issue, I suppose it is appropriate to post here even though I am using Manjaro. - This issue is non-present on a Thinkpad 3 14ADA05 with touchpad MSFT0001:00 06CB:CE2D on kernel 5.9.16-1 which uses i2c_hid. It is not elantech or designware (doesn't load the associated specific i2c drivers). Installing an entirely new keyboard panel with a new touchpad, essentially rebuilding the entire laptop does not address this issue. It is the same model touchpad for this specific laptop model even if you order a new one (unless I got bad luck of the draw). - The issue becomes present on kernel 5.10.23-1 (and previous versions of 5.10) up to 5.12rc3. Have not tried compiling 5.12rc5, but no reason to believe it would work. The touchpad will fail to be recognized and work on bootup between 1-30 reboots. I have tried many things such as different kernels and GRUB_CMDLINE_LINUX_DEFAULT options, yes even checking to set the kernel config option others are suggesting (Manjaro removed then reinstated the CONFIG_I2C_HID_ACPI=m option). I also tore apart kernels 5.9 and 5.10 to look at the pinctrl-amd.c driver and found that there was no difference between the two on these kernels, so it is something other than what https://launchpadlibrarian.net/500948605/0303-pinctrl-amd2.patch addresses since it works on the former kernel but not the latter. Also, the patch fails to apply on 5.12rc5. I don't really know how to compare the entire torn-apart kernels 5.9 and 5.10 to try and find what change(s) could possibly cause this bug. Hopefully someone else knows how to? Might be able to get somewhere if so... Other mods might be replacing the touchpad with a model not designed for the laptop, but I don't know where to start with that either. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1913453] [NEW] Xorg freeze
Public bug reported: System Description:Ubuntu 20.04.1 LTS Release:20.04 Description: Plugging in USB hub with peripherals while system is running causes gradual lag of a visual response, until freezing. usually takes < 1 min. Only work around is to sleep system between plugging in hub. I thought I fixed it by change DM but the issue has persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 27 14:27:12 2021 DistUpgraded: 2020-04-28 14:42:33,856 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-62-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-64-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-65-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] InstallationDate: Installed on 2018-12-25 (763 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 2324AS7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=957184f1-8feb-4ca9-ac97-3fb70937b4ac ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-04-28 (274 days ago) dmi.bios.date: 04/11/2018 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324AS7 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETB2WW(2.72):bd04/11/2018:svnLENOVO:pn2324AS7:pvrThinkPadX230:rvnLENOVO:rn2324AS7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2324AS7 dmi.product.sku: LENOVO_MT_2324 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~ppa1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Tue Nov 24 16:32:27 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.4 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze third-party-packages ubuntu wayland-session ** Description changed: System Description: Ubuntu 20.04.1 LTS Release: 20.04 Description: Plugging in USB hub with peripherals while system is running causes gradual lag of a visual response, until freezing. usually takes < 1 min. Only work around is to sleep system between plugging in hub. - I thought I fixed it by change DE but the issue has persisted. + I thought I fixed it by change DM but the issue has persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 .tmp.unity_support_test.0: - + ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 27 14:27:12 2021 DistUpgraded: 2020-04-28 14:42:33,856 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: - acpi-call, 1.1.0, 5.4.0-62-generic, x86_64: installed - acpi-call, 1.1.0, 5.4.0-64-generic, x86_64: installed - acpi-call, 1.1.0, 5.4.0-65-generic, x86_64: installed + acpi-call, 1.1.0, 5.4.0-62-generic, x86_64: installed + acpi-call, 1.1.0, 5.4.0-64-generic, x86_64: installed + acpi-call, 1.1.0, 5.4.0-65-generic, x86_64: installed
[Ubuntu-x-swat] [Bug 1900360] [NEW] Xorg freeze
Public bug reported: Description:Ubuntu 20.04.1 LTS Release:20.04 xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I think the problem arises from use of a USB switch. However it does not necessarily happen when engaging or disengaging USB hub. Inbuilt trackpad allows use of cursor during freeze, but not usb attatched mouse. aside from that nothing gets a response on the display. Using a Thinkpad X230 kern.log includes crash ``` Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.457323] usb 3-3.1: USB disconnect, device number 4 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.457328] usb 3-3.1.1: USB disconnect, device number 5 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.504690] usb 3-3.1.4: USB disconnect, device number 8 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663393] BUG: unable to handle page fault for address: 1c18 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663396] #PF: supervisor read access in kernel mode Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663398] #PF: error_code(0x) - not-present page Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663399] PGD 0 P4D 0 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663402] Oops: [#1] SMP PTI Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663405] CPU: 2 PID: 25 Comm: kworker/2:0 Not tainted 5.4.0-51-generic #56-Ubuntu Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663406] Hardware name: LENOVO 2324AS7/2324AS7, BIOS G2ETB2WW (2.72 ) 04/11/2018 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663412] Workqueue: usb_hub_wq hub_event Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663417] RIP: 0010:holtek_kbd_input_event+0x4d/0x80 [hid_holtek_kbd] Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663419] Code: 80 10 19 00 00 48 8b 78 40 48 81 ef a0 00 00 00 e8 78 b4 62 d5 48 85 c0 74 2f 48 8b 80 a8 00 00 00 44 89 f1 44 89 ea 44 89 e6 <48> 8b 80 18 1c 00 00 48 8b 78 18 48 8b 87 e0 01 00 00 e8 4c 5c c4 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663420] RSP: 0018:b8018014b7b8 EFLAGS: 00010086 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663422] RAX: RBX: 0011 RCX: Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663424] RDX: RSI: 0011 RDI: 9ea909877000 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663425] RBP: b8018014b7d0 R08: 9ea9138cd800 R09: 0004 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663426] R10: 9ea8c3f2cd9d R11: 9ea9c3f2cd97 R12: 0011 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663427] R13: R14: R15: 0003 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663429] FS: () GS:9ea91648() knlGS: Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663430] CS: 0010 DS: ES: CR0: 80050033 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663431] CR2: 1c18 CR3: 00013580a001 CR4: 001606e0 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663432] Call Trace: Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663439] input_handle_event+0x7f/0x610 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663441] input_inject_event+0x82/0x84 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663445] input_leds_brightness_set+0x27/0x30 [input_leds] Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663449] led_set_brightness_nopm+0x17/0x40 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663450] led_set_brightness+0x28/0x60 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663452] led_trigger_set+0x12c/0x2a0 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663455] ? synchronize_rcu+0x67/0x70 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663457] ? __call_rcu+0x1d0/0x1d0 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663459] led_classdev_unregister.part.0+0x32/0xd0 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663460] led_classdev_unregister+0x1f/0x30 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663462] input_leds_disconnect+0x39/0x70 [input_leds] Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663464] __input_unregister_device+0xb5/0x150 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663465] input_unregister_device+0x49/0x70 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663471] hidinput_disconnect+0x89/0xf0 [hid] Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663474] hid_disconnect+0x5c/0x80 [hid] Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663476] hid_device_remove+0x92/0xb0 [hid] Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663479] device_release_driver_internal+0xf0/0x1d0 Oct 18 21:43:21 james-ThinkPad-X230
[Ubuntu-x-swat] [Bug 1867655] [NEW] intel graphics drivers ubuntu 16.04 32bit
Public bug reported: cannot run windows programs on playonlinux program especially empire earth 2 which it opens the program but the mouse cursor hangs ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-88.88~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-88-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 Architecture: i386 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 16 20:13:03 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:0233] Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:0233] InstallationDate: Installed on 2016-02-11 (1495 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228) MachineType: Dell Inc. Latitude E6400 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic root=UUID=64a984b3-0627-4713-99e8-1ed3743886ff ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0RX493 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd12/17/2008:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0RX493:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6400 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu xenial -- 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/1867655 Title: intel graphics drivers ubuntu 16.04 32bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1867655/+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 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot
Just checked, issue persists in 5.6.0 RC1 Kernel, Bios 1.10.0, Ubuntu 20.04. Closing laptop lid while at login until suspend occurs and then immediately resuming from suspend appears to enable the keyboard and touchpad. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+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 1861633] Re: Rx vega m gl undervolt and overclock pp_od_clk_voltage values cannot be changed using echo
I have done some searching around and each of the OD_RANGE parameters,
as they appear in PP_OD_CLK_VOLTAGE seem to be defined in lines 4495 to
4506 of linux/drivers/gpu/drm/amd/powerplay/hwmgr/smu7_hwmgr.c as
follows:
linux/drivers/gpu/drm/amd/powerplay/hwmgr/smu7_hwmgr.c
As copied from file:
""
case OD_RANGE:
if (hwmgr->od_enabled) {
size = sprintf(buf, "%s:\n", "OD_RANGE");
size += sprintf(buf + size, "SCLK: %7uMHz %10uMHz\n",
data->golden_dpm_table.sclk_table.dpm_levels[0].value/100,
hwmgr->platform_descriptor.overdriveLimit.engineClock/100);
size += sprintf(buf + size, "MCLK: %7uMHz %10uMHz\n",
data->golden_dpm_table.mclk_table.dpm_levels[0].value/100,
hwmgr->platform_descriptor.overdriveLimit.memoryClock/100);
size += sprintf(buf + size, "VDDC: %7umV %11umV\n",
data->odn_dpm_table.min_vddc,
data->odn_dpm_table.max_vddc);
""
Hope this helps
--
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/1861633
Title:
Rx vega m gl undervolt and overclock pp_od_clk_voltage values cannot
be changed using echo
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1861633/+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 1861633] Re: Rx vega m gl undervolt and overclock pp_od_clk_voltage values cannot be changed using echo
** Description changed: GPU=Rx vega m gl Release=Focal, 20.04 (development) xserver-xorg-video-amdgpu version=19.1.0-1 (active development) /sys/class/drm/card1/device/pp_od_clk_voltage cannot be change beyond the parameters stated at the bottom of this file within the title OD_RANGE, as follows: OD_RANGE: SCLK: 225MHz 1011MHz MCLK: 300MHz700MHz VDDC: 750mV 750mV The parameters in OD_RANGE are too constrictive and do not allow - practcable overclocking/undervolting. Please could these values be + practicable overclocking/undervolting. Please could these values be changed to the following?: OD_RANGE: SCLK: 225MHz 1500MHz MCLK: 300MHz850MHz VDDC: 300mV 1500mV This bug was also found here; https://gitlab.freedesktop.org/drm/amd/issues/574 The voltages and clock speeds cannot be amended above 1011Mhz, the HBM2 cannot exceed 700MHz and all voltages can only equal 750mV. -- 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/1861633 Title: Rx vega m gl undervolt and overclock pp_od_clk_voltage values cannot be changed using echo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1861633/+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 1861633] Re: Rx vega m gl undervolt and overclock pp_od_clk_voltage values cannot be changed using echo
Following my previous post I have amended the above, to reflect that values can be changed, but only within constrictive ranges. Please amend these ranges to allow overclocking and undervolting. ** Description changed: GPU=Rx vega m gl Release=Focal, 20.04 (development) xserver-xorg-video-amdgpu version=19.1.0-1 (active development) - The expected outcome of altering the file, pp_od_clk_voltage, p-states cannot be changed using echo commands i.e. - echo "s 3 700 700" > /sys/class/drm/card1/device/pp_od_clk_voltage - Various variations of the above have been tried, including using sudo su and checking file write permissions. + /sys/class/drm/card1/device/pp_od_clk_voltage cannot be change beyond + the parameters stated at the bottom of this file within the title + OD_RANGE, as follows: - The file power_dpm_force_performance_level could be changed only within sudo su when DRI_PRIME=1 was used to open a program in the background i.e. DRI_PRIME=1 steam: - sudo su - echo "manual" > /sys/class/drm/card1/device/power_dpm_force_performance_level + OD_RANGE: + SCLK: 225MHz 1011MHz + MCLK: 300MHz700MHz + VDDC: 750mV 750mV - Following this, pp_od_clk_voltage could still not be changed. + The parameters in OD_RANGE are too constrictive and do not allow + practcable overclocking/undervolting. Please could these values be + changed to the following?: - A similar bug was found here; + OD_RANGE: + SCLK: 225MHz 1500MHz + MCLK: 300MHz850MHz + VDDC: 300mV 1500mV + + This bug was also found here; https://gitlab.freedesktop.org/drm/amd/issues/574 - However, I was not able to amend any P-states as described in the bug in this link. - The voltages and clock speeds cannot be amended. + The voltages and clock speeds cannot be amended above 1011Mhz, the HBM2 + cannot exceed 700MHz and all voltages can only equal 750mV. -- 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/1861633 Title: Rx vega m gl undervolt and overclock pp_od_clk_voltage values cannot be changed using echo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1861633/+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 1861633] Re: Rx vega m gl undervolt and overclock pp_od_clk_voltage values cannot be changed using echo
** Description changed: - GPU=Rx vega m gl + GPU=Rx vega m gl Release=Focal, 20.04 (development) xserver-xorg-video-amdgpu version=19.1.0-1 (active development) - The expected outcome of altering the file, pp_od_clk_voltage, p-states cannot be changed using echo commands i.e. + The expected outcome of altering the file, pp_od_clk_voltage, p-states cannot be changed using echo commands i.e. echo "s 3 700 700" > /sys/class/drm/card1/device/pp_od_clk_voltage Various variations of the above have been tried, including using sudo su and checking file write permissions. The file power_dpm_force_performance_level could be changed only within sudo su when DRI_PRIME=1 was used to open a program in the background i.e. DRI_PRIME=1 steam: sudo su echo "manual" > /sys/class/drm/card1/device/power_dpm_force_performance_level Following this, pp_od_clk_voltage could still not be changed. - A similar bug was found here; + A similar bug was found here; https://gitlab.freedesktop.org/drm/amd/issues/574 - However, I was not able to amend any P-states as described in the bug described in this link. + However, I was not able to amend any P-states as described in the bug in this link. The voltages and clock speeds cannot be amended. -- 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/1861633 Title: Rx vega m gl undervolt and overclock pp_od_clk_voltage values cannot be changed using echo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1861633/+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 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot
I am running BIOS 1.10.0, Kernel 5.5, Ubuntu 20.04 (development) and am getting the same issue. The duration appears to vary for the keyboard and track pad to activate, sometimes it is longer or shorter than 13seconds stated above. I am also running 9575. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+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 1861633] [NEW] Rx vega m gl undervolt and overclock pp_od_clk_voltage values cannot be changed using echo
Public bug reported: GPU=Rx vega m gl Release=Focal, 20.04 (development) xserver-xorg-video-amdgpu version=19.1.0-1 (active development) The expected outcome of altering the file, pp_od_clk_voltage, p-states cannot be changed using echo commands i.e. echo "s 3 700 700" > /sys/class/drm/card1/device/pp_od_clk_voltage Various variations of the above have been tried, including using sudo su and checking file write permissions. The file power_dpm_force_performance_level could be changed only within sudo su when DRI_PRIME=1 was used to open a program in the background i.e. DRI_PRIME=1 steam: sudo su echo "manual" > /sys/class/drm/card1/device/power_dpm_force_performance_level Following this, pp_od_clk_voltage could still not be changed. A similar bug was found here; https://gitlab.freedesktop.org/drm/amd/issues/574 However, I was not able to amend any P-states as described in the bug described in this link. The voltages and clock speeds cannot be amended. ** Affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: 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/1861633 Title: Rx vega m gl undervolt and overclock pp_od_clk_voltage values cannot be changed using echo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1861633/+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 1858294] Re: Ubuntu 19.10 Razer Core X Saphire RX 580 - hot-plug freeze; kernel oops on boot
Appears to work with updated Ubuntu 18.04. I'll keep the 19.10 partition around for a little while in case I can provide further information. -- 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/1858294 Title: Ubuntu 19.10 Razer Core X Saphire RX 580 - hot-plug freeze; kernel oops on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1858294/+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 1858294] Re: Ubuntu 19.10 Razer Core X Saphire RX 580 - hot-plug freeze; kernel oops on boot
dmesg.0.before-hot-plug.txt dmesg.1.not-yet-frozen-after-hot-plug.txt dmesg.2.frozen-after-hot-plug.txt dmesg.3.kernel-oops-reboot-while-attached.jpg lspci-vvnn.log regdump_broke.txt regdump_good.txt uname-a.log version.log Xorg.0.log ** Attachment added: "logs.tgz" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1858294/+attachment/5317593/+files/logs.tgz -- 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/1858294 Title: Ubuntu 19.10 Razer Core X Saphire RX 580 - hot-plug freeze; kernel oops on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1858294/+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 1858294] [NEW] Ubuntu 19.10 Razer Core X Saphire RX 580 - hot-plug freeze; kernel oops on boot
Public bug reported: Hardware (verified working with Windows 10) - Lenovo X1 Carbon Gen 7 - Razer Core X with Saphire RX 580 - lspci-vvnn.log Software - New install of Ubuntu 19.10 - uname-a.log - version.log - mesa and amdgpu software from eoan repo Symptoms when hot connected - Doesn't work - Eventially freezes (mouse and clock frozen) - dmesg.0.before-hot-plug.txt - dmesg.1.not-yet-frozen-after-hot-plug.txt - dmesg.2.frozen-after-hot-plug.txt - Xorg.0.log - regdump_good.txt - regdump_broke.txt - on `sudo reboot`, GPu attached displays show shutdown banner (this is the only time they display anything) Symptoms when connected at startup - Crash - dmesg.3.kernel-oops-reboot-while-attached.jpg - Reported bug through GUI after reboot, I think this identifies it: ``` rhew@x1:/var/crash$ sudo cat _usr_bin_gnome-shell.124.uploaded 6be3909c-2f27-11ea-a76d-fa163ee63de6 ** Affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: New ** Tags: amdgpu gpu kernel-oops mesa xorg ** Attachment added: "logs.gz" https://bugs.launchpad.net/bugs/1858294/+attachment/5317592/+files/logs.gz ** Attachment removed: "logs.gz" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1858294/+attachment/5317592/+files/logs.gz -- 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/1858294 Title: Ubuntu 19.10 Razer Core X Saphire RX 580 - hot-plug freeze; kernel oops on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1858294/+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 1856091] Re: Xorg freeze
I extracted the following from /var/log/syslog: Dec 11 20:53:17 solidus kernel: [ 6767.461655] INFO: task Xorg:3261 blocked for more than 120 seconds. Dec 11 20:53:17 solidus kernel: [ 6767.462842] Tainted: G OE 5.3.0-24-generic #26-Ubuntu Dec 11 20:53:17 solidus kernel: [ 6767.463851] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Dec 11 20:53:17 solidus kernel: [ 6767.464887] XorgD0 3261 3259 0x0004 Dec 11 20:53:17 solidus kernel: [ 6767.465947] Call Trace: Dec 11 20:53:17 solidus kernel: [ 6767.466998] __schedule+0x2b9/0x6c0 Dec 11 20:53:17 solidus kernel: [ 6767.468054] schedule+0x42/0xb0 Dec 11 20:53:17 solidus kernel: [ 6767.469116] schedule_timeout+0x203/0x2f0 Dec 11 20:53:17 solidus kernel: [ 6767.470187] ? __wake_up_common_lock+0x8a/0xc0 Dec 11 20:53:17 solidus kernel: [ 6767.471259] dma_fence_default_wait+0x1a5/0x290 Dec 11 20:53:17 solidus kernel: [ 6767.472335] ? dma_fence_free+0x20/0x20 Dec 11 20:53:17 solidus kernel: [ 6767.473421] dma_fence_wait_timeout+0xe7/0xf0 Dec 11 20:53:17 solidus kernel: [ 6767.474572] gmc_v10_0_flush_gpu_tlb+0x163/0x1a0 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.475709] amdgpu_gart_bind+0x67/0x90 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.476838] amdgpu_ttm_gart_bind+0x78/0xc0 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.478014] amdgpu_ttm_alloc_gart+0x21c/0x2e0 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.479189] ? ttm_bo_unreserve+0x60/0x60 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.480356] amdgpu_vm_sdma_map_table+0x2f/0x40 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.481562] amdgpu_vm_clear_bo+0x170/0x3c0 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.482703] ? _cond_resched+0x19/0x30 Dec 11 20:53:17 solidus kernel: [ 6767.483838] ? mutex_lock+0x13/0x40 Dec 11 20:53:17 solidus kernel: [ 6767.485044] amdgpu_vm_update_ptes+0x292/0x750 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.486233] ? _cond_resched+0x19/0x30 Dec 11 20:53:17 solidus kernel: [ 6767.487403] ? __kmalloc+0x180/0x270 Dec 11 20:53:17 solidus kernel: [ 6767.488641] amdgpu_vm_bo_update_mapping+0xb3/0xe0 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.489887] amdgpu_vm_bo_update+0x317/0x720 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.491125] amdgpu_gem_va_ioctl+0x502/0x530 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.492345] ? idr_remove+0x11/0x20 Dec 11 20:53:17 solidus kernel: [ 6767.493607] ? amdgpu_gem_metadata_ioctl+0x1b0/0x1b0 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.494849] drm_ioctl_kernel+0xae/0xf0 [drm] Dec 11 20:53:17 solidus kernel: [ 6767.496088] ? native_flush_tlb_others+0xc7/0x130 Dec 11 20:53:17 solidus kernel: [ 6767.497322] drm_ioctl+0x234/0x3d0 [drm] Dec 11 20:53:17 solidus kernel: [ 6767.498599] ? amdgpu_gem_metadata_ioctl+0x1b0/0x1b0 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.499909] amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.501163] do_vfs_ioctl+0x407/0x670 Dec 11 20:53:17 solidus kernel: [ 6767.502416] ksys_ioctl+0x67/0x90 Dec 11 20:53:17 solidus kernel: [ 6767.503691] __x64_sys_ioctl+0x1a/0x20 Dec 11 20:53:17 solidus kernel: [ 6767.504958] do_syscall_64+0x5a/0x130 Dec 11 20:53:17 solidus kernel: [ 6767.506226] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Dec 11 20:53:17 solidus kernel: [ 6767.507528] RIP: 0033:0x7efbfec8867b Dec 11 20:53:17 solidus kernel: [ 6767.508826] Code: Bad RIP value. Dec 11 20:53:17 solidus kernel: [ 6767.510110] RSP: 002b:7ffbaad8 EFLAGS: 0246 ORIG_RAX: 0010 Dec 11 20:53:17 solidus kernel: [ 6767.511432] RAX: ffda RBX: 7ffbab20 RCX: 7efbfec8867b Dec 11 20:53:17 solidus kernel: [ 6767.512768] RDX: 7ffbab20 RSI: c0286448 RDI: 000d Dec 11 20:53:17 solidus kernel: [ 6767.514122] RBP: c0286448 R08: 80010e80 R09: 000e Dec 11 20:53:17 solidus kernel: [ 6767.515475] R10: 0017 R11: 0246 R12: 565559a24f90 Dec 11 20:53:17 solidus kernel: [ 6767.516844] R13: 000d R14: 00dec000 R15: 56555785e800 -- 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/1856091 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1856091/+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 1856091] [NEW] Xorg freeze
Public bug reported: On this occasion (and there have been many before), X froze (with cursor still movable) while using Firefox. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 11 21:05:05 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-23-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Once a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [1002:731f] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [1002:0b36] InstallationDate: Installed on 2019-11-07 (34 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=2e5c8ff6-67d0-4aa4-ae83-63a0b2838d04 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ULTRA dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/13/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS ULTRA dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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 N/A 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan freeze 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/1856091 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1856091/+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 1746232] Re: driver looping then crashing
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1746232 Title: driver looping then crashing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746232/+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 1752194] Re: Intel GPU tools crash with "Couldn't map MMIO region"
I've hit this too on 18.04. It may be related to kernel lockdown in UEFI secure boot. https://bugs.freedesktop.org/show_bug.cgi?id=93199 ** Bug watch added: freedesktop.org Bugzilla #93199 https://bugs.freedesktop.org/show_bug.cgi?id=93199 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1752194 Title: Intel GPU tools crash with "Couldn't map MMIO region" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1752194/+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
Re: [Ubuntu-x-swat] [Bug 1821533] Re: drm fails to accept edid version 2.4
ZenBook UX431FA > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic > root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 12/14/2018 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: UX431FA.205 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: UX431FA > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: ZenBook > dmi.product.name: ZenBook UX431FA > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.95-1~18.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 > version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 > version.xserver-xorg-core: xserver-xorg-core N/A > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A > version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1821533/+subscriptions > -- James Parris Fmr. Staff Sergeant, U.S. Army Grovetown, GA Cell: (334)294-4932 "Two things are infinite: the universe and human stupidity; and I'm not completely sure about the former." - Albert Einstein -- 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/1821533 Title: drm fails to accept edid version 2.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1821533/+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 1821533] Re: drm fails to accept edid version 2.4
Our company just purchased these laptops and we could really use a fix for them. Would you mind sharing the edid files you created to get the displays functioning? ** Bug watch added: bugs.dragonflybsd.org/issues #3167 https://bugs.dragonflybsd.org/issues/3167 -- 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/1821533 Title: drm fails to accept edid version 2.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1821533/+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 1821533] Re: drm fails to accept edid version 2.4
Does Linux plan of patching this issue since 18.04 is an LTS? Anyone know? -- 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/1821533 Title: drm fails to accept edid version 2.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1821533/+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 1834375] [NEW] Gaia.com videos unsupported
Public bug reported: Firefox could not play videos on Gaia.com. The error message blamed the browser. So I downloaded and installed the browser Opera, with the same results and message. Both browsers would play Youtube videos. Please enable Gaia.com videos. Thanks. I downloaded the latest Ubuntu release today. 18.04...something ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18 Uname: Linux 4.15.0-52-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jun 26 17:57:24 2019 DistUpgraded: 2019-06-26 11:14:51,559 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics Controller [103c:3048] Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics Controller [103c:3048] InstallationDate: Installed on 2019-06-25 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic root=UUID=dfa2862a-4da8-414d-9f41-cecde30f67c6 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-06-26 (0 days ago) dmi.bios.date: 06/23/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G2 v02.02 dmi.board.name: 3048h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G2v02.02:bd06/23/2011:svnHewlett-Packard:pn:pvr:rvnHewlett-Packard:rn3048h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 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 xserver.bootTime: Wed Jun 26 10:11:57 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1834375 Title: Gaia.com videos unsupported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1834375/+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 1806511] [NEW] FreeCAD 17 Beta text displayed as squares
Public bug reported: FreeCAD installed from Ubuntu Software Center - FreeCAD 17 Beta - worked with Ubuntu 18.04 but after upgrading to Ubuntu 18.10 the display is unusable. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:40:04 2018 DistUpgraded: 2018-10-20 08:18:12,951 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: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Crystal Well Integrated Graphics Controller [8086:0d26] (rev 08) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Crystal Well Integrated Graphics Controller [1558:7410] InstallationDate: Installed on 2014-03-28 (1711 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) MachineType: System76, Inc. Galago UltraPro ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-12-generic root=UUID=c330a467-be0d-4c14-aff3-caeb375596b7 ro rootflags=subvol=@ i915.disable_power_well=0 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-10-20 (44 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago UltraPro dmi.board.vendor: System76, Inc. dmi.board.version: galu1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc, dmi.chassis.version: galu1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1: dmi.product.family: Not Applicable dmi.product.name: Galago UltraPro dmi.product.sku: Not Applicable dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption cosmic ubuntu ** Attachment added: "screenshot of FreeCAD at startup Ubuntu 18.10" https://bugs.launchpad.net/bugs/1806511/+attachment/5218712/+files/FreeCAD%2017Beta%20screenshot%202018-12-03%2018-47-00.png -- 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/1806511 Title: FreeCAD 17 Beta text displayed as squares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1806511/+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 268506] Re: Cannot configure Synaptics TouchStyk settings (e.g. sensitivity, tapping, press/select)
@penalvch Unfortunately, 5 years later, this exact bug is still here. HP EliteBook 8470p, the TouchStyk is showing up as a "PS/2 Generic Mouse" with no way to configure tap-to-click through either xinput or a config file. ** Also affects: libinput (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/268506 Title: Cannot configure Synaptics TouchStyk settings (e.g. sensitivity, tapping, press/select) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/268506/+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 1308105]
Thanks jkampe68! Attachment 6590 completely fixes the problem for me on Ubuntu and Arch Linux. I've made an AUR package including your patch: https://aur.archlinux.org/packages/xfce4-settings-blank-screen-fix/ -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1308105 Title: Xfce resets TV mode to NULL when power cycled To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+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 1770591] [NEW] On boot, for a few seconds, the color of the selection lasso is the default (orange), regardless of background picture and/or theme.
Public bug reported: To comply with reporting guidelines: 1) lsb_release -rd output: Description:Ubuntu 18.04 LTS Release:18.04 2) Unsure of package name 3) I expected that on boot, the lasso color would immediately be the correct color, based on background image and/or theme. 4) The lasso is the default orange for a few seconds immediately following boot, regardless of background color and/or theme. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Fri May 11 18:05:18 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:1a8d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 950M] [1043:1a8d] InstallationDate: Installed on 2018-04-28 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. GL552JX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=e126ae85-5a7a-456f-bb81-817468fde00d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL552JX.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL552JX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL552JX.209:bd12/22/2015:svnASUSTeKCOMPUTERINC.:pnGL552JX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552JX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL552JX dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- 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/1770591 Title: On boot, for a few seconds, the color of the selection lasso is the default (orange), regardless of background picture and/or theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770591/+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 1752053] Re: nvidia-390 fails to boot graphical display
Reiterating the above experiences regarding the Dell XPS 9560. Black screen with nvidia drivers. Cannot workaround this issue unless I remove the drivers. -- 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/1752053 Title: nvidia-390 fails to boot graphical display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1750393] [NEW] Blank screen with only mouse pointer after mesa driver update; display does not switch to tty7 upon lightdm start; Xorg.0.log quickly grows
Public bug reported: I get a blank screen with only mouse pointer upon boot, after the splash. This started after the mesa driver update on 2/15/18. The display does not appear to switch to tty7 upon lightdm start. Xorg.0.log quickly grows and continues to grow. I believe `lightdm` is not starting `Xorg` on the correct display, but, I don't know how to determine this from the logs. Here is the command line `lightdm` uses to launch `Xorg`: ~$ ps -ef | grep lightdm root 1261 1 0 18:23 ?00:00:00 /usr/sbin/lightdm root 1316 1261 6 18:23 tty7 00:00:03 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch root 1350 1261 0 18:23 ?00:00:00 lightdm --session-child 12 15 *OCCURRENCE ON 2/15/18:* I performed a normal upgrade on 2/15/18 through the software manager in 16.04LTS. It upgraded the following libraries (`/var/log/dpkg.log [pkg][old ver][new ver]`): libegl1-mesa-dev:amd64 17.2.4-0ubuntu1~16.04.4 17.2.8-0ubuntu0~16.04.1 libwayland-egl1-mesa:amd64 17.2.4-0ubuntu1~16.04.4 17.2.8-ubuntu0~16.04.1 libwayland-egl1-mesa:i386 17.2.4-0ubuntu1~16.04.4 17.2.8-0ubuntu0~16.04.1 libegl1-mesa:i386 17.2.4-0ubuntu1~16.04.4 17.2.8-0ubuntu0~16.04.1 libegl1-mesa:amd64 17.2.4-0ubuntu1~16.04.4 17.2.8-0ubuntu0~16.04.1 libgbm1:amd64 17.2.4-0ubuntu1~16.04.4 17.2.8-0ubuntu0~16.04.1 libgbm1:i386 17.2.4-0ubuntu1~16.04.4 17.2.8-0ubuntu0~16.04.1 libosmesa6:amd64 17.2.4-0ubuntu1~16.04.4 17.2.8-0ubuntu0~16.04.1 libosmesa6:i386 17.2.4-0ubuntu1~16.04.4 17.2.8-0ubuntu0~16.04.1 libgles2-mesa:amd64 17.2.4-0ubuntu1~16.04.4 17.2.8-0ubuntu0~16.04.1 libgl1-mesa-glx:amd64 17.2.4-0ubuntu1~16.04.4 17.2.8-0ubuntu0~16.04.1 libgl1-mesa-glx:i386 17.2.4-0ubuntu1~16.04.4 17.2.8-0ubuntu0~16.04.1 libglapi-mesa:i386 17.2.4-0ubuntu1~16.04.4 17.2.8-0ubuntu0~16.04.1 libglapi-mesa:amd64 17.2.4-0ubuntu1~16.04.4 17.2.8-0ubuntu0~16.04.1 libgl1-mesa-dri:amd64 17.2.4-0ubuntu1~16.04.4 17.2.8-0ubuntu0~16.04.1 libgl1-mesa-dri:i386 17.2.4-0ubuntu1~16.04.4 17.2.8-0ubuntu0~16.04.1 libxatracker2:amd64 17.2.4-0ubuntu1~16.04.4 17.2.8-0ubuntu0~16.04.1 linux-firmware:all 1.157.15 1.157.16 mesa-vdpau-drivers:i386 17.2.4-0ubuntu1~16.04.4 17.2.8-0ubuntu0~16.04.1 mesa-vdpau-drivers:amd64 17.2.4-0ubuntu1~16.04.4 17.2.8-0ubuntu0~16.04.1 xserver-xorg-video-radeon-hwe-16.04:amd64 1:7.9.0-0ubuntu1~16.04.1 1:7.10.0-1~16.04.1 xserver-xorg-video-ati-hwe-16.04:amd64 1:7.9.0-0ubuntu1~16.04.1 1:7.10.0-1~16.04.1 I should note, this is *not* the compiz/unity update package list. It is the mesa drivers. Upon reboot, I started getting a blank screen with only a mouse pointer when the display manager started. I press CTRL+ALT+F1 to go into console, and I can find the following in the `Xorg.0.log`: [ 4800.851] (WW) RADEON(0): flip queue failed: Invalid argument [ 4800.851] (WW) RADEON(0): Page flip failed: Invalid argument These warning messages are *constantly* streaming into the log file, and it *keeps growing*. This wasn't present before the library update. I will be happy to provide a logfile upon request. Video h/w on my laptop: *-display description: VGA compatible controller product: RV516/M64-S [Mobility Radeon X2300] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 32 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:16 memory:d000-d3ff ioport:4000(size=256) memory:d830-d830 memory:c-d 1st lines of modinfo output: filename: /lib/modules/4.13.0-26-generic/kernel/drivers/gpu/drm/radeon/radeon.ko license:GPL and additional rights description:ATI Radeon *UPDATE 2/16/18:* I appear to be booting to the wrong VT display. All of the symptoms above are true; however, if I perform a CTRL+ALT+F1 (up to F6) at startup and then immediately perform a CTRL+ALT+F7, which switches the VT, I go to my normal desktop as if it had booted correctly. CTRL+ALT+F7 without first going to console does not do anything. So, this simplifies things somewhat as it now looks to be a config issue. Lightdm seems to start Xorg on the wrong display. I tried a vt.handoff=7 on the linux kernel command line, and this did not help. Here is the output of `w` immediately after pressing CTRL+ALT+F7 and going to the normal desktop: 09:38:01 up 44 min, 1 user, load average: 0.60, 0.67, 0.82 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT user1tty7 :0 08:53 44:14 6:16 0.29s /sbin/upstart - This display listing appears normal. I should note that compiz and unity still seem to function. The desktop is fully available and already loaded
[Ubuntu-x-swat] [Bug 1746232] Re: driver looping then crashing
I have raised this bug at https://bugzilla.kernel.org/show_bug.cgi?id=198669 ** Bug watch added: Linux Kernel Bug Tracker #198669 https://bugzilla.kernel.org/show_bug.cgi?id=198669 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1746232 Title: driver looping then crashing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746232/+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 1746232] Re: driver looping then crashing
The file name above should read radeon_ring.c. I thought you used to be able to edit comments on here! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1746232 Title: driver looping then crashing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746232/+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 1746232] Re: driver looping then crashing
This crash looks very similar to #1301649. However is does not require the system to go into power save. The crash is in radeon_ring_backup which is in linux/drivers/gpu/drm/radeon/radeon_device.c and part of the linux (kernel) package. I have added that package to this bug. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1746232 Title: driver looping then crashing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746232/+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 1746232] Re: driver looping then crashing
** 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 xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1746232 Title: driver looping then crashing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746232/+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 1746232] [NEW] driver looping then crashing
Public bug reported: Running driver on Artful with the xwayland compositor. At random times the GPU stalls with. Jan 30 11:22:28 dragon kernel: [ 487.046219] radeon :02:00.0: ring 0 stalled for more than 29200msec Jan 30 11:22:28 dragon kernel: [ 487.046224] radeon :02:00.0: GPU lockup (current fence id 0x1bdb last fence id 0x1bdc on ring 0) Usually when the system is idle. The above message is repeated once a second for a while. This usually but not always terminates with a page load fault in the driver. System can run for a few days without this happening. But on average it is once or twice a day. Jan 30 11:22:30 dragon kernel: [ 488.507091] BUG: unable to handle kernel paging request at b406c1891ffc Jan 30 11:22:30 dragon kernel: [ 488.507176] IP: radeon_ring_backup+0xd3/0x140 [radeon] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xserver-xorg-video-radeon 1:7.10.0-1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Jan 30 11:40:08 2018 DistUpgraded: 2017-11-06 18:26:08,552 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.10.0, 4.13.0-21-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-25-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-31-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850] [1002:9442] (rev ff) (prog-if ff) InstallationDate: Installed on 2016-07-01 (577 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic root=/dev/mapper/wd-root ro SourcePackage: xserver-xorg-video-ati UpgradeStatus: Upgraded to artful on 2017-11-06 (84 days ago) dmi.bios.date: 05/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0403 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T SE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0403:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TSE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Dec 9 13:32:35 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu ** Description changed: Running driver on Artful with the xwayland compositor. At random times the GPU stalls with. Jan 30 11:22:28 dragon kernel: [ 487.046219] radeon :02:00.0: ring 0 stalled for more than 29200msec Jan 30 11:22:28 dragon kernel: [ 487.046224] radeon :02:00.0: GPU lockup (current fence id 0x1bdb last fence id 0x1bdc on ring 0) Usually when the system is idle. - The above message is repeated once a second for a while. The usually but - not always terminates with a page load fault in the driver. + The above message is repeated once a second for a while. This usually + but not always terminates with a page load fault in the driver. + + System can run for a few days without this happening. But on average it + is once or twice a day. + + Jan 30 11:22:30 dragon kernel: [ 488.507091] BUG: unable to handle kernel paging request at b406c1891ffc Jan 30 11:22:30 dragon kernel: [ 488.507176] IP: radeon_ring_backup+0xd3/0x140 [radeon] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xserver-xorg-video-radeon 1:7.10.0-1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname:
Re: [Ubuntu-x-swat] [Bug 1741914] Re: artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfut
Right after reporting this and 3 other bugs all at the same time, I rebooted and it got cought in a loop right before the login and I had to reinstall. Thank you for working on these issues, your way ahead of me. James On Tue, Jan 9, 2018 at 7:27 AM, Videonauth <1741...@bugs.launchpad.net> wrote: > Yes, sadly now the NVidia Driver 384.90 (I still wonder where you get > the 384.111 on artful) fails still to build even after the released fix. > But this time with a different message and build log. And without > showing me an opportunity to report the bug (except using ubuntu-bug > command which will maybe not fetch all information). > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1742039). > https://bugs.launchpad.net/bugs/1741914 > > Title: > artful-proposed 4.13.0-24: kernel module failed to build [Cannot > generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install > libelf-dev, libelf-devel or elfutils-libelf-devel] > > Status in bbswitch package in Ubuntu: > Confirmed > Status in bcmwl package in Ubuntu: > Confirmed > Status in linux package in Ubuntu: > Fix Committed > Status in ndiswrapper package in Ubuntu: > Confirmed > Status in nvidia-graphics-drivers-304 package in Ubuntu: > Confirmed > Status in nvidia-graphics-drivers-340 package in Ubuntu: > Confirmed > Status in nvidia-graphics-drivers-384 package in Ubuntu: > Confirmed > Status in virtualbox package in Ubuntu: > Confirmed > > Bug description: > After update to new kernel (4.13.0-24) the system prompted me with > this. > > ProblemType: Package > DistroRelease: Ubuntu 17.10 > Package: nvidia-384 384.90-0ubuntu3.17.10.2 > ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13 > Uname: Linux 4.13.0-22-generic x86_64 > NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia > ApportVersion: 2.20.7-0ubuntu3.7 > Architecture: amd64 > DKMSKernelVersion: 4.13.0-24-generic > Date: Mon Jan 8 16:30:09 2018 > PackageVersion: 384.90-0ubuntu3.17.10.2 > Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, > 3.6.3-0ubuntu2 > PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, > 2.7.14-2ubuntu1 > RelatedPackageVersions: >dpkg 1.18.24ubuntu1 >apt 1.5.1 > SourcePackage: nvidia-graphics-drivers-384 > Title: nvidia-384 384.90-0ubuntu3.17.10.2: nvidia-384 kernel module > failed to build > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/ > 1741914/+subscriptions > -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1741914 Title: artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1741914/+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
Re: [Ubuntu-x-swat] [Bug 1741914] Re: artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfut
Right after reporting this and 3 other bugs all at the same time, I rebooted and it got cought in a loop right before the login and I had to reinstall. Thank you for working on these issues, your way ahead of me. James On Tue, Jan 9, 2018 at 5:17 AM, Jacques Koch <1741...@bugs.launchpad.net> wrote: > Thanks will definitely go and take a look. Only been on Linux about a month > or so and really loving it ,but still finding my feet > > On 9 Jan 2018 12:50, "Daniel van Vugt" <daniel.van.v...@canonical.com> > wrote: > > > It looks like this bug is now fixed as of 1 hour ago, in linux > > 4.13.0-25.29. You had to be unlucky to have an artful system on proposed > > do an update during the previous day and get the faulty package linux > > 4.13.0-24. That one doesn't exist any more so this bug should quieten > > down now. > > > > See bug 1741955 for updates. > > > > ** Changed in: linux (Ubuntu) > >Status: Confirmed => Fix Committed > > > > -- > > You received this bug notification because you are subscribed to a > > duplicate bug report (1742014). > > https://bugs.launchpad.net/bugs/1741914 > > > > Title: > > artful-proposed 4.13.0-24: kernel module failed to build [Cannot > > generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install > > libelf-dev, libelf-devel or elfutils-libelf-devel] > > > > Status in bbswitch package in Ubuntu: > > Confirmed > > Status in bcmwl package in Ubuntu: > > Confirmed > > Status in linux package in Ubuntu: > > Fix Committed > > Status in ndiswrapper package in Ubuntu: > > Confirmed > > Status in nvidia-graphics-drivers-304 package in Ubuntu: > > Confirmed > > Status in nvidia-graphics-drivers-340 package in Ubuntu: > > Confirmed > > Status in nvidia-graphics-drivers-384 package in Ubuntu: > > Confirmed > > Status in virtualbox package in Ubuntu: > > Confirmed > > > > Bug description: > > After update to new kernel (4.13.0-24) the system prompted me with > > this. > > > > ProblemType: Package > > DistroRelease: Ubuntu 17.10 > > Package: nvidia-384 384.90-0ubuntu3.17.10.2 > > ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13 > > Uname: Linux 4.13.0-22-generic x86_64 > > NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia > > ApportVersion: 2.20.7-0ubuntu3.7 > > Architecture: amd64 > > DKMSKernelVersion: 4.13.0-24-generic > > Date: Mon Jan 8 16:30:09 2018 > > PackageVersion: 384.90-0ubuntu3.17.10.2 > > Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, > > 3.6.3-0ubuntu2 > > PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, > > 2.7.14-2ubuntu1 > > RelatedPackageVersions: > >dpkg 1.18.24ubuntu1 > >apt 1.5.1 > > SourcePackage: nvidia-graphics-drivers-384 > > Title: nvidia-384 384.90-0ubuntu3.17.10.2: nvidia-384 kernel module > > failed to build > > UpgradeStatus: No upgrade log present (probably fresh install) > > > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/ > > 1741914/+subscriptions > > > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1742039). > https://bugs.launchpad.net/bugs/1741914 > > Title: > artful-proposed 4.13.0-24: kernel module failed to build [Cannot > generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install > libelf-dev, libelf-devel or elfutils-libelf-devel] > > Status in bbswitch package in Ubuntu: > Confirmed > Status in bcmwl package in Ubuntu: > Confirmed > Status in linux package in Ubuntu: > Fix Committed > Status in ndiswrapper package in Ubuntu: > Confirmed > Status in nvidia-graphics-drivers-304 package in Ubuntu: > Confirmed > Status in nvidia-graphics-drivers-340 package in Ubuntu: > Confirmed > Status in nvidia-graphics-drivers-384 package in Ubuntu: > Confirmed > Status in virtualbox package in Ubuntu: > Confirmed > > Bug description: > After update to new kernel (4.13.0-24) the system prompted me with > this. > > ProblemType: Package > DistroRelease: Ubuntu 17.10 > Package: nvidia-384 384.90-0ubuntu3.17.10.2 > ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13 > Uname: Linux 4.13.0-22-generic x86_64 > NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia > ApportVersion: 2.20.7-0ubuntu3.7 > Architecture: amd64 > DKMSKernelVersion: 4.13.0-24-generic >
[Ubuntu-x-swat] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
** Also affects: lightdm-gtk-greeter-settings Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/backintime/+bug/1713313/+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 1734500] Re: Ubuntu Web Browser content upside down on rotated screen
Anyone with a dual monitor setup (regardless of whether either monitor is physically rotated) should be able to test if they observe this problem after setting one monitor rotate-setting to Clockwise. I don't know whether it can be observed on a single-monitor system. -- 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/1734500 Title: Ubuntu Web Browser content upside down on rotated screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1734500/+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 1734500] [NEW] Ubuntu Web Browser content upside down on rotated screen
Public bug reported: I use two monitors, a Plain Tree 22" on the left and a Goldstar 29" on the right. The Plain Tree is physically rotated 90 degrees counterclockwise and the Goldstar is not rotated. In Settings - Displays, the Goldstar 29" has Rotation set to Normal, and content displays ok in normal right side up fashion. In Settings - Displays, the Plain Tree has Rotation set to Clockwise because that causes most content to display ok and right side up. For example, Firefox Web Browser windows display their content right side up on both monitors. However, while window title bar text is upright for Ubuntu Web Browser windows on the Plain Tree, the window content is upside down. When I drag that window to the Goldstar the content flips over and displays correctly. I don't know the version number of webbrowser-app, or if it's relevant. Clicking on the Amazon icon on the launcher brought up an Amazon page in a frame labeled Ubuntu Web Browser which according to https://help.ubuntu.com/community/WebBrowsers is webbrowser-app . Anyhow, webbrowser-app directory info is: -rwxr-xr-x 1 root root 710984 Dec 20 2016 /usr/bin/webbrowser-app Summary: On this system, Ubuntu Web Browser page rotation is 180 degrees different from page rotation in other programs. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Nov 25 19:53:51 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2001] InstallationDate: Installed on 2017-11-26 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic root=UUID=cbde7fc0-9735-4631-bed5-1f884bfee3b2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/15/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0076.2010.1115.1959 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67GD dmi.board.vendor: Intel Corporation dmi.board.version: AAG10206-205 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0076.2010.1115.1959:bd11/15/2010:svn:pn:pvr:rvnIntelCorporation:rnDH67GD:rvrAAG10206-205:cvn:ct3:cvr: version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Nov 25 19:16:54 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1734500 Title: Ubuntu Web Browser content upside down on rotated screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1734500/+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 1694225] Re: [Thinkpad T450s] Click lock effect on trackpoint left button when touchpad is disabled
In my case I want to disable the touchpad completely :) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1694225 Title: [Thinkpad T450s] Click lock effect on trackpoint left button when touchpad is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1694225/+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 1694225] Re: [Thinkpad T450s] Click lock effect on trackpoint left button when touchpad is disabled
I'm not sure why but a workaround is to run: sudo rmmod psmouse && sudo modprobe psmouse proto=imps Then the touchpad gets recognized as: I: Bus=0011 Vendor=0002 Product=0001 Version= N: Name="PS/2 Synaptics TouchPad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input19 U: Uniq= H: Handlers=mouse0 event4 B: PROP=1 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 This prevents the lock effect from happening. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1694225 Title: [Thinkpad T450s] Click lock effect on trackpoint left button when touchpad is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1694225/+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 1682978] Re: Random Screen Rotation
Today I grabbed the daily build of 17.10 and booted into it from a USB drive. It still rotates--but at times I can't predict, the screen will blank out and then come back rotated. (Should I create a new bug for 17.10?) I should mention that this happens on my laptop, an HP Pavilion with AMD graphics. On my desktop, which has an Nvidia 960, it doesn't. -- 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/1682978 Title: Random Screen Rotation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682978/+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 1715479] Re: Touchpad won't stay disabled after resuming from suspend
** Bug watch added: Red Hat Bugzilla #1448962 https://bugzilla.redhat.com/show_bug.cgi?id=1448962 ** Also affects: libinput (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1448962 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1715479 Title: Touchpad won't stay disabled after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715479/+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 1694225] Re: [Thinkpad T450s] Click lock effect on trackpoint left button when touchpad is disabled
Here is what I'm seeing in dmesg: [2.827809] psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4758] [2.859072] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1096..] [2.920584] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2b 1, caps: 0xf008a3/0x943300/0x12e800/0x41, board id: 3053, fw id: 2491654 [2.920586] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0 [2.959657] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input5 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1694225 Title: [Thinkpad T450s] Click lock effect on trackpoint left button when touchpad is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1694225/+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 1406810] Re: [iMac11,1] Unable to boot
Bug also affects me. I've isolated it to a specific kernel patch and updated the upstream bug. -- 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/1406810 Title: [iMac11,1] Unable to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1406810/+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 1682978] Re: Random Screen Rotation
For me, it's counterclockwise. I tried setting the "lock rotation" option referenced in https://askubuntu.com/questions/874487/ubuntu- gnome-16-10-screen-orientation-spontaneously-changes (had to switch to Unity 8 to find it), but it didn't make a difference when I logged back in under Cinnamon, the windowing environment I usually use. -- 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/1682978 Title: Random Screen Rotation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682978/+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 1677050] [NEW] Youtube video will not run
Public bug reported: When I first set up ubuntu I was able to look at youtube videos, but then they just stopped running. I have no real idea why. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-82.90-generic 3.19.8-ckt22 Uname: Linux 3.19.0-82-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Mar 28 16:44:30 2017 DistUpgraded: 2017-02-13 13:49:16,446 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2a5e] InstallationDate: Installed on 2015-12-03 (481 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: HP-Pavilion GC670AA-ABA a6120n ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-82-generic root=UUID=38cc240f-f1a8-40ed-98a0-6c59680dea14 ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to vivid on 2017-02-13 (43 days ago) dmi.bios.date: 06/07/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.20 dmi.board.name: Leonite2 dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 6.00 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.20:bd06/07/2007:svnHP-Pavilion:pnGC670AA-ABAa6120n:pvr:rvnASUSTekComputerINC.:rnLeonite2:rvr6.00:cvnHewlett-Packard:ct3:cvr: dmi.product.name: GC670AA-ABA a6120n dmi.sys.vendor: HP-Pavilion version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue Mar 28 15:50:33 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputGenPS/2 Genius Mouse MOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 27137 vendor VSC xserver.version: 2:1.17.1-0ubuntu3.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu vivid -- 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/1677050 Title: Youtube video will not run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1677050/+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 1675433] [NEW] I don't know
Public bug reported: I don't know ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17 Uname: Linux 4.8.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Mar 23 10:32:52 2017 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wrestler [Radeon HD 6310] [103c:188b] InstallationDate: Installed on 2017-03-09 (13 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Hewlett-Packard HP 2000 Notebook PC ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-42-generic root=UUID=4ffafae4-18bd-4555-a4e0-a5cd0af7cbf0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 188B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 69.17 dmi.chassis.asset.tag: 5CG33427QN dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd05/22/2013:svnHewlett-Packard:pnHP2000NotebookPC:pvr088613000330591620100:rvnHewlett-Packard:rn188B:rvrKBCVersion69.17:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 2000 Notebook PC dmi.product.version: 088613000330591620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Thu Mar 23 10:22:06 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu yakkety -- 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/1675433 Title: I don't know To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1675433/+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 1653666] [NEW] know not what to put here
Public bug reported: post initramfs ??? error satus 1, or something like that new to ubuntu and don't know much about commandline and how to find and repair problems; please help thank you much James Street ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-51.72-lowlatency 4.4.30 Uname: Linux 4.4.0-51-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Jan 3 06:02:15 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:1526] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:1526] InstallationDate: Installed on 2016-11-20 (44 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125) MachineType: Hewlett-Packard HP 620 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-51-lowlatency root=/dev/mapper/ubuntu--studio--vg-root ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PVI Ver. F.20 dmi.board.name: 1526 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.0E dmi.chassis.asset.tag: 5CG104013Q dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PVIVer.F.20:bd12/12/2011:svnHewlett-Packard:pnHP620:pvrF.20:rvnHewlett-Packard:rn1526:rvrKBCVersion71.0E:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP 620 dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Jan 3 05:38:23 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial -- 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/1653666 Title: know not what to put here To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1653666/+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 1651924] Re: [HP Pavilion Notebook - 15-ab114no] Intermittent black screen
The tricky thing is that it is not a system crash, the computer keeps running fine. Just the screen goes blank and it is pretty much impossible to do anything after that. I hope that there is some kind of error message produced when it happens, now if i could only find it. -- 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/1651924 Title: [HP Pavilion Notebook - 15-ab114no] Intermittent black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1651924/+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 1651924] Re: [HP Pavilion Notebook - 15-ab114no] Intermittent black screen
No luck with the daily live-cd, some of the kernel messages fly by and when it tries to change graphics modes for the first time, black screen. With 16.04 it would sometimes get to the desktop and then would go to black screen. I also found this bug report describing the same exact problem: https://bugs.freedesktop.org/show_bug.cgi?id=95306 ** Bug watch added: freedesktop.org Bugzilla #95306 https://bugs.freedesktop.org/show_bug.cgi?id=95306 -- 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/1651924 Title: [HP Pavilion Notebook - 15-ab114no] Intermittent black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1651924/+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 1577074] Re: [HP Pavilion 15] Intermittent black screens
Done, please note that in the bug report i am using the crimson (fglrx) driver and kubuntu 15.10, because this is the only way that i can use my computer. If i try to upgrade to 16.04 and AMDGPU, my computer is unusable because of the bug. But maybe my hardware information helps. -- 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/1577074 Title: [HP Pavilion 15] Intermittent black screens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1577074/+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
