[Desktop-packages] [Bug 1967719] Re: No QXL display showing
The QXL crash in comment #22, #53, #54 is also mentioned upstream in: https://gitlab.freedesktop.org/xorg/driver/xf86-video- qxl/-/issues/14#note_1231895 ** Bug watch added: gitlab.freedesktop.org/xorg/driver/xf86-video-qxl/-/issues #14 https://gitlab.freedesktop.org/xorg/driver/xf86-video-qxl/-/issues/14 -- 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/1967719 Title: No QXL display showing Status in xorg-server package in Ubuntu: Incomplete Status in xserver-xorg-video-qxl package in Ubuntu: Incomplete Bug description: My Lubuntu VM isn't showing any display output Virt-manager. Can't TTY as well. I tried to update Mesa driver using Oibaf's PPA, but didn't work. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-video-qxl 0.1.5+git20200331-2build1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown Date: Mon Apr 4 02:12:53 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] InstallationDate: Installed on 2022-01-23 (70 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220119) Lsusb: Bus 002 Device 003: ID 46f4:0001 QEMU QEMU USB HARDDRIVE Bus 002 Device 002: ID 46f4:0001 QEMU QEMU USB HARDDRIVE Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M |__ Port 4: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M |__ Port 5: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=a6cde581-8b64-4557-816a-f80ffc0a683e ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-qxl UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-6.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.0:cvnQEMU:ct1:cvrpc-q35-6.0:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-6.0 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-01-23 (70 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220119) Package: xserver-xorg-video-qxl PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Tags: jammy Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass DistUpgraded: Fresh install DistroCodename: jammy DistroRelease: Ubuntu 22.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] InstallationDate: Installed on 2022-02-06 (56 days ago) InstallationMedia: Ubuntu Unity 22.04 Lsusb: Bus 002 Device 003: ID 46f4:0001 QEMU QEMU USB HARDDRIVE Bus 002 Device 002: ID 46f4:0001 QEMU QEMU USB HARDDRIVE
[Desktop-packages] [Bug 1967901] Re: [qxl] Xorg fails to start with "Screen(s) found, but none have a usable configuration."
Maybe report the issue upstream at https://gitlab.freedesktop.org/xorg/driver/xf86-video-qxl/-/issues although it doesn't look very active... If the offending change is in the kernel then it might be useful to try some older and newer kernels (after installation): https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/1967901 Title: [qxl] Xorg fails to start with "Screen(s) found, but none have a usable configuration." Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-qxl package in Ubuntu: New Bug description: Ubuntu Desktop Jammy 20220405 It fails to boot to the live session in virt-manager and gnome-boxes. ubiquity-dm starts fine but the live session does. The graphical session keeps dying. If I switch from QXL to Virtio then it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967901] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1967901 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/1967901 Title: [qxl] Xorg fails to start with "Screen(s) found, but none have a usable configuration." Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-qxl package in Ubuntu: New Bug description: Ubuntu Desktop Jammy 20220405 It fails to boot to the live session in virt-manager and gnome-boxes. ubiquity-dm starts fine but the live session does. The graphical session keeps dying. If I switch from QXL to Virtio then it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245506] Re: package libwmf0.2-7-gtk 0.2.8.4-10ubuntu2 failed to install/upgrade: ErrorMessage: subprocess dpkg-split returned error exit status 2
[Expired for libwmf (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libwmf (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwmf in Ubuntu. https://bugs.launchpad.net/bugs/1245506 Title: package libwmf0.2-7-gtk 0.2.8.4-10ubuntu2 failed to install/upgrade: ErrorMessage: subprocess dpkg-split returned error exit status 2 Status in libwmf package in Ubuntu: Expired Bug description: after a reboot from an upgrade to 12.10 ProblemType: Package DistroRelease: Ubuntu 13.04 Package: libwmf0.2-7-gtk 0.2.8.4-10ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic i686 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: i386 Date: Mon Oct 28 02:00:03 2013 DuplicateSignature: package:libwmf0.2-7-gtk:0.2.8.4-10ubuntu2:ErrorMessage: subprocess dpkg-split returned error exit status 2 ErrorMessage: ErrorMessage: subprocess dpkg-split returned error exit status 2 InstallationDate: Installed on 2013-09-24 (33 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True SourcePackage: libwmf Title: package libwmf0.2-7-gtk 0.2.8.4-10ubuntu2 failed to install/upgrade: ErrorMessage: subprocess dpkg-split returned error exit status 2 UpgradeStatus: Upgraded to raring on 2013-10-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwmf/+bug/1245506/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967901] Re: [qxl] Xorg fails to start with "Screen(s) found, but none have a usable configuration."
Also your kernel log shows the 'qxl' DRM kernel driver seems to be working. And Xorg has clearly found the kernel qxl device. So if Xorg says "Screen(s) found, but none have a usable configuration" then it suggests there might have been some change in the kernel driver that the Xorg driver doesn't yet support. ** Also affects: linux (Ubuntu) Importance: Undecided Status: 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/1967901 Title: [qxl] Xorg fails to start with "Screen(s) found, but none have a usable configuration." Status in linux package in Ubuntu: New Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-qxl package in Ubuntu: New Bug description: Ubuntu Desktop Jammy 20220405 It fails to boot to the live session in virt-manager and gnome-boxes. ubiquity-dm starts fine but the live session does. The graphical session keeps dying. If I switch from QXL to Virtio then it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967967] Re: Firefox snap does not remember cookies or settings
The firefox snap is built and supported directly by Mozilla. Please see https://support.mozilla.org/products/firefox for support options. ** Changed in: firefox (Ubuntu) Status: New => Invalid -- 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/1967967 Title: Firefox snap does not remember cookies or settings Status in firefox package in Ubuntu: Invalid Bug description: Since installing the Kubuntu Jammy beta and running `apt upgrade` a few times, I have had the issue that the Firefox snap forgets my cookies and settings (perhaps my whole profile?) every time I close and re-open it. When I open Firefox, sometimes it works correctly, sometimes I am shown the new-user onboarding screen and then it remembers my extensions and Sync session but my cookies are still gone, and sometimes it doesn't remember my Sync session or anything at all. I tried to report this bug using ubuntu-bug but was unable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967967/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967782] Re: Please sync latest changes from 1.36.4-2
This bug was fixed in the package network-manager - 1.36.4-2ubuntu1 --- network-manager (1.36.4-2ubuntu1) jammy; urgency=medium * Cherry pick WPA3 fixes from Debian, thanks Michael Biebl! (lp: #1967782) -- Sebastien Bacher Tue, 05 Apr 2022 15:28:36 +0200 ** Changed in: network-manager (Ubuntu) Status: Fix Committed => Fix Released -- 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/1967782 Title: Please sync latest changes from 1.36.4-2 Status in network-manager package in Ubuntu: Fix Released Bug description: Please consider syncing the following changes from Debian https://tracker.debian.org/news/1315963/accepted-network-manager-1364-2-source-into-unstable/ For more background see https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1003907 Seeing that Ubuntu 22.04 will ship wpasupplicant 2.10 it would be good to have this patch. When you sync the changes from Debian, a few remarks on the remaining diff to the Debian package: - isc-dhcp-client Depends NetworkManager defaults to its internal dhcp client (based on sd-network) since a while. Ubuntu doesn't override that default. So either it should explicitly override that default and specify dhclient as preferred dhcp client or it should drop this dependency as Debian does (or at least demote it). - avahi-autoipd Suggests NetworkManager doesn't use avahi-autoipd anymore. See the relevant commit from 2016! https://salsa.debian.org/utopia-team/network-manager/-/commit/d701201bfd5b2d7a6bb1cc81660ae55fd4f4e36b - lto Enabling lto means significantly increased build times. Last time I checked the space savings were miniscule. That's why the Debian doesn't enable lto. - restarting NM on upgrades NM does *not* tear down Ethernet connections on restart. For WiFi connections the situation is different but keep in mind that wpasupplicant.postinst will restart its service anyway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1967782/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967963] Re: Firefox snap cannot be set as default browser
** Package changed: xorg (Ubuntu) => firefox (Ubuntu) -- 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/1967963 Title: Firefox snap cannot be set as default browser Status in firefox package in Ubuntu: New Bug description: I was unable to set Firefox as the default browser by going to Settings -> Applications -> Default Applications -> Web browser. It was set to Other... and web links opened in Kate. In addition, I was unable to report a bug against Firefox because "it is provided by a snap provided by Mozilla." ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Tue Apr 5 19:54:54 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2022-03-30 (6 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. Card Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56a6 IMC Networks Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20L50067US ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 1.41 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET66W (1.41 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L50067US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrN24ET66W(1.41):bd10/20/2021:br1.41:efr1.22:svnLENOVO:pn20L50067US:pvrThinkPadT480:rvnLENOVO:rn20L50067US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L5_BU_Think_FM_ThinkPadT480: dmi.product.family: ThinkPad T480 dmi.product.name: 20L50067US dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967935] Re: there is no bluetooth in 22.04
It looks like the problem is the kernel: [ 55.796659] usbcore: registered new interface driver btusb [ 55.799361] usb 1-4: Direct firmware load for ar3k/AthrBT_0x1102.dfu failed with error -2 [ 55.799368] Bluetooth: Patch file not found ar3k/AthrBT_0x1102.dfu [ 55.799373] Bluetooth: Loading patch file failed [ 55.799420] ath3k: probe of 1-4:1.0 failed with error -2 [ 55.822336] usbcore: registered new interface driver ath3k But rather than associate this bug with the PCI device "AR9462" we should probably focus on the USB device "13d3:3393 IMC Networks". Sounds related to bug 1965953. ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Summary changed: - there is no bluetooth in 22.04 + Bluetooth doesn't work on Google Beltino board (AR9462 PCI, IMC Networks USB) ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1967935 Title: Bluetooth doesn't work on Google Beltino board (AR9462 PCI, IMC Networks USB) Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Bug description: 21.10 there was bluetooth no problem 22.04 bluetooth is off and stays off ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 20:07:02 2022 InstallationDate: Installed on 2022-01-30 (65 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: bnep btusb bluetooth MachineType: GOOGLE Panther ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-03-31 (5 days ago) dmi.bios.date: 01/04/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.9 dmi.board.name: Panther dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.9:bd01/04/2019:br4.0:efr0.0:svnGOOGLE:pnPanther:pvr1.0:rvnGOOGLE:rnPanther:rvr1.0:cvnGOOGLE:ct3:cvr:sku: dmi.product.family: Google_Beltino dmi.product.name: Panther dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967935/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967971] Re: libreoffice help isn't opening - "Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en-US=UNIX
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1967971 ** Tags added: iso-testing -- 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/1967971 Title: libreoffice help isn't opening - "Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.3." Status in libreoffice package in Ubuntu: New Bug description: Lubuntu jammy live test on - samsung 700t1c-p10aat (i5-3317u, 4gb, 3rd gen.core.intel.graphics.4000) ISOs builds have been failing, so this is an older ISO with upgrades applied. Purpose was exploration of an libreoffice update to fix confinement issue (https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210) Libreoffice package lubuntu@lubuntu:~$ apt-cache policy libreoffice libreoffice: Installed: 1:7.3.2-0ubuntu1 Candidate: 1:7.3.2-0ubuntu1 Version table: *** 1:7.3.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status ** to re-create To re-create, open libreoffice & hit F1 or use menu to open Help->Libreoffice.Help ** Expected outcome Firefox opens & help page is shown in windows ** Actual outcome Firefox opens, but error instead --- File not found Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.3. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice 1:7.3.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: LXQt Date: Wed Apr 6 01:46:35 2022 LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220403) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1967971/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967976] [NEW] Impress Video plays once and second time no video but sound
Public bug reported: LibreOffice Impress version 7.3.2.2, when I do a presentation with slides and mp4 videos, it plays the first video correctly once and thereafter on any video, there is only sound and no image displayed! I am on Kubuntu 22.04 and this problem has existed since Version 7.2.5.2. I have two Laptops with LibreOffice and one has Version 7.2.5.2 locked in as this is my main Laptop for presentations and this version works perfectly with no problem. My other Laptop is my sacrificial Laptop which has version 7.3.2.2. In the attached video I used Kazam to record both monitors. The presentation screen is the right half. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: fails impress jammy video ** Attachment added: "This is a Video to Illustrate the Problem" https://bugs.launchpad.net/bugs/1967976/+attachment/5577443/+files/LibreOffice_Video_Fault.mp4 -- 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/1967976 Title: Impress Video plays once and second time no video but sound Status in libreoffice package in Ubuntu: New Bug description: LibreOffice Impress version 7.3.2.2, when I do a presentation with slides and mp4 videos, it plays the first video correctly once and thereafter on any video, there is only sound and no image displayed! I am on Kubuntu 22.04 and this problem has existed since Version 7.2.5.2. I have two Laptops with LibreOffice and one has Version 7.2.5.2 locked in as this is my main Laptop for presentations and this version works perfectly with no problem. My other Laptop is my sacrificial Laptop which has version 7.3.2.2. In the attached video I used Kazam to record both monitors. The presentation screen is the right half. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1967976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967885] Re: blanking locks screen although screen lock is disabled
Assuming the screen is really locked then this bug is the responsibility of gnome-shell. Although if gnome-shell crashed when the screen blanked then you might be returned to the login screen. Which is it? Can you provide a photo of the lock screen? ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1967885 Title: blanking locks screen although screen lock is disabled Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: I disabled screen lock from Settings > Privacy > Screen. Even so, I am forced to log in any time my screen has blanked. When I inspect dconf-editor (org.gnome.desktop.lockdown), I see that locking is indeed active. This looks like a discrepancy between the settings mechanism and dconf. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 16:06:06 2022 InstallationDate: Installed on 2022-03-27 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1967885/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967883] Re: [snap] Firefox Nightly Application Icon missing from "Show Applications" screen
Did you suspend/resume/sleep or VT switch at any point? If so then this could be bug 1876632. -- 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/1967883 Title: [snap] Firefox Nightly Application Icon missing from "Show Applications" screen Status in firefox package in Ubuntu: New Bug description: From a clean install of Ubuntu 22.04 beta, I have installed VLC and Firefox (nightly) from Ubuntu Software (as snaps). Neither of the two icons/graphics show up in the show applications window - either in the thumbnails of the groups I have created, or the expanded windows (see screenshots). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 14:49:04 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967883/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966786] Re: login screen shown twice with VirtualBox Guest Additions
BertN45: The only error that stands out to me in your log is that the vmwgfx kernel driver keeps logging: kernel: [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel. If that's the problem then it's a bug in the kernel (where the vmwgfx driver lives) and/or the hypervisor. Otherwise the log shows that the Wayland session starts successfully and tries to register itself with GDM. And 30 seconds later, GDM starts a Xorg session. ** Tags added: vmwgfx -- 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/1966786 Title: login screen shown twice with VirtualBox Guest Additions Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: The login screen is shown twice and I have to supply the password twice. The system works normally afterwards. When I select auto-login in the settings still one login screen is shown. gdm.service - GNOME Display Manager Loaded: loaded (/lib/systemd/system/gdm.service; static) Active: active (running) since Mon 2022-03-28 11:47:32 AST; 6min ago Process: 1885 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS) Main PID: 1915 (gdm3) Tasks: 3 (limit: 2291) Memory: 5.0M CPU: 125ms CGroup: /system.slice/gdm.service └─1915 /usr/sbin/gdm3 mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Starting GNOME Display Manager... mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Started GNOME Display Manager. mar 28 11:47:32 vm-ubuntu-2204 gdm-launch-environment][1921]: pam_unix(gdm-launch-environment:session): session opened for user gdm(uid=125) by (uid=0) mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: unable to locate daemon control file mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: stashed password to try later in open session mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: pam_unix(gdm-password:session): session opened for user bertadmin(uid=1000) by (uid=0) mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring mar 28 11:47:57 vm-ubuntu-2204 gdm3[1915]: Gdm: Child process -1937 was already dead. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 11:48:17 2022 InstallationDate: Installed on 2020-01-25 (793 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-23 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967971] Re: libreoffice help isn't opening - "Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en-US=UNIX
A check on logs... it's possible not all package upgrades had taken effect, there is a message saying a restart is required because of dbus-deamon upgrade (can't do that on a live system) & lack of disk space on system.. so may require verification when an ISO build completes. The error on this system however matches the following I got earlier today when tested on my installed/primary box --- File not found Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.3. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- that system is NOT live & has all upgrades applied.. It was clean booted this morning -- 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/1967971 Title: libreoffice help isn't opening - "Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.3." Status in libreoffice package in Ubuntu: New Bug description: Lubuntu jammy live test on - samsung 700t1c-p10aat (i5-3317u, 4gb, 3rd gen.core.intel.graphics.4000) ISOs builds have been failing, so this is an older ISO with upgrades applied. Purpose was exploration of an libreoffice update to fix confinement issue (https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210) Libreoffice package lubuntu@lubuntu:~$ apt-cache policy libreoffice libreoffice: Installed: 1:7.3.2-0ubuntu1 Candidate: 1:7.3.2-0ubuntu1 Version table: *** 1:7.3.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status ** to re-create To re-create, open libreoffice & hit F1 or use menu to open Help->Libreoffice.Help ** Expected outcome Firefox opens & help page is shown in windows ** Actual outcome Firefox opens, but error instead --- File not found Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.3. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice 1:7.3.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: LXQt Date: Wed Apr 6 01:46:35 2022 LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220403) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1967971/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946476] Re: New on-demand default causes RTD3 never to be enabled
** Changed in: oem-priority Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1946476 Title: New on-demand default causes RTD3 never to be enabled Status in OEM Priority Project: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Fix Released Status in nvidia-prime source package in Hirsute: Incomplete Status in nvidia-prime source package in Impish: Fix Released Bug description: As per LP: #1942307 we now set on-demand as the default. This however, causes "prime-select on-demand", called by ubuntu-drivers, not to even try to detect RTD3 and to enable it, since "on-demand" is already set. We cannot make informed choices about RTD3 in the postinstallation script of nvidia-prime, therefore we should simply drop the check that prime-select makes to abort if the new profile is determined to be the same as the current profile. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Handle BrokenPipeError (LP: #1965520). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967901] Re: [qxl] Xorg fails to start with "Screen(s) found, but none have a usable configuration."
"no screens found" is a strangely common problem with Xorg, even on bare metal: bug 1543192 -- 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/1967901 Title: [qxl] Xorg fails to start with "Screen(s) found, but none have a usable configuration." Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-qxl package in Ubuntu: New Bug description: Ubuntu Desktop Jammy 20220405 It fails to boot to the live session in virt-manager and gnome-boxes. ubiquity-dm starts fine but the live session does. The graphical session keeps dying. If I switch from QXL to Virtio then it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1967901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967971] Re: libreoffice help isn't opening - "Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en-US=UNIX
** Description changed: - Lubuntu jammy live test. + Lubuntu jammy live test on + - samsung 700t1c-p10aat (i5-3317u, 4gb, 3rd gen.core.intel.graphics.4000) ISOs builds have been failing, so this is an older ISO with upgrades applied. Purpose was exploration of an libreoffice update to fix confinement issue (https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210) Libreoffice package lubuntu@lubuntu:~$ apt-cache policy libreoffice libreoffice: Installed: 1:7.3.2-0ubuntu1 Candidate: 1:7.3.2-0ubuntu1 Version table: *** 1:7.3.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status ** to re-create To re-create, open libreoffice & hit F1 or use menu to open Help->Libreoffice.Help ** Expected outcome Firefox opens & help page is shown in windows ** Actual outcome Firefox opens, but error instead --- File not found Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.3. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice 1:7.3.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: LXQt Date: Wed Apr 6 01:46:35 2022 LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220403) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1967971 Title: libreoffice help isn't opening - "Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.3." Status in libreoffice package in Ubuntu: New Bug description: Lubuntu jammy live test on - samsung 700t1c-p10aat (i5-3317u, 4gb, 3rd gen.core.intel.graphics.4000) ISOs builds have been failing, so this is an older ISO with upgrades applied. Purpose was exploration of an libreoffice update to fix confinement issue (https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210) Libreoffice package lubuntu@lubuntu:~$ apt-cache policy libreoffice libreoffice: Installed: 1:7.3.2-0ubuntu1 Candidate: 1:7.3.2-0ubuntu1 Version table: *** 1:7.3.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status ** to re-create To re-create, open libreoffice & hit F1 or use menu to open Help->Libreoffice.Help ** Expected outcome Firefox opens & help page is shown in windows ** Actual outcome Firefox opens, but error instead --- File not found Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.3. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice 1:7.3.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: LXQt Date: Wed Apr 6 01:46:35 2022 LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220403) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1967971/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1947420] Re: Buggish interface @ workstation panels previews when using dual portrait
** Changed in: mate-panel (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwnck3 in Ubuntu. https://bugs.launchpad.net/bugs/1947420 Title: Buggish interface @ workstation panels previews when using dual portrait Status in MATE Desktop: New Status in libwnck3 package in Ubuntu: Fix Released Status in mate-panel package in Ubuntu: Invalid Bug description: ...Freshly upgraded to 21.10 using the same OS that I used to open most of my previous video glitches ever... Using 2x monitor in portrait mode, the preview panel/widget(?) located at the bottom right side shows 2 things wrong: 1. The "Workspace 1" preview is very elongated when compared to not only all of it's previous incarnations (from 14.04 to 21.10) but also has an inconsistent size when compared to it's neighbouring "Workspace 2". Expectation: both 1 and 2 should be sized identically. 2. When hovering the mouse cursor on "Workspace 2" only it's left portion will highlight. Expectation: both monitors of "2" should highlight See enclosed picture. To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1947420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967971] [NEW] libreoffice help isn't opening - "Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en-US=UNIX
Public bug reported: Lubuntu jammy live test. ISOs builds have been failing, so this is an older ISO with upgrades applied. Purpose was exploration of an libreoffice update to fix confinement issue (https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210) Libreoffice package lubuntu@lubuntu:~$ apt-cache policy libreoffice libreoffice: Installed: 1:7.3.2-0ubuntu1 Candidate: 1:7.3.2-0ubuntu1 Version table: *** 1:7.3.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status ** to re-create To re-create, open libreoffice & hit F1 or use menu to open Help->Libreoffice.Help ** Expected outcome Firefox opens & help page is shown in windows ** Actual outcome Firefox opens, but error instead --- File not found Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.3. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice 1:7.3.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: LXQt Date: Wed Apr 6 01:46:35 2022 LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220403) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Description changed: Lubuntu jammy live test. ISOs builds have been failing, so this is an older ISO with upgrades applied. Purpose was exploration of an libreoffice update to fix confinement issue + (https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210) Libreoffice package lubuntu@lubuntu:~$ apt-cache policy libreoffice libreoffice: - Installed: 1:7.3.2-0ubuntu1 - Candidate: 1:7.3.2-0ubuntu1 - Version table: - *** 1:7.3.2-0ubuntu1 500 - 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1:7.3.2-0ubuntu1 + Candidate: 1:7.3.2-0ubuntu1 + Version table: + *** 1:7.3.2-0ubuntu1 500 + 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages + 100 /var/lib/dpkg/status ** to re-create To re-create, open libreoffice & hit F1 or use menu to open Help->Libreoffice.Help ** Expected outcome Firefox opens & help page is shown in windows ** Actual outcome Firefox opens, but error instead --- File not found Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.3. - Check the file name for capitalization or other typing errors. - Check to see if the file was moved, renamed or deleted. + Check the file name for capitalization or other typing errors. + Check to see if the file was moved, renamed or deleted. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice 1:7.3.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: LXQt Date: Wed Apr 6 01:46:35 2022 LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220403) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1967971 Title: libreoffice help isn't opening - "Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.3." Status in libreoffice package in Ubuntu: New Bug description: Lubuntu jammy live test. ISOs builds have been failing, so this is an older ISO with upgrades applied. Purpose was exploration of an libreoffice update to fix confinement issue (https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210) Libreoffice package lubuntu@lubuntu:~$ apt-cache policy libreoffice libreoffice: Installed: 1:7.3.2-0ubuntu1 Candidate: 1:7.3.2-0ubuntu1 Version table: *** 1:7.3.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status ** to re-create To re-create, open libreoffice & hit F1 or use menu to open Help->Libreoffice.Help ** Expected outcome Firefox opens & help page is shown in windows ** Actual outcome Firefox opens, but error instead --- File not found Firefox can’t find the file at
[Desktop-packages] [Bug 1967901] Re: [qxl] Xorg fails to start with "Screen(s) found, but none have a usable configuration."
** Summary changed: - Jammy fails to boot to live session in virt-manager with QXL + [qxl] Xorg fails to start with "Screen(s) found, but none have a usable configuration." -- 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/1967901 Title: [qxl] Xorg fails to start with "Screen(s) found, but none have a usable configuration." Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-qxl package in Ubuntu: New Bug description: Ubuntu Desktop Jammy 20220405 It fails to boot to the live session in virt-manager and gnome-boxes. ubiquity-dm starts fine but the live session does. The graphical session keeps dying. If I switch from QXL to Virtio then it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1967901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967853] Re: gnome-shell crashed with SIGSEGV
*** This bug is a duplicate of bug 1964458 *** https://bugs.launchpad.net/bugs/1964458 QXL issues are being tracked in bug 1967901, bug 1967719 and bug 1953035. -- 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/1967853 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: New Bug description: Tested jammy-desktop-amd64.iso from 2022-04-05 on Ubuntu 21.10 with virt-manager. I created a virtual machine and selected "Ubuntu 21.04" as OS (which then uses pc-q35-6.0) and changed the video to virtio with 3D acceleration. I tried all video models. Here is the result: * Bochs: works and gnome-shell is stable * QXL: Failed after "Try Ubuntu". Screen goes black. * Ramfb: No screen change/update after GRUB. * VGA: gnome-shell crashes * Virtio with 3D acceleration: gnome-shell crashes * Virtio without 3D acceleration: gnome-shell crashes ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 10:42:56 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) ProcCmdline: gnome-shell --sm-disable --mode=ubiquity ProcEnviron: PATH=(custom, no user) LANG=C.UTF-8 XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7ff155766f44:mov(%rsi),%rax PC (0x7ff155766f44) ok source "(%rsi)" (0x1bd441c0) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7ff155766f44 in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7fffd34c3ae0 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967853/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967853] Re: gnome-shell crashed with SIGSEGV
*** This bug is a duplicate of bug 1964458 *** https://bugs.launchpad.net/bugs/1964458 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1964458, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1964458 [jammy] gnome-shell live session crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl -- 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/1967853 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: New Bug description: Tested jammy-desktop-amd64.iso from 2022-04-05 on Ubuntu 21.10 with virt-manager. I created a virtual machine and selected "Ubuntu 21.04" as OS (which then uses pc-q35-6.0) and changed the video to virtio with 3D acceleration. I tried all video models. Here is the result: * Bochs: works and gnome-shell is stable * QXL: Failed after "Try Ubuntu". Screen goes black. * Ramfb: No screen change/update after GRUB. * VGA: gnome-shell crashes * Virtio with 3D acceleration: gnome-shell crashes * Virtio without 3D acceleration: gnome-shell crashes ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 10:42:56 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) ProcCmdline: gnome-shell --sm-disable --mode=ubiquity ProcEnviron: PATH=(custom, no user) LANG=C.UTF-8 XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7ff155766f44:mov(%rsi),%rax PC (0x7ff155766f44) ok source "(%rsi)" (0x1bd441c0) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7ff155766f44 in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7fffd34c3ae0 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967853/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712223] Re: open-vm-tools does not work under wayland
The wayland package shouldn't be assigned here unless there's a bug in
the protocol itself.
** No longer affects: wayland (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1712223
Title:
open-vm-tools does not work under wayland
Status in open-vm-tools package in Ubuntu:
Incomplete
Bug description:
At first I thought this bug was caused with the recent changes in
open-vm-tools 10.1.10; however, after restoring my VM to the snapshot
that had 17.04 and re-performing the dist-upgrade with open-vm-tools
and open-vm-tools-desktop held at 10.1.5 I am experiencing the same
issue where VMWare Workstation no longer can interact with display
resolution detection of the host monitor(s). Multiple monitor support
is also lost in the update process.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.6-0ubuntu6
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 21 17:09:59 2017
DistUpgraded: 2017-08-07 09:05:02,559 DEBUG found components:
{'artful-updates': {'multiverse', 'restricted', 'universe', 'main'}, 'artful':
{'multiverse', 'restricted', 'universe', 'main'}, 'artful-security':
{'multiverse', 'restricted', 'universe', 'main'}}
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
virtualbox, 5.1.26, 4.10.0-30-generic, x86_64: installed
virtualbox, 5.1.26, 4.12.0-11-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2016-11-30 (264 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic
root=UUID=dd284488-2aa1-430d-a510-0527b909f561 ro find_preseed=/preseed.cfg
auto noprompt priority=critical locale=en_US quiet
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to artful on 2017-08-07 (14 days ago)
dmi.bios.date: 07/02/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
version.compiz: compiz 1:0.9.13.1+17.10.20170720-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.82-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0~rc4-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0~rc4-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Aug 21 16:27:55 2017
xserver.configfile: default
xserver.devices:
inputPower Button KEYBOARD, id 6
inputAT Translated Set 2 keyboard KEYBOARD, id 7
inputVirtualPS/2 VMware VMMouse MOUSE, id 8
inputVirtualPS/2 VMware VMMouse MOUSE, id 9
xserver.errors:
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: Output
Virtual2Virtual3Virtual4Virtual5Virtual6
Virtual7Virtual8
xserver.version: 2:1.19.3-1ubuntu1.1
xserver.video_driver: vmware
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1712223/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964274] Re: Xwayland crashes with wl_display@1: error 1: invalid arguments for wl_shm@6.create_pool
** Changed in: wayland (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-in-wayland-1.20.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1964274 Title: Xwayland crashes with wl_display@1: error 1: invalid arguments for wl_shm@6.create_pool Status in X.Org X server: Unknown Status in mutter package in Ubuntu: Fix Released Status in wayland package in Ubuntu: Fix Committed Status in xwayland package in Ubuntu: Fix Released Bug description: System : Ubuntu 21.10 Kernel 5.13.0-35 Session : Wayland Each time I try to rip a CD with "abcde" gnome-shell crashes What I understand from the logs : Before the CD is ripped, abcde downloads a picture (from internet) as a cover of the CD. When tracker-extract discovers this picture something bad happens. Then gnome-shell crashes. After the crash (and re-login into Ubuntu) I can resume the ripping process as the picture has been cached by abcde, and tracker-extract does not interact again with it. Obviously the problem is back for each new CD. The problem appeared quite recently, probably less than 1 month ago. Logs : 00:13:06 host dbus-daemon[3541]: [session uid=1000 pid=3541] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Extract' unit='tracker-extract-3.service' requested by ':1.8' (uid=1000 pid=3573 comm="/usr/libexec/tracker-mi> 00:13:06 host systemd[3523]: Starting Tracker metadata extractor... 00:13:06 host dbus-daemon[3541]: [session uid=1000 pid=3541] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract' 00:13:06 host systemd[3523]: Started Tracker metadata extractor. 00:13:14 host tracker-extract-3[11545]: Not a JPEG file: starts with 0x89 0x50 00:13:14 host tracker-extract[11545]: Task for 'file:///home/user/Downloads/abcde.a80c7f0c/cover.jpg' finished with error: Could not get any metadata for uri:'file:///home/user/Downloads/abcde.a80c7f0c/cover.jpg' and mime:'image/jpeg' 00:13:14 host gnome-shell[3640]: WL: file descriptor expected, object (6), message create_pool(nhi) 00:13:14 host gnome-shell[3640]: WL: error in client communication (pid 3640) 00:13:14 host gnome-shell[4456]: (EE) 00:13:14 host gnome-shell[4456]: Fatal server error: 00:13:14 host gnome-shell[4456]: (EE) wl_display@1: error 1: invalid arguments for wl_shm@6.create_pool 00:13:14 host gnome-shell[4456]: (EE) 00:13:14 host gnome-shell[3640]: Connection to xwayland lost To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1964274/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964458] Re: [jammy] gnome-shell live session crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl
The fix is still awaiting review/sponsorship in https://salsa.debian.org/gnome-team/gnome-shell/-/merge_requests/60 -- 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/1964458 Title: [jammy] gnome-shell live session crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl Status in gjs: Unknown Status in gnome-shell package in Ubuntu: In Progress Bug description: Core was generated by `gnome-shell --sm-disable --mode=ubiquity'. Program terminated with signal SIGSEGV, Segmentation fault. In mozjs91: #0 0x7f5a697c3f44 in js::gc::Cell::storeBuffer (this=, this=) at .././js/src/gc/Cell.h:357 #1 js::gc::PostWriteBarrierImpl (next=, prev=, cellp=) at .././js/src/gc/StoreBuffer.h:654 #2 js::gc::PostWriteBarrier (next=, prev=, vp=) at .././js/src/gc/StoreBuffer.h:666 #3 js::InternalBarrierMethods::postBarrier (next=, prev=, vp=0x7f5a5002b200) at .././js/src/gc/Barrier.h:333 #4 js::InternalBarrierMethods::postBarrier (vp=0x7f5a5002b200, prev=, next=) at .././js/src/gc/Barrier.h:332 #5 0x7f5a6b637722 in js::BarrierMethods::postWriteBarrier (next=, prev=, vp=, vp=, prev=, next=) at /usr/include/mozjs-91/js/RootingAPI.h:770 #6 JS::Heap::postWriteBarrier (next=, prev=, this=, this=, prev=, next=) at /usr/include/mozjs-91/js/RootingAPI.h:361 #7 JS::Heap::~Heap (this=, this=) at /usr/include/mozjs-91/js/RootingAPI.h:323 #8 mozilla::detail::VectorImpl, 0ul, js::SystemAllocPolicy, false>::destroy ( aEnd=0x7f5a5002b218, aBegin=) at /usr/include/mozjs-91/mozilla/Vector.h:65 #9 mozilla::Vector, 0ul, js::SystemAllocPolicy>::~Vector (this=, this=) at /usr/include/mozjs-91/mozilla/Vector.h:901 #10 JS::GCVector, 0ul, js::SystemAllocPolicy>::~GCVector (this=, this=) at /usr/include/mozjs-91/js/GCVector.h:43 #11 GjsContextPrivate::~GjsContextPrivate (this=, this=) at ../gjs/context.cpp:482 #12 0x7f5a6b638978 in gjs_context_finalize (object=0x557e2a3f7180) at ../gjs/context.cpp:495 #13 0x7f5a6c0d2dfd in g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #14 0x7f5a6c31d77d in _shell_global_destroy_gjs_context (self=) at ../src/shell-global.c:703 #15 0x557e2950bece in main (argc=, argv=) at ../src/main.c:659 In mozjs78: See bug 1947130 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1964458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967967] [NEW] Firefox snap does not remember cookies or settings
Public bug reported: Since installing the Kubuntu Jammy beta and running `apt upgrade` a few times, I have had the issue that the Firefox snap forgets my cookies and settings (perhaps my whole profile?) every time I close and re-open it. When I open Firefox, sometimes it works correctly, sometimes I am shown the new-user onboarding screen and then it remembers my extensions and Sync session but my cookies are still gone, and sometimes it doesn't remember my Sync session or anything at all. I tried to report this bug using ubuntu-bug but was unable. ** 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/1967967 Title: Firefox snap does not remember cookies or settings Status in firefox package in Ubuntu: New Bug description: Since installing the Kubuntu Jammy beta and running `apt upgrade` a few times, I have had the issue that the Firefox snap forgets my cookies and settings (perhaps my whole profile?) every time I close and re-open it. When I open Firefox, sometimes it works correctly, sometimes I am shown the new-user onboarding screen and then it remembers my extensions and Sync session but my cookies are still gone, and sometimes it doesn't remember my Sync session or anything at all. I tried to report this bug using ubuntu-bug but was unable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967967/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964747] Re: [Jammy][regression] u-d-c default to use 470 instead of 510
Hello jeremyszu, or anyone else affected, Accepted ubuntu-drivers-common into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-drivers- common/1:0.9.2.4~0.21.10.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-drivers-common (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags added: verification-needed-impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1964747 Title: [Jammy][regression] u-d-c default to use 470 instead of 510 Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in ubuntu-drivers-common source package in Impish: Fix Committed Bug description: [Impact] * In Ubuntu 22.04, ubuntu-drivers install will install nvidia-470 instead of 510. (the ubuntu-drivers install is the best and recommended way to install nvidia driver). * nvidia-470 is LTSB (although webpage shows PB) and nvidia-510 is PB, in this case, we need to chose the newer version since the support is fair in both version. * Also, 22.04 announces Wayland supports but nvidia-470 doesn't support in Wayland scope at least from gdm upstream. [Test Plan] * Call "ubuntu-drivers debug" and check that 510 is marked as "(auto-install)" ``` ... === matching driver packages === nvidia-driver-510: installed:available: 510.54-0ubuntu2 [distro] non-free modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00 path: /sys/devices/pci:00/:00:01.0/:01:00.0 vendor: NVIDIA Corporation model: GA107M [GeForce RTX 3050 Ti Mobile] ... nvidia-driver-470: installed:available: 470.103.01-0ubuntu2 (auto-install) [distro] non-free modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00 path: /sys/devices/pci:00/:00:01.0/:01:00.0 vendor: NVIDIA Corporation model: GA107M [GeForce RTX 3050 Ti Mobile] support level: LTSB ... ``` * As you can see, "(auto-install)" points to 470 because it owns LTSB tag. [Fix] * Adjust the priority in UbuntuDrivers/detect.py, if the PB and LTSB versions found, then it needs to pick the newer version one. [Where problems could occur] * It has less possible to introduce regression since the patch only changes _cmp_gfx_alternatives() which counts the priority of nvidia drivers be installed. * In Ubuntu, we have nvidia-390, 470 and 510 so far as I known and these cases are listed in test_system_driver_packages_chroot_support_branch_pb. --- + nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1) + + * New upstream release (LP: #1961075): + - Fixed a bug that could cause GPU exceptions when minimizing a + fullscreen Vulkan application on certain desktops, such as + Plasma. + * debian/templates/control.in: + - Set XB-Support to PB (production branch). + * debian/rules.defs: + - Add support for video ABI 25. --- Since * debian/templates/control.in: - Set XB-Support to PB (production branch). The u-d-c will choose LTS branch instead of PB branch. because `def _cmp_gfx_alternatives(x, y):` doesn't define PB. [Additional information] If installed 470 instead of 510, then it will cause https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1963701 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967901] Re: Jammy fails to boot to live session in virt-manager with QXL
The gnome-shell crash is bug 1964458 so I'll remove references to that here. Your log shows Xorg is failing to start on QXL with: avril 05 16:15:58 ubuntu /usr/libexec/gdm-x-session[4265]: (EE) Screen(s) found, but none have a usable configuration. avril 05 16:15:58 ubuntu /usr/libexec/gdm-x-session[4265]: (EE) avril 05 16:15:58 ubuntu /usr/libexec/gdm-x-session[4265]: Fatal server error: avril 05 16:15:58 ubuntu /usr/libexec/gdm-x-session[4265]: (EE) no screens found(EE) avril 05 16:15:58 ubuntu /usr/libexec/gdm-x-session[4265]: (EE) Although see also bug 1967719 and bug 1953035. ** Description changed: Ubuntu Desktop Jammy 20220405 It fails to boot to the live session in virt-manager and gnome-boxes. - ubiquity-dm starts fine but the live session does. The graphical session keeps dying. There are crashes of gnome-shell and xorg in /var/crash. - - From the journal - avril 05 16:15:55 ubuntu kernel: gnome-shell[1383]: segfault at 3f1d5d20 ip 7fa1ca256f44 sp 7fff16f7c2a0 error 4 in libmozjs-91.so.91.7.0[7fa1ca1d7000+8e6000] - avril 05 16:15:55 ubuntu kernel: Code: 00 00 00 0f 85 73 05 00 00 48 83 c4 38 5b 5d 41 5c 41 5d 41 5e 41 5f c3 66 0f 1f 44 00 00 48 85 f6 74 d2 48 81 e6 00 00 f0 ff <48> 8b 06 48 85 c0 74 c3 80 b8 61 01 00 00 00 74 ba 48 3b 98 d0 00 - avril 05 16:15:55 ubuntu systemd[1]: Started crash report submission - + ubiquity-dm starts fine but the live session does. The graphical session keeps dying. If I switch from QXL to Virtio then it works. ** Package changed: ubiquity (Ubuntu) => xserver-xorg-video-qxl (Ubuntu) ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags added: qxl -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/1967901 Title: Jammy fails to boot to live session in virt-manager with QXL Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-qxl package in Ubuntu: New Bug description: Ubuntu Desktop Jammy 20220405 It fails to boot to the live session in virt-manager and gnome-boxes. ubiquity-dm starts fine but the live session does. The graphical session keeps dying. If I switch from QXL to Virtio then it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1967901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967901] [NEW] Jammy fails to boot to live session in virt-manager with QXL
You have been subscribed to a public bug: Ubuntu Desktop Jammy 20220405 It fails to boot to the live session in virt-manager and gnome-boxes. ubiquity-dm starts fine but the live session does. The graphical session keeps dying. If I switch from QXL to Virtio then it works. ** Affects: xserver-xorg-video-qxl (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- Jammy fails to boot to live session in virt-manager with QXL https://bugs.launchpad.net/bugs/1967901 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-qxl in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967963] [NEW] Firefox snap cannot be set as default browser
Public bug reported: I was unable to set Firefox as the default browser by going to Settings -> Applications -> Default Applications -> Web browser. It was set to Other... and web links opened in Kate. In addition, I was unable to report a bug against Firefox because "it is provided by a snap provided by Mozilla." ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Tue Apr 5 19:54:54 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2022-03-30 (6 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. Card Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56a6 IMC Networks Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20L50067US ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 1.41 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET66W (1.41 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L50067US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrN24ET66W(1.41):bd10/20/2021:br1.41:efr1.22:svnLENOVO:pn20L50067US:pvrThinkPadT480:rvnLENOVO:rn20L50067US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L5_BU_Think_FM_ThinkPadT480: dmi.product.family: ThinkPad T480 dmi.product.name: 20L50067US dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy kubuntu 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/1967963 Title: Firefox snap cannot be set as default browser Status in xorg package in Ubuntu: New Bug description: I was unable to set Firefox as the default browser by going to Settings -> Applications -> Default Applications -> Web browser. It was set to Other... and web links opened in Kate. In addition, I was unable to report a bug against Firefox because "it is provided by a snap provided by Mozilla." ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Tue Apr 5 19:54:54 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2022-03-30 (6 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. Card Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56a6 IMC Networks Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[Desktop-packages] [Bug 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)
A quick test using package guiverc@d960-ubu2:/de2900$ apt-cache policy libreoffice libreoffice: Installed: (none) Candidate: 1:7.3.2-0ubuntu1 Version table: 1:7.3.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages and I'm getting a firefox tab opening with page being --- File not found Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.3. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- this is an installed system (rebooted this morning), I'll wait and re- test when we have a daily ISO available with this package to confirm if it occurs there, or with a fresh install. -- 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/1951210 Title: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html) Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Released Bug description: Ubuntu jammy live QA-test on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) Opened LibreOffice Writer as random apps in QA-test. Hit F1 to call help, and all I get is an error URL: file:///tmp/lu417531j7po.tmp/NewHelp0.html --- File not found Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- Firefox opens as a snap; but it isn't accessing the data from LibreOffice. Reported first at https://forum.snapcraft.io/t/firefox-snap-breaks- libreoffice-deb/27537 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465+canary3.3 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 17 04:46:33 2021 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
I have determined the root cause via git bisecting the master branch. The issue was introduced in: commit 58de82b3d463b69f4c0bef75667e47020924e28b Author: Jakub Adam Date: Tue Sep 3 13:00:30 2019 +0200 Subject: Support camera video formats with MJPEG output Link: https://gitlab.gnome.org/GNOME/cheese/-/commit/58de82b3d463b69f4c0bef75667e47020924e28b If I checkout current master branch and revert this commit, things work fine. I will report the issue to upstream, and we can go from there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: In Progress Status in cheese source package in Jammy: In Progress Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default
[Desktop-packages] [Bug 1967883] Re: Application Icons missing from "Show Applications" screen
I reassigned this to Firefox. I recommend filing a different issue for VLC. ** Package changed: gnome-shell (Ubuntu) => firefox (Ubuntu) ** Tags added: snap ** Summary changed: - Application Icons missing from "Show Applications" screen + [snap] Firefox Nightly Application Icon missing from "Show Applications" screen -- 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/1967883 Title: [snap] Firefox Nightly Application Icon missing from "Show Applications" screen Status in firefox package in Ubuntu: New Bug description: From a clean install of Ubuntu 22.04 beta, I have installed VLC and Firefox (nightly) from Ubuntu Software (as snaps). Neither of the two icons/graphics show up in the show applications window - either in the thumbnails of the groups I have created, or the expanded windows (see screenshots). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 14:49:04 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967883/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964747] Re: [Jammy][regression] u-d-c default to use 470 instead of 510
Hello jeremyszu, or anyone else affected, Accepted ubuntu-drivers-common into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-drivers- common/1:0.9.0~0.20.04.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1964747 Title: [Jammy][regression] u-d-c default to use 470 instead of 510 Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in ubuntu-drivers-common source package in Impish: In Progress Bug description: [Impact] * In Ubuntu 22.04, ubuntu-drivers install will install nvidia-470 instead of 510. (the ubuntu-drivers install is the best and recommended way to install nvidia driver). * nvidia-470 is LTSB (although webpage shows PB) and nvidia-510 is PB, in this case, we need to chose the newer version since the support is fair in both version. * Also, 22.04 announces Wayland supports but nvidia-470 doesn't support in Wayland scope at least from gdm upstream. [Test Plan] * Call "ubuntu-drivers debug" and check that 510 is marked as "(auto-install)" ``` ... === matching driver packages === nvidia-driver-510: installed:available: 510.54-0ubuntu2 [distro] non-free modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00 path: /sys/devices/pci:00/:00:01.0/:01:00.0 vendor: NVIDIA Corporation model: GA107M [GeForce RTX 3050 Ti Mobile] ... nvidia-driver-470: installed:available: 470.103.01-0ubuntu2 (auto-install) [distro] non-free modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00 path: /sys/devices/pci:00/:00:01.0/:01:00.0 vendor: NVIDIA Corporation model: GA107M [GeForce RTX 3050 Ti Mobile] support level: LTSB ... ``` * As you can see, "(auto-install)" points to 470 because it owns LTSB tag. [Fix] * Adjust the priority in UbuntuDrivers/detect.py, if the PB and LTSB versions found, then it needs to pick the newer version one. [Where problems could occur] * It has less possible to introduce regression since the patch only changes _cmp_gfx_alternatives() which counts the priority of nvidia drivers be installed. * In Ubuntu, we have nvidia-390, 470 and 510 so far as I known and these cases are listed in test_system_driver_packages_chroot_support_branch_pb. --- + nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1) + + * New upstream release (LP: #1961075): + - Fixed a bug that could cause GPU exceptions when minimizing a + fullscreen Vulkan application on certain desktops, such as + Plasma. + * debian/templates/control.in: + - Set XB-Support to PB (production branch). + * debian/rules.defs: + - Add support for video ABI 25. --- Since * debian/templates/control.in: - Set XB-Support to PB (production branch). The u-d-c will choose LTS branch instead of PB branch. because `def _cmp_gfx_alternatives(x, y):` doesn't define PB. [Additional information] If installed 470 instead of 510, then it will cause https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1963701 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
Upstream bug: https://gitlab.gnome.org/GNOME/cheese/-/issues/126 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: In Progress Status in cheese source package in Jammy: In Progress Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1967843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
I downgraded cheese from 41.1-1build1 to 3.38.0-4 and it works fine again. Seems to be a cheese 41 problem. GST_V4L2_USE_LIBV4L2=1 gst-launch-1.0 v4l2src ! xvimagesink works fine, as well as using the webcam in Google Meet with Firefox. ** No longer affects: linux (Ubuntu) ** Also affects: cheese (Ubuntu Jammy) Importance: Low Status: Incomplete ** Changed in: cheese (Ubuntu Jammy) Status: Incomplete => In Progress ** Changed in: cheese (Ubuntu Jammy) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Bug watch added: gitlab.gnome.org/GNOME/cheese/-/issues #126 https://gitlab.gnome.org/GNOME/cheese/-/issues/126 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: In Progress Status in cheese source package in Jammy: In Progress Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Desktop-packages] [Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
Hi Jack, Thanks for reporting. I have a Logitech C270 camera, and I am also affected. Attached is what I see, I get green and purple bars, and overall terrible performance. I am on Jammy 5.15.0-25-generic, Wayland session, gnome 42, cheese 41.1-1build1. I will start investigating. Thanks, Matthew ** Attachment added: "Issue reproduced" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967843/+attachment/5577402/+files/Screenshot%20from%202022-04-06%2011-30-47.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version:
[Desktop-packages] [Bug 1965812] Re: slideshow does not work any more with dark mode
This bug was fixed in the package shotwell - 0.30.14-1ubuntu5 --- shotwell (0.30.14-1ubuntu5) jammy; urgency=medium * Cherry-pick patch to also set dark wallpaper (LP: #1965812) -- Jeremy Bicha Mon, 04 Apr 2022 16:53:50 -0400 ** Changed in: shotwell (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1965812 Title: slideshow does not work any more with dark mode Status in shotwell package in Ubuntu: Fix Released Bug description: Hi, I had ubuntu 22.04, which was upgraded from 21.10 following the link: https://linuxconfig.org/how-to-upgrade-ubuntu-to-22-04-lts-jammy- jellyfish. It has worked well for me until I run "apt update and apt upgrade" around Mar 18. I have wallpaper slideshow setup using shotwell before the upgrade. I noticed my desktop background went to black after the upgrade. I then logged out and logged in. The background was changed to an Ubuntu default. I tried to set desktop slideshow again using shotwell but it never worked any more. From the GUI, I did not see anything abnormal. But the desktop background simply did not change at all. I guess something was broken by one of the upgraded packages. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: shotwell 0.30.14-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 21 11:29:40 2022 InstallationDate: Installed on 2021-08-27 (205 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: shotwell UpgradeStatus: Upgraded to jammy on 2022-02-08 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1965812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967854] Re: Gaming input devices are not supported
This bug was fixed in the package ayatana-indicator-power - 22.2.0-1ubuntu0 --- ayatana-indicator-power (22.2.0-1ubuntu0) jammy; urgency=medium * debian/patches: + Add 1000_add-gaming-input-devices.patch. (LP: #1967854) -- Martin Wimpress Tue, 05 Apr 2022 12:44:04 +0100 ** Changed in: ayatana-indicator-power (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1967854 Title: Gaming input devices are not supported Status in ayatana-indicator-power package in Ubuntu: Fix Released Status in mate-power-manager package in Ubuntu: Fix Released Status in ubuntu-mate-artwork package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: Fix Committed Bug description: If a battery-powered gaming input device (controller, joystick, etc) is connected MATE Power Manager detects the device as "Unknown" and Power Statistics shows a missing icon image. Ayatana Indicator Power is also missing support for gaming input devices and displays a broken icon in the panel and lists the gaming input devices as Unknown. The Yaru themes are also missing panel icons to represent gaming-input battery levels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-power/+bug/1967854/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1966786] Re: login screen shown twice with VirtualBox Guest Additions
The requested file On Tue, 2022-04-05 at 01:47 +, Daniel van Vugt wrote: > > My first login was with xorg and it failed > > If you could provide a fresh clean log of the issue I would be > interested to see. Please: > > 1. Reboot. > > 2. Reproduce the bug. > > 3. Reboot. > > 4. Run: > > journalctl -b-1 > prevboot.txt > > 5. Attach the resulting text file here. > ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/bugs/1966786/+attachment/5577397/+files/prevboot.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/1966786 Title: login screen shown twice with VirtualBox Guest Additions Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: The login screen is shown twice and I have to supply the password twice. The system works normally afterwards. When I select auto-login in the settings still one login screen is shown. gdm.service - GNOME Display Manager Loaded: loaded (/lib/systemd/system/gdm.service; static) Active: active (running) since Mon 2022-03-28 11:47:32 AST; 6min ago Process: 1885 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS) Main PID: 1915 (gdm3) Tasks: 3 (limit: 2291) Memory: 5.0M CPU: 125ms CGroup: /system.slice/gdm.service └─1915 /usr/sbin/gdm3 mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Starting GNOME Display Manager... mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Started GNOME Display Manager. mar 28 11:47:32 vm-ubuntu-2204 gdm-launch-environment][1921]: pam_unix(gdm-launch-environment:session): session opened for user gdm(uid=125) by (uid=0) mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: unable to locate daemon control file mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: stashed password to try later in open session mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: pam_unix(gdm-password:session): session opened for user bertadmin(uid=1000) by (uid=0) mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring mar 28 11:47:57 vm-ubuntu-2204 gdm3[1915]: Gdm: Child process -1937 was already dead. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 11:48:17 2022 InstallationDate: Installed on 2020-01-25 (793 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-23 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962593] Re: SMB Mount to backup directory prevents mounting parent directory
Hello Dan, thank you for reporting this bug. I am triaging this as "Medium" for Ubuntu because it has "a moderate impact on a core application" but "Low" for Déjà Dup (upstream) as it does not affect any interaction in the application itself. Some comments on the proposed solutions: Déjà Dup is unlikely to implement a new "Share root" because that goes against the policy of providing a tool for (new) standard users and keeping the interface as simple as possible. The second solution is much better in this regard as it hides the workaround from the user. Leaving Déjà Dup as "New" for now as I will have to check who does the mount in the end. ** Changed in: deja-dup Importance: Undecided => Low -- 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/1962593 Title: SMB Mount to backup directory prevents mounting parent directory Status in Déjà Dup: New Status in Duplicity: New Status in deja-dup package in Ubuntu: Triaged Bug description: May also apply to the "duplicity" package and is related to network "mount"s: To reproduce: * Set up a writeable SMB share: smb://1.2.3.4/backup * Create a subdir: smb://1.2.3.4/backup/UbuntuBackup * Using "deja-dup" -> "Storage location" set: Storage location: Network Server Network Location: smb://1.2.3.4/backup/UbuntuBackup Folder: MyMachineBackup * REBOOT THE MACHINE (or clear any cached mounts to "smb://1.2.3.4/backup") * Select "deja-dup" -> "Overview" -> "Back Up Now..." * Allow the backup to start, but not finish * Go to Nautilus (file browser) -> "+ Other Locations" - At the bottom set "Connect to server" to: smb://1.2.3.4/backup Result: * The parent SMB directory "smb://1.2.3.4/backup" is inaccessible because the "UbuntuBackup" subdir is currently mounted * Can happen at semi-random times if the backup is on a schedule * This is especially a problem when backing up remotely over a VPN which can take a long time * Prevents access to all parent folders of the backup folder * Nautilus will hang, unable to mount the "backup" parent directory * Also a problem if the "smb://1.2.3.4/backup" folder is bookmarked in nautilus * This problem is persistent throughout backup process and for a period of time afterwards until the mount to "UbuntuBackup" times out or the backup process exits Possible solutions: * Add a configuration option to deja-dup/duplicity to specify the "Share root" and mount that first before accessing the configured "Network Location" * Have deja-dup or duplicity attempt to mount the parent directory/directories first by starting at the root of the SMB share and walking down the directory tree until a successful mount is made. In the above example, start by attempting to mount "smb://1.2.3.4/backup" first and then "smb://1.2.3.4/backup/UbuntuBackup" (in the case of deeper folder structures, try each one successively) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: deja-dup 40.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 08:51:47 2022 ExecutablePath: /usr/bin/deja-dup InstallationDate: Installed on 2021-09-13 (168 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1962593/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962593] Re: SMB Mount to backup directory prevents mounting parent directory
** Changed in: deja-dup (Ubuntu) Status: New => Triaged ** Changed in: deja-dup (Ubuntu) Importance: Undecided => Medium -- 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/1962593 Title: SMB Mount to backup directory prevents mounting parent directory Status in Déjà Dup: New Status in Duplicity: New Status in deja-dup package in Ubuntu: Triaged Bug description: May also apply to the "duplicity" package and is related to network "mount"s: To reproduce: * Set up a writeable SMB share: smb://1.2.3.4/backup * Create a subdir: smb://1.2.3.4/backup/UbuntuBackup * Using "deja-dup" -> "Storage location" set: Storage location: Network Server Network Location: smb://1.2.3.4/backup/UbuntuBackup Folder: MyMachineBackup * REBOOT THE MACHINE (or clear any cached mounts to "smb://1.2.3.4/backup") * Select "deja-dup" -> "Overview" -> "Back Up Now..." * Allow the backup to start, but not finish * Go to Nautilus (file browser) -> "+ Other Locations" - At the bottom set "Connect to server" to: smb://1.2.3.4/backup Result: * The parent SMB directory "smb://1.2.3.4/backup" is inaccessible because the "UbuntuBackup" subdir is currently mounted * Can happen at semi-random times if the backup is on a schedule * This is especially a problem when backing up remotely over a VPN which can take a long time * Prevents access to all parent folders of the backup folder * Nautilus will hang, unable to mount the "backup" parent directory * Also a problem if the "smb://1.2.3.4/backup" folder is bookmarked in nautilus * This problem is persistent throughout backup process and for a period of time afterwards until the mount to "UbuntuBackup" times out or the backup process exits Possible solutions: * Add a configuration option to deja-dup/duplicity to specify the "Share root" and mount that first before accessing the configured "Network Location" * Have deja-dup or duplicity attempt to mount the parent directory/directories first by starting at the root of the SMB share and walking down the directory tree until a successful mount is made. In the above example, start by attempting to mount "smb://1.2.3.4/backup" first and then "smb://1.2.3.4/backup/UbuntuBackup" (in the case of deeper folder structures, try each one successively) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: deja-dup 40.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 08:51:47 2022 ExecutablePath: /usr/bin/deja-dup InstallationDate: Installed on 2021-09-13 (168 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1962593/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
** Attachment added: "screenshot of the rendering artifact in cheese under 22.04" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967843/+attachment/5577395/+files/Screenshot%20from%202022-04-05%2016-53-06.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1967843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
I also can confirm that the warnings... (cheese:2554): cheese-WARNING **: 16:50:13.024: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. and associated rendering artifacts in the cheese display occur for both the nouveau and nvidia 510 drivers. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string
[Desktop-packages] [Bug 1967843] lspci.txt
apport information ** Attachment added: "lspci.txt" https://bugs.launchpad.net/bugs/1967843/+attachment/5577393/+files/lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1967843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1967843] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1967843/+attachment/5577392/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1967843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1967843] lsusb.txt
apport information ** Attachment added: "lsusb.txt" https://bugs.launchpad.net/bugs/1967843/+attachment/5577394/+files/lsusb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1967843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
Unlike cheese, 'ST_V4L2_USE_LIBV4L2=1 gst-launch-1.0 v4l2src ! xvimagesink' displays the webcam image fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1967843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1967843] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1967843/+attachment/5577390/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1967843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1967843] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1967843/+attachment/5577391/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1967843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
apport information ** Tags added: apport-collected ** Description changed: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu80 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-03-31 (4 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) + MachineType: Gigabyte Technology Co., Ltd. X570 UD + NonfreeKernelModules: nvidia_modeset nvidia + Package: cheese 41.1-1build1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 + RelatedPackageVersions: + cheese41.1-1build1 + cheese-common 41.1-1build1 + Tags: wayland-session third-party-packages jammy gstreamer-error + Uname: Linux 5.15.0-25-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 01/18/2021 + dmi.bios.release: 5.17 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: F32 + dmi.board.asset.tag: Default string + dmi.board.name: X570 UD + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: x.x + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: + dmi.product.family: X570 MB + dmi.product.name: X570 UD + dmi.product.sku: Default string + dmi.product.version: Default string + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "CheeseDebug.txt.gz" https://bugs.launchpad.net/bugs/1967843/+attachment/5577389/+files/CheeseDebug.txt.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form...
[Desktop-packages] [Bug 1967951] Re: hotplug external monitor logs me out
I have been using Ubuntu 22.04 for several months, initially Ubuntu on wayland was working but at some point Ubuntu on wayland stopped working (It doesn't even show up as an option on the gdm3 login screen). I am mentioning this to preemptively say that: - Ubuntu on wayland is not working - Sway on wayland is working - I don't know why Ubuntu-wayland is not working. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1967951 Title: hotplug external monitor logs me out Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: Summary: When hotplugging an external monitor, I am sent immediately to the login screen. Actions: Boot my laptop either with or without the external plugged in and then log in to my user account. If the monitor is not plugged in, plug it in. Expected result: The monitor is detected and the previous monitor configurations are loaded. Actual result: When the monitor is detected, I am immediately sent to the login screen. On X, with either HDMI or usb c port: I need to log in again. The monitor is detected and functions as expected once I have logged in. On sway with HDMI: I can change to tty2 (where my sway session was started) and the monitor is detected and functions as expected. On sway with usb c: I cannot log in again. It is stuck in a log-in loop. Other info: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 xserver-xorg-video-nouveau: Installed: 1:1.0.17-2build1 Candidate: 1:1.0.17-2build1 Version table: *** 1:1.0.17-2build1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Sway version 1.5.1 I have uninstalled all the propriety drivers. From the 'About Ubuntu' page, it seems that my Nvidia GPU is not in use. Laptop ASUS TUF A15 FA506IH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1967951/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967951] [NEW] hotplug external monitor logs me out
Public bug reported: Summary: When hotplugging an external monitor, I am sent immediately to the login screen. Actions: Boot my laptop either with or without the external plugged in and then log in to my user account. If the monitor is not plugged in, plug it in. Expected result: The monitor is detected and the previous monitor configurations are loaded. Actual result: When the monitor is detected, I am immediately sent to the login screen. On X, with either HDMI or usb c port: I need to log in again. The monitor is detected and functions as expected once I have logged in. On sway with HDMI: I can change to tty2 (where my sway session was started) and the monitor is detected and functions as expected. On sway with usb c: I cannot log in again. It is stuck in a log-in loop. Other info: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 xserver-xorg-video-nouveau: Installed: 1:1.0.17-2build1 Candidate: 1:1.0.17-2build1 Version table: *** 1:1.0.17-2build1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Sway version 1.5.1 I have uninstalled all the propriety drivers. >From the 'About Ubuntu' page, it seems that my Nvidia GPU is not in use. Laptop ASUS TUF A15 FA506IH ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1967951 Title: hotplug external monitor logs me out Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: Summary: When hotplugging an external monitor, I am sent immediately to the login screen. Actions: Boot my laptop either with or without the external plugged in and then log in to my user account. If the monitor is not plugged in, plug it in. Expected result: The monitor is detected and the previous monitor configurations are loaded. Actual result: When the monitor is detected, I am immediately sent to the login screen. On X, with either HDMI or usb c port: I need to log in again. The monitor is detected and functions as expected once I have logged in. On sway with HDMI: I can change to tty2 (where my sway session was started) and the monitor is detected and functions as expected. On sway with usb c: I cannot log in again. It is stuck in a log-in loop. Other info: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 xserver-xorg-video-nouveau: Installed: 1:1.0.17-2build1 Candidate: 1:1.0.17-2build1 Version table: *** 1:1.0.17-2build1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Sway version 1.5.1 I have uninstalled all the propriety drivers. From the 'About Ubuntu' page, it seems that my Nvidia GPU is not in use. Laptop ASUS TUF A15 FA506IH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1967951/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961092] Re: Installing collectd pulls in the X.org stack
This bug was fixed in the package libnotify - 0.7.9-3ubuntu5 --- libnotify (0.7.9-3ubuntu5) jammy; urgency=medium * Drop libnotify4 Recommends on "gnome-shell | notification-daemon" to Suggests so that headless packages with notification capability don't pull in parts of the desktop stack (LP: #1961092). -- Robie Basak Tue, 05 Apr 2022 13:34:40 +0100 ** Changed in: libnotify (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1961092 Title: Installing collectd pulls in the X.org stack Status in libnotify package in Ubuntu: Fix Released Status in libnotify source package in Focal: New Bug description: On Ubuntu Server, "apt install collectd" pulls in huge parts of the X.org stack, which is generally undesirable. This was brought up in #ubuntu-server earlier. Workaround: use --no-install-recommends This seems to be due to collectd -> libnotify4 -> gnome-shell -> ... chain. This appears to have been made worse in an Ubuntu delta regarding gnome-shell. Debian's packaging still recommends notification-daemon which still pulls in quite a lot. It seems odd to me that a lib* package would recommend anything, since they tend to be leaves in the dependency tree apart from other lib* packages. Further it's difficult to avoid depending on a lib* package for optional functionality, so it ends up being inconvenient as demonstrated in this use case. Wouldn't it be better for the desktop environment to recommend something that can receive notifications in order for the dependency system to do the sensible thing by default, instead of using Recommends from the notification sending end? Then headless systems wouldn't end up pulling in a "head" via Recommends. So my suggestion is to drop the Recommends from libnotify4 altogether, including in Debian. From a policy perspective, Recommends is defined as "The Recommends field should list packages that would be found together with this one in all but unusual installations". I think the headless case is a common installation, not an unusual one, so that disqualifies libnotify4 anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1961092/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966132] Re: [USB-Audio - SteelSeries Arctis 5, playback] Crackling sound about every second when audio starts
Looks like this bug related to this one: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966066 Tried workaround from this thread on 5.13.0-39-generic and it worked for me. -- 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/1966132 Title: [USB-Audio - SteelSeries Arctis 5, playback] Crackling sound about every second when audio starts Status in alsa-driver package in Ubuntu: New Bug description: Sound is fine on any other device. The Steelseries headphones doesn't affected by this issue on Windows 11. Both Steelseries Game/Chat outputs are affected by this issue. Doesn't matter if I play the sound is on the browser or download. The crackling sound appears about every second. Ear where I hear it is always random. It can be quieter or louder randomly but when you increase volume, the crackling is also became louder. Description: Ubuntu 20.04.4 LTS Release: 20.04 Advanced Linux Sound Architecture Driver Version k5.13.0-37-generic. I expect clear sound but hear repeating crackles. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 00:00:47 2022 InstallationDate: Installed on 2022-03-05 (18 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S5 successful Symptom_Card: GM204 High Definition Audio Controller - HDA NVidia Symptom_PulseAudioLog: мар 23 19:27:36 nick-pc dbus-daemon[1048]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.38' (uid=125 pid=1358 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [USB-Audio - SteelSeries Arctis 5, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2020 dmi.bios.release: 10.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1003 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z490-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1003:bd11/30/2020:br10.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ490-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: Default string dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-03-23T18:40:09.773036 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1966132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1430068] Re: Unable to launch gnome-system-monitor
executing > sudo echo 512 > /proc/sys/fs/inotify/max_user_instances does not work because it won't open the file as root but as your current user. This is because "> /proc/sys/fs/inotify/max_user_instances" is not part of what sudo executes. The command is interpreted by your shell as follows: open the file "/proc/sys/fs/inotify/max_user_instances " for writing and execute the programm "sudo" with the following arguments ["echo", "512"] and replace the output(stdout) of the program with said file for starting it. Since your shell is not running as root, it cannot open "/proc/sys/fs/inotify/max_user_instances" for writing. You can either get a shell running as root (with "sudo -i" for example), or do "echo 512 | sudo tee /proc/sys/fs/inotify/max_user_instances". The 2nd way works by passing the output of echo to sudo with in turn will pass it on to tee which then will open the file, which it can do because sudo invoked tee as root. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1430068 Title: Unable to launch gnome-system-monitor Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: When you have too many open files, you can't launch gnome-system- monitor: $ gnome-system-monitor (gnome-system-monitor:23720): glibmm-CRITICAL **: unhandled exception (type Glib::Error) in signal handler: domain: g-io-error-quark code : 0 what : Unable to find default local directory monitor type (gnome-system-monitor:23720): Gtk-CRITICAL **: gtk_window_present_with_time: assertion 'GTK_IS_WINDOW (window)' failed ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gnome-system-monitor 3.8.2.1-2ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 10 09:32:12 2015 InstallationDate: Installed on 2014-06-26 (255 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to utopic on 2014-10-27 (133 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1430068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967935] [NEW] there is no bluetooth in 22.04
Public bug reported: 21.10 there was bluetooth no problem 22.04 bluetooth is off and stays off ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 20:07:02 2022 InstallationDate: Installed on 2022-01-30 (65 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: bnep btusb bluetooth MachineType: GOOGLE Panther ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-03-31 (5 days ago) dmi.bios.date: 01/04/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.9 dmi.board.name: Panther dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.9:bd01/04/2019:br4.0:efr0.0:svnGOOGLE:pnPanther:pvr1.0:rvnGOOGLE:rnPanther:rvr1.0:cvnGOOGLE:ct3:cvr:sku: dmi.product.family: Google_Beltino dmi.product.name: Panther dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1967935 Title: there is no bluetooth in 22.04 Status in bluez package in Ubuntu: New Bug description: 21.10 there was bluetooth no problem 22.04 bluetooth is off and stays off ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 20:07:02 2022 InstallationDate: Installed on 2022-01-30 (65 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: bnep btusb bluetooth MachineType: GOOGLE Panther ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-03-31 (5 days ago) dmi.bios.date: 01/04/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.9 dmi.board.name: Panther dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.9:bd01/04/2019:br4.0:efr0.0:svnGOOGLE:pnPanther:pvr1.0:rvnGOOGLE:rnPanther:rvr1.0:cvnGOOGLE:ct3:cvr:sku: dmi.product.family: Google_Beltino dmi.product.name: Panther dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1967935/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
The autopkgtest regressions blocking systemd 248.3-1ubuntu8.5 in impish- proposed have been resolved. The regressions were caused either by (1) network/infrastructure issues and succeeded on retry, or by (2) unrelated snapd regressions. The systemd 248.3-1ubuntu8.5 upload added an autopkgtest change for systemd to ignore failed snap mount units which are caused by unrelated snapd issues. -- 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/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: Fix Committed Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: Fix Committed Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily
[Desktop-packages] [Bug 1967854] Re: Gaming input devices are not supported
This bug was fixed in the package mate-power-manager - 1.26.0-1ubuntu0 --- mate-power-manager (1.26.0-1ubuntu0) jammy; urgency=medium * debian/patches: + Add 0001_add-gaming-input-devices.patch. (LP: #1967854) -- Martin Wimpress Tue, 05 Apr 2022 11:57:19 +0100 ** Changed in: mate-power-manager (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1967854 Title: Gaming input devices are not supported Status in ayatana-indicator-power package in Ubuntu: Fix Committed Status in mate-power-manager package in Ubuntu: Fix Released Status in ubuntu-mate-artwork package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: Fix Committed Bug description: If a battery-powered gaming input device (controller, joystick, etc) is connected MATE Power Manager detects the device as "Unknown" and Power Statistics shows a missing icon image. Ayatana Indicator Power is also missing support for gaming input devices and displays a broken icon in the panel and lists the gaming input devices as Unknown. The Yaru themes are also missing panel icons to represent gaming-input battery levels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-power/+bug/1967854/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967854] Re: Gaming input devices are not supported
This bug was fixed in the package ubuntu-mate-artwork - 22.04.14 --- ubuntu-mate-artwork (22.04.14) jammy; urgency=medium * Sync Yaru-MATE themes/icons with upstream Yaru. * Add symlinks for gaming-input devices battery levels. (LP: #1967854) -- Martin Wimpress Tue, 05 Apr 2022 12:56:27 +0100 ** Changed in: ubuntu-mate-artwork (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1967854 Title: Gaming input devices are not supported Status in ayatana-indicator-power package in Ubuntu: Fix Committed Status in mate-power-manager package in Ubuntu: Fix Committed Status in ubuntu-mate-artwork package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: Fix Committed Bug description: If a battery-powered gaming input device (controller, joystick, etc) is connected MATE Power Manager detects the device as "Unknown" and Power Statistics shows a missing icon image. Ayatana Indicator Power is also missing support for gaming input devices and displays a broken icon in the panel and lists the gaming input devices as Unknown. The Yaru themes are also missing panel icons to represent gaming-input battery levels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-power/+bug/1967854/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966979] Re: Firefox says one of it's files is in use after new installation
My setup: - OS on a 256GB SSD disk, ext4, defaults - /home on a 8TB Seagate Archive HDD, f2fs, defaults, mounted to /home. The disk has *no partition table*. It is entirely fsf2-formatted. (as a super-floppy). ** No longer affects: firefox (Ubuntu) -- 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/1966979 Title: Firefox says one of it's files is in use after new installation Status in systemd package in Ubuntu: New Bug description: Steps to reproduce: - Make a full backup of Firefox user data; - rm -rf /home//.mozilla; - apt purge firefox; - apt install firefox; On first run, Firefox Says "The bookmarks and history system will not be functional because one of Firefox's files is in use by another application. Some security software can cause this problem" Trying to enter sync is not possible because Firefox says coookies are disabled, despite it being enabled. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 98.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luzemario 1437 F pulseaudio /dev/snd/controlC1: luzemario 1437 F pulseaudio BuildID: 20220322144853 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: KDE Date: Tue Mar 29 12:48:28 2022 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:364 DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False InstallationDate: Installed on 2021-01-23 (429 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.1.1 dev enp4s0 proto static metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 192.168.1.0/24 dev enp4s0 proto kernel scope link src 192.168.1.20 metric 100 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 ProcEnviron: LANGUAGE=pt_BR:en_US PATH=(custom, user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=98.0.2/20220322144853 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2016 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0502 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M PLUS/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0502:bd11/18/2016:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MPLUS/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966979/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967816] Re: PDF file completely silently fails to print, computer claims it printed, printer shows no trace of it
Backported to upstream 1.x branch in https://github.com/OpenPrinting/cups-filters/commit/2134daad68 Will be included in cups-filters 1.28.15 in Ubuntu 22.04 (Jammy). -- 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/1967816 Title: PDF file completely silently fails to print, computer claims it printed, printer shows no trace of it Status in cups-filters package in Ubuntu: In Progress Bug description: I have an HP LaserJet M551dn printer which usually works just fine with CUPS. Tonight, however, I discovered that I was completely unable to print one particular PDF file (unfortunately I can't provide you with the file because it's a scan of a tax form with PII on it). CUPS claimed that it printed the file and there are no errors in the log. On the other side, the printer doesn't show any trace of the file haven't been sent to it. The print job isn't in the job log, and at no point while CUPS claims it's printing does the printer make any noise or any of its lights blink as they usually do when a job is being sent to it. I don't know how to debug this further. I'm attaching the section of /var/log/cups/error_log from the attempt to print the file. This is reproducible every time with this particular file, including immediately after updating to all current Jammy packages and rebooting. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 4 20:51:23 2022 InstallationDate: Installed on 2019-01-02 (1188 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lpstat: device for duplex: socket://m551dn.kamens.brookline.ma.us:9100 device for HP_LaserJet_500_color_M551_1637DA: implicitclass://HP_LaserJet_500_color_M551_1637DA/ device for simplex: socket://m551dn.kamens.brookline.ma.us:9100 MachineType: Acer Predator G6-710 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', '/etc/cups/ppd/duplex.ppd', '/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd'] failed with exit code 2: grep: /etc/cups/ppd/simplex.ppd: Permission denied grep: /etc/cups/ppd/duplex.ppd: Permission denied grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-02-20 (43 days ago) dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1967816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965439] Re: Driver manager KCM can no longer launch
This seems to be a bigger bug and applies to software-properties-qt and perhaps pkexec. As it turns out, one cannot launch "sofware-properties- qt" from within plasma-discover either. Even though it calls pkexec to launch it, it fails every time even if the user is a system admin. ** Changed in: ubuntustudio-default-settings (Ubuntu Jammy) Status: Fix Released => In Progress ** Summary changed: - Driver manager KCM can no longer launch + software-properties-qt can no longer launch ** Summary changed: - software-properties-qt can no longer launch + software-properties-qt can no longer launch when called by pkexec ** Also affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Also affects: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Changed in: policykit-1 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: software-properties (Ubuntu Jammy) Status: New => Confirmed ** Changed in: policykit-1 (Ubuntu Jammy) Importance: Undecided => Critical ** Changed in: software-properties (Ubuntu Jammy) Importance: Undecided => Critical ** Changed in: ubuntustudio-default-settings (Ubuntu Jammy) Importance: Critical => High ** Changed in: kubuntu-settings (Ubuntu Jammy) Importance: Undecided => High ** Description changed: + See description below. As the driver manager is done inside software- + properties-qt, it's basically the same bug, but now it's affected by + something we can't exactly get into the mechanism of: plasma-discover's + "Software Sources" link. + + + Earlier description: + The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver-manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: software-properties-qt can no longer launch when called by pkexec Status in kubuntu-settings package in Ubuntu: In Progress Status in policykit-1 package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: In Progress Status in kubuntu-settings source package in Jammy: In Progress Status in policykit-1 source package in Jammy: Confirmed Status in software-properties source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the
[Desktop-packages] [Bug 1967859] Re: Ubuntu 22.04 Desktop Guide add-on
** Package changed: ubuntu-docs (Ubuntu) => gnome-user-docs (Ubuntu) ** Changed in: gnome-user-docs (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1967859 Title: Ubuntu 22.04 Desktop Guide add-on Status in gnome-user-docs package in Ubuntu: New Bug description: On the Ubuntu Desktop Guide for the new Ubuntu 22.04 LTS Jammy Jellyfish Ubuntu Desktop Guide documentation that is being wrote. Include a Firewall category within the Network, Web, & email section. The firewall category should link to the UFW wiki page. https://help.ubuntu.com/community/UFW This way new users have information how to configure the firewall on Ubuntu. Mainly as a security aspect especially for new enthusiasts starting with Ubuntu that do not know their is a firewall. Looking at the current desktop guide for 20.04 LTS the information for a firewall is missing. Ubuntu Desktop Guide Ubuntu 20.04 https://help.ubuntu.com/lts/ubuntu-help/index.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1967859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967859] [NEW] Ubuntu 22.04 Desktop Guide add-on
You have been subscribed to a public bug: On the Ubuntu Desktop Guide for the new Ubuntu 22.04 LTS Jammy Jellyfish Ubuntu Desktop Guide documentation that is being wrote. Include a Firewall category within the Network, Web, & email section. The firewall category should link to the UFW wiki page. https://help.ubuntu.com/community/UFW This way new users have information how to configure the firewall on Ubuntu. Mainly as a security aspect especially for new enthusiasts starting with Ubuntu that do not know their is a firewall. Looking at the current desktop guide for 20.04 LTS the information for a firewall is missing. Ubuntu Desktop Guide Ubuntu 20.04 https://help.ubuntu.com/lts/ubuntu-help/index.html ** Affects: gnome-user-docs (Ubuntu) Importance: Wishlist Status: New ** Tags: bot-comment jammy -- Ubuntu 22.04 Desktop Guide add-on https://bugs.launchpad.net/bugs/1967859 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967816] Re: PDF file completely silently fails to print, computer claims it printed, printer shows no trace of it
Fixed upstream in https://github.com/OpenPrinting/cups-filters/commit/607f5e9066 ** Package changed: cups (Ubuntu) => cups-filters (Ubuntu) ** Changed in: cups-filters (Ubuntu) Importance: Undecided => Medium ** Changed in: cups-filters (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1967816 Title: PDF file completely silently fails to print, computer claims it printed, printer shows no trace of it Status in cups-filters package in Ubuntu: In Progress Bug description: I have an HP LaserJet M551dn printer which usually works just fine with CUPS. Tonight, however, I discovered that I was completely unable to print one particular PDF file (unfortunately I can't provide you with the file because it's a scan of a tax form with PII on it). CUPS claimed that it printed the file and there are no errors in the log. On the other side, the printer doesn't show any trace of the file haven't been sent to it. The print job isn't in the job log, and at no point while CUPS claims it's printing does the printer make any noise or any of its lights blink as they usually do when a job is being sent to it. I don't know how to debug this further. I'm attaching the section of /var/log/cups/error_log from the attempt to print the file. This is reproducible every time with this particular file, including immediately after updating to all current Jammy packages and rebooting. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 4 20:51:23 2022 InstallationDate: Installed on 2019-01-02 (1188 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lpstat: device for duplex: socket://m551dn.kamens.brookline.ma.us:9100 device for HP_LaserJet_500_color_M551_1637DA: implicitclass://HP_LaserJet_500_color_M551_1637DA/ device for simplex: socket://m551dn.kamens.brookline.ma.us:9100 MachineType: Acer Predator G6-710 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', '/etc/cups/ppd/duplex.ppd', '/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd'] failed with exit code 2: grep: /etc/cups/ppd/simplex.ppd: Permission denied grep: /etc/cups/ppd/duplex.ppd: Permission denied grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-02-20 (43 days ago) dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1967816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966979] Re: Firefox says one of it's files is in use after new installation
After extensive trial-and-error effort, I discovered this issue is not related with browsers, but can be related to systemd. Google Chrome also does not save bookmarks and history, behaving erratically because this. Trying to start watsapp web brings an error message saying that the was an error with browser database. I wiped Ubuntu install, trying Linux Mint and Debian, and the same issue happens after I activate my /home partition in /etc/fstab. I use an additional f2fs formatted disk as home, with file system defaults. When default /home is mounted again, the problem is gone. How do I do to suspect systemd? simple, I removed Debian and installed Devuan distro, which is Debian without systemd. The problem was solved. Maybe some user config at my /home disk can be causing this behavior, but it is time-consuming for me to check what is causing this to systemd, so I will give up using Ubuntu, unfortunately. Please close this bug if you want, but I think it is a systemd bug, and needs to be investigated. Since now, I don't trust systemd anymore. -- 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/1966979 Title: Firefox says one of it's files is in use after new installation Status in firefox package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Steps to reproduce: - Make a full backup of Firefox user data; - rm -rf /home//.mozilla; - apt purge firefox; - apt install firefox; On first run, Firefox Says "The bookmarks and history system will not be functional because one of Firefox's files is in use by another application. Some security software can cause this problem" Trying to enter sync is not possible because Firefox says coookies are disabled, despite it being enabled. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 98.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luzemario 1437 F pulseaudio /dev/snd/controlC1: luzemario 1437 F pulseaudio BuildID: 20220322144853 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: KDE Date: Tue Mar 29 12:48:28 2022 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:364 DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False InstallationDate: Installed on 2021-01-23 (429 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.1.1 dev enp4s0 proto static metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 192.168.1.0/24 dev enp4s0 proto kernel scope link src 192.168.1.20 metric 100 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 ProcEnviron: LANGUAGE=pt_BR:en_US PATH=(custom, user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=98.0.2/20220322144853 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2016 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0502 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M PLUS/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0502:bd11/18/2016:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MPLUS/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name:
[Desktop-packages] [Bug 1967782] Re: Please sync latest changes from 1.36.4-2
thanks a lot for the quick upload. Now that wpasupplicant 2.10 is more widely available, I've seen this issue popping up at several places. I'm not sure if it's only related to FRITZ!Boxes but those alone are extremely popular in Germany, so I would have hated if the next LTS potentially breaks WiFi for lots of users. -- 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/1967782 Title: Please sync latest changes from 1.36.4-2 Status in network-manager package in Ubuntu: Fix Committed Bug description: Please consider syncing the following changes from Debian https://tracker.debian.org/news/1315963/accepted-network-manager-1364-2-source-into-unstable/ For more background see https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1003907 Seeing that Ubuntu 22.04 will ship wpasupplicant 2.10 it would be good to have this patch. When you sync the changes from Debian, a few remarks on the remaining diff to the Debian package: - isc-dhcp-client Depends NetworkManager defaults to its internal dhcp client (based on sd-network) since a while. Ubuntu doesn't override that default. So either it should explicitly override that default and specify dhclient as preferred dhcp client or it should drop this dependency as Debian does (or at least demote it). - avahi-autoipd Suggests NetworkManager doesn't use avahi-autoipd anymore. See the relevant commit from 2016! https://salsa.debian.org/utopia-team/network-manager/-/commit/d701201bfd5b2d7a6bb1cc81660ae55fd4f4e36b - lto Enabling lto means significantly increased build times. Last time I checked the space savings were miniscule. That's why the Debian doesn't enable lto. - restarting NM on upgrades NM does *not* tear down Ethernet connections on restart. For WiFi connections the situation is different but keep in mind that wpasupplicant.postinst will restart its service anyway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1967782/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967782] Re: Please sync latest changes from 1.36.4-2
If it's enabled in the toolchain, is there still a need to explicitly enable it (like in this case via --enable-lto) in individual packages? -- 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/1967782 Title: Please sync latest changes from 1.36.4-2 Status in network-manager package in Ubuntu: Fix Committed Bug description: Please consider syncing the following changes from Debian https://tracker.debian.org/news/1315963/accepted-network-manager-1364-2-source-into-unstable/ For more background see https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1003907 Seeing that Ubuntu 22.04 will ship wpasupplicant 2.10 it would be good to have this patch. When you sync the changes from Debian, a few remarks on the remaining diff to the Debian package: - isc-dhcp-client Depends NetworkManager defaults to its internal dhcp client (based on sd-network) since a while. Ubuntu doesn't override that default. So either it should explicitly override that default and specify dhclient as preferred dhcp client or it should drop this dependency as Debian does (or at least demote it). - avahi-autoipd Suggests NetworkManager doesn't use avahi-autoipd anymore. See the relevant commit from 2016! https://salsa.debian.org/utopia-team/network-manager/-/commit/d701201bfd5b2d7a6bb1cc81660ae55fd4f4e36b - lto Enabling lto means significantly increased build times. Last time I checked the space savings were miniscule. That's why the Debian doesn't enable lto. - restarting NM on upgrades NM does *not* tear down Ethernet connections on restart. For WiFi connections the situation is different but keep in mind that wpasupplicant.postinst will restart its service anyway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1967782/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966979] Re: Firefox says one of it's files is in use after new installation
** Also affects: systemd (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/1966979 Title: Firefox says one of it's files is in use after new installation Status in firefox package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Steps to reproduce: - Make a full backup of Firefox user data; - rm -rf /home//.mozilla; - apt purge firefox; - apt install firefox; On first run, Firefox Says "The bookmarks and history system will not be functional because one of Firefox's files is in use by another application. Some security software can cause this problem" Trying to enter sync is not possible because Firefox says coookies are disabled, despite it being enabled. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 98.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luzemario 1437 F pulseaudio /dev/snd/controlC1: luzemario 1437 F pulseaudio BuildID: 20220322144853 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: KDE Date: Tue Mar 29 12:48:28 2022 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:364 DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False InstallationDate: Installed on 2021-01-23 (429 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.1.1 dev enp4s0 proto static metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 192.168.1.0/24 dev enp4s0 proto kernel scope link src 192.168.1.20 metric 100 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 ProcEnviron: LANGUAGE=pt_BR:en_US PATH=(custom, user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=98.0.2/20220322144853 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2016 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0502 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M PLUS/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0502:bd11/18/2016:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MPLUS/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966979/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967777] Re: xdg-desktop-portal-gnome uses libadwaita & doesn't respect Ubuntu default themes
** Also affects: libadwaita-1 (Ubuntu) Importance: Undecided Status: New ** Changed in: libadwaita-1 (Ubuntu Jammy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: libadwaita-1 (Ubuntu Jammy) Status: New => In Progress ** Changed in: libadwaita-1 (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gnome in Ubuntu. https://bugs.launchpad.net/bugs/196 Title: xdg-desktop-portal-gnome uses libadwaita & doesn't respect Ubuntu default themes Status in libadwaita-1 package in Ubuntu: In Progress Status in xdg-desktop-portal-gnome package in Ubuntu: Fix Released Status in libadwaita-1 source package in Jammy: In Progress Status in xdg-desktop-portal-gnome source package in Jammy: Fix Released Bug description: xdg-desktop-portal-gnome 42 uses libadwaita. It uses the libadwaita style with blue buttons & different grays. It doesn't respect the Ubuntu default themes coloring. This is the only "app" in the default Ubuntu 22.04 LTS install that uses libadwaita. (And there are only 2 or 3 apps in universe that do.) The easiest way to handle this is to revert the commits that switched xdg-desktop-portal-gnome to libadwaita. Note that you'll probably need to log out and log back in after installing the update to see the changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libadwaita-1/+bug/196/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964541]
*** Bug 1763090 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1964541 Title: Cannot rearrange Firefox (snap) browser tabs/bookmarks in gnome-shell 42 (Wayland session) Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2, attempting to re-arrange tabs in Firefox fails. Click and drag the tab and release, nothing changes. The next click to the tab is ignored. syslog has the following: Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. gnome-shell 42~beta-1ubuntu2 Firefox Snap 98.0-3 (1073) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1964541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967816] Re: PDF file completely silently fails to print, computer claims it printed, printer shows no trace of it
The file prints with pdftops-renderer=gs. I can fix this for me personally, but is there any way to adjust the default CUPS configuration for the type of printer that I have to make this setting the default for others with the same printer, so they don't also run into this issue? ** Changed in: cups (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1967816 Title: PDF file completely silently fails to print, computer claims it printed, printer shows no trace of it Status in cups package in Ubuntu: New Bug description: I have an HP LaserJet M551dn printer which usually works just fine with CUPS. Tonight, however, I discovered that I was completely unable to print one particular PDF file (unfortunately I can't provide you with the file because it's a scan of a tax form with PII on it). CUPS claimed that it printed the file and there are no errors in the log. On the other side, the printer doesn't show any trace of the file haven't been sent to it. The print job isn't in the job log, and at no point while CUPS claims it's printing does the printer make any noise or any of its lights blink as they usually do when a job is being sent to it. I don't know how to debug this further. I'm attaching the section of /var/log/cups/error_log from the attempt to print the file. This is reproducible every time with this particular file, including immediately after updating to all current Jammy packages and rebooting. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 4 20:51:23 2022 InstallationDate: Installed on 2019-01-02 (1188 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lpstat: device for duplex: socket://m551dn.kamens.brookline.ma.us:9100 device for HP_LaserJet_500_color_M551_1637DA: implicitclass://HP_LaserJet_500_color_M551_1637DA/ device for simplex: socket://m551dn.kamens.brookline.ma.us:9100 MachineType: Acer Predator G6-710 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', '/etc/cups/ppd/duplex.ppd', '/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd'] failed with exit code 2: grep: /etc/cups/ppd/simplex.ppd: Permission denied grep: /etc/cups/ppd/duplex.ppd: Permission denied grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-02-20 (43 days ago) dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1967816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)
This bug was fixed in the package libreoffice - 1:7.3.2-0ubuntu1 --- libreoffice (1:7.3.2-0ubuntu1) jammy; urgency=medium * New upstream release * Use XDG_DOWNLOAD_DIR as location for temporary file for offline help (LP: #1951210) -- Rico Tzschichholz Mon, 04 Apr 2022 12:28:12 +0200 ** Changed in: libreoffice (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1951210 Title: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html) Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Released Bug description: Ubuntu jammy live QA-test on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) Opened LibreOffice Writer as random apps in QA-test. Hit F1 to call help, and all I get is an error URL: file:///tmp/lu417531j7po.tmp/NewHelp0.html --- File not found Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- Firefox opens as a snap; but it isn't accessing the data from LibreOffice. Reported first at https://forum.snapcraft.io/t/firefox-snap-breaks- libreoffice-deb/27537 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465+canary3.3 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 17 04:46:33 2021 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
** Changed in: gnome-shell (Ubuntu) Milestone: ubuntu-22.04-beta => None -- 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/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Status in packagekit package in Ubuntu: Invalid Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964036] Re: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04
** Changed in: firefox (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- 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/1964036 Title: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04 Status in firefox package in Ubuntu: New Bug description: 1) lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 (Kubuntu Jammy live session in QEMU VM) 2) apt-cache policy ubuntu-release-upgrader-core ubuntu-release-upgrader-core: Installed: 1:22.04.6 3) expected (upgrade from Kubuntu 20.04.3 -> 22.04. Reboot.) * Firefox icon on panel to be intact. * Clicked icon launches browser. * Icon tooltip/mouse hover to describe application. 4) happened instead * Icon is missing/replaced with a generic icon * Icon click produces error notification "Plasma Workspace - preferred://browser" * Icon tooltip/mouse hover appears, though is blank. Additional info: * firefox is still installed, works as expected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-07 (2 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy dist-upgrade Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964036/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964541] Re: Cannot rearrange Firefox (snap) browser tabs/bookmarks in gnome-shell 42 (Wayland session)
I rebuilt and installed mutter and gnome-shell 41.5 in jammy, and drag and drop works there, so it really is a regression in the 42 branch. -- 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/1964541 Title: Cannot rearrange Firefox (snap) browser tabs/bookmarks in gnome-shell 42 (Wayland session) Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2, attempting to re-arrange tabs in Firefox fails. Click and drag the tab and release, nothing changes. The next click to the tab is ignored. syslog has the following: Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. gnome-shell 42~beta-1ubuntu2 Firefox Snap 98.0-3 (1073) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1964541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
** Tags removed: rls-jj-incoming ** Tags added: rls-jj-notfixing -- 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/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Status in packagekit package in Ubuntu: Invalid Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964545] Re: 42beta: moving mouse as screen is fading to screensaver prevents input to shell
I'm closing this issue since gnome-shell 42.0-1ubuntu1 has migrated out of proposed. ** Changed in: gnome-shell (Ubuntu Jammy) Status: Fix Committed => 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/1964545 Title: 42beta: moving mouse as screen is fading to screensaver prevents input to shell Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Bug description: [Impact] If you move the mouse as the system fades into black for the screensaver, the screensaver will be prevented as normal, but the user will not be able to interact with the shell. Mouse clicks are ignored, and most key presses are ignored too. Workaround is to press super to enter shell overview, then super again to close, and mouse clicks will begin working again. gnome-shell 42~beta-1ubuntu2 from -proposed. [Testcase] 1) Leave your system idle, until the screen starts fading to black 2) As the screen is fading to black, move the mouse to prevent screensaver. 3) Attempt to click any window or type something To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964545/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966386] Re: /usr/libexec/xdg-desktop-portal:11:map_pid_if_needed:map_pid_if_needed:handle_make_thread_realtime_with_pid:ffi_call_unix64:ffi_call_int
that's fixed in https://bugs.launchpad.net/ubuntu/+source/xdg-desktop- portal/1.14.2-1 ** Changed in: xdg-desktop-portal (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1966386 Title: /usr/libexec/xdg-desktop- portal:11:map_pid_if_needed:map_pid_if_needed:handle_make_thread_realtime_with_pid:ffi_call_unix64:ffi_call_int Status in xdg-desktop-portal: Fix Released Status in xdg-desktop-portal package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xdg-desktop-portal. This problem was most recently seen with package version 1.14.1-1, the problem page at https://errors.ubuntu.com/problem/34483c95acb7a7b00ab9e83731350bf5e4233db0 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/xdg-desktop-portal/+bug/1966386/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Changed in: evince (Ubuntu) Assignee: Georgia Garcia (georgiag) => James Henstridge (jamesh) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: This is related to bug #1792648. After fixing that one (see discussion at https://salsa.debian.org/gnome-team/evince/merge_requests/1), clicking a hyperlink in a PDF opens it correctly if the default browser is a well-known application (such as /usr/bin/firefox), but it fails to do so if the default browser is a snap (e.g. the chromium snap). This is not a recent regression, it's not working on bionic either. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evince 3.30.0-2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 24 12:28:06 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (813 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: evince UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago) modified.conffile..etc.apparmor.d.abstractions.evince: [modified] mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967885] [NEW] blanking locks screen although screen lock is disabled
Public bug reported: I disabled screen lock from Settings > Privacy > Screen. Even so, I am forced to log in any time my screen has blanked. When I inspect dconf-editor (org.gnome.desktop.lockdown), I see that locking is indeed active. This looks like a discrepancy between the settings mechanism and dconf. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 16:06:06 2022 InstallationDate: Installed on 2022-03-27 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1967885 Title: blanking locks screen although screen lock is disabled Status in gdm3 package in Ubuntu: New Bug description: I disabled screen lock from Settings > Privacy > Screen. Even so, I am forced to log in any time my screen has blanked. When I inspect dconf-editor (org.gnome.desktop.lockdown), I see that locking is indeed active. This looks like a discrepancy between the settings mechanism and dconf. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 16:06:06 2022 InstallationDate: Installed on 2022-03-27 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1967885/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Tags added: desktop-lts-wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: This is related to bug #1792648. After fixing that one (see discussion at https://salsa.debian.org/gnome-team/evince/merge_requests/1), clicking a hyperlink in a PDF opens it correctly if the default browser is a well-known application (such as /usr/bin/firefox), but it fails to do so if the default browser is a snap (e.g. the chromium snap). This is not a recent regression, it's not working on bionic either. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evince 3.30.0-2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 24 12:28:06 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (813 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: evince UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago) modified.conffile..etc.apparmor.d.abstractions.evince: [modified] mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)
** Changed in: libreoffice (Ubuntu Jammy) Status: Triaged => Fix Committed -- 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/1951210 Title: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html) Status in libreoffice package in Ubuntu: Fix Committed Status in libreoffice source package in Jammy: Fix Committed Bug description: Ubuntu jammy live QA-test on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) Opened LibreOffice Writer as random apps in QA-test. Hit F1 to call help, and all I get is an error URL: file:///tmp/lu417531j7po.tmp/NewHelp0.html --- File not found Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- Firefox opens as a snap; but it isn't accessing the data from LibreOffice. Reported first at https://forum.snapcraft.io/t/firefox-snap-breaks- libreoffice-deb/27537 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465+canary3.3 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 17 04:46:33 2021 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967782] Re: Please sync latest changes from 1.36.4-2
I've merged the changes and uploaded. Thanks also for review the package delta, we will check those more in details and remove some of the delta but probably at the start of next cycle at this point. About LTO it's part of our default toolchain now, https://wiki.ubuntu.com/ToolChain/LTO and I think our default position is that it should be enable unless there is a valid reason to not do it which doesn't seem to be the case there? Note that there is a proposal for Debian to do the same on https://wiki.debian.org/ToolChain/LTO but I don't know what's the status -- 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/1967782 Title: Please sync latest changes from 1.36.4-2 Status in network-manager package in Ubuntu: Fix Committed Bug description: Please consider syncing the following changes from Debian https://tracker.debian.org/news/1315963/accepted-network-manager-1364-2-source-into-unstable/ For more background see https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1003907 Seeing that Ubuntu 22.04 will ship wpasupplicant 2.10 it would be good to have this patch. When you sync the changes from Debian, a few remarks on the remaining diff to the Debian package: - isc-dhcp-client Depends NetworkManager defaults to its internal dhcp client (based on sd-network) since a while. Ubuntu doesn't override that default. So either it should explicitly override that default and specify dhclient as preferred dhcp client or it should drop this dependency as Debian does (or at least demote it). - avahi-autoipd Suggests NetworkManager doesn't use avahi-autoipd anymore. See the relevant commit from 2016! https://salsa.debian.org/utopia-team/network-manager/-/commit/d701201bfd5b2d7a6bb1cc81660ae55fd4f4e36b - lto Enabling lto means significantly increased build times. Last time I checked the space savings were miniscule. That's why the Debian doesn't enable lto. - restarting NM on upgrades NM does *not* tear down Ethernet connections on restart. For WiFi connections the situation is different but keep in mind that wpasupplicant.postinst will restart its service anyway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1967782/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967883] Re: Application Icons missing from "Show Applications" screen
** Attachment added: "Screenshot from 2022-04-05 14-48-11.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967883/+attachment/5577339/+files/Screenshot%20from%202022-04-05%2014-48-11.png -- 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/1967883 Title: Application Icons missing from "Show Applications" screen Status in gnome-shell package in Ubuntu: New Bug description: From a clean install of Ubuntu 22.04 beta, I have installed VLC and Firefox (nightly) from Ubuntu Software (as snaps). Neither of the two icons/graphics show up in the show applications window - either in the thumbnails of the groups I have created, or the expanded windows (see screenshots). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 14:49:04 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967883/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967883] Re: Application Icons missing from "Show Applications" screen
** Attachment added: "Screenshot from 2022-04-05 14-48-11.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967883/+attachment/5577338/+files/Screenshot%20from%202022-04-05%2014-48-11.png -- 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/1967883 Title: Application Icons missing from "Show Applications" screen Status in gnome-shell package in Ubuntu: New Bug description: From a clean install of Ubuntu 22.04 beta, I have installed VLC and Firefox (nightly) from Ubuntu Software (as snaps). Neither of the two icons/graphics show up in the show applications window - either in the thumbnails of the groups I have created, or the expanded windows (see screenshots). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 14:49:04 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967883/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967883] [NEW] Application Icons missing from "Show Applications" screen
Public bug reported: >From a clean install of Ubuntu 22.04 beta, I have installed VLC and Firefox >(nightly) from Ubuntu Software (as snaps). Neither of the two icons/graphics show up in the show applications window - either in the thumbnails of the groups I have created, or the expanded windows (see screenshots). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 14:49:04 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "Screenshot from 2022-04-05 14-47-30.png" https://bugs.launchpad.net/bugs/1967883/+attachment/5577331/+files/Screenshot%20from%202022-04-05%2014-47-30.png -- 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/1967883 Title: Application Icons missing from "Show Applications" screen Status in gnome-shell package in Ubuntu: New Bug description: From a clean install of Ubuntu 22.04 beta, I have installed VLC and Firefox (nightly) from Ubuntu Software (as snaps). Neither of the two icons/graphics show up in the show applications window - either in the thumbnails of the groups I have created, or the expanded windows (see screenshots). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 14:49:04 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967883/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966127] Re: ubuntu-desktop-minimal pulls gnome-session which is in universe
Thanks Jeremy! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1966127 Title: ubuntu-desktop-minimal pulls gnome-session which is in universe Status in gdm3 package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Invalid Bug description: ubuntu-desktop-minimal is in main but installing it pulls gnome- session from universe. Here is how to reproduce it: 1) Create a Jammy VM: $ lxc launch images:ubuntu/jammy jammy-vm --vm 2) Enter the Jammy VM: $ lxc shell jammy-vm 3) Install ubuntu-desktop-minimal root@jammy-vm:~# apt-get update ... root@jammy-vm:~# apt-get install -V ubuntu-desktop-minimal ... Get:726 http://archive.ubuntu.com/ubuntu jammy/main amd64 libxfont2 amd64 1:2.0.5-1 [94.7 kB] Get:727 http://archive.ubuntu.com/ubuntu jammy/main amd64 xwayland amd64 2:22.1.0-1 [932 kB] Get:728 http://archive.ubuntu.com/ubuntu jammy/universe amd64 gnome-session all 42.0-1ubuntu1 [15.2 kB] Get:729 http://archive.ubuntu.com/ubuntu jammy/main amd64 yaru-theme-gnome-shell all 22.04.2 [66.4 kB] Get:730 http://archive.ubuntu.com/ubuntu jammy/main amd64 ubuntu-session all 42.0-1ubuntu1 [5,418 B] ... 4) Check the policy of packages: root@jammy-vm:~# apt-cache policy ubuntu-desktop-minimal gnome-session ubuntu-desktop-minimal: Installed: 1.478 Candidate: 1.478 Version table: *** 1.478 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session: Installed: 42.0-1ubuntu1 Candidate: 42.0-1ubuntu1 Version table: *** 42.0-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status Both should be from main. Additional information: root@jammy-vm:~# lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967782] Re: Please sync latest changes from 1.36.4-2
Thanks for the report Michael! ** Changed in: network-manager (Ubuntu) Importance: Undecided => High ** Changed in: network-manager (Ubuntu) Status: New => In Progress ** Changed in: network-manager (Ubuntu) Status: In Progress => Fix Committed -- 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/1967782 Title: Please sync latest changes from 1.36.4-2 Status in network-manager package in Ubuntu: Fix Committed Bug description: Please consider syncing the following changes from Debian https://tracker.debian.org/news/1315963/accepted-network-manager-1364-2-source-into-unstable/ For more background see https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1003907 Seeing that Ubuntu 22.04 will ship wpasupplicant 2.10 it would be good to have this patch. When you sync the changes from Debian, a few remarks on the remaining diff to the Debian package: - isc-dhcp-client Depends NetworkManager defaults to its internal dhcp client (based on sd-network) since a while. Ubuntu doesn't override that default. So either it should explicitly override that default and specify dhclient as preferred dhcp client or it should drop this dependency as Debian does (or at least demote it). - avahi-autoipd Suggests NetworkManager doesn't use avahi-autoipd anymore. See the relevant commit from 2016! https://salsa.debian.org/utopia-team/network-manager/-/commit/d701201bfd5b2d7a6bb1cc81660ae55fd4f4e36b - lto Enabling lto means significantly increased build times. Last time I checked the space savings were miniscule. That's why the Debian doesn't enable lto. - restarting NM on upgrades NM does *not* tear down Ethernet connections on restart. For WiFi connections the situation is different but keep in mind that wpasupplicant.postinst will restart its service anyway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1967782/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964541] Re: Cannot rearrange Firefox (snap) browser tabs/bookmarks in gnome-shell 42 (Wayland session)
See also https://bugzilla.mozilla.org/show_bug.cgi?id=1710344 ** Bug watch added: Mozilla Bugzilla #1710344 https://bugzilla.mozilla.org/show_bug.cgi?id=1710344 -- 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/1964541 Title: Cannot rearrange Firefox (snap) browser tabs/bookmarks in gnome-shell 42 (Wayland session) Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2, attempting to re-arrange tabs in Firefox fails. Click and drag the tab and release, nothing changes. The next click to the tab is ignored. syslog has the following: Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. gnome-shell 42~beta-1ubuntu2 Firefox Snap 98.0-3 (1073) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1964541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961092] Re: Installing collectd pulls in the X.org stack
This was originally reported against 20.04. I haven't validated that, but that report seems likely to be correct to me. It's worth considering an SRU for 20.04 too, but I'm focused elsewhere now. If someone would like to drive an SRU, then please do! Things to consider for an SRU: Are we sure that this doesn't regress desktop in any way? For example, does the desktop seed rely on this Recommends to pull in parts of the notification stack? It might be worth waiting for Jammy to settle to help determine that. Are any server users relying on the Recommends in any way to pull in other dependencies? For example, if in automation a server deployment is directly installing collectd but then relying on the Recommend to pull in some other package, then that package wouldn't get installed after an SRU and therefore regress that deployment automation. This is probably OK, but worth pointing out. ** Also affects: libnotify (Ubuntu Focal) Importance: Undecided Status: New ** Tags added: bitesize -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1961092 Title: Installing collectd pulls in the X.org stack Status in libnotify package in Ubuntu: Fix Committed Status in libnotify source package in Focal: New Bug description: On Ubuntu Server, "apt install collectd" pulls in huge parts of the X.org stack, which is generally undesirable. This was brought up in #ubuntu-server earlier. Workaround: use --no-install-recommends This seems to be due to collectd -> libnotify4 -> gnome-shell -> ... chain. This appears to have been made worse in an Ubuntu delta regarding gnome-shell. Debian's packaging still recommends notification-daemon which still pulls in quite a lot. It seems odd to me that a lib* package would recommend anything, since they tend to be leaves in the dependency tree apart from other lib* packages. Further it's difficult to avoid depending on a lib* package for optional functionality, so it ends up being inconvenient as demonstrated in this use case. Wouldn't it be better for the desktop environment to recommend something that can receive notifications in order for the dependency system to do the sensible thing by default, instead of using Recommends from the notification sending end? Then headless systems wouldn't end up pulling in a "head" via Recommends. So my suggestion is to drop the Recommends from libnotify4 altogether, including in Debian. From a policy perspective, Recommends is defined as "The Recommends field should list packages that would be found together with this one in all but unusual installations". I think the headless case is a common installation, not an unusual one, so that disqualifies libnotify4 anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1961092/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967853] Re: gnome-shell crashed with SIGSEGV
** Description changed: Tested jammy-desktop-amd64.iso from 2022-04-05 on Ubuntu 21.10 with virt-manager. I created a virtual machine and selected "Ubuntu 21.04" as OS (which then uses pc-q35-6.0) and changed the video to virtio with 3D acceleration. - gnome-shell also crashes with 3D acceleration disabled. + I tried all video models. Here is the result: - After switching from virtio to Bochs, gnome-shell stopped crashing. + * Bochs: works and gnome-shell is stable + * QXL: Failed after "Try Ubuntu". Screen goes black. + * Ramfb: No screen change/update after GRUB. + * VGA: gnome-shell crashes + * Virtio with 3D acceleration: gnome-shell crashes + * Virtio without 3D acceleration: gnome-shell crashes ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 10:42:56 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) ProcCmdline: gnome-shell --sm-disable --mode=ubiquity ProcEnviron: PATH=(custom, no user) LANG=C.UTF-8 XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7ff155766f44:mov(%rsi),%rax PC (0x7ff155766f44) ok source "(%rsi)" (0x1bd441c0) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7ff155766f44 in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7fffd34c3ae0 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: -- 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/1967853 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: New Bug description: Tested jammy-desktop-amd64.iso from 2022-04-05 on Ubuntu 21.10 with virt-manager. I created a virtual machine and selected "Ubuntu 21.04" as OS (which then uses pc-q35-6.0) and changed the video to virtio with 3D acceleration. I tried all video models. Here is the result: * Bochs: works and gnome-shell is stable * QXL: Failed after "Try Ubuntu". Screen goes black. * Ramfb: No screen change/update after GRUB. * VGA: gnome-shell crashes * Virtio with 3D acceleration: gnome-shell crashes * Virtio without 3D acceleration: gnome-shell crashes ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 10:42:56 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) ProcCmdline: gnome-shell --sm-disable --mode=ubiquity ProcEnviron: PATH=(custom, no user) LANG=C.UTF-8 XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7ff155766f44:mov(%rsi),%rax PC (0x7ff155766f44) ok source "(%rsi)" (0x1bd441c0) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7ff155766f44 in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7fffd34c3ae0 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967853/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967853] Re: gnome-shell crashed with SIGSEGV
** Description changed: Tested jammy-desktop-amd64.iso from 2022-04-05 on Ubuntu 21.10 with virt-manager. I created a virtual machine and selected "Ubuntu 21.04" as OS (which then uses pc-q35-6.0) and changed the video to virtio with 3D acceleration. gnome-shell also crashes with 3D acceleration disabled. + + After switching from virtio to Bochs, gnome-shell stopped crashing. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 10:42:56 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) ProcCmdline: gnome-shell --sm-disable --mode=ubiquity ProcEnviron: PATH=(custom, no user) LANG=C.UTF-8 XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7ff155766f44:mov(%rsi),%rax PC (0x7ff155766f44) ok source "(%rsi)" (0x1bd441c0) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7ff155766f44 in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7fffd34c3ae0 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: -- 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/1967853 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: New Bug description: Tested jammy-desktop-amd64.iso from 2022-04-05 on Ubuntu 21.10 with virt-manager. I created a virtual machine and selected "Ubuntu 21.04" as OS (which then uses pc-q35-6.0) and changed the video to virtio with 3D acceleration. gnome-shell also crashes with 3D acceleration disabled. After switching from virtio to Bochs, gnome-shell stopped crashing. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 10:42:56 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) ProcCmdline: gnome-shell --sm-disable --mode=ubiquity ProcEnviron: PATH=(custom, no user) LANG=C.UTF-8 XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7ff155766f44:mov(%rsi),%rax PC (0x7ff155766f44) ok source "(%rsi)" (0x1bd441c0) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7ff155766f44 in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7fffd34c3ae0 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967853/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967853] Re: gnome-shell crashed with SIGSEGV
** Description changed: Tested jammy-desktop-amd64.iso from 2022-04-05 on Ubuntu 21.10 with virt-manager. I created a virtual machine and selected "Ubuntu 21.04" as OS (which then uses pc-q35-6.0) and changed the video to virtio with 3D acceleration. + + gnome-shell also crashes with 3D acceleration disabled. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 10:42:56 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) ProcCmdline: gnome-shell --sm-disable --mode=ubiquity ProcEnviron: - PATH=(custom, no user) - LANG=C.UTF-8 - XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANG=C.UTF-8 + XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SegvAnalysis: - Segfault happened at: 0x7ff155766f44:mov(%rsi),%rax - PC (0x7ff155766f44) ok - source "(%rsi)" (0x1bd441c0) not located in a known VMA region (needed readable region)! - destination "%rax" ok + Segfault happened at: 0x7ff155766f44:mov(%rsi),%rax + PC (0x7ff155766f44) ok + source "(%rsi)" (0x1bd441c0) not located in a known VMA region (needed readable region)! + destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell Stacktrace: - #0 0x7ff155766f44 in ?? () - No symbol table info available. - Backtrace stopped: Cannot access memory at address 0x7fffd34c3ae0 + #0 0x7ff155766f44 in ?? () + No symbol table info available. + Backtrace stopped: Cannot access memory at address 0x7fffd34c3ae0 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: -- 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/1967853 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: New Bug description: Tested jammy-desktop-amd64.iso from 2022-04-05 on Ubuntu 21.10 with virt-manager. I created a virtual machine and selected "Ubuntu 21.04" as OS (which then uses pc-q35-6.0) and changed the video to virtio with 3D acceleration. gnome-shell also crashes with 3D acceleration disabled. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 10:42:56 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) ProcCmdline: gnome-shell --sm-disable --mode=ubiquity ProcEnviron: PATH=(custom, no user) LANG=C.UTF-8 XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7ff155766f44:mov(%rsi),%rax PC (0x7ff155766f44) ok source "(%rsi)" (0x1bd441c0) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7ff155766f44 in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7fffd34c3ae0 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967853/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863981] Re: espeak-ng cannot load mbrola language files
This can be closed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to espeak-ng in Ubuntu. https://bugs.launchpad.net/bugs/1863981 Title: espeak-ng cannot load mbrola language files Status in espeak-ng package in Ubuntu: New Bug description: I tried using all of the mbrola files named by espeak-ng --voices=de : Pty Language Age/Gender VoiceName File Other Languages 5 de --/M German gmw/de 6 de --/F german-mbrola-1mb/mb-de1 6 de --/M german-mbrola-2mb/mb-de2 6 de --/F german-mbrola-3mb/mb-de3 6 de --/M german-mbrola-4mb/mb-de4 6 de --/M german-mbrola-6mb/mb-de6 7 de --/F german-mbrola-5mb/mb-de5 7 de --/F german-mbrola-7mb/mb-de7 espeak-ng -vmb-de1 "Test" gives me: mbrola: FATAL ERROR : cannot find file /usr/share/mbrola/de1/de1 ! mbrowrap error: mbrola closed stderr and did not exit Error: Could not load the specified mbrola voice file. It does speak, though, seemingly using a default voice. /usr/share/mbrola does not exist. The files actually seem to reside in /usr/lib/x86_64-linux-gnu/espeak-ng-data/voices/mb I doubt that I can solve this via a simple symbolic link because seemingly the expected directory structure is different: all mbrola files are in the mb directory; there are no subdirectories like /de/de1 or similar. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: espeak-ng 1.49.2+dfsg-8 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 20 05:08:20 2020 InstallationDate: Installed on 2017-09-03 (899 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: espeak-ng UpgradeStatus: Upgraded to eoan on 2020-01-18 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/espeak-ng/+bug/1863981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967857] [NEW] Upgrade espeak-ng to version 1.51
Public bug reported: Please upgrade espeak-ng to version 1.51. The current package 1.50 is from December 2021 and 1.51 is from April 2022 with many fixes. See also https://github.com/espeak-ng/espeak-ng/releases ** Affects: espeak-ng (Ubuntu) Importance: Undecided Status: New ** Tags: focal impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to espeak-ng in Ubuntu. https://bugs.launchpad.net/bugs/1967857 Title: Upgrade espeak-ng to version 1.51 Status in espeak-ng package in Ubuntu: New Bug description: Please upgrade espeak-ng to version 1.51. The current package 1.50 is from December 2021 and 1.51 is from April 2022 with many fixes. See also https://github.com/espeak-ng/espeak-ng/releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/espeak-ng/+bug/1967857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967854] Re: Gaming input devices are not supported
** Also affects: ayatana-indicator-power (Ubuntu) Importance: Undecided Status: New ** Changed in: ayatana-indicator-power (Ubuntu) Importance: Undecided => Medium ** Changed in: ayatana-indicator-power (Ubuntu) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) ** Changed in: ayatana-indicator-power (Ubuntu) Status: New => Triaged ** Description changed: If a battery-powered gaming input device (controller, joystick, etc) is connected MATE Power Manager detect the device as "Unknown" and Power Statistics show a missing icon image. + + Ayatana Indicator Power is also missing support for gaming input devices + and displays a broken icon in the panel and lists the gaming input + devices as Unknown. ** Changed in: mate-power-manager (Ubuntu) Status: In Progress => Fix Committed ** Also affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Changed in: yaru-theme (Ubuntu) Status: New => Fix Committed ** Changed in: yaru-theme (Ubuntu) Importance: Undecided => Medium ** Changed in: yaru-theme (Ubuntu) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) ** Also affects: ubuntu-mate-artwork (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-mate-artwork (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-mate-artwork (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-mate-artwork (Ubuntu) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1967854 Title: Gaming input devices are not supported Status in ayatana-indicator-power package in Ubuntu: Triaged Status in mate-power-manager package in Ubuntu: Fix Committed Status in ubuntu-mate-artwork package in Ubuntu: In Progress Status in yaru-theme package in Ubuntu: Fix Committed Bug description: If a battery-powered gaming input device (controller, joystick, etc) is connected MATE Power Manager detect the device as "Unknown" and Power Statistics show a missing icon image. Ayatana Indicator Power is also missing support for gaming input devices and displays a broken icon in the panel and lists the gaming input devices as Unknown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-power/+bug/1967854/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895486] Re: [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll Lock" keyboards
** Changed in: xkeyboard-config (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1895486
Title:
[media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll
Lock" keyboards
Status in GNOME Shell:
Unknown
Status in xkeyboard-config package in Ubuntu:
Fix Released
Bug description:
I use Ubuntu 20.04.1.
After some use, I noticed a delay when using keyboard media controls
(for example: increase volume audio).
The first time I push these key Gnome hangs for a short time before
display the action on the screen.
(This problem is still happening in Ubuntu 18.04 too. Even worse some
times, the system crashes when using media keys.)
For some reason, my Gnome freezes when using Fn keys, or when I try to
use two keyboards. A friend of mine pointed to me that it occurs when
switching to a keyboard layout that has Scroll Lock enabled, so I
disabled it in the X11 keyboard layout file for my language, and it
solved the problem.
A workaround to solve the problem is:
1) Opened the keyboard layout file for my language, in my case:
sudo nano /usr/share/X11/xkb/symbols/br
2) Commented the line:
modifier_map Mod3 { Scroll_Lock };
3) Logged out and logged in again or run command setxkbmap.
These steps are specific for the Brazilian Portuguese ABNT2 Layout and
may not work for other layouts, but it can help you find a similar
solution.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: x11-xkb-utils 7.7+5
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-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.100 Fri May 29 08:45:51
UTC 2020
GCC version:
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 13 21:52:03 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
Subsystem: Dell UHD Graphics 630 (Desktop) [1028:0859]
NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if
00 [VGA controller])
Subsystem: Dell GP107 [GeForce GTX 1050 Ti] [1028:3512]
InstallationDate: Installed on 2020-08-15 (29 days ago)
InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa"
(20200815)
MachineType: Dell Inc. XPS 8930
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic
root=UUID=706721d5-f527-41fe-98ca-96706a36bb42 ro quiet splash
SourcePackage: x11-xkb-utils
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.15
dmi.board.name: 0T88YD
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.15:bd07/01/2020:svnDellInc.:pnXPS8930:pvr1.1.15:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
dmi.product.family: XPS
dmi.product.name: XPS 8930
dmi.product.sku: 0859
dmi.product.version: 1.1.15
dmi.sys.vendor: Dell Inc.
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: 2020-08-15T17:44:36
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1895486/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
