Re: [Desktop-packages] [Bug 1878105] Re: Xorg crash
Hello, Bellow is link to the reproduced crash: https://errors.ubuntu.com/oops/8d27672b-9413-11ea-a435-fa163e6cac46 On 12-05-2020 05:41, Daniel van Vugt wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. It sounds like some part of the system has crashed. To > help us find the cause of the crash please follow these steps: > > 1. Look in /var/crash for crash files and if found run: > ubuntu-bug YOURFILE.crash > Then tell us the ID of the newly-created bug. > > 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where > ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. > Do you find any links to recent problems on that page? If so then please > send the links to us. > > 3. If step 2 also failed then apply the workaround from bug 994921, > reboot, reproduce the crash, and retry step 1. > > Please take care to avoid attaching .crash files to bugs as we are > unable to process them as file attachments. It would also be a security > risk for yourself. > > ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) > > ** Changed in: xorg-server (Ubuntu) > Status: New => Incomplete > -- 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/1878105 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: Crash is caused when visiting websites that attempt to customize the cursor layout. (Tested with Firefox 76.0 (64-bit)) The website on which the crash first occurred was the following: https://www.yellibeanz.com/ the crash is triggered after moving the cursor around. To test the hypothesis of the cursor causing the bug I also tested the following website with identical outcome: http://www.flockofsiegel.tv/ I am sure that one can find more examples here: https://onextrapixel.com/10-websites-that-replace-mouse-cursors-for-a -better-cause/ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 11 23:58:41 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Mobile) [1043:1fc0] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1fc0] InstallationDate: Installed on 2020-05-03 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 13d3:56a2 IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X580GD_N580GD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=04dedfb2-c5a9-4447-af72-16999d76fce2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X580GD.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X580GD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag
Re: [Desktop-packages] [Bug 1877565] Re: при подключении к роутеру Keenetic iii набираю smb://keenetic/ появляется папка (диск Usbi) связь разрывается. при подключении ftp://192.168.1.1/ всё открывает
-- 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/1877565 Title: при подключении к роутеру Keenetic iii набираю smb://keenetic/ появляется папка (диск Usbi) связь разрывается. при подключении ftp://192.168.1.1/ всё открывается, но при запуске видео не открывается проигрыватель, а открывается ссылка на сайт, откуда было скачано видео. при назначении открыть в другом приложении проигрыватель открывается, но тормозит. при обращении из проигрывателя VLC сети windows всё работает хорошо. проблема наблюдается на компьютере и на ноутбуке Status in nautilus package in Ubuntu: Incomplete Bug description: при подключении к роутеру Keenetic iii набираю smb://keenetic/ появляется папка (диск Usbi) связь разрывается. при подключении ftp://192.168.1.1/ всё открывается, но при запуске видео не открывается проигрыватель, а открывается ссылка на сайт, откуда было скачано видео. при назначении открыть в другом приложении проигрыватель открывается, но тормозит. при обращении из проигрывателя VLC к сети windows всё работает хорошо. проблема наблюдается на компьютере и на ноутбуке. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 8 14:57:59 2020 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2020-05-04 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1877565/+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 1726453] Re: on screen keyboard does not pop up on firefox ubuntu-gnome 16.04.3
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1726453 Title: on screen keyboard does not pop up on firefox ubuntu-gnome 16.04.3 Status in gnome-shell package in Ubuntu: Expired Bug description: on screen key board not appearing in non ubuntu shell applications output of lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726453/+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 1867066] Re: [Dell XPS M1530] Touchpad issues
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1867066 Title: [Dell XPS M1530] Touchpad issues Status in libinput package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in xserver-xorg-input-libinput package in Ubuntu: Expired Bug description: Good evening all I just change the laptop from lenovo to dell and can not find out how make work the touchpad. Can not use two-finger scroll, pgdn/up, right primary button and an external mouse neither. The bluetooth will never work again untill re-installing an OS from micro-horror-soft, switching up the bluetooth module and re-installing ubuntu back. But I still love Linux ! I will appreciate if you help me, in the meantime i keep searching by myself in the ubuntu's forum how to fix my issues. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 23:49:44 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 4.15.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G84M [GeForce 8600M GT] [1028:022e] InstallationDate: Installed on 2020-03-06 (5 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS M1530 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic root=UUID=d2388a4a-3b22-4fb6-af07-913d081f1cab ro quiet splash acpi_osi=!Windows 2012 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0D501F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn0D501F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1530 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.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1867066/+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 1867066] Re: [Dell XPS M1530] Touchpad issues
[Expired for xserver-xorg-input-libinput (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xserver-xorg-input-libinput (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1867066 Title: [Dell XPS M1530] Touchpad issues Status in libinput package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in xserver-xorg-input-libinput package in Ubuntu: Expired Bug description: Good evening all I just change the laptop from lenovo to dell and can not find out how make work the touchpad. Can not use two-finger scroll, pgdn/up, right primary button and an external mouse neither. The bluetooth will never work again untill re-installing an OS from micro-horror-soft, switching up the bluetooth module and re-installing ubuntu back. But I still love Linux ! I will appreciate if you help me, in the meantime i keep searching by myself in the ubuntu's forum how to fix my issues. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 23:49:44 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 4.15.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G84M [GeForce 8600M GT] [1028:022e] InstallationDate: Installed on 2020-03-06 (5 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS M1530 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic root=UUID=d2388a4a-3b22-4fb6-af07-913d081f1cab ro quiet splash acpi_osi=!Windows 2012 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0D501F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn0D501F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1530 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.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1867066/+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 1867066] Re: [Dell XPS M1530] Touchpad issues
[Expired for libinput (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libinput (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1867066 Title: [Dell XPS M1530] Touchpad issues Status in libinput package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in xserver-xorg-input-libinput package in Ubuntu: Expired Bug description: Good evening all I just change the laptop from lenovo to dell and can not find out how make work the touchpad. Can not use two-finger scroll, pgdn/up, right primary button and an external mouse neither. The bluetooth will never work again untill re-installing an OS from micro-horror-soft, switching up the bluetooth module and re-installing ubuntu back. But I still love Linux ! I will appreciate if you help me, in the meantime i keep searching by myself in the ubuntu's forum how to fix my issues. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 23:49:44 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 4.15.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G84M [GeForce 8600M GT] [1028:022e] InstallationDate: Installed on 2020-03-06 (5 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS M1530 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic root=UUID=d2388a4a-3b22-4fb6-af07-913d081f1cab ro quiet splash acpi_osi=!Windows 2012 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0D501F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn0D501F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1530 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.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1867066/+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 1878132] Re: Canon i560 driver missing in 20.04
Canon BJC-7000 driver not, really satisfactory -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gutenprint in Ubuntu. https://bugs.launchpad.net/bugs/1878132 Title: Canon i560 driver missing in 20.04 Status in gutenprint package in Ubuntu: New Bug description: cant find canon i560 driver in 20.04 distro. Worked great in 19 and 18. I've still got the printer and it's still functional and I want to use it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gutenprint/+bug/1878132/+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 1878132] [NEW] Canon i560 driver missing in 20.04
Public bug reported: cant find canon i560 driver in 20.04 distro. Worked great in 19 and 18. I've still got the printer and it's still functional and I want to use it. ** Affects: gutenprint (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gutenprint in Ubuntu. https://bugs.launchpad.net/bugs/1878132 Title: Canon i560 driver missing in 20.04 Status in gutenprint package in Ubuntu: New Bug description: cant find canon i560 driver in 20.04 distro. Worked great in 19 and 18. I've still got the printer and it's still functional and I want to use it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gutenprint/+bug/1878132/+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 1878105] Re: Xorg crash
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1878105 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: Crash is caused when visiting websites that attempt to customize the cursor layout. (Tested with Firefox 76.0 (64-bit)) The website on which the crash first occurred was the following: https://www.yellibeanz.com/ the crash is triggered after moving the cursor around. To test the hypothesis of the cursor causing the bug I also tested the following website with identical outcome: http://www.flockofsiegel.tv/ I am sure that one can find more examples here: https://onextrapixel.com/10-websites-that-replace-mouse-cursors-for-a -better-cause/ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 11 23:58:41 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Mobile) [1043:1fc0] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1fc0] InstallationDate: Installed on 2020-05-03 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 13d3:56a2 IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X580GD_N580GD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=04dedfb2-c5a9-4447-af72-16999d76fce2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X580GD.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X580GD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias:
[Desktop-packages] [Bug 1878109] Re: Certain features in the Sharing panel fail with D-Bus related messages when gnome-control-center is run over ssh -X
** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1878109 Title: Certain features in the Sharing panel fail with D-Bus related messages when gnome-control-center is run over ssh -X Status in gnome-control-center package in Ubuntu: New Bug description: When I run gnome-control-center (1:3.36.1-1ubuntu5) on a remote Ubuntu 20.04 host over ssh -X, trying to enable Screen Sharing (VNC) or Media Sharing in the Sharing panel (*) fails with the following D-Bus related messages on the standard error: -- (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:12.770: couldn't list networks: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:28.646: Failed to enable service vino-server: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:54.309: Failed to enable service rygel: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files -- What does this mean? Can I do anything about it? A remote user, sitting in front of the remote computer, can enable Screen Sharing or Media Sharing in gnome-control-center themselves. Failure to enable only occurs over ssh -X, as far as I can tell. Looking up this error online led me down a D-Bus rabbit hole. I found many year-old StackExchange answers that recommend setting various environment variables and/or running dbus-launch to start a session bus instance of dbus-daemon, in case of D-Bus related errors. I am rather unfamiliar with D-Bus, but I can see using ps -ef | grep dbus that a session bus instance of dbus-daemon is already running. It has been started under my UID at the time of my SSH login. So I'm wary of those old resources. I have tried following their instructions though, for completeness sake, but to no avail. I can provide more information if necessary. (*) This odd situation happened when I had to provide technical support over VNC to an older user whose computer I had previously set up with SSH access. Hence why I was using ssh -X to try and enable VNC in gnome-control-center... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1878109/+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 1878091] Re: [nvidia] Non-fractional scaling not working
Is the problem only when you try to set resolution 1920x1080? This certainly sounds like a bug. But if the system defaults to 3840x2160, scale = 200%, then that should actually give a better result than 1920x1080 would. -- 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/1878091 Title: [nvidia] Non-fractional scaling not working Status in mutter package in Ubuntu: Incomplete Bug description: My laptop has a 4K display. Default Resolution = 3840x2160, scale = 200%. If I set resolution to 1920x1080, everything on the desktop is scaled to double size. So, if I reduce the Scale setting from 200% to 100%, I would expect everything to look normal again, but it does not. 100% and 200% look identical. However, if I enable Fractional scaling and select 125%, that looks correct. So, Fractional scaling works correctly, but non-fractional scaling does not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 11 15:58:43 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3978] Subsystem: Lenovo GM107M [GeForce GTX 960M] [17aa:3978] InstallationDate: Installed on 2020-05-07 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20349 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=4f7e434e-f524-450c-8486-29302f1ca495 ro persistent quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: K0J40709WIN dmi.board.name: Lenovo Y50-70 Touch dmi.board.vendor: LENOVO dmi.board.version: K0J40709WIN dmi.chassis.asset.tag: K0J40709WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 Touch dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20349:pvrLenovoY50-70Touch:rvnLENOVO:rnLenovoY50-70Touch:rvrK0J40709WIN:cvnLENOVO:ct10:cvrLenovoY50-70Touch: dmi.product.family: IDEAPAD dmi.product.name: 20349 dmi.product.sku: LENOVO_MT_20349_BU_idea_FM_Lenovo Y50-70 Touch dmi.product.version: Lenovo Y50-70 Touch dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1878091/+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 1878091] Re: Non-fractional scaling not working
Please attach screenshots of the Settings window while things are working, and while things are not working. ** Tags added: nvidia xrandr-scaling ** Summary changed: - Non-fractional scaling not working + [nvidia] Non-fractional scaling not working ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (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/1878091 Title: [nvidia] Non-fractional scaling not working Status in mutter package in Ubuntu: Incomplete Bug description: My laptop has a 4K display. Default Resolution = 3840x2160, scale = 200%. If I set resolution to 1920x1080, everything on the desktop is scaled to double size. So, if I reduce the Scale setting from 200% to 100%, I would expect everything to look normal again, but it does not. 100% and 200% look identical. However, if I enable Fractional scaling and select 125%, that looks correct. So, Fractional scaling works correctly, but non-fractional scaling does not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 11 15:58:43 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3978] Subsystem: Lenovo GM107M [GeForce GTX 960M] [17aa:3978] InstallationDate: Installed on 2020-05-07 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20349 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=4f7e434e-f524-450c-8486-29302f1ca495 ro persistent quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: K0J40709WIN dmi.board.name: Lenovo Y50-70 Touch dmi.board.vendor: LENOVO dmi.board.version: K0J40709WIN dmi.chassis.asset.tag: K0J40709WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 Touch dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20349:pvrLenovoY50-70Touch:rvnLENOVO:rnLenovoY50-70Touch:rvrK0J40709WIN:cvnLENOVO:ct10:cvrLenovoY50-70Touch: dmi.product.family: IDEAPAD dmi.product.name: 20349 dmi.product.sku: LENOVO_MT_20349_BU_idea_FM_Lenovo Y50-70 Touch dmi.product.version: Lenovo Y50-70 Touch dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1878091/+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 1231730] Re: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Playback problem
Dear Marcus, this was not, as it turned out, strictly a "bug" in Launchpad terms. In fact, as I and my Watcher Raymond discovered from inspired research by a guy whose name I have forgotten, it started life as a deliberate "System Restriction" approved and adopted in the minutes of Ubuntu's Central Committee. Although originally intended as an emergency remedy to cover the imminent release of the upcoming Ubuntu version, it remained in force over the next _half dozen or so_ releases. The story goes like so;- with HDMI becoming accepted it was intended to include suitable drivers in the next Ubuntu, but with the release deadline looming, it was recognised that the "Radeon" drivers for ATI video cards, were not fit to go. The sound sub-system of said drivers was seen to host a nest of insecticide resistant bugs keen to crash the entire system. The official solution was to go ahead with the release _with HDMI sound disabled_ but leaving the video. It effectively _became a bug_ when, possibly from embarrassment (?), all mention of this was omitted from the "Release Notes" of this, and following versions. There were two workarounds:- 1) select the appropriate proprietary ATI driver & install 2) follow instructions from Launchpad contributors, ignore the risk, and _simply re-enable audio._ I had fun with this at the time. Hope you find it of interest. Regards, Bob On 05/03/2020 13:14, Marcus Tomlinson wrote: > This release of Ubuntu is no longer receiving maintenance updates. If > this is still an issue on a maintained version of Ubuntu please let us > know. > > ** Changed in: alsa-driver (Ubuntu) > Status: New => Incomplete > -- 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/1231730 Title: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Playback problem Status in alsa-driver package in Ubuntu: Invalid Bug description: I have 2 computers; 1) this with Asus M2A-VMHDMI motherboard, 2core AMD CPU and ATI HD 6000 series graphic card where I do not actually use the HDMI output ; 2) the second with Asus M4A 72 PRO motherboard, 4core Phenom and ATI HD 7000 (previously with the 6000 above), which does use the HDMI to connect to a Sharp brand TV. The symptom is the same:- i) turn computer on ii) select "system settings" iii) select "sound" iv) observe that I am presented with only 2 choices for sound "output" ---onboard analogue, or onboard digital; NO HDMI This same symptom occurs with every attempted upgrade from 12.04 Precise Pangolin, whether I upgrade online or from CD ; or erase the entire installation and re-install the later versions fresh from CD (which I often do when out of frustration I have been tempted to load proprietary ATI drivers ...resulting in little pop-ups with AMD kindly informing me that I am mounting "Unsupported Hardware" sic.) NOW:- When ASUS make half the Motherboards on the planet and ATI make half the Graphic cards, then WHY?? , if I choose on account of this prevalence to regard this as a rather general bug and and start writing this report is my computer already telling me that I have to go "unix-nerd" , and open a terminal, and install a program called "pavucontrol" which is a volume control for something called "Pulse Audio" and which as I eventually find instruction; will, if run with no options and no commands, tell me in an extremely frustrating fashion, that somewhere in it's interior it is running my desired HDMI at 100% volume !! ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bob1848 F pulseaudio /dev/snd/controlC0: bob1848 F pulseaudio /dev/snd/pcmC0D0c: bob1848 F...m pulseaudio
[Desktop-packages] [Bug 1878050] Re: Nvidia GT 240m gives problems
I can see three issues: 1. You're using Ubuntu 16.04. While that is supported, it is not well supported. Please consider trying Ubuntu 20.04 instead: https://ubuntu.com/download/desktop 2. The nvidia driver (when it is working) reports the screen is faulty: [19.136] (WW) NVIDIA(GPU-0): The EDID read for display device DFP-0 is invalid: the [19.136] (WW) NVIDIA(GPU-0): checksum for EDID version 1 is invalid. Please try to get a BIOS update from Acer to fix that. 3. The Nvidia driver is possibly not installed properly. Please uninstall it completely. Then if the system still doesn't work without it, reinstall it. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1878050 Title: Nvidia GT 240m gives problems Status in xorg-server package in Ubuntu: Incomplete Bug description: Can't install proprietary NVIDIA driver 340.107 X uses software rendering rather than hardware ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-178.208-generic 4.4.217 Uname: Linux 4.4.0-178-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon May 11 18:41:34 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-178-generic, x86_64: installed virtualbox, 5.1.38, 4.4.0-148-generic, x86_64: installed virtualbox, 5.1.38, 4.4.0-178-generic, x86_64: installed virtualbox, 5.1.38, 4.4.0-98-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 240M] [10de:0a34] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GT216M [GeForce GT 240M] [10de:0688] InstallationDate: Installed on 2017-09-18 (965 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Acer Aspire Z5610 ProcEnviron: LANGUAGE=nl_BE:nl PATH=(custom, no user) LANG=nl_BE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-178-generic root=UUID=398c17c4-3b3b-4a56-92f8-6f6a37b9eee1 ro nomodeset quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/19/2010 dmi.bios.vendor: Phoenix dmi.bios.version: P01-B2L dmi.board.name: Aspire Z5610 dmi.board.vendor: Acer dmi.chassis.type: 13 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnPhoenix:bvrP01-B2L:bd01/19/2010:svnAcer:pnAspireZ5610:pvr:rvnAcer:rnAspireZ5610:rvr:cvnAcer:ct13:cvr: dmi.product.name: Aspire Z5610 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon May 11 18:16:46 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1878050/+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 1877932] Re: Bluetooth not connecting to last paired device when enabling bluetooth
** Package changed: pulseaudio (Ubuntu) => bluez (Ubuntu) ** Summary changed: - Bluetooth not connecting to last paired device when enabling bluetooth + Bluetooth not connecting to last paired device (Anker headset) when enabling bluetooth ** Changed in: bluez (Ubuntu) Status: Incomplete => 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/1877932 Title: Bluetooth not connecting to last paired device (Anker headset) when enabling bluetooth Status in bluez package in Ubuntu: New Bug description: I am using a Dell Lattitude E7470 laptop. I am trying to connect a Bluetooth headset (Anker). I am seeing this issue with the latest upgrade to the Ubuntu 20.04 LTS version. I have a Bluetooth headset which is paired with the machine. Given the Bluetooth is enabled in the Ubuntu machine and I switch on my Bluetooth headset, the ubuntu machine does not automatically connect to this device anymore. It used to do it very easily with 18.04,19.04 and 19.10 ubuntu version. I have to do a variety of steps to get it connected: * turn off and on the headset. * turn off and on the laptop bluetooth. * try manully connecting to the device from the setting menu multiple times. * Sometimes it detects and get connected automatically as it should. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: justin 2220 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 19:42:46 2020 InstallationDate: Installed on 2019-02-21 (444 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/usr/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to focal on 2020-04-27 (13 days ago) dmi.bios.date: 10/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.22.8 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.22.8:bd10/08/2019:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7470 dmi.product.sku: 06DC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1877932/+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 1696594] Re: gnome-font-viewer crashed with SIGSEGV
No, I don’t think this is still reproducible as it was. gnome-font- viewer is still rough around the edges, but not as egregiously as in 2017. Will close. ** Changed in: gnome-font-viewer (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1696594 Title: gnome-font-viewer crashed with SIGSEGV Status in gnome-font-viewer package in Ubuntu: Invalid Bug description: The viewer crashes immediately after trying to open a font file from the file manager. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-font-viewer 3.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Jun 7 17:29:50 2017 ExecutablePath: /usr/bin/gnome-font-viewer InstallationDate: Installed on 2017-01-29 (129 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170118) ProcCmdline: /usr/bin/gnome-font-viewer --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_MX:es PATH=(custom, no user) LANG=es_MX.UTF-8 SegvAnalysis: Segfault happened at: 0x7fc08bd7f6ea:mov0x50(%r12),%rdi PC (0x7fc08bd7f6ea) ok source "0x50(%r12)" (0x00f0) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-font-viewer StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () () () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-font-viewer crashed with SIGSEGV UpgradeStatus: Upgraded to artful on 2017-06-04 (3 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1696594/+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 1877850] Re: Super key is logically stuck down
Sounds related. Maybe wait until bug 1871913 is fix released to focal. Then if this issue is still not fixed after that we can report it upstream. -- 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/1877850 Title: Super key is logically stuck down Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: There are shortcuts like 'Super + P' to change the display mode or 'Super + l' to go to login screen. However, after i upgraded ubuntu 18.04 to 20.04, if i press P or l or any other character which there is a 'super + key' for it, it's does the same thing. It's like the super key is always on! My keyboard works fine in Unity so it's not a hardware problem. GNOME Shell 3.36.1 Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877850/+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 1877871] Re: X windows hnags following upgrade from 18.04 to 20.04
Thanks for the bug report. The log in comment #2 shows lots of radeon kernel errors so I am moving this bug to the kernel. ** Tags added: radeon ** Summary changed: - X windows hnags following upgrade from 18.04 to 20.04 + [radeon] X windows hangs following upgrade from 18.04 to 20.04 ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1877871 Title: [radeon] X windows hangs following upgrade from 18.04 to 20.04 Status in linux package in Ubuntu: New Bug description: Following an upgrade from 18.04 to 20.04 when I boot, X windows comes to a point where I get a white background with a bunch of colored dots. Nothing progresses from there. I can boot successfully by pressing escape after booting, going to advanced options, booting to 5.4.0-29 recovery mode. When that menu appears, I select "root". I press Enter for maintenance. When the root prompt appears I immediately type EXIT to return to the menu and then RESUME followed by OK. The system then starts the desktop properly. I would be happy to provide boot logs and/or Xorg.0.logs if desired. It appears to me that there are out of memory errors occurring along with some addressing issues. I am on an HP EliteBook 8570w laptop 15.6 G memory. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 10:22:37 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-22 (595 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-05-09 09:07:41.355959 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877871/+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 1877746] Re: Lock screen not working
Please run these commands and send us the output: gsettings list-recursively org.gnome.desktop.session gsettings list-recursively org.gnome.desktop.lockdown ** 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/1877746 Title: Lock screen not working Status in gnome-shell package in Ubuntu: Incomplete Bug description: The screen will not automatically lock on the specified timer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09: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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 9 08:54:58 2020 DistUpgraded: 2020-04-27 21:42:55,589 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1660 Ti] [1458:3fbe] InstallationDate: Installed on 2018-07-01 (678 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6998b6fb-9ba7-4ce9-a023-b36dab34d51a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-28 (11 days ago) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: X470 AORUS ULTRA GAMING-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.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSULTRAGAMING:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSULTRAGAMING-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X470 AORUS ULTRA GAMING 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.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877746/+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 1877828] Re: Missing feature: disable one specific wireless device meanwhile another remain switched on
See also bug 1877074. ** Changed in: gnome-shell (Ubuntu) Importance: Low => Wishlist ** Changed in: gnome-shell (Ubuntu) Status: New => 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/1877828 Title: Missing feature: disable one specific wireless device meanwhile another remain switched on Status in gnome-shell package in Ubuntu: Triaged Bug description: When working on laptop, we may need an external wifi adapter in order to catch a remote access point no working well with the built-in wireless card of the laptop. In such case, it would make sense to disable the internal wireless card in order to have just the external on working. However, Ubuntu does not offer a simple way to do so. Moreover, if I click on "Turn off" for the built-in wifi adapter in the top right corner menu (see the screenshot), both wifi adapters are swtiched off, which is not the desired effect. See for example: https://askubuntu.com/questions/168032/how-to- disable-built-in-wifi-and-use-only-usb-wifi-card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877828/+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 1877686] Re: Mouse lags since 20.04 update
There are some interesting PCI errors in your kernel log, which might be related. But if those are relevant then they would not be fixable in software. So I can't tell if this is a hardware issue, mutter issue, a kernel issue, a libinput issue or a Xorg issue. Please confirm again the problem does occur when you log into 'Ubuntu on Wayland' and run 'xrandr' after doing so. Then paste the output here. ** Package changed: xorg-server (Ubuntu) => ubuntu -- 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/1877686 Title: Mouse lags since 20.04 update Status in Ubuntu: Incomplete Bug description: After installing ubuntu 20.04, I have an issue with my mouse pointer lagging a lot. It happens on my trackpad, physical mouse, wacom tablet, and trackpoint. It's only a graphical issue (ie: The underlying whatever is actually moving. The visible pointer just isn't). Other mouse moving related actions do not exhibit the same behaviour. Window dragging is smooth. Applications that use custom mouse pointers, such as krita, work smoothly. The issue persists both on nVidia graphics and intel integrated graphics. I am using a lenovo thinkpad p50. The issue persists constantly when I am using the in built laptop screen. However, when I connect a second monitor, it only happens occasionally. I installed ubuntu 20.04 from a usb drive, keeping my home partition from 18.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 9 01:28:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 530 [17aa:222e] NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo GM107GLM [Quadro M1000M] [17aa:222e] InstallationDate: Installed on 2020-05-08 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:0090 Validity Sensors, Inc. VFS7500 Touch Fingerprint Sensor Bus 001 Device 002: ID 04ca:7058 Lite-On Technology Corp. Integrated Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 8: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 8: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 9: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M MachineType: LENOVO 20EQS2BH00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=9eb4b789-a22e-455b-8e8b-19e78e0ef3d6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET86W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EQS2BH00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET86W(1.59):bd08/28/2019:svnLENOVO:pn20EQS2BH00:pvrThinkPadP50:rvnLENOVO:rn20EQS2BH00:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EQS2BH00 dmi.product.sku: LENOVO_MT_20EQ_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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.8-2ubuntu2 version.xserver-xorg-input-evdev:
[Desktop-packages] [Bug 1878128] Re: PCI/internal sound card not detected
...ignore me. Start-Date: 2020-05-09 16:01:28 Commandline: apt install oss4-base Requested-By: logan (1000) Install: oss4-base:amd64 (4.2-build2010-5ubuntu5), libx86-1:amd64 (1.1+ds1-11, a utomatic), vbetool:amd64 (1.1-4, automatic), pm-utils:amd64 (1.4.1-19, automatic ), ethtool:amd64 (1:5.4-1, automatic) Remove: alsa-base:amd64 (1.0.25+dfsg-0ubuntu5), ubuntu-desktop-minimal:amd64 (1.450), linux-sound-base:amd64 (1.0.25+dfsg-0ubuntu5), ubuntu-desktop:amd64 (1.450) End-Date: 2020-05-09 16:01:33 ** Changed in: alsa-driver (Ubuntu) Status: New => Invalid -- 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/1878128 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Invalid Bug description: Sound mysteriously stopped working recently on my Dell XPS 9560 laptop. I only see Dummy Output and not my actual speakers. Rebooting didn't fix it, and sound continues to work in Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 11 22:24:09 2020 InstallationDate: Installed on 2020-02-14 (87 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1878128/+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 1878128] [NEW] PCI/internal sound card not detected
Public bug reported: Sound mysteriously stopped working recently on my Dell XPS 9560 laptop. I only see Dummy Output and not my actual speakers. Rebooting didn't fix it, and sound continues to work in Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 11 22:24:09 2020 InstallationDate: Installed on 2020-02-14 (87 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug focal -- 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/1878128 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Invalid Bug description: Sound mysteriously stopped working recently on my Dell XPS 9560 laptop. I only see Dummy Output and not my actual speakers. Rebooting didn't fix it, and sound continues to work in Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 11 22:24:09 2020 InstallationDate: Installed on 2020-02-14 (87 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1878128/+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 1877675] Re: Workspaces broken with latest update
Please check that you do have workspaces configured in: gnome-tweaks > Workspaces Also I have a feeling this will be related to bug 1870188 which also has an upstream bug. Ignore comment #3 - the crashes I was talking about are old and from two years ago in your attached XorgLog.txt and XorgLogOld.txt. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1877675 Title: Workspaces broken with latest update Status in gnome-shell package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: Incomplete Bug description: Multiple workspaces broke with latest gnome config update. Unable to create, or go to different workspaces. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09: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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 8 17:05:52 2020 DistUpgraded: 2020-04-27 21:42:55,589 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1660 Ti] [1458:3fbe] InstallationDate: Installed on 2018-07-01 (677 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6998b6fb-9ba7-4ce9-a023-b36dab34d51a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-28 (10 days ago) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: X470 AORUS ULTRA GAMING-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.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSULTRAGAMING:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSULTRAGAMING-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X470 AORUS ULTRA GAMING 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.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877675/+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 1877655] Re: [Dell Venue 11 Pro 7140] Trackpad does not work in Xorg sessions
Since you said the trackpad works in Wayland until you run Software Center, please: 1. Log into 'Ubuntu on Wayland'. 2. Make sure the trackpad works. 3. Open a Terminal and run: dmesg -w Leave it running but tap Enter several times to make some blank lines. 4. Open Software Centre. 5. Does the Terminal window now show any new messages? ** Summary changed: - Synaptic Trackpad does not work in Xorg sessions + [Dell Venue 11 Pro 7140] Trackpad does not work in Xorg sessions ** Package changed: xorg-server (Ubuntu) => linux (Ubuntu) ** Summary changed: - [Dell Venue 11 Pro 7140] Trackpad does not work in Xorg sessions + [Dell Venue 11 Pro 7140] Trackpad does not work -- 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/1877655 Title: [Dell Venue 11 Pro 7140] Trackpad does not work Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2
[Desktop-packages] [Bug 1877822] Re: xorg (Ubuntu) bug reporting guidelines:
*** This bug is a duplicate of bug 1877821 *** https://bugs.launchpad.net/bugs/1877821 ** Information type changed from Private Security to Public ** This bug has been marked a duplicate of bug 1877821 xorg (Ubuntu) bug reporting guidelines: -- 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/1877822 Title: xorg (Ubuntu) bug reporting guidelines: Status in xorg package in Ubuntu: New Bug description: Please report bugs against xorg with this command: $ ubuntu-bug xorg For more tips on effective bug reporting against Ubuntu Xorg packages, please see http://wiki.ubuntu.com/X/Reporting and thanks ahead of time! Ubuntu bug reporting guidelines: Are you uncertain if your issue is really a bug? Then ask a support question about Ubuntu at http://answers.launchpad.net/ubuntu/ - these can be made into bugs later. Another support venue is http://askubuntu.com. If you are certain this is a bug please include the source package the bug is in. For help see https://wiki.ubuntu.com/Bugs/FindRightPackage. We also need: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 10 06:15:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2020-05-05 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Latitude 5500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=55faf464-9082-49b3-9a16-cab619ffa5a9 ro dis_ucode_ldr quiet splash nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.5 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.5:bd12/26/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101+git2005070630.c997ba~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2005091930.e622e0~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1877822/+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 1825580] Re: Gnome Online Accounts fails to sign in Exchange emails
Looking around some more, it seems it may be related to this: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1866974 I did add the suggested item to the /etc/gnutls and the account successfully is added to GOA now, but still isn't letting me download email due to a different error, but it does seem that it could be related to the TLS key length issue cited above. -- 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/1825580 Title: Gnome Online Accounts fails to sign in Exchange emails Status in gnome-online-accounts: New Status in gnome-online-accounts package in Ubuntu: Triaged Bug description: After upgrading from 18.10 and/or on fresh install, a known-working Exchange email setup fails to sign in, giving "Error 7: Unexpected response from server". Tested the same settings and credentials on a new install of 18.10 and it worked. I have Evolution and Evolution-ews installed on all instances, working in 18.10, not in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-online-accounts 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 16:38:32 2019 InstallationDate: Installed on 2018-03-24 (391 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to disco on 2019-03-12 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1825580/+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 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series
Hi Alberto, can I use lutris/fortnite wil my NVIDIA 340.108 on ubuntu? I have failed the first time since the Volkan version was not updated. Thanks. Regards, Pietro -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1854485 Title: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series Status in linux package in Ubuntu: Triaged Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-440 source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-restricted-modules source package in Eoan: Fix Released Status in nvidia-graphics-drivers-340 source package in Eoan: New Status in nvidia-graphics-drivers-390 source package in Eoan: Fix Released Status in nvidia-graphics-drivers-440 source package in Eoan: Fix Released Status in nvidia-settings source package in Eoan: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] 440.40: * New upstream release: - Added support for the following GPU: Quadro T2000 with Max-Q Design - Added support for the __GL_SYNC_DISPLAY_DEVICE environment variable for Vulkan applications. - Fixed a bug that caused applications running directly on a display (such as VR HMDs) to tear when a G-SYNC or G-SYNC Compatible monitor is plugged in the system. - Fixed a bug in an error handling path that could cause a kernel crash while loading nvidia.ko. - Fixed driver installation failure on Oracle Linux 7.7 systems, where the NVIDIA kernel module failed to build with error "unknown type name 'vm_fault_t'". * Changes from the 440.36 series: - Added support for the following GPUs: o GeForce GTX 1650 SUPER o GeForce GTX 1660 SUPER - Fixed graphical corruption that can occur when using glslang SPIR-V Generator Version <= 2. - Fixed a bug that could cause the X server to crash when running applications using GLX indirect rendering. - Updated the Module.symvers sanity check, which is part of the NVIDIA kernel module build process, to accommodate the recent addition of a new field in the Module.symvers file format. This fixes the error "The Module.symvers file is missing [...]" seen during driver installation or DKMS rebuilds with Linux 5.4 RC kernels. - Fixed kernel module build problems with Linux kernel 5.4.0 release candidates. - Updated nvidia-bug-report.sh to collect information about X server crashes from coredumpctl, when available. - Updated the nvidia-drm kernel module for compatibility with the removal of the DRIVER_PRIME flag in recent Linux kernel versions. - Enabled parallel GLSL shader linking by default; i.e., allow GL_ARB_parallel_shader_compile to work without first calling glMaxShaderCompilerThreadsARB(). - Added support for HDMI 2.1 variable refresh rate (VRR) G-SYNC Compatible monitors on supported GPUs.For more details, see "Configuring Multiple Display Devices on One X Screen" in the README. Added support for the GLX_NV_multigpu_context and GL_NV_gpu_multicast extensions.For more details, see the "Configuring SLI and Multi-GPU
[Desktop-packages] [Bug 1877568] Re: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)
If it is a compositor bug as the Wayland library is suggesting then next please try uninstalling all non-Ubuntu gnome-shell extensions, and reboot. ** Changed in: gnome-terminal (Ubuntu) Status: New => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Changed in: wayland (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1877568 Title: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing) Status in gnome-terminal package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in wayland package in Ubuntu: Incomplete Bug description: Since upgrading to 20.04 and switching to Wayland, Gnome terminal occasionally crashes. I interpret the corresponding logs to mean that it's actually Wayland that fails to do something in the background, which then takes down Gnome terminal: touko 08 11:35:16 saegusa gnome-shell[4227]: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client. touko 08 11:35:16 saegusa gnome-shell[4227]: WL: error in client communication (pid 11639) touko 08 11:35:16 saegusa gnome-terminal-[11639]: Error reading events from display: Katkennut putki touko 08 11:35:16 saegusa systemd[4153]: vte-spawn-bbca1723-5987-4ccf-98cb-3389ad05641e.scope: Succeeded. touko 08 11:35:16 saegusa systemd[4153]: vte-spawn-fbe02208-95df-4cf4-bfbe-fffc71d6bc7e.scope: Succeeded. touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: Failed with result 'exit-code'. I have yet to nail down the precise circumstances, as this has (so far) been somewhat rare, having occurred perhaps once or twice a week. Since the log mentions pointer, I should perhaps mention that I've set `org.gnome.desktop.wm.preferences` > `focus-mode` to `mouse`. Gnome terminal also exhibits other misbehaviour wrt. to this, occasionally refusing to get focus, or alternatively losing the focus, despite mouse cursor being over the terminal window. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xwayland 2:1.20.8-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 8 15:22:28 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 20.03.00, 5.4.0-29-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms, 20.03.00, 5.4.0-30-generic, x86_64: installed (WARNING! Diff between built and installed module!) xtables-addons, 3.8, 5.4.0-29-generic, x86_64: installed xtables-addons, 3.8, 5.4.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca] InstallationDate: Installed on 2016-10-13 (1302 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-30-generic root=UUID=45ed9550-28e7-4af4-a625-9f31663dce9b ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1505 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-M PRO 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.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
[Desktop-packages] [Bug 1876797] Re: Numerous issues
Please tell us the resulting new bugs IDs *or* tell us the links you got from step 2 of comment 2. -- 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/1876797 Title: Numerous issues Status in xorg-server package in Ubuntu: Incomplete Bug description: I upgraded from 18.04 -> 20.04. After upgrade, it will not remember my display configuration if I reboot. Settings can be saved (forced) into Xconfig, but for some reason it ignores them. I have a 1080p monitor vertical on my left, and a 1440p monitor on my right. Also, the system still believes I'm on Ubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09: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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 4 13:54:32 2020 DistUpgraded: 2020-04-27 21:42:55,589 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1660 Ti] [1458:3fbe] InstallationDate: Installed on 2018-07-01 (673 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6998b6fb-9ba7-4ce9-a023-b36dab34d51a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-28 (6 days ago) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: X470 AORUS ULTRA GAMING-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.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSULTRAGAMING:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSULTRAGAMING-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X470 AORUS ULTRA GAMING 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.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1876797/+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 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
** Summary changed: - [nvidia] Secondary (rotated) monitor configuration is not applied correctly in gnome settings + [nvidia] Rotating secondary monitor to portrait fails, results in landscape -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: SZ77 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1874567/+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 1876369] Re: [nouveau] garbled/frozen screen after waking from sleep mode
Thanks. Since there's nothing identifiable on that screen it seems like a kernel issue. Not the mutter issue I was thinking of. Please: 1. Reproduce the bug. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Package changed: mutter (Ubuntu) => linux (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/1876369 Title: [nouveau] garbled/frozen screen after waking from sleep mode Status in linux package in Ubuntu: Incomplete Bug description: Computer boots and runs normally until it goes into sleep mode. wehen trying to wake from sleep mode, screen is filled with what looks like frozen static on an old TV, then it locks up. I have to force power- off the computer and reboot to make it work again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Fri May 1 14:45:37 2020 DistUpgraded: 2020-04-28 09:50:34,578 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G96CM [GeForce 9650M GT] [10de:064c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G96CM [GeForce 9650M GT] [1043:1912] InstallationDate: Installed on 2018-04-28 (734 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: ASUSTeK Computer Inc. M70Vn ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d4a14cd2-2bf0-4a55-a605-f421a799c4eb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-28 (3 days ago) dmi.bios.date: 12/21/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M70Vn dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd12/21/2009:svnASUSTeKComputerInc.:pnM70Vn:pvr1.0:rvnASUSTeKComputerInc.:rnM70Vn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M70Vn dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Fri May 1 14:38:54 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876369/+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 1875435] Re: Re-logging occurs continuously during ubuntu operation
This bug has become confused by too many different configurations and an insufficient problem description. Please: 1. Use an Ubuntu kernel only. 2. Uninstall and reinstall the Nvidia driver. 3. Reboot. 4. If the problem still occurs then please open a new bug by running: ubuntu-bug xorg ** Package changed: xserver-xorg-video-nouveau (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1875435 Title: Re-logging occurs continuously during ubuntu operation Status in Ubuntu: Incomplete Bug description: I thought that I had some kind of problem with the video driver and all the detailed logs are contained here https://forums.developer.nvidia.com/t/ubuntu-kernel-v5-6-v5-7-for-hp-omen-17t-bc000-gforce-rtx2080-unstable-driver-nvidia-linux-x86-64-440-82-run/120027/25 But I installed ubuntu 20.04 and the problem is repeated not only on new kernels ubuntu 5.6 and 5.7.0-rc but also on kernel 5.4 with the Nouveau driver The system constantly logs onto the standard screen and requires a password to close all current programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1875435/+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 1875435] Re: Re-logging occurs continuously during ubuntu operation
journalctl8.log shows the open source driver can't start because of missing features in the kernel. Please try a supported Ubuntu kernel. (EE) [drm] Failed to open DRM device for pci::01:00.0: -19 (EE) open /dev/dri/card0: No such file or directory journalctl7.log shows the Nvidia driver seems to be working. journalctl6.log shows the Nvidia driver seems to be working. journalctl5.log shows the Nvidia driver seems to be working. -- 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/1875435 Title: Re-logging occurs continuously during ubuntu operation Status in Ubuntu: Incomplete Bug description: I thought that I had some kind of problem with the video driver and all the detailed logs are contained here https://forums.developer.nvidia.com/t/ubuntu-kernel-v5-6-v5-7-for-hp-omen-17t-bc000-gforce-rtx2080-unstable-driver-nvidia-linux-x86-64-440-82-run/120027/25 But I installed ubuntu 20.04 and the problem is repeated not only on new kernels ubuntu 5.6 and 5.7.0-rc but also on kernel 5.4 with the Nouveau driver The system constantly logs onto the standard screen and requires a password to close all current programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1875435/+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 1874567] Re: [nvidia] Secondary (rotated) monitor configuration is not applied correctly in gnome settings
Not sure it an nvidia driver issue. Using nvidia-settings to change anything in 'X Server Display Configuration' fixes the problem. Here is my xrandr output after changing the x offset of one monitor from +230 to +240. Ubuntu display settings: $ xrandr --current Screen 0: minimum 8 x 8, current 2800 x 2680, maximum 32767 x 32767 DVI-D-0 connected 1200x1600+1200+0 right (normal left inverted right x axis y axis) 408mm x 306mm panning 1600x1600+1200+0 tracking 2800x2680+0+0 border 0/0/0/0 1600x1200 60.00*+ 1280x1024 85.0275.0260.02 1280x960 60.00 1024x768 85.0075.0360.00 800x600 85.0660.32 640x480 85.0175.0059.94 HDMI-0 connected 1200x1600+0+0 right (normal left inverted right x axis y axis) 408mm x 306mm panning 1600x1600+0+0 tracking 2800x2680+0+0 border 0/0/0/0 1600x1200 60.00*+ 1280x1024 85.0275.0260.02 1280x960 60.00 1024x768 85.0075.0360.00 800x600 85.0660.32 640x480 85.0175.0059.94 DP-0 connected primary 1920x1080+230+1600 (normal left inverted right x axis y axis) 527mm x 296mm panning 2320x1080+230+1600 tracking 2800x2680+0+0 border 0/0/0/0 1920x1080 60.00*+ 59.9450.00 1680x1050 59.95 1440x900 74.9859.89 1280x1024 75.0260.02 1280x960 60.00 1280x720 60.0059.9450.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0072.8159.9459.93 DP-1 disconnected (normal left inverted right x axis y axis) after adjusting ofset using nvidia-settings (temporarily fixes the issue): $ xrandr --current Screen 0: minimum 8 x 8, current 2400 x 2680, maximum 32767 x 32767 DVI-D-0 connected 1200x1600+1200+0 right (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.00*+ 1280x1024 85.0275.0260.02 1280x960 60.00 1024x768 85.0075.0360.00 800x600 85.0660.32 640x480 85.0175.0059.94 HDMI-0 connected 1200x1600+0+0 right (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.00*+ 1280x1024 85.0275.0260.02 1280x960 60.00 1024x768 85.0075.0360.00 800x600 85.0660.32 640x480 85.0175.0059.94 DP-0 connected primary 1920x1080+240+1600 (normal left inverted right x axis y axis) 527mm x 296mm 1920x1080 60.00*+ 59.9450.00 1680x1050 59.95 1440x900 74.9859.89 1280x1024 75.0260.02 1280x960 60.00 1280x720 60.0059.9450.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0072.8159.9459.93 DP-1 disconnected (normal left inverted right x axis y axis) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Secondary (rotated) monitor configuration is not applied correctly in gnome settings Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
Having the same issue... But the tmp fix, posted by kristo on 2020-05-06 works great for me too: Browsers, my IDE (Intellij Idea), Slack, Thunderbird, the terminal, they all scale very well. I increased the size of the mouse pointer, the dock icons and the icons in nautilus as well. As Daniel wrote on 2020-05-07 the performance is even better compared with fractional scaling activated. But it has some downsides. From my point of view the most annoying one: these settings cannot be configured per display but only globally. @Daniel would it be possible to make the settings, mentioned above per display? It might be a more stable way if the performance issues and bugs, related to xrandr and Xorg in general, might occur again with every new nvidia graphic card model or new driver. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+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 1878114] [NEW] full width symbols in half width mode
Public bug reported: I am using ibus-chewing 1.6.1-1 in ubuntu 20.04. I turned off easy symbol input, so if I press "shift+6" in chinese mode, it should be a "^", but I instead get a "︿". Similar situations happen when I try to type other symbols like @#$%. ** Affects: ibus-chewing (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-chewing in Ubuntu. https://bugs.launchpad.net/bugs/1878114 Title: full width symbols in half width mode Status in ibus-chewing package in Ubuntu: New Bug description: I am using ibus-chewing 1.6.1-1 in ubuntu 20.04. I turned off easy symbol input, so if I press "shift+6" in chinese mode, it should be a "^", but I instead get a "︿". Similar situations happen when I try to type other symbols like @#$%. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-chewing/+bug/1878114/+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 1878109] Re: Certain features in the Sharing panel fail with D-Bus related messages when gnome-control-center is run over ssh -X
Here is another user reporting the same GDBus errors when trying to enable Screen Sharing on Ubuntu Server 20.04, if I understand correctly: https://askubuntu.com/questions/1238329 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1878109 Title: Certain features in the Sharing panel fail with D-Bus related messages when gnome-control-center is run over ssh -X Status in gnome-control-center package in Ubuntu: New Bug description: When I run gnome-control-center (1:3.36.1-1ubuntu5) on a remote Ubuntu 20.04 host over ssh -X, trying to enable Screen Sharing (VNC) or Media Sharing in the Sharing panel (*) fails with the following D-Bus related messages on the standard error: -- (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:12.770: couldn't list networks: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:28.646: Failed to enable service vino-server: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:54.309: Failed to enable service rygel: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files -- What does this mean? Can I do anything about it? A remote user, sitting in front of the remote computer, can enable Screen Sharing or Media Sharing in gnome-control-center themselves. Failure to enable only occurs over ssh -X, as far as I can tell. Looking up this error online led me down a D-Bus rabbit hole. I found many year-old StackExchange answers that recommend setting various environment variables and/or running dbus-launch to start a session bus instance of dbus-daemon, in case of D-Bus related errors. I am rather unfamiliar with D-Bus, but I can see using ps -ef | grep dbus that a session bus instance of dbus-daemon is already running. It has been started under my UID at the time of my SSH login. So I'm wary of those old resources. I have tried following their instructions though, for completeness sake, but to no avail. I can provide more information if necessary. (*) This odd situation happened when I had to provide technical support over VNC to an older user whose computer I had previously set up with SSH access. Hence why I was using ssh -X to try and enable VNC in gnome-control-center... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1878109/+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 1878109] [NEW] Certain features in the Sharing panel fail with D-Bus related messages when gnome-control-center is run over ssh -X
Public bug reported: When I run gnome-control-center (1:3.36.1-1ubuntu5) on a remote Ubuntu 20.04 host over ssh -X, trying to enable Screen Sharing (VNC) or Media Sharing in the Sharing panel (*) fails with the following D-Bus related messages on the standard error: -- (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:12.770: couldn't list networks: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:28.646: Failed to enable service vino-server: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:54.309: Failed to enable service rygel: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files -- What does this mean? Can I do anything about it? A remote user, sitting in front of the remote computer, can enable Screen Sharing or Media Sharing in gnome-control-center themselves. Failure to enable only occurs over ssh -X, as far as I can tell. Looking up this error online led me down a D-Bus rabbit hole. I found many year-old StackExchange answers that recommend setting various environment variables and/or running dbus-launch to start a session bus instance of dbus-daemon, in case of D-Bus related errors. I am rather unfamiliar with D-Bus, but I can see using ps -ef | grep dbus that a session bus instance of dbus-daemon is already running. It has been started under my UID at the time of my SSH login. So I'm wary of those old resources. I have tried following their instructions though, for completeness sake, but to no avail. I can provide more information if necessary. (*) This odd situation happened when I had to provide technical support over VNC to an older user whose computer I had previously set up with SSH access. Hence why I was using ssh -X to try and enable VNC in gnome- control-center... ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1878109 Title: Certain features in the Sharing panel fail with D-Bus related messages when gnome-control-center is run over ssh -X Status in gnome-control-center package in Ubuntu: New Bug description: When I run gnome-control-center (1:3.36.1-1ubuntu5) on a remote Ubuntu 20.04 host over ssh -X, trying to enable Screen Sharing (VNC) or Media Sharing in the Sharing panel (*) fails with the following D-Bus related messages on the standard error: -- (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:12.770: couldn't list networks: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:28.646: Failed to enable service vino-server: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:54.309: Failed to enable service rygel: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files -- What does this mean? Can I do anything about it? A remote user, sitting in front of the remote computer, can enable Screen Sharing or Media Sharing in gnome-control-center themselves. Failure to enable only occurs over ssh -X, as far as I can tell. Looking up this error online led me down a D-Bus rabbit hole. I found many year-old StackExchange answers that recommend setting various environment variables and/or running dbus-launch to start a session bus instance of dbus-daemon, in case of D-Bus related errors. I am rather unfamiliar with D-Bus, but I can see using ps -ef | grep dbus that a session bus instance of dbus-daemon is already running. It has been started under my UID at the time of my SSH login. So I'm wary of those old resources. I have tried following their instructions though, for completeness sake, but to no avail. I can provide more information if necessary. (*) This odd situation happened when I had to provide technical support over VNC to an older user whose computer I had previously set up with SSH access. Hence why I was using ssh -X to try and enable VNC in gnome-control-center... To
Re: [Desktop-packages] [Bug 1825580] Re: Gnome Online Accounts fails to sign in Exchange emails
Still seeing it on Ubuntu 20.04: Code 6: Unexpected response from server. We did upgrade the version of Exchange used at my work within the last year, but the odd part is setup and use works when I'm on the work network, but not when I work from home (where it used to in versions of Gnome prior, and in the Exchange version prior). Not sure if it is a server issue on my employer's side, a network configuration issue, or a Gnome issue, at this point. On Mon, May 11, 2020 at 6:01 AM Sebastien Bacher wrote: > could you try if that's still an issue in newer Ubuntu series? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1825580 > > Title: > Gnome Online Accounts fails to sign in Exchange emails > > Status in gnome-online-accounts: > New > Status in gnome-online-accounts package in Ubuntu: > Triaged > > Bug description: > After upgrading from 18.10 and/or on fresh install, a known-working > Exchange email setup fails to sign in, giving "Error 7: Unexpected > response from server". Tested the same settings and credentials on a > new install of 18.10 and it worked. > > I have Evolution and Evolution-ews installed on all instances, working > in 18.10, not in 19.04. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: gnome-online-accounts 3.32.0-1ubuntu1 > ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 > Uname: Linux 5.0.0-13-generic x86_64 > ApportVersion: 2.20.10-0ubuntu27 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Fri Apr 19 16:38:32 2019 > InstallationDate: Installed on 2018-03-24 (391 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 > (20180208) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: gnome-online-accounts > UpgradeStatus: Upgraded to disco on 2019-03-12 (38 days ago) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/gnome-online-accounts/+bug/1825580/+subscriptions > -- 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/1825580 Title: Gnome Online Accounts fails to sign in Exchange emails Status in gnome-online-accounts: New Status in gnome-online-accounts package in Ubuntu: Triaged Bug description: After upgrading from 18.10 and/or on fresh install, a known-working Exchange email setup fails to sign in, giving "Error 7: Unexpected response from server". Tested the same settings and credentials on a new install of 18.10 and it worked. I have Evolution and Evolution-ews installed on all instances, working in 18.10, not in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-online-accounts 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 16:38:32 2019 InstallationDate: Installed on 2018-03-24 (391 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to disco on 2019-03-12 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1825580/+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 1877775] Re: Chromium browser not launching after Ubuntu 20 upgrade
Enabling apparmor fixed the problem.I just don't get why I have to have this enabled just to get basic apps working, doesn't make sense. -- 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/185 Title: Chromium browser not launching after Ubuntu 20 upgrade Status in chromium-browser package in Ubuntu: Incomplete Bug description: After successful upgrade from Ubuntu 19.10 to 20 Chromium browser is not launching. Removing re-installing doesn't help. Installing via apt tells that Chromium browser snap exists. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: chromium-browser 80.0.3987.163-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 9 12:50:45 2020 DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/sda4 ext4 164G 2.9G 153G 2% /home tmpfs tmpfs 7.8G 226M 7.6G 3% /dev/shm /dev/sda4 ext4 164G 2.9G 153G 2% /home InstallationDate: Installed on 2020-04-08 (30 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1058:25e2 Western Digital Technologies, Inc. My Passport (WD40NMZW) Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 0bc2:ac41 Seagate RSS LLC BUP Portable Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z370 HD3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=05511df3-f98b-4a65-be14-d202da25b6ee ro quiet splash vt.handoff=7 Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium'] failed with exit code 1: error: no changes found Snap.ChromeDriverVersion: Error: command ['snap', 'run', 'chromium.chromedriver', '--version'] failed with exit code 1: snap-confine has elevated permissions and is not confined but should be. Refusing to continue to avoid permission escalation attacks: Operation not permitted Snap.ChromiumVersion: Error: command ['snap', 'run', 'chromium', '--version'] failed with exit code 1: snap-confine has elevated permissions and is not confined but should be. Refusing to continue to avoid permission escalation attacks: Operation not permitted SourcePackage: chromium-browser UpgradeStatus: Upgraded to focal on 2020-05-09 (0 days ago) dmi.bios.date: 11/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F14b dmi.board.asset.tag: Default string dmi.board.name: Z370 HD3-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.:bvrF14b:bd11/28/2019:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370 HD3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/185/+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 1877776] Re: Ubuntu-Software app is not launching after upgrade to 20
Re-enabling apparmor fixed the problem.I just don't get why I have to have apparmor enabled just to get basic apps working, doesn't make sense. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/186 Title: Ubuntu-Software app is not launching after upgrade to 20 Status in gnome-software package in Ubuntu: Incomplete Bug description: Ubuntu-Software app is not launching after 19.10 to 20 upgrade. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 9 13:19:53 2020 InstallationDate: Installed on 2020-04-08 (30 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.36.0-0ubuntu3 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to focal on 2020-05-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/186/+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 1876292] Re: Error in layout from MS DOCX file, especially after saving as ODT
$ ls -ld /home/ich/.cache/apport/ drwxr-xr-x 2 root root 4096 Jul 10 2018 /home/ich/.cache/apport/ It is empty! -- 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/1876292 Title: Error in layout from MS DOCX file, especially after saving as ODT Status in LibreOffice: Invalid Status in libreoffice package in Ubuntu: Incomplete Bug description: For the details and example file please see: https://bugs.documentfoundation.org/show_bug.cgi?id=132552 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1876292/+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 1878105] [NEW] Xorg crash
Public bug reported: Crash is caused when visiting websites that attempt to customize the cursor layout. (Tested with Firefox 76.0 (64-bit)) The website on which the crash first occurred was the following: https://www.yellibeanz.com/ the crash is triggered after moving the cursor around. To test the hypothesis of the cursor causing the bug I also tested the following website with identical outcome: http://www.flockofsiegel.tv/ I am sure that one can find more examples here: https://onextrapixel.com/10-websites-that-replace-mouse-cursors-for-a -better-cause/ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 11 23:58:41 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Mobile) [1043:1fc0] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1fc0] InstallationDate: Installed on 2020-05-03 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 13d3:56a2 IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X580GD_N580GD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=04dedfb2-c5a9-4447-af72-16999d76fce2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X580GD.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X580GD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX580GD.309:bd10/18/2018:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX580GD_N580GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX580GD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X580GD_N580GD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1878105 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: Crash is caused when visiting websites that attempt to customize the cursor layout. (Tested with Firefox 76.0 (64-bit)) The website on which the crash first occurred was the following:
[Desktop-packages] [Bug 1877821] Re: xorg (Ubuntu) bug reporting guidelines:
** Information type changed from Private Security to Public -- 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/1877821 Title: xorg (Ubuntu) bug reporting guidelines: Status in xorg package in Ubuntu: New Bug description: Please report bugs against xorg with this command: $ ubuntu-bug xorg For more tips on effective bug reporting against Ubuntu Xorg packages, please see http://wiki.ubuntu.com/X/Reporting and thanks ahead of time! Ubuntu bug reporting guidelines: Are you uncertain if your issue is really a bug? Then ask a support question about Ubuntu at http://answers.launchpad.net/ubuntu/ - these can be made into bugs later. Another support venue is http://askubuntu.com. If you are certain this is a bug please include the source package the bug is in. For help see https://wiki.ubuntu.com/Bugs/FindRightPackage. We also need: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 10 06:15:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2020-05-05 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Latitude 5500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=55faf464-9082-49b3-9a16-cab619ffa5a9 ro dis_ucode_ldr quiet splash nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.5 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.5:bd12/26/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101+git2005070630.c997ba~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2005091930.e622e0~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1877821/+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 1877675] Re: Workspaces broken with latest update
It was a gnome config update that came down a couple of days ago. I have two monitors, the left is 1920x1080 rotated left. The monitor on the right is 3440x1440. I use the keyboard bindings ctrl up arrow and down arrow. -- 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/1877675 Title: Workspaces broken with latest update Status in gnome-shell package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: Incomplete Bug description: Multiple workspaces broke with latest gnome config update. Unable to create, or go to different workspaces. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09: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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 8 17:05:52 2020 DistUpgraded: 2020-04-27 21:42:55,589 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1660 Ti] [1458:3fbe] InstallationDate: Installed on 2018-07-01 (677 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6998b6fb-9ba7-4ce9-a023-b36dab34d51a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-28 (10 days ago) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: X470 AORUS ULTRA GAMING-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.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSULTRAGAMING:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSULTRAGAMING-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X470 AORUS ULTRA GAMING 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.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877675/+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 1878059] Re: Audio device not reachable after wake up
there are some known nvidia/hdmi issue with the current kernel, reassigning ** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1878059 Title: Audio device not reachable after wake up Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04, Gnome shell On older Ubuntu releases (<= 19.10), all is working fine. After waking up from suspend mode when I play music or a video, the system changed playing sound at my monitor speakers, detected as „card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]“. Here is the full list: $ LANG=C aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 I can only choose the HDMI device in gnome-control-center or pavucontrol. The other devices are gone, why what ever. When I restart the pulseaudio process, all devices will come back: $ sudo killall -9 pulseaudio # (many times, because pa restarts itself) $ /usr/bin/pulseaudio --daemonize=no --log-target=journal ^Z [1]+ Angehalten /usr/bin/pulseaudio --daemonize=no --log-target=journal $ bg 1 This behavior is new in 20.04. Before I establish the behavior of pulseaudio, I logged off and on again and all devices are shown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878059/+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 1876292] Re: Error in layout from MS DOCX file, especially after saving as ODT
what's the output of * ls -ld /home/ich/.cache/apport/ -- 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/1876292 Title: Error in layout from MS DOCX file, especially after saving as ODT Status in LibreOffice: Invalid Status in libreoffice package in Ubuntu: Incomplete Bug description: For the details and example file please see: https://bugs.documentfoundation.org/show_bug.cgi?id=132552 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1876292/+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 1877427] Re: Double-clicking on a thread does not open the latest message
sorry, can you $ snap refresh --edge thunderbird it should give the current 68.7 version and try if it's an issue there? ** Changed in: thunderbird (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1877427 Title: Double-clicking on a thread does not open the latest message Status in thunderbird package in Ubuntu: New Status in thunderbird package in Debian: New Bug description: When grouping messages by thread and double-clicking on a thread, it should open every message in the thread in a new tab. However, it does not open the latest message and instead opens the first message twice (one time correctly and a second time at the end with a messed up character encoding). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: thunderbird 1:68.7.0+build1-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pierre 1530 F pulseaudio /dev/snd/pcmC0D0p: pierre 1530 F...m pulseaudio BuildID: 20200407160932 Channel: Unavailable CurrentDesktop: XFCE Date: Thu May 7 19:50:11 2020 ExecutablePath: /usr/lib/thunderbird/thunderbird Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-04-06 (1492 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.21 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-70906f39-d462-489a-8cc7-a27970180403 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1141 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=68.7.0/20200407160932 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to eoan on 2019-11-24 (165 days ago) dmi.bios.date: 10/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: W510LU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:svnNotebook:pnW510LU:pvrNotApplicable:rvnNotebook:rnW510LU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W510LU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1877427/+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 1877675] Re: Workspaces broken with latest update
Which update did you install where the issue started? How are configured the monitors? how do you switch workspaces? -- 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/1877675 Title: Workspaces broken with latest update Status in gnome-shell package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: Incomplete Bug description: Multiple workspaces broke with latest gnome config update. Unable to create, or go to different workspaces. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09: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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 8 17:05:52 2020 DistUpgraded: 2020-04-27 21:42:55,589 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1660 Ti] [1458:3fbe] InstallationDate: Installed on 2018-07-01 (677 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6998b6fb-9ba7-4ce9-a023-b36dab34d51a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-28 (10 days ago) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: X470 AORUS ULTRA GAMING-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.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSULTRAGAMING:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSULTRAGAMING-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X470 AORUS ULTRA GAMING 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.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877675/+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 1877705] Re: package libreoffice-help-en-us 1:6.4.2-0ubuntu3 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-ne
I am new to the ubuntu environment. Not sure how to run the report you request. By the way, I have ubuntu 20.04 installed in the Virtualbox latest build. Regards,eddieeleung...@yahoo.com On Monday, May 11, 2020, 02:41:08 p.m. PDT, Sebastien Bacher wrote: thanks, closing the bug report then, it sounds like a download corruption rather than a package bug ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1877705 Title: package libreoffice-help-en-us 1:6.4.2-0ubuntu3 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/en- US/text/swriter/main0503.html.dpkg-new': Operation not permitted Status in libreoffice package in Ubuntu: Invalid Bug description: getting this error when running sudo apt --fix-broken install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-help-en-us 1:6.4.2-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 8 20:39:30 2020 DpkgTerminalLog: Preparing to unpack .../0-libreoffice-help-en-us_1%3a6.4.3-0ubuntu0.20.04.1_all.deb ... Unpacking libreoffice-help-en-us (1:6.4.3-0ubuntu0.20.04.1) over (1:6.4.2-0ubuntu3) ... [1mdpkg:[0m error processing archive /tmp/apt-dpkg-install-w9oOcm/0-libreoffice-help-en-us_1%3a6.4.3-0ubuntu0.20.04.1_all.deb (--unpack): unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-04-29 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: libreoffice Title: package libreoffice-help-en-us 1:6.4.2-0ubuntu3 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1877705/+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/1877705 Title: package libreoffice-help-en-us 1:6.4.2-0ubuntu3 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/en- US/text/swriter/main0503.html.dpkg-new': Operation not permitted Status in libreoffice package in Ubuntu: Invalid Bug description: getting this error when running sudo apt --fix-broken install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-help-en-us 1:6.4.2-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 8 20:39:30 2020 DpkgTerminalLog: Preparing to unpack .../0-libreoffice-help-en-us_1%3a6.4.3-0ubuntu0.20.04.1_all.deb ... Unpacking libreoffice-help-en-us (1:6.4.3-0ubuntu0.20.04.1) over (1:6.4.2-0ubuntu3) ... [1mdpkg:[0m error processing archive /tmp/apt-dpkg-install-w9oOcm/0-libreoffice-help-en-us_1%3a6.4.3-0ubuntu0.20.04.1_all.deb (--unpack): unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-04-29 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: libreoffice Title: package libreoffice-help-en-us 1:6.4.2-0ubuntu3 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1877705/+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 1877746] Re: Lock screen not working
** Information type changed from Private Security to Public Security ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1877746 Title: Lock screen not working Status in gnome-shell package in Ubuntu: New Bug description: The screen will not automatically lock on the specified timer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09: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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 9 08:54:58 2020 DistUpgraded: 2020-04-27 21:42:55,589 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1660 Ti] [1458:3fbe] InstallationDate: Installed on 2018-07-01 (678 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6998b6fb-9ba7-4ce9-a023-b36dab34d51a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-28 (11 days ago) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: X470 AORUS ULTRA GAMING-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.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSULTRAGAMING:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSULTRAGAMING-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X470 AORUS ULTRA GAMING 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.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877746/+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 1878081] Re: dbus-launch of gnome-terminal slow on 20.04
thank you for your bug report, it looks like an issue with xdg-desktop- portal , could you try to temporarly uninstall it to see if workaround the issue? ** Package changed: dbus (Ubuntu) => xdg-desktop-portal (Ubuntu) ** Changed in: xdg-desktop-portal (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1878081 Title: dbus-launch of gnome-terminal slow on 20.04 Status in xdg-desktop-portal package in Ubuntu: New Bug description: Since upgrading to 20.04 I've seen a roughly 20 second delay between running 'dbus-launch gnome-terminal' and when the terminal actually opens. This happens 100% of the time and was basically instant on previous versions (I've tried on 18.04, 19.04, and 19.10). I've tried explicitly unlocking my keyring given the secret error message below and I've verified gnome-terminal-server and dbus-daemon are both running. If I run gnome-terminal without dbus-launch it activates instantly so there's something about the route through dbus that is causing an issue. I get the following output from the dbus-launch invocation: # _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ # watch_fast: "/org/appmenu/gtk-module/" (establishing: 0, active: 0) # unwatch_fast: "/org/appmenu/gtk-module/" (active: 0, establishing: 1) # watch_established: "/org/appmenu/gtk-module/" (establishing: 0) # _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ # watch_fast: "/org/appmenu/gtk-module/" (establishing: 0, active: 0) # unwatch_fast: "/org/appmenu/gtk-module/" (active: 0, establishing: 1) # watch_established: "/org/appmenu/gtk-module/" (establishing: 0) # Failed to use specified server: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.87 was not provided by any .service files # Falling back to default server. # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0) # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1) # watch_established: "/org/gnome/terminal/legacy/" (establishing: 0) And I see the following in syslog during the launch (note the delay in timestamps): May 11 09:15:57 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] AppArmor D-Bus mediation is enabled May 11 09:15:57 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=1000 pid=6298 comm="/usr/bin/gnome-terminal.real " label="unconfined") May 11 09:15:57 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Successfully activated service 'org.gtk.vfs.Daemon' May 11 09:15:57 rfairfax-ubh org.gtk.vfs.Daemon[6310]: fusermount: failed to access mountpoint /run/user/1000/gvfs: Permission denied May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.gnome.Terminal' requested by ':1.0' (uid=1000 pid=6298 comm="/usr/bin/gnome-terminal.real " label="unconfined") May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Successfully activated service 'org.gnome.Terminal' May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.freedesktop.portal.Desktop' requested by ':1.2' (uid=1000 pid=6313 comm="/usr/libexec/gnome-terminal-server " label="unconfined") May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.freedesktop.portal.Documents' requested by ':1.3' (uid=1000 pid=6319 comm="/usr/libexec/xdg-desktop-portal " label="unconfined") May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.4' (uid=1000 pid=6324 comm="/usr/libexec/xdg-document-portal " label="unconfined") May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore' May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Successfully activated service 'org.freedesktop.portal.Documents' May 11 09:15:58 rfairfax-ubh systemd[1]: run-user-1000-doc.mount: Succeeded. May 11 09:15:58 rfairfax-ubh systemd[1108]: run-user-1000-doc.mount: Succeeded. May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.freedesktop.impl.portal.desktop.gtk' requested by ':1.3' (uid=1000 pid=6319 comm="/usr/libexec/xdg-desktop-portal " label="unconfined") May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='ca.desrt.dconf' requested by ':1.6' (uid=1000 pid=6345 comm="/usr/libexec/xdg-desktop-portal-gtk " label="unconfined") May
[Desktop-packages] [Bug 1877847] Re: causes freezeups with zsh related to .histfile.LOCK
*** This bug is a duplicate of bug 1812883 *** https://bugs.launchpad.net/bugs/1812883 Thanks for confirming, then it's a duplicate of bug #1812883, your configuration makes it more inconvenient because the userdir changes more often than the desktop would ** This bug has been marked a duplicate of bug 1812883 Desktop view flashes every time ~/Desktop changes -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1877847 Title: causes freezeups with zsh related to .histfile.LOCK Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: This problem only happens to me when I select the Ubuntu WM, not under Cinnamon. I see it in gnome-terminal. After I enter a command, like "ls" or "cd" into gnome-terminal and press Enter, the desktop icons blink out for a split-second, and while they do, the command does not finish. This makes it annoying for me to work in the command-line, since I'm used to most programs responding immediately. From my experience, it looks like when a program is already running, like Vim, and I ask it to do a disk operation, this "blinking out" and "freezing" does not happen. I'm attaching a video of this happening. I've noticed this line in journalctl -b: Mai 10 13:24:55 agentydragon kernel: mce: CPU3: Package temperature/speed normal Mai 10 13:24:55 agentydragon kernel: mce: CPU1: Package temperature/speed normal Mai 10 13:24:55 agentydragon kernel: mce: CPU2: Package temperature/speed normal Mai 10 13:24:55 agentydragon kernel: mce: CPU0: Package temperature/speed normal Mai 10 13:24:56 agentydragon wpa_supplicant[1011]: wlp4s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-67 noise= txrate=13 Mai 10 13:25:07 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.histfile.LOCK«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:10 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.histfile.LOCK«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:12 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.histfile.LOCK«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:14 agentydragon dbus-daemon[3143]: [session uid=1000 pid=3143] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.1' (uid=1000 pid=3139 comm="/usr/libexec/tracker-miner-fs " label="> Mai 10 13:25:14 agentydragon systemd[3110]: Starting Tracker metadata database store and lookup manager... Mai 10 13:25:14 agentydragon dbus-daemon[3143]: [session uid=1000 pid=3143] Successfully activated service 'org.freedesktop.Tracker1' Mai 10 13:25:14 agentydragon systemd[3110]: Started Tracker metadata database store and lookup manager. Mai 10 13:25:14 agentydragon dbus-daemon[3143]: [session uid=1000 pid=3143] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.1' (uid=1000 pid=3139 comm="/usr/libexec/tracker-mi> Mai 10 13:25:14 agentydragon systemd[3110]: Starting Tracker metadata extractor... Mai 10 13:25:14 agentydragon tracker-extract[49035]: Set scheduler policy to SCHED_IDLE Mai 10 13:25:14 agentydragon tracker-extract[49035]: Setting priority nice level to 19 Mai 10 13:25:14 agentydragon dbus-daemon[3143]: [session uid=1000 pid=3143] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract' Mai 10 13:25:14 agentydragon systemd[3110]: Started Tracker metadata extractor. Mai 10 13:25:15 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.histfile.LOCK«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:18 agentydragon gnome-shell[5836]: JS ERROR: TypeError: fileItem is undefined _updateDesktopIfChanged@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:349:17 _monitorDesktopFolder/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:311:94 Mai 10 13:25:18 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.viminfo.tmp«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:21 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.histfile.LOCK«: Datei oder Verzeichnis nicht gefunden Mai
[Desktop-packages] [Bug 1878091] Re: Non-fractional scaling not working
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1878091 Title: Non-fractional scaling not working Status in gnome-shell package in Ubuntu: New Bug description: My laptop has a 4K display. Default Resolution = 3840x2160, scale = 200%. If I set resolution to 1920x1080, everything on the desktop is scaled to double size. So, if I reduce the Scale setting from 200% to 100%, I would expect everything to look normal again, but it does not. 100% and 200% look identical. However, if I enable Fractional scaling and select 125%, that looks correct. So, Fractional scaling works correctly, but non-fractional scaling does not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 11 15:58:43 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3978] Subsystem: Lenovo GM107M [GeForce GTX 960M] [17aa:3978] InstallationDate: Installed on 2020-05-07 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20349 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=4f7e434e-f524-450c-8486-29302f1ca495 ro persistent quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: K0J40709WIN dmi.board.name: Lenovo Y50-70 Touch dmi.board.vendor: LENOVO dmi.board.version: K0J40709WIN dmi.chassis.asset.tag: K0J40709WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 Touch dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20349:pvrLenovoY50-70Touch:rvnLENOVO:rnLenovoY50-70Touch:rvrK0J40709WIN:cvnLENOVO:ct10:cvrLenovoY50-70Touch: dmi.product.family: IDEAPAD dmi.product.name: 20349 dmi.product.sku: LENOVO_MT_20349_BU_idea_FM_Lenovo Y50-70 Touch dmi.product.version: Lenovo Y50-70 Touch dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878091/+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 1878081] [NEW] dbus-launch of gnome-terminal slow on 20.04
You have been subscribed to a public bug: Since upgrading to 20.04 I've seen a roughly 20 second delay between running 'dbus-launch gnome-terminal' and when the terminal actually opens. This happens 100% of the time and was basically instant on previous versions (I've tried on 18.04, 19.04, and 19.10). I've tried explicitly unlocking my keyring given the secret error message below and I've verified gnome-terminal-server and dbus-daemon are both running. If I run gnome-terminal without dbus-launch it activates instantly so there's something about the route through dbus that is causing an issue. I get the following output from the dbus-launch invocation: # _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ # watch_fast: "/org/appmenu/gtk-module/" (establishing: 0, active: 0) # unwatch_fast: "/org/appmenu/gtk-module/" (active: 0, establishing: 1) # watch_established: "/org/appmenu/gtk-module/" (establishing: 0) # _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ # watch_fast: "/org/appmenu/gtk-module/" (establishing: 0, active: 0) # unwatch_fast: "/org/appmenu/gtk-module/" (active: 0, establishing: 1) # watch_established: "/org/appmenu/gtk-module/" (establishing: 0) # Failed to use specified server: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.87 was not provided by any .service files # Falling back to default server. # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0) # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1) # watch_established: "/org/gnome/terminal/legacy/" (establishing: 0) And I see the following in syslog during the launch (note the delay in timestamps): May 11 09:15:57 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] AppArmor D-Bus mediation is enabled May 11 09:15:57 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=1000 pid=6298 comm="/usr/bin/gnome-terminal.real " label="unconfined") May 11 09:15:57 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Successfully activated service 'org.gtk.vfs.Daemon' May 11 09:15:57 rfairfax-ubh org.gtk.vfs.Daemon[6310]: fusermount: failed to access mountpoint /run/user/1000/gvfs: Permission denied May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.gnome.Terminal' requested by ':1.0' (uid=1000 pid=6298 comm="/usr/bin/gnome-terminal.real " label="unconfined") May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Successfully activated service 'org.gnome.Terminal' May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.freedesktop.portal.Desktop' requested by ':1.2' (uid=1000 pid=6313 comm="/usr/libexec/gnome-terminal-server " label="unconfined") May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.freedesktop.portal.Documents' requested by ':1.3' (uid=1000 pid=6319 comm="/usr/libexec/xdg-desktop-portal " label="unconfined") May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.4' (uid=1000 pid=6324 comm="/usr/libexec/xdg-document-portal " label="unconfined") May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore' May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Successfully activated service 'org.freedesktop.portal.Documents' May 11 09:15:58 rfairfax-ubh systemd[1]: run-user-1000-doc.mount: Succeeded. May 11 09:15:58 rfairfax-ubh systemd[1108]: run-user-1000-doc.mount: Succeeded. May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.freedesktop.impl.portal.desktop.gtk' requested by ':1.3' (uid=1000 pid=6319 comm="/usr/libexec/xdg-desktop-portal " label="unconfined") May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='ca.desrt.dconf' requested by ':1.6' (uid=1000 pid=6345 comm="/usr/libexec/xdg-desktop-portal-gtk " label="unconfined") May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Successfully activated service 'ca.desrt.dconf' May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Successfully activated service 'org.freedesktop.impl.portal.desktop.gtk' May 11 09:15:58 rfairfax-ubh dbus-daemon[6297]: [session uid=1000 pid=6295] Activating service name='org.freedesktop.secrets' requested by ':1.3' (uid=1000 pid=6319 comm="/usr/libexec/xdg-desktop-portal " label="unconfined") May 11 09:15:58 rfairfax-ubh org.freedesktop.secrets[6359]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh May 11 09:16:23 rfairfax-ubh
[Desktop-packages] [Bug 1878094] Re: Ubuntu 20.04 / Pulseaudio RTP receive broken sound
Thank you for your bug report, that's likely an upstream issue, could you report it there? https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/ ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low -- 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/1878094 Title: Ubuntu 20.04 / Pulseaudio RTP receive broken sound Status in pulseaudio package in Ubuntu: New Bug description: just upgraded some of my computers to Ubuntu 20.04, also tried with fresh install, in all case the pulseaudio rtp receive module is giving me very poor sound. Easily reproducible on a single machine : pacmd load-module module-null-sink sink_name=MyNullSink pacmd load-module module-rtp-send source=MyNullSink.monitor loop=true pacmd load-module module-rtp-recv And then play something in the null sink, loopback sound will be bad (lags). What I noticed : if I open the rtp stream with vlc, it's ok, sound is good. Ubuntu 20 uses PulseAudio 13.99, aka (I guess) PulseAudio 14 which implements RTP through gstreamer, which is new. So I tested my rtp stream with gstreamer: gst-launch-1.0 udpsrc address=224.0.0.56 port=46586 caps="application/x-rtp, media=audio, payload=10, clock-rate=44100" ! .recv_rtp_sink_0 rtpbin ! rtpL16depay ! audioconvert ! audioresample ! pulsesink And it works fine, so I definitively believe there is an issue in the new module-rtp-recv.so bundled with PulseAudio and that is now based on gstreamer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-id', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 11 22:22:55 2020 InstallationDate: Installed on 2019-03-31 (407 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-05-09 (2 days ago) dmi.bios.date: 09/13/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1404 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX H370-I GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1404:bd09/13/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXH370-IGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] modified.conffile..etc.pulse.system.pa: [modified] modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [deleted] mtime.conffile..etc.pulse.daemon.conf: 2020-05-10T12:17:27.278185 mtime.conffile..etc.pulse.default.pa: 2020-05-10T12:13:15.278817 mtime.conffile..etc.pulse.system.pa: 2020-05-11T16:24:47.654012 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878094/+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 1877705] Re: package libreoffice-help-en-us 1:6.4.2-0ubuntu3 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new':
thanks, closing the bug report then, it sounds like a download corruption rather than a package bug ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Invalid -- 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/1877705 Title: package libreoffice-help-en-us 1:6.4.2-0ubuntu3 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/en- US/text/swriter/main0503.html.dpkg-new': Operation not permitted Status in libreoffice package in Ubuntu: Invalid Bug description: getting this error when running sudo apt --fix-broken install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-help-en-us 1:6.4.2-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 8 20:39:30 2020 DpkgTerminalLog: Preparing to unpack .../0-libreoffice-help-en-us_1%3a6.4.3-0ubuntu0.20.04.1_all.deb ... Unpacking libreoffice-help-en-us (1:6.4.3-0ubuntu0.20.04.1) over (1:6.4.2-0ubuntu3) ... [1mdpkg:[0m error processing archive /tmp/apt-dpkg-install-w9oOcm/0-libreoffice-help-en-us_1%3a6.4.3-0ubuntu0.20.04.1_all.deb (--unpack): unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-04-29 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: libreoffice Title: package libreoffice-help-en-us 1:6.4.2-0ubuntu3 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1877705/+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 1877725] Re: Displays aberrant percentages for disks belonging to btrfs RAID volume
** Also affects: gnome-disk-utility via https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/24 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1877725 Title: Displays aberrant percentages for disks belonging to btrfs RAID volume Status in GNOME Disks: Unknown Status in gnome-disk-utility package in Ubuntu: Triaged Bug description: Hi, when I use gnome-disks to display information about disks that belong to a btrfs RAID volume, I see percentages that are way above 100% (see screenshot below). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-disk-utility 3.36.1-1ubuntu1 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 11:18:26 2020 SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1877725/+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 1878100] [NEW] latex compilation fails with included graphics
Public bug reported: The following very simple file (test.tex) fails to compile using pdflatex \documentclass{article} \usepackage{graphicx} \begin{document} text \begin{figure}[tbp] \centering \includegraphics[width=0.7\textwidth]{ubndens} \caption{test} \label{fig:test} \end{figure} \end{document} The error message is Runaway argument? "ubndens.eps" \edef \Gin@ext {\Gin@temp }\fi \def \Gin@temp {.ps}\ifx \ETC. ! Paragraph ended before \@tempa was complete. \par l.24 ? latex files with no included graphics compile fine. The graphics file is attached. This problem was seen in other texlive distributions recently (miktex for example) so the problem is likely upstream and might be solved by pulling a more recent texlive distribution such as is done with a ppa. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: texlive-full 2019.20200218-1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Mon May 11 17:19:18 2020 InstallationDate: Installed on 2019-03-26 (412 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: texlive-base UpgradeStatus: Upgraded to focal on 2020-04-12 (29 days ago) ** Affects: texlive-base (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "Graphics file needed" https://bugs.launchpad.net/bugs/1878100/+attachment/5370071/+files/ubndens.eps -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1878100 Title: latex compilation fails with included graphics Status in texlive-base package in Ubuntu: New Bug description: The following very simple file (test.tex) fails to compile using pdflatex \documentclass{article} \usepackage{graphicx} \begin{document} text \begin{figure}[tbp] \centering \includegraphics[width=0.7\textwidth]{ubndens} \caption{test} \label{fig:test} \end{figure} \end{document} The error message is Runaway argument? "ubndens.eps" \edef \Gin@ext {\Gin@temp }\fi \def \Gin@temp {.ps}\ifx \ETC. ! Paragraph ended before \@tempa was complete. \par l.24 ? latex files with no included graphics compile fine. The graphics file is attached. This problem was seen in other texlive distributions recently (miktex for example) so the problem is likely upstream and might be solved by pulling a more recent texlive distribution such as is done with a ppa. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: texlive-full 2019.20200218-1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Mon May 11 17:19:18 2020 InstallationDate: Installed on 2019-03-26 (412 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: texlive-base UpgradeStatus: Upgraded to focal on 2020-04-12 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1878100/+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 1877705] Re: package libreoffice-help-en-us 1:6.4.2-0ubuntu3 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-ne
Thanks for the following up. The issue is now resolved. I rerun the update a few days afterward and it seems it is working now. Thanks,eddieeleung...@yahoo.com On Monday, May 11, 2020, 09:05:53 a.m. PDT, Sebastien Bacher wrote: Thank you for your bug report, do you have issues with other softwares? Could you check the disk and memory for errors? It looks like some sort of local corruption ** Changed in: libreoffice (Ubuntu) Importance: Undecided => Low ** Changed in: libreoffice (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1877705 Title: package libreoffice-help-en-us 1:6.4.2-0ubuntu3 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/en- US/text/swriter/main0503.html.dpkg-new': Operation not permitted Status in libreoffice package in Ubuntu: Incomplete Bug description: getting this error when running sudo apt --fix-broken install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-help-en-us 1:6.4.2-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 8 20:39:30 2020 DpkgTerminalLog: Preparing to unpack .../0-libreoffice-help-en-us_1%3a6.4.3-0ubuntu0.20.04.1_all.deb ... Unpacking libreoffice-help-en-us (1:6.4.3-0ubuntu0.20.04.1) over (1:6.4.2-0ubuntu3) ... [1mdpkg:[0m error processing archive /tmp/apt-dpkg-install-w9oOcm/0-libreoffice-help-en-us_1%3a6.4.3-0ubuntu0.20.04.1_all.deb (--unpack): unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-04-29 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: libreoffice Title: package libreoffice-help-en-us 1:6.4.2-0ubuntu3 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1877705/+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/1877705 Title: package libreoffice-help-en-us 1:6.4.2-0ubuntu3 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/en- US/text/swriter/main0503.html.dpkg-new': Operation not permitted Status in libreoffice package in Ubuntu: Incomplete Bug description: getting this error when running sudo apt --fix-broken install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-help-en-us 1:6.4.2-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 8 20:39:30 2020 DpkgTerminalLog: Preparing to unpack .../0-libreoffice-help-en-us_1%3a6.4.3-0ubuntu0.20.04.1_all.deb ... Unpacking libreoffice-help-en-us (1:6.4.3-0ubuntu0.20.04.1) over (1:6.4.2-0ubuntu3) ... [1mdpkg:[0m error processing archive /tmp/apt-dpkg-install-w9oOcm/0-libreoffice-help-en-us_1%3a6.4.3-0ubuntu0.20.04.1_all.deb (--unpack): unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-04-29 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: libreoffice Title: package libreoffice-help-en-us 1:6.4.2-0ubuntu3 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1877705/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1878095] [NEW] Uninstallation leads to broken system
Public bug reported: Steps to reproduce: - Have Ubuntu installed. - Install lightdm. This makes lightdm the active window manager, as far as I can remember. - Uninstall lightdm. - Reboot. Expected result: - System booting another available window manager (gdm3 in this case). - At very least an error message about something being broken (might belong to another package). Actual result: - System boots, but doesn't proceed up to visible graphics -> blank, black screen. Diagnosis: - One can still switch to a text console using Ctrl-Alt-F1..F4 - /etc contains a broken link (took me 2 full days to find that): $ ls -l /etc/systemd/system/display-manager.service ... /etc/systemd/system/display-manager.service -> /lib/systemd/system/lightdm.service Manual fix: $ cd /etc/systemd/system $ sudo ln -sf /lib/systemd/system/gdm3.service display-manager.service Suggested fix: - lightdm making another window manager active on uninstallation, just like it becomes the active manager on installation. - Printing a big ERROR message if there is no other window manager installed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 11 22:18:02 2020 InstallationDate: Installed on 2016-05-04 (1468 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: Upgraded to focal on 2020-05-03 (7 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1878095 Title: Uninstallation leads to broken system Status in lightdm package in Ubuntu: New Bug description: Steps to reproduce: - Have Ubuntu installed. - Install lightdm. This makes lightdm the active window manager, as far as I can remember. - Uninstall lightdm. - Reboot. Expected result: - System booting another available window manager (gdm3 in this case). - At very least an error message about something being broken (might belong to another package). Actual result: - System boots, but doesn't proceed up to visible graphics -> blank, black screen. Diagnosis: - One can still switch to a text console using Ctrl-Alt-F1..F4 - /etc contains a broken link (took me 2 full days to find that): $ ls -l /etc/systemd/system/display-manager.service ... /etc/systemd/system/display-manager.service -> /lib/systemd/system/lightdm.service Manual fix: $ cd /etc/systemd/system $ sudo ln -sf /lib/systemd/system/gdm3.service display-manager.service Suggested fix: - lightdm making another window manager active on uninstallation, just like it becomes the active manager on installation. - Printing a big ERROR message if there is no other window manager installed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 11 22:18:02 2020 InstallationDate: Installed on 2016-05-04 (1468 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: Upgraded to focal on 2020-05-03 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1878095/+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 1878094] [NEW] Ubuntu 20.04 / Pulseaudio RTP receive broken sound
Public bug reported: just upgraded some of my computers to Ubuntu 20.04, also tried with fresh install, in all case the pulseaudio rtp receive module is giving me very poor sound. Easily reproducible on a single machine : pacmd load-module module-null-sink sink_name=MyNullSink pacmd load-module module-rtp-send source=MyNullSink.monitor loop=true pacmd load-module module-rtp-recv And then play something in the null sink, loopback sound will be bad (lags). What I noticed : if I open the rtp stream with vlc, it's ok, sound is good. Ubuntu 20 uses PulseAudio 13.99, aka (I guess) PulseAudio 14 which implements RTP through gstreamer, which is new. So I tested my rtp stream with gstreamer: gst-launch-1.0 udpsrc address=224.0.0.56 port=46586 caps="application/x-rtp, media=audio, payload=10, clock-rate=44100" ! .recv_rtp_sink_0 rtpbin ! rtpL16depay ! audioconvert ! audioresample ! pulsesink And it works fine, so I definitively believe there is an issue in the new module-rtp-recv.so bundled with PulseAudio and that is now based on gstreamer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-id', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 11 22:22:55 2020 InstallationDate: Installed on 2019-03-31 (407 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-05-09 (2 days ago) dmi.bios.date: 09/13/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1404 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX H370-I GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1404:bd09/13/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXH370-IGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] modified.conffile..etc.pulse.system.pa: [modified] modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [deleted] mtime.conffile..etc.pulse.daemon.conf: 2020-05-10T12:17:27.278185 mtime.conffile..etc.pulse.default.pa: 2020-05-10T12:13:15.278817 mtime.conffile..etc.pulse.system.pa: 2020-05-11T16:24:47.654012 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1878094 Title: Ubuntu 20.04 / Pulseaudio RTP receive broken sound Status in pulseaudio package in Ubuntu: New Bug description: just upgraded some of my computers to Ubuntu 20.04, also tried with fresh install, in all case the pulseaudio rtp receive module is giving me very poor sound. Easily reproducible on a single machine : pacmd load-module module-null-sink sink_name=MyNullSink pacmd load-module module-rtp-send source=MyNullSink.monitor loop=true pacmd load-module module-rtp-recv And then play something in the null sink, loopback sound will be bad (lags). What I noticed : if I open the rtp stream with vlc, it's ok, sound is good. Ubuntu 20 uses PulseAudio 13.99, aka (I guess) PulseAudio 14 which implements RTP through gstreamer, which is new. So I tested my rtp stream with gstreamer: gst-launch-1.0 udpsrc address=224.0.0.56 port=46586 caps="application/x-rtp, media=audio, payload=10, clock-rate=44100" ! .recv_rtp_sink_0 rtpbin ! rtpL16depay ! audioconvert ! audioresample ! pulsesink And it works fine, so I definitively believe there is an issue in the new module-rtp-recv.so bundled with PulseAudio and that is now based on gstreamer.
[Desktop-packages] [Bug 1877601] Re: /usr/share/alsa missing within snap
So in general it is not possible to connect an interface which the snap didn’t request? If not, sounds like a powerful feature to add. Forcing a custom interface on a snap can be used to affect its filesystem in the desired way. -- 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/1877601 Title: /usr/share/alsa missing within snap Status in chromium-browser package in Ubuntu: Incomplete Bug description: $ ls /snap/chromium/current/usr/share/alsa alsa.conf alsa.conf.d cards pcm pulse-alsa.conf smixer.conf sndo-mixer.alisp topology ucm $ sudo nsenter -m -t $(pgrep --oldest chromium) ls /usr/share/alsa ls: cannot access '/usr/share/alsa': No such file or directory For this reason there’s no sound. How to make sure that /usr/share/alsa which is present in the snap does not somehow go missing when the snap runs? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1877601/+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 1878091] [NEW] Non-fractional scaling not working
Public bug reported: My laptop has a 4K display. Default Resolution = 3840x2160, scale = 200%. If I set resolution to 1920x1080, everything on the desktop is scaled to double size. So, if I reduce the Scale setting from 200% to 100%, I would expect everything to look normal again, but it does not. 100% and 200% look identical. However, if I enable Fractional scaling and select 125%, that looks correct. So, Fractional scaling works correctly, but non-fractional scaling does not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 11 15:58:43 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3978] Subsystem: Lenovo GM107M [GeForce GTX 960M] [17aa:3978] InstallationDate: Installed on 2020-05-07 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20349 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=4f7e434e-f524-450c-8486-29302f1ca495 ro persistent quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: K0J40709WIN dmi.board.name: Lenovo Y50-70 Touch dmi.board.vendor: LENOVO dmi.board.version: K0J40709WIN dmi.chassis.asset.tag: K0J40709WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 Touch dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20349:pvrLenovoY50-70Touch:rvnLENOVO:rnLenovoY50-70Touch:rvrK0J40709WIN:cvnLENOVO:ct10:cvrLenovoY50-70Touch: dmi.product.family: IDEAPAD dmi.product.name: 20349 dmi.product.sku: LENOVO_MT_20349_BU_idea_FM_Lenovo Y50-70 Touch dmi.product.version: Lenovo Y50-70 Touch dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Summary changed: - Non-ractional scaling not working + Non-fractional scaling not working -- 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/1878091 Title: Non-fractional scaling not working Status in xorg package in Ubuntu: New Bug description: My laptop has a 4K display. Default Resolution = 3840x2160, scale = 200%. If I set resolution to 1920x1080, everything on the desktop is scaled to double size. So, if I reduce the Scale setting from 200% to 100%, I would expect everything to look normal again, but it does not. 100% and 200% look identical. However, if I enable Fractional scaling and select 125%, that looks correct. So, Fractional scaling works correctly, but non-fractional scaling does not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend
[Desktop-packages] [Bug 1877601] Re: /usr/share/alsa missing within snap
The chromium snaps need work, it's not something you can do now -- 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/1877601 Title: /usr/share/alsa missing within snap Status in chromium-browser package in Ubuntu: Incomplete Bug description: $ ls /snap/chromium/current/usr/share/alsa alsa.conf alsa.conf.d cards pcm pulse-alsa.conf smixer.conf sndo-mixer.alisp topology ucm $ sudo nsenter -m -t $(pgrep --oldest chromium) ls /usr/share/alsa ls: cannot access '/usr/share/alsa': No such file or directory For this reason there’s no sound. How to make sure that /usr/share/alsa which is present in the snap does not somehow go missing when the snap runs? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1877601/+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 1877528] Re: Applet does not terminate at end of X desktop session
** Changed in: system-config-printer (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1877528 Title: Applet does not terminate at end of X desktop session Status in System Config Printer: New Status in system-config-printer package in Ubuntu: Triaged Bug description: This concerns system-config-printer 1.5.12-0ubuntu1 in Ubuntu focal. I log into the Xfce desktop, and then logout. The screen returns to the LightDM login screen. A few minutes later, "loginctl list-sessions" shows the following: SESSION UID USERSEAT TTY 90 root c2 1000 skunk seat0 c3 116 lightdm seat0 3 sessions listed. Output from "loginctl session-status c2": c2 - skunk (1000) Since: Fri 2020-05-08 03:09:05 EDT; 9min ago Leader: 2530 Seat: seat0; vc7 Display: :0 Service: lightdm; type x11; class user Desktop: xubuntu State: closing Unit: session-c2.scope └─2856 /usr/bin/python3 /usr/share/system-config-printer/applet.py This process sticks around forever until I kill it, or its parent "systemd --user" process. Only then does the session disappear from list-sessions. When I run "session-status" while I'm logged in, I see a list of nearly 30 desktop-related processes. All of them except this one go away on logout. This one should too. To manage notifications about this bug go to: https://bugs.launchpad.net/system-config-printer/+bug/1877528/+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 1878065] Re: Sync onboard 1.4.1-5 (universe) from Debian unstable (main)
This bug was fixed in the package onboard - 1.4.1-5 Sponsored for Amr Ibrahim (amribrahim1987) --- onboard (1.4.1-5) unstable; urgency=medium [ Mike Gabriel ] * debian/control: + Bump Standards-Version: to 4.4.1. No changes needed. + Add Rules-Requires-Root: field and set it to no. + Don't build gnome-shell-extension-onboard anymore. It is broken with recent GNONME and there is no feedback from upstream about the future perspective of the shell extension. NOTE: for now, this is a temporary measure until the Debian maintainer has received feedback from Onboard upstream about this. + Enforce removal of gnome-shell-extension-onboard via B:/R: when upgrading onboard to this package version. (Closes: #891236). + Switch to debhelper-compat notation. Bump DH compat level to version 12. * debian/rules: + Switch from dh_install --fail-missing to dh_missing override. + Don't install gnome-shell extension files for Onboard anymore. * debian/copyright: + Drop COPYING file. Thanks, lintian. [ Balint Reczey ] * debian/patches: + Add 0001-Replace-invalid-UTF-8-characters-in-ACPI-events.patch. Resolves UnicodeDecodeError in AcpidListener. (Closes: #936019, LP:#1808446). + Add 1003_disable_onboard_on_gnome.patch. Disable onboard on GNOME. (Closes: #931961, LP:#1721125). -- Mike Gabriel Thu, 09 Jan 2020 11:26:40 +0100 onboard (1.4.1-4) unstable; urgency=medium * debian/control: + Drop pkg-mate-team Alioth mailing list from Uploaders: field. + One uploader per line... + Bump Standards-Version: to 4.2.0. No changes needed. * debian/copyright: + Use secure URL in Source: field. -- Mike Gabriel Wed, 22 Aug 2018 12:09:38 +0200 onboard (1.4.1-3) unstable; urgency=medium [ Vangelis Mouhtsis ] * debian/control: + Rename pretty name of our team -> Debian+Ubuntu MATE Packaging Team. + Update Maintainer: field to debian-mate ML on lists.debian.org. + Add myself to Uploaders: field. + Temporarily have pkg-mate-team ML under Uploaders:. [ Mike Gabriel ] * debian/copyright: + Use secure URI for copyright format. + Update Vcs-*: fields. Package has been migrated to salsa.debian.org. + Bump Standards-Version: to 4.1.4. No changes needed. + Switch R from gir1.2-appindicator3-0.1 to gir1.2-ayatanaappindicator3-0.1. * debian/patches: + Add 1002_build-against-Ayatana-AppIndicator.patch. -- Mike Gabriel Fri, 11 May 2018 13:37:23 +0200 ** Changed in: onboard (Ubuntu) Importance: Undecided => Wishlist ** Changed in: onboard (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1878065 Title: Sync onboard 1.4.1-5 (universe) from Debian unstable (main) Status in onboard package in Ubuntu: Fix Released Bug description: Please sync onboard 1.4.1-5 (universe) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Replace invalid UTF-8 characters in ACPI events (LP: #1808446) [ Andrea Azzarone ] * debian/patches/1002_disable_onboard_on_gnome.patch: - don't enable onboard in GNOME sessions since caribou is being used and it leads to have two onscreen keyboards loaded at the same time (lp: #1721125) All the Ubuntu changes are now in Debian. Changelog entries since current groovy version 1.4.1-2ubuntu7: onboard (1.4.1-5) unstable; urgency=medium [ Mike Gabriel ] * debian/control: + Bump Standards-Version: to 4.4.1. No changes needed. + Add Rules-Requires-Root: field and set it to no. + Don't build gnome-shell-extension-onboard anymore. It is broken with recent GNONME and there is no feedback from upstream about the future perspective of the shell extension. NOTE: for now, this is a temporary measure until the Debian maintainer has received feedback from Onboard upstream about this. + Enforce removal of gnome-shell-extension-onboard via B:/R: when upgrading onboard to this package version. (Closes: #891236). + Switch to debhelper-compat notation. Bump DH compat level to version 12. * debian/rules: + Switch from dh_install --fail-missing to dh_missing override. + Don't install gnome-shell extension files for Onboard anymore. * debian/copyright: + Drop COPYING file. Thanks, lintian. [ Balint Reczey ] * debian/patches: + Add 0001-Replace-invalid-UTF-8-characters-in-ACPI-events.patch. Resolves UnicodeDecodeError in AcpidListener. (Closes: #936019, LP: #1808446). + Add 1003_disable_onboard_on_gnome.patch. Disable onboard on GNOME. (Closes: #931961, LP: #1721125). -- Mike Gabriel Thu, 09 Jan 2020 11:26:40 +0100 onboard (1.4.1-4) unstable; urgency=medium * debian/control:
[Desktop-packages] [Bug 1878026] Re: [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] No sound at all
Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: alsa-driver (Ubuntu) Importance: Undecided => Low ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- 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/1878026 Title: [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: There is no sound at all. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: abhi 1362 F pulseaudio /dev/snd/controlC0: abhi 1362 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 11 20:31:56 2020 InstallationDate: Installed on 2020-05-06 (5 days ago) InstallationMedia: It PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: abhi 1362 F pulseaudio /dev/snd/controlC0: abhi 1362 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2281 dmi.board.vendor: Hewlett-Packard dmi.board.version: 77.13 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd06/11/2014:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr097610405F1610180:rvnHewlett-Packard:rn2281:rvr77.13:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.sku: G8D90PA#ACJ dmi.product.version: 097610405F1610180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1878026/+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 1878080] Re: HPLIP fails to install working printer and scanner drivers.
Thank you for your bug report, could you add the journalctl log from the session where you installed the driver and include a screenshot showing the issue? ** Changed in: hplip (Ubuntu) Importance: Undecided => Low ** Changed in: hplip (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1878080 Title: HPLIP fails to install working printer and scanner drivers. Status in hplip package in Ubuntu: Incomplete Bug description: When using HPLIP to install drivers for HP ENVY 5530 e-All-in-One Printer, the software correctly detects and tries to install the printer driver. However, launching the printer window using printer icon in the system tray shows a printer with a red x and a message that says printer drivers install incomplete(?). Only a small subset of functions are listed for the printer (thus consistent with the incomplete message). Although HPLIP detects the correct printer, printing fails. Also, when launching scanlite, user is prompted with 4 flavors for envy 5530 scanner connections, but only one of them works correctly. None of these issues existed in 18.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hplip 3.20.3+dfsg0-2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: E [11/May/2020:07:15:37 -0600] [Client 4] Returning IPP client-error-bad-request for Create-Printer-Subscriptions (/) from localhost. CurrentDesktop: KDE Date: Mon May 11 09:30:27 2020 InstallationDate: Installed on 2019-06-15 (331 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for Brother_HL-2170W_series: dnssd://Brother%20HL-2170W%20series._pdl-datastream._tcp.local/ MachineType: ASUS All Series Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Brother_HL-2170W_series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Brother_HL-2170W_series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=2846c5c0-4d72-429f-959a-1f08f0454389 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: Upgraded to focal on 2020-03-26 (45 days ago) dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO 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.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx: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/ubuntu/+source/hplip/+bug/1878080/+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 1878050] Re: Nvidia GT 240m gives problems
Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1878050 Title: Nvidia GT 240m gives problems Status in xorg package in Ubuntu: Incomplete Bug description: Can't install proprietary NVIDIA driver 340.107 X uses software rendering rather than hardware ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-178.208-generic 4.4.217 Uname: Linux 4.4.0-178-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon May 11 18:41:34 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-178-generic, x86_64: installed virtualbox, 5.1.38, 4.4.0-148-generic, x86_64: installed virtualbox, 5.1.38, 4.4.0-178-generic, x86_64: installed virtualbox, 5.1.38, 4.4.0-98-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 240M] [10de:0a34] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GT216M [GeForce GT 240M] [10de:0688] InstallationDate: Installed on 2017-09-18 (965 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Acer Aspire Z5610 ProcEnviron: LANGUAGE=nl_BE:nl PATH=(custom, no user) LANG=nl_BE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-178-generic root=UUID=398c17c4-3b3b-4a56-92f8-6f6a37b9eee1 ro nomodeset quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/19/2010 dmi.bios.vendor: Phoenix dmi.bios.version: P01-B2L dmi.board.name: Aspire Z5610 dmi.board.vendor: Acer dmi.chassis.type: 13 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnPhoenix:bvrP01-B2L:bd01/19/2010:svnAcer:pnAspireZ5610:pvr:rvnAcer:rnAspireZ5610:rvr:cvnAcer:ct13:cvr: dmi.product.name: Aspire Z5610 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon May 11 18:16:46 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1878050/+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 1877847] Re: causes freezeups with zsh related to .histfile.LOCK
Hi. I don't like having folders like Desktop, Pictures, Videos, etc. in my home, so I have overrides in ~/.config/user-dirs.dirs: XDG_DESKTOP_DIR="$HOME" XDG_DOWNLOAD_DIR="$HOME/downloads" XDG_TEMPLATES_DIR="$HOME" XDG_PUBLICSHARE_DIR="$HOME" XDG_DOCUMENTS_DIR="$HOME" XDG_MUSIC_DIR="$HOME" XDG_PICTURES_DIR="$HOME" XDG_VIDEOS_DIR="$HOME" So basically my desktop dir is the same as my home dir (/home/agentydragon), so it makes sense that desktop icons would be interested in .histfile.LOCK appearing in there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1877847 Title: causes freezeups with zsh related to .histfile.LOCK Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: This problem only happens to me when I select the Ubuntu WM, not under Cinnamon. I see it in gnome-terminal. After I enter a command, like "ls" or "cd" into gnome-terminal and press Enter, the desktop icons blink out for a split-second, and while they do, the command does not finish. This makes it annoying for me to work in the command-line, since I'm used to most programs responding immediately. From my experience, it looks like when a program is already running, like Vim, and I ask it to do a disk operation, this "blinking out" and "freezing" does not happen. I'm attaching a video of this happening. I've noticed this line in journalctl -b: Mai 10 13:24:55 agentydragon kernel: mce: CPU3: Package temperature/speed normal Mai 10 13:24:55 agentydragon kernel: mce: CPU1: Package temperature/speed normal Mai 10 13:24:55 agentydragon kernel: mce: CPU2: Package temperature/speed normal Mai 10 13:24:55 agentydragon kernel: mce: CPU0: Package temperature/speed normal Mai 10 13:24:56 agentydragon wpa_supplicant[1011]: wlp4s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-67 noise= txrate=13 Mai 10 13:25:07 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.histfile.LOCK«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:10 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.histfile.LOCK«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:12 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.histfile.LOCK«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:14 agentydragon dbus-daemon[3143]: [session uid=1000 pid=3143] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.1' (uid=1000 pid=3139 comm="/usr/libexec/tracker-miner-fs " label="> Mai 10 13:25:14 agentydragon systemd[3110]: Starting Tracker metadata database store and lookup manager... Mai 10 13:25:14 agentydragon dbus-daemon[3143]: [session uid=1000 pid=3143] Successfully activated service 'org.freedesktop.Tracker1' Mai 10 13:25:14 agentydragon systemd[3110]: Started Tracker metadata database store and lookup manager. Mai 10 13:25:14 agentydragon dbus-daemon[3143]: [session uid=1000 pid=3143] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.1' (uid=1000 pid=3139 comm="/usr/libexec/tracker-mi> Mai 10 13:25:14 agentydragon systemd[3110]: Starting Tracker metadata extractor... Mai 10 13:25:14 agentydragon tracker-extract[49035]: Set scheduler policy to SCHED_IDLE Mai 10 13:25:14 agentydragon tracker-extract[49035]: Setting priority nice level to 19 Mai 10 13:25:14 agentydragon dbus-daemon[3143]: [session uid=1000 pid=3143] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract' Mai 10 13:25:14 agentydragon systemd[3110]: Started Tracker metadata extractor. Mai 10 13:25:15 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.histfile.LOCK«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:18 agentydragon gnome-shell[5836]: JS ERROR: TypeError: fileItem is undefined _updateDesktopIfChanged@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:349:17 _monitorDesktopFolder/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:311:94 Mai 10 13:25:18 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.viminfo.tmp«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:21 agentydragon gnome-shell[5836]: Error getting desktop unix mode:
[Desktop-packages] [Bug 1877985] Re: I can't see folder
User has been removed from Launchpad so closing. ** Changed in: yaru-theme (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1877985 Title: I can't see folder Status in yaru-theme package in Ubuntu: Invalid Bug description: I can't see folder. :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1877985/+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 1877957] Re: Package fonts-noto-cjk seems to be corrupt in 20.04
Thank you for the advice, that fixed my issue. ** Changed in: fonts-noto-cjk (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-cjk in Ubuntu. https://bugs.launchpad.net/bugs/1877957 Title: Package fonts-noto-cjk seems to be corrupt in 20.04 Status in fonts-noto-cjk package in Ubuntu: Invalid Bug description: I just upgraded to Ubuntu Budgie 20.04 from 19.10 and this package refused to update. After uninstalling it and attempting to reinstall it I received the following: cameron@cameron-M14xR2:~$ sudo apt-get install fonts-noto-cjk [sudo] password for cameron: Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: fonts-noto-cjk-extra The following NEW packages will be installed: fonts-noto-cjk 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/55.7 MB of archives. After this operation, 92.0 MB of additional disk space will be used. (Reading database ... 323769 files and directories currently installed.) Preparing to unpack .../fonts-noto-cjk_1%3a20190410+repack1-2_all.deb ... Unpacking fonts-noto-cjk (1:20190410+repack1-2) ... dpkg-deb (subprocess): decompressing archive member: lzma error: compressed data is corrupt dpkg-deb: error: subprocess returned error exit status 2 dpkg: error processing archive /var/cache/apt/archives/fonts-noto-cjk_1%3a20190410+repack1-2_all.deb (--unpack): cannot copy extracted data for './usr/share/fonts/opentype/noto/NotoSerifCJK-Bold.ttc' to '/usr/share/fonts/opentype/noto/NotoSerifCJK-Bold.ttc.dpkg-new': unexpected end of file or stream Errors were encountered while processing: /var/cache/apt/archives/fonts-noto-cjk_1%3a20190410+repack1-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fonts-noto-cjk (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Mon May 11 02:28:42 2020 InstallationDate: Installed on 2019-12-31 (131 days ago) InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: fonts-noto-cjk UpgradeStatus: Upgraded to focal on 2020-05-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1877957/+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 1877542] Re: Ubuntu 18.04.4 Inspiron 5379 No sound ALC3253 alsa-driver
Hello Sebastien, I was too happy at the first place. Yes there is the sound on speakers (I didn't managed yet to check HDMI), but there is neither nor sound nor the possibility to connect with BT headphones (all of my 3 sets are failed to connect). And regarding the booting previous kernel: sound from speakers appear only if I boot 4.15.0-96 in safemode Bizarre! Sincerely, Alexey On Mon, 11 May 2020 at 19:05, Alexey Nuyanzin wrote: > Salut Sebastien, > > Thanks for your letter. Log file is in attachment. > > And yay it works again, but not from the first time on 4.15.0-96. I had to > reboot it second time at safemode(without any applied changes in the menu ) > and it sounded well. > Thanks again for you help, I'm not the first-timer on ubuntu, but anyhow I > didn't even thought to just reboot myself under previous version system =) > Is there anyway I can help to fight this bug ? > > Alexey > > > On Mon, 11 May 2020 at 18:35, Sebastien Bacher wrote: > >> Thank you for your bug report, could you look in /var/log/dpkg.log what >> was updated? Could you try to start a previous kernel from the boot menu >> see if that makes a difference? >> >> ** Tags added: bionic >> >> ** Changed in: alsa-driver (Ubuntu) >>Status: New => Incomplete >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1877542 >> >> Title: >> Ubuntu 18.04.4 Inspiron 5379 No sound ALC3253 alsa-driver >> >> Status in alsa-driver package in Ubuntu: >> Incomplete >> >> Bug description: >> Hello, >> After last general update sound stops working on all interfaces. >> speakers, headphones nor HDMI provide any sound output even bluetooth >> headphones can't be connected. >> It seems that interface is connected to HDMI >> aplay -l >> >> List of PLAYBACK Hardware Devices >> card 0: PCH [HDA Intel PCH], device 0: ALC3253 Analog [ALC3253 Analog] >> Subdevices: 1/1 >> Subdevice #0: subdevice #0 >> card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] >> Subdevices: 1/1 >> Subdevice #0: subdevice #0 >> card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] >> Subdevices: 1/1 >> Subdevice #0: subdevice #0 >> card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] >> Subdevices: 1/1 >> Subdevice #0: subdevice #0 >> card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] >> Subdevices: 1/1 >> Subdevice #0: subdevice #0 >> card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] >> Subdevices: 1/1 >> Subdevice #0: subdevice #0 >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877542/+subscriptions >> > -- 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/1877542 Title: Ubuntu 18.04.4 Inspiron 5379 No sound ALC3253 alsa-driver Status in alsa-driver package in Ubuntu: Incomplete Bug description: Hello, After last general update sound stops working on all interfaces. speakers, headphones nor HDMI provide any sound output even bluetooth headphones can't be connected. It seems that interface is connected to HDMI aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3253 Analog [ALC3253 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877542/+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 1878080] [NEW] HPLIP fails to install working printer and scanner drivers.
Public bug reported: When using HPLIP to install drivers for HP ENVY 5530 e-All-in-One Printer, the software correctly detects and tries to install the printer driver. However, launching the printer window using printer icon in the system tray shows a printer with a red x and a message that says printer drivers install incomplete(?). Only a small subset of functions are listed for the printer (thus consistent with the incomplete message). Although HPLIP detects the correct printer, printing fails. Also, when launching scanlite, user is prompted with 4 flavors for envy 5530 scanner connections, but only one of them works correctly. None of these issues existed in 18.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hplip 3.20.3+dfsg0-2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: E [11/May/2020:07:15:37 -0600] [Client 4] Returning IPP client-error-bad-request for Create-Printer-Subscriptions (/) from localhost. CurrentDesktop: KDE Date: Mon May 11 09:30:27 2020 InstallationDate: Installed on 2019-06-15 (331 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for Brother_HL-2170W_series: dnssd://Brother%20HL-2170W%20series._pdl-datastream._tcp.local/ MachineType: ASUS All Series Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Brother_HL-2170W_series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Brother_HL-2170W_series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=2846c5c0-4d72-429f-959a-1f08f0454389 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: Upgraded to focal on 2020-03-26 (45 days ago) dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO 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.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx: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 ** Affects: hplip (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1878080 Title: HPLIP fails to install working printer and scanner drivers. Status in hplip package in Ubuntu: New Bug description: When using HPLIP to install drivers for HP ENVY 5530 e-All-in-One Printer, the software correctly detects and tries to install the printer driver. However, launching the printer window using printer icon in the system tray shows a printer with a red x and a message that says printer drivers install incomplete(?). Only a small subset of functions are listed for the printer (thus consistent with the incomplete message). Although HPLIP detects the correct printer, printing fails. Also, when launching scanlite, user is prompted with 4 flavors for envy 5530 scanner connections, but only one of them works correctly. None of these issues existed in 18.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hplip 3.20.3+dfsg0-2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: E [11/May/2020:07:15:37 -0600] [Client 4] Returning IPP client-error-bad-request for Create-Printer-Subscriptions (/) from localhost. CurrentDesktop: KDE Date: Mon May 11 09:30:27 2020 InstallationDate: Installed on 2019-06-15 (331 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for Brother_HL-2170W_series: dnssd://Brother%20HL-2170W%20series._pdl-datastream._tcp.local/ MachineType: ASUS All Series Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Brother_HL-2170W_series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Brother_HL-2170W_series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=2846c5c0-4d72-429f-959a-1f08f0454389 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: Upgraded to focal on 2020-03-26 (45 days ago) dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103
[Desktop-packages] [Bug 1878076] [NEW] GTK save-dialogs input-focus moves from filename to file search if a folder is selected
Public bug reported: This bug is also reported on GNOME's GTK GitLab: https://gitlab.gnome.org/GNOME/gtk/issues/326 ## Steps to reproduce 1. Open any GTK app which uses save dialogs (e.g. gedit) 2. Press save 3. A save dialog appears and the filename is highlighted (if typing at this point you edit the file name) 4. Click on a different folder (e.g. Downloads) 5. The filename is still highlighted, hinting that the focus is still there 6. Type and find yourself searching for a file in the selected folder -- Current behavior -- The higlighting (on the file name) hints a focus which is not the actual input focus, and the actual input focus (the search bar) is hidden until one starts to type, which I think to be confusing and unexpected. Also, clicking back on the highlighted filename you lose the highlighting, so you have to highlight again some already highlighted text; I think this to be confusing and counterintuitive. -- Expected outcome -- Highlighting and focus need to match. If they don't that's a UX bug, and there are several options to solve it, some examples: - keep highlighting as is and keep focus on the filename, this whould require finding a different path for file search (I think this is the most productive option, because I assume a user wants to change the folder and eventually rename or name the file, which I consider more likely than a user wanting to search for a file within a save-file dialog); - keep filesearch as is, but show its bar before typing begins, and remove any highlighting from filename. For reference, Windows 10's native save-file dialogs disables the highlighting when clicking on a different folder. Typing does nothing at that point. Tested on gedit 3.36.1 on Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk-3-0 3.24.18-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon May 11 21:53:37 2020 InstallationDate: Installed on 2020-04-03 (37 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 ** Affects: gtk Importance: Unknown Status: Unknown ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #326 https://gitlab.gnome.org/GNOME/gtk/issues/326 ** Also affects: gtk via https://gitlab.gnome.org/GNOME/gtk/issues/326 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1878076 Title: GTK save-dialogs input-focus moves from filename to file search if a folder is selected Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: New Bug description: This bug is also reported on GNOME's GTK GitLab: https://gitlab.gnome.org/GNOME/gtk/issues/326 ## Steps to reproduce 1. Open any GTK app which uses save dialogs (e.g. gedit) 2. Press save 3. A save dialog appears and the filename is highlighted (if typing at this point you edit the file name) 4. Click on a different folder (e.g. Downloads) 5. The filename is still highlighted, hinting that the focus is still there 6. Type and find yourself searching for a file in the selected folder -- Current behavior -- The higlighting (on the file name) hints a focus which is not the actual input focus, and the actual input focus (the search bar) is hidden until one starts to type, which I think to be confusing and unexpected. Also, clicking back on the highlighted filename you lose the highlighting, so you have to highlight again some already highlighted text; I think this to be confusing and counterintuitive. -- Expected outcome -- Highlighting and focus need to match. If they don't that's a UX bug, and there are several options to solve it, some examples: - keep highlighting as is and keep focus on the filename, this whould require finding a different path for file search (I think this is the most productive option, because I assume a user wants to change the folder and eventually rename or name the file, which I consider more likely than a user wanting to search for a file within a save-file dialog); - keep filesearch as is, but show its bar before typing begins, and remove any highlighting from filename. For reference, Windows 10's native save-file dialogs disables the highlighting when clicking on a different folder. Typing does nothing at that point. Tested on gedit 3.36.1 on Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package:
[Desktop-packages] [Bug 1877528] Re: Applet does not terminate at end of X desktop session
** Changed in: system-config-printer Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1877528 Title: Applet does not terminate at end of X desktop session Status in System Config Printer: New Status in system-config-printer package in Ubuntu: New Bug description: This concerns system-config-printer 1.5.12-0ubuntu1 in Ubuntu focal. I log into the Xfce desktop, and then logout. The screen returns to the LightDM login screen. A few minutes later, "loginctl list-sessions" shows the following: SESSION UID USERSEAT TTY 90 root c2 1000 skunk seat0 c3 116 lightdm seat0 3 sessions listed. Output from "loginctl session-status c2": c2 - skunk (1000) Since: Fri 2020-05-08 03:09:05 EDT; 9min ago Leader: 2530 Seat: seat0; vc7 Display: :0 Service: lightdm; type x11; class user Desktop: xubuntu State: closing Unit: session-c2.scope └─2856 /usr/bin/python3 /usr/share/system-config-printer/applet.py This process sticks around forever until I kill it, or its parent "systemd --user" process. Only then does the session disappear from list-sessions. When I run "session-status" while I'm logged in, I see a list of nearly 30 desktop-related processes. All of them except this one go away on logout. This one should too. To manage notifications about this bug go to: https://bugs.launchpad.net/system-config-printer/+bug/1877528/+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 1876797] Re: Numerous issues
They've been sent. -- 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/1876797 Title: Numerous issues Status in xorg-server package in Ubuntu: Incomplete Bug description: I upgraded from 18.04 -> 20.04. After upgrade, it will not remember my display configuration if I reboot. Settings can be saved (forced) into Xconfig, but for some reason it ignores them. I have a 1080p monitor vertical on my left, and a 1440p monitor on my right. Also, the system still believes I'm on Ubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09: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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 4 13:54:32 2020 DistUpgraded: 2020-04-27 21:42:55,589 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1660 Ti] [1458:3fbe] InstallationDate: Installed on 2018-07-01 (673 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6998b6fb-9ba7-4ce9-a023-b36dab34d51a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-28 (6 days ago) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: X470 AORUS ULTRA GAMING-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.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSULTRAGAMING:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSULTRAGAMING-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X470 AORUS ULTRA GAMING 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.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1876797/+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 1877675] Re: Workspaces broken with latest update
This issue seems to be related to the saving the screen resolution issue. If my left monitor gets switched back to vertical, workspaces come back. -- 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/1877675 Title: Workspaces broken with latest update Status in gnome-shell package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: Incomplete Bug description: Multiple workspaces broke with latest gnome config update. Unable to create, or go to different workspaces. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09: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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 8 17:05:52 2020 DistUpgraded: 2020-04-27 21:42:55,589 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1660 Ti] [1458:3fbe] InstallationDate: Installed on 2018-07-01 (677 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6998b6fb-9ba7-4ce9-a023-b36dab34d51a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-28 (10 days ago) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: X470 AORUS ULTRA GAMING-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.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSULTRAGAMING:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSULTRAGAMING-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X470 AORUS ULTRA GAMING 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.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877675/+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 1876292] Re: Error in layout from MS DOCX file, especially after saving as ODT
I get an error with: $ apport-collect 1876292 The authorization page: (https://launchpad.net/+authorize-token?oauth_token=H0bZnbhmgWSGsdlRpbJD_permission=DESKTOP_INTEGRATION) should be opening in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Waiting to hear from Launchpad about your decision... ERROR: connecting to Launchpad failed: [Errno 13] Keine Berechtigung: '/home/ich/.cache/apport/launchpad.credentials' You can reset the credentials by removing the file "/home/ich/.cache/apport/launchpad.credentials" Can't do this, as this file doesn't exist. -- 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/1876292 Title: Error in layout from MS DOCX file, especially after saving as ODT Status in LibreOffice: Invalid Status in libreoffice package in Ubuntu: Incomplete Bug description: For the details and example file please see: https://bugs.documentfoundation.org/show_bug.cgi?id=132552 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1876292/+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 1877427] Re: Double-clicking on a thread does not open the latest message
I don't get any warning in the console when I open the thread. Also, it seems it does not always happen the first time I open a thread (but always the next few times I try). I am using an IMAP account. (And I could also reproduce on another computer with another IMAP account.) I could not reproduce with thunderbird 68.4.1 installed from snap (with a new profile). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1877427 Title: Double-clicking on a thread does not open the latest message Status in thunderbird package in Ubuntu: Incomplete Status in thunderbird package in Debian: New Bug description: When grouping messages by thread and double-clicking on a thread, it should open every message in the thread in a new tab. However, it does not open the latest message and instead opens the first message twice (one time correctly and a second time at the end with a messed up character encoding). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: thunderbird 1:68.7.0+build1-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pierre 1530 F pulseaudio /dev/snd/pcmC0D0p: pierre 1530 F...m pulseaudio BuildID: 20200407160932 Channel: Unavailable CurrentDesktop: XFCE Date: Thu May 7 19:50:11 2020 ExecutablePath: /usr/lib/thunderbird/thunderbird Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-04-06 (1492 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.21 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-70906f39-d462-489a-8cc7-a27970180403 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1141 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=68.7.0/20200407160932 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to eoan on 2019-11-24 (165 days ago) dmi.bios.date: 10/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: W510LU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:svnNotebook:pnW510LU:pvrNotApplicable:rvnNotebook:rnW510LU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W510LU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1877427/+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 1877627] Re: /etc/default/im-config leaves temporary variables fixed in environment
This bug was fixed in the package im-config - 0.44-1ubuntu2 --- im-config (0.44-1ubuntu2) groovy; urgency=medium * debian/patches/01-ubuntu-default-mode.patch: - Declare temporary variables as local to avoid the risk that they alter environment variables (LP: #1877627). -- Gunnar Hjalmarsson Mon, 11 May 2020 18:13:00 +0200 ** Changed in: im-config (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1877627 Title: /etc/default/im-config leaves temporary variables fixed in environment Status in im-config package in Ubuntu: Fix Released Bug description: Ubuntu 18.04 im-config 0.34-1ubuntu1.3 You can reproduce the issue following these steps: - Open a X terminal - echo $d - Returns "GNOME" The source is this line in /etc/default/im-config: for d in 'Unity' 'MATE' 'GNOME'; do the temporary variable d gets fixed in the environment variables. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1877627/+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 1878065] [NEW] Sync onboard 1.4.1-5 (universe) from Debian unstable (main)
Public bug reported: Please sync onboard 1.4.1-5 (universe) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Replace invalid UTF-8 characters in ACPI events (LP: #1808446) [ Andrea Azzarone ] * debian/patches/1002_disable_onboard_on_gnome.patch: - don't enable onboard in GNOME sessions since caribou is being used and it leads to have two onscreen keyboards loaded at the same time (lp: #1721125) All the Ubuntu changes are now in Debian. Changelog entries since current groovy version 1.4.1-2ubuntu7: onboard (1.4.1-5) unstable; urgency=medium [ Mike Gabriel ] * debian/control: + Bump Standards-Version: to 4.4.1. No changes needed. + Add Rules-Requires-Root: field and set it to no. + Don't build gnome-shell-extension-onboard anymore. It is broken with recent GNONME and there is no feedback from upstream about the future perspective of the shell extension. NOTE: for now, this is a temporary measure until the Debian maintainer has received feedback from Onboard upstream about this. + Enforce removal of gnome-shell-extension-onboard via B:/R: when upgrading onboard to this package version. (Closes: #891236). + Switch to debhelper-compat notation. Bump DH compat level to version 12. * debian/rules: + Switch from dh_install --fail-missing to dh_missing override. + Don't install gnome-shell extension files for Onboard anymore. * debian/copyright: + Drop COPYING file. Thanks, lintian. [ Balint Reczey ] * debian/patches: + Add 0001-Replace-invalid-UTF-8-characters-in-ACPI-events.patch. Resolves UnicodeDecodeError in AcpidListener. (Closes: #936019, LP: #1808446). + Add 1003_disable_onboard_on_gnome.patch. Disable onboard on GNOME. (Closes: #931961, LP: #1721125). -- Mike Gabriel Thu, 09 Jan 2020 11:26:40 +0100 onboard (1.4.1-4) unstable; urgency=medium * debian/control: + Drop pkg-mate-team Alioth mailing list from Uploaders: field. + One uploader per line... + Bump Standards-Version: to 4.2.0. No changes needed. * debian/copyright: + Use secure URL in Source: field. -- Mike Gabriel Wed, 22 Aug 2018 12:09:38 +0200 onboard (1.4.1-3) unstable; urgency=medium [ Vangelis Mouhtsis ] * debian/control: + Rename pretty name of our team -> Debian+Ubuntu MATE Packaging Team. + Update Maintainer: field to debian-mate ML on lists.debian.org. + Add myself to Uploaders: field. + Temporarily have pkg-mate-team ML under Uploaders:. [ Mike Gabriel ] * debian/copyright: + Use secure URI for copyright format. + Update Vcs-*: fields. Package has been migrated to salsa.debian.org. + Bump Standards-Version: to 4.1.4. No changes needed. + Switch R from gir1.2-appindicator3-0.1 to gir1.2-ayatanaappindicator3-0.1. * debian/patches: + Add 1002_build-against-Ayatana-AppIndicator.patch. -- Mike Gabriel Fri, 11 May 2018 13:37:23 +0200 ** Affects: onboard (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1878065 Title: Sync onboard 1.4.1-5 (universe) from Debian unstable (main) Status in onboard package in Ubuntu: New Bug description: Please sync onboard 1.4.1-5 (universe) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Replace invalid UTF-8 characters in ACPI events (LP: #1808446) [ Andrea Azzarone ] * debian/patches/1002_disable_onboard_on_gnome.patch: - don't enable onboard in GNOME sessions since caribou is being used and it leads to have two onscreen keyboards loaded at the same time (lp: #1721125) All the Ubuntu changes are now in Debian. Changelog entries since current groovy version 1.4.1-2ubuntu7: onboard (1.4.1-5) unstable; urgency=medium [ Mike Gabriel ] * debian/control: + Bump Standards-Version: to 4.4.1. No changes needed. + Add Rules-Requires-Root: field and set it to no. + Don't build gnome-shell-extension-onboard anymore. It is broken with recent GNONME and there is no feedback from upstream about the future perspective of the shell extension. NOTE: for now, this is a temporary measure until the Debian maintainer has received feedback from Onboard upstream about this. + Enforce removal of gnome-shell-extension-onboard via B:/R: when upgrading onboard to this package version. (Closes: #891236). + Switch to debhelper-compat notation. Bump DH compat level to version 12. * debian/rules: + Switch from dh_install --fail-missing to dh_missing override. + Don't install gnome-shell extension files for Onboard anymore. * debian/copyright: + Drop COPYING file. Thanks, lintian. [ Balint Reczey ] * debian/patches: + Add
[Desktop-packages] [Bug 1877528] Re: Applet does not terminate at end of X desktop session
Reported upstream as https://github.com/OpenPrinting/system-config-printer/issues/175 ** Bug watch added: github.com/OpenPrinting/system-config-printer/issues #175 https://github.com/OpenPrinting/system-config-printer/issues/175 ** Also affects: system-config-printer via https://github.com/OpenPrinting/system-config-printer/issues/175 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1877528 Title: Applet does not terminate at end of X desktop session Status in System Config Printer: Unknown Status in system-config-printer package in Ubuntu: New Bug description: This concerns system-config-printer 1.5.12-0ubuntu1 in Ubuntu focal. I log into the Xfce desktop, and then logout. The screen returns to the LightDM login screen. A few minutes later, "loginctl list-sessions" shows the following: SESSION UID USERSEAT TTY 90 root c2 1000 skunk seat0 c3 116 lightdm seat0 3 sessions listed. Output from "loginctl session-status c2": c2 - skunk (1000) Since: Fri 2020-05-08 03:09:05 EDT; 9min ago Leader: 2530 Seat: seat0; vc7 Display: :0 Service: lightdm; type x11; class user Desktop: xubuntu State: closing Unit: session-c2.scope └─2856 /usr/bin/python3 /usr/share/system-config-printer/applet.py This process sticks around forever until I kill it, or its parent "systemd --user" process. Only then does the session disappear from list-sessions. When I run "session-status" while I'm logged in, I see a list of nearly 30 desktop-related processes. All of them except this one go away on logout. This one should too. To manage notifications about this bug go to: https://bugs.launchpad.net/system-config-printer/+bug/1877528/+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 1873764] Re: CUPS Apparmor Error opening /proc/sys/kernel/random/boot_id
*** This bug is a duplicate of bug 1872564 *** https://bugs.launchpad.net/bugs/1872564 This is a dupe of https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1872564 which, AIUI, the server team will be performing an SRU for. ** This bug has been marked a duplicate of bug 1872564 /proc/sys/kernel/random/boot_id rule missing from abstractions/nameservice -- 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/1873764 Title: CUPS Apparmor Error opening /proc/sys/kernel/random/boot_id Status in cups package in Ubuntu: Confirmed Bug description: I noted the following messages on a just installed Ubuntu Focal: $ dmesg | grep cups [ 1769.505132] audit: type=1400 audit(1587372138.575:3011): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=15230 comm="cups-browsed" capability=23 capname="sys_nice" [ 1776.623181] audit: type=1400 audit(1587372145.693:3012): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=15510 comm="cups-browsed" capability=23 capname="sys_nice" [ 2040.426033] audit: type=1400 audit(1587372409.494:3013): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2040.426044] audit: type=1400 audit(1587372409.494:3014): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2040.426074] audit: type=1400 audit(1587372409.494:3015): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2040.426092] audit: type=1400 audit(1587372409.494:3016): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2040.426106] audit: type=1400 audit(1587372409.494:3017): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2041.404914] audit: type=1400 audit(1587372410.473:3018): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2041.404920] audit: type=1400 audit(1587372410.473:3019): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2041.404926] audit: type=1400 audit(1587372410.473:3020): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2041.404953] audit: type=1400 audit(1587372410.473:3021): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2041.404963] audit: type=1400 audit(1587372410.473:3022): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2071.925327] audit: type=1400 audit(1587372440.994:3028): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2071.925330] audit: type=1400 audit(1587372440.994:3029): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2071.925337] audit: type=1400 audit(1587372440.994:3030): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2071.925382] audit: type=1400 audit(1587372440.994:3031): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2071.925391] audit: type=1400 audit(1587372440.994:3032): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 It happened after installing Brother DCPL3550CDW Linux drivers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups-daemon 2.3.1-9ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-lowlatency 5.4.30 Uname: Linux 5.4.0-25-lowlatency x86_64
[Desktop-packages] [Bug 1878059] Re: Audio device not reachable after wake up
When the devices are gone and test the missing device as $ speaker-test -D hw:0,0 -c 2 It plays the noise sound to my usual speakers. -- 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/1878059 Title: Audio device not reachable after wake up Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 20.04, Gnome shell On older Ubuntu releases (<= 19.10), all is working fine. After waking up from suspend mode when I play music or a video, the system changed playing sound at my monitor speakers, detected as „card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]“. Here is the full list: $ LANG=C aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 I can only choose the HDMI device in gnome-control-center or pavucontrol. The other devices are gone, why what ever. When I restart the pulseaudio process, all devices will come back: $ sudo killall -9 pulseaudio # (many times, because pa restarts itself) $ /usr/bin/pulseaudio --daemonize=no --log-target=journal ^Z [1]+ Angehalten /usr/bin/pulseaudio --daemonize=no --log-target=journal $ bg 1 This behavior is new in 20.04. Before I establish the behavior of pulseaudio, I logged off and on again and all devices are shown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878059/+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 1878059] [NEW] Audio device not reachable after wake up
Public bug reported: Ubuntu 20.04, Gnome shell On older Ubuntu releases (<= 19.10), all is working fine. After waking up from suspend mode when I play music or a video, the system changed playing sound at my monitor speakers, detected as „card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]“. Here is the full list: $ LANG=C aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 I can only choose the HDMI device in gnome-control-center or pavucontrol. The other devices are gone, why what ever. When I restart the pulseaudio process, all devices will come back: $ sudo killall -9 pulseaudio # (many times, because pa restarts itself) $ /usr/bin/pulseaudio --daemonize=no --log-target=journal ^Z [1]+ Angehalten /usr/bin/pulseaudio --daemonize=no --log-target=journal $ bg 1 This behavior is new in 20.04. Before I establish the behavior of pulseaudio, I logged off and on again and all devices are shown. ** 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/1878059 Title: Audio device not reachable after wake up Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 20.04, Gnome shell On older Ubuntu releases (<= 19.10), all is working fine. After waking up from suspend mode when I play music or a video, the system changed playing sound at my monitor speakers, detected as „card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]“. Here is the full list: $ LANG=C aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 I can only choose the HDMI device in gnome-control-center or pavucontrol. The other devices are gone, why what ever. When I restart the pulseaudio process, all devices will come back: $ sudo killall -9 pulseaudio # (many times, because pa restarts itself) $ /usr/bin/pulseaudio --daemonize=no --log-target=journal ^Z [1]+ Angehalten /usr/bin/pulseaudio --daemonize=no --log-target=journal $ bg 1 This behavior is new in 20.04. Before I establish the behavior of pulseaudio, I logged off and on again and all devices are shown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878059/+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 1877648] Re: [nouveau] Laptop video problem
I can't try Ubuntu 20.04 or Xubuntu 20.04 because it's a 32 bits CPU. I had similar problem at startup with Debian buster i386 but i'm waiting an other hard disk to say if it was exactly the same thing or not. -- 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/1877648 Title: [nouveau] Laptop video problem Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: After a fresh install, the system goes to sleep mode in place of showing logon display. After waking up, the screen stay black but login action and shutdown button seems to work so there's no video on laptop screen (LVDS-1). When i connect an DVI-I monitor before starting, the computer doesn't go in sleep mode at startup. I can see the logon on external monitor but there nothing on internal monitor. I can use the two monitor when i use those commands: xrandr --output DVI-I-1 --mode 1400x1050 --primary xrandr --output LVDS-1 --mode 1440x900 --right-of DVI-I-1 --crtc 0 LVDS-1 is reported as "unknown connection" in place of "connected" or "disconnected". Xorg0.log report that the internal monitor is disconnected : [31.856] (II) NOUVEAU(0): Output VGA-1 disconnected [31.856] (II) NOUVEAU(0): Output LVDS-1 disconnected [31.856] (II) NOUVEAU(0): Output DVI-I-1 connected [31.856] (II) NOUVEAU(0): Output TV-1 disconnected ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic i686 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: i386 CompositorRunning: None CurrentDesktop: XFCE Date: Fri May 8 20:28:43 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation NV41M [GeForce Go 6800] [10de:00c8] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Technology Solutions NV41M [GeForce Go 6800] [1734:107c] InstallationDate: Installed on 2020-04-17 (21 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: FUJITSU SIEMENS Amilo M3438 Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=f910d7c1-f499-455a-ade2-472c22149dcd ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2005 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.10C dmi.board.name: P71EN0 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.10C:bd10/05/2005:svnFUJITSUSIEMENS:pnAmiloM3438Series:pvr:rvn:rnP71EN0:rvr:cvnFUJITSUSIEMENS:ct10:cvr: dmi.product.name: Amilo M3438 Series dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 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/xserver-xorg-video-nouveau/+bug/1877648/+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 684982]
I hate to be negative here but this new behavior does not make sense under Gnome 3 with its default settings, where workspaces are created dynamically; workspaceID=3 will refer to a completely different workspace after I reboot my computer. Typically, I have ~6 firefox windows across different workspaces. Most of those workspaces only have the firefox window in them. When I close firefox, these workspaces are removed by Gnome. If I start firefox again, I have to spend time searching for all the firefox windows that appear in (seemingly) random workspaces. Please give users the option to disable the new behavior and restore the old one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 263505]
*** Bug 1433991 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/263505 Title: Wishlist: add "use input as a search term" to "address not found" page Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Incomplete Bug description: Binary package hint: firefox Altogether too often when I get the "Address Not Found" page, it is because I expected too much from the Wonderful Bar or whatever it's called. It would be a useful addition if the "Address Not Found" page could offer the option to use the stuff you typed into the location bar as input for your designated search engine, and/or perform history search on those terms. (For me, the former is the more useful, but I expect both would be handy, and the effort to offer both is probably marginal if you decide to do one or the other.) All to often, what you typed in is no longer visible in the location bar, because http:// gets prepended and sometimes a .com appended to what is displayed in the location bar at the point you get the "Address Not Found" error. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/263505/+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 73536]
*** Bug 1634905 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/73536 Title: MASTER Firefox crashes on instant X server shutdown Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Triaged Bug description: Firefox crashes when X server is forcefully torn down (e.g. by pressing ctrl-alt-backspace) and a crash report gets generated on next login. (Original Report: I've reproduced it once on my machine with the following steps. With, oh, about 5 tabs open, I just pressed ctrl-alt-backspace, logged back in when the X server restarted, and FF crashed with a bug report when Gnome tried to restore the session. It's not terribly important, I don't think anyone does this very often, but maybe it'll be helpful. ) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/73536/+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 684982]
(In reply to Martin Stránský [:stransky] from comment #97) > (In reply to Marios Titas from comment #96) > > I hate to be negative here but this new behavior does not make sense under > > Gnome 3 with its default settings, where workspaces are created > > dynamically; workspaceID=3 will refer to a completely different workspace > > after I reboot my computer. > > > > Typically, I have ~6 firefox windows across different workspaces. Most of > > those workspaces only have the firefox window in them. When I close > > firefox, these workspaces are removed by Gnome. If I start firefox again, I > > have to spend time searching for all the firefox windows that appear in > > (seemingly) random workspaces. > > > > Please give users the option to disable the new behavior and restore the > > old one. > > Please file a new bug for it and cc me there. > Thanks. Done: Bug 1635787 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
(In reply to Marios Titas from comment #96) > I hate to be negative here but this new behavior does not make sense under > Gnome 3 with its default settings, where workspaces are created dynamically; > workspaceID=3 will refer to a completely different workspace after I reboot > my computer. > > Typically, I have ~6 firefox windows across different workspaces. Most of > those workspaces only have the firefox window in them. When I close firefox, > these workspaces are removed by Gnome. If I start firefox again, I have to > spend time searching for all the firefox windows that appear in (seemingly) > random workspaces. > > Please give users the option to disable the new behavior and restore the old > one. Please file a new bug for it and cc me there. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 73536]
*** Bug 1629049 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/73536 Title: MASTER Firefox crashes on instant X server shutdown Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Triaged Bug description: Firefox crashes when X server is forcefully torn down (e.g. by pressing ctrl-alt-backspace) and a crash report gets generated on next login. (Original Report: I've reproduced it once on my machine with the following steps. With, oh, about 5 tabs open, I just pressed ctrl-alt-backspace, logged back in when the X server restarted, and FF crashed with a bug report when Gnome tried to restore the session. It's not terribly important, I don't think anyone does this very often, but maybe it'll be helpful. ) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/73536/+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 1628153] Re: [W65_67SF, VIA VT1802, Speaker, Internal] No sound at all on most restarts
** Changed in: alsa-driver (Ubuntu) Assignee: (unassigned) => Abhirup Pal (monalisarai) -- 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/1628153 Title: [W65_67SF, VIA VT1802, Speaker, Internal] No sound at all on most restarts Status in alsa-driver package in Ubuntu: Confirmed Bug description: On the vast majority of restarts of Ubuntu 16.04 I get no internal sound at all. There are no reported issues in system settings on the only sound card I have. The volume is not muted. On an estimated 1 in 10 restart, the sound works, and both the test sounds get played and other applications work fine. There is no reported errors or messages on the restarts when the sound has failed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: tony 16160 F...m pulseaudio /dev/snd/controlC1: tony 16160 F pulseaudio /dev/snd/controlC0: tony 16160 F pulseaudio CurrentDesktop: Unity Date: Tue Sep 27 15:56:02 2016 InstallationDate: Installed on 2015-10-29 (334 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: tony 16160 F...m pulseaudio /dev/snd/controlC1: tony 16160 F pulseaudio /dev/snd/controlC0: tony 16160 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [W65_67SF, VIA VT1802, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to xenial on 2016-08-13 (45 days ago) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_67SF dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.03:bd04/01/2014:svnNotebook:pnW65_67SF:pvrNotApplicable:rvnNotebook:rnW65_67SF:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W65_67SF dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1628153/+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 1875435] Re: Re-logging occurs continuously during ubuntu operation
5.7.0-rc5 without nvidia driver, only nouveau driver ** Attachment added: "journalctl8.log" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1875435/+attachment/5369965/+files/journalctl8.log -- 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/1875435 Title: Re-logging occurs continuously during ubuntu operation Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: I thought that I had some kind of problem with the video driver and all the detailed logs are contained here https://forums.developer.nvidia.com/t/ubuntu-kernel-v5-6-v5-7-for-hp-omen-17t-bc000-gforce-rtx2080-unstable-driver-nvidia-linux-x86-64-440-82-run/120027/25 But I installed ubuntu 20.04 and the problem is repeated not only on new kernels ubuntu 5.6 and 5.7.0-rc but also on kernel 5.4 with the Nouveau driver The system constantly logs onto the standard screen and requires a password to close all current programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1875435/+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 1877871] Re: X windows hnags following upgrade from 18.04 to 20.04
** Package changed: ubuntu-release-upgrader (Ubuntu) => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1877871 Title: X windows hnags following upgrade from 18.04 to 20.04 Status in xorg package in Ubuntu: New Bug description: Following an upgrade from 18.04 to 20.04 when I boot, X windows comes to a point where I get a white background with a bunch of colored dots. Nothing progresses from there. I can boot successfully by pressing escape after booting, going to advanced options, booting to 5.4.0-29 recovery mode. When that menu appears, I select "root". I press Enter for maintenance. When the root prompt appears I immediately type EXIT to return to the menu and then RESUME followed by OK. The system then starts the desktop properly. I would be happy to provide boot logs and/or Xorg.0.logs if desired. It appears to me that there are out of memory errors occurring along with some addressing issues. I am on an HP EliteBook 8570w laptop 15.6 G memory. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 10:22:37 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-22 (595 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-05-09 09:07:41.355959 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1877871/+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 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
Thanks for all the help so far. -- 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/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem Status in HWE Next: New Status in alsa-driver package in Ubuntu: New Bug description: On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa- base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that now "snd-hda-intel" is loaded instead of sof-audio-pci. While the speakers are working fine, I do not have the internal microphone working (suspect a digital array). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wittawat 2063 F pulseaudio /dev/snd/controlC0: wittawat 2063 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 12:42:32 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Left Symptom_Type: None of the above Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8600 dmi.board.vendor: HP dmi.board.version: 44.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-dh0xxx dmi.product.sku: 7JX54EA#ABD dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+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 1877871] [NEW] X windows hnags following upgrade from 18.04 to 20.04
You have been subscribed to a public bug: Following an upgrade from 18.04 to 20.04 when I boot, X windows comes to a point where I get a white background with a bunch of colored dots. Nothing progresses from there. I can boot successfully by pressing escape after booting, going to advanced options, booting to 5.4.0-29 recovery mode. When that menu appears, I select "root". I press Enter for maintenance. When the root prompt appears I immediately type EXIT to return to the menu and then RESUME followed by OK. The system then starts the desktop properly. I would be happy to provide boot logs and/or Xorg.0.logs if desired. It appears to me that there are out of memory errors occurring along with some addressing issues. I am on an HP EliteBook 8570w laptop 15.6 G memory. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 10:22:37 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-22 (595 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-05-09 09:07:41.355959 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal -- X windows hnags following upgrade from 18.04 to 20.04 https://bugs.launchpad.net/bugs/1877871 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp