[Desktop-packages] [Bug 1811900] Re: SRU 3.28 latest git to bionic
fossfreedom, Since this is a blocking issue please also report it to the GNOME developers at: https://gitlab.gnome.org/GNOME/mutter/issues It would obviously be best if we could get a proper fix without any reverts. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1811900 Title: SRU 3.28 latest git to bionic Status in gnome-shell package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Status in gnome-shell source package in Bionic: Fix Committed Status in mutter source package in Bionic: Fix Committed Bug description: [ Description ] 3.28 gnome git branch has various upstream approved fixes for many months now, but no release has been done yet, thus we're releasing a git snapshot of the latest approved fixes. [ QA ] Run Ubuntu session, expect the shell to work normally with various setups https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Many patches we were including already have been included in upstream git now, various optimizations to clutter actors could cause drawing issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1811900/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected
I am using a Logitech M337 on Ubuntu 18.04 via Intel 8265 right now and cannot reproduce any bug. If the problem ever was specific to Intel 8265 then it might have been fixed in firmware updates already here: https://launchpad.net/ubuntu/+source/linux-firmware While comment #50 is interesting, I don't think it is relevant to this bug at all. And this bug doesn't seem to exist any more anyway. ** No longer affects: gnome-bluetooth (Ubuntu) ** Changed in: oem-priority Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Confirmed Status in OEM Priority Project: Incomplete Status in bluez package in Ubuntu: Invalid Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1362848] Re: black/blank screen and freeze at startup after installing nvidia driver (with hybrid graphic card)
** Changed in: nvidia-graphics-drivers-364 (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1362848 Title: black/blank screen and freeze at startup after installing nvidia driver (with hybrid graphic card) Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-346 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-352 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-355 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-361 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-364 package in Ubuntu: Won't Fix Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 14.04 64bit, after install nvidia binary driver 331.89 from Additional Drivers application then reboot, it shows black screen, no login window, I even can't use ctrl+alt+F2 to switch to text mode, then I reboot and go to recovery mode, use 'prime-select intel' to switch to intel GPU and reboot, everything is fine, but as soon as I switch to nvidia GPU, still same issue. OS: Ubuntu 14.04 64bit Laptop: HP ENVY 15t Nvidia GeForce GT 740M + Intel HD 4600 Desktop: Unity Kernel: 3.13.0 CPU: Intel® Core™ i7-4700MQ -- Temporary workaround (intel session): Reboot to recovery mode, mount the filesystem and run `prime-select intel`. Than reboot. Temporary workaround (nvidia session): close the lid and open it back http://askubuntu.com/questions/762329/black-screen-on-boot-screen-reappears-after-closing-and-opening-lid Possible temporary fix: see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1362848/comments/18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1362848/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1576859] Re: [nvidia] Graphics corruption when resuming from suspend
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 > IIRC I asked for all the bug reports that I made to be closed OK we will use bug 1809407 instead. Aside from anything else, JournalErrors.txt above is showing this bug is from Nvidia driver version 364.19 which doesn't seem to have ever been officially released so is not supported: https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-364 But regardless of the driver version, Nvidia is closed source so neither Canonical nor the community have any power to fix it. We can only track its bugs. ** This bug has been marked a duplicate of bug 1809407 [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1576859 Title: [nvidia] Graphics corruption when resuming from suspend Status in gnome-shell package in Ubuntu: Confirmed Bug description: Resuming from suspend results in graphical glitches. These glitches, at least on the cover screen(shows date/time) go away when the Hard Drive spins back up. Additional corruption can occur in overview on currently active applications(Such as Chromium). Description: Ubuntu 16.04 LTS Release: 16.04 gnome-shell: Installed: 3.18.4-0ubuntu3 Candidate: 3.18.4-0ubuntu3 Version table: *** 3.18.4-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 29 15:56:14 2016 DisplayManager: gdm3 InstallationDate: Installed on 2016-04-23 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1576859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809407] Re: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything.
** No longer affects: gdm3 (Ubuntu) ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Tags added: disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1809407 Title: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Every other wake from sleep presents a corrupted screen with no unlock app. There's a dock and system menu on a black background with pixel garbage. Some personal information in the dock's large window thumbnails. Bitmap garbage flashes on the screen when interacting with anything. Only workaround is doing another sleep-wake cycle. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:4b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 20 22:19:29 2018 DistUpgraded: 2018-12-01 23:07:50,385 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 DkmsStatus: nvidia, 390.87, 4.18.0-11-generic, x86_64: installed nvidia, 390.87, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162] InstallationDate: Installed on 2018-10-28 (54 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Default string 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-12-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-CF 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.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe
[Desktop-packages] [Bug 1809407] Re: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-418 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1809407 Title: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Every other wake from sleep presents a corrupted screen with no unlock app. There's a dock and system menu on a black background with pixel garbage. Some personal information in the dock's large window thumbnails. Bitmap garbage flashes on the screen when interacting with anything. Only workaround is doing another sleep-wake cycle. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:4b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 20 22:19:29 2018 DistUpgraded: 2018-12-01 23:07:50,385 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 DkmsStatus: nvidia, 390.87, 4.18.0-11-generic, x86_64: installed nvidia, 390.87, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162] InstallationDate: Installed on 2018-10-28 (54 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Default string 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-12-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-CF 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.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1809407] Re: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything.
** This bug is no longer a duplicate of bug 1576859 [nvidia] Graphics corruption when resuming from suspend -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1809407 Title: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Every other wake from sleep presents a corrupted screen with no unlock app. There's a dock and system menu on a black background with pixel garbage. Some personal information in the dock's large window thumbnails. Bitmap garbage flashes on the screen when interacting with anything. Only workaround is doing another sleep-wake cycle. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:4b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 20 22:19:29 2018 DistUpgraded: 2018-12-01 23:07:50,385 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 DkmsStatus: nvidia, 390.87, 4.18.0-11-generic, x86_64: installed nvidia, 390.87, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162] InstallationDate: Installed on 2018-10-28 (54 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Default string 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-12-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-CF 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.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1809407] Re: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1809407 Title: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Every other wake from sleep presents a corrupted screen with no unlock app. There's a dock and system menu on a black background with pixel garbage. Some personal information in the dock's large window thumbnails. Bitmap garbage flashes on the screen when interacting with anything. Only workaround is doing another sleep-wake cycle. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:4b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 20 22:19:29 2018 DistUpgraded: 2018-12-01 23:07:50,385 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 DkmsStatus: nvidia, 390.87, 4.18.0-11-generic, x86_64: installed nvidia, 390.87, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162] InstallationDate: Installed on 2018-10-28 (54 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Default string 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-12-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-CF 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.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1809407] Re: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1809407 Title: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Every other wake from sleep presents a corrupted screen with no unlock app. There's a dock and system menu on a black background with pixel garbage. Some personal information in the dock's large window thumbnails. Bitmap garbage flashes on the screen when interacting with anything. Only workaround is doing another sleep-wake cycle. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:4b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 20 22:19:29 2018 DistUpgraded: 2018-12-01 23:07:50,385 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 DkmsStatus: nvidia, 390.87, 4.18.0-11-generic, x86_64: installed nvidia, 390.87, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162] InstallationDate: Installed on 2018-10-28 (54 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Default string 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-12-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-CF 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.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help
[Desktop-packages] [Bug 1809407] Re: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1809407 Title: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Every other wake from sleep presents a corrupted screen with no unlock app. There's a dock and system menu on a black background with pixel garbage. Some personal information in the dock's large window thumbnails. Bitmap garbage flashes on the screen when interacting with anything. Only workaround is doing another sleep-wake cycle. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:4b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 20 22:19:29 2018 DistUpgraded: 2018-12-01 23:07:50,385 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 DkmsStatus: nvidia, 390.87, 4.18.0-11-generic, x86_64: installed nvidia, 390.87, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162] InstallationDate: Installed on 2018-10-28 (54 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Default string 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-12-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-CF 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.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1822179] Re: Resuming from sleep breaks desktop and lock screen background in GNOME
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 ** This bug is no longer a duplicate of bug 1576859 [nvidia] Graphics corruption when resuming from suspend ** This bug has been marked a duplicate of bug 1809407 [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1822179 Title: Resuming from sleep breaks desktop and lock screen background in GNOME Status in gnome-shell package in Ubuntu: New Bug description: CPU: AMD Ryzen 5 1600 MOBO: MSI B350M MORTAR GPU: NVIDIA GTX 1060 Ubuntu version: 19.04 Nvidia driver version: 418.56 The system is updated with the latest updates as today, 28 March 2019 As the title says, in Ubuntu 19.04 the GNOME lockscreen gets corrupted, and the GNOME desktop has blank background after resuming from standby/sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822179/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809407] Re: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything.
** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-418 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1809407 Title: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Every other wake from sleep presents a corrupted screen with no unlock app. There's a dock and system menu on a black background with pixel garbage. Some personal information in the dock's large window thumbnails. Bitmap garbage flashes on the screen when interacting with anything. Only workaround is doing another sleep-wake cycle. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:4b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 20 22:19:29 2018 DistUpgraded: 2018-12-01 23:07:50,385 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 DkmsStatus: nvidia, 390.87, 4.18.0-11-generic, x86_64: installed nvidia, 390.87, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162] InstallationDate: Installed on 2018-10-28 (54 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Default string 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-12-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-CF 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.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1822184] Re: clear_console locks up video when X is running and you log out from a plain text console
** Changed in: xorg-server Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1822184 Title: clear_console locks up video when X is running and you log out from a plain text console Status in X.Org X server: New Status in bash package in Ubuntu: Opinion Status in xorg-server package in Ubuntu: Confirmed Status in xorg package in Debian: New Status in xorg-server package in Debian: Confirmed Bug description: References: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810660 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866898 If X is running and you switch to a plain text console (ie ctrl-alt-f3), log in as a regular user, and then log out, the display switches back to the graphical login screen and locks up. The system is still functioning (can ssh in, etc) but the video output is frozen. The underlying cause is: https://gitlab.freedesktop.org/xorg/xserver/issues/492 However, the problem can at least be worked around by making clear_console switch to tty 6 and back instead of switching to 1 and back. This patch corrects the problem: --- bash-4.4.18.orig/debian/clear_console.c 2019-03-28 12:09:02.415907787 -0400 +++ bash-4.4.18/debian/clear_console.c 2019-03-28 12:08:11.984366858 -0400 @@ -205,7 +205,7 @@ #if defined(__linux__) num = vtstat.v_active; #endif - tmp_num = (num == 1 ? 2 : 1); + tmp_num = (num == 6 ? 5 : 6); /* switch vt to clear the scrollback buffer */ if (ioctl(fd, VT_ACTIVATE, tmp_num)) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1822184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818766] Re: Update to 1.47
Now I double check snapd-glib is not published in 18.04 yet - I must have tested the locally installed version. Will retest when published. ** Tags removed: verification-done-bionic ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1818766 Title: Update to 1.47 Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Xenial: Fix Committed Status in snapd-glib source package in Bionic: Fix Committed Status in snapd-glib source package in Cosmic: Fix Committed Status in snapd-glib source package in Disco: Fix Released Bug description: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Any new release has a risk of introducing bugs, this is mitigated by automatic regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1818766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812918] Re: Bose QC35 bluetooth audio cuts out and is disjoined in 18.04
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1812918 Title: Bose QC35 bluetooth audio cuts out and is disjoined in 18.04 Status in bluez package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: Since upgrade Ubuntu 16.04 to 18.04, my bluetooth did not work fine, sound is disjoined 1) Ubuntu 18.04.1 LTS 2) apt-cache policy pkgname N: Impossible de trouver le paquet pkgname 3) With Ubuntu 16.04, my headset ( Bose QC35 ) was working fine by bluetooth connection 4) Sound is disjoined with Ubuntu 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 22 21:47:25 2019 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=53832273-15e8-4b92-b0a3-6b1f2cf57770 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A78M-DS2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd01/08/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:1B:10:00:2A:EC ACL MTU: 1017:8 SCO MTU: 64:0 UP RUNNING PSCAN INQUIRY RX bytes:2620674 acl:357 sco:53942 events:1739 errors:0 TX bytes:3630646 acl:4536 sco:0 commands:218 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813352] Re: confined applications show as unconfined
[Expired for gnome-software (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-software (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1813352 Title: confined applications show as unconfined Status in gnome-software package in Ubuntu: Expired Bug description: Applications that are confined, e.g.; chromium (https://snapcraft.io/chromium) show up as unconfined on gnome- software. Screenshots attached. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-software-plugin-snap 3.30.6-2ubuntu2 Uname: Linux 4.18.20-surface-linux-surface x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 25 16:26:54 2019 InstallationDate: Installed on 2019-01-24 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190123) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu2 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1813352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812918] Re: Bose QC35 bluetooth audio cuts out and is disjoined in 18.04
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1812918 Title: Bose QC35 bluetooth audio cuts out and is disjoined in 18.04 Status in bluez package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: Since upgrade Ubuntu 16.04 to 18.04, my bluetooth did not work fine, sound is disjoined 1) Ubuntu 18.04.1 LTS 2) apt-cache policy pkgname N: Impossible de trouver le paquet pkgname 3) With Ubuntu 16.04, my headset ( Bose QC35 ) was working fine by bluetooth connection 4) Sound is disjoined with Ubuntu 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 22 21:47:25 2019 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=53832273-15e8-4b92-b0a3-6b1f2cf57770 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A78M-DS2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd01/08/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:1B:10:00:2A:EC ACL MTU: 1017:8 SCO MTU: 64:0 UP RUNNING PSCAN INQUIRY RX bytes:2620674 acl:357 sco:53942 events:1739 errors:0 TX bytes:3630646 acl:4536 sco:0 commands:218 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1576859] Re: [nvidia] Graphics corruption when resuming from suspend
Seriously, what the actual fuck? This bug(and others!) was reported 3 goddamn years ago and you people are still resurrecting it by adding useless tags that in no shape or form help the problem getting solved. If you have no interest in actually fixing the issue then mark it as "won't fix" and let it die since there is clearly *NO* intention of EVER fixing it. Ubuntu is a buggy pile of bovine manure and Canonical and related community members seem to have little to no interest in changing that. I installed Ubuntu 18.04 LTS only to instantly run into a bug where the launcher would appear on the lock screen and being completely functional. How the actual fuck did that not get fixed in the beta? IIRC I asked for all the bug reports that I made to be closed since -despite being mostly critical- they were never going to be fixed. If no one at canonical or the surrounding community can at least have the decency to try to fix *CRITICAL* bugs in the software in their distro then at least have the decency to not resurrect *YEARS OLD* dead bug reports that will never get fixed. I'm not asking much here. inb4 "Ubuntu is a community project and relies on community volunteers" Sorry, you don't get to use that defense after shouting from the rooftops how (metaphorically) big your dicks are compared to the competition. You want to be a big boy OS? Start actually supporting your distro. There is ZERO reason why an LTS distro should have critical -easy-to-run-into bugs 6 months after it's release(looking at you Ubuntu Gnome, but much probably applies to standard Ubuntu). You drop a deuce of a distro release and then drop another 6 months later. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1576859 Title: [nvidia] Graphics corruption when resuming from suspend Status in gnome-shell package in Ubuntu: Confirmed Bug description: Resuming from suspend results in graphical glitches. These glitches, at least on the cover screen(shows date/time) go away when the Hard Drive spins back up. Additional corruption can occur in overview on currently active applications(Such as Chromium). Description: Ubuntu 16.04 LTS Release: 16.04 gnome-shell: Installed: 3.18.4-0ubuntu3 Candidate: 3.18.4-0ubuntu3 Version table: *** 3.18.4-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 29 15:56:14 2016 DisplayManager: gdm3 InstallationDate: Installed on 2016-04-23 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1576859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818766] Re: Update to 1.47
Correction gnome-initial-setup is on 18.10 - tested this and it is showing promoted snaps with updated snapd-glib. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1818766 Title: Update to 1.47 Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Xenial: Fix Committed Status in snapd-glib source package in Bionic: Fix Committed Status in snapd-glib source package in Cosmic: Fix Committed Status in snapd-glib source package in Disco: Fix Released Bug description: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Any new release has a risk of introducing bugs, this is mitigated by automatic regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1818766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818766] Re: Update to 1.47
Tested snapd-glib 1.47-0ubuntu0.18.04.0 in Ubuntu 18.104 LTS (bionic). GNOME software able to install/remove/launch snaps (moon-buggy tested), pulse audio still working, gnome-initial-setup showing promoted snaps. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1818766 Title: Update to 1.47 Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Xenial: Fix Committed Status in snapd-glib source package in Bionic: Fix Committed Status in snapd-glib source package in Cosmic: Fix Committed Status in snapd-glib source package in Disco: Fix Released Bug description: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Any new release has a risk of introducing bugs, this is mitigated by automatic regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1818766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818766] Re: Update to 1.47
Tested snapd-glib 1.47-0ubuntu0.18.10.0 in Ubuntu 18.10 (cosmic). GNOME software able to install/remove/launch snaps (moon-buggy tested), pulse audio still working, gnome-initial-setup not present on this system. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1818766 Title: Update to 1.47 Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Xenial: Fix Committed Status in snapd-glib source package in Bionic: Fix Committed Status in snapd-glib source package in Cosmic: Fix Committed Status in snapd-glib source package in Disco: Fix Released Bug description: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Any new release has a risk of introducing bugs, this is mitigated by automatic regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1818766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822184] Re: clear_console locks up video when X is running and you log out from a plain text console
** Changed in: xorg-server (Debian) Status: Unknown => Confirmed ** Changed in: xorg (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1822184 Title: clear_console locks up video when X is running and you log out from a plain text console Status in X.Org X server: Unknown Status in bash package in Ubuntu: Opinion Status in xorg-server package in Ubuntu: Confirmed Status in xorg package in Debian: New Status in xorg-server package in Debian: Confirmed Bug description: References: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810660 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866898 If X is running and you switch to a plain text console (ie ctrl-alt-f3), log in as a regular user, and then log out, the display switches back to the graphical login screen and locks up. The system is still functioning (can ssh in, etc) but the video output is frozen. The underlying cause is: https://gitlab.freedesktop.org/xorg/xserver/issues/492 However, the problem can at least be worked around by making clear_console switch to tty 6 and back instead of switching to 1 and back. This patch corrects the problem: --- bash-4.4.18.orig/debian/clear_console.c 2019-03-28 12:09:02.415907787 -0400 +++ bash-4.4.18/debian/clear_console.c 2019-03-28 12:08:11.984366858 -0400 @@ -205,7 +205,7 @@ #if defined(__linux__) num = vtstat.v_active; #endif - tmp_num = (num == 1 ? 2 : 1); + tmp_num = (num == 6 ? 5 : 6); /* switch vt to clear the scrollback buffer */ if (ioctl(fd, VT_ACTIVATE, tmp_num)) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1822184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821426] Re: [nvidia] Ubuntu 19.14 disco will not boot on Dell Precision5530
*** This bug is a duplicate of bug 1822026 *** https://bugs.launchpad.net/bugs/1822026 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1822026, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - Ubuntu 19.14 disco will not boot on Dell Precision5530 + [nvidia] Ubuntu 19.14 disco will not boot on Dell Precision5530 ** Tags added: nvidia ** Summary changed: - [nvidia] Ubuntu 19.14 disco will not boot on Dell Precision5530 + Ubuntu 19.14 disco will not boot on Dell Precision 5530 with Quadro P1000 Mobile ** Summary changed: - Ubuntu 19.14 disco will not boot on Dell Precision 5530 with Quadro P1000 Mobile + Ubuntu 19.04 disco will not boot on Dell Precision 5530 with Quadro P1000 Mobile ** This bug has been marked a duplicate of bug 1822026 [Dell Precision 7530/5530 with Nvidia Quadro P1000] Live USB freezes or cannot complete install when nouveau driver is loaded (crashing in GP100 code) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1821426 Title: Ubuntu 19.04 disco will not boot on Dell Precision 5530 with Quadro P1000 Mobile Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: I'm uncertain which package is causing the problem, though I strongly suspect it may be nvidia related. This laptop runs 18.10 just fine, but attempting to boot 19.04 from a USB disk (tried multiple USB boot disks) results in a blank screen after Grub. The video will go between black with back light and black without back light. I cannot switch to a TTY, I cannot get further, keyboard seems to respond (lights up when keys are pressed). Additionally, when trying to upgrade from 18.10 the same result happens. After running the upgrade and rebooting, I cannot get it to boot unless I first start in recovery mode from grub. After that I can get to the desktop (nouveau driver seems to be installed by default). Any attempt to boot normally results in a black screen. Attempting to switch to proprietary nvidia driver results in never getting the luks screen (encrypted disk). I get no luks screen when booting normally either. lspci 00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07) 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 07) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10) 00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) 00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10) 00:15.0 Serial bus controller [0c80]: Intel Corporation Device a368 (rev 10) 00:15.1 Serial bus controller [0c80]: Intel Corporation Device a369 (rev 10) 00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10) 00:17.0 SATA controller: Intel Corporation Device a353 (rev 10) 00:1b.0 PCI bridge: Intel Corporation Device a340 (rev f0) 00:1c.0 PCI bridge: Intel Corporation Device a338 (rev f0) 00:1c.4 PCI bridge: Intel Corporation Device a33c (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port 9 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device a30e (rev 10) 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10) 01:00.0 3D controller: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] (rev a1) 3b:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29) 3c:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 3d:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 011a --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha
[Desktop-packages] [Bug 1822072] Re: User selector doesn't have focus from login screen after screen turned off
** No longer affects: gnome-shell -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1822072 Title: User selector doesn't have focus from login screen after screen turned off Status in gnome-shell package in Ubuntu: Confirmed Bug description: In gdm usually the user name is pre-selected. This means that you can just hit enter and then put your password in. In Disco this is the case on boot up. If you wait for the screensaver to kick in (i.e. boot and do nothing for 5 mins) then when the screen comes back again the username is not selected. Steps To Reproduce 1. Boot Disco 2. Once you get to the login screen, notice that your username is selected. 3. Do nothing, touch nothing. Wait for the screensaver to kick in and blank the screens. 4. Wiggle the mouse, dismiss the clock screen and you will be back at the login screen 5. Notice that you user is no longer selected and in order to log in you have to move the mouse and click on the user name What should happen The username should be pre-selected so that I can log in without having to use the mouse. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822072/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822184] Re: clear_console locks up video when X is running and you log out from a plain text console
** Bug watch added: Debian Bug tracker #866898 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866898 ** Also affects: xorg (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866898 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #810660 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810660 ** Also affects: xorg-server (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810660 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #492 https://gitlab.freedesktop.org/xorg/xserver/issues/492 ** Also affects: xorg-server via https://gitlab.freedesktop.org/xorg/xserver/issues/492 Importance: Unknown Status: Unknown ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: bash (Ubuntu) Status: Confirmed => Opinion ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1822184 Title: clear_console locks up video when X is running and you log out from a plain text console Status in X.Org X server: Unknown Status in bash package in Ubuntu: Opinion Status in xorg-server package in Ubuntu: Confirmed Status in xorg package in Debian: Unknown Status in xorg-server package in Debian: Unknown Bug description: References: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810660 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866898 If X is running and you switch to a plain text console (ie ctrl-alt-f3), log in as a regular user, and then log out, the display switches back to the graphical login screen and locks up. The system is still functioning (can ssh in, etc) but the video output is frozen. The underlying cause is: https://gitlab.freedesktop.org/xorg/xserver/issues/492 However, the problem can at least be worked around by making clear_console switch to tty 6 and back instead of switching to 1 and back. This patch corrects the problem: --- bash-4.4.18.orig/debian/clear_console.c 2019-03-28 12:09:02.415907787 -0400 +++ bash-4.4.18/debian/clear_console.c 2019-03-28 12:08:11.984366858 -0400 @@ -205,7 +205,7 @@ #if defined(__linux__) num = vtstat.v_active; #endif - tmp_num = (num == 1 ? 2 : 1); + tmp_num = (num == 6 ? 5 : 6); /* switch vt to clear the scrollback buffer */ if (ioctl(fd, VT_ACTIVATE, tmp_num)) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1822184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821426] modified.conffile..etc.gdm3.custom.conf.txt
apport information ** Attachment added: "modified.conffile..etc.gdm3.custom.conf.txt" https://bugs.launchpad.net/bugs/1821426/+attachment/5250381/+files/modified.conffile..etc.gdm3.custom.conf.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1821426 Title: Ubuntu 19.14 disco will not boot on Dell Precision5530 Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: I'm uncertain which package is causing the problem, though I strongly suspect it may be nvidia related. This laptop runs 18.10 just fine, but attempting to boot 19.04 from a USB disk (tried multiple USB boot disks) results in a blank screen after Grub. The video will go between black with back light and black without back light. I cannot switch to a TTY, I cannot get further, keyboard seems to respond (lights up when keys are pressed). Additionally, when trying to upgrade from 18.10 the same result happens. After running the upgrade and rebooting, I cannot get it to boot unless I first start in recovery mode from grub. After that I can get to the desktop (nouveau driver seems to be installed by default). Any attempt to boot normally results in a black screen. Attempting to switch to proprietary nvidia driver results in never getting the luks screen (encrypted disk). I get no luks screen when booting normally either. lspci 00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07) 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 07) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10) 00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) 00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10) 00:15.0 Serial bus controller [0c80]: Intel Corporation Device a368 (rev 10) 00:15.1 Serial bus controller [0c80]: Intel Corporation Device a369 (rev 10) 00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10) 00:17.0 SATA controller: Intel Corporation Device a353 (rev 10) 00:1b.0 PCI bridge: Intel Corporation Device a340 (rev f0) 00:1c.0 PCI bridge: Intel Corporation Device a338 (rev f0) 00:1c.4 PCI bridge: Intel Corporation Device a33c (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port 9 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device a30e (rev 10) 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10) 01:00.0 3D controller: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] (rev a1) 3b:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29) 3c:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 3d:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 011a --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) Package: gnome-shell PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-03-29T03:07:48.704000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1821426/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821426] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1821426/+attachment/5250380/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1821426 Title: Ubuntu 19.14 disco will not boot on Dell Precision5530 Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: I'm uncertain which package is causing the problem, though I strongly suspect it may be nvidia related. This laptop runs 18.10 just fine, but attempting to boot 19.04 from a USB disk (tried multiple USB boot disks) results in a blank screen after Grub. The video will go between black with back light and black without back light. I cannot switch to a TTY, I cannot get further, keyboard seems to respond (lights up when keys are pressed). Additionally, when trying to upgrade from 18.10 the same result happens. After running the upgrade and rebooting, I cannot get it to boot unless I first start in recovery mode from grub. After that I can get to the desktop (nouveau driver seems to be installed by default). Any attempt to boot normally results in a black screen. Attempting to switch to proprietary nvidia driver results in never getting the luks screen (encrypted disk). I get no luks screen when booting normally either. lspci 00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07) 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 07) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10) 00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) 00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10) 00:15.0 Serial bus controller [0c80]: Intel Corporation Device a368 (rev 10) 00:15.1 Serial bus controller [0c80]: Intel Corporation Device a369 (rev 10) 00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10) 00:17.0 SATA controller: Intel Corporation Device a353 (rev 10) 00:1b.0 PCI bridge: Intel Corporation Device a340 (rev f0) 00:1c.0 PCI bridge: Intel Corporation Device a338 (rev f0) 00:1c.4 PCI bridge: Intel Corporation Device a33c (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port 9 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device a30e (rev 10) 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10) 01:00.0 3D controller: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] (rev a1) 3b:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29) 3c:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 3d:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 011a --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) Package: gnome-shell PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-03-29T03:07:48.704000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1821426/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820850] Re: [FFe] Distro patch GNOME hi-dpi support for x11 sessions
This bug was fixed in the package mutter - 3.32.0-1ubuntu1 --- mutter (3.32.0-1ubuntu1) disco; urgency=medium * debian/control: - Update VCS flags to point to launchpad - Update maintainer to ubuntu * debian/gbp.conf: update branch to point to ubuntu/master * debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch: - X11: Add support for fractional scaling using Randr (LP: #1820850) -- Marco Trevisan (Treviño) Wed, 27 Mar 2019 06:48:11 +0100 ** Changed in: mutter (Ubuntu) Status: Triaged => Fix Released ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1820850 Title: [FFe] Distro patch GNOME hi-dpi support for x11 sessions Status in gnome-control-center package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Triaged Bug description: The first part of our work on better handling of HI-DPI screens got merged upstream in 3.32, but it's for wayland only https://blog.3v1n0.net/informatica/linux/gnome-shell-fractional-scaling-in-wayland-landed/ Since our default session in Ubuntu is based on xorg we would like to distro patch the x11 equivalent for Disco so our users can benefit from the feature. Updates packages are up for testing in that ppa https://launchpad.net/~3v1n0/+archive/ubuntu/mutter-x11-fractional-scaling The main change is https://launchpadlibrarian.net/415722066/mutter_3.32.0-1_3.32.0-1ubuntu1~xrandrscaling3.diff.gz The ppa also includes a bugfix and a settings change to allow easy configuration. Note that the feature is behind an experimental gsettings key and the code has no impact on the rendering for users who don't enable it, which means it shouldn't be too risk. It's available as a opt-in for those who want to test it. From our testing it works fine and we feel like it's ready to be included. We do plan to get that work merged upstream in the next cycle so it should not be an Ubuntu delta to carry over forever. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1820850/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820850] Re: [FFe] Distro patch GNOME hi-dpi support for x11 sessions
This bug was fixed in the package gnome-control-center - 1:3.32.0.1-1ubuntu6 --- gnome-control-center (1:3.32.0.1-1ubuntu6) disco; urgency=medium * debian/patches/display-Don-t-always-set-the-primary-monitor-to-the-first.patch: - Make sure the display panel primary monitor matches configured one * debian/patches/display-Support-UI-scaled-logical-monitor-mode.patch: - Support scaled logical monitors using UI scale as it could happen when using the X11 Randr scaling (LP: #1820850) -- Marco Trevisan (Treviño) Wed, 27 Mar 2019 06:10:59 +0100 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1820850 Title: [FFe] Distro patch GNOME hi-dpi support for x11 sessions Status in gnome-control-center package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Triaged Bug description: The first part of our work on better handling of HI-DPI screens got merged upstream in 3.32, but it's for wayland only https://blog.3v1n0.net/informatica/linux/gnome-shell-fractional-scaling-in-wayland-landed/ Since our default session in Ubuntu is based on xorg we would like to distro patch the x11 equivalent for Disco so our users can benefit from the feature. Updates packages are up for testing in that ppa https://launchpad.net/~3v1n0/+archive/ubuntu/mutter-x11-fractional-scaling The main change is https://launchpadlibrarian.net/415722066/mutter_3.32.0-1_3.32.0-1ubuntu1~xrandrscaling3.diff.gz The ppa also includes a bugfix and a settings change to allow easy configuration. Note that the feature is behind an experimental gsettings key and the code has no impact on the rendering for users who don't enable it, which means it shouldn't be too risk. It's available as a opt-in for those who want to test it. From our testing it works fine and we feel like it's ready to be included. We do plan to get that work merged upstream in the next cycle so it should not be an Ubuntu delta to carry over forever. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1820850/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821426] Re: Ubuntu 19.14 disco will not boot on Dell Precision5530
I can get to the desktop by adding nomodeset Tried it on the latest 19.04 from 3/26 Without nomodeset it continues its flashing black screen However it reports as "unknown display" and I can not get it to detect an external display. Attaching the apport-collect but it is from a live disk, I'm not sure if that'll be helpful. Unfortunately I cannot install ubuntu 19.04 at this time because I need use of the computer which works fine under 18.10. It looks like I cannot disable the GPU in BIOS on this machine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1821426 Title: Ubuntu 19.14 disco will not boot on Dell Precision5530 Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: I'm uncertain which package is causing the problem, though I strongly suspect it may be nvidia related. This laptop runs 18.10 just fine, but attempting to boot 19.04 from a USB disk (tried multiple USB boot disks) results in a blank screen after Grub. The video will go between black with back light and black without back light. I cannot switch to a TTY, I cannot get further, keyboard seems to respond (lights up when keys are pressed). Additionally, when trying to upgrade from 18.10 the same result happens. After running the upgrade and rebooting, I cannot get it to boot unless I first start in recovery mode from grub. After that I can get to the desktop (nouveau driver seems to be installed by default). Any attempt to boot normally results in a black screen. Attempting to switch to proprietary nvidia driver results in never getting the luks screen (encrypted disk). I get no luks screen when booting normally either. lspci 00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07) 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 07) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10) 00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) 00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10) 00:15.0 Serial bus controller [0c80]: Intel Corporation Device a368 (rev 10) 00:15.1 Serial bus controller [0c80]: Intel Corporation Device a369 (rev 10) 00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10) 00:17.0 SATA controller: Intel Corporation Device a353 (rev 10) 00:1b.0 PCI bridge: Intel Corporation Device a340 (rev f0) 00:1c.0 PCI bridge: Intel Corporation Device a338 (rev f0) 00:1c.4 PCI bridge: Intel Corporation Device a33c (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port 9 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device a30e (rev 10) 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10) 01:00.0 3D controller: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] (rev a1) 3b:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29) 3c:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 3d:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 011a --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) Package: gnome-shell PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-03-29T03:07:48.704000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1821426/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1818766] Re: Update to 1.47
Test packages now accepted and 1.47 is available in -proposed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1818766 Title: Update to 1.47 Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Xenial: Fix Committed Status in snapd-glib source package in Bionic: Fix Committed Status in snapd-glib source package in Cosmic: Fix Committed Status in snapd-glib source package in Disco: Fix Released Bug description: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Any new release has a risk of introducing bugs, this is mitigated by automatic regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1818766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821426] Re: Ubuntu 19.14 disco will not boot on Dell Precision5530
apport information ** Tags added: apport-collected disco ** Description changed: I'm uncertain which package is causing the problem, though I strongly suspect it may be nvidia related. This laptop runs 18.10 just fine, but attempting to boot 19.04 from a USB disk (tried multiple USB boot disks) results in a blank screen after Grub. The video will go between black with back light and black without back light. I cannot switch to a TTY, I cannot get further, keyboard seems to respond (lights up when keys are pressed). Additionally, when trying to upgrade from 18.10 the same result happens. After running the upgrade and rebooting, I cannot get it to boot unless I first start in recovery mode from grub. After that I can get to the desktop (nouveau driver seems to be installed by default). Any attempt to boot normally results in a black screen. Attempting to switch to proprietary nvidia driver results in never getting the luks screen (encrypted disk). I get no luks screen when booting normally either. lspci 00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07) 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 07) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10) 00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) 00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10) 00:15.0 Serial bus controller [0c80]: Intel Corporation Device a368 (rev 10) 00:15.1 Serial bus controller [0c80]: Intel Corporation Device a369 (rev 10) 00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10) 00:17.0 SATA controller: Intel Corporation Device a353 (rev 10) 00:1b.0 PCI bridge: Intel Corporation Device a340 (rev f0) 00:1c.0 PCI bridge: Intel Corporation Device a338 (rev f0) 00:1c.4 PCI bridge: Intel Corporation Device a33c (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port 9 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device a30e (rev 10) 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10) 01:00.0 3D controller: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] (rev a1) 3b:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29) 3c:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 3d:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 011a + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu23 + Architecture: amd64 + CasperVersion: 1.402 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.04 + LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) + Package: gnome-shell + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 + Tags: disco + Uname: Linux 5.0.0-7-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + mtime.conffile..etc.gdm3.custom.conf: 2019-03-29T03:07:48.704000 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1821426/+attachment/5250379/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1821426 Title: Ubuntu 19.14 disco will not boot on Dell Precision5530 Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: I'm uncertain which package is causing the problem, though I strongly suspect it may be nvidia related. This laptop runs 18.10 just fine, but attempting to boot 19.04 from a USB disk (tried multiple USB boot disks) results in a blank screen after Grub. The video will go between black with back light and black without back light. I cannot switch to a TTY, I cannot get further, keyboard seems to respond (lights up when keys are pressed). Additionally, when trying to upgrade from 18.10 the same result happens. After running the upgrade and rebooting, I cannot get it to boot unless I first start in
[Desktop-packages] [Bug 1822072] Re: User selector doesn't have focus from login screen after screen turned off
** Changed in: gnome-shell Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1822072 Title: User selector doesn't have focus from login screen after screen turned off Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: In gdm usually the user name is pre-selected. This means that you can just hit enter and then put your password in. In Disco this is the case on boot up. If you wait for the screensaver to kick in (i.e. boot and do nothing for 5 mins) then when the screen comes back again the username is not selected. Steps To Reproduce 1. Boot Disco 2. Once you get to the login screen, notice that your username is selected. 3. Do nothing, touch nothing. Wait for the screensaver to kick in and blank the screens. 4. Wiggle the mouse, dismiss the clock screen and you will be back at the login screen 5. Notice that you user is no longer selected and in order to log in you have to move the mouse and click on the user name What should happen The username should be pre-selected so that I can log in without having to use the mouse. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1822072/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout
*** This bug is a duplicate of bug 1822184 *** https://bugs.launchpad.net/bugs/1822184 Updates from bug 1804607, this is a known xorg issue and duplicates bug 1822184 that can be worked around by disable clear_console in the $HOME/.bash_logout: $ cat $HOME/.bash_logout # ~/.bash_logout: executed by bash(1) when login shell exits. # when leaving the console clear the screen to increase privacy if [ "$SHLVL" = 1 ]; then # [ -x /usr/bin/clear_console ] && /usr/bin/clear_console -q fi ** This bug has been marked a duplicate of bug 1822184 clear_console locks up video when X is running and you log out from a plain text console -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-graphics-drivers-410 package in Ubuntu: New Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: *
[Desktop-packages] [Bug 1576859] Re: [nvidia] Graphics corruption when resuming from suspend
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1576859 Title: [nvidia] Graphics corruption when resuming from suspend Status in gnome-shell package in Ubuntu: Confirmed Bug description: Resuming from suspend results in graphical glitches. These glitches, at least on the cover screen(shows date/time) go away when the Hard Drive spins back up. Additional corruption can occur in overview on currently active applications(Such as Chromium). Description: Ubuntu 16.04 LTS Release: 16.04 gnome-shell: Installed: 3.18.4-0ubuntu3 Candidate: 3.18.4-0ubuntu3 Version table: *** 3.18.4-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 29 15:56:14 2016 DisplayManager: gdm3 InstallationDate: Installed on 2016-04-23 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1576859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1576859] Re: [nvidia] Graphics corruption when resuming from suspend
** Tags added: cosmic disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1576859 Title: [nvidia] Graphics corruption when resuming from suspend Status in gnome-shell package in Ubuntu: Confirmed Bug description: Resuming from suspend results in graphical glitches. These glitches, at least on the cover screen(shows date/time) go away when the Hard Drive spins back up. Additional corruption can occur in overview on currently active applications(Such as Chromium). Description: Ubuntu 16.04 LTS Release: 16.04 gnome-shell: Installed: 3.18.4-0ubuntu3 Candidate: 3.18.4-0ubuntu3 Version table: *** 3.18.4-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 29 15:56:14 2016 DisplayManager: gdm3 InstallationDate: Installed on 2016-04-23 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1576859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809407] Re: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything.
*** This bug is a duplicate of bug 1576859 *** https://bugs.launchpad.net/bugs/1576859 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1576859, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1576859 [nvidia] Graphics corruption when resuming from suspend -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1809407 Title: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. Status in gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: Every other wake from sleep presents a corrupted screen with no unlock app. There's a dock and system menu on a black background with pixel garbage. Some personal information in the dock's large window thumbnails. Bitmap garbage flashes on the screen when interacting with anything. Only workaround is doing another sleep-wake cycle. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:4b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 20 22:19:29 2018 DistUpgraded: 2018-12-01 23:07:50,385 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 DkmsStatus: nvidia, 390.87, 4.18.0-11-generic, x86_64: installed nvidia, 390.87, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162] InstallationDate: Installed on 2018-10-28 (54 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Default string 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-12-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-CF 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.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Desktop-packages] [Bug 1758544] Re: [nvidia] On resume, a black screen delays login screen
** Summary changed: - On unsuspend, a black screen delays login screen + [nvidia] On resume, a black screen delays login screen -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1758544 Title: [nvidia] On resume, a black screen delays login screen Status in gnome-shell package in Ubuntu: New Bug description: Every time I suspend the notebook (close lid, not sure about suspension by command) when I unsuspend (open lid) a long time black screen with only mouse pointer visible delays the login screen to display (about 10~15 seconds of delaying). The mouse pointer works but with brief freezings when moving, something like 0,5s of freezing for each 1,5s moving. This notebook is a i7 16GB ram 120GB SSD so it should never happen, in fact, it never happened in Deepin Linux or even Ubuntu 16.04. I will be available to provide some other information you need. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.42 Sat Mar 3 04:10:22 PST 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-11ubuntu1) ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 24 12:26:54 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.42, 4.15.0-12-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 530 [1179:f840] InstallationDate: Installed on 2018-03-09 (14 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 009: ID 04f2:b446 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 248a:8366 Bus 001 Device 002: ID 04f3:2228 Elan Microelectronics Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA Satellite S55t-C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=62fa4fcd-f1c6-43f5-a86d-ccaae2565dac ro locale=pt_BR quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.20 dmi.board.name: 06F4 dmi.board.vendor: FF50 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.20:bd10/08/2015:svnTOSHIBA:pnSatelliteS55t-C:pvrPSPUGU-00200D:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite S55t-C dmi.product.version: PSPUGU-00200D dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1758544/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822179] Re: Resuming from sleep breaks desktop and lock screen background in GNOME
*** This bug is a duplicate of bug 1576859 *** https://bugs.launchpad.net/bugs/1576859 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1576859, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** This bug has been marked a duplicate of bug 1576859 [nvidia] Graphics corruption when resuming from suspend -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1822179 Title: Resuming from sleep breaks desktop and lock screen background in GNOME Status in gnome-shell package in Ubuntu: New Bug description: CPU: AMD Ryzen 5 1600 MOBO: MSI B350M MORTAR GPU: NVIDIA GTX 1060 Ubuntu version: 19.04 Nvidia driver version: 418.56 The system is updated with the latest updates as today, 28 March 2019 As the title says, in Ubuntu 19.04 the GNOME lockscreen gets corrupted, and the GNOME desktop has blank background after resuming from standby/sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822179/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822082] Re: [disco] Shell sometimes shows username instead of full name in top-right menu
Please report this bug to the GNOME developers here: https://gitlab.gnome.org/GNOME/gnome-shell/issues and then tell us the new issue ID. ** Tags added: disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1822082 Title: [disco] Shell sometimes shows username instead of full name in top- right menu Status in gnome-shell package in Ubuntu: New Bug description: The drop-down menu of gnome-shell where you can logout etc. sometimes shows my username (jak) isntead of my fullname. Closing and opening again fixes it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822082/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822073] Re: Bluetooth headset profile forgotten after disconnection
AFAIK, only gnome-control-center has any memory of user preferences. So reassigning there. ** Tags added: a2dp ** Package changed: pulseaudio (Ubuntu) => gnome-control-center (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1822073 Title: Bluetooth headset profile forgotten after disconnection Status in pulseaudio package in Ubuntu: Confirmed Bug description: Similar to bug 1283003, after connecting my Bluetooth headset (Sony WH-1000X M3) they appear in Gnome Control Centre's Sound tab but are not selectable. I've narrowed down the circumstances to reproduce the bug as follows: 1. Start with working sound through Bluetooth to headset 2. In pavucontrol's Configuration tab, note that headset is listed with A2DP profile 3. Disconnect (power off) the headset 4. Note that sound comes out of fallback device (as expected) 5. Power on the headset and reconnect to Bluetooth 6. Look in Gnome Control Centre and note the headset appears in Sound, but is not selectable (buggy) 7. In pavucontrol's Configuration tab, note headset is listed with "Off" 8. Manually switch to A2DP 9. At the point, we have to cycle the connection again (disconnect/reconnect) and then sound is once more routed to the headset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 28 10:33:37 2019 InstallationDate: Installed on 2015-07-04 (1363 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97 GAMING 5 (MS-7917) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd12/23/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7917 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1822073/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822073] Re: Bluetooth headset profile forgotten after disconnection
I stand corrected. There is also ~/.config/pulse ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed ** No longer affects: gnome-control-center (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1822073 Title: Bluetooth headset profile forgotten after disconnection Status in pulseaudio package in Ubuntu: Confirmed Bug description: Similar to bug 1283003, after connecting my Bluetooth headset (Sony WH-1000X M3) they appear in Gnome Control Centre's Sound tab but are not selectable. I've narrowed down the circumstances to reproduce the bug as follows: 1. Start with working sound through Bluetooth to headset 2. In pavucontrol's Configuration tab, note that headset is listed with A2DP profile 3. Disconnect (power off) the headset 4. Note that sound comes out of fallback device (as expected) 5. Power on the headset and reconnect to Bluetooth 6. Look in Gnome Control Centre and note the headset appears in Sound, but is not selectable (buggy) 7. In pavucontrol's Configuration tab, note headset is listed with "Off" 8. Manually switch to A2DP 9. At the point, we have to cycle the connection again (disconnect/reconnect) and then sound is once more routed to the headset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 28 10:33:37 2019 InstallationDate: Installed on 2015-07-04 (1363 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97 GAMING 5 (MS-7917) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd12/23/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7917 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1822073/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822075] Re: tooltips and combo boxes in webbrowsers are all garbage in xserver-xorg-video-radeon 1:19.0.0-1
** Summary changed: - tooltips and combo boxes in webbrowsers are all garbage + tooltips and combo boxes in webbrowsers are all garbage in xserver-xorg-video-radeon 1:19.0.0-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1822075 Title: tooltips and combo boxes in webbrowsers are all garbage in xserver- xorg-video-radeon 1:19.0.0-1 Status in gtk+3.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Triaged Bug description: Disco up to date With Chrome and Firefox tooltips and combo boxes are all garbage and make the browser unusable. Cf screenshots. Graphics card: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] I tried gtk2 and gtk3 demos and the combo boxes are broken in the same way. I also tried FF as a snap and as a deb and the problem is the same. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 28 11:51:41 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-07-15 (1717 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-03-24 (368 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1822075/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822072] Re: User selector doesn't have focus from login screen after screen turned off
The best match I could find upstream was an old bug: https://gitlab.gnome.org/GNOME/gdm/issues/457 ** Bug watch added: gitlab.gnome.org/GNOME/gdm/issues #457 https://gitlab.gnome.org/GNOME/gdm/issues/457 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gdm/issues/457 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Tags added: disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1822072 Title: User selector doesn't have focus from login screen after screen turned off Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: In gdm usually the user name is pre-selected. This means that you can just hit enter and then put your password in. In Disco this is the case on boot up. If you wait for the screensaver to kick in (i.e. boot and do nothing for 5 mins) then when the screen comes back again the username is not selected. Steps To Reproduce 1. Boot Disco 2. Once you get to the login screen, notice that your username is selected. 3. Do nothing, touch nothing. Wait for the screensaver to kick in and blank the screens. 4. Wiggle the mouse, dismiss the clock screen and you will be back at the login screen 5. Notice that you user is no longer selected and in order to log in you have to move the mouse and click on the user name What should happen The username should be pre-selected so that I can log in without having to use the mouse. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1822072/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822072] Re: User selector doesn't have focus from login screen after screen turned off
Reassigned to gnome-shell, which provides the GUI here. ** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1822072 Title: User selector doesn't have focus from login screen after screen turned off Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: In gdm usually the user name is pre-selected. This means that you can just hit enter and then put your password in. In Disco this is the case on boot up. If you wait for the screensaver to kick in (i.e. boot and do nothing for 5 mins) then when the screen comes back again the username is not selected. Steps To Reproduce 1. Boot Disco 2. Once you get to the login screen, notice that your username is selected. 3. Do nothing, touch nothing. Wait for the screensaver to kick in and blank the screens. 4. Wiggle the mouse, dismiss the clock screen and you will be back at the login screen 5. Notice that you user is no longer selected and in order to log in you have to move the mouse and click on the user name What should happen The username should be pre-selected so that I can log in without having to use the mouse. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1822072/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822047] Re: After install, cannot boot into system unless I use nomodeset kernel parameter (repeated kernel crashes in the nouveau driver)
*** This bug is a duplicate of bug 1822026 *** https://bugs.launchpad.net/bugs/1822026 ** Summary changed: - After install, cannot boot into system unless I use nomodeset kernel parameter + After install, cannot boot into system unless I use nomodeset kernel parameter (repeated kernel crashes in the nouveau driver) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1822047 Title: After install, cannot boot into system unless I use nomodeset kernel parameter (repeated kernel crashes in the nouveau driver) Status in xorg package in Ubuntu: Incomplete Bug description: System: Disco (19.04 beta) Hardware: Dell Precision 7530 After installing the system, it cannot start unless manually adding `nomodeset` in the kernel command line at boot time. Steps to reproduce: 1. Install disco 19.04 beta on the device. Leave all the options at default values (i.e. do not install third party drivers) 2. Once installation is finished, restart the system (the system will freeze after install is finished, it's a known issue -> lp:1822044) Expected result: 2. The system boots and user can log in and see Gnome interface. Actual result: 2. The first time, I could log into the system. However, when I tried to access the Settings screen, the system froze. After that, everytime I tried to boot the device, the screen was filled with dark purple, a mouse cursor may appear, but nothing else would happen. At that stage, the only thing I could do was to force shutdown the device, start it again and at Grub screen, press `e` to edit the kernel parameters and add `nomodeset`. This bug is created from the actual device, using `nomodeset` kernel parameter. `nouveau` graphics driver is most likely the culprit, like in all the previous issues that have been raised (see lp:1822026, lp:1822044, lp:1821882) Two workarounds exist: 1. After installation, use `nomodeset` kernel parameter to boot into the system, then install proprietary nvidia drivers. 2. During installation, install third party drivers. If Secure Boot is enabled, this requires to set a password that will be asked when the device reboots. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 28 15:39:40 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0889] NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107GLM [Quadro P1000 Mobile] [1028:0889] InstallationDate: Installed on 2019-03-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) MachineType: Dell Inc. Precision 7530 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=e07663b1-0b3d-4cdb-aa6c-f6f2e8c4ee5d ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd02/19/2019:svnDellInc.:pnPrecision7530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7530 dmi.product.sku: 0889 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1822047/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821936] Re: No sound output on Zen AIO 27 Z272SD_Z272SD
I think you might be right about bug 1784485 being similar. In that case this would be a kernel bug. And the title should refer to the model of the computer instead of the model of sound chip. ** Summary changed: - No sound output from ALC274 + No sound output on Zen AIO 27 Z272SD_Z272SD ** No longer affects: pulseaudio (Ubuntu) ** No longer affects: alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1821936 Title: No sound output on Zen AIO 27 Z272SD_Z272SD Status in linux package in Ubuntu: New Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO
[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
The kernel fix (comment #77) only checks for the laptop model name, not anything else. So it will only work for "ASUS UX391UA". If you have a different model of laptop then please open a different bug. https://mailman.alsa-project.org/pipermail/alsa- devel/2018-December/143282.html ** No longer affects: alsa-driver (Ubuntu) ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: Fix Committed ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Cosmic) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821936] Re: No sound output from ALC274
** Summary changed: - ALC274 unsupported + No sound output from ALC274 ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1821936 Title: No sound output on Zen AIO 27 Z272SD_Z272SD Status in linux package in Ubuntu: New Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi.sys.vendor:
[Desktop-packages] [Bug 701856] Re: Brother's printer/scanner drivers awkward to find and install
I just upgraded to from Xenial 16.04 to Bionic 18.04 and unfortunately the scanner broke again. Unfortunately the changes affect two places -- udev seems to have made big changes to the scanner section, so I wrote a completely new udev file, and the sane-dll backend doesn't look in the same directory. I composed my new udev script, then after lots of tinkering and some judicious use of the debug command: $ SANE_DEBUG_DLL=128 scanimage -L I discovered the changes to the sane-dll backend. I installed an instance of Trusty 14.04 and used the above command to confirm Trusty looked for brother2 in: /usr/lib/x86_64-linux-gnu/sane /usr/lib/sane Bionic ONLY looks for brother2 in: /usr/lib/x86_64-linux-gnu/sane I manually linked the files the brscan2 .deb installs into /usr/lib/x86_64-linux-gnu/sane/ and /usr/lib/x86_64-linux-gnu/ into /usr/lib/x86_64-linux-gnu/sane/ and /usr/lib/x86_64-linux-gnu/ and it seems to work. I will attempt to write up a procedure (for my benefit if nothing else). But it may take me a little while. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/701856 Title: Brother's printer/scanner drivers awkward to find and install Status in cups package in Ubuntu: Opinion Bug description: Binary package hint: cupsys Hello, I have the multifonction laser printer and scan Brother DCP-7030. It works very well in Ubuntu, but with some hard configuration. Printer is automatically detected when connected in USB, but Ubuntu does not propose DCP-7030 drivers, only DCP-7025, and it doesn't work well. To get DCP-7030 fully recognized and well printing / scanning, I have to do this (it's a short summary) : http://solutions.brother.com/linux/en_us/before.html - Printer BROTHER DCP-7030 : cd ~/desktop sudo aa-complain cupsd sudo mkdir /usr/share/cups/model http://solutions.brother.com/linux/en_us/download_prn.html#DCP-7030 sudo dpkg -i --force-all --force-architecture brdcp7030lpr-2.0.2-1.i386.deb sudo dpkg -i --force-all --force-architecture cupswrapperDCP7030-2.0.2-1.i386.deb http://127.0.0.1:631/printers/DCP7030 : OK After that printer works - SCANNING : Install scan-key-tools / Brscan3 http://solutions.brother.com/linux/en_us/download_scn.html#brscan3 http://solutions.brother.com/linux/en_us/instruction_scn1a.html sudo gedit /lib/udev/rules.d/50-udev-default.rules : in section "libusb device nodes", replacer 0664 by 0666 sudo lsusb Bus 001 Device 004: ID 04f9:01a Brother Industries, Ltd Go to dev/bus/usb : bus 1 and device 4 is root owned Open it in Nautilus as root, change it to my user name and take ownership Now Simple Scan works, Brother-DCP is seen. But... big problem ! At each restart of Ubuntu or DCP Brother, permission resets and comes back to root, I have to change ownership and re-log each time, this is not nice... Is it a way to "protect" the file against erasing or permission change ? It's also true for other models than DCP-7030 (like DCP-7040...). I do not know if it is a Cups / Ubuntu "bug" or Openprinting missing for new drivers, but as Brother gives functional drivers for Linux, this should be easily implemented I hope, as more and more materials are natively identified in Ubuntu. Thanks in advance for your help. Best regards, Xavier To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/701856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821933] Re: Touch input is offset with two screens (even appearing on the wrong screen)
More questions: * From the video it looks like the rubber band moves faster than your finger. Does it only happen when desktop scaling is >100%? * Does touch respond in the right place for the shell or apps? ** Summary changed: - Touch input is misaligned with two screens + Touch input is offset with two screens (even appearing on the wrong screen) ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags added: multimonitor touch ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1821933 Title: Touch input is offset with two screens (even appearing on the wrong screen) Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: Using touch input with one screen seems fine. However, when connecting a second screen the touch event happens at the wrong coordinates. Steps to reproduce 1. Starting with a single screen touch and hold on the background and drag. The rubber band selector shows up with the moving corner at your finger. 2. Connect a second screen 3. Do the same touch and drag as in step 1 and notice that the moving corner is offset to the right and slightly below where the touch is happening. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'" InstallationDate: Installed on 2019-03-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) Package: gnome-shell 3.32.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821904] Re: Gnome Shell always started muted on Disco
I assume this bug is about audio and you're not talking about something appearing muted...? :) I also can't see any obvious problems. Do you have any gnome-shell extensions installed? Or any other software starting automatically on login? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1821904 Title: Gnome Shell always started muted on Disco Status in pulseaudio package in Ubuntu: Incomplete Bug description: On Disco, Gnome Shell always starts muted. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe4766 F pulseaudio /dev/snd/pcmC0D0p: joe4766 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-09-15 (193 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: pulseaudio 1:12.2-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Tags: disco wayland-session Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-03-20 (7 days ago) UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/14/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1821904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1817924] Re: apps launched from gnome shell do not get input focus
** Also affects: mutter (Ubuntu Disco) Importance: High Status: Triaged ** Also affects: gnome-shell (Ubuntu Disco) Importance: High Assignee: Daniel van Vugt (vanvugt) Status: Triaged ** Changed in: mutter (Ubuntu Disco) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1817924 Title: apps launched from gnome shell do not get input focus Status in Mutter: New Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in gnome-shell source package in Disco: Triaged Status in mutter source package in Disco: Triaged Bug description: Observed on upgrading to disco-proposed today... When launching an app from the dock or from the applications grid (so i believe it's a gnome-shell thing rather than a dock thing), the app opens, but does not get the input focus. You have to either click in the window, or clicking again on the icon of the running app in the dock works, to give it focus. An extra step my muscle memory isn't prepared for! It seems like the sort of thing that might be an option rather than a bug, but if so, changing this behaviour back to its previous default is not at all obvious (I haven't found a way). So guessing it is a bug. NB: After launching an app this way, *no* window has focus. It is lost by the app that had it before, but not given to the newly started app. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 27 15:53:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (169 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-01-13 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1817924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803319] Re: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled
I think for Ubuntu 19.04 we'd probably just wait for upstream mutter release 3.32.1 which will contain the fix. ** Changed in: gnome-shell (Ubuntu Disco) Status: In Progress => Triaged ** Changed in: gnome-shell (Ubuntu Disco) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Changed in: mutter (Ubuntu Disco) Status: In Progress => Triaged ** Changed in: mutter (Ubuntu Disco) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** No longer affects: gnome-shell (Ubuntu Bionic) ** No longer affects: mutter (Ubuntu Bionic) ** Tags added: fixed-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1803319 Title: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in gnome-shell source package in Cosmic: Triaged Status in mutter source package in Cosmic: Triaged Status in gnome-shell source package in Disco: Triaged Status in mutter source package in Disco: Triaged Bug description: My set-up: a laptop with an internal screen open and scaled to 150% and an external monitor at 100% set to act as the primary screen. When I open the menus in the GNOME Shell task bar (calendar or settings/log-out/etc menu) they are displayed but not updated when I mouse over them or click on them. I can still use them by blind clicking. When I set both screens to 100% I did not see this. I am using the Wayland session. With the internal screen at 125% I saw this too, but after changing the relative position of the two it went away. I think this was a fluke, but I was unable to do the same after going back to 150%. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CasperVersion: 1.399 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 14 11:23:54 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-06-12 (154 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-10-08 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1803319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818790] Re: [regression] Desktop zoom is missing the mouse pointer
** Changed in: gnome-shell (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1818790 Title: [regression] Desktop zoom is missing the mouse pointer Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell source package in Disco: Fix Committed Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1020 Proposed fix: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/454 --- Desktop zoom is missing the mouse pointer. ProblemType: BugDistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 Date: Wed Mar 6 15:12:04 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-04 (92 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1818790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816004] Re: GLVND: AARCH64 : Fix address passed to clear cache
This bug was fixed in the package libglvnd - 1.1.1-0ubuntu1
---
libglvnd (1.1.1-0ubuntu1) disco; urgency=medium
* New upstream release. (LP: #1816004)
-- Timo Aaltonen Wed, 13 Mar 2019 20:05:49 +0200
** Changed in: libglvnd (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libglvnd in Ubuntu.
https://bugs.launchpad.net/bugs/1816004
Title:
GLVND: AARCH64 : Fix address passed to clear cache
Status in libglvnd package in Ubuntu:
Fix Released
Bug description:
[Impact]
A new fix has been merged to NVIDIA libglvnd repo at
https://github.com/NVIDIA/libglvnd/pull/171/commits/9948df636708e2915e5c2daa61b318e6252bc02e
We need to include it in bionic.
It would be ok to just include this fix even without updating to the latest
glvnd version.
This change fixes a crash seen in some GLX apps while calling
glXGetProcAddress.
Source Package :
https://launchpad.net/ubuntu/+source/libglvnd/1.0.0-2ubuntu2.2
Can we get this fix merged in current LTS 18.04 as "-updates"
[Test app]
To reproduce this failure: Install python-pyglet on 18.04 ubuntu.
And run a small test app with this piece of code.
void *handle = dlopen("libGLX.so.0", 2);
glXGetProcAddressARB = (GLXextFuncPtr (*)(const GLubyte*))dlsym(handle,
"glXGetProcAddressARB");
glXGetProcAddressARB("glXAllocateMemoryMESA");
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1816004/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822092] Re: FFe: Mesa 19.0.1 for disco
This bug was fixed in the package mesa - 19.0.1-1ubuntu1 --- mesa (19.0.1-1ubuntu1) disco; urgency=medium * Merge from Debian. (LP: #1822092) -- Timo Aaltonen Thu, 28 Mar 2019 15:51:31 +0200 ** Changed in: mesa (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1822092 Title: FFe: Mesa 19.0.1 for disco Status in mesa package in Ubuntu: Fix Released Bug description: Mesa 19.0.1 is a bug fix release which fixes bugs found since the 19.0.0 release. Mesa 19.0.1 implements the OpenGL 4.5 API, but the version reported by glGetString(GL_VERSION) or glGetIntegerv(GL_MAJOR_VERSION) / glGetIntegerv(GL_MINOR_VERSION) depends on the particular driver being used. Some drivers don't support all the features required in OpenGL 4.5. OpenGL 4.5 is only available if requested at context creation. Compatibility contexts may report a lower version depending on each driver. https://www.mesa3d.org/relnotes/19.0.1.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1822092/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822179] Re: Resuming from sleep breaks desktop and lock screen background in GNOME
** Tags added: disco ** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1822179 Title: Resuming from sleep breaks desktop and lock screen background in GNOME Status in xorg package in Ubuntu: New Bug description: CPU: AMD Ryzen 5 1600 MOBO: MSI B350M MORTAR GPU: NVIDIA GTX 1060 Ubuntu version: 19.04 Nvidia driver version: 418.56 The system is updated with the latest updates as today, 28 March 2019 As the title says, in Ubuntu 19.04 the GNOME lockscreen gets corrupted, and the GNOME desktop has blank background after resuming from standby/sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1822179/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822179] [NEW] Resuming from sleep breaks desktop and lock screen background in GNOME
You have been subscribed to a public bug: CPU: AMD Ryzen 5 1600 MOBO: MSI B350M MORTAR GPU: NVIDIA GTX 1060 Ubuntu version: 19.04 Nvidia driver version: 418.56 The system is updated with the latest updates as today, 28 March 2019 As the title says, in Ubuntu 19.04 the GNOME lockscreen gets corrupted, and the GNOME desktop has blank background after resuming from standby/sleep ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment disco -- Resuming from sleep breaks desktop and lock screen background in GNOME https://bugs.launchpad.net/bugs/1822179 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821505] Re: [radeon] screen cannot be turned back on after some time of inactivity
1) I believe it will work, but am currently unwilling to upgrade from the working X stack. 2) Yes, underlying bug seems to be fixed in the 7.7.1 package version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1821505 Title: [radeon] screen cannot be turned back on after some time of inactivity Status in xserver-xorg-video-ati package in Ubuntu: Fix Released Bug description: When using my AMD Radeon X1300 card, if the screen turns off due to inactivity, it cannot be woken up by moving the mouse or by hitting a key. If you type in a terminal: xset -display :0.0 dpms force off you can wake the screen normally. Typing the following in a terminal turns my screen off, and after typing this line, the screen can be woken up by moving the mouse or by hitting a key: gnome-screensaver-command -a When I restart the display manager via ssh with another computer, the screen then comes to life again and I can log back in. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Mar 24 11:11:17 2019 DistUpgraded: 2019-03-20 18:17:04,395 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] [1002:7187] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RV516 [Radeon X1300/X1550 Series] [1458:215c] InstallationDate: Installed on 2010-05-13 (3236 days ago) InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) MachineType: FUJITSU SIEMENS ESPRIMO E5720 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-143-generic root=/dev/mapper/orao-root ro rootfstype=ext4 quiet SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2019-03-20 (3 days ago) dmi.bios.date: 02/05/2009 dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd. dmi.bios.version: 6.00 R1.18.2594.A1 dmi.board.name: D2594-A1 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: S26361-D2594-A1 dmi.chassis.type: 3 dmi.chassis.vendor: FUJITSU SIEMENS dmi.modalias: dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.18.2594.A1:bd02/05/2009:svnFUJITSUSIEMENS:pnESPRIMOE5720:pvr:rvnFUJITSUSIEMENS:rnD2594-A1:rvrS26361-D2594-A1:cvnFUJITSUSIEMENS:ct3:cvr: dmi.product.name: ESPRIMO E5720 dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A 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 2:1.18.4-0ubuntu0.8 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: Sun Mar 24 11:06:06 2019 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1821505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1804804] Re: Screen rotation does not rotate all input devices and needs custom user commands (iio-sensor-proxy or libinput should probably handle this?)
Also experiencing same problem on a Dell Inspiron 3168. Seems as though what should be handled by iio-sensor-proxy is not being handled for the input part of the touchscreen. ** Also affects: iio-sensor-proxy (Ubuntu) Importance: Undecided Status: New ** Changed in: iio-sensor-proxy (Ubuntu) Status: New => Confirmed ** Also affects: libinput (Ubuntu) Importance: Undecided Status: New ** Changed in: libinput (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1804804 Title: Screen rotation does not rotate all input devices and needs custom user commands (iio-sensor-proxy or libinput should probably handle this?) Status in iio-sensor-proxy package in Ubuntu: Confirmed Status in libinput package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.10 GNOME Shell 3.30.1 Cinnamon 3.8.8 Hardware: ASUS Transformer Mini. Also confirmed problematic for Yoga Series tablet/laptop hybrids. (https://github.com/linuxmint/cinnamon-settings-daemon/issues/188) Screen rotation works fine, but tablet coords including touch screen and pen coords do not rotate with it. Gnome gets touch screen rotation correct, but not pen coords Cinnamon gets touch screen rotation and peen coords wrong User can correct using convoluted xinput commands like: xinput set-prop "ELAN22A6:00 04F3:22A6" --type=float "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1 I spoke with Mint devs who said I should file it against iio-sensor- proxy or libinput, which I assume is a better solution that asking various wm developers to fix it individually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1804804/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800465] Re: Vulkan error when using NVIDIA-Prime
In general nvidia-drm.modeset=1 is required to have Nvidia PRIME enabled, which reduces (or even removes) tearing of moving images on Optimus setups. KMS - kernel mode settings, allows kernel to control video card and in Optimus setups, among other features, this allows to synchronize graphics buffers by both graphics cards - so there are no artifacts/tearing/etc, because before displaying anything on monitor buffers are fully copied from one card to another. When modeset is disabled for Nvidia driver - buffers of both graphics cards cannot be synchronized properly so sometimes images that are displayed are only partially updated and this is visible as taring or other similar artifacts (part of the screen is filled with current frame and part of the screen is filled with previous frame). The problem is that for some reason when KMS is enabled for Nvidia driver - vulkan requires root privileges to be initialized properly. After initialization for the first time (as root), it can be used with normal user privileges. The bug is still there on Ubuntu 18.04 with newer drivers and kernel: nvidia-driver-418 linux-image-4.18.0-16-generic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1800465 Title: Vulkan error when using NVIDIA-Prime Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-prime package in Ubuntu: Confirmed Bug description: After installing Ubuntu 18.10 and the Nvidia driver + Vulkan-Utils, switching to NVIDIA and then running vulkaninfo or vulkan-cube works perfectly. But when you reboot and update, then switch to Intel, then back to Nvidia, all Vulkan programs give an "Assertion `!err' failed." Vulkaninfo: === Presentable Surfaces: = GPU id : 0 (GeForce GTX 960M) Surface type : VK_KHR_xcb_surface vulkaninfo: /build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/vulkaninfo/vulkaninfo.c:1253: AppDumpSurfaceFormats: Assertion `!err' failed. Annullato (core dump creato) Vulkancube: vulkan-cube: /build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/cube/cube.c:3416: demo_init_vk_swapchain: Assertion `!err' failed. Annullato (core dump creato) I still have not found a workaround for that, the only way to get it working again is to reinstall everything. - Install Ubuntu 18.10 - Install proprietary 390 NVIDIA drivers - Switch NVIDIA-Prime to NVIDIA - Testing the vulkan capabilities works - Updating the system then switching to intel - Reboot - Switch to nvida - Now all Vulkan programs when using NVIDIA give that error To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800465/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820514] Re: Saving a web page from Tom's Hardware forums fails
** Changed in: firefox Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1820514 Title: Saving a web page from Tom's Hardware forums fails Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: == Steps to reproduce == 1. Open https://forums.tomshardware.com/threads/what-is-the-actually-difference-between-udimm-and-dimm.1575984/ 2. Right-click and select 'Save page as'. Point the dialog to your directory of choice. == What I expect to happen == For the directory to contain a downloaded copy of the page. == What happens == There's no copy of the page in the target directory. Going to about:downloads reveals that the download has failed, without further details. == Other info == I'm reporting this from up-to-date Disco, albeit with a 4.* kernel (as gdm currently fails to start in my VirtualBox VM with 5.*) but it's equally reproducible in Bionic. Any page under https://forums.tomshardware.com/ seems to trigger this, but I have yet to come across other sites that do. Pages can even be saved from the main Tom's Hardware domain (https://www.tomshardware.com/) without issues. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: firefox 66.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8 Uname: Linux 4.19.0-9-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jani 1324 F pulseaudio BuildID: 20190315094614 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 15:37:04 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-09-30 (167 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180930) IpRoute: default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 169.254.0.0/16 dev enp0s3 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=66.0/20190315094614 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1820514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820514]
Paul_B, can you do a quick check to see if this is a regression? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1820514 Title: Saving a web page from Tom's Hardware forums fails Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: == Steps to reproduce == 1. Open https://forums.tomshardware.com/threads/what-is-the-actually-difference-between-udimm-and-dimm.1575984/ 2. Right-click and select 'Save page as'. Point the dialog to your directory of choice. == What I expect to happen == For the directory to contain a downloaded copy of the page. == What happens == There's no copy of the page in the target directory. Going to about:downloads reveals that the download has failed, without further details. == Other info == I'm reporting this from up-to-date Disco, albeit with a 4.* kernel (as gdm currently fails to start in my VirtualBox VM with 5.*) but it's equally reproducible in Bionic. Any page under https://forums.tomshardware.com/ seems to trigger this, but I have yet to come across other sites that do. Pages can even be saved from the main Tom's Hardware domain (https://www.tomshardware.com/) without issues. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: firefox 66.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8 Uname: Linux 4.19.0-9-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jani 1324 F pulseaudio BuildID: 20190315094614 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 15:37:04 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-09-30 (167 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180930) IpRoute: default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 169.254.0.0/16 dev enp0s3 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=66.0/20190315094614 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1820514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820514]
I tried running mozregression tool but I could not reach a regression range. The generated builds for bisection revealed the same issue in 09/2016 / not working build on 06/2015 and a different issue on the last build 11/2014 when the page is saved but with 0 bytes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1820514 Title: Saving a web page from Tom's Hardware forums fails Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: == Steps to reproduce == 1. Open https://forums.tomshardware.com/threads/what-is-the-actually-difference-between-udimm-and-dimm.1575984/ 2. Right-click and select 'Save page as'. Point the dialog to your directory of choice. == What I expect to happen == For the directory to contain a downloaded copy of the page. == What happens == There's no copy of the page in the target directory. Going to about:downloads reveals that the download has failed, without further details. == Other info == I'm reporting this from up-to-date Disco, albeit with a 4.* kernel (as gdm currently fails to start in my VirtualBox VM with 5.*) but it's equally reproducible in Bionic. Any page under https://forums.tomshardware.com/ seems to trigger this, but I have yet to come across other sites that do. Pages can even be saved from the main Tom's Hardware domain (https://www.tomshardware.com/) without issues. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: firefox 66.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8 Uname: Linux 4.19.0-9-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jani 1324 F pulseaudio BuildID: 20190315094614 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 15:37:04 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-09-30 (167 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180930) IpRoute: default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 169.254.0.0/16 dev enp0s3 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=66.0/20190315094614 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1820514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820514]
Saving only the HTML works, "web page, complete" doesn't. There's some issue with nsIWebBrowserPersist here. There's a
[Desktop-packages] [Bug 1820514]
Hi reporter, Thank you for taking the time to add this report. I was able to reproduce the behavior that you have described on all the latest Firefox versions across OS-es ( Windows 10, Ubuntu 18.04 and Mac OS 10.14). I'm going to add this Downloads Panel component for an advised input. If this is not the proper component, please feel free to change it to a more appropriate one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1820514 Title: Saving a web page from Tom's Hardware forums fails Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: == Steps to reproduce == 1. Open https://forums.tomshardware.com/threads/what-is-the-actually-difference-between-udimm-and-dimm.1575984/ 2. Right-click and select 'Save page as'. Point the dialog to your directory of choice. == What I expect to happen == For the directory to contain a downloaded copy of the page. == What happens == There's no copy of the page in the target directory. Going to about:downloads reveals that the download has failed, without further details. == Other info == I'm reporting this from up-to-date Disco, albeit with a 4.* kernel (as gdm currently fails to start in my VirtualBox VM with 5.*) but it's equally reproducible in Bionic. Any page under https://forums.tomshardware.com/ seems to trigger this, but I have yet to come across other sites that do. Pages can even be saved from the main Tom's Hardware domain (https://www.tomshardware.com/) without issues. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: firefox 66.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8 Uname: Linux 4.19.0-9-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jani 1324 F pulseaudio BuildID: 20190315094614 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 15:37:04 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-09-30 (167 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180930) IpRoute: default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 169.254.0.0/16 dev enp0s3 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=66.0/20190315094614 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1820514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821936] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250292/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1821936] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250291/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1821936] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250297/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1821936] Re: ALC274 unsupported
I did this yesterday per request and marked it as confirmed. I just completed this for a second time agreeing to send some data which mentioned pulse-audio, etc., to you all. It completed at 16:39 local time, Miami. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage
[Desktop-packages] [Bug 1821936] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250295/+files/RfKill.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1821936] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250296/+files/UdevDb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1821936] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250294/+files/ProcModules.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1821936] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250293/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1821936] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250290/+files/Lsusb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1821936] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250287/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1821936] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250288/+files/IwConfig.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1821936] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250289/+files/Lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1821936] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250286/+files/CRDA.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1821936] Re: ALC274 unsupported
apport information ** Tags added: apport-collected bionic ** Description changed: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.6 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: gdm1903 F pulseaudio + derek 2464 F pulseaudio + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2019-03-23 (5 days ago) + InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) + MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash + ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-4.18.0-16-generic N/A + linux-backports-modules-4.18.0-16-generic N/A + linux-firmware 1.173.3 + Tags: bionic + Uname: Linux 4.18.0-16-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 09/26/2018 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: Z272SD.300 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: Z272SD + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 13 + dmi.chassis.vendor: ASUSTeK COMPUTER INC. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: + dmi.product.family: Zen AIO + dmi.product.name: Zen AIO 27 Z272SD_Z272SD + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250285/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be
[Desktop-packages] [Bug 335662] Re: [jaunty] hplip status service cannot find system tray
Installed HPLIP 3.19.3 on Ubuntu 18.04 System Tray problem still there -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/335662 Title: [jaunty] hplip status service cannot find system tray Status in HPLIP: Fix Released Status in hplip package in Ubuntu: Fix Released Status in hplip package in Debian: Fix Released Bug description: Binary package hint: hplip After login to ubuntu hplip status service cannot find system tray. It shows dialog box: "No system tray detected on this system. Unable to start, exiting". hplip version is 2.8.12-3ubuntu1 on jaunty I found the same bug reported in Debian http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg618714.html Regards To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/335662/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1733002] Re: Google Online Account Two Factor with hardware key fails immediately
** Changed in: gnome-online-accounts (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1733002 Title: Google Online Account Two Factor with hardware key fails immediately Status in gnome-online-accounts: Unknown Status in gnome-online-accounts package in Ubuntu: Triaged Bug description: The hardware key authentication two factor fails immediately with a web based retry dialogue when connecting a Google account to the online accounts in settings using a hardware key second factor. Steps to reproduce: 1. Set Google Account to default to a hardware security key like a Yubikey or other FIDO standard key after having two factor authentication enabled on your Google Account. 2. Open Online accounts 3. Add a Google Account 4. Enter google email address 5. Enter google password 6. (this is the login flow of two factor, if default is the hardware key the error should appear). Work around: Choose use another method to authenticate: enter the authentication code and you will proceed. Expectations were: The ability to use the hardware key to authenticate as the second factor. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 17 16:01:11 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1733002/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1603430] Re: Firefox dropdowns in wrong location
I'm on ubuntu 18.10. head to Customise and uncheck the ‘Title Bar’ box at the very bottom of the settings page. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1603430 Title: Firefox dropdowns in wrong location Status in Linux Mint: New Status in cinnamon-desktop-environment package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: On Mint 17.3 Cinnamon 64bit. Steps to reproduce: * Do a fresh install. * Run mintupdate and update all packages. * Run firefox. * Start right clicking on the page to open the context menu. Resize the window and perhaps move it around the screen a couple of times. Right click some more. * Observer that, eventually, the context menu will start to appear in incorrect locations on the screen. The same also happens with the search bar, text fields and any other dropdown box. In the worst embodiment of the bug, the menu opens underneath the pointer and treats the release of the mouse button as a click, and so does things the user does not want to do. I believe the root cause is the following bug in GTK+ 3.10.8. Firefox switched over to using GTK+3 in version 46 which is when this bug appeared and has been there ever since. https://bugzilla.gnome.org/show_bug.cgi?id=758609 https://bugzilla.mozilla.org/show_bug.cgi?id=1022241 Mozilla aren't going to fix it because it's a GTK bug. GTK have already fixed it. But Mint 17.3 remains on GTK+ 3.10.8 which does not have the patch. Please roll out the patch for us 17.3 users who cannot upgrade. I can confirm that the problem is solved in Mint 18. To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1603430/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1682883] Re: Missing 2560x1440 resolution on a Dell XPS 2720 all-in-one
Bug confirmed on newer versions of Ubuntu also. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1682883 Title: Missing 2560x1440 resolution on a Dell XPS 2720 all-in-one Status in xorg package in Ubuntu: Won't Fix Bug description: The problem appeared after a distro upgrade from Ubuntu 16.10 to Ubuntu 17.04 (kernel 4.10.0-19-generic). The issue doesn't exist when booting with the previous kernel (4.8.0-46-generic). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4 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:Unity7 Date: Fri Apr 14 19:03:35 2017 DistUpgraded: 2017-04-14 16:22:07,220 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio "./xorg_fix_proprietary.py" non riuscita (No such file or directory) (8)) DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-19-generic, x86_64: installed bbswitch, 0.8, 4.8.0-46-generic, x86_64: installed nvidia-375, 375.39, 4.10.0-19-generic, x86_64: installed nvidia-375, 375.39, 4.8.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes 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:05b0] NVIDIA Corporation GK107M [GeForce GT 750M] [10de:0fe4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GK107M [GeForce GT 750M] [1028:05b0] InstallationDate: Installed on 2015-01-17 (818 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Dell Inc. XPS 2720 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=d1a29a63-27bc-4b4f-b455-9be750a1356e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago) dmi.bios.date: 11/13/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 05R2TK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 00 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd11/13/2015:svnDellInc.:pnXPS2720:pvr00:rvnDellInc.:rn05R2TK:rvrA00:cvnDellInc.:ct13:cvr00: dmi.product.name: XPS 2720 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 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.9.0-0ubuntu1 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.14-0ubuntu1 xserver.bootTime: Fri Apr 14 18:53:04 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682883/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1682883] Re: Missing 2560x1440 resolution on a Dell XPS 2720 all-in-one
The bug is still present in all subsequent versions of Ubuntu (17.10, 18.04 and 18.10). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1682883 Title: Missing 2560x1440 resolution on a Dell XPS 2720 all-in-one Status in xorg package in Ubuntu: Won't Fix Bug description: The problem appeared after a distro upgrade from Ubuntu 16.10 to Ubuntu 17.04 (kernel 4.10.0-19-generic). The issue doesn't exist when booting with the previous kernel (4.8.0-46-generic). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4 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:Unity7 Date: Fri Apr 14 19:03:35 2017 DistUpgraded: 2017-04-14 16:22:07,220 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio "./xorg_fix_proprietary.py" non riuscita (No such file or directory) (8)) DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-19-generic, x86_64: installed bbswitch, 0.8, 4.8.0-46-generic, x86_64: installed nvidia-375, 375.39, 4.10.0-19-generic, x86_64: installed nvidia-375, 375.39, 4.8.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes 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:05b0] NVIDIA Corporation GK107M [GeForce GT 750M] [10de:0fe4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GK107M [GeForce GT 750M] [1028:05b0] InstallationDate: Installed on 2015-01-17 (818 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Dell Inc. XPS 2720 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=d1a29a63-27bc-4b4f-b455-9be750a1356e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago) dmi.bios.date: 11/13/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 05R2TK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 00 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd11/13/2015:svnDellInc.:pnXPS2720:pvr00:rvnDellInc.:rn05R2TK:rvrA00:cvnDellInc.:ct13:cvr00: dmi.product.name: XPS 2720 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 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.9.0-0ubuntu1 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.14-0ubuntu1 xserver.bootTime: Fri Apr 14 18:53:04 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682883/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820323] Re: amdgpu-pro xorg crash
The uninstall and reinstall of amdgpu-pro has not worked for me. I have also tried to purge amdgpu-core and amdgpu-dmks which I was told by others got around this issue. I have not been successful thus far. Any other suggestions and or logs needed to help me find a suitable workaround until this is resolved? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1820323 Title: amdgpu-pro xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: This is on Precision 3620, Precision 5820, Precision 7820 - systems with AMD bundled for OEM fail to properly boot after update/upgrade. I believe this is related to this issue: https://www.amd.com/en/support/kb/faq/amdgpupro-ubuntu-advisory Since our image contains the amdgpu-pro package we are impacted. Canonical image is not impacted. Various systems (Precision 3420, 3620, 5820, and 7820) are having login issues with AMD GPUs after running system updates on the OEM Ubuntu image. After running sudo apt-get update && apt-get upgrade, the system will exhibit one of a few different behaviors: • Boots to a black screen • Loops at login • Boots to a screen indicating the system has been forced to low graphics mode and hard locks. I have a systems in the lab that exhibits this issue and I don’t know how to get around it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: Scanning for Btrfs filesystems UBUNTU: clean, 267691/28237824 files, 3796147/112924672 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Mar 15 13:22:36 2019 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: Dell Device [1028:06c7] Advanced Micro Devices, Inc. [AMD/ATI] Lexa XT [Radeon PRO WX 2100] [1002:6995] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b0c] InstallationDate: Installed on 2019-03-14 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision Tower 3420 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=ced18cfc-68aa-461d-a69d-d482f5880d16 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.2 dmi.board.name: 02K9CR dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.2:bd11/07/2018:svnDellInc.:pnPrecisionTower3420:pvr:rvnDellInc.:rn02K9CR:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.name: Precision Tower 3420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A 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 2:1.18.4-0ubuntu0.8 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: Fri Mar 15 13:21:28 2019 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1820323/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821264] Re: gnome-software from xps 13 9365 with Dell-oem running Ubuntu 16.04 segfaults
Is there any updates on this bug? Anything you need me to collect? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1821264 Title: gnome-software from xps 13 9365 with Dell-oem running Ubuntu 16.04 segfaults Status in gnome-software package in Ubuntu: Incomplete Bug description: installing Dell Oem. Running update/upgrade sudo -s sudo apt-get update && sudo apt-get upgrade -y Then running gnome-software results in the GUI loading but after 10 seconds it crashes and you see a segfault. I tried information in +Bug/1798236 but U16 does not have a later version of gnome-software. I also saw a bug similar that mentioned we need packagekit 1.12 but U16 doesn't bundle that only U19 does. I tried download a package for testing purposes but it does not resolve the issue. I saw another case within our Dell database that suggests appstream might cause the crash so I removed appstream and did and update/upgrade again. It stopped the crash initially but not on reboot. I also added the gnome3 repository in hopes I could get the updates that way and that did not help either. It is unclear what is needed to resolve this issue. Please let me know what logs you need me to provide to look into this further. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.5-0ubuntu0.16.04.11 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 21 19:11:27 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-rebase-20170712-0 InstallationDate: Installed on 2019-03-04 (17 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20170712-02:34 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1821264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822185] [NEW] Update to 66.0.2
Public bug reported: https://www.mozilla.org/en-US/firefox/66.0.2/releasenotes/ ** Affects: firefox (Ubuntu) Importance: Undecided Status: Fix Released ** Changed in: firefox (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1822185 Title: Update to 66.0.2 Status in firefox package in Ubuntu: Fix Released Bug description: https://www.mozilla.org/en-US/firefox/66.0.2/releasenotes/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1822185/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1813423] Re: Frequent system freezing with i915 error "*ERROR* Atomic update failure on pipe A"
> > Hello! > > I will explain what I did, I have little ability, so i made some research > to get knowledge on how I could perform the configuration of this parameter. > > I found a location with the instructions I followed: > > # sudo cat /sys/module/i915/parameters/enable_psr > > This command returned -1; > # sudo nano /etc/modprobe.d/i915.conf > > In this file I put: > options i915 enable_psr = 0; > > I saved the file; > > performed: > # sudo update-initramfs -u > > rebooted the computer; > > performed: > # sudo cat /sys/module/i915/parameters/enable_psr > > This command returned 0; > > Then I connected the HDMI cable from my LG monitor and started testing. > > I noticed a specific behavior. I had already set up the gnome-shell dock > to be displayed on all displays ... So I used the mouse pointer to fire the > quick-launch shortcuts of applications I have recorded in the gnome-shell > dock, but I made those shots from LG monitor. > > Every time I ran an application, there was a delay and a slight freezing > of the mouse pointer while the application was loading up to a fraction of > a second after the application was fully loaded. I continued to load the > various applications, always using Dock shortcuts, and the same problem > happened with several of these applications. This is a remarkable detail > because I do not remember similar behavior in linux before... In addition, > we notice a certain slowness and some truncation in the movement of the > mouse pointer (only when it is on the LG display). > > So I realized that in this system reboot, my WiFi network was not > activated (this is another uncomfortable instability that has been > happening, that is, these faults in the load of the wifi or the wired > network when we have to reboot the system). When I realized that the > network was not working I completely turned off the notebook and turned it > on again. Note that the LG monitor was connected all the time ... Then the > network started up again and I was able to do the load tests again ... > Again firing the applications through the gnome shell dock shortcuts using > the LG monitor. This time, however, at the very first shot of the > gnome-calculator, the complete interface and system freeze has already > happened, not even the caps-lock button LED works ... Neither Ctrl Alt > BkSpace ... Neither Ctrl Alt Delete ... or Ctrl Alt F "n" ... nothing. I > had to turn off the notebook on the power button. > > Again I turned off the HDMI connection and re-used only the built-in > monitor of the notebook. > > Very well ... To the point above I was ready to respond to the previous > email with the alleged result of the proposed test. Then, reading the > propose again, I realized that the proposed test was about a kernel > parameter called "enable_rc6" and not "enable_psr" as it appears in the > Arch Linux forum. Therefore, I tried to repeat the previous test using > "enable_rc6". However, the "sudo cat > /sys/module/i915/parameters/enable_rc6" command did not acknowledge the > existence of this parameter. Nor after I change the > "/etc/modprobe.d/i915.conf", run the "sudo update-initramfs -u" and restart > the notebook. Even so I went ahead with the test, reconnected the HDMI, > turned it off and turned the notebook on again and started firing the apps > like before. It was not long before a new freeze happened, more or less as > before, during application loading. I could only point out that the freeze > time after the mouse strokes is not greater than the application load time, > it is actually little lower. These small freezes are happening and > repeating themselves every time an application is triggered until a time > when a complete system freeze occurs... and noticed also the same "lazy" > behavior in the mouse pointer movement on LG display. > > After that, in another search, there was the guideline to change kermel > load parameters, not like I did, but directly editing "/etc/default/grub" > by changing the line "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" and adding > "i915.enable_psr = 0" inside the "quiet splash" quotes. Well ... First I > deleted "/etc/modprobe.d/i915.conf", so I did all the tests again using > "i915.enable_rc6 = 0" in "/etc/default/grub". However, after making this > change, and before making the tests, I ran a "sudo update-grub" commands > and then "sudo update-initramfs -u", I rebooted the notebook with the > second display connected... Again, the system was frozen in the same way as > before. > > Then I restarted the computer, edited "/etc/default/grub" again and > changed the parameter to "i915.enable_psr = 0", I ran "update-grub" and > "update-initramfs -u". I turned off the notebook, turned it on again, > tested the "sudo cat/sys/module/i915/parameters/enable_psr" by looking at > its value changed to "0" ... and restarted application load tests, as > before using the gnome-shell dock on the secondary display ... I did these > load tests for 5 to 10 minutes and
[Desktop-packages] [Bug 1821505] Re: [radeon] screen cannot be turned back on after some time of inactivity
Hark: 1) For one who is using 16.04, an upgrade for the X stack is available following instructions from https://wiki.ubuntu.com/Kernel/LTSEnablementStack . Could you please advise to the results? 2) Regarding the package xserver-xorg-video-ati, this is fixed as per https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/1821505/comments/4 . ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1821505 Title: [radeon] screen cannot be turned back on after some time of inactivity Status in xserver-xorg-video-ati package in Ubuntu: Fix Released Bug description: When using my AMD Radeon X1300 card, if the screen turns off due to inactivity, it cannot be woken up by moving the mouse or by hitting a key. If you type in a terminal: xset -display :0.0 dpms force off you can wake the screen normally. Typing the following in a terminal turns my screen off, and after typing this line, the screen can be woken up by moving the mouse or by hitting a key: gnome-screensaver-command -a When I restart the display manager via ssh with another computer, the screen then comes to life again and I can log back in. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Mar 24 11:11:17 2019 DistUpgraded: 2019-03-20 18:17:04,395 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] [1002:7187] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RV516 [Radeon X1300/X1550 Series] [1458:215c] InstallationDate: Installed on 2010-05-13 (3236 days ago) InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) MachineType: FUJITSU SIEMENS ESPRIMO E5720 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-143-generic root=/dev/mapper/orao-root ro rootfstype=ext4 quiet SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2019-03-20 (3 days ago) dmi.bios.date: 02/05/2009 dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd. dmi.bios.version: 6.00 R1.18.2594.A1 dmi.board.name: D2594-A1 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: S26361-D2594-A1 dmi.chassis.type: 3 dmi.chassis.vendor: FUJITSU SIEMENS dmi.modalias: dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.18.2594.A1:bd02/05/2009:svnFUJITSUSIEMENS:pnESPRIMOE5720:pvr:rvnFUJITSUSIEMENS:rnD2594-A1:rvrS26361-D2594-A1:cvnFUJITSUSIEMENS:ct3:cvr: dmi.product.name: ESPRIMO E5720 dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A 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 2:1.18.4-0ubuntu0.8 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: Sun Mar 24 11:06:06 2019 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1821505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822085] Re: Often the VGA screen stops working after screen saver was on
try linux-oem -1035 from bionic-proposed, it has ~50 commits backported from 5.0 to i915 driver which should help with these issues ** Description changed: I have two connected external monitors. They are connected through a Dell Dock W15. One is connected with VGA, the other with DP. Sometimes the VGA monitor complains about the resolution and will not work after the screen saver has been active (and putting the monitors to sleep). When shutting down the system, it then hangs and I have to force a shutdown with the power button. There seems to be a kernel crash before as seen in the dmesg log. + + + ProblemType: Bug + DistroRelease: Ubuntu 18.04 + Package: xorg 1:7.7+19ubuntu7.1 + ProcVersionSignature: Ubuntu 4.15.0-1034.39-oem 4.15.18 + Uname: Linux 4.15.0-1034-oem x86_64 + ApportVersion: 2.20.9-0ubuntu7.6 + Architecture: amd64 + BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log' + CompositorRunning: None + CurrentDesktop: ubuntu:GNOME + Date: Thu Mar 28 12:04:07 2019 + DistUpgraded: Fresh install + DistributionChannelDescriptor: + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31 + DistroCodename: bionic + DistroVariant: ubuntu + DkmsStatus: virtualbox, 5.2.18, 4.15.0-1034-oem, x86_64: installed + ExtraDebuggingInterest: Yes + GraphicsCard: + Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) +Subsystem: Dell Device [1028:08af] + InstallationDate: Installed on 2019-02-12 (44 days ago) + InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 + MachineType: Dell Inc. XPS 13 9380 + ProcEnviron: + LANG=sv_SE.UTF-8 + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= + PATH=(custom, no user) + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1034-oem root=UUID=0b807479-b451-4f56-b9cc-307300b68200 ro quiet splash vt.handoff=1 + SourcePackage: xorg + Symptom: display + UpgradeStatus: No upgrade log present (probably fresh install) + dmi.bios.date: 02/14/2019 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.2.1 + dmi.board.name: 0KTDY6 + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTDY6:rvrA00:cvnDellInc.:ct10:cvr: + dmi.product.family: XPS + dmi.product.name: XPS 13 9380 + dmi.sys.vendor: Dell 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 2:1.19.6-1ubuntu4.2 + 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 ** Package changed: xorg (Ubuntu) => linux-oem (Ubuntu) ** Changed in: linux-oem (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1822085 Title: Often the VGA screen stops working after screen saver was on Status in linux-oem package in Ubuntu: Incomplete Bug description: I have two connected external monitors. They are connected through a Dell Dock W15. One is connected with VGA, the other with DP. Sometimes the VGA monitor complains about the resolution and will not work after the screen saver has been active (and putting the monitors to sleep). When shutting down the system, it then hangs and I have to force a shutdown with the power button. There seems to be a kernel crash before as seen in the dmesg log. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-1034.39-oem 4.15.18 Uname: Linux 4.15.0-1034-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 28 12:04:07 2019 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-1034-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:08af] InstallationDate: Installed
[Desktop-packages] [Bug 1822047] Re: After install, cannot boot into system unless I use nomodeset kernel parameter
*** This bug is a duplicate of bug 1822026 *** https://bugs.launchpad.net/bugs/1822026 ** This bug has been marked a duplicate of bug 1822026 Live USB freezes or cannot complete install when nouveau driver is loaded -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1822047 Title: After install, cannot boot into system unless I use nomodeset kernel parameter Status in xorg package in Ubuntu: Incomplete Bug description: System: Disco (19.04 beta) Hardware: Dell Precision 7530 After installing the system, it cannot start unless manually adding `nomodeset` in the kernel command line at boot time. Steps to reproduce: 1. Install disco 19.04 beta on the device. Leave all the options at default values (i.e. do not install third party drivers) 2. Once installation is finished, restart the system (the system will freeze after install is finished, it's a known issue -> lp:1822044) Expected result: 2. The system boots and user can log in and see Gnome interface. Actual result: 2. The first time, I could log into the system. However, when I tried to access the Settings screen, the system froze. After that, everytime I tried to boot the device, the screen was filled with dark purple, a mouse cursor may appear, but nothing else would happen. At that stage, the only thing I could do was to force shutdown the device, start it again and at Grub screen, press `e` to edit the kernel parameters and add `nomodeset`. This bug is created from the actual device, using `nomodeset` kernel parameter. `nouveau` graphics driver is most likely the culprit, like in all the previous issues that have been raised (see lp:1822026, lp:1822044, lp:1821882) Two workarounds exist: 1. After installation, use `nomodeset` kernel parameter to boot into the system, then install proprietary nvidia drivers. 2. During installation, install third party drivers. If Secure Boot is enabled, this requires to set a password that will be asked when the device reboots. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 28 15:39:40 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0889] NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107GLM [Quadro P1000 Mobile] [1028:0889] InstallationDate: Installed on 2019-03-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) MachineType: Dell Inc. Precision 7530 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=e07663b1-0b3d-4cdb-aa6c-f6f2e8c4ee5d ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd02/19/2019:svnDellInc.:pnPrecision7530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7530 dmi.product.sku: 0889 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1822047/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821936] Re: ALC274 unsupported
Please run `apport-collect 1821936` to collect log. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821936/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1087582] Re: [gen3] Bad GPU performance whilst CPU is in deep sleep
** Changed in: xserver-xorg-video-intel Status: Won't Fix => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1087582 Title: [gen3] Bad GPU performance whilst CPU is in deep sleep Status in xf86-video-intel: Fix Released Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: I have an Acer AOD250(KAV60) netbook. On Ubuntu 12.10 with glxgears I get 50-60 fps, while on Lubuntu I get half that and sometimes worse. The odd thing about this is that when I start moving my mouse around it straightens up and goes back to roughly 55-60 fps, and once I stop moving the mouse, the performance drops again. I know the chipset and GPU isn't the best out there, but it shouldn't be acting like this(before, I was able to use Celestia with ease but now I get below 5 fps). Latest available BIOS(v1.29) Intel Atom N270 1.6GHz(1 core, 2 threads) 1024RAM Intel 945GMA(8MB VRAM from BIOS) Tested glxgears from mesa-utils "8.0.1+git20110129+d8f7d6b-0ubuntu2" ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic i686 ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 Date: Fri Dec 7 02:37:04 2012 InstallationDate: Installed on 2012-12-07 (0 days ago) InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1) MarkForUpload: True SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1087582/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1087582]
I got fed up with my 945gm not being capabile of 60fps glxgears. commit d938da6b132a2d6addeba4c57a67ec3c07824843 Author: Ville Syrjälä Date: Fri Mar 22 20:08:03 2019 +0200 drm/i915: Disable C3 when enabling vblank interrupts on i945gm The main difference compared to the older pm_qos attempts is that I found a way to dig out the exact c3 disable latency, so we should have a reasonable guarantee that we do disable c3 but not c2. The power cost of not using c3 seems to be about 0.7W on my machine (with the display on), so this isn't exactly cheap :( I did spend quite a bit of time at some point digging through the chipset docs (such as they are). It's been a while since I did that but I'll try to summarize what I recall; Gen3 introduced some kind of new mechanism by which the gmch can wake up the CPU. The old AGPBUSY/PM_BUSY involved the ICH as well IIRC, whereas the new mechanism supposedly does not. IIRC the new mechanism already appears in the i915gm docs, but my theory is that i945gm is where it actually got into use and either it is broken or we're missing some magic undocumented bit somewhere. I did try (blindly if necessary) poking at various registers that seemed relevant. Alas, I was unable to find a magic bit to make C3+vblank interrupts cooperate. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1087582 Title: [gen3] Bad GPU performance whilst CPU is in deep sleep Status in xf86-video-intel: Fix Released Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: I have an Acer AOD250(KAV60) netbook. On Ubuntu 12.10 with glxgears I get 50-60 fps, while on Lubuntu I get half that and sometimes worse. The odd thing about this is that when I start moving my mouse around it straightens up and goes back to roughly 55-60 fps, and once I stop moving the mouse, the performance drops again. I know the chipset and GPU isn't the best out there, but it shouldn't be acting like this(before, I was able to use Celestia with ease but now I get below 5 fps). Latest available BIOS(v1.29) Intel Atom N270 1.6GHz(1 core, 2 threads) 1024RAM Intel 945GMA(8MB VRAM from BIOS) Tested glxgears from mesa-utils "8.0.1+git20110129+d8f7d6b-0ubuntu2" ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic i686 ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 Date: Fri Dec 7 02:37:04 2012 InstallationDate: Installed on 2012-12-07 (0 days ago) InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1) MarkForUpload: True SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1087582/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822165] Re: [snap] steam:// application links don't work in chromium
Acknowledging the bug, but marking "invalid" for chromium as this would have to be fixed in snapd. Added a snapd task for that. ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1822165 Title: [snap] steam:// application links don't work in chromium Status in snapd: New Status in chromium-browser package in Ubuntu: Invalid Bug description: Example of a link: steam://connect/164.132.201.196:27119 This link is supposed to open a window or start a game in the steam application, but steam is not doing anything. It works in non-snap Chromium (tested on a new installation and a chrome prompt appeared, maybe some setting in my snap version is preventing this?). Ubuntu 18.10 Chromium Version 73.0.3683.75 (Official Build) snap (64-bit) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1822165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822165] Re: Steam application links don't work in Chromium Snap
When run from a terminal, the following message gives a clue: user-open error: Supplied URL scheme "steam" is not allowed The xdg-open wrapper in snapd white-lists known URL schemes (https://github.com/snapcore/snapd/blob/master/userd/launcher.go#L60), and "steam" is not one of them. ** Summary changed: - Steam application links don't work in Chromium Snap + [snap] steam:// application links don't work in chromium ** Tags added: snap ** Also affects: snapd Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1822165 Title: [snap] steam:// application links don't work in chromium Status in snapd: New Status in chromium-browser package in Ubuntu: Invalid Bug description: Example of a link: steam://connect/164.132.201.196:27119 This link is supposed to open a window or start a game in the steam application, but steam is not doing anything. It works in non-snap Chromium (tested on a new installation and a chrome prompt appeared, maybe some setting in my snap version is preventing this?). Ubuntu 18.10 Chromium Version 73.0.3683.75 (Official Build) snap (64-bit) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1822165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821814] Re: Todoist extension missing in Ubuntu 19.04
** Tags added: disc ** Tags removed: disc ** Tags added: disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-todo in Ubuntu. https://bugs.launchpad.net/bugs/1821814 Title: Todoist extension missing in Ubuntu 19.04 Status in gnome-todo package in Ubuntu: New Bug description: The gnome-todo package previously supported Todoist as a source, however on upgrading to 19.04 beta, the Todoist online account option is missing, and the extension for gnome-todo appears to be missing as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-todo/+bug/1821814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822092] Re: FFe: Mesa 19.0.1 for disco
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1822092 Title: FFe: Mesa 19.0.1 for disco Status in mesa package in Ubuntu: New Bug description: Mesa 19.0.1 is a bug fix release which fixes bugs found since the 19.0.0 release. Mesa 19.0.1 implements the OpenGL 4.5 API, but the version reported by glGetString(GL_VERSION) or glGetIntegerv(GL_MAJOR_VERSION) / glGetIntegerv(GL_MINOR_VERSION) depends on the particular driver being used. Some drivers don't support all the features required in OpenGL 4.5. OpenGL 4.5 is only available if requested at context creation. Compatibility contexts may report a lower version depending on each driver. https://www.mesa3d.org/relnotes/19.0.1.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1822092/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
