[Desktop-packages] [Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
Comet Lake is a gen9 gpu like Skylake etc, it only needed pci-id's to gain support. I have the upcoming desktop version ('CML-S') running without issues, and don't recall seeing issues with the mobile version either ('CML-U'). -- 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/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 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+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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/linux/+bug/1859730/+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 1860483] Re: [nouveau] screen background overlaid with scan type artifact in red
and can skip the headers too, if there are no dkms modules that need those -- 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/1860483 Title: [nouveau] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860483/+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 1860483] Re: [nouveau] screen background overlaid with scan type artifact in red
I know, this is a common question and we should do better to make it clear. You only need the non-lowlatency packages: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc7/linux- headers-5.5.0-050500rc7_5.5.0-050500rc7.202001192030_all.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc7/linux- headers-5.5.0-050500rc7-generic_5.5.0-050500rc7.202001192030_amd64.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc7/linux-image- unsigned-5.5.0-050500rc7-generic_5.5.0-050500rc7.202001192030_amd64.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc7/linux- modules-5.5.0-050500rc7-generic_5.5.0-050500rc7.202001192030_amd64.deb -- 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/1860483 Title: [nouveau] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860483/+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 1860634] Re: Gnome shell extensions disabled at every restart
It sounds like one of your extensions might be experiencing errors on startup, causing them to be disabled. Please remove them one-by-one and see if any one extension is causing the problem. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1860634 Title: Gnome shell extensions disabled at every restart Status in gnome-shell package in Ubuntu: Incomplete Bug description: same like #1813511 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 23 08:07:50 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-05 (140 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-21 (93 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860634/+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 1860634] [NEW] Gnome shell extensions disabled at every restart
Public bug reported: same like #1813511 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 23 08:07:50 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-05 (140 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-21 (93 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1860634 Title: Gnome shell extensions disabled at every restart Status in gnome-shell package in Ubuntu: New Bug description: same like #1813511 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 23 08:07:50 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-05 (140 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-21 (93 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860634/+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 1860483] Re: [nouveau] screen background overlaid with scan type artifact in red
Should I try all the amd64 packages, i.e. headers, images, and modules in both generic and low latency flavors, or is there a specific package? I've pulled down the entire amd64 set, and the headers-all as well. On 1/22/20 6:55 PM, Daniel van Vugt wrote: > Thanks. This is starting to sound like general problems with the nouveau > kernel driver, or maybe GPU memory corruption, since multiple desktop > environments are broken. > > Next please try the latest kernel packages from > https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc7/ > > ** No longer affects: mutter (Ubuntu) > -- 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/1860483 Title: [nouveau] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860483/+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 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
(I think) It makes development easier, you don't have to build it for every Ubuntu version in support, or any Linux OS, it contains specific libraries you know won't cause issues with the app. -- 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/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in chromium-browser package in Ubuntu: Triaged Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1741074/+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 1836700] Re: [regression] Subpixel font rendering doesn't work any more in shell panels/menus for Wayland sessions
** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Status: Triaged => In Progress ** Tags added: focal ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Invalid ** Tags added: visual-quality -- 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/1836700 Title: [regression] Subpixel font rendering doesn't work any more in shell panels/menus for Wayland sessions Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: In Progress Bug description: Subpixel font rendering doesn't work any more in shell panels/menus for Wayland sessions. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 Date: Tue Jul 16 14:40:03 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-05-02 (75 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501) RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1 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/1836700/+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 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
Is this the kernel that ships with the machine? 5.4.11-050411-generic Also is Mesa 19.0 expected to support Comet Lake fully? -- 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/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 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+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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/linux/+bug/1859730/+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 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
SSD or FS corruption doesn't seem to appear in the original kernel log attached to this bug. I suspect that's a new issue and not the cause of this bug, but it might be... -- 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/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 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+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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/linux/+bug/1859730/+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 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
yep, best to get it serviced -- 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/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 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+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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/linux/+bug/1859730/+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 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
Hello, 7 days ago I received the notebook and the bios was version 1.2 and automatically updated to 1.4. dell support doesn't respond yet but since I tried 3 OS (ubuntu 18, fedora 31 and ubuntu 20.04) and all three failed in the same way, it could point to a problem of Hw that can be the Ssd. I attach new photos ... ** Attachment added: "WhatsApp Image 2020-01-23 at 01.30.27(2).jpeg" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1859730/+attachment/5322278/+files/WhatsApp%20Image%202020-01-23%20at%2001.30.27%282%29.jpeg -- 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/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 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+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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/linux/+bug/1859730/+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 1563781] Re: Flickering and invisible mouse pointer after wakeup from suspend
[Expired for lightdm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lightdm (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1563781 Title: Flickering and invisible mouse pointer after wakeup from suspend Status in Light Display Manager: Incomplete Status in lightdm package in Ubuntu: Expired Bug description: Hello, I run Arch linux on a Thinkpad X230 uname -a Linux schwarzbaer 4.4.5-1-ARCH #1 SMP PREEMPT Thu Mar 10 07:38:19 CET 2016 x86_64 GNU/Linux I use xmonad and a custom .xinitrc to start my session. I run `light- locker --lock-on-suspend` there and xmonad. - When I wake up my laptop from suspend, the login screen shows up as expected. - After about 2 second, the screen flickers once and the login screen shows up again. - If I start typing a password before the flickering, the input field will be reset upon flickering. Usually I end up with my password half-typed and a wrong password notice. - After logging back into the session, there is no mouse pointer. - Going to VT1 and back to VT7 restores the pointer. Please find the lightdm and journalctl logs below. I am happy to provide more logs and info. Thanks, Dominik The lightdm log: [+14840.86s] DEBUG: Seat seat0: Creating greeter session [+14840.86s] DEBUG: Seat seat0: Creating display server of type x [+14840.86s] DEBUG: Using VT 8 [+14840.86s] DEBUG: Seat seat0: Starting local X display on VT 8 [+14840.86s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log [+14840.86s] DEBUG: DisplayServer x-1: Writing X server authority to /run/lightdm/root/:1 [+14840.86s] DEBUG: DisplayServer x-1: Launching X Server [+14840.86s] DEBUG: Launching process 16458: /usr/sbin/X :1 -seat seat0 -auth /run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch [+14840.86s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server :1 [+14841.11s] DEBUG: Seat seat0 changes active session to [+14841.36s] DEBUG: Got signal 10 from process 16458 [+14841.36s] DEBUG: DisplayServer x-1: Got signal from X server :1 [+14841.36s] DEBUG: DisplayServer x-1: Connecting to XServer :1 [+14841.36s] DEBUG: Seat seat0: Display server ready, starting session authentication [+14841.36s] DEBUG: Session pid=16473: Started with service 'lightdm-greeter', username 'lightdm' [+14841.37s] DEBUG: Session pid=16473: Authentication complete with return value 0: Success [+14841.37s] DEBUG: Seat seat0: Session authenticated, running command [+14841.37s] DEBUG: Session pid=16473: Running command /usr/sbin/lightdm-gtk-greeter [+14841.37s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm [+14841.37s] DEBUG: Session pid=16473: Logging to /var/log/lightdm/x-1-greeter.log [+14841.41s] DEBUG: Activating VT 8 [+14841.41s] DEBUG: Locking login1 session c2 [+14841.41s] DEBUG: Activating login1 session c16 [+14841.41s] DEBUG: Seat seat0 changes active session to c16 [+14841.41s] DEBUG: Session c16 is already active [+14841.58s] DEBUG: Session pid=16473: Greeter connected version=1.16.7 resettable=false [+14841.76s] DEBUG: Session pid=16473: Greeter start authentication for dominik [+14841.76s] DEBUG: Session pid=16510: Started with service 'lightdm', username 'dominik' [+14841.77s] DEBUG: Session pid=16510: Got 1 message(s) from PAM [+14841.77s] DEBUG: Session pid=16473: Prompt greeter with 1 message(s) [+14846.18s] DEBUG: Session pid=16473: Continue authentication [+14846.20s] DEBUG: Session pid=16510: Authentication complete with return value 0: Success [+14846.20s] DEBUG: Session pid=16473: Authenticate result for user dominik: Success [+14846.20s] DEBUG: Session pid=16473: User dominik authorized [+14846.20s] DEBUG: Session pid=16473: Greeter sets language en_US.utf8 [+14846.26s] DEBUG: Session pid=16473: Greeter requests session xmonad-dominik [+14846.26s] DEBUG: Seat seat0: Returning to existing user session dominik [+14846.26s] DEBUG: Unlocking login1 session c2 [+14846.26s] DEBUG: Activating VT 7 [+14846.45s] DEBUG: Seat seat0: Stopping greeter [+14846.45s] DEBUG: Session pid=16473: Sending SIGTERM [+14846.45s] DEBUG: Activating login1 session c2 [+14846.46s] DEBUG: Session pid=16510: Exited with return value 0 [+14846.46s] DEBUG: Seat seat0: Session stopped [+14846.46s] DEBUG: Seat seat0 changes active session to c2 [+14846.46s] DEBUG: Session c2 is already active [+14846.50s] DEBUG: Session pid=16473: Greeter closed communication channel [+14846.50s] DEBUG: Session pid=16473: Exited with return value 0 [+14846.50s] DEBUG: Seat seat0: Session stopped [+14846.50s] DEBUG: Seat seat0: Stopping display server, no sessions require it [+14846.50s] DEBUG: Sending signal 15 to process 16458 [+14846.51s] DEBUG: Process 16458 exited wi
[Desktop-packages] [Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
The platform has gone through extensive testing when it was certified by us, so I wonder if the hw is faulty somehow, or if there's a BIOS update available that might help? -- 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/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 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+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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/linux/+bug/1859730/+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 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
Note that the problem also occurs in all debian distros including the most recent testing (but again not fedora 29+/arch ones). I feel like if we can find the difference in how the MSCHAPV2 or etc is handled, we can solve this pesky bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: This problem is also happened on my desktop. After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no CA certificate/true username and password. I tried to solve the problem following URL link; however, it could not help me also. https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, OS: Ubuntu 18.04.1 (64-bit). root@joe-UBTPC:/root # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+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 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
I have this same issue. What's very curious though is that I can connect to my work's network with Fedora 29+ (28 didn't work) as well as Arch/Manjaro based distros but not any Ubuntu version (including most recently 19.10) I can't. Just get repeated authentication failures. It's something to do with wpa_supplicant (or downstream) rather than anything upstream like network manager. For instance using wpa_supplicant on fedora 28 to connect manually it goes through the error but in I have documented extensively what I did to try to find the problem on a reddit post ( https://www.reddit.com/r/linuxquestions/comments/b1b8jo/psa_for_people_struggling_with_wifi_on_linux_on/eitv4oh/ ) but ultimately was unsuccessful at figuring out the issue. I even tried compiling wpa_supplicant from source from the github for wpa_supplicant on Ubuntu but it didn't fix the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: This problem is also happened on my desktop. After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no CA certificate/true username and password. I tried to solve the problem following URL link; however, it could not help me also. https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, OS: Ubuntu 18.04.1 (64-bit). root@joe-UBTPC:/root # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+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 1858164] Re: libpulse-dev needs a rebuild for libpulse0-1:11.1-1ubuntu7.5 on bionic-updates
** Tags added: update-reverted -- 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/1858164 Title: libpulse-dev needs a rebuild for libpulse0-1:11.1-1ubuntu7.5 on bionic-updates Status in pulseaudio package in Ubuntu: Fix Committed Bug description: 1) The release of Ubuntu you are using: $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 2) The version of the package you are using: $ dpkg -l | grep libpulse ii libpulse-mainloop-glib0:amd64 1:11.1-1ubuntu7.5 amd64PulseAudio client libraries (glib support) ii libpulse0:amd64 1:11.1-1ubuntu7.5 amd64PulseAudio client libraries ii libpulse0:i3861:11.1-1ubuntu7.5 i386 PulseAudio client libraries ii libpulsedsp:amd64 1:11.1-1ubuntu7.5 amd64PulseAudio OSS pre-load library 3) What you expected to happen "sudo apt install libpulse-dev" should installed libpulse-dev. 4) What happened instead $ sudo apt install libpulse-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. libpulse-dev : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed Depends: libpulse-mainloop-glib0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1858164/+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 1856691] Re: libpulse-mainloop-glib0:i386 cannot be installed
** Tags added: update-reverted -- 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/1856691 Title: libpulse-mainloop-glib0:i386 cannot be installed Status in pulseaudio package in Ubuntu: Fix Committed Bug description: libpulse-mainloop-glib0:i386 cannot be installed because it needs libpulse0:i386 (= 1:11.1-1ubuntu7.4), but 1:11.1-1ubuntu7.5 is installed. I am running Linux Mint 19.2 which is using the Ubuntu bionic packages. user@computer:$ sudo apt policy libpulse-mainloop-glib0:i386 libpulse-mainloop-glib0:i386: Installiert: (keine) Installationskandidat: 1:11.1-1ubuntu7.4 Versionstabelle: 1:11.1-1ubuntu7.4 500 500 http://ubuntu.unitedcolo.de/ubuntu bionic-updates/main i386 Packages 1:11.1-1ubuntu7 500 500 http://ubuntu.unitedcolo.de/ubuntu bionic/main i386 Packages user@computer:$ sudo apt policy libpulse0:i386 libpulse0:i386: Installiert: 1:11.1-1ubuntu7.5 Installationskandidat: 1:11.1-1ubuntu7.5 Versionstabelle: *** 1:11.1-1ubuntu7.5 100 100 /var/lib/dpkg/status 1:11.1-1ubuntu7.4 500 500 http://ubuntu.unitedcolo.de/ubuntu bionic-updates/main i386 Packages 1:11.1-1ubuntu7 500 500 http://ubuntu.unitedcolo.de/ubuntu bionic/main i386 Packages user@computer:$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856691/+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 1860622] Re: Dependency error installing pulseaudio-esound-compat
It seems this is a side effect of a mistake made in the release and subsequent withdrawal of update 1:11.1-1ubuntu7.5. So it's not a bug in the code but is a problem people will encounter with Ubuntu updates... This should automatically correct itself with the re-release of 1:11.1-1ubuntu7.5. In the meantime you can manually install whichever set of packages you need from either: 1:11.1-1ubuntu7.4: https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu7.4/+build/17893827 1:11.1-1ubuntu7.5: https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu7.5/+build/18146190 ** Tags added: bionic ** Changed in: pulseaudio (Ubuntu) Status: New => Fix Committed ** Tags added: update-reverted -- 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/1860622 Title: Dependency error installing pulseaudio-esound-compat Status in pulseaudio package in Ubuntu: Fix Committed Bug description: Running: apt-get install pulseaudio-esound-compat I get the following error: The following packages have unmet dependencies: pulseaudio-esound-compat : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed Depends: pulseaudio (= 1:11.1-1ubuntu7.4) Seems like pulseaudio-esound-compat has not been updated for the latest package versions of libpulse0 and pulseaudio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1860622/+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 1860622] [NEW] Dependency error installing pulseaudio-esound-compat
Public bug reported: Running: apt-get install pulseaudio-esound-compat I get the following error: The following packages have unmet dependencies: pulseaudio-esound-compat : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed Depends: pulseaudio (= 1:11.1-1ubuntu7.4) Seems like pulseaudio-esound-compat has not been updated for the latest package versions of libpulse0 and pulseaudio. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1860622 Title: Dependency error installing pulseaudio-esound-compat Status in pulseaudio package in Ubuntu: New Bug description: Running: apt-get install pulseaudio-esound-compat I get the following error: The following packages have unmet dependencies: pulseaudio-esound-compat : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed Depends: pulseaudio (= 1:11.1-1ubuntu7.4) Seems like pulseaudio-esound-compat has not been updated for the latest package versions of libpulse0 and pulseaudio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1860622/+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 994306] Re: [7300 GS] Intermittent GUI hangs in 12.04
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/994306 Title: [7300 GS] Intermittent GUI hangs in 12.04 Status in Nouveau Xorg driver: Incomplete Status in xserver-xorg-video-nouveau package in Ubuntu: Won't Fix Bug description: I have upgraded to 12.04 two days ago and since then, the GUI has hung 4-5 times (a couple times a day basically). I'm running Gnome3 (not Unity) Here is a forum post which describes what happened and what I have done: http://askubuntu.com/questions/130803/12-04-gui-hangs I don't use much, only Eclipse, Chrome and terminal windows. Skype and Pidgeon are running as well. The hangs have happened in the middle of using Eclipse or typing into a terminal window. Prior to the upgrade (I was on 11.10) I had no similar problems. [16010.668949] [drm] nouveau :01:00.0: fail post-validate sync [16010.668953] [drm] nouveau :01:00.0: validate vram_list [16010.668970] [drm] nouveau :01:00.0: validate: -16 [16010.705778] [drm] nouveau :01:00.0: error fencing pushbuf: -16 [16659.050796] [drm] nouveau :01:00.0: Setting dpms mode 3 on vga encoder (output 0) [16897.375174] [drm] nouveau :01:00.0: Setting dpms mode 0 on vga encoder (output 0) [18430.055424] [drm] nouveau :01:00.0: fail pre-validate sync [18430.055429] [drm] nouveau :01:00.0: validate vram_list [18430.055450] [drm] nouveau :01:00.0: validate: -16 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,resize,fade,unitymtgrabhandles,scale,session,unityshell] CompositorRunning: None Date: Thu May 3 16:22:18 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: NVIDIA Corporation G71 [GeForce 7300 GS] [10de:01df] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Device [196e:034e] InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=f7005cee-4159-4061-aed9-488ac44f8679 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1004 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1004:bd01/22/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.7.8-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu35 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage no
[Desktop-packages] [Bug 1859730] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 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+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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/linux/+bug/1859730/+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 1860483] Re: [nouveau] screen background overlaid with scan type artifact in red
Thanks. This is starting to sound like general problems with the nouveau kernel driver, or maybe GPU memory corruption, since multiple desktop environments are broken. Next please try the latest kernel packages from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc7/ ** No longer affects: mutter (Ubuntu) -- 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/1860483 Title: [nouveau] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860483/+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 1860204] Re: GNOME3 notification background layer paints over notification text if mouse is moved in notification area
Thanks. It looks like broken damage tracking, maybe relating to a software cursor? Though I'm not sure why you would have a software cursor when the graphics driver is working properly. ** Tags added: nvidia ** Summary changed: - GNOME3 notification background layer paints over notification text if mouse is moved in notification area + [nvidia] GNOME3 notification background layer paints over notification text if mouse is moved in notification area ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Also affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided Status: 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/1860204 Title: [nvidia] GNOME3 notification background layer paints over notification text if mouse is moved in notification area Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-435 package in Ubuntu: New Bug description: Hello, I do not know if it is a problem of the current proprietary driver or xorg or GNOME. I tried my best to include all the info you might need. Problem: When I receive a notification in the notification centre of GNOME, it shows up in the notification bubble. If the text in the notification bubble is longer than the amount of text can be shown at once, the it needs to be opened. If I click on the bubble, it opens, but if I move my mouse pointer inside the said notification the light greyish background color of the notification area paints over the text rendering it to be unreadable. If I wait some seconds then this 'layer' disappears partly or completely. Since my VGA works fine under heavy load (GPU intensive applications and games) I guess it is a software related bug --- Release: 19.10 xorg: Installed: 1:7.7+19ubuntu12 Candidate: 1:7.7+19ubuntu12 NVIDIA Driver Version: 435.21 VGA: GTX 960 4GB ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:07:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 18 11:21:51 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GM206 [GeForce GTX 960] [1458:36c2] InstallationDate: Installed on 2020-01-17 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE 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.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
[Desktop-packages] [Bug 1832812] Re: Locking and unlocking the screen is slow and stuttery
No, that is bug 1851067. ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged -- 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/1832812 Title: Locking and unlocking the screen is slow and stuttery Status in gnome-shell package in Ubuntu: Triaged Bug description: Details in my video: https://photos.app.goo.gl/x45Razdc2d3TPqCF8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 14 10:10:38 2019 InstallationDate: Installed on 2019-06-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2019-06-13T15:35:30.513049 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832812/+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 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
** Changed in: mesa (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- 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/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 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+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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/linux/+bug/1859730/+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 1860532] Re: add rbac replicasets to apps apigroup
** Package changed: totem (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1860532 Title: add rbac replicasets to apps apigroup Status in Ubuntu: New Bug description: Brief Description - Metricbeat couldn't collect state_replicaset due to the missing RBAC role definition Severity Provide the severity of the defect. Minor -- 1. Add state_statefulset to metricbeat kubernetes deployment. 2. build new sysinv patch. 3. apply the new patch to the system. 4. install stx-monitor app. 5. lunch Kibana and notice the error message: Failed to list *v1.StatefulSet: replicasets.apps is forbidden: User "system:serviceaccount:monitor:mon-metricbeat" cannot list resource "replicasets" in API group "apps" at the cluster scope ecs.version:1.1.0 tags:beats_input_codec_plain_applied host.name:controller-1 Expected Behavior The system is able to collect state_replicaset metricset successfully. --- Intermittent System Configuration Two Node, Virtual Box Branch/Pull Time/Commit --- 2020-01-16_20-00-00 Logs --- See the output in Kibana when searching for state_replicaset Test Activity - Regression Testing, Developer Testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1860532/+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 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
KDE Connect is also affected by this. I'm wondering though, unable to find the answer online, why was the transition to snap-based chromium made? -- 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/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in chromium-browser package in Ubuntu: Triaged Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1741074/+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 1860522] Autopkgtest regression report (mesa/19.2.8-0ubuntu0~18.04.1)
All autopkgtests for the newly accepted mesa (19.2.8-0ubuntu0~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: kidentitymanagement/17.12.3-0ubuntu1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#mesa [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1860522 Title: Mesa 19.2.8 stable release Status in mesa package in Ubuntu: Invalid Status in mesa source package in Bionic: Fix Committed Status in mesa source package in Eoan: Fix Committed Bug description: [Impact] 19.10 released with mesa 19.2.1. We need the last point release of the 19.2.x series in eoan and backported for bionic. [Test case] Check on intel/radeon hw that things still work fine. [Regression potential] This is the last update of the series, all regressions should be shaken off at this point by upstream CI/community To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860522/+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 1832812] Re: Locking and unlocking the screen is slow and stuttery
Will that fix change this issue?: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/757 Other links: - https://askubuntu.com/questions/1187437/override-gnome-3s-slow-screen- lock-recovery - https://www.reddit.com/r/gnome/comments/eocpga/unnecessary_delays_recovering_from_screen_lock/ ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #757 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/757 -- 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/1832812 Title: Locking and unlocking the screen is slow and stuttery Status in gnome-shell package in Ubuntu: Confirmed Bug description: Details in my video: https://photos.app.goo.gl/x45Razdc2d3TPqCF8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 14 10:10:38 2019 InstallationDate: Installed on 2019-06-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2019-06-13T15:35:30.513049 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832812/+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 1860616] Re: package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1860616 Title: package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in cups-filters package in Ubuntu: New Bug description: Package:cups-browsed1.20.2-0ubuntu3.1 is the fault given ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cups-browsed 1.8.3-2ubuntu3.5 ProcVersionSignature: Ubuntu 4.4.0-171.200-generic 4.4.203 Uname: Linux 4.4.0-171-generic i686 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.21 Architecture: i386 CupsErrorLog: Date: Wed Jan 22 14:31:53 2020 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-08-23 (1613 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: System manufacturer P5E Papersize: letter PpdFiles: Eastman-Kodak-Company-KODAK-ESP-3200-Series-AiO: Kodak ESP 3200 Series AiO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-171-generic root=UUID=55519785-6788-462a-b70a-aecb67b96400 ro quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: cups-filters Title: package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2020-01-22 (0 days ago) dmi.bios.date: 02/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd02/19/2009:svnSystemmanufacturer:pnP5E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5E dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1860616/+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 1860616] [NEW] package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Package:cups-browsed1.20.2-0ubuntu3.1 is the fault given ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cups-browsed 1.8.3-2ubuntu3.5 ProcVersionSignature: Ubuntu 4.4.0-171.200-generic 4.4.203 Uname: Linux 4.4.0-171-generic i686 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.21 Architecture: i386 CupsErrorLog: Date: Wed Jan 22 14:31:53 2020 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-08-23 (1613 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: System manufacturer P5E Papersize: letter PpdFiles: Eastman-Kodak-Company-KODAK-ESP-3200-Series-AiO: Kodak ESP 3200 Series AiO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-171-generic root=UUID=55519785-6788-462a-b70a-aecb67b96400 ro quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: cups-filters Title: package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2020-01-22 (0 days ago) dmi.bios.date: 02/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd02/19/2009:svnSystemmanufacturer:pnP5E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5E dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: cups-filters (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package bionic i386 third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1860616 Title: package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in cups-filters package in Ubuntu: New Bug description: Package:cups-browsed1.20.2-0ubuntu3.1 is the fault given ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cups-browsed 1.8.3-2ubuntu3.5 ProcVersionSignature: Ubuntu 4.4.0-171.200-generic 4.4.203 Uname: Linux 4.4.0-171-generic i686 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.21 Architecture: i386 CupsErrorLog: Date: Wed Jan 22 14:31:53 2020 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-08-23 (1613 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: System manufacturer P5E Papersize: letter PpdFiles: Eastman-Kodak-Company-KODAK-ESP-3200-Series-AiO: Kodak ESP 3200 Series AiO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-171-generic root=UUID=55519785-6788-462a-b70a-aecb67b96400 ro quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: cups-filters Title: package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2020-01-22 (0 days ago) dmi.bios.date: 02/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd02/19/2009:svnSystemmanufacturer:pnP5E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5E dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1860616/+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 1860163] Re: By default, group the LibreOffice icons into a folder called "LibreOffice"
I was referring to the "Show Applications" screen. They are separate, instead of grouped into a folder. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1860163 Title: By default, group the LibreOffice icons into a folder called "LibreOffice" Status in libreoffice package in Ubuntu: Won't Fix Bug description: 1) Ubuntu 19.10 2) 1:6.3.2-0ubuntu2 3) By default, the LibreOffice icons should be grouped into a folder called "LibreOffice". 4) By default, the LibreOffice icons were not grouped into a folder called "LibreOffice". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1860163/+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 1857815] Re: cups-browsed assert failure: corrupted double-linked list
On Wed, Jan 22, 2020 at 3:16 AM Till Kamppeter <1857...@bugs.launchpad.net> wrote: > Now I have tried with creating a fresh VM with the daily snapshot of > Focal and tried to reproduce the crash. Both with all normal, the host > providing some remote printers for which the cups-browsed in the VM > creates local queues and also with CUPS on the host stopped so that > cups-browsed does not create queues. No crash at all. > > > > T > I'll post to say that I did have this problem in Lu 20.04 and added myself to this bug, did a regular upgrade, problem seemed to go away, but then on another log in, returned. This morning after seeing this recent post logged into Lu and no "system problem" error window showing . . . i.e., no crash-ing. Perhaps this to will change?? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1857815 Title: cups-browsed assert failure: corrupted double-linked list Status in cups-filters package in Ubuntu: New Bug description: Same bug on Focal ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: cups-browsed 1.26.0-1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AssertionMessage: corrupted double-linked list CupsErrorLog: Date: Thu Dec 26 08:18:13 2019 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2019-12-12 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191211) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0cf3:e007 Qualcomm Atheros Communications Bus 001 Device 003: ID 1bcf:2c01 Sunplus Innovation Technology Inc. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15 7000 Gaming Papersize: a4 ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=ada0b905-9f6f-4911-9311-d1930ae73b8a ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups-filters StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fa8703a73a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7fa8703a54d3 "corrupted double-linked list") at malloc.c:5332 unlink_chunk (p=p@entry=0x55c22905f000, av=0x7fa8703d8b80 ) at malloc.c:1460 _int_malloc (av=av@entry=0x7fa8703d8b80 , bytes=bytes@entry=184) at malloc.c:4041 __libc_calloc (n=, elem_size=) at malloc.c:3428 Title: cups-browsed assert failure: corrupted double-linked list UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 0P84C9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd05/17/2019:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1857815/+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 1860199] Re: OpenCL programs give error messages
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- 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/1860199 Title: OpenCL programs give error messages Status in mesa package in Ubuntu: Confirmed Bug description: OpenCL programs print ac_rtld error: !s->is_rx LLVM failed to upload shader when calling clEnqueueNDRangeKernel. lsb_release -rd displays: Description: Ubuntu 19.10 Release: 19.10 apt-cache policy mesa-opencl-icd displays: mesa-opencl-icd: Installed: 19.2.1-1ubuntu1 Candidate: 19.2.1-1ubuntu1 Version table: *** 19.2.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mesa-opencl-icd 19.2.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.427 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 23:09:17 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev e1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:82fe] LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Pavilion Desktop PC 570-p0xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed quiet splash --- SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2017 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: CNV7500FYH dmi.board.name: 82FE dmi.board.vendor: HP dmi.board.version: 11 dmi.chassis.asset.tag: CNV7500FYH dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.20:bd10/30/2017:svnHP:pnHPPavilionDesktopPC570-p0xx:pvr:rvnHP:rn82FE:rvr11:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Pavilion dmi.product.name: HP Pavilion Desktop PC 570-p0xx dmi.product.sku: Z5P18AA#ABL dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860199/+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 1860565] Re: Remove ubuntu-web-launchers from 18.04.4
Hello Jean-Baptiste, or anyone else affected, Accepted ubuntu-settings into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- settings/18.04.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-settings (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1860565 Title: Remove ubuntu-web-launchers from 18.04.4 Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-meta source package in Bionic: Fix Committed Status in ubuntu-settings source package in Bionic: Fix Committed Bug description: ubuntu-web-launchers only contains the amazon launcher and should be removed from 18.04.4 like focal. [Test Case] 1. On a freshly installed system, uninstall ubuntu-web-launchers, logout/login. 2. Boot an ISO without ubuntu-web-launchers being seeded to the live session 3. Do a default installation from an ISO without ubuntu-web-launchers being seeded 4. Customise your launcher by adding or removing some icons. Remove ubuntu-web-launchers and make sure that your custom icons are all there 5. *With the default set of launcher favourites*, update to ubuntu-settings 18.04.7 For all cases, verify that the Amazon launcher is not in the dock [Impact] None [Risk of regression] If the shell handles this removal badly on existing systems then maybe favourites wouldn't be displayed or you'd see a weird icon not found icon (test cases #4). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-web-launchers 18.04.6 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:41:43 2020 InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1860565/+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 1860483] Re: [nouveau] screen background overlaid with scan type artifact in red
I tried "Ubuntu on Wayland". Crash. Logged in. Screen loaded improperly and keyboard and mouse froze; handlers blocked and who knows what else. The screen didn't have the red artifact though; it had a cluster of diagonal black and white scan lines covering about the middle third of the screen, an incomplete population of the left hand tool bar icons I use and none of the desktop icons. The top tool bar seemed complete, but was non-functional. Tried "Unity" while I was at it, and that was a complete flop post-log-in. Blank screen, except for an oversized audio slider icon at the top right and the cursor arrow, and the cursor was frozen; once again, no handlers. On 1/22/20 8:40 AM, Paul Collinsworth wrote: > I encountered an issue after advising you that 18.04.3 works. Perhaps > it sheds some light on the problem. > > It occurred to me that perhaps there is a graphics issue and that part > of what I was seeing is contamination of the background image I was > using. So I tried to open "Settings" in order to revert to the default > image. Didn't work; that is, "Settings" doesn't work. No response. I > can click on "Settings" on either toolbar or try to access it through > "Show Applications" and no response. > > What's more, after getting no response there, other stuff is locked > out and doesn't respond. I have to reboot to get functionality back. > In getting to reboot, the shutdown process does report that anything > I've tried to open or start, after trying to reach "Settings", isn't > responding, and then it hangs. If I click on "Power down" again at > that point, it doesn't, it just puts up an image and stalls (the image > it displays is the background image I've been using, without the > toolbars and the contaminant artifact!). At that point, I've just hit > the power switch. > > I've not tried "Ubuntu on Wayland" or the test kernel package. I'll > see what happens there. I can boot into the prior Linux generic via > grub; haven't tried to pull up any apps there, but the image issue was > still there. > > > > On 1/22/20 12:43 AM, Daniel van Vugt wrote: >> OK, thanks. Assuming the bug isn't just hiding and wouldn't reappear >> later in 18.04.3 if used long enough, then this implies a fix exists >> somewhere in the HWE packages (which are the difference between 18.04 >> fully updated and 18.04.3 fully updated). >> >> The only two sets of HWE packages I can think of that affect graphics >> are Xorg and the kernel. >> >> Firstly Xorg: Does the bug occur if you log into "Ubuntu on Wayland" >> instead? >> >> Secondly the kernel: Does the bug occur if you install the latest test >> kernel packages from here?https://kernel.ubuntu.com/~kernel- >> ppa/mainline/v5.5-rc7/ Remember to run 'uname -a' to check which kernel >> is active. >> > -- 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/1860483 Title: [nouveau] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chass
[Desktop-packages] [Bug 1860565] Re: Remove ubuntu-web-launchers from 18.04.4
Hello Jean-Baptiste, or anyone else affected, Accepted ubuntu-meta into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- meta/1.417.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-meta (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1860565 Title: Remove ubuntu-web-launchers from 18.04.4 Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-meta source package in Bionic: Fix Committed Status in ubuntu-settings source package in Bionic: In Progress Bug description: ubuntu-web-launchers only contains the amazon launcher and should be removed from 18.04.4 like focal. [Test Case] 1. On a freshly installed system, uninstall ubuntu-web-launchers, logout/login. 2. Boot an ISO without ubuntu-web-launchers being seeded to the live session 3. Do a default installation from an ISO without ubuntu-web-launchers being seeded 4. Customise your launcher by adding or removing some icons. Remove ubuntu-web-launchers and make sure that your custom icons are all there 5. *With the default set of launcher favourites*, update to ubuntu-settings 18.04.7 For all cases, verify that the Amazon launcher is not in the dock [Impact] None [Risk of regression] If the shell handles this removal badly on existing systems then maybe favourites wouldn't be displayed or you'd see a weird icon not found icon (test cases #4). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-web-launchers 18.04.6 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:41:43 2020 InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1860565/+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 1860565] Re: Remove ubuntu-web-launchers from 18.04.4
** Changed in: ubuntu-settings (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1860565 Title: Remove ubuntu-web-launchers from 18.04.4 Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-meta source package in Bionic: In Progress Status in ubuntu-settings source package in Bionic: In Progress Bug description: ubuntu-web-launchers only contains the amazon launcher and should be removed from 18.04.4 like focal. [Test Case] 1. On a freshly installed system, uninstall ubuntu-web-launchers, logout/login. 2. Boot an ISO without ubuntu-web-launchers being seeded to the live session 3. Do a default installation from an ISO without ubuntu-web-launchers being seeded 4. Customise your launcher by adding or removing some icons. Remove ubuntu-web-launchers and make sure that your custom icons are all there 5. *With the default set of launcher favourites*, update to ubuntu-settings 18.04.7 For all cases, verify that the Amazon launcher is not in the dock [Impact] None [Risk of regression] If the shell handles this removal badly on existing systems then maybe favourites wouldn't be displayed or you'd see a weird icon not found icon (test cases #4). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-web-launchers 18.04.6 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:41:43 2020 InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1860565/+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 1860564] Re: 2 ports for 2 monitors, usb c port works, hdmi gives "NO SIGNAL" on monitor
** Package changed: ubuntu => lightdm (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1860564 Title: 2 ports for 2 monitors, usb c port works, hdmi gives "NO SIGNAL" on monitor Status in lightdm package in Ubuntu: New Bug description: From what I have read, this appears to be a lightdm bug. It will occasionally resolve when switching managers and rebooting, but it's inconsistent. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 09:41:13 2020 InstallationDate: Installed on 2019-01-07 (379 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1860564/+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 1860564] [NEW] 2 ports for 2 monitors, usb c port works, hdmi gives "NO SIGNAL" on monitor
You have been subscribed to a public bug: >From what I have read, this appears to be a lightdm bug. It will occasionally resolve when switching managers and rebooting, but it's inconsistent. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 09:41:13 2020 InstallationDate: Installed on 2019-01-07 (379 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 2 ports for 2 monitors, usb c port works, hdmi gives "NO SIGNAL" on monitor https://bugs.launchpad.net/bugs/1860564 You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm 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 1860522] Re: Mesa 19.2.8 stable release
Hello Timo, or anyone else affected, Accepted mesa into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/19.2.8-0ubuntu0~19.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-eoan ** Changed in: mesa (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- 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/1860522 Title: Mesa 19.2.8 stable release Status in mesa package in Ubuntu: Invalid Status in mesa source package in Bionic: Fix Committed Status in mesa source package in Eoan: Fix Committed Bug description: [Impact] 19.10 released with mesa 19.2.1. We need the last point release of the 19.2.x series in eoan and backported for bionic. [Test case] Check on intel/radeon hw that things still work fine. [Regression potential] This is the last update of the series, all regressions should be shaken off at this point by upstream CI/community To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860522/+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 1860522] Please test proposed package
Hello Timo, or anyone else affected, Accepted mesa into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/19.2.8-0ubuntu0~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1860522 Title: Mesa 19.2.8 stable release Status in mesa package in Ubuntu: Invalid Status in mesa source package in Bionic: Fix Committed Status in mesa source package in Eoan: Fix Committed Bug description: [Impact] 19.10 released with mesa 19.2.1. We need the last point release of the 19.2.x series in eoan and backported for bionic. [Test case] Check on intel/radeon hw that things still work fine. [Regression potential] This is the last update of the series, all regressions should be shaken off at this point by upstream CI/community To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860522/+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 1860483] Re: [nouveau] screen background overlaid with scan type artifact in red
I encountered an issue after advising you that 18.04.3 works. Perhaps it sheds some light on the problem. It occurred to me that perhaps there is a graphics issue and that part of what I was seeing is contamination of the background image I was using. So I tried to open "Settings" in order to revert to the default image. Didn't work; that is, "Settings" doesn't work. No response. I can click on "Settings" on either toolbar or try to access it through "Show Applications" and no response. What's more, after getting no response there, other stuff is locked out and doesn't respond. I have to reboot to get functionality back. In getting to reboot, the shutdown process does report that anything I've tried to open or start, after trying to reach "Settings", isn't responding, and then it hangs. If I click on "Power down" again at that point, it doesn't, it just puts up an image and stalls (the image it displays is the background image I've been using, without the toolbars and the contaminant artifact!). At that point, I've just hit the power switch. I've not tried "Ubuntu on Wayland" or the test kernel package. I'll see what happens there. I can boot into the prior Linux generic via grub; haven't tried to pull up any apps there, but the image issue was still there. On 1/22/20 12:43 AM, Daniel van Vugt wrote: > OK, thanks. Assuming the bug isn't just hiding and wouldn't reappear > later in 18.04.3 if used long enough, then this implies a fix exists > somewhere in the HWE packages (which are the difference between 18.04 > fully updated and 18.04.3 fully updated). > > The only two sets of HWE packages I can think of that affect graphics > are Xorg and the kernel. > > Firstly Xorg: Does the bug occur if you log into "Ubuntu on Wayland" > instead? > > Secondly the kernel: Does the bug occur if you install the latest test > kernel packages from here? https://kernel.ubuntu.com/~kernel- > ppa/mainline/v5.5-rc7/ Remember to run 'uname -a' to check which kernel > is active. > -- 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/1860483 Title: [nouveau] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 v
[Desktop-packages] [Bug 1852874] Re: Version 78.0.3904.97 (Official Build) snap (64-bit) cannot connect to internet with VPN enabled. Connects fine with VPN disabled.
I am having this same issue with release 79.0.3945.117; DNS failures on VPN, OK without; attaching log for more info. Chrome and Firefox are Ok on VPN or off. ** Attachment added: "chrome-net-export-log.json" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1852874/+attachment/5322195/+files/chrome-net-export-log.json -- 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/1852874 Title: Version 78.0.3904.97 (Official Build) snap (64-bit) cannot connect to internet with VPN enabled. Connects fine with VPN disabled. Status in chromium-browser package in Ubuntu: Incomplete Bug description: Chromium Version 78.0.3904.70 (Official Build) snap (64-bit) on Ubuntu 19.10, Intel® Core™ i7-8550U CPU @ 1.80GHz × 8, GeForce GTX 1050/PCIe/SSE2. Since my upgrade to 19.10, snap chromium will not connect when VPN is enabled. Chromium does connect when VPN is disabled. Access NetworkManager service is enabled in chromium snap. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 16 14:52:46 2019 InstallationDate: Installed on 2019-10-05 (42 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: chromium-browser UpgradeStatus: Upgraded to eoan on 2019-10-26 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1852874/+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 1860532] Re: add rbac replicasets to apps apigroup
** Description changed: Brief Description - - Need to add replicasets to metricbeat clusterroles to allow collecting state_statefulset metricset. + Metricbeat couldn't collect state_replicaset due to the missing RBAC role definition Severity Provide the severity of the defect. Minor -- - 1. Add state_statefulset to metricbeat kubernetes deployment. - 2. build new sysinv patch. - 3. apply the new patch to the system. - 4. install stx-monitor app. - 5. lunch Kibana and search for state_statefulset and notice the error message: - - Failed to list *v1.StatefulSet: replicasets.apps is forbidden: User "system:serviceaccount:monitor:mon-metricbeat" cannot list resource "replicasets" in API group "apps" at the cluster scope ecs.version:1.1.0 tags:beats_input_codec_plain_applied host.name:controller-1 + 1. Add state_statefulset to metricbeat kubernetes deployment. + 2. build new sysinv patch. + 3. apply the new patch to the system. + 4. install stx-monitor app. + 5. lunch Kibana and notice the error message: + + Failed to list *v1.StatefulSet: replicasets.apps is forbidden: User + "system:serviceaccount:monitor:mon-metricbeat" cannot list resource + "replicasets" in API group "apps" at the cluster scope ecs.version:1.1.0 + tags:beats_input_codec_plain_applied host.name:controller-1 Expected Behavior - The system is able to collect state_statefulset metricset successfully. + The system is able to collect state_replicaset metricset successfully. --- Intermittent System Configuration Two Node, Virtual Box Branch/Pull Time/Commit --- 2020-01-16_20-00-00 Logs --- - See the output in Kibana when searching for state_statefulset + See the output in Kibana when searching for state_replicaset Test Activity - Regression Testing, Developer Testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1860532 Title: add rbac replicasets to apps apigroup Status in totem package in Ubuntu: New Bug description: Brief Description - Metricbeat couldn't collect state_replicaset due to the missing RBAC role definition Severity Provide the severity of the defect. Minor -- 1. Add state_statefulset to metricbeat kubernetes deployment. 2. build new sysinv patch. 3. apply the new patch to the system. 4. install stx-monitor app. 5. lunch Kibana and notice the error message: Failed to list *v1.StatefulSet: replicasets.apps is forbidden: User "system:serviceaccount:monitor:mon-metricbeat" cannot list resource "replicasets" in API group "apps" at the cluster scope ecs.version:1.1.0 tags:beats_input_codec_plain_applied host.name:controller-1 Expected Behavior The system is able to collect state_replicaset metricset successfully. --- Intermittent System Configuration Two Node, Virtual Box Branch/Pull Time/Commit --- 2020-01-16_20-00-00 Logs --- See the output in Kibana when searching for state_replicaset Test Activity - Regression Testing, Developer Testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1860532/+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 1860565] Re: Remove ubuntu-web-launchers from 18.04.4
** Description changed: ubuntu-web-launchers only contains the amazon launcher and should be removed from 18.04.4 like focal. [Test Case] 1. On a freshly installed system, uninstall ubuntu-web-launchers, logout/login. 2. Boot an ISO without ubuntu-web-launchers being seeded to the live session 3. Do a default installation from an ISO without ubuntu-web-launchers being seeded 4. Customise your launcher by adding or removing some icons. Remove ubuntu-web-launchers and make sure that your custom icons are all there + 5. *With the default set of launcher favourites*, update to ubuntu-settings 18.04.7 For all cases, verify that the Amazon launcher is not in the dock [Impact] None [Risk of regression] If the shell handles this removal badly on existing systems then maybe favourites wouldn't be displayed or you'd see a weird icon not found icon (test cases #4). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-web-launchers 18.04.6 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:41:43 2020 InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1860565 Title: Remove ubuntu-web-launchers from 18.04.4 Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: In Progress Status in ubuntu-meta source package in Bionic: In Progress Status in ubuntu-settings source package in Bionic: In Progress Bug description: ubuntu-web-launchers only contains the amazon launcher and should be removed from 18.04.4 like focal. [Test Case] 1. On a freshly installed system, uninstall ubuntu-web-launchers, logout/login. 2. Boot an ISO without ubuntu-web-launchers being seeded to the live session 3. Do a default installation from an ISO without ubuntu-web-launchers being seeded 4. Customise your launcher by adding or removing some icons. Remove ubuntu-web-launchers and make sure that your custom icons are all there 5. *With the default set of launcher favourites*, update to ubuntu-settings 18.04.7 For all cases, verify that the Amazon launcher is not in the dock [Impact] None [Risk of regression] If the shell handles this removal badly on existing systems then maybe favourites wouldn't be displayed or you'd see a weird icon not found icon (test cases #4). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-web-launchers 18.04.6 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:41:43 2020 InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1860565/+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 1860204] Re: GNOME3 notification background layer paints over notification text if mouse is moved in notification area
Thanks for your response. Sure, it can be seen here: https://imgur.com/a/8Cnu0hl -- 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/1860204 Title: GNOME3 notification background layer paints over notification text if mouse is moved in notification area Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, I do not know if it is a problem of the current proprietary driver or xorg or GNOME. I tried my best to include all the info you might need. Problem: When I receive a notification in the notification centre of GNOME, it shows up in the notification bubble. If the text in the notification bubble is longer than the amount of text can be shown at once, the it needs to be opened. If I click on the bubble, it opens, but if I move my mouse pointer inside the said notification the light greyish background color of the notification area paints over the text rendering it to be unreadable. If I wait some seconds then this 'layer' disappears partly or completely. Since my VGA works fine under heavy load (GPU intensive applications and games) I guess it is a software related bug --- Release: 19.10 xorg: Installed: 1:7.7+19ubuntu12 Candidate: 1:7.7+19ubuntu12 NVIDIA Driver Version: 435.21 VGA: GTX 960 4GB ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:07:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 18 11:21:51 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GM206 [GeForce GTX 960] [1458:36c2] InstallationDate: Installed on 2020-01-17 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE 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.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860204/+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 1860565] Re: Remove ubuntu-web-launchers from 18.04.4
** Description changed: ubuntu-web-launchers only contains the amazon launcher and should be removed from 18.04.4 like focal. [Test Case] 1. On a freshly installed system, uninstall ubuntu-web-launchers, logout/login. - 2. Boot an ISO without ubuntu-web-launcher being seeded to the live session - 3. Do a default installation from an ISO without ubuntu-web-launcher being seeded + 2. Boot an ISO without ubuntu-web-launchers being seeded to the live session + 3. Do a default installation from an ISO without ubuntu-web-launchers being seeded + 4. Customise your launcher by adding or removing some icons. Remove ubuntu-web-launchers and make sure that your custom icons are all there - For the 3 cases, verify that the Amazon launcher is not in the dock + For all cases, verify that the Amazon launcher is not in the dock [Impact] None [Risk of regression] - None + + If the shell handles this removal badly on existing systems then maybe + favourites wouldn't be displayed or you'd see a weird icon not found + icon (test cases #4). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-web-launchers 18.04.6 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:41:43 2020 InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1860565 Title: Remove ubuntu-web-launchers from 18.04.4 Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: In Progress Status in ubuntu-meta source package in Bionic: In Progress Status in ubuntu-settings source package in Bionic: In Progress Bug description: ubuntu-web-launchers only contains the amazon launcher and should be removed from 18.04.4 like focal. [Test Case] 1. On a freshly installed system, uninstall ubuntu-web-launchers, logout/login. 2. Boot an ISO without ubuntu-web-launchers being seeded to the live session 3. Do a default installation from an ISO without ubuntu-web-launchers being seeded 4. Customise your launcher by adding or removing some icons. Remove ubuntu-web-launchers and make sure that your custom icons are all there 5. *With the default set of launcher favourites*, update to ubuntu-settings 18.04.7 For all cases, verify that the Amazon launcher is not in the dock [Impact] None [Risk of regression] If the shell handles this removal badly on existing systems then maybe favourites wouldn't be displayed or you'd see a weird icon not found icon (test cases #4). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-web-launchers 18.04.6 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:41:43 2020 InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1860565/+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 1860565] Re: Remove ubuntu-web-launchers from 18.04.4
** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu) Status: New => Fix Released ** Changed in: ubuntu-settings (Ubuntu) Status: Fix Released => In Progress ** Changed in: ubuntu-settings (Ubuntu Bionic) Status: Triaged => Fix Committed ** Changed in: ubuntu-settings (Ubuntu Bionic) Status: Fix Committed => In Progress ** Changed in: ubuntu-settings (Ubuntu) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: ubuntu-meta (Ubuntu Bionic) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: ubuntu-meta (Ubuntu) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: ubuntu-meta (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1860565 Title: Remove ubuntu-web-launchers from 18.04.4 Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: In Progress Status in ubuntu-meta source package in Bionic: In Progress Status in ubuntu-settings source package in Bionic: In Progress Bug description: ubuntu-web-launchers only contains the amazon launcher and should be removed from 18.04.4 like focal. [Test Case] 1. On a freshly installed system, uninstall ubuntu-web-launchers, logout/login. 2. Boot an ISO without ubuntu-web-launcher being seeded to the live session 3. Do a default installation from an ISO without ubuntu-web-launcher being seeded For the 3 cases, verify that the Amazon launcher is not in the dock [Impact] None [Risk of regression] None ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-web-launchers 18.04.6 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:41:43 2020 InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1860565/+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 1860565] [NEW] Remove ubuntu-web-launchers from 18.04.4
Public bug reported: ubuntu-web-launchers only contains the amazon launcher and should be removed from 18.04.4 like focal. [Test Case] 1. On a freshly installed system, uninstall ubuntu-web-launchers, logout/login. 2. Boot an ISO without ubuntu-web-launcher being seeded to the live session 3. Do a default installation from an ISO without ubuntu-web-launcher being seeded For the 3 cases, verify that the Amazon launcher is not in the dock [Impact] None [Risk of regression] None ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-web-launchers 18.04.6 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:41:43 2020 InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Assignee: Iain Lane (laney) Status: Fix Released ** Affects: ubuntu-settings (Ubuntu) Importance: High Assignee: Iain Lane (laney) Status: In Progress ** Affects: ubuntu-meta (Ubuntu Bionic) Importance: Undecided Assignee: Iain Lane (laney) Status: In Progress ** Affects: ubuntu-settings (Ubuntu Bionic) Importance: High Assignee: Iain Lane (laney) Status: In Progress ** Tags: amd64 apport-bug bionic ** Also affects: ubuntu-settings (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: ubuntu-settings (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-settings (Ubuntu) Status: New => Fix Released ** Changed in: ubuntu-settings (Ubuntu Bionic) Importance: Undecided => High ** Changed in: ubuntu-settings (Ubuntu Bionic) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: ubuntu-settings (Ubuntu Bionic) Status: New => Triaged ** Changed in: ubuntu-settings (Ubuntu Bionic) Milestone: None => ubuntu-18.04.4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1860565 Title: Remove ubuntu-web-launchers from 18.04.4 Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: In Progress Status in ubuntu-meta source package in Bionic: In Progress Status in ubuntu-settings source package in Bionic: In Progress Bug description: ubuntu-web-launchers only contains the amazon launcher and should be removed from 18.04.4 like focal. [Test Case] 1. On a freshly installed system, uninstall ubuntu-web-launchers, logout/login. 2. Boot an ISO without ubuntu-web-launcher being seeded to the live session 3. Do a default installation from an ISO without ubuntu-web-launcher being seeded For the 3 cases, verify that the Amazon launcher is not in the dock [Impact] None [Risk of regression] None ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-web-launchers 18.04.6 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:41:43 2020 InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1860565/+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 463796] Re: Alsa doesn't detect external mic
Fix was apparently released, yet for me the problem arose first when I upgraded to 19.10. I now have no access to the microphone on my headset. -- 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/463796 Title: Alsa doesn't detect external mic Status in alsa-driver package in Ubuntu: Fix Released Bug description: I have a Logitech mini-jack headset with a mic. Sound playback works, but recording does not; it only works through the computer's built-in microphone. ProblemType: Bug Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: josh 2688 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0x9240 irq 16' Mixer name : 'IDT 92HD71B7X' Components : 'HDA:111d76b2,103c3600,00100302' Controls : 35 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0x9231 irq 19' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,0010' Controls : 4 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] CheckboxSubmission: 6bacad257d07e21537e077802a955e05 CheckboxSystem: e704f33cc0866ff0f0256a33de39ea1c Date: Thu Oct 29 17:31:38 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: fglrx Package: alsa-base 1.0.20+dfsg-1ubuntu5 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: alsa-driver Uname: Linux 2.6.31-14-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/463796/+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 1779432]
LibreWriter still does not do duplex printing. Atril does. HP OfficeJet Pro 7740 USB connection Ubuntu MATE 18.04 (printing does not work at all with Ubuntu MATE 19.10 so I rolled back to 18.04). Need to steal the code from Atril to get LibreWriter printing 2-sided. Robert Pearson On Sat, Jan 11, 2020 at 12:05 PM timur <1779...@bugs.launchpad.net> wrote: > Said it's fixed: > rosgn...@gmx.ch: reporter, Works for me with Ubuntu 16.04 LTS and LO > 5.1.6.2 > i...@gwendragon.de: HP Officejet Pro 8100 on Debian 7 Wheezy: Bug 86848 > herman.via...@edpnet.be: OK for me on Mageia 6RC and LibreOffice 5.3.3.2 > > No follow up or details - please comment for current LO version: > fre...@gmail.com: LO 4.0.2.2 and a HP OJ8600+ on Ubuntu 13.04 (64bits) > mig...@almeida.at: HP Officejet 8610 - Ubuntu 12.04 + LO 4.2.6.3 - > Windows 8.1 + 4.1.04 > viktor.b...@gmail.com: Linux Mint 17.1, LO 4.2.7.2, 4.4, 3.5.6 and 3.3.4 > p.stol...@googlemail.com: LO 4.0, HP Officejet Pro 8100 > przem...@gmail.com: LO 4.1, HP DJ 4050 DN > d0m1...@gmx.net: HP ColorJet CP 1515n > tenets33...@mypacks.net: LO 5.2, HP 7740 > > Confirmed for newer LO: > r.pear...@ieee.org: Ubuntu MATE 18.10, HP OfficeJet Pro 7740. > > Useful comment, but maybe another issue for Brother: > berndheinz...@yahoo.de: Windows XP with LibreOffice 5.3.3.2 and a Brother > HL-1430 printer > > Some users wrote duplex worked for them, so this is a tricky bug. > Workaround: "You need to use the option for "Duplex" within the > printer dialogue." > Bug 83602 was from sanjay.kuma...@hp.com to report "Libreoffice sends A4 > even though A4.duplex is selected in the Libreoffice print dialog." > That seems to be the cause, as also noted in Comment 19. > Comment 17 confirmed even from 3.3.4 so not clear why this was marked > regression, unless OO 3.3 works. > There's a discussion and duplicates in Bug 39809. > > Another issue because reporter said it worked before 6.3: bug 129923 with > HP OfficeJet 8100 and Lexmark CS310DN > Due to the latest report, best to test with LO 6.2.8 and separately with > LO 6.3.4 and master 6.5+. You may get those as Appimage at > http://libreoffice.soluzioniopen.com/ > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1779432 > > Title: > [upstream] Libre Writer doesn't do duplex printing > > Status in LibreOffice: > Confirmed > Status in Ubuntu MATE: > Invalid > Status in libreoffice package in Ubuntu: > Confirmed > > Bug description: > The Libre Writer print settings are set to two side printing, but > program only prints single side. Is not HP Linux driver because both > FireFox and Chrome print both sides. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: libreoffice-core 1:6.0.3-0ubuntu1 > ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 > Uname: Linux 4.15.0-23-generic x86_64 > NonfreeKernelModules: ufsd > ApportVersion: 2.20.9-0ubuntu7.2 > Architecture: amd64 > CurrentDesktop: MATE > Date: Fri Jun 29 22:17:38 2018 > ExecutablePath: /usr/lib/libreoffice/program/soffice.bin > InstallationDate: Installed on 2018-06-15 (14 days ago) > InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > SourcePackage: libreoffice > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/df-libreoffice/+bug/1779432/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1779432 Title: [upstream] Libre Writer doesn't do duplex printing Status in LibreOffice: Confirmed Status in Ubuntu MATE: Invalid Status in libreoffice package in Ubuntu: Confirmed Bug description: The Libre Writer print settings are set to two side printing, but program only prints single side. Is not HP Linux driver because both FireFox and Chrome print both sides. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-core 1:6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: ufsd ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: MATE Date: Fri Jun 29 22:17:38 2018 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2018-06-15 (14 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1779432/+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.ne
[Desktop-packages] [Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
Dear, I have the same mistakes again with Wayland and especially with the updates. I did everything you suggested, I no longer have outdated library problems but the bugs remain the same: c -- 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/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 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+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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/linux/+bug/1859730/+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 1859963] Re: Info package on Ubuntu Focal comes preinstalled with desktop file
Maybe GNOME should just hide all Terminal=true apps in a folder called "Terminal applications" or something? Debian is adding more and more of these, and it's annoying. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texinfo in Ubuntu. https://bugs.launchpad.net/bugs/1859963 Title: Info package on Ubuntu Focal comes preinstalled with desktop file Status in One Hundred Papercuts: New Status in texinfo package in Ubuntu: New Bug description: The "info" package that is preinstalled on Ubuntu Focal ships with a "info.desktop" file that adds a "TeXInfo" desktop launcher displayed among other apps. The launcher opens a terminal application that is confusing and user unfriendly for many users. Users that actually want to use info can do it using a terminal. Please, consider removing the desktop file or at least set it to not show among other apps. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1859963/+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 1860551] Re: package chromium-browser 78.0.3904.70-0ubuntu0.19.04.4 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error ex
** Tags removed: need-duplicate-check -- 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/1860551 Title: package chromium-browser 78.0.3904.70-0ubuntu0.19.04.4 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 128 Status in chromium-browser package in Ubuntu: New Bug description: During a routine update, the installation of this package got stuck for several minutes with process pk-debconf-help taking 100% CPU. I then killed that process and run apt -f install, and it went without problem. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: chromium-browser 78.0.3904.70-0ubuntu0.19.04.4 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-2: enabled: enabled dpms: On status: connected edid-base64: AP///wAebX5YAQEBAQEVAQOAMx146l6lolVNoCYRUFQhCACzAIGAgUBxQAEBAQEBAQEBAjqAGHE4LUBYLEUA/iIRAAAe/QA4PR5TDwAKICAgICAg/ABJUFMyMzUKICAgICAg/wBTZXJpYWwgTnVtYmVyAUkCAx3xSpAEAwEUEgUfEBMjCQcHgwEAAGUDDAAQAAI6gBhxOC1AWCxFAP4iEQAAHgEdgBhxHBYgWCwlAP4iEQAAngEdAHJR0B4gbihVAP4iEQAAHowK0Iog4C0QED6WAP4iEQAAGAAA5g== modes: 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080i 1920x1080 1920x1080i 1680x1050 1280x1024 1280x960 1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-eDP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAw5KcFAAAbAQSlHxF44kQVoVJGoCkPUFQBAQEBAQEBAQEBAQEBAQEBaV4AoKCgKVAwIKUANa4QAAAaiEsAoKCgKVAwIKUANa4QAAAa/gBMRyBEaXNwbGF5CiAg/gBMUDE0MFFIMi1TUEExAHw= modes: 2560x1440 2560x1440 Date: Wed Jan 22 10:24:02 2020 Desktop-Session: 'None' 'None' 'None' Env: 'None' 'None' ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2018-12-14 (404 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Load-Avg-1min: 3.18 Load-Processes-Running-Percent: 0.1% MachineType: LENOVO 20LDCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=f3170b45-30d1-4b61-89eb-954adc8f5363 ro quiet splash mem_sleep_default=deep vt.handoff=7 Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 SourcePackage: chromium-browser Title: package chromium-browser 78.0.3904.70-0ubuntu0.19.04.4 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 128 UpgradeStatus: Upgraded to eoan on 2019-11-11 (71 days ago) dmi.bios.date: 10/30/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N25ET51W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN25ET51W(1.37):bd10/30/2019:svnLENOVO:pn20LDCTO1WW:pvrThinkPadX1Yoga3rd:rvnLENOVO:rn20LDCTO1WW:rvrNotDefined:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 3rd dmi.product.name: 20LDCTO1WW dmi.product.sku: LENOVO_MT_20LD_BU_Think_FM_ThinkPad X1 Yoga 3rd dmi.product.version: ThinkPad X1 Yoga 3rd dmi.sys.vendor: LENOVO modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1860551/+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 1860551] [NEW] package chromium-browser 78.0.3904.70-0ubuntu0.19.04.4 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error
Public bug reported: During a routine update, the installation of this package got stuck for several minutes with process pk-debconf-help taking 100% CPU. I then killed that process and run apt -f install, and it went without problem. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: chromium-browser 78.0.3904.70-0ubuntu0.19.04.4 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-2: enabled: enabled dpms: On status: connected edid-base64: AP///wAebX5YAQEBAQEVAQOAMx146l6lolVNoCYRUFQhCACzAIGAgUBxQAEBAQEBAQEBAjqAGHE4LUBYLEUA/iIRAAAe/QA4PR5TDwAKICAgICAg/ABJUFMyMzUKICAgICAg/wBTZXJpYWwgTnVtYmVyAUkCAx3xSpAEAwEUEgUfEBMjCQcHgwEAAGUDDAAQAAI6gBhxOC1AWCxFAP4iEQAAHgEdgBhxHBYgWCwlAP4iEQAAngEdAHJR0B4gbihVAP4iEQAAHowK0Iog4C0QED6WAP4iEQAAGAAA5g== modes: 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080i 1920x1080 1920x1080i 1680x1050 1280x1024 1280x960 1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-eDP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAw5KcFAAAbAQSlHxF44kQVoVJGoCkPUFQBAQEBAQEBAQEBAQEBAQEBaV4AoKCgKVAwIKUANa4QAAAaiEsAoKCgKVAwIKUANa4QAAAa/gBMRyBEaXNwbGF5CiAg/gBMUDE0MFFIMi1TUEExAHw= modes: 2560x1440 2560x1440 Date: Wed Jan 22 10:24:02 2020 Desktop-Session: 'None' 'None' 'None' Env: 'None' 'None' ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2018-12-14 (404 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Load-Avg-1min: 3.18 Load-Processes-Running-Percent: 0.1% MachineType: LENOVO 20LDCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=f3170b45-30d1-4b61-89eb-954adc8f5363 ro quiet splash mem_sleep_default=deep vt.handoff=7 Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 SourcePackage: chromium-browser Title: package chromium-browser 78.0.3904.70-0ubuntu0.19.04.4 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 128 UpgradeStatus: Upgraded to eoan on 2019-11-11 (71 days ago) dmi.bios.date: 10/30/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N25ET51W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN25ET51W(1.37):bd10/30/2019:svnLENOVO:pn20LDCTO1WW:pvrThinkPadX1Yoga3rd:rvnLENOVO:rn20LDCTO1WW:rvrNotDefined:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 3rd dmi.product.name: 20LDCTO1WW dmi.product.sku: LENOVO_MT_20LD_BU_Think_FM_ThinkPad X1 Yoga 3rd dmi.product.version: ThinkPad X1 Yoga 3rd dmi.sys.vendor: LENOVO modified.conffile..etc.default.chromium-browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- 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/1860551 Title: package chromium-browser 78.0.3904.70-0ubuntu0.19.04.4 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 128 Status in chromium-browser package in Ubuntu: New Bug description: During a routine update, the installation of this package got stuck for several minutes with process pk-debconf-help taking 100% CPU. I then killed that process and run apt -f install, and it went without problem. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: chromium-browser 78.0.3904.70-0ubuntu0.19.04.4 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-2: enabled: enabled dpms: On status: connected edid-base64: AP///wAebX5YAQEBAQEVAQOAMx146l6lolVNoCYRUFQhCACzAIGAgUBxQAEBAQEBAQEBAjqAGHE4LUBYLEUA/iIRAAAe/QA4PR5TDwAKICAgICAg/ABJUFMyMzUKICAgICAg/wBTZXJpYWwgTnVtYmVyAUkCAx3xSpAEAwEUEgUfEBMjCQcHgwEAAGUDDAAQAAI6gBhxOC1AWCxFAP4iEQAAHgEdgBhxHBYgWCwlAP4iEQAAngEdAHJR0B4
[Desktop-packages] [Bug 1860547] [NEW] cupsd high memory consumption
Public bug reported: Ubuntu version: 19.10 cups version: 2.2.12-2ubuntu1 cupsd process slowly increases memory consumption. The /var/log/cups/error_log is full of errors below: E [22/Jan/2020:11:06:17 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:19 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:20 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:21 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:22 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:24 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:25 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:26 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:28 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:29 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:30 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:32 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:33 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- 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/1860547 Title: cupsd high memory consumption Status in cups package in Ubuntu: New Bug description: Ubuntu version: 19.10 cups version: 2.2.12-2ubuntu1 cupsd process slowly increases memory consumption. The /var/log/cups/error_log is full of errors below: E [22/Jan/2020:11:06:17 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:19 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:20 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:21 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:22 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:24 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:25 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:26 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:28 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:29 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add
[Desktop-packages] [Bug 1826159] Re: gsd-print-notifications assert failure: free(): invalid pointer
** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1826159 Title: gsd-print-notifications assert failure: free(): invalid pointer Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: This problem occurs since upgrade to disco dingo. Have not seen this in earlier releases. It seems to be related to printers in the gnome settings. janw-LIFEBOOK-AH532-G21{janw}(79)% lsb_release -rd Description: Ubuntu 19.04 Release: 19.04 apt-cache policy gnome-settings-daemon gnome-settings-daemon: Installerad: 3.32.0-1ubuntu1 Kandidat:3.32.0-1ubuntu1 Versionstabell: *** 3.32.0-1ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-settings-daemon 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AssertionMessage: free(): invalid pointer CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 22:16:13 2019 ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-print-notifications InstallationDate: Installed on 2018-02-20 (427 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-print-notifications ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/tcsh Signal: 6 SourcePackage: gnome-settings-daemon StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f247b810952 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f247b80ea9b "free(): invalid pointer") at malloc.c:5352 _int_free (av=, p=, have_lock=) at malloc.c:4181 () g_list_foreach () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gsd-print-notifications assert failure: free(): invalid pointer UpgradeStatus: Upgraded to disco on 2019-04-19 (4 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo mtime.conffile..etc.apport.crashdb.conf: 2019-04-24T11:16:47.806271 separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1826159/+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 1713581] Re: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1713581 Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Bionic: Fix Released Bug description: [ Impact ] Nautilus crashes when trying to open a folder selecting a file, when another has already been selected before and the current folder didn't finish loading. [ Test case ] It's not easy to verify this without hacking the code to change the scenario, but an example could be launching quickly: nautilus /usr/bin/true & nautilus /usr/bin/false At the second command nautilus could crash. [ Regression potential ] Calling nautilus with a file argument might not select that file -- Upstream bug: https://gitlab.gnome.org/GNOME/nautilus/issues/295 Upstream MR: https://gitlab.gnome.org/GNOME/nautilus/merge_requests/277 --- https://errors.ubuntu.com/problem/ef1ce30f6325c683b207fd96a3be93eda5384054 Fixed in https://gitlab.gnome.org/GNOME/nautilus/commit/b6691821b86460bf9d4caa6391666ae506a743c5 no idea,sorry ProblemType: CrashDistroRelease: Ubuntu 17.10 Package: nautilus 1:3.25.90-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.6-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 29 00:07:44 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-08-09 (19 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170807) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=de_DE.UTF-8 SegvAnalysis: Segfault happened at: 0x7f8b19a60d27 : mov(%rdi),%rdx PC (0x7f8b19a60d27) ok source "(%rdi)" (0x0002) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading NULL VMASignal: 11SourcePackage: nautilus StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_list_copy_deep () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1713581/+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 1860042] Re: openCL application gives error after update
could you test with a newer mesa from this ppa https://launchpad.net/~ubuntu-x-swat/+archive/ubuntu/updates it's got latest bugfix release of the series, 19.2.8, and it's now pending as a distro update as well ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/1860042 Title: openCL application gives error after update Status in mesa package in Ubuntu: Incomplete Bug description: My OpenCL program was working normally until a software update. The program prints out: ac_rtld error: !s->is_rx LLVM failed to upload shader when clEnqueueNDRangeKernel is called. I've downloaded the source for mesa and traced the problem to the gallium radeon driver. The first error message is from mesa-19.2.1/src/amd/common/ac_rtld.c and the second error message is from mesa-19.2.1/src/gallium/drivers/radeonsi/si_compute.c ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libllvm9 1:9-2~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-lowlatency 4.15.18 Uname: Linux 4.15.0-74-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 14:35:15 2020 InstallationDate: Installed on 2018-04-28 (628 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mesa-opencl-icd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860042/+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 1860235] Re: totem crashed with SIGSEGV in g_mount_spec_get()
** Description changed: https://errors.ubuntu.com/problem/4ef67c07533ef05b6c12894767e604456aca3ace https://gitlab.gnome.org/GNOME/gvfs/issues/446 --- - I don't know what happened. + This happened to me when I opened nautilus and accessed my NAS through + smb. And press double click on file. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 Uname: Linux 5.4.12-050412-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 19:08:13 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (412 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7ff6dc45dd09 : mov (%rbx),%rdi PC (0x7ff6dc45dd09) ok source "(%rbx)" (0x7000600070007) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: totem StacktraceTop: g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 Title: totem crashed with SIGSEGV in g_mount_spec_get() UpgradeStatus: Upgraded to focal on 2018-12-02 (412 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Description changed: https://errors.ubuntu.com/problem/4ef67c07533ef05b6c12894767e604456aca3ace https://gitlab.gnome.org/GNOME/gvfs/issues/446 --- This happened to me when I opened nautilus and accessed my NAS through - smb. And press double click on file. + smb. And press double click on file and totem crash. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 Uname: Linux 5.4.12-050412-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 19:08:13 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (412 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7ff6dc45dd09 : mov (%rbx),%rdi PC (0x7ff6dc45dd09) ok source "(%rbx)" (0x7000600070007) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: totem StacktraceTop: g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 Title: totem crashed with SIGSEGV in g_mount_spec_get() UpgradeStatus: Upgraded to focal on 2018-12-02 (412 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1860235 Title: totem crashed with SIGSEGV in g_mount_spec_get() Status in gvfs: New Status in gvfs package in Ubuntu: Triaged Status in totem package in Ubuntu: Triaged Bug description: https://errors.ubuntu.com/problem/4ef67c07533ef05b6c12894767e604456aca3ace https://gitlab.gnome.org/GNOME/gvfs/issues/446 --- This happened to me when I opened nautilus and accessed my NAS through smb. And press double click on file and totem crash. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 Uname: Linux 5.4.12-050412-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 19:08:13 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (412 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7ff6dc45dd09 : mov (%rbx),%rdi PC (0x7ff6dc45dd09) ok source "(%rbx)" (0x7000600070007) not located in a known VMA region (needed rea
[Desktop-packages] [Bug 1860522] Re: Mesa 19.2.8 stable release
** Changed in: mesa (Ubuntu Bionic) Status: New => In Progress ** Changed in: mesa (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: mesa (Ubuntu Eoan) Status: New => In Progress ** Changed in: mesa (Ubuntu Eoan) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- 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/1860522 Title: Mesa 19.2.8 stable release Status in mesa package in Ubuntu: Invalid Status in mesa source package in Bionic: In Progress Status in mesa source package in Eoan: In Progress Bug description: [Impact] 19.10 released with mesa 19.2.1. We need the last point release of the 19.2.x series in eoan and backported for bionic. [Test case] Check on intel/radeon hw that things still work fine. [Regression potential] This is the last update of the series, all regressions should be shaken off at this point by upstream CI/community To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860522/+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 1857815] Re: cups-browsed assert failure: corrupted double-linked list
Now I have tried with creating a fresh VM with the daily snapshot of Focal and tried to reproduce the crash. Both with all normal, the host providing some remote printers for which the cups-browsed in the VM creates local queues and also with CUPS on the host stopped so that cups-browsed does not create queues. No crash at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1857815 Title: cups-browsed assert failure: corrupted double-linked list Status in cups-filters package in Ubuntu: New Bug description: Same bug on Focal ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: cups-browsed 1.26.0-1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AssertionMessage: corrupted double-linked list CupsErrorLog: Date: Thu Dec 26 08:18:13 2019 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2019-12-12 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191211) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0cf3:e007 Qualcomm Atheros Communications Bus 001 Device 003: ID 1bcf:2c01 Sunplus Innovation Technology Inc. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15 7000 Gaming Papersize: a4 ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=ada0b905-9f6f-4911-9311-d1930ae73b8a ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups-filters StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fa8703a73a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7fa8703a54d3 "corrupted double-linked list") at malloc.c:5332 unlink_chunk (p=p@entry=0x55c22905f000, av=0x7fa8703d8b80 ) at malloc.c:1460 _int_malloc (av=av@entry=0x7fa8703d8b80 , bytes=bytes@entry=184) at malloc.c:4041 __libc_calloc (n=, elem_size=) at malloc.c:3428 Title: cups-browsed assert failure: corrupted double-linked list UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 0P84C9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd05/17/2019:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1857815/+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 1310831] Re: scrolling unfocus libreoffice calc window, contents are not refreshed properly
You are most welcome, Marcus. Thank you for your kind attention. On 22/01/20 15.39, Marcus Tomlinson wrote: > Excellent, thanks for the update Tora. > > ** Changed in: libreoffice (Ubuntu) > Status: Incomplete => Fix Released > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1310831 Title: scrolling unfocus libreoffice calc window, contents are not refreshed properly Status in libreoffice package in Ubuntu: Fix Released Bug description: Ubuntu 14.04 64 bit, Asus i3, LibreOffice Calc 4.2.3.3, 21 April 2014: Open LibreOffice Calc side by side. Pleasantly surprised, in Ubuntu 14.04 we can scroll the content of unfocused Calc window without first clicking it focus, just hover the cursor over it and scross the mouse scroller. However the content of the scrolled window IS NOT PROPERLY REFRESHED. Content scroll, but two or tree lines of all content are still showing, hence we have repeating contents in the unfocused windows. It takes clicking the unfocused window to focus, scroll the window slide scroller, than the content will refresh properly again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1310831/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
This may come as a big problem in a business environment: frequently conference calls need affordable audio, in and out. We found many great devices at low cost, but with this Ubuntu problem, they become unusable. Please, give higher rate to this issue, if possible. -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838151/+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 1765832] Re: Two finger scrolling not working after suspend
*** This bug is a duplicate of bug 1722478 *** https://bugs.launchpad.net/bugs/1722478 I have the same issue on 18.04.3 on x1 carbon gen 5th the below solves it too: $ sudo modprobe -r psmouse $ sudo modprobe psmouse -- 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/1765832 Title: Two finger scrolling not working after suspend Status in xorg package in Ubuntu: Confirmed Bug description: When waking up my laptop, two finger scrolling is not working anymore. Running: $ modprobe -r psmouse $ modprobe psmouse restores the functionality. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 20 08:23:33 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2227] InstallationDate: Installed on 2018-04-10 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) MachineType: LENOVO 20BTS09800 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET26W (1.04 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BTS09800 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET26W(1.04):bd01/23/2015:svnLENOVO:pn20BTS09800:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS09800:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BTS09800 dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO 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.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1765832/+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 1860532] [NEW] add rbac replicasets to apps apigroup
Public bug reported: Brief Description - Need to add replicasets to metricbeat clusterroles to allow collecting state_statefulset metricset. Severity Provide the severity of the defect. Minor -- 1. Add state_statefulset to metricbeat kubernetes deployment. 2. build new sysinv patch. 3. apply the new patch to the system. 4. install stx-monitor app. 5. lunch Kibana and search for state_statefulset and notice the error message: Failed to list *v1.StatefulSet: replicasets.apps is forbidden: User "system:serviceaccount:monitor:mon-metricbeat" cannot list resource "replicasets" in API group "apps" at the cluster scope ecs.version:1.1.0 tags:beats_input_codec_plain_applied host.name:controller-1 Expected Behavior The system is able to collect state_statefulset metricset successfully. --- Intermittent System Configuration Two Node, Virtual Box Branch/Pull Time/Commit --- 2020-01-16_20-00-00 Logs --- See the output in Kibana when searching for state_statefulset Test Activity - Regression Testing, Developer Testing ** Affects: totem (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1860532 Title: add rbac replicasets to apps apigroup Status in totem package in Ubuntu: New Bug description: Brief Description - Need to add replicasets to metricbeat clusterroles to allow collecting state_statefulset metricset. Severity Provide the severity of the defect. Minor -- 1. Add state_statefulset to metricbeat kubernetes deployment. 2. build new sysinv patch. 3. apply the new patch to the system. 4. install stx-monitor app. 5. lunch Kibana and search for state_statefulset and notice the error message: Failed to list *v1.StatefulSet: replicasets.apps is forbidden: User "system:serviceaccount:monitor:mon-metricbeat" cannot list resource "replicasets" in API group "apps" at the cluster scope ecs.version:1.1.0 tags:beats_input_codec_plain_applied host.name:controller-1 Expected Behavior The system is able to collect state_statefulset metricset successfully. --- Intermittent System Configuration Two Node, Virtual Box Branch/Pull Time/Commit --- 2020-01-16_20-00-00 Logs --- See the output in Kibana when searching for state_statefulset Test Activity - Regression Testing, Developer Testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1860532/+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 1860099] Re: [nouveau] Xorg freeze randomly
After updating BIOS it seems to work properly now. Updated my motherboard GA-AB350N-Gaming WIFI with BIOS version F22 to F50a. Will update if issue still persist. -- 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/1860099 Title: [nouveau] Xorg freeze randomly Status in xorg-server package in Ubuntu: Incomplete Bug description: I've had issues with ubuntu for a couple of days now where the system suddenly freezes. I've tried to use the command ALT + Sys Req + REISUB with no feedback. The only way (to my knowledge) to get it back is to to a hard reboot. The freezes can occur when using PhpStorm (when indexing I get it to freeze every time) and/or just randomly when browsing, using terminal or other programs. If you require more logs I can be helpful providing these. Thanks! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 10:43:55 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB] [19da:1438] InstallationDate: Installed on 2019-06-05 (226 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=9ac23602-df5d-4612-89a8-5b1cfef4b5bd ro quiet splash crashkernel=512M-:192M vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22 dmi.board.asset.tag: Default string dmi.board.name: AB350N-Gaming WIFI-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.:bvrF22:bd03/15/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350N-Gaming WIFI 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.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1860099/+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 1792085] Re: MTP not working/very slow on Bionic
I use ubuntu 19.10 and a lg d855. The version of libmtp is 1.1.16-2. Transfers do not work on USB3 but work on USB2 (My motherboard has both types of USB ports). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1792085 Title: MTP not working/very slow on Bionic Status in libmtp: New Status in gvfs package in Ubuntu: Incomplete Bug description: Hi, unfortunately (for me) MTP android devices no more work on Ubuntu 18.04. I have used MTP on 16.04 without problems, but on 18.04 it does not work. When I connect my Android devices (Samsung A5 and Samsung J3) and I try to list directories with many files (e.g. /DCIM/Camera) the window hangs until I disconnect the device. Same issue if I try to post the command "ls /var/run/1000/gvfs/". I have installed Ubuntu 18.04 on two different machines - an older HP laptop and a recent DELL laptop - and the issue is present on the all of them. I suspect a defect on the "libmtp". I tried many alternative solutions suggested by the net (e.g. jmtpfs and so on) but anyone worked. That's all! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-fuse 1.36.1-0ubuntu1.1 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 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 06:20:07 2018 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libmtp/+bug/1792085/+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 1850088] Re: permission denied when opening a mounted folder in save file dialog
Ok, I have found a fix: snap connect chromium:removable-media -- 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/1850088 Title: permission denied when opening a mounted folder in save file dialog Status in Chromium Browser: New Status in chromium-browser package in Ubuntu: Incomplete Bug description: After upgrading to Ubuntu 19.10, when I tried to open a file into a sshfs-mounted folder inside my home folder, it says permission denied. This didn't happen at Ubuntu 19.04. Steps to reproduce: 1. Use sshfs to mount a sftp folder on an empty folder inside my home drive (e.g. ~/.server) 2. Create a soft link in the home folder to a folder inside the mounted sftp file system (e.g. ~/server > .server/home/michael ) 3. Open chromium 4. Download a file 5. Enter that folder in the file dialog Expected result: I can enter the folder Actual result: It says permission denied ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE DRM.card1-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card1-VGA-1: enabled: enabled dpms: On status: connected edid-base64: AP///wBBDGbAJEYAAA8WAQNuMx14LspFpFZLnCUSUFS9SwDRwLMAlQCBgJUPAQEBAQEBAjqAGHE4LUBYLEUA/R4RAAAe/wBVSEIxMjE1MDE3OTU2/ABQaGlsaXBzIDIzNENM/QA4TB5TEQAKICAgICAgAHs= modes: 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 800x600 800x600 640x480 640x480 640x480 640x480 720x400 Date: Mon Oct 28 10:14:27 2019 DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/vg0-root ext4 230G 190G 29G 87% / tmpfstmpfs 7.8G 165M 7.6G 3% /dev/shm /dev/mapper/vg0-root ext4 230G 190G 29G 87% / InstallationDate: Installed on 2016-10-03 (1119 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=/dev/mapper/vg0-root ro quiet splash resume=/dev/vg0/swap vt.handoff=7 Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.70 (edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800}) Snap.ChromiumVersion: Chromium 78.0.3904.70 snap SourcePackage: chromium-browser UpgradeStatus: Upgraded to eoan on 2019-10-25 (2 days ago) dmi.bios.date: 08/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2105 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2105:bd08/13/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1850088/+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 1856516] Re: Excessive memory usage by gnome-shell in 19.10
** 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/1856516 Title: Excessive memory usage by gnome-shell in 19.10 Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Incomplete Bug description: The gnome-shell process on my system is currently at 5473M VIRT 1224M RSS 566M SHR; this seems a bit excessive. This session has been up for >4 days with a number of suspend/resume cycles in there, so this might be a slow leak? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic 5.3.10 Uname: Linux 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 16 16:50:10 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-29 (109 days ago) InstallationMedia: Ubuntu 19.10 bcachefs (20190828) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/usr/bin/fish XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 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/1856516/+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 1850088] Re: permission denied when opening a mounted folder in save file dialog
I have the same bug - When I want to open a file in /media/user/folder, Chromium refuses. "Permission denied" ** Also affects: chromium-browser 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/1850088 Title: permission denied when opening a mounted folder in save file dialog Status in Chromium Browser: New Status in chromium-browser package in Ubuntu: Incomplete Bug description: After upgrading to Ubuntu 19.10, when I tried to open a file into a sshfs-mounted folder inside my home folder, it says permission denied. This didn't happen at Ubuntu 19.04. Steps to reproduce: 1. Use sshfs to mount a sftp folder on an empty folder inside my home drive (e.g. ~/.server) 2. Create a soft link in the home folder to a folder inside the mounted sftp file system (e.g. ~/server > .server/home/michael ) 3. Open chromium 4. Download a file 5. Enter that folder in the file dialog Expected result: I can enter the folder Actual result: It says permission denied ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE DRM.card1-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card1-VGA-1: enabled: enabled dpms: On status: connected edid-base64: AP///wBBDGbAJEYAAA8WAQNuMx14LspFpFZLnCUSUFS9SwDRwLMAlQCBgJUPAQEBAQEBAjqAGHE4LUBYLEUA/R4RAAAe/wBVSEIxMjE1MDE3OTU2/ABQaGlsaXBzIDIzNENM/QA4TB5TEQAKICAgICAgAHs= modes: 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 800x600 800x600 640x480 640x480 640x480 640x480 720x400 Date: Mon Oct 28 10:14:27 2019 DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/vg0-root ext4 230G 190G 29G 87% / tmpfstmpfs 7.8G 165M 7.6G 3% /dev/shm /dev/mapper/vg0-root ext4 230G 190G 29G 87% / InstallationDate: Installed on 2016-10-03 (1119 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=/dev/mapper/vg0-root ro quiet splash resume=/dev/vg0/swap vt.handoff=7 Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.70 (edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800}) Snap.ChromiumVersion: Chromium 78.0.3904.70 snap SourcePackage: chromium-browser UpgradeStatus: Upgraded to eoan on 2019-10-25 (2 days ago) dmi.bios.date: 08/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2105 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2105:bd08/13/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1850088/+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 1860522] [NEW] Mesa 19.2.8 stable release
Public bug reported: [Impact] 19.10 released with mesa 19.2.1. We need the last point release of the 19.2.x series in eoan and backported for bionic. [Test case] Check on intel/radeon hw that things still work fine. [Regression potential] This is the last update of the series, all regressions should be shaken off at this point by upstream CI/community ** Affects: mesa (Ubuntu) Importance: Undecided Status: Invalid ** Affects: mesa (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: mesa (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Invalid -- 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/1860522 Title: Mesa 19.2.8 stable release Status in mesa package in Ubuntu: Invalid Status in mesa source package in Bionic: New Status in mesa source package in Eoan: New Bug description: [Impact] 19.10 released with mesa 19.2.1. We need the last point release of the 19.2.x series in eoan and backported for bionic. [Test case] Check on intel/radeon hw that things still work fine. [Regression potential] This is the last update of the series, all regressions should be shaken off at this point by upstream CI/community To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860522/+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 1856516] Re: Excessive memory usage by gnome-shell in 19.10
Vague bugs like gnome-shell#2061 are probably too risky to link to. There's a reasonable chance the reporter of that bug is experiencing a different leak to the reporter of this bug. Especially when the test case to reliably reproduce the leak is not yet agreed on. -- 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/1856516 Title: Excessive memory usage by gnome-shell in 19.10 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: The gnome-shell process on my system is currently at 5473M VIRT 1224M RSS 566M SHR; this seems a bit excessive. This session has been up for >4 days with a number of suspend/resume cycles in there, so this might be a slow leak? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic 5.3.10 Uname: Linux 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 16 16:50:10 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-29 (109 days ago) InstallationMedia: Ubuntu 19.10 bcachefs (20190828) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/usr/bin/fish XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 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/1856516/+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 1856516] Re: Excessive memory usage by gnome-shell in 19.10
That said, if we do link to that upstream bug then at least we will get notifications and avoid duplicate LP bugs linking to it... ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/2061 Importance: Unknown Status: Unknown -- 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/1856516 Title: Excessive memory usage by gnome-shell in 19.10 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: The gnome-shell process on my system is currently at 5473M VIRT 1224M RSS 566M SHR; this seems a bit excessive. This session has been up for >4 days with a number of suspend/resume cycles in there, so this might be a slow leak? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic 5.3.10 Uname: Linux 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 16 16:50:10 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-29 (109 days ago) InstallationMedia: Ubuntu 19.10 bcachefs (20190828) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/usr/bin/fish XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 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/1856516/+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 1310831] Re: scrolling unfocus libreoffice calc window, contents are not refreshed properly
Excellent, thanks for the update Tora. ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1310831 Title: scrolling unfocus libreoffice calc window, contents are not refreshed properly Status in libreoffice package in Ubuntu: Fix Released Bug description: Ubuntu 14.04 64 bit, Asus i3, LibreOffice Calc 4.2.3.3, 21 April 2014: Open LibreOffice Calc side by side. Pleasantly surprised, in Ubuntu 14.04 we can scroll the content of unfocused Calc window without first clicking it focus, just hover the cursor over it and scross the mouse scroller. However the content of the scrolled window IS NOT PROPERLY REFRESHED. Content scroll, but two or tree lines of all content are still showing, hence we have repeating contents in the unfocused windows. It takes clicking the unfocused window to focus, scroll the window slide scroller, than the content will refresh properly again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1310831/+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 1860516] [NEW] Cannot login to microsoft office365 account with 2fa enabled
Public bug reported: I have just enabled 2fa via time based codes on my office365 account. Now, when I try to relogin to the account again via settings > Online Accounts > Add Microsoft Exchange, I get an error, and I am never asked to input my time based code from my authenticator app. > Error connecting to Microsoft Exchange server: > Code: 456 -- Unexpected response from server Perhaps there should be an external login window, just like google login, to get 2fa working? ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New -- 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/1860516 Title: Cannot login to microsoft office365 account with 2fa enabled Status in gnome-online-accounts package in Ubuntu: New Bug description: I have just enabled 2fa via time based codes on my office365 account. Now, when I try to relogin to the account again via settings > Online Accounts > Add Microsoft Exchange, I get an error, and I am never asked to input my time based code from my authenticator app. > Error connecting to Microsoft Exchange server: > Code: 456 -- Unexpected response from server Perhaps there should be an external login window, just like google login, to get 2fa working? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1860516/+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 1856516] Re: Excessive memory usage by gnome-shell in 19.10
Maybe the same as https://gitlab.gnome.org/GNOME/gnome-shell/issues/2061 ? Although that has no more useful information than here. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2061 https://gitlab.gnome.org/GNOME/gnome-shell/issues/2061 -- 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/1856516 Title: Excessive memory usage by gnome-shell in 19.10 Status in gnome-shell package in Ubuntu: Incomplete Bug description: The gnome-shell process on my system is currently at 5473M VIRT 1224M RSS 566M SHR; this seems a bit excessive. This session has been up for >4 days with a number of suspend/resume cycles in there, so this might be a slow leak? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic 5.3.10 Uname: Linux 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 16 16:50:10 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-29 (109 days ago) InstallationMedia: Ubuntu 19.10 bcachefs (20190828) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/usr/bin/fish XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 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/1856516/+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 1856516] Re: Excessive memory usage by gnome-shell in 19.10
So, for reference: things which *don't* seem to (immediately) increase memory useage: *) Powering up the discrete GPU *) Super-A / Super *) Locking/unlocking the session. -- 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/1856516 Title: Excessive memory usage by gnome-shell in 19.10 Status in gnome-shell package in Ubuntu: Incomplete Bug description: The gnome-shell process on my system is currently at 5473M VIRT 1224M RSS 566M SHR; this seems a bit excessive. This session has been up for >4 days with a number of suspend/resume cycles in there, so this might be a slow leak? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic 5.3.10 Uname: Linux 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 16 16:50:10 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-29 (109 days ago) InstallationMedia: Ubuntu 19.10 bcachefs (20190828) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/usr/bin/fish XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 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/1856516/+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 1310831] Re: scrolling unfocus libreoffice calc window, contents are not refreshed properly
It is no more an issue. Thank you. On 21/01/20 18.23, Marcus Tomlinson wrote: > I'm setting this bug to Incomplete as it's not seen any activity since > the official release of Ubuntu 16.04 LTS. If this is still an issue on a > maintained version of Ubuntu please let us know. > > ** Changed in: libreoffice (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1310831 Title: scrolling unfocus libreoffice calc window, contents are not refreshed properly Status in libreoffice package in Ubuntu: Incomplete Bug description: Ubuntu 14.04 64 bit, Asus i3, LibreOffice Calc 4.2.3.3, 21 April 2014: Open LibreOffice Calc side by side. Pleasantly surprised, in Ubuntu 14.04 we can scroll the content of unfocused Calc window without first clicking it focus, just hover the cursor over it and scross the mouse scroller. However the content of the scrolled window IS NOT PROPERLY REFRESHED. Content scroll, but two or tree lines of all content are still showing, hence we have repeating contents in the unfocused windows. It takes clicking the unfocused window to focus, scroll the window slide scroller, than the content will refresh properly again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1310831/+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