[Desktop-packages] [Bug 1827428] Re: Mouse cursor left frozen copy of itself
Another with this problem here. I have Radeon HD 7850 - no nvidia - also scaling at 125%. Unscaled is OK. -- 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/1827428 Title: Mouse cursor left frozen copy of itself Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Mouse cursor left freezed copy of itself over all the windows after login after lock screen. Functionality is not broken. It's just not aesthetic. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 2 16:10:09 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8392] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] [103c:8392] InstallationDate: Installed on 2019-04-29 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 17-an0xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=08661a81-0386-4b44-9d3e-17ad6fa2de96 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8392 dmi.board.vendor: HP dmi.board.version: 40.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.05:bd06/21/2017:svnHP:pnOMENbyHPLaptop17-an0xx:pvr:rvnHP:rn8392:rvr40.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-an0xx dmi.product.sku: 2FP35EA#ACB dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Sorry about the noise. I have shotgunned a more appropriate set of packages related to this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Set to priority Low since you need to be using both the Nvidia proprietary driver and automatic logins to hit this bug. ** No longer affects: gnome-shell (Ubuntu) ** No longer affects: gnome-shell (Ubuntu Eoan) ** Also affects: nvidia-graphics-drivers-430 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-430 (Ubuntu) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-430 (Ubuntu) Importance: Undecided => Low ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided => Low ** Changed in: gdm3 (Ubuntu Eoan) Status: Incomplete => Confirmed ** Changed in: gnome-session (Ubuntu) Status: Incomplete => Confirmed ** Changed in: gnome-session (Ubuntu Eoan) Status: Incomplete => Confirmed ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Confirmed ** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
[Desktop-packages] [Bug 1859123] Re: No global menus (panel-appmenu / dbus) in Firefox 72.0.1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1859123 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- 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/1859123 Title: No global menus (panel-appmenu / dbus) in Firefox 72.0.1 Status in firefox package in Ubuntu: New Bug description: No global menus are displayed in latest Firefox 72.0.1 (possibly in a slightly earlier version). This issue was observed on three different systems all running Ubuntu MATE 20.04 Focal (development), and I first noticed it on each system upon updating to 72.0.1 today. The symptoms are identical to https://bugs.launchpad.net/ubuntu- mate/+bug/1743687 , but running `env UBUNTU_MENUPROXY=0 firefox` does not resolve the issue. `env UBUNTU_MENUPROXY=1 firefox` does not resolve the issue either. My first guess is that the issue is a change in Firefox, due to how the previous solution with the environment variable no longer works. (Perhaps a change to the Unity menu patch?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1859123/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Changed in: gdm3 (Ubuntu) Importance: Undecided => Low ** Changed in: gdm3 (Ubuntu Eoan) Importance: Undecided => Low ** Changed in: gnome-session (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-session (Ubuntu Eoan) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu Eoan) Importance: Undecided => Low ** Also affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided => Low ** Changed in: nvidia-graphics-drivers-435 (Ubuntu Eoan) Importance: Undecided => Low ** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-435 (Ubuntu Eoan) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Incomplete Status in gnome-session source package in Eoan: Incomplete Status in gnome-shell source package in Eoan: Incomplete Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
[Desktop-packages] [Bug 1859123] [NEW] No global menus (panel-appmenu / dbus) in Firefox 72.0.1
Public bug reported: No global menus are displayed in latest Firefox 72.0.1 (possibly in a slightly earlier version). This issue was observed on three different systems all running Ubuntu MATE 20.04 Focal (development), and I first noticed it on each system upon updating to 72.0.1 today. The symptoms are identical to https://bugs.launchpad.net/ubuntu- mate/+bug/1743687 , but running `env UBUNTU_MENUPROXY=0 firefox` does not resolve the issue. `env UBUNTU_MENUPROXY=1 firefox` does not resolve the issue either. My first guess is that the issue is a change in Firefox, due to how the previous solution with the environment variable no longer works. (Perhaps a change to the Unity menu patch?) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/1859123 Title: No global menus (panel-appmenu / dbus) in Firefox 72.0.1 Status in firefox package in Ubuntu: New Bug description: No global menus are displayed in latest Firefox 72.0.1 (possibly in a slightly earlier version). This issue was observed on three different systems all running Ubuntu MATE 20.04 Focal (development), and I first noticed it on each system upon updating to 72.0.1 today. The symptoms are identical to https://bugs.launchpad.net/ubuntu- mate/+bug/1743687 , but running `env UBUNTU_MENUPROXY=0 firefox` does not resolve the issue. `env UBUNTU_MENUPROXY=1 firefox` does not resolve the issue either. My first guess is that the issue is a change in Firefox, due to how the previous solution with the environment variable no longer works. (Perhaps a change to the Unity menu patch?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1859123/+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 1340907] Re: cannot edit tags in m4a files
I just encountered this in Ubuntu 19.10 with Rhythmbox 3.4.3. I had just replaced some MP3 files with FLAC files and then wanted to edit metadata for consistency with my library. I got the same error "File corrupted during write." -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1340907 Title: cannot edit tags in m4a files Status in rhythmbox package in Ubuntu: Confirmed Bug description: Rhythmbox cannot edit m4a tags. For example, I right-click on a song and the "properties" window opens. I change a field, for example "title", and then click "close". A window opens saying "Error while saving song information. File corrupted during write." The title is unchanged in the song, as can be seen in the Rhythmbox window and can be verified with another program like Easytag. Additional details that might be useful: * The permissions on the m4a file are -rw-rw-rw- * Though the error window says the "File corrupted during write", the m4a file is in fact not even modified * There is no problem with mp3 files; for example, the process described above can be used successfully to change the title of an mp3 song * I used to be able to edit m4a tags in Ubuntu 12.10; this problem arose when I upgraded to Ubuntu 14.04 LTS. Although there exist other programs to tag m4a files, they do not provide a useable work-around. If you use such a program to change an m4a tag, then the music library comes inconsistent with Rhythmbox's "rhythmdb.xml" database. Thanks for your help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 11 11:42:44 2014 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2014-04-25 (77 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1340907/+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 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized
** Changed in: bluez (Ubuntu) Importance: High => Medium ** Changed in: pulseaudio (Ubuntu) Importance: High => Undecided ** Changed in: bluez (Ubuntu) Importance: Medium => Undecided -- 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/1577197 Title: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized Status in bluez package in Ubuntu: Confirmed Status in indicator-sound package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period of time. Only restart fixes the issue. This started early 2016 in 15.10. Issue is discussed here as well http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04 and mentioned in other unrelated bugs. Ubuntu Xenial 16.04 LTS The log below: May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profile May 1 17:18:07 jalexoidmobile bluetoothd[7349]: /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 10967 of process 2884 (n/a) owned by '1000' RT at priority 5. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed for transport /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized) May 1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 May 1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s camera Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad] Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF advanced mode) Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [20389.070122] usb 1-1.4: Product: BCM20702A0 [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD [20389.076232] Bluetooth: hci0: BCM: chip id 63 [20389.092220] Bluetooth: hci0: BCM20702A [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3) [20389.557790] wlan0: authenticated [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3) [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 status=0 aid=2) [20389.581260] wlan0: associated [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669 [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23 [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1577197/+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 1859113] [NEW] No support for Zstandard
Public bug reported: As stated on https://facebook.github.io/zstd/ "Zstandard is a real-time compression algorithm, providing high compression ratios. It offers a very wide range of compression / speed trade-off, while being backed by a very fast decoder". Other Linux distributions even started to use the Zstandard in the place of xz compression for their packages due to how fast the decompression is, even if there is a small penalty on ratio. On my own testing, I noticed 17% faster compression and 88% faster decompression compared to xz while there was a 3% differences on compression ratio for system images. With this bug report, I ask to add support for Zstandard on at least file-roller. Currently, I have to use the command line tool zstd to work with files compressed using Zstandard. On Thunar, *.zst files appear as unknown and file-roller says there is no support for this file type. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: file-roller 3.32.2-1 Uname: Linux 4.19.93-041969 x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jan 9 22:59:56 2020 InstallationDate: Installed on 2017-06-13 (940 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: file-roller UpgradeStatus: Upgraded to focal on 2019-12-22 (18 days ago) mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240 ** Affects: file-roller (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 file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1859113 Title: No support for Zstandard Status in file-roller package in Ubuntu: New Bug description: As stated on https://facebook.github.io/zstd/ "Zstandard is a real-time compression algorithm, providing high compression ratios. It offers a very wide range of compression / speed trade-off, while being backed by a very fast decoder". Other Linux distributions even started to use the Zstandard in the place of xz compression for their packages due to how fast the decompression is, even if there is a small penalty on ratio. On my own testing, I noticed 17% faster compression and 88% faster decompression compared to xz while there was a 3% differences on compression ratio for system images. With this bug report, I ask to add support for Zstandard on at least file-roller. Currently, I have to use the command line tool zstd to work with files compressed using Zstandard. On Thunar, *.zst files appear as unknown and file-roller says there is no support for this file type. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: file-roller 3.32.2-1 Uname: Linux 4.19.93-041969 x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jan 9 22:59:56 2020 InstallationDate: Installed on 2017-06-13 (940 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: file-roller UpgradeStatus: Upgraded to focal on 2019-12-22 (18 days ago) mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1859113/+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 1859112] Re: Xorg crashed with SIGSEGV in drmmode_output_create_resources() from xf86RandR12CreateObjects12() from xf86RandR12Init12() from xf86RandR12Init() from xf86CrtcScree
** Summary changed: - /usr/lib/xorg/Xorg:6:drmmode_output_create_resources:xf86RandR12CreateObjects12:xf86RandR12Init12:xf86RandR12Init:xf86CrtcScreenInit + Xorg crashed with SIGSEGV in drmmode_output_create_resources() from xf86RandR12CreateObjects12() from xf86RandR12Init12() from xf86RandR12Init() from xf86CrtcScreenInit() -- 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/1859112 Title: Xorg crashed with SIGSEGV in drmmode_output_create_resources() from xf86RandR12CreateObjects12() from xf86RandR12Init12() from xf86RandR12Init() from xf86CrtcScreenInit() Status in xorg-server package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.5+git20191008-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/5a8ef52c35776ebea6efc6dee4784fb12f4c01d6 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1859112/+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 1856846] Re: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work)
Thanks. The crash report is not usable according to the robots, not sure why... However your new prevboot.txt is useful and shows: Jan 09 11:40:31 ektorp /usr/lib/gdm3/gdm-x-session[3134]: (EE) Jan 09 11:40:31 ektorp /usr/lib/gdm3/gdm-x-session[3134]: (EE) Backtrace: Jan 09 11:40:31 ektorp /usr/lib/gdm3/gdm-x-session[3134]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x555af506d7d9] Jan 09 11:40:31 ektorp /usr/lib/gdm3/gdm-x-session[3134]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f69368f68df] Jan 09 11:40:31 ektorp /usr/lib/gdm3/gdm-x-session[3134]: (EE) 2: /usr/lib/xorg/modules/drivers/modesetting_drv.so (_init+0x6501) [0x7f6933be1251] Jan 09 11:40:31 ektorp /usr/lib/gdm3/gdm-x-session[3134]: (EE) 3: /usr/lib/xorg/Xorg (xf86RandR12Init+0x394) [0x555af4f8cae4] Jan 09 11:40:31 ektorp /usr/lib/gdm3/gdm-x-session[3134]: (EE) 4: /usr/lib/xorg/Xorg (xf86CrtcScreenInit+0x2b) [0x555af4f7f58b] Jan 09 11:40:31 ektorp /usr/lib/gdm3/gdm-x-session[3134]: (EE) 5: /usr/lib/xorg/modules/drivers/modesetting_drv.so (_init+0x3d0e) [0x7f6933bdbeee] Jan 09 11:40:31 ektorp /usr/lib/gdm3/gdm-x-session[3134]: (EE) 6: /usr/lib/xorg/Xorg (AddScreen+0xd7) [0x555af4f107e7] Jan 09 11:40:31 ektorp /usr/lib/gdm3/gdm-x-session[3134]: (EE) 7: /usr/lib/xorg/Xorg (InitOutput+0x3ce) [0x555af4f50c0e] Jan 09 11:40:31 ektorp /usr/lib/gdm3/gdm-x-session[3134]: (EE) 8: /usr/lib/xorg/Xorg (InitFonts+0x1dd) [0x555af4f1438d] Jan 09 11:40:31 ektorp /usr/lib/gdm3/gdm-x-session[3134]: (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xe7) [0x7f6936514b97] Jan 09 11:40:31 ektorp /usr/lib/gdm3/gdm-x-session[3134]: (EE) 10: /usr/lib/xorg/Xorg (_start+0x2a) [0x555af4efe1ea] Jan 09 11:40:31 ektorp /usr/lib/gdm3/gdm-x-session[3134]: (EE) Jan 09 11:40:31 ektorp /usr/lib/gdm3/gdm-x-session[3134]: (EE) Segmentation fault at address 0x30 Jan 09 11:40:31 ektorp /usr/lib/gdm3/gdm-x-session[3134]: (EE) Jan 09 11:40:31 ektorp /usr/lib/gdm3/gdm-x-session[3134]: Fatal server error: Jan 09 11:40:31 ektorp /usr/lib/gdm3/gdm-x-session[3134]: (EE) Caught signal 11 (Segmentation fault). Server aborting Jan 09 11:40:31 ektorp /usr/lib/gdm3/gdm-x-session[3134]: (EE) which seems to agree with comments #8-#10. ** Summary changed: - Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work) + Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work). Xorg crashes with SIGSEGV in ?? from _init() from xf86RandR12Init() from xf86CrtcScreenInit() ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1856846 Title: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work). Xorg crashes with SIGSEGV in ?? from _init() from xf86RandR12Init() from xf86CrtcScreenInit() Status in xorg-server package in Ubuntu: New Bug description: When trying to login to Gnome with an remote user from an LDAP (LDAP is available and connectable when in GDM) using X11, GDM loops around three to five times before actually granting access to the desktop. This does not happen when a) Wayland is used instead of X11 or, b) the LDAP server is not reachable during login, using X11, or c) a local user is logged in instead, using X11 The LDAP connection is established using the Univention Domain Join Client: https://launchpad.net/~univention- dev/+archive/ubuntu/ppa?field.series_filter=bionic Do you require additional information? Release: Description: Ubuntu 18.04.3 LTS Release: 18.04 GDM3: gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1856846/+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 1856846] Re: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work). Xorg crashes with SIGSEGV in ?? from _init() from xf86RandR12Init() from xf86C
I did just find and create bug 1859112. This might be the same as that one but we can't be sure without line number info. -- 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/1856846 Title: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work). Xorg crashes with SIGSEGV in ?? from _init() from xf86RandR12Init() from xf86CrtcScreenInit() Status in xorg-server package in Ubuntu: New Bug description: When trying to login to Gnome with an remote user from an LDAP (LDAP is available and connectable when in GDM) using X11, GDM loops around three to five times before actually granting access to the desktop. This does not happen when a) Wayland is used instead of X11 or, b) the LDAP server is not reachable during login, using X11, or c) a local user is logged in instead, using X11 The LDAP connection is established using the Univention Domain Join Client: https://launchpad.net/~univention- dev/+archive/ubuntu/ppa?field.series_filter=bionic Do you require additional information? Release: Description: Ubuntu 18.04.3 LTS Release: 18.04 GDM3: gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1856846/+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 1859112] [NEW] Xorg crashed with SIGSEGV in drmmode_output_create_resources() from xf86RandR12CreateObjects12() from xf86RandR12Init12() from xf86RandR12Init() from xf86CrtcScr
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.5+git20191008-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/5a8ef52c35776ebea6efc6dee4784fb12f4c01d6 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic disco eoan xenial yakkety zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1859112 Title: Xorg crashed with SIGSEGV in drmmode_output_create_resources() from xf86RandR12CreateObjects12() from xf86RandR12Init12() from xf86RandR12Init() from xf86CrtcScreenInit() Status in xorg-server package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.5+git20191008-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/5a8ef52c35776ebea6efc6dee4784fb12f4c01d6 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1859112/+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 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session
It seems the robots either can't or haven't yet got to providing analysis of those crash reports... In the meantime, immediately after each crash happens please run: journalctl -b0 > journal.txt and attach 'journal.txt' here. If you have to reboot after each crash before you can run that command then please use this instead: journalctl -b-1 > prevjournal.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/1853199 Title: Ctrl + c (copy) anywhere some times crashes gnome session Status in gnome-shell package in Ubuntu: Incomplete Bug description: Copy text anwyhere (browser, terminal) crashes user session and shows login screen. It may take few login attempts to actually login back. I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is always ON but tv is ON amd OFF as needed. Every time I turn tv ON and try to do something and use ctrl + c it would restart gnome session. After login it seem to work fine and ctrl+c does not break anything. Then the next day the similar thing happens. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 20:55:37 2019 DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 [1297:4057] InstallationDate: Installed on 2019-07-21 (121 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Shuttle Inc. XH270 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago) dmi.bios.date: 01/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.02 dmi.board.asset.tag: Default string dmi.board.name: FH270 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X dmi.product.name: XH270 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.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+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 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session
Please also ensure you have UNINSTALLED all gnome-shell extensions. -- 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/1853199 Title: Ctrl + c (copy) anywhere some times crashes gnome session Status in gnome-shell package in Ubuntu: Incomplete Bug description: Copy text anwyhere (browser, terminal) crashes user session and shows login screen. It may take few login attempts to actually login back. I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is always ON but tv is ON amd OFF as needed. Every time I turn tv ON and try to do something and use ctrl + c it would restart gnome session. After login it seem to work fine and ctrl+c does not break anything. Then the next day the similar thing happens. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 20:55:37 2019 DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 [1297:4057] InstallationDate: Installed on 2019-07-21 (121 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Shuttle Inc. XH270 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago) dmi.bios.date: 01/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.02 dmi.board.asset.tag: Default string dmi.board.name: FH270 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X dmi.product.name: XH270 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.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+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 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
** Tags added: eoan -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in LibreOffice: Confirmed Status in Mutter: New Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in libreoffice source package in Eoan: Triaged Status in mutter source package in Eoan: Triaged Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+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 1859101] Re: stuck on 800x600
Thanks for the bug report. The first thing I notice is that the kernel doesn't have a driver for your GPU because it seems to be QEMU's "-vga std" option. So Xorg defaults to 800x600 and does not support any other modes besides the default one... [27.274] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 24 [27.274] (==) FBDEV(0): RGB weight 888 [27.274] (==) FBDEV(0): Default visual is TrueColor [27.274] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0) [27.275] (II) FBDEV(0): hardware: EFI VGA (video memory: 1408kB) [27.275] (II) FBDEV(0): checking modes against framebuffer device... [27.275] (II) FBDEV(0): checking modes against monitor... [27.275] (--) FBDEV(0): Virtual size is 800x600 (pitch 800) [27.275] (**) FBDEV(0): Built-in mode "current": 48.0 MHz, 46.9 kHz, 75.1 Hz [27.275] (II) FBDEV(0): Modeline "current"x0.0 48.00 800 832 928 1024 600 604 608 624 -hsync -vsync -csync (46.9 kHz b) [27.275] (==) FBDEV(0): DPI set to (96, 96) This is understandably annoying, but your only other options are to: * Get SeaBIOS/QEMU to support other modes; or * Get QEMU to emulate a different GPU type using "-vga ..." ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Invalid -- 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/1859101 Title: stuck on 800x600 Status in xorg-server package in Ubuntu: Invalid Bug description: Intel integrated graphics, HPE DL360 Gen6 server VM running Ubuntu 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 10 00:22:23 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Device [1234:] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Device [1af4:1100] InstallationDate: Installed on 2020-01-06 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-74-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.1 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1912100730.f66d39~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1859101/+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 1859096] Re: No sound or Crazy sound on Display port since kernel change to 5.4 (but 5.3.0-24 works)
** Summary changed: - No sound or Crazy sound on Display port since kernel change to 5.4 + No sound or Crazy sound on Display port since kernel change to 5.4 (but 5.3.0-24 works) ** 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/1859096 Title: No sound or Crazy sound on Display port since kernel change to 5.4 (but 5.3.0-24 works) Status in linux package in Ubuntu: New Bug description: I use Nvidia driver 440. The sound became crazy on DisplayPort. Volume is not adjustable. I have either full volume or nothing. sound is crazy on my GTX1650 video card. If I use Nouveau driver I have no sound on my Display port. If I boot with 5.3.0-24 kernel sound is OK with Nivdia driver. But no sound with nouveau driver. Same things append on Focal and on Ubuntu 19.10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/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.44 Sun Dec 8 03:38:56 UTC 2019 GCC version: gcc version 9.2.1 20191130 (Ubuntu 9.2.1-21ubuntu1) ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: MATE Date: Fri Jan 10 00:26:20 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.44, 5.4.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU117 [GeForce GTX 1650] [1458:3fcb] InstallationDate: Installed on 2020-01-05 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104) MachineType: Micro-Star International Co., Ltd. MS-7B51 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=0b5d6829-5bb4-40e3-9fee-0fdec99e5f5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.50 dmi.board.asset.tag: Default string dmi.board.name: MPG Z390 GAMING PLUS (MS-7B51) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.50:bd02/21/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B51:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ390GAMINGPLUS(MS-7B51):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B51 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859096/+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 1424201] Re: Web browsers lacking hardware-accelerated video decoding
It looks like the VAAPI version is gone from the snap store again. Is there some reason why this hasn't been merged yet as mentioned in #96? -- 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/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Confirmed Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: The chromium team has done a great job to totally disable hardware decoding on Linux. Even ignoring the GPU blacklist does not enable GPU decoding. How ever the patch is quite simple and it's already working using this PPA ( using libVA ) : https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev the corresponding patch is here : http://bazaar.launchpad.net/~saiarcot895/chromium-browser/chromium- browser.trusty.beta/view/head:/debian/patches/enable_vaapi_on_linux.diff that would be great if we could have this patch indefault Ubuntu chromium build, this situation is really sad right now, google use linux to make chromeOS so chromebook are really good at playing videos but GNU/Linux chromium is slow at doing it. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+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 1859101] [NEW] stuck on 800x600
Public bug reported: Intel integrated graphics, HPE DL360 Gen6 server VM running Ubuntu 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 10 00:22:23 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Device [1234:] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Device [1af4:1100] InstallationDate: Installed on 2020-01-06 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-74-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.1 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1912100730.f66d39~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu uec-images -- 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/1859101 Title: stuck on 800x600 Status in xorg package in Ubuntu: New Bug description: Intel integrated graphics, HPE DL360 Gen6 server VM running Ubuntu 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 10 00:22:23 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Device [1234:] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Device [1af4:1100] InstallationDate: Installed on 2020-01-06 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-74-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.1 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri:
[Desktop-packages] [Bug 1859098] [NEW] Exiting Writer's Print Preview mode is slow in long documents
Public bug reported: (Cross-posting from https://bugs.documentfoundation.org/show_bug.cgi?id=129900 as problem not reproducible on Windows.) Compared to LibreOffice 5, exiting Print Preview in long documents on LO6 is extremely slow. With a 1,500 page document, for example, exiting Print Preview is instant in LO5, but takes 5-6 seconds (!) in LO6. To reproduce: 1. In LibreOffice 6 Writer, fill a document with text so that it comprises at least a few hundred pages. 2. Enter Print Preview (e.g. File -> Print Preview). 3. Observe it takes a second or two (based on document length) to display the Print Preview screen. This is similar to LibreOffice 5. 4. Press Escape to exit Print Preview mode. 5. Observe a significant delay (approx. 5-6 seconds for a 1,500 page document) with CPU usage spiking before returning to normal view. There is no such delay in LibreOffice 5.3.0.3 Writer. I tend to flip back and forth between Normal View and Print Preview when editing a document, and this new delay makes this very awkward. Ubuntu 19.10 Version: 6.3.4.2 Build ID: 1:6.3.4-0ubuntu0.19.10.1 CPU threads: 4; OS: Linux 5.3; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libreoffice-writer 1:6.3.4-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 10 10:53:20 2020 InstallationDate: Installed on 2013-04-11 (2464 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) SourcePackage: libreoffice UpgradeStatus: Upgraded to eoan on 2019-11-07 (63 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2015-03-26T08:56:12.843910 ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages -- 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/1859098 Title: Exiting Writer's Print Preview mode is slow in long documents Status in libreoffice package in Ubuntu: New Bug description: (Cross-posting from https://bugs.documentfoundation.org/show_bug.cgi?id=129900 as problem not reproducible on Windows.) Compared to LibreOffice 5, exiting Print Preview in long documents on LO6 is extremely slow. With a 1,500 page document, for example, exiting Print Preview is instant in LO5, but takes 5-6 seconds (!) in LO6. To reproduce: 1. In LibreOffice 6 Writer, fill a document with text so that it comprises at least a few hundred pages. 2. Enter Print Preview (e.g. File -> Print Preview). 3. Observe it takes a second or two (based on document length) to display the Print Preview screen. This is similar to LibreOffice 5. 4. Press Escape to exit Print Preview mode. 5. Observe a significant delay (approx. 5-6 seconds for a 1,500 page document) with CPU usage spiking before returning to normal view. There is no such delay in LibreOffice 5.3.0.3 Writer. I tend to flip back and forth between Normal View and Print Preview when editing a document, and this new delay makes this very awkward. Ubuntu 19.10 Version: 6.3.4.2 Build ID: 1:6.3.4-0ubuntu0.19.10.1 CPU threads: 4; OS: Linux 5.3; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libreoffice-writer 1:6.3.4-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 10 10:53:20 2020 InstallationDate: Installed on 2013-04-11 (2464 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) SourcePackage: libreoffice UpgradeStatus: Upgraded to eoan on 2019-11-07 (63 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2015-03-26T08:56:12.843910 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1859098/+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 1859096] [NEW] No sound or Crazy sound on Display port since kernel change to 5.4
Public bug reported: I use Nvidia driver 440. The sound became crazy on DisplayPort. Volume is not adjustable. I have either full volume or nothing. sound is crazy on my GTX1650 video card. If I use Nouveau driver I have no sound on my Display port. If I boot with 5.3.0-24 kernel sound is OK with Nivdia driver. But no sound with nouveau driver. Same things append on Focal and on Ubuntu 19.10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/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.44 Sun Dec 8 03:38:56 UTC 2019 GCC version: gcc version 9.2.1 20191130 (Ubuntu 9.2.1-21ubuntu1) ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: MATE Date: Fri Jan 10 00:26:20 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.44, 5.4.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU117 [GeForce GTX 1650] [1458:3fcb] InstallationDate: Installed on 2020-01-05 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104) MachineType: Micro-Star International Co., Ltd. MS-7B51 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=0b5d6829-5bb4-40e3-9fee-0fdec99e5f5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.50 dmi.board.asset.tag: Default string dmi.board.name: MPG Z390 GAMING PLUS (MS-7B51) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.50:bd02/21/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B51:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ390GAMINGPLUS(MS-7B51):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B51 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal reproducible single-occurrence 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/1859096 Title: No sound or Crazy sound on Display port since kernel change to 5.4 Status in xorg package in Ubuntu: New Bug description: I use Nvidia driver 440. The sound became crazy on DisplayPort. Volume is not adjustable. I have either full volume or nothing. sound is crazy on my GTX1650 video card. If I use Nouveau driver I have no sound on my Display port. If I boot with 5.3.0-24 kernel sound is OK with Nivdia driver. But no sound with nouveau driver. Same things append on Focal and on Ubuntu 19.10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/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.44 Sun Dec 8 03:38:56 UTC 2019 GCC version: gcc version 9.2.1 20191130 (Ubuntu 9.2.1-21ubuntu1) ApportVersion:
[Desktop-packages] [Bug 1858611] Re: package fonts-noto-core 20200103-1 failed to install/upgrade: trying to overwrite '/usr/share/fonts/truetype/noto/NotoSansJavanese-Bold.ttf', which is also in pack
** Changed in: fonts-noto (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto in Ubuntu. https://bugs.launchpad.net/bugs/1858611 Title: package fonts-noto-core 20200103-1 failed to install/upgrade: trying to overwrite '/usr/share/fonts/truetype/noto/NotoSansJavanese- Bold.ttf', which is also in package fonts-noto-unhinted 20181227-1 Status in fonts-noto package in Ubuntu: New Status in fonts-noto package in Debian: New Bug description: after upgrade packages ProblemType: Package DistroRelease: Ubuntu 20.04 Package: fonts-noto-core 20200103-1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Tue Jan 7 10:22:10 2020 Dependencies: ErrorMessage: trying to overwrite '/usr/share/fonts/truetype/noto/NotoSansJavanese-Bold.ttf', which is also in package fonts-noto-unhinted 20181227-1 InstallationDate: Installed on 2019-12-22 (15 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191221) PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.5 SourcePackage: fonts-noto Title: package fonts-noto-core 20200103-1 failed to install/upgrade: trying to overwrite '/usr/share/fonts/truetype/noto/NotoSansJavanese-Bold.ttf', which is also in package fonts-noto-unhinted 20181227-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto/+bug/1858611/+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 1838253] Re: Gigabyte X570 Aorus Elite: whine/beep when recording sound, not present under Windows
** Summary changed: - whine/beep when recording sound, not present under Windows + Gigabyte X570 Aorus Elite: whine/beep when recording sound, not present under Windows -- 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/1838253 Title: Gigabyte X570 Aorus Elite: whine/beep when recording sound, not present under Windows Status in alsa-driver package in Ubuntu: New Bug description: When recording sound under Ubuntu 18.04 there is a whine/beep present. This is not the case under Windows 10, as such I suspect missing driver/software bits. See attachments for audio samples of both cases. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-20.21~18.04.1-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: az 1795 F pulseaudio /dev/snd/controlC2: az 1795 F pulseaudio /dev/snd/pcmC2D0p: az 1795 F...m pulseaudio /dev/snd/controlC0: az 1795 F pulseaudio CurrentDesktop: XFCE Date: Mon Jul 29 12:44:43 2019 InstallationDate: Installed on 2019-07-17 (11 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4g dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4g:bd07/12/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1838253/+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 1859083] Re: Global menu in Kubuntu is gone in Firefox Beta 73.0 on Eoan
** Description changed: Using Plasma Desktop's Global Menu plasmoid on Kubuntu 19.10, the recent - Firefox Beta 73 updates do not have the Unity global menu feature - enabled. This feature was working only a couple of days ago. Not sure if - this is a regression or an intended removal of the global menu patch. + Firefox Beta 73 updates via Mozilla Team's firefox-next PPA do not have + the Unity global menu feature enabled. This feature was working only a + couple of days ago. Not sure if this is a regression or an intended + removal of the global menu patch. If you need any logs or debug information, I'll be happy to supply them. Thanks for everyone's work on this PPA, it's great :) -- 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/1859083 Title: Global menu in Kubuntu is gone in Firefox Beta 73.0 on Eoan Status in firefox package in Ubuntu: New Bug description: Using Plasma Desktop's Global Menu plasmoid on Kubuntu 19.10, the recent Firefox Beta 73 updates via Mozilla Team's firefox-next PPA do not have the Unity global menu feature enabled. This feature was working only a couple of days ago. Not sure if this is a regression or an intended removal of the global menu patch. If you need any logs or debug information, I'll be happy to supply them. Thanks for everyone's work on this PPA, it's great :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1859083/+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 1859083] [NEW] Global menu in Kubuntu is gone in Firefox Beta 73.0 on Eoan
Public bug reported: Using Plasma Desktop's Global Menu plasmoid on Kubuntu 19.10, the recent Firefox Beta 73 updates via Mozilla Team's firefox-next PPA do not have the Unity global menu feature enabled. This feature was working only a couple of days ago. Not sure if this is a regression or an intended removal of the global menu patch. If you need any logs or debug information, I'll be happy to supply them. Thanks for everyone's work on this PPA, it's great :) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/1859083 Title: Global menu in Kubuntu is gone in Firefox Beta 73.0 on Eoan Status in firefox package in Ubuntu: New Bug description: Using Plasma Desktop's Global Menu plasmoid on Kubuntu 19.10, the recent Firefox Beta 73 updates via Mozilla Team's firefox-next PPA do not have the Unity global menu feature enabled. This feature was working only a couple of days ago. Not sure if this is a regression or an intended removal of the global menu patch. If you need any logs or debug information, I'll be happy to supply them. Thanks for everyone's work on this PPA, it's great :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1859083/+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 1858611] Re: package fonts-noto-core 20200103-1 failed to install/upgrade: trying to overwrite '/usr/share/fonts/truetype/noto/NotoSansJavanese-Bold.ttf', which is also in pack
** Bug watch added: Debian Bug tracker #948331 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948331 ** Also affects: fonts-noto (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948331 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto in Ubuntu. https://bugs.launchpad.net/bugs/1858611 Title: package fonts-noto-core 20200103-1 failed to install/upgrade: trying to overwrite '/usr/share/fonts/truetype/noto/NotoSansJavanese- Bold.ttf', which is also in package fonts-noto-unhinted 20181227-1 Status in fonts-noto package in Ubuntu: New Status in fonts-noto package in Debian: Unknown Bug description: after upgrade packages ProblemType: Package DistroRelease: Ubuntu 20.04 Package: fonts-noto-core 20200103-1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Tue Jan 7 10:22:10 2020 Dependencies: ErrorMessage: trying to overwrite '/usr/share/fonts/truetype/noto/NotoSansJavanese-Bold.ttf', which is also in package fonts-noto-unhinted 20181227-1 InstallationDate: Installed on 2019-12-22 (15 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191221) PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.5 SourcePackage: fonts-noto Title: package fonts-noto-core 20200103-1 failed to install/upgrade: trying to overwrite '/usr/share/fonts/truetype/noto/NotoSansJavanese-Bold.ttf', which is also in package fonts-noto-unhinted 20181227-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto/+bug/1858611/+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 1859080] [NEW] NetworkMonitor.get_default() hangs consuming 100% of a core, blocking unattended-upgrades
Public bug reported: On an Ubuntu Server operating as a BGP router with over 800k routes, the call to NetworkMonitor.get_default() invoked by unattended-upgrades will hang indefinitely consuming a cpu core. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: python3-gi 3.20.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Thu Jan 9 16:03:20 2020 ProcEnviron: SHELL=/bin/bash TERM=xterm-kitty PATH=(custom, no user) LANG=en_US LANGUAGE=en_US: SourcePackage: pygobject UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pygobject (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1859080 Title: NetworkMonitor.get_default() hangs consuming 100% of a core, blocking unattended-upgrades Status in pygobject package in Ubuntu: New Bug description: On an Ubuntu Server operating as a BGP router with over 800k routes, the call to NetworkMonitor.get_default() invoked by unattended- upgrades will hang indefinitely consuming a cpu core. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: python3-gi 3.20.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Thu Jan 9 16:03:20 2020 ProcEnviron: SHELL=/bin/bash TERM=xterm-kitty PATH=(custom, no user) LANG=en_US LANGUAGE=en_US: SourcePackage: pygobject UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1859080/+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 397574]
68.4: https://hg.mozilla.org/releases/comm-esr68/rev/3f45fb298e6800a27449ca2acb4909d42108dc5d -- 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/397574 Title: Encoding problems after switching the layout Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: thunderbird steps to reproduce: - View -> Layout -> Classic View - View -> Layout -> enable Message Pane - select a message in which you can see special characters (e.g. ö,ä,ü...) - switch the layout, e.g. View -> Layout -> Wide View now you can see, that the special characters are displayed wrong (e.g. ö instead of ö) If you select another mail and select this mail again, the characters are displayed without problems! I think there is a problem with the encoding after switching the layout Regards scamp ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: mozilla-thunderbird 2.0.0.21+nobinonly-0ubuntu1.9.04.1 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird Uname: Linux 2.6.28-11-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/397574/+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 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
I'm experiencing the same bug since 2 weeks. Using Ubuntu 19.10, Libreoffice Calc 6.3.4.2 Build ID: 1:6.3.4-0ubuntu0.19.10.1. Please help! -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in LibreOffice: Confirmed Status in Mutter: New Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in libreoffice source package in Eoan: Triaged Status in mutter source package in Eoan: Triaged Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+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 1859073] [NEW] Gnome Software - rejected send message
Public bug reported: When I check for new updates on GNOME Software I get the follow error: gnome-software[3885]: not GsPlugin error FwupdError:0: Rejected send message, 3 matched rules; type="method_call", sender=":1.517" (uid=1000 pid=3885 comm="/usr/bin/gnome-software --gapplication-service " label="unconfined") interface="org.freedesktop.fwupd" member="GetRemotes" error name="(unset)" requested_reply="0" destination=":1.836" (uid=0 pid=11919 comm="/usr/lib/fwupd/fwupd " label="unconfined") $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ sudo apt-cache policy gnome-software gnome-software: Installed: 3.30.6-2ubuntu10.19.10.0 Candidate: 3.30.6-2ubuntu10.19.10.0 Version table: *** 3.30.6-2ubuntu10.19.10.0 500 500 http://ubuntu-archive.locaweb.com.br/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.30.6-2ubuntu10 500 500 http://ubuntu-archive.locaweb.com.br/ubuntu eoan/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10.19.10.0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 9 17:03:11 2020 InstallationDate: Installed on 2018-03-02 (677 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301) InstalledPlugins: gnome-software-plugin-flatpak 3.30.6-2ubuntu10.19.10.0 gnome-software-plugin-snap3.30.6-2ubuntu10.19.10.0 SourcePackage: gnome-software UpgradeStatus: Upgraded to eoan on 2019-10-22 (79 days ago) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Image from error" https://bugs.launchpad.net/bugs/1859073/+attachment/5318920/+files/error.png -- 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/1859073 Title: Gnome Software - rejected send message Status in gnome-software package in Ubuntu: New Bug description: When I check for new updates on GNOME Software I get the follow error: gnome-software[3885]: not GsPlugin error FwupdError:0: Rejected send message, 3 matched rules; type="method_call", sender=":1.517" (uid=1000 pid=3885 comm="/usr/bin/gnome-software --gapplication- service " label="unconfined") interface="org.freedesktop.fwupd" member="GetRemotes" error name="(unset)" requested_reply="0" destination=":1.836" (uid=0 pid=11919 comm="/usr/lib/fwupd/fwupd " label="unconfined") $ lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 $ sudo apt-cache policy gnome-software gnome-software: Installed: 3.30.6-2ubuntu10.19.10.0 Candidate: 3.30.6-2ubuntu10.19.10.0 Version table: *** 3.30.6-2ubuntu10.19.10.0 500 500 http://ubuntu-archive.locaweb.com.br/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.30.6-2ubuntu10 500 500 http://ubuntu-archive.locaweb.com.br/ubuntu eoan/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10.19.10.0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 9 17:03:11 2020 InstallationDate: Installed on 2018-03-02 (677 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301) InstalledPlugins: gnome-software-plugin-flatpak 3.30.6-2ubuntu10.19.10.0 gnome-software-plugin-snap3.30.6-2ubuntu10.19.10.0 SourcePackage: gnome-software UpgradeStatus: Upgraded to eoan on 2019-10-22 (79 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1859073/+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 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session
This was actually ctrl + x inside libreoffice calc 100% reproducable (did 3 times in a row). https://errors.ubuntu.com/oops/0a86d610-331b-11ea-b88b-fa163e102db1 https://errors.ubuntu.com/oops/615fd93e-3312-11ea-b1f4-fa163e983629 https://errors.ubuntu.com/oops/3279fd88-3188-11ea-a9c1-fa163e6cac46 -- 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/1853199 Title: Ctrl + c (copy) anywhere some times crashes gnome session Status in gnome-shell package in Ubuntu: Incomplete Bug description: Copy text anwyhere (browser, terminal) crashes user session and shows login screen. It may take few login attempts to actually login back. I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is always ON but tv is ON amd OFF as needed. Every time I turn tv ON and try to do something and use ctrl + c it would restart gnome session. After login it seem to work fine and ctrl+c does not break anything. Then the next day the similar thing happens. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 20:55:37 2019 DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 [1297:4057] InstallationDate: Installed on 2019-07-21 (121 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Shuttle Inc. XH270 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago) dmi.bios.date: 01/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.02 dmi.board.asset.tag: Default string dmi.board.name: FH270 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X dmi.product.name: XH270 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.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+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 1859043] Re: thunderbird completely broken after upgrade
This can be a duplicate of bug 1849542 - do you agree? -- 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/1859043 Title: thunderbird completely broken after upgrade Status in thunderbird package in Ubuntu: New Bug description: When trying to start thunderbird 1.68 with my 1.60 profile, the following error appears: JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined TypeError: aAttrDef.objectNounDef is undefined -- Exception object -- * -- Stack Trace -- defineAttribute@resource:///modules/gloda/gloda.js:1922:5 defineAttributes@resource:///modules/gloda/fundattr.js:71:35 init@resource:///modules/gloda/fundattr.js:43:12 @resource:///modules/gloda/everybody.js:13:15 @resource:///modules/gloda/public.js:8:57 nsAutoCompleteGloda@jar:file:///usr/lib/thunderbird/omni.ja!/components/glautocomp.js:516:32 createInstance@resource://gre/modules/XPCOMUtils.jsm:433:19 glodaSearch_XBL_Constructor@chrome://messenger/content/search.xml:73:16 JavaScript error: chrome://messenger/content/msgMail3PaneWindow.js, line 470: TypeError: TagUtils is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: chrome://messenger/content/mailWindowOverlay.js, line 172: TypeError: gFolderDisplay is null JavaScript error: chrome://messenger/content/mailWindowOverlay.js, line 172: TypeError: gFolderDisplay is null JavaScript error: chrome://messenger/content/mailWindowOverlay.js, line 172: TypeError: gFolderDisplay is null JavaScript error: chrome://messenger/content/msgMail3PaneWindow.js, line 780: TypeError: accountManager is undefined The result is a completely unusable thunderbird: the main window opens, but there are no messages and it is not possible to open any secondary window. Downgrading to 1.60 (from disco) solves this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1859043/+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 1853175] Re: [MIR] libmail-authenticationresults-perl
Maintained by Debian Perl Group, and has a subscriber. Promoting. $ change-override -c main -S libmail-authenticationresults-perl Override component to main libmail-authenticationresults-perl 1.20180923-2 in focal: universe/misc -> main libmail-authenticationresults-perl 1.20180923-2 in focal amd64: universe/perl/optional/100% -> main libmail-authenticationresults-perl 1.20180923-2 in focal arm64: universe/perl/optional/100% -> main libmail-authenticationresults-perl 1.20180923-2 in focal armhf: universe/perl/optional/100% -> main libmail-authenticationresults-perl 1.20180923-2 in focal i386: universe/perl/optional/100% -> main libmail-authenticationresults-perl 1.20180923-2 in focal ppc64el: universe/perl/optional/100% -> main libmail-authenticationresults-perl 1.20180923-2 in focal s390x: universe/perl/optional/100% -> main Override [y|N]? y 7 publications overridden. ** Changed in: libmail-authenticationresults-perl (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmail-authenticationresults-perl in Ubuntu. https://bugs.launchpad.net/bugs/1853175 Title: [MIR] libmail-authenticationresults-perl Status in libmail-authenticationresults-perl package in Ubuntu: Fix Released Bug description: [Availability] It is available for all architectures in the universe. https://launchpad.net/ubuntu/+source/libmail-authenticationresults- perl [Rationale] A new dependency of libmail-dkim-perl. [Security] No known CVEs. https://security-tracker.debian.org/tracker/source-package/libmail-authenticationresults-perl https://launchpad.net/ubuntu/+source/libmail-authenticationresults-perl/+cve [Quality assurance] - Desktop Packages team subscribed - dh_auto_test runs as part of build (353 tests) - autopkgtest capability was added in 1.20180923-2 [Dependencies] Depends on perl (already in main), libscalar-list-utils-perl (in universe, see bug #1854849) [Standards compliance] debhelper [Maintenance] The upstream does not appear to be very active but the package is maintained by the Debian perl team (testing and unstable) https://github.com/marcbradshaw/Mail-AuthenticationResults https://packages.debian.org/search?keywords=libmail-authenticationresults-perl=names=all=all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmail-authenticationresults-perl/+bug/1853175/+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 1851936] Re: User profile won't load after upgrade - prompt to create new profile
This bug was fixed in the package firefox -
72.0.1+build1-0ubuntu0.19.10.1
---
firefox (72.0.1+build1-0ubuntu0.19.10.1) eoan; urgency=medium
* New upstream stable release (72.0.1+build1)
* Fix creating the source tarball with recent versions of cargo
- debian/build/create-tarball.py
-- Olivier Tilloy Wed, 08 Jan 2020
15:53:48 +0100
--
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/1851936
Title:
User profile won't load after upgrade - prompt to create new profile
Status in firefox package in Ubuntu:
Fix Released
Bug description:
Did upgrade to focal fossa from standard Ubuntu 19.10. Existing
firefox profile won't load on starting, instead application wants new
default profile.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 70.0.1+build1-0ubuntu2
Uname: Linux 5.3.9-050309-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stefan 1861 F pulseaudio
/dev/snd/controlC0: stefan 1861 F pulseaudio
BuildID: 20191031000133
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 9 14:49:28 2019
DefaultProfileIncompatibleExtensions:
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
DefaultProfilePrefSources: prefs.js
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2019-05-02 (190 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
IpRoute:
default via 192.168.178.1 dev enp30s0 proto dhcp metric 100
169.254.0.0/16 dev enp30s0 scope link metric 1000
192.168.178.0/24 dev enp30s0 proto kernel scope link src 192.168.178.44
metric 100
MostRecentCrashID: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
Profile1 - LastVersion=70.0.1/20191031000133 (In use)
Profile0 (Default) - LastVersion=70.0.1/20191031091608 (Out of date)
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
UpgradeStatus: Upgraded to focal on 2019-11-09 (0 days ago)
dmi.bios.date: 04/23/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P5.80
dmi.board.name: AB350M-HDV
dmi.board.vendor: ASRock
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.:bvrP5.80:bd04/23/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1851936/+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 1851936] Re: User profile won't load after upgrade - prompt to create new profile
This bug was fixed in the package firefox -
72.0.1+build1-0ubuntu0.16.04.1
---
firefox (72.0.1+build1-0ubuntu0.16.04.1) xenial; urgency=medium
* New upstream stable release (72.0.1+build1)
-- Olivier Tilloy Wed, 08 Jan 2020
10:33:51 +0100
** Changed in: firefox (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: firefox (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1851936
Title:
User profile won't load after upgrade - prompt to create new profile
Status in firefox package in Ubuntu:
Fix Released
Bug description:
Did upgrade to focal fossa from standard Ubuntu 19.10. Existing
firefox profile won't load on starting, instead application wants new
default profile.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 70.0.1+build1-0ubuntu2
Uname: Linux 5.3.9-050309-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stefan 1861 F pulseaudio
/dev/snd/controlC0: stefan 1861 F pulseaudio
BuildID: 20191031000133
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 9 14:49:28 2019
DefaultProfileIncompatibleExtensions:
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
DefaultProfilePrefSources: prefs.js
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2019-05-02 (190 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
IpRoute:
default via 192.168.178.1 dev enp30s0 proto dhcp metric 100
169.254.0.0/16 dev enp30s0 scope link metric 1000
192.168.178.0/24 dev enp30s0 proto kernel scope link src 192.168.178.44
metric 100
MostRecentCrashID: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
Profile1 - LastVersion=70.0.1/20191031000133 (In use)
Profile0 (Default) - LastVersion=70.0.1/20191031091608 (Out of date)
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
UpgradeStatus: Upgraded to focal on 2019-11-09 (0 days ago)
dmi.bios.date: 04/23/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P5.80
dmi.board.name: AB350M-HDV
dmi.board.vendor: ASRock
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.:bvrP5.80:bd04/23/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1851936/+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 1856861] Re: Firefox 73 require C++17, not available in xenial
Firefox 73 is now in beta phase. -- 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/1856861 Title: Firefox 73 require C++17, not available in xenial Status in firefox package in Ubuntu: Triaged Bug description: Firefox trunk, to become version 73.0 in February 2020, has bumped its C++ requirement to C++17 (https://bugzilla.mozilla.org/show_bug.cgi?id=1560664). This requires a more recent version (>= 7) of libstdc++6 than what is currently available in xenial (5.4.0-6ubuntu1~16.04.12). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1856861/+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 1858504] Re: Firefox 72 Released
related: https://www.mozilla.org/en- US/security/advisories/mfsa2020-03/#CVE-2019-17026 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-17026 -- 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/1858504 Title: Firefox 72 Released Status in firefox package in Ubuntu: In Progress Bug description: New release of firefox today, see: https://www.phoronix.com/scan.php?page=news_item=Firefox-72-Available --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BuildID: 20191205220404 CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:722 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: firefox 71.0+build5-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=71.0/20191205220404 (In use) Tags: focal Uname: Linux 5.4.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1858504/+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 1848086] Re: Keyboard shortcuts to launch apps sometimes launch twice in Wayland sessions
When changing desktops with the command, for example, this problem manifests itself by sending an extra to whichever window is in the foreground. If a terminal is in the foreground, the characters "^[[1;7A" will be written. -- 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/1848086 Title: Keyboard shortcuts to launch apps sometimes launch twice in Wayland sessions Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Noticed that recently (past few days? since 3.34.1?) the key combinations that I have set to launch web browser or launch terminal end up launching two browsers or terminals instead of just one. Only happens ~50% of the time, but still pretty frequently. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mutter 3.34.1-1ubuntu1 Uname: Linux 5.3.0-custom x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 14 12:56:44 2019 InstallationDate: Installed on 2019-08-17 (58 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-18 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848086/+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 1859030] Re: libcairo2 does not install on Bionic (18.04)
I have now enabled bionic-updates, it must have been disabled in error. Thank you for your help, apologies for the unnecessary report. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1859030 Title: libcairo2 does not install on Bionic (18.04) Status in cairo package in Ubuntu: Invalid Bug description: Attempt at installing libcairo2-dev on a clean Bionic install fails as follows: $ sudo apt install libcairo2-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. libcairo2-dev : Depends: libcairo2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libcairo-gobject2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libxcb-shm0-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. Similar issues reported previously on Launchpad are: https://answers.launchpad.net/ubuntu/+source/cairo/+question/262830 and most recently on StackOverflow (just over a week ago) here: https://stackoverflow.com/questions/9437246/unable-to-install-cairo-package-under-linux $ lsb_release -a; uname -a; apt-cache policy libcairo2-dev No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic Linux gnuradio 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux libcairo2-dev: Installed: (none) Candidate: 1.15.10-2 Version table: 1.15.10-2 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1859030/+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 1859030] Re: libcairo2 does not install on Bionic (18.04)
Thanks for the update, closing the bug then since it was a local system configuration error and not an issue with the Ubuntu source ** Changed in: cairo (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1859030 Title: libcairo2 does not install on Bionic (18.04) Status in cairo package in Ubuntu: Invalid Bug description: Attempt at installing libcairo2-dev on a clean Bionic install fails as follows: $ sudo apt install libcairo2-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. libcairo2-dev : Depends: libcairo2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libcairo-gobject2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libxcb-shm0-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. Similar issues reported previously on Launchpad are: https://answers.launchpad.net/ubuntu/+source/cairo/+question/262830 and most recently on StackOverflow (just over a week ago) here: https://stackoverflow.com/questions/9437246/unable-to-install-cairo-package-under-linux $ lsb_release -a; uname -a; apt-cache policy libcairo2-dev No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic Linux gnuradio 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux libcairo2-dev: Installed: (none) Candidate: 1.15.10-2 Version table: 1.15.10-2 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1859030/+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 1859030] Re: libcairo2 does not install on Bionic (18.04)
If there is a simple way to downgrade packages from 18.04.1 to 18.04 I would be greatly appreciative if somebody could help me with this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1859030 Title: libcairo2 does not install on Bionic (18.04) Status in cairo package in Ubuntu: Invalid Bug description: Attempt at installing libcairo2-dev on a clean Bionic install fails as follows: $ sudo apt install libcairo2-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. libcairo2-dev : Depends: libcairo2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libcairo-gobject2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libxcb-shm0-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. Similar issues reported previously on Launchpad are: https://answers.launchpad.net/ubuntu/+source/cairo/+question/262830 and most recently on StackOverflow (just over a week ago) here: https://stackoverflow.com/questions/9437246/unable-to-install-cairo-package-under-linux $ lsb_release -a; uname -a; apt-cache policy libcairo2-dev No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic Linux gnuradio 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux libcairo2-dev: Installed: (none) Candidate: 1.15.10-2 Version table: 1.15.10-2 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1859030/+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 1859043] [NEW] thunderbird completely broken after upgrade
Public bug reported: When trying to start thunderbird 1.68 with my 1.60 profile, the following error appears: JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined TypeError: aAttrDef.objectNounDef is undefined -- Exception object -- * -- Stack Trace -- defineAttribute@resource:///modules/gloda/gloda.js:1922:5 defineAttributes@resource:///modules/gloda/fundattr.js:71:35 init@resource:///modules/gloda/fundattr.js:43:12 @resource:///modules/gloda/everybody.js:13:15 @resource:///modules/gloda/public.js:8:57 nsAutoCompleteGloda@jar:file:///usr/lib/thunderbird/omni.ja!/components/glautocomp.js:516:32 createInstance@resource://gre/modules/XPCOMUtils.jsm:433:19 glodaSearch_XBL_Constructor@chrome://messenger/content/search.xml:73:16 JavaScript error: chrome://messenger/content/msgMail3PaneWindow.js, line 470: TypeError: TagUtils is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: chrome://messenger/content/mailWindowOverlay.js, line 172: TypeError: gFolderDisplay is null JavaScript error: chrome://messenger/content/mailWindowOverlay.js, line 172: TypeError: gFolderDisplay is null JavaScript error: chrome://messenger/content/mailWindowOverlay.js, line 172: TypeError: gFolderDisplay is null JavaScript error: chrome://messenger/content/msgMail3PaneWindow.js, line 780: TypeError: accountManager is undefined The result is a completely unusable thunderbird: the main window opens, but there are no messages and it is not possible to open any secondary window. Downgrading to 1.60 (from disco) solves this issue. ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: 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/1859043 Title: thunderbird completely broken after upgrade Status in thunderbird package in Ubuntu: New Bug description: When trying to start thunderbird 1.68 with my 1.60 profile, the following error appears: JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined TypeError: aAttrDef.objectNounDef is undefined -- Exception object -- * -- Stack Trace -- defineAttribute@resource:///modules/gloda/gloda.js:1922:5 defineAttributes@resource:///modules/gloda/fundattr.js:71:35 init@resource:///modules/gloda/fundattr.js:43:12 @resource:///modules/gloda/everybody.js:13:15 @resource:///modules/gloda/public.js:8:57 nsAutoCompleteGloda@jar:file:///usr/lib/thunderbird/omni.ja!/components/glautocomp.js:516:32 createInstance@resource://gre/modules/XPCOMUtils.jsm:433:19 glodaSearch_XBL_Constructor@chrome://messenger/content/search.xml:73:16 JavaScript error: chrome://messenger/content/msgMail3PaneWindow.js, line 470: TypeError: TagUtils is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: chrome://messenger/content/mailWindowOverlay.js, line 172: TypeError: gFolderDisplay is null JavaScript error: chrome://messenger/content/mailWindowOverlay.js, line 172: TypeError: gFolderDisplay is null JavaScript error: chrome://messenger/content/mailWindowOverlay.js, line 172: TypeError: gFolderDisplay is null JavaScript error: chrome://messenger/content/msgMail3PaneWindow.js, line 780: TypeError: accountManager is undefined The result is a completely unusable thunderbird: the main window opens, but there are no messages and it is not possible to open any secondary window. Downgrading to 1.60 (from disco) solves this issue. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1859030] Re: libcairo2 does not install on Bionic (18.04)
I'm not certain whether I have bionic-updates enabled, although I have realised the issue has been caused by the versions of packages (namely 1.15.10-2ubuntu0.1) being more recent than 1.15.10-2, I guess this means that the system on which I am installing has indeed had some updates to the original Bionic package list. Apologies for the bug if this means it was filed in error, as this is my first time using Ubuntu in a while I did not expect these two versions to be different. I have manually downgraded all of the dependencies e.g.: $sudo apt install libcairo-gobject2=1.15.10-2 Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be DOWNGRADED: libcairo-gobject2 0 to upgrade, 0 to newly install, 1 to downgrade, 0 to remove and 0 not to upgrade. Need to get 17.2 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 libcairo-gobject2 amd64 1.15.10-2 [17.2 kB] Fetched 17.2 kB in 0s (506 kB/s) Which has allowed me to correctly install libcairo2-dev as required. One perhaps useful update to come from this would be adjusting libcairo2-dev's dependencies to include those packages from the Bionic updates. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1859030 Title: libcairo2 does not install on Bionic (18.04) Status in cairo package in Ubuntu: Incomplete Bug description: Attempt at installing libcairo2-dev on a clean Bionic install fails as follows: $ sudo apt install libcairo2-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. libcairo2-dev : Depends: libcairo2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libcairo-gobject2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libxcb-shm0-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. Similar issues reported previously on Launchpad are: https://answers.launchpad.net/ubuntu/+source/cairo/+question/262830 and most recently on StackOverflow (just over a week ago) here: https://stackoverflow.com/questions/9437246/unable-to-install-cairo-package-under-linux $ lsb_release -a; uname -a; apt-cache policy libcairo2-dev No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic Linux gnuradio 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux libcairo2-dev: Installed: (none) Candidate: 1.15.10-2 Version table: 1.15.10-2 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1859030/+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 1749562] Re: openvpn tls-crypt not working
I'm not a programmer but I'll be happy to do whatever I can to facilitate getting this resolved. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1749562 Title: openvpn tls-crypt not working Status in network-manager package in Ubuntu: Confirmed Bug description: Hi, if i try to connect to my openvpn 2.4 server i got this error on serverside: Feb 14 18:42:22 fenrir openvpn[58665]: tls-crypt unwrap error: packet too short Feb 14 18:42:22 fenrir openvpn[58665]: TLS Error: tls-crypt unwrapping failed from [AF_INET6]:::91.33.41.15:51754 (via :::192.168.2.2%igb0) my server conf: dev ovpns1 verb 1 dev-type tun dev-node /dev/tun1 writepid /var/run/openvpn_server1.pid #user nobody #group nobody script-security 3 daemon keepalive 10 60 ping-timer-rem persist-tun persist-key proto udp cipher AES-256-CBC auth SHA512 up /usr/local/sbin/ovpn-linkup down /usr/local/sbin/ovpn-linkdown client-connect /usr/local/sbin/openvpn.attributes.sh client-disconnect /usr/local/sbin/openvpn.attributes.sh multihome engine cryptodev tls-server server 10.4.0.0 255.255.0.0 client-config-dir /var/etc/openvpn-csc/server1 username-as-common-name auth-user-pass-verify "/usr/local/sbin/ovpn_auth_verify user ZmVucmly false server1 1194" via-env tls-verify "/usr/local/sbin/ovpn_auth_verify tls 'domain.local' 1" lport 1194 management /var/etc/openvpn/server1.sock unix ca /var/etc/openvpn/server1.ca cert /var/etc/openvpn/server1.cert key /var/etc/openvpn/server1.key dh /etc/dh-parameters.4096 tls-crypt /var/etc/openvpn/server1.tls-crypt ncp-ciphers AES-256-CBC persist-remote-ip float topology subnet my client config: dev tun persist-tun persist-key cipher AES-256-CBC ncp-ciphers AES-256-CBC auth SHA512 tls-client client resolv-retry infinite remote tuxist.ddns.net 1194 udp verify-x509-name "domain.local" name auth-user-pass remote-cert-tls server ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.8.4-1ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Wed Feb 14 18:46:29 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-13 (550 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 10.3.0.1 dev wlp3s0 proto static metric 600 10.3.0.0/16 dev wlp3s0 proto kernel scope link src 10.3.141.174 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-02-12 (1 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 gameofgods 404f7dfd-a05c-4271-9a7f-6e18bc31e0cf /org/freedesktop/NetworkManager/ActiveConnection/2 eno1ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1749562/+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 1859030] Re: libcairo2 does not install on Bionic (18.04)
Thank you for your bug report, it looks like the SRU from https://launchpad.net/ubuntu/+source/cairo/1.15.10-2ubuntu0.1 is not correctly available, do you have bionic-updates enabled for universe? ** Changed in: cairo (Ubuntu) Importance: Undecided => Low ** Changed in: cairo (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1859030 Title: libcairo2 does not install on Bionic (18.04) Status in cairo package in Ubuntu: Incomplete Bug description: Attempt at installing libcairo2-dev on a clean Bionic install fails as follows: $ sudo apt install libcairo2-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. libcairo2-dev : Depends: libcairo2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libcairo-gobject2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libxcb-shm0-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. Similar issues reported previously on Launchpad are: https://answers.launchpad.net/ubuntu/+source/cairo/+question/262830 and most recently on StackOverflow (just over a week ago) here: https://stackoverflow.com/questions/9437246/unable-to-install-cairo-package-under-linux $ lsb_release -a; uname -a; apt-cache policy libcairo2-dev No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic Linux gnuradio 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux libcairo2-dev: Installed: (none) Candidate: 1.15.10-2 Version table: 1.15.10-2 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1859030/+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 1846790] Re: [upstream] Saving files with a '#' in the name silently(!) fails on GVFS smb:// paths (Samba share)
** Summary changed: - Saving files with a '#' in the name silently(!) fails on GVFS smb:// paths (Samba share) + [upstream] Saving files with a '#' in the name silently(!) fails on GVFS smb:// paths (Samba share) -- 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/1846790 Title: [upstream] Saving files with a '#' in the name silently(!) fails on GVFS smb:// paths (Samba share) Status in LibreOffice: New Status in libreoffice package in Ubuntu: Confirmed Bug description: [Reported via ubuntu-bug, I'm assuming it has gathered all relevant system info. More, especially on the Samba server, if required, is available on request.] What I'm trying to do: Save a file whose name contains a '#' character to a Samba share accessed via a GVFS smb:// path. Ex. 1: Open a blank Writer (ODT) document, save that under the name "Test #1.odt" on a Samba share mounted via Nautilus. Ex. 2: Open a pre-existing file "Test #2.odt", either via Nautilus or File-Open, make some changes, save it & quit. What I'm expecting to happen: The file shows up under the assigned name on both the client and the Samba server (in case of a new file); or the existing file now contains the changes made (in case of an existing file being modified). Ex. 1: I'd expect to see "Test #1.odt" in the relevant directory. Ex. 2: I'd expect "Test #2.odt" to contain my changes. What happens instead: Ex. 1: LibreOffice actually saves the data in a file named "TFNZPF~F" as seen from the client, "Test " [note the space at the end] on the server. Ex. 2: The original file remains untouched, but a new file "TFNZPF~F" (client), or "Test " (server) is created with the saved data. Effectively, the save operation does not succeed -- without any error message. Analysis: This is based on experiments with more complex filenames. Somehow, when LibreOffice saves a file in this constellation, the filename gets truncated at the first '#', inclusive, first, suffix and all. (This in turn leaves a filename ending in a space, which isn't legal under Windows, so Samba's name mangling kicks in.) The problem does not occur with local files or on a sshfs-mount. Gedit has no problem even on smb://. It's unclear whether '#' is the only character affected. Some kind of URL handling/escaping bug in LibreOffice's GIO support? In any case, this cost me a day of work. (By the time I realised my changes hadn't actually been lost but landed in a new, cryptically- named file, I'd already recreated it to meet the deadline.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-gnome 1:6.0.7-0ubuntu0.18.04.10 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 4 17:12:21 2019 InstallationDate: Installed on 2019-09-23 (10 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1846790/+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 1848086] Re: Keyboard shortcuts to launch apps sometimes launch twice in Wayland sessions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1848086 Title: Keyboard shortcuts to launch apps sometimes launch twice in Wayland sessions Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Noticed that recently (past few days? since 3.34.1?) the key combinations that I have set to launch web browser or launch terminal end up launching two browsers or terminals instead of just one. Only happens ~50% of the time, but still pretty frequently. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mutter 3.34.1-1ubuntu1 Uname: Linux 5.3.0-custom x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 14 12:56:44 2019 InstallationDate: Installed on 2019-08-17 (58 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-18 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848086/+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 1848086] Re: Keyboard shortcuts to launch apps sometimes launch twice in Wayland sessions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1848086 Title: Keyboard shortcuts to launch apps sometimes launch twice in Wayland sessions Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Noticed that recently (past few days? since 3.34.1?) the key combinations that I have set to launch web browser or launch terminal end up launching two browsers or terminals instead of just one. Only happens ~50% of the time, but still pretty frequently. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mutter 3.34.1-1ubuntu1 Uname: Linux 5.3.0-custom x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 14 12:56:44 2019 InstallationDate: Installed on 2019-08-17 (58 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-18 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848086/+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 1852183]
Reportedly, if the Clipboard Indicator GNOME Shell Extension was installed, removing that cured the symptom. -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in LibreOffice: Confirmed Status in Mutter: New Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in libreoffice source package in Eoan: Triaged Status in mutter source package in Eoan: Triaged Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+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 1852183]
The corresponding Mutter bug is https://gitlab.gnome.org/GNOME/mutter/issues/919 -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in LibreOffice: Confirmed Status in Mutter: New Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in libreoffice source package in Eoan: Triaged Status in mutter source package in Eoan: Triaged Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+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 1796698]
Mike Kaganski committed a patch related to this issue. It has been pushed to "libreoffice-6-3": https://git.libreoffice.org/core/commit/6599bdfd7a108617e7b920a7ebe30cd1da585718 tdf#120502: Excel doesn't increment max column for OOXML It will be available in 6.3.5. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- 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/1796698 Title: [upstream] Assigns style to columns it cannot handle in .xlsx files Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) Open LibreOffice Calc 2) File > New > Spreadsheet 3) File > Save As, choose name vanilla.xlsx > Save Extract contents of vanilla.xlsx file to some directory. In the xl/worksheets/sheet1.xml file in the node worksheet/cols/ you'll find node LibreOffice Calc can handle only 1024 columns, but style says it apply to 1025. If such .xlsx document is processed with PhpOffice and single cell value is written, nodes gets expanded, including for . This column cannot be processed by LibreOffice Calc and produces warnings that some information is lost. Value should be at most 1024 (or whatever limit is in 6.1). File produced on my copy of libreoffice is attached. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-calc 1:6.0.6-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 18:08:43 2018 InstallationDate: Installed on 2018-04-11 (180 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1796698/+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 1796698]
(In reply to Kevin Suo from comment #8) > Mike Kaganski: Thanks for the fix. Any plan to backport this to > libreoffice-6-3 and libreoffice-6-4 branch? Backported to 6-4: https://gerrit.libreoffice.org/c/core/+/86428 -- 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/1796698 Title: [upstream] Assigns style to columns it cannot handle in .xlsx files Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) Open LibreOffice Calc 2) File > New > Spreadsheet 3) File > Save As, choose name vanilla.xlsx > Save Extract contents of vanilla.xlsx file to some directory. In the xl/worksheets/sheet1.xml file in the node worksheet/cols/ you'll find node LibreOffice Calc can handle only 1024 columns, but style says it apply to 1025. If such .xlsx document is processed with PhpOffice and single cell value is written, nodes gets expanded, including for . This column cannot be processed by LibreOffice Calc and produces warnings that some information is lost. Value should be at most 1024 (or whatever limit is in 6.1). File produced on my copy of libreoffice is attached. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-calc 1:6.0.6-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 18:08:43 2018 InstallationDate: Installed on 2018-04-11 (180 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1796698/+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 1796698]
Mike Kaganski committed a patch related to this issue. It has been pushed to "libreoffice-6-4": https://git.libreoffice.org/core/commit/925be88167868798c97ff1f66dcdb9bd3bbec1e2 tdf#120502: Excel doesn't increment max column for OOXML It will be available in 6.4.0.2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- 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/1796698 Title: [upstream] Assigns style to columns it cannot handle in .xlsx files Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) Open LibreOffice Calc 2) File > New > Spreadsheet 3) File > Save As, choose name vanilla.xlsx > Save Extract contents of vanilla.xlsx file to some directory. In the xl/worksheets/sheet1.xml file in the node worksheet/cols/ you'll find node LibreOffice Calc can handle only 1024 columns, but style says it apply to 1025. If such .xlsx document is processed with PhpOffice and single cell value is written, nodes gets expanded, including for . This column cannot be processed by LibreOffice Calc and produces warnings that some information is lost. Value should be at most 1024 (or whatever limit is in 6.1). File produced on my copy of libreoffice is attached. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-calc 1:6.0.6-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 18:08:43 2018 InstallationDate: Installed on 2018-04-11 (180 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1796698/+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 1852183]
Note that a selection's content is not stored in the clipboard (unless LibreOffice is exited) but upon pasting the target asks for the available formats and picks the best offered, that in this case should be the internal Calc format, which then would be transferred from source to target, but somehow here instead it gets a bitmap/image from the clipboard "manager" (apparently). (In reply to Marcus Tomlinson from comment #1) > However, LibreOffice does seem to be doing something strange in its type > requests from the clipboard (stand by for a comment from a colleague with > more mutter knowledge), so I suspect there may be fault on both ends here. So what would that "doing something strange" be? -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in LibreOffice: Confirmed Status in Mutter: New Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in libreoffice source package in Eoan: Triaged Status in mutter source package in Eoan: Triaged Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+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 1859033] Re: guile-2.2 installed but not guild-2.2
As a test, download https://github.com/TaylanUB/scheme- bytestructures/releases/download/v1.0.7/bytestructures-1.0.7.tar.gz, unpack and run ./configure in the top directory. Then check the Makefile and notice that GUILE is defined but not GUILD. "make" will fail for that reason. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to guile-2.2 in Ubuntu. https://bugs.launchpad.net/bugs/1859033 Title: guile-2.2 installed but not guild-2.2 Status in guile-2.2 package in Ubuntu: New Bug description: guile-2.2 package apparently installs guile, guile-2.2 and guild in /usr/bin, but not guild-2.2. This causes packages using configure w/ guile.m4 macros to fail: GUILE is defined but not GUILD. So builds which use commands (in the Makefiles) of the form "$(GUILD) compile ..." will fail. Suggest adding guild-2.2 to the install process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: guile-2.2 2.2.3+1-3ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 9 06:30:37 2020 InstallationDate: Installed on 2019-02-03 (339 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: guile-2.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/guile-2.2/+bug/1859033/+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 1859033] [NEW] guile-2.2 installed but not guild-2.2
Public bug reported: guile-2.2 package apparently installs guile, guile-2.2 and guild in /usr/bin, but not guild-2.2. This causes packages using configure w/ guile.m4 macros to fail: GUILE is defined but not GUILD. So builds which use commands (in the Makefiles) of the form "$(GUILD) compile ..." will fail. Suggest adding guild-2.2 to the install process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: guile-2.2 2.2.3+1-3ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 9 06:30:37 2020 InstallationDate: Installed on 2019-02-03 (339 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: guile-2.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: guile-2.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to guile-2.2 in Ubuntu. https://bugs.launchpad.net/bugs/1859033 Title: guile-2.2 installed but not guild-2.2 Status in guile-2.2 package in Ubuntu: New Bug description: guile-2.2 package apparently installs guile, guile-2.2 and guild in /usr/bin, but not guild-2.2. This causes packages using configure w/ guile.m4 macros to fail: GUILE is defined but not GUILD. So builds which use commands (in the Makefiles) of the form "$(GUILD) compile ..." will fail. Suggest adding guild-2.2 to the install process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: guile-2.2 2.2.3+1-3ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 9 06:30:37 2020 InstallationDate: Installed on 2019-02-03 (339 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: guile-2.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/guile-2.2/+bug/1859033/+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 1859030] [NEW] libcairo2 does not install on Bionic (18.04)
Public bug reported: Attempt at installing libcairo2-dev on a clean Bionic install fails as follows: $ sudo apt install libcairo2-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. libcairo2-dev : Depends: libcairo2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libcairo-gobject2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libxcb-shm0-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. Similar issues reported previously on Launchpad are: https://answers.launchpad.net/ubuntu/+source/cairo/+question/262830 and most recently on StackOverflow (just over a week ago) here: https://stackoverflow.com/questions/9437246/unable-to-install-cairo-package-under-linux $ lsb_release -a; uname -a; apt-cache policy libcairo2-dev No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic Linux gnuradio 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux libcairo2-dev: Installed: (none) Candidate: 1.15.10-2 Version table: 1.15.10-2 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: cairo (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1859030 Title: libcairo2 does not install on Bionic (18.04) Status in cairo package in Ubuntu: New Bug description: Attempt at installing libcairo2-dev on a clean Bionic install fails as follows: $ sudo apt install libcairo2-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. libcairo2-dev : Depends: libcairo2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libcairo-gobject2 (= 1.15.10-2) but 1.15.10-2ubuntu0.1 is to be installed Depends: libxcb-shm0-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. Similar issues reported previously on Launchpad are: https://answers.launchpad.net/ubuntu/+source/cairo/+question/262830 and most recently on StackOverflow (just over a week ago) here: https://stackoverflow.com/questions/9437246/unable-to-install-cairo-package-under-linux $ lsb_release -a; uname -a; apt-cache policy libcairo2-dev No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic Linux gnuradio 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux libcairo2-dev: Installed: (none) Candidate: 1.15.10-2 Version table: 1.15.10-2 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1859030/+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 1859031] [NEW] Cursor freezes with synergy software kvm
Public bug reported: I'm using the synergy software KVM to share a mouse and keyboard between two machines, with my Ubuntu workstation as the client. When attempting to drag-and-drop within Qt apps, the mouse cursor will freeze for several seconds. Cursor freezes also occur intermittently as well. I have an issue report for synergy as well: https://github.com/symless /synergy-core/issues/6487 This issue seems to be a regression related to update 1.6.4-3ubuntu0.2. The current workaround is to pin all libx11 packages to the previous (0.1) versions. Release Version: Ubuntu 18.04.3 LTS Package Version: libx11-6:amd64 2:1.6.4-3ubuntu0.2 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libx11-6 2:1.6.4-3ubuntu0.1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-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.33.01 Wed Nov 13 00:00:22 UTC 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Jan 9 09:13:29 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GP104GLM [Quadro P5200 Mobile] [10de:1bb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP104GLM [Quadro P5200 Mobile] [1028:1832] InstallationDate: Installed on 2018-07-30 (527 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Precision 7730 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=6599bc95-d2cf-4bb0-b32d-653b78ae0fe9 ro quiet splash acpi=force vt.handoff=1 SourcePackage: libx11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0MG0JR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd11/11/2019:svnDellInc.:pnPrecision7730:pvr:rvnDellInc.:rn0MG0JR:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7730 dmi.product.sku: 0832 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: libx11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic possible-manual-nvidia-install ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1859031 Title: Cursor freezes with synergy software kvm Status in libx11 package in Ubuntu: New Bug description: I'm using the synergy software KVM to share a mouse and keyboard between two machines, with my Ubuntu workstation as the client. When attempting to drag-and-drop within Qt apps, the mouse cursor will freeze for several seconds. Cursor freezes also occur intermittently as well. I have an issue report for synergy as well: https://github.com/symless/synergy-core/issues/6487 This issue seems to be a regression related to update 1.6.4-3ubuntu0.2. The current workaround is to pin all libx11 packages to the previous (0.1) versions. Release Version: Ubuntu 18.04.3 LTS Package Version: libx11-6:amd64 2:1.6.4-3ubuntu0.2 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libx11-6 2:1.6.4-3ubuntu0.1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-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.33.01 Wed Nov 13 00:00:22 UTC 2019
[Desktop-packages] [Bug 1851322] Re: VPN auto-connect is not working
** Changed in: gnome-shell Status: New => Fix Released -- 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/1851322 Title: VPN auto-connect is not working Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hi, This is a duplicate of bug: https://bugs.launchpad.net/network-manager/+bug/1718931 It is marked as fixed, but the feature is still broken for me. I configured my Wifi connection to automatically connect to a VPN, but it only works if I manually connect to the Wifi via NetworkManager. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 5 04:07:00 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-09-26 (39 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1851322/+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 1736164] Re: deja-dup/duplicity backup fails with UnicodeDecodeError
*** This bug is a duplicate of bug 1770929 ***
https://bugs.launchpad.net/bugs/1770929
Seeing it on Ubuntu 18.04.3 LTS
De ja Dup: 37.0
backups fail
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
File "/usr/bin/duplicity", line 1511, in do_backup
full_backup(col_stats)
File "/usr/bin/duplicity", line 572, in full_backup
globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
(tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
146, in schedule_task
return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
172, in __run_synchronously
ret = fn(*params)
File "/usr/bin/duplicity", line 453, in
vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in
inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37:
ordinal not in range(128)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1736164
Title:
deja-dup/duplicity backup fails with UnicodeDecodeError
Status in Déjà Dup:
Triaged
Status in Duplicity:
New
Status in deja-dup package in Ubuntu:
Triaged
Status in deja-dup package in Fedora:
Fix Released
Bug description:
See: https://bugzilla.redhat.com/show_bug.cgi?id=1470873
Description of problem:
With the update from Fedora 25 to Fedora 26 Workstation, backups with
deja-dup/duplicity are failing
Version-Release number of selected component (if applicable):
duplicity 0.7.13.1
deja-dup 34.3
How reproducible:
Always (scheduled and manually started backup)
Steps to Reproduce:
1. Wait for the scheduled backup to start or start it via the "Backup now"
button
2. Some or a large number of files might get backed up, then the backup stops
with "Failed with an unknown error"
3.
Actual results:
Backup fails
Expected results:
Backup completes as it always did
Additional info:
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1540, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1534, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1385, in main
do_backup(action)
File "/usr/bin/duplicity", line 1516, in do_backup
incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
globals.backend)
File "/usr/bin/duplicity", line 453, in write_multivol
(tdp, dest_filename, vol_num)))
File "/usr/lib64/python2.7/site-packages/duplicity/asyncscheduler.py", line
146, in schedule_task
return self.__run_synchronously(fn, params)
File "/usr/lib64/python2.7/site-packages/duplicity/asyncscheduler.py", line
172, in __run_synchronously
ret = fn(*params)
File "/usr/bin/duplicity", line 452, in
vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 341, in put
backend.put(tdp, dest_filename)
File "/usr/lib64/python2.7/site-packages/duplicity/backend.py", line 376,
in inner_retry
% exception_traceback())
File "/usr/lib64/python2.7/site-packages/duplicity/util.py", line 51, in
exception_traceback
return uexc(msg)
File "/usr/lib64/python2.7/site-packages/duplicity/util.py", line 79, in
uexc
e = unicode(e).encode('utf-8')
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 746:
ordinal not in range(128)
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1736164/+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 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
Can also confirm being affected by this bug. Strangely it randomly happens in LibreOffice for me, but constantly in WPS Office. When I copy something it either pasts nothing (suggesting nothing was copied) or pasts as a bitmap. Sometimes this bitmap shows all content that was copied, sometimes a random bit. When it pasts a bitmap, re-copying everything and then pasting does always work. -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in LibreOffice: Confirmed Status in Mutter: New Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in libreoffice source package in Eoan: Triaged Status in mutter source package in Eoan: Triaged Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+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 1856846] Re: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work)
** Attachment added: "lspcik.txt (new)" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1856846/+attachment/5318841/+files/lspcik.txt -- 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/1856846 Title: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work) Status in xorg-server package in Ubuntu: Incomplete Bug description: When trying to login to Gnome with an remote user from an LDAP (LDAP is available and connectable when in GDM) using X11, GDM loops around three to five times before actually granting access to the desktop. This does not happen when a) Wayland is used instead of X11 or, b) the LDAP server is not reachable during login, using X11, or c) a local user is logged in instead, using X11 The LDAP connection is established using the Univention Domain Join Client: https://launchpad.net/~univention- dev/+archive/ubuntu/ppa?field.series_filter=bionic Do you require additional information? Release: Description: Ubuntu 18.04.3 LTS Release: 18.04 GDM3: gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1856846/+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 1856846] Re: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work)
Attached are the three log files, and a new crash report (upload now worked with apport-cli): https://errors.ubuntu.com/oops/327a1f18-32cd- 11ea-b1f2-fa163e983629 -- 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/1856846 Title: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work) Status in xorg-server package in Ubuntu: Incomplete Bug description: When trying to login to Gnome with an remote user from an LDAP (LDAP is available and connectable when in GDM) using X11, GDM loops around three to five times before actually granting access to the desktop. This does not happen when a) Wayland is used instead of X11 or, b) the LDAP server is not reachable during login, using X11, or c) a local user is logged in instead, using X11 The LDAP connection is established using the Univention Domain Join Client: https://launchpad.net/~univention- dev/+archive/ubuntu/ppa?field.series_filter=bionic Do you require additional information? Release: Description: Ubuntu 18.04.3 LTS Release: 18.04 GDM3: gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1856846/+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 1856846] Re: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work)
dmesg.txt (new) ** Attachment added: "dmesg.txt (new)" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1856846/+attachment/5318840/+files/dmesg.txt -- 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/1856846 Title: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work) Status in xorg-server package in Ubuntu: Incomplete Bug description: When trying to login to Gnome with an remote user from an LDAP (LDAP is available and connectable when in GDM) using X11, GDM loops around three to five times before actually granting access to the desktop. This does not happen when a) Wayland is used instead of X11 or, b) the LDAP server is not reachable during login, using X11, or c) a local user is logged in instead, using X11 The LDAP connection is established using the Univention Domain Join Client: https://launchpad.net/~univention- dev/+archive/ubuntu/ppa?field.series_filter=bionic Do you require additional information? Release: Description: Ubuntu 18.04.3 LTS Release: 18.04 GDM3: gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1856846/+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 1856846] Re: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work)
** Attachment added: "prevboot.txt (new)" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1856846/+attachment/5318842/+files/prevboot.txt -- 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/1856846 Title: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work) Status in xorg-server package in Ubuntu: Incomplete Bug description: When trying to login to Gnome with an remote user from an LDAP (LDAP is available and connectable when in GDM) using X11, GDM loops around three to five times before actually granting access to the desktop. This does not happen when a) Wayland is used instead of X11 or, b) the LDAP server is not reachable during login, using X11, or c) a local user is logged in instead, using X11 The LDAP connection is established using the Univention Domain Join Client: https://launchpad.net/~univention- dev/+archive/ubuntu/ppa?field.series_filter=bionic Do you require additional information? Release: Description: Ubuntu 18.04.3 LTS Release: 18.04 GDM3: gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1856846/+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 1311990] Re: Switching keyboard layouts from some non-English to Japanese (Anthy, Mozc) does not work on 14.04 and 18.04
hm, this bug was fixed for jp (anthy) by adding korean layout (anthy). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-anthy in Ubuntu. https://bugs.launchpad.net/bugs/1311990 Title: Switching keyboard layouts from some non-English to Japanese (Anthy, Mozc) does not work on 14.04 and 18.04 Status in ibus-anthy package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 14.04 LTS with multiple keyboard layouts: English (US) – Thai – Japanese (Anthy, Mozc), as appeared in Text Entry settings. The problem is that … when I cycle through the layouts in this order [EN → TH → JP], I would have expected to be able to type Japanese properly; however, although the indicator on the top right says JP, the output was still in TH. However, if I cycle in the reverse order [TH → EN → JP], the Japanese input works correctly. In more details, whenever I switch to JP from TH (by switching to "next" input if TH precedes JP in the settings, or by switching to "previous" input if TH succeeds JP in the settings), the output is in TH instead of JP (but the indicator is already in JP). On the other hand, switching to JP from EN works fine. Here's what the output from apt-cache policy ibus: ibus: Installed: 1.5.5-1ubuntu3 Candidate: 1.5.5-1ubuntu3 Version table: *** 1.5.5-1ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-anthy/+bug/1311990/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
Never mind the however part, it is fixed. -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. [Test Case] 0. Plug in a monitor that supports HDMI audio (one that appears in your Settings>Sound) 1. Log out and in again. Verify the default audio device in Settings is still speakers or headphones. Not the monitor's HDMI audio device. [Regression Potential] The behaviour is changed back to what it was before 19.10, some users might find it inconvenient and prefer the auto switch but the feedback we got shows it's unreliable and an annoying for the majority of our users so we will got back to default to safest behaviour. The fix proposed just reverts to the same code used in PulseAudio 12 and earlier. It has also been released and verified on focal already. [Workaround] Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
I can confirm that hdmi is not selected when monitor returns from sleep (I did something and the correct sound device would be selected at startup before updating from proposed). However, closing and reopening the monitor manually causes HDMI to be selected. I don't think that used to happen previously. -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. [Test Case] 0. Plug in a monitor that supports HDMI audio (one that appears in your Settings>Sound) 1. Log out and in again. Verify the default audio device in Settings is still speakers or headphones. Not the monitor's HDMI audio device. [Regression Potential] The behaviour is changed back to what it was before 19.10, some users might find it inconvenient and prefer the auto switch but the feedback we got shows it's unreliable and an annoying for the majority of our users so we will got back to default to safest behaviour. The fix proposed just reverts to the same code used in PulseAudio 12 and earlier. It has also been released and verified on focal already. [Workaround] Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1838838] Re: username is not saved in openconnect connection dialog
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/328 ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/issues #328 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/328 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1838838 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Confirmed Status in network-manager-openconnect package in Ubuntu: Confirmed Bug description: Same issue as https://bugs.launchpad.net/ubuntu/+source/network- manager-openconnect/+bug/1609700 This was marked resolved. The report of its reappearance in Ubuntu 19.04 and 19.10 has not been acknowledged. This was working for me in 18.10, but a fresh install of 19.04 and 19.10 show that it is back. The password is saved when the option to save passwords is selected, but the username must be entered manually upon connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1838838/+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 1858860] Re: Gnome Disk Utility Issues incorrect command when ejecting a SATA Harddisk or Solid State Drive
Thank you for your bug report. The eject command is issues by udisks so issue is more likely there Could you maybe report it also upstream on https://github.com/storaged-project/udisks/ ? ** Changed in: gnome-disk-utility (Ubuntu) Importance: Undecided => Low -- 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/1858860 Title: Gnome Disk Utility Issues incorrect command when ejecting a SATA Harddisk or Solid State Drive Status in gnome-disk-utility package in Ubuntu: New Bug description: Use case: As a user of hot swap-able SATA disks using a Harddrive Riser over eSATA. I need a safe, easy and convenient way to remove the hot swap-able SATA disk without rebooting and without having to go to the command line. When attempting to eject an harddisk or a solid state disk using the eject button in "Gnome Disk Utility" it issues the 'eject' command which results in an IOCTL error. The correct commands the eject button in the GUI should issue to eject a SATA HDD or SSD are: # where X is the drive letter of the drive being worked with # -Y Put drive to sleep sudo hdparm -Y /dev/sdX # remove the device from the kernel sudo sh -c 'echo 1 > /sys/block/sdX/device/delete' Please see the screen shots for the error. This should be an easy fix (20 minutes) for someone who is good a programmer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-disk-utility 3.28.3-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 8 21:07:32 2020 InstallationDate: Installed on 2018-11-11 (423 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1858860/+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 1858848] Re: Unable to add printer on Focal
Thank you for your bug report, could you add your 'journalctl -b 0 ' log to the bug after trying to add a printer? The problem could be due to cups-browsed being broken at the moment on focal... Till any idea there? ** Changed in: hplip (Ubuntu) Status: New => Incomplete ** Changed in: hplip (Ubuntu) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) -- 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/1858848 Title: Unable to add printer on Focal Status in hplip package in Ubuntu: Incomplete Bug description: I bought a new laptop and put Ubuntu Focal 20.04 on it. I installed hplip-gui so I can use the wizard to add my HP Color LaserJet Pro MFP M281fdw. The wizard sees the printer but when I click "Add Printer" nothing happens. There are no logs or error messages, it just sits there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1858848/+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 1856501] Re: xgettext cannot deal with jsx self-closing tags
thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1856501 Title: xgettext cannot deal with jsx self-closing tags Status in gettext package in Ubuntu: In Progress Bug description: Bug in xgettext: https://savannah.gnu.org/bugs/?56848 Fixed through https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=commitdiff;h=8f8b910322f5905045a8731df7aca5e601c9b082 Can you apply this patch? It really needed. ProblemType: Bug Architecture: x86_64 Date: Mon Dec 16 09:30:05 +07 2019 DistroRelease: Ubuntu 18.04 Package: gettext 0.19.8.1-6ubuntu0.3 PackageArchitecture: amd64 SourcePackage: gettext Uname: Linux 5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/1856501/+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 1856501] Re: xgettext cannot deal with jsx self-closing tags
xgettext --from-code=utf-8 --language=JavaScript --keyword=translate Documentation.jsx ** Attachment added: "Documentation.jsx" https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/1856501/+attachment/5318792/+files/Documentation.jsx -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1856501 Title: xgettext cannot deal with jsx self-closing tags Status in gettext package in Ubuntu: In Progress Bug description: Bug in xgettext: https://savannah.gnu.org/bugs/?56848 Fixed through https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=commitdiff;h=8f8b910322f5905045a8731df7aca5e601c9b082 Can you apply this patch? It really needed. ProblemType: Bug Architecture: x86_64 Date: Mon Dec 16 09:30:05 +07 2019 DistroRelease: Ubuntu 18.04 Package: gettext 0.19.8.1-6ubuntu0.3 PackageArchitecture: amd64 SourcePackage: gettext Uname: Linux 5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/1856501/+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 1838838] Re: username is not saved in openconnect connection dialog
Could someone having the issue report it upstream on https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1838838 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Confirmed Status in network-manager-openconnect package in Ubuntu: Confirmed Bug description: Same issue as https://bugs.launchpad.net/ubuntu/+source/network- manager-openconnect/+bug/1609700 This was marked resolved. The report of its reappearance in Ubuntu 19.04 and 19.10 has not been acknowledged. This was working for me in 18.10, but a fresh install of 19.04 and 19.10 show that it is back. The password is saved when the option to save passwords is selected, but the username must be entered manually upon connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1838838/+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 1858977] Re: cups-browsed assert failure: double free or corruption (!prev)
** Information type changed from Private to Public ** Changed in: cups-filters (Ubuntu) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1858977 Title: cups-browsed assert failure: double free or corruption (!prev) Status in cups-filters package in Ubuntu: New Bug description: Not sure. After update and reboot, got this error. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: cups-browsed 1.26.1-1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AssertionMessage: double free or corruption (!prev) Date: Thu Jan 9 02:05:08 2020 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2019-12-31 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: TOSHIBA Satellite S55t-C Papersize: a4 ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=2e6d7c37-0c60-4753-ba34-61e7e806523a ro locale=pt_BR quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups-filters StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f61820e93a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f61820eb0c0 "double free or corruption (!prev)") at malloc.c:5332 _int_free (av=0x7f618211ab80 , p=0x55599ade5730, have_lock=) at malloc.c:4317 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 g_queue_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: cups-browsed assert failure: double free or corruption (!prev) UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/08/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.20 dmi.board.name: 06F4 dmi.board.vendor: FF50 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.20:bd10/08/2015:svnTOSHIBA:pnSatelliteS55t-C:pvrPSPUGU-00200D:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite S55t-C dmi.product.sku: PSPUGU dmi.product.version: PSPUGU-00200D dmi.sys.vendor: TOSHIBA separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1858977/+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 1856501] Re: xgettext cannot deal with jsx self-closing tags
Thanks for the detail, could you add a jsx example to the bug that could be used as testcase? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1856501 Title: xgettext cannot deal with jsx self-closing tags Status in gettext package in Ubuntu: In Progress Bug description: Bug in xgettext: https://savannah.gnu.org/bugs/?56848 Fixed through https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=commitdiff;h=8f8b910322f5905045a8731df7aca5e601c9b082 Can you apply this patch? It really needed. ProblemType: Bug Architecture: x86_64 Date: Mon Dec 16 09:30:05 +07 2019 DistroRelease: Ubuntu 18.04 Package: gettext 0.19.8.1-6ubuntu0.3 PackageArchitecture: amd64 SourcePackage: gettext Uname: Linux 5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/1856501/+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 1848476] Re: [ZenBook UX534FT_UX534FT, Realtek ALC294, Black Headphone Out, Left] No sound at all
*** This bug is a duplicate of bug 1850439 *** https://bugs.launchpad.net/bugs/1850439 ** This bug has been marked a duplicate of bug 1850439 No sound on ASUS UX534FT -- 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/1848476 Title: [ZenBook UX534FT_UX534FT, Realtek ALC294, Black Headphone Out, Left] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.3 LTS The sound works until I plug the headphones and then it never works again, even without them. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.3.6-050306-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniela2692 F pulseaudio /dev/snd/pcmC0D0c: daniela2692 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 17 11:03:37 2019 InstallationDate: Installed on 2019-09-18 (28 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) 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/controlC0: gdm1426 F pulseaudio daniela2692 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [ZenBook UX534FT_UX534FT, Realtek ALC294, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX534FT.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX534FT 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.:bvrUX534FT.204:bd06/10/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX534FT_UX534FT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX534FT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX534FT_UX534FT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1848476/+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
