[Desktop-packages] [Bug 1987026] Re: Account Online crash in wayland session Ubuntu 22.04.1
** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1987026 Title: Account Online crash in wayland session Ubuntu 22.04.1 Status in gnome-online-accounts package in Ubuntu: New Bug description: I am trying to add my google account but dialog box closes immediately and then give me error Ubuntu 22.04.1 has experienced and internal error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1987026/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987033] [NEW] Ubuntu Software every time proposes ThinkPad P50 ME update
Public bug reported: Ubuntu Software propose every time to perform ThinkPad P50 ME firmware Update After performing the update at next boot ME firmware is correctly updated. Ubuntu software proposed again at next update. ** Affects: software-center (Ubuntu) Importance: Undecided Status: New ** Tags: jammy ** Attachment added: "Schermata del 2022-08-19 07-16-47.png" https://bugs.launchpad.net/bugs/1987033/+attachment/5609795/+files/Schermata%20del%202022-08-19%2007-16-47.png ** Package changed: gnome-online-accounts (Ubuntu) => software-center (Ubuntu) ** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1987033 Title: Ubuntu Software every time proposes ThinkPad P50 ME update Status in software-center package in Ubuntu: New Bug description: Ubuntu Software propose every time to perform ThinkPad P50 ME firmware Update After performing the update at next boot ME firmware is correctly updated. Ubuntu software proposed again at next update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1987033/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949299] Re: gtk4-broadwayd missing in libgtk-4-bin 4.4 (impish and jammy)
gtk4-broadwayd is available in the libgtk4-bin package for Ubuntu 22.10 which will be released in October. ** Changed in: gtk4 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/1949299 Title: gtk4-broadwayd missing in libgtk-4-bin 4.4 (impish and jammy) Status in gtk4 package in Ubuntu: Fix Released Status in gtk4 package in Debian: New Bug description: The binary (gtk4-broadwayd) and also the devel files for gtk4 broadway are missing in the 4.4 packages for impish and jammy. They are in the hirsute package (4.0) though. For example this would be needed for Cambalache: WARNING:cambalache.cmb_view gtk4-broadwayd not found, Gtk 4 workspace wont work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/1949299/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987026] Re: Account Online crash in wayland session Ubuntu 22.04.1
** Summary changed: - Account Online crash in wayland session + Account Online crash in wayland session Ubuntu 22.04.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1987026 Title: Account Online crash in wayland session Ubuntu 22.04.1 Status in gnome-online-accounts package in Ubuntu: New Bug description: I am trying to add my google account but dialog box closes immediately and then give me error Ubuntu 22.04.1 has experienced and internal error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1987026/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987026] [NEW] Account Online crash in wayland session
Public bug reported: I am trying to add my google account but dialog box closes immediately and then give me error Ubuntu 22.04.1 has experienced and internal error. ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1987026 Title: Account Online crash in wayland session Status in gnome-online-accounts package in Ubuntu: New Bug description: I am trying to add my google account but dialog box closes immediately and then give me error Ubuntu 22.04.1 has experienced and internal error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1987026/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1979064] Re: Context menu shows again on other screen
[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1979064 Title: Context menu shows again on other screen Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Expired Bug description: When I right-click an application from the Dock, the context- menu/dialog comes up with the different options, but when I click on one of them, for some reason, the context-menu/dialog appears one more time but in the left screen and when I click again in the context option in which I'm interested it works correctly. I have 2 screens, the secondary is on the left, and the dock is on the primary. Im gonna attach screenshots of the process. In the first image I bring the cursor near the Dock and it opens. In the second image I right-click on an application, Terminal in this case. After that I click on 'New Window'. In the third image the context-menu/dialog shows up again in the secondary screen. 1. Description: Ubuntu 22.04 LTS Release: 22.04 2. gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5 Candidate: 72~ubuntu5 Version table: *** 72~ubuntu5 500 500 http://es.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status 3. I expected to execute the action, instead of opening the context menu again but on the left screen. 4. The context menu opened again, but on the left screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1979064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986450] Re: Visual artifact 1px vertical white line right side of the wallpaper
Thanks, that's enough info. My immediate thought is that it might relate to mutter's background rendering code which aggressively tries to limit the number of wallpaper pixels it redraws each frame. Maybe there's an off-by-one mistake in that code. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1986450 Title: Visual artifact 1px vertical white line right side of the wallpaper Status in gnome-shell package in Ubuntu: New Bug description: After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that there is a 1px wide vertical white line on the desktop that appears whenever an application has focus. It is on the right side of the monitor, covering the background wallpaper but not the menu. Workaround: in Displays, change scale to something else than 100% and then change back to 100%. That white vertical line will stay at the former 100% window size location until the Settings window is closed. It disappears when the Settings is closed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-27 (1570 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: gnome-shell 42.2-0ubuntu0.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: wayland-session jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1986450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987004] Re: [Dell Inspiron 3180] Touchpad stops functioning after wakeup
*** This bug is a duplicate of bug 1899235 *** https://bugs.launchpad.net/bugs/1899235 ** Summary changed: - Touchpad stops functioning after wakeup + [Dell Inspiron 3180] Touchpad stops functioning after wakeup ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** This bug has been marked a duplicate of bug 1899235 [Dell Inspiron 3180] Touchpad freeze after overnight sleep -- 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/1987004 Title: [Dell Inspiron 3180] Touchpad stops functioning after wakeup Status in linux package in Ubuntu: New Bug description: Although it happens randomly. The touchpad stops working where the cursor freezes after the system wakes up from suspension mode. The mouse, though, does work. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: GNOME Date: Thu Aug 18 15:15:02 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Once a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Today GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=a0f3455c-f4c6-4dc2-a499-28f2f500c291 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:br5.3:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:sku087E: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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/linux/+bug/1987004/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1975935] Re: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
** Summary changed: - Key input repeated unintendedly + Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1975935 Title: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Status in gnome-shell package in Ubuntu: Confirmed Bug description: gnome-shell[3502]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! syslog above. sometimes keys repeat(and slight system freeze / hitch) whithout holding key. like; $ helllo (of cource I typed just h, e, l, l, o ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 27 20:29:17 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-18 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 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/1975935/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** Also affects: gnome-shell-extension-desktop-icons-ng Importance: Undecided Status: New ** Also affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: New ** No longer affects: gnome-shell-extension-desktop-icons-ng -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in OEM Priority Project: Confirmed Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Status in nautilus package in Ubuntu: Incomplete Bug description: Can't move file/directory by drag and drop by using a touch monitor OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987004] Re: Touchpad stops functioning after wakeup
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1987004 Title: Touchpad stops functioning after wakeup Status in xorg package in Ubuntu: New Bug description: Although it happens randomly. The touchpad stops working where the cursor freezes after the system wakes up from suspension mode. The mouse, though, does work. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: GNOME Date: Thu Aug 18 15:15:02 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Once a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Today GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=a0f3455c-f4c6-4dc2-a499-28f2f500c291 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:br5.3:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:sku087E: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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/xorg/+bug/1987004/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987004] [NEW] Touchpad stops functioning after wakeup
You have been subscribed to a public bug: Although it happens randomly. The touchpad stops working where the cursor freezes after the system wakes up from suspension mode. The mouse, though, does work. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: GNOME Date: Thu Aug 18 15:15:02 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Once a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Today GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=a0f3455c-f4c6-4dc2-a499-28f2f500c291 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:br5.3:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:sku087E: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 freeze jammy ubuntu wayland-session -- Touchpad stops functioning after wakeup https://bugs.launchpad.net/bugs/1987004 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain
This bug was fixed in the package netplan.io - 0.105-0ubuntu1 --- netplan.io (0.105-0ubuntu1) kinetic; urgency=medium * New upstream release: 0.105 - Add support for VXLAN tunnels (#288), LP: #1764716 - Add support for VRF devices (#285), LP: #1773522 - Add support for InfiniBand (IPoIB) (#283), LP: #1848471 - Allow key configuration for GRE tunnels (#274), LP: #1966476 - Allow setting the regulatory domain (#281), LP: #1951586 - Documentation improvements & restructuring (#287) - Add meson build system (#268) - Add abigail ABI compatibility checker (#269) - Update of Fedora RPM spec (#264) - CI improvements (#265, #282) - Netplan `set` uses the consolidated libnetplan YAML parser (#254) - Refactor ConfigManager to use the libnetplan YAML parser (#255) - New `netplan_netdef_get_filepath` API (#275) - Improve NetworkManager device management logic (#276), LP: #1951653 Bug fixes: - Fix `apply` netdev rename/create race condition (#260), LP: #1962095 - Fix `try` timeout (#271), LP: #1967084 - Fix infinite timeouts in ovs-vsctl (#266), Closes: #1000137 - Fix offload options using tristate setting (#270), LP: #1956264 - Fix rendering of NetworkManager passthrough WPA (#279), LP: #1972800 - Fix CLI crash on LibNetplanException (#286) - Fix NetworkManager internal DHCP client lease lookup (#284), LP: #1979674 * Update symbols file for 0.105 * d/patches/: Drop patches, applied upstream * d/p/autopkgtest-fixes.patch: Refresh * d/control: bump Standards-Version, no changes needed * d/control, d/tests/control: suggest/add iw for setting a regulatory domain * d/control: merge with Debian, dropping deprecated versioned depends * d/control: Update Vcs-* tags for Ubuntu * d/watch: sync with Debian * d/u/metadata: sync with Debian * d/tests: partially merge with Debian -- Lukas Märdian Thu, 18 Aug 2022 14:53:33 +0200 ** Changed in: netplan.io (Ubuntu Kinetic) Status: Triaged => 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/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in netplan: Fix Committed Status in NetworkManager: New Status in netplan.io package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Incomplete Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: Incomplete Status in netplan.io source package in Kinetic: Fix Released Status in network-manager source package in Kinetic: Incomplete Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951653] Re: can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged'
This bug was fixed in the package netplan.io - 0.105-0ubuntu1 --- netplan.io (0.105-0ubuntu1) kinetic; urgency=medium * New upstream release: 0.105 - Add support for VXLAN tunnels (#288), LP: #1764716 - Add support for VRF devices (#285), LP: #1773522 - Add support for InfiniBand (IPoIB) (#283), LP: #1848471 - Allow key configuration for GRE tunnels (#274), LP: #1966476 - Allow setting the regulatory domain (#281), LP: #1951586 - Documentation improvements & restructuring (#287) - Add meson build system (#268) - Add abigail ABI compatibility checker (#269) - Update of Fedora RPM spec (#264) - CI improvements (#265, #282) - Netplan `set` uses the consolidated libnetplan YAML parser (#254) - Refactor ConfigManager to use the libnetplan YAML parser (#255) - New `netplan_netdef_get_filepath` API (#275) - Improve NetworkManager device management logic (#276), LP: #1951653 Bug fixes: - Fix `apply` netdev rename/create race condition (#260), LP: #1962095 - Fix `try` timeout (#271), LP: #1967084 - Fix infinite timeouts in ovs-vsctl (#266), Closes: #1000137 - Fix offload options using tristate setting (#270), LP: #1956264 - Fix rendering of NetworkManager passthrough WPA (#279), LP: #1972800 - Fix CLI crash on LibNetplanException (#286) - Fix NetworkManager internal DHCP client lease lookup (#284), LP: #1979674 * Update symbols file for 0.105 * d/patches/: Drop patches, applied upstream * d/p/autopkgtest-fixes.patch: Refresh * d/control: bump Standards-Version, no changes needed * d/control, d/tests/control: suggest/add iw for setting a regulatory domain * d/control: merge with Debian, dropping deprecated versioned depends * d/control: Update Vcs-* tags for Ubuntu * d/watch: sync with Debian * d/u/metadata: sync with Debian * d/tests: partially merge with Debian -- Lukas Märdian Thu, 18 Aug 2022 14:53:33 +0200 ** Changed in: netplan.io (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/1951653 Title: can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged' Status in netplan.io package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Confirmed Bug description: I have tried to tell netplan to let my ethernet device be managed by NetworkManager, so that I can then configure a pppoe connection on top of this device. This fails with: # nmcli c up netplan-wan Error: Connection activation failed: No suitable device found for this connection (device lo not available because device is strictly unmanaged). # I don't know why it mentions 'lo' in that message, but the wan interface is unmanaged (as are all devices on the system, but this one is supposed to be managed): # nmcli d status | grep wan wan ethernet unmanaged -- # After much searching, I've figured out that this comes from /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf: keyfile] unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma Even though I've told netplan to use the NM renderer for this device, the configuration emitted by netplan is insufficient to override this. Using the workaround from https://askubuntu.com/questions/71159/network-manager-says-device-not- managed (sudo touch /etc/NetworkManager/conf.d/10-globally-managed- devices.conf) doesn't work, but if I set NetworkManager as the toplevel renderer in /etc/netplan, /run/NetworkManager/conf.d/10-globally-managed-devices.conf is emitted, which evidently DOES work. But I only have one device that I want rendered by NM, so I shouldn't have to declare NM at the top level of the yaml with a lot of duplication in order to get this result. I would argue that the 10-globally-managed-devices.conf should not be there at all. But if it is going to be, then netplan needs to consistently override it whenever there is any use of the NetworkManager backend. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1951653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973604] Re: [nvidia340] display hangs 10s on boot with nvidia-340
This bug was fixed in the package ubuntu-drivers-common - 1:0.9.6.2 --- ubuntu-drivers-common (1:0.9.6.2) kinetic; urgency=medium [ Jeremy Szu ] * share/hybrid/gpu-manager.c: - Don't wait for nvidia-drm when dealing with nvidia-340 (LP: #1973604). [ Ēriks Remess ] * UbuntuDrivers/kerneldetection.py: - Detect unsigned kernel images correctly. [ Alberto Milone ] * UbuntuDrivers/detect.py: - Make sure -open drivers have a lower priority. -- Alberto Milone Thu, 11 Aug 2022 15:09:46 + ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Fix Released -- 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/1973604 Title: [nvidia340] display hangs 10s on boot with nvidia-340 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Bug description: Since ubuntu-drivers-common 1:0.9.0~0.20.04.6, system running kernel 5.4 & nvidia-340 will experience 10s useless delay on boot because gpu-manager is waiting for nvidia-drm to load & nvidia-drm is not built in with nvidia-340. Several legacy nvidia cards are stuck to nvidia-340 & Kernel 5.4 as detailled in: https://nvidia.custhelp.com/app/answers/detail/a_id/3142/%7E/support-timeframes-for-unix-legacy-gpu-releases See prior investigation in comments of https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1958488 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1973604/+subscriptions -- Mailing list: https://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 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.
Last comment for the day ... from what little I've seen, it seems like it might require defining a lengthy list of packages relative to 22.04 to migrate this snap to 22.04. Or maybe I'm misreading it. In any event, I'd still like to make this happen. On Thu, Aug 18, 2022 at 3:56 PM Robert Day wrote: > Actually, another part of my grep search produced the following, which > seems to suggest that an older version of libwayland-client0 is being used: > > > parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.mips64el: > https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_mips64el.deb > > parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.arm64: > https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_arm64.deb > > parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.i386: > https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_i386.deb > > parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.armel: > https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_armel.deb > > parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.mipsel: > https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_mipsel.deb > > parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.arm: > https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_armhf.deb > > parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.amd64: > https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_amd64.deb > > At least that's the way I read it. > > rday > > On Thu, Aug 18, 2022 at 3:43 PM Robert Day > wrote: > >> A comprehensive grep includes the lines: >> >> parts/launcher/state/build: - libwayland-client0=1.20.0-1 >> parts/va-drivers/state/build: - libwayland-client0=1.20.0-1 >> parts/pipewire/state/build: - libwayland-client0=1.20.0-1 >> parts/chromium-build/state/build: - libwayland-client0=1.20.0-1 >> parts/manpage/state/build: - libwayland-client0=1.20.0-1 >> >> Oh, wait, there we >> go: >> parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json >> appears to be a version manifest that does not include anything for 22.04. >> Does that sound like the problem? >> >> P.S. Thanks for your patience with all of this. >> >> On Thu, Aug 18, 2022 at 3:30 PM Nathan Teodosio < >> 1986...@bugs.launchpad.net> wrote: >> >>> What is libwayland-client0 version in your logs? Focal has 1.18.0, but >>> >>> wayland-1.21.0/debian/libwayland-client0.symbols: >>> wl_proxy_marshal_flags@Base 1.20.0 >>> >>> -- >>> You received this bug notification because you are subscribed to the bug >>> report. >>> https://bugs.launchpad.net/bugs/1986925 >>> >>> Title: >>> [snap] Trying to build chromium snap for core22: pkg-config fails. >>> >>> Status in chromium-browser package in Ubuntu: >>> New >>> >>> Bug description: >>> I checked out the "dev" branch of chromium-browser from launchpad and >>> did what seemed necessary to update snapcraft.yaml to build with >>> snapcraft 7 for core22. The only change of any significance was to >>> change the extension from "gnome-3-38" to the core22-specific "gnome" >>> extension. I started the build and it ran for quite some time (in a >>> persistent 22.04 LXD container) until: >>> >>> 2022-08-18 09:11:00.869 :: + OUT=out/Release >>> >>> 2022-08-18 09:11:00.869 :: + mkdir -p out/Release >>> >>> 2022-08-18 09:11:00.888 :: + cp >>> /root/snaps/snap-from-source/stage/build/args.gn out/Release/ >>> >>> 2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']' >>> >>> 2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']' >>> >>> 2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig >>> >>> 2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc >>> >>> 2022-08-18 09:11:00.935 :: + cd - >>> >>> 2022-08-18 09:11:00.935 :: >>> /root/snaps/snap-from-source/parts/chromium/build >>> >>> 2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release >>> >>> 2022-08-18 09:11:07.112 :: ERROR at >>> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit >>> code. >>> >>> 2022-08-18 09:11:07.112 :: pkgresult = >>> exec_script(pkg_config_script, args, "value") >>> 2022-08-18 09:11:07.113 :: ^-- >>> >>> 2022-08-18 09:11:07.113 :: Current dir: >>> /root/snaps/snap-from-source/parts/chromium/build/out/Release/ >>> 2022-08-18 09:11:07.113 :: Command: python3 >>>
[Desktop-packages] [Bug 1913979] Re: misleading error messages when /etc/NetworkManager/system-connections is a cross-filesystem symlink
I think there are multiple bugs in play here. My system-connections dir is a symlink within the same filesystem, and whenever I try to save a new connection I get the "settings plugin does not support adding connections" message. Aug 18 17:11:08 workhorse4 NetworkManager[4092654]: [1660857068.1365] audit: op="connection-add" pid=4124192 uid=1000 result="fail" reason="failure adding connection: settings plugin does not support adding connections" The symlink target dir has the same ownership/permissions as the original system-connections dir - 0755, root:root. -- 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/1913979 Title: misleading error messages when /etc/NetworkManager/system-connections is a cross-filesystem symlink Status in network-manager package in Ubuntu: Confirmed Bug description: If the /etc/NetworkManager/system-connections directory is a cross- filesystem symlink, activating connections will fail with the unrelated messages: * "failed to create file ...: Read-only file system" (TRACE level) * "failure adding connection: settings plugin does not support adding connections" (DEBUG level and above) * no error message (Gnome UI) I suspect moving the systems-connections directory onto a separate filesystem is not supported because network manager tries to atomically move a connection temp file into place and fails, but this is really hard to figure out since the error messages are completely unrelated. Versions: Ubuntu 20.10 network-manager 1.26.2-1ubuntu1 network-manager-gnome 1.18.0-1ubuntu2 How to reproduce: sudo mv /etc/NetworkManager/system-connections /some/other/mountpoint/system-connections sudo ln -s /some/other/mountpoint/system-connections /etc/NetworkManager/system-connections Then: * select any wifi network via the Gnome UI, or * connect to a wifi network via nmcli, or * connect to a wifi network via nmtui Symptoms: * "failed to create file ...: Read-only file system" (TRACE level, journalctl) * "failure adding connection: settings plugin does not support adding connections" (DEBUG level and above, journalctl and nmtui/nmcli output) * no error message (Gnome UI) Relevant sample logs: Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4038] active-connection[0x56274f6f0a60]: creating Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4039] active-connection[0x56274f6f0a60]: set device "wlp61s0" [0x56274f883f00] Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4039] device[d62304f9da70d783] (wlp61s0): add_pending_action (1): 'activation-5' Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4040] active-connection[0x56274f6f0a60]: constructed (NMActRequest, version-id 5, type managed) Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4040] auth: call[37]: CheckAuthorization(org.freedesktop.NetworkManager.network-control), subject=unix-process[pid=1369566, uid=0, start=18908113] (succeeding for root) Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4041] auth: call[37]: completed: authorized=1, challenge=0 (simulated) Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4041] auth: call[38]: CheckAuthorization(org.freedesktop.NetworkManager.settings.modify.system), subject=unix-process[pid=1369566, uid=0, start=18908113] (succeeding for root) Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4042] auth: call[38]: completed: authorized=1, challenge=0 (simulated) Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4042] settings: add-connection: failed to add a4e6f563-eb2a-41ff-bc23-986ee3438ed9/'mywifi_2G': settings plugin does not support adding connections Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4061] keyfile: commit: a4e6f563-eb2a-41ff-bc23-986ee3438ed9 (mywifi_2G) failed to add: error writing to file '/etc/NetworkManager/system-connections/mywifi_2G.nmconnection': failed to create file /etc/NetworkManager/system-connections/mywifi_2G.nmconnection.ZE5DY0: Read-only file system Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4062] settings: add-connection: failed to add a4e6f563-eb2a-41ff-bc23-986ee3438ed9/'mywifi_2G': error writing to file '/etc/NetworkManager/system-connections/mywifi_2G.nmconnection': failed to create file /etc/NetworkManager/system-connections/mywifi_2G.nmconnection.ZE5DY0: Read-only file system Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4062] active-connection[0x56274f6f0a60]: Failed to activate '(null)': failure adding connection: settings plugin does not support adding connections Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4062] active-connection[0x56274f6f0a60]: set state deactivated (was unknown) Feb 01 20:56:04 laptop
[Desktop-packages] [Bug 1934579] Re: Nautilus crashes when opening places from the dock contextmenu
Just wanted to confirm as the op that this bug exists on fresh install of 22.04 LTS. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1934579 Title: Nautilus crashes when opening places from the dock contextmenu Status in nautilus package in Ubuntu: Confirmed Bug description: After updating to Ubuntu 21.04, Nautilus crashes every time I try to open a second folder by right-clicking on the Nautilus icon in the "Favorites" left sidebar (i.e., launch panel) and selecting a bookmarked "Places" folder. Normally, this would open a second Nautilus window for the selected folder, but instead, any open Nautilus windows disappear and no window opens for the selected folder. In other words, Nautilus crashes. This did not occur on Ubuntu 20.10. This AskUbuntu post describes the same issue: https://askubuntu.com/questions/1344175/nautilus-crashes-when-trying- to-open-another-window-by-right-clicking-the-nautil If, instead, I right-click the Nautilus icon, select "New Window" and then select the desired "Places" folder from the left sidebar of the newly opened window, Nautilus does not crash. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jul 4 13:36:13 2021 InstallationDate: Installed on 2020-02-05 (514 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: Upgraded to hirsute on 2021-06-30 (4 days ago) usr_lib_nautilus: evince40.1-1 file-roller 3.38.1-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934579/+subscriptions -- Mailing list: https://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 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.
Actually, another part of my grep search produced the following, which seems to suggest that an older version of libwayland-client0 is being used: parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.mips64el: https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_mips64el.deb parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.arm64: https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_arm64.deb parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.i386: https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_i386.deb parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.armel: https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_armel.deb parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.mipsel: https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_mipsel.deb parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.arm: https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_armhf.deb parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.amd64: https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_amd64.deb At least that's the way I read it. rday On Thu, Aug 18, 2022 at 3:43 PM Robert Day wrote: > A comprehensive grep includes the lines: > > parts/launcher/state/build: - libwayland-client0=1.20.0-1 > parts/va-drivers/state/build: - libwayland-client0=1.20.0-1 > parts/pipewire/state/build: - libwayland-client0=1.20.0-1 > parts/chromium-build/state/build: - libwayland-client0=1.20.0-1 > parts/manpage/state/build: - libwayland-client0=1.20.0-1 > > Oh, wait, there we > go: > parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json > appears to be a version manifest that does not include anything for 22.04. > Does that sound like the problem? > > P.S. Thanks for your patience with all of this. > > On Thu, Aug 18, 2022 at 3:30 PM Nathan Teodosio < > 1986...@bugs.launchpad.net> wrote: > >> What is libwayland-client0 version in your logs? Focal has 1.18.0, but >> >> wayland-1.21.0/debian/libwayland-client0.symbols: >> wl_proxy_marshal_flags@Base 1.20.0 >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1986925 >> >> Title: >> [snap] Trying to build chromium snap for core22: pkg-config fails. >> >> Status in chromium-browser package in Ubuntu: >> New >> >> Bug description: >> I checked out the "dev" branch of chromium-browser from launchpad and >> did what seemed necessary to update snapcraft.yaml to build with >> snapcraft 7 for core22. The only change of any significance was to >> change the extension from "gnome-3-38" to the core22-specific "gnome" >> extension. I started the build and it ran for quite some time (in a >> persistent 22.04 LXD container) until: >> >> 2022-08-18 09:11:00.869 :: + OUT=out/Release >> >> 2022-08-18 09:11:00.869 :: + mkdir -p out/Release >> >> 2022-08-18 09:11:00.888 :: + cp >> /root/snaps/snap-from-source/stage/build/args.gn out/Release/ >> >> 2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']' >> >> 2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']' >> >> 2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig >> >> 2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc >> >> 2022-08-18 09:11:00.935 :: + cd - >> >> 2022-08-18 09:11:00.935 :: >> /root/snaps/snap-from-source/parts/chromium/build >> >> 2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release >> >> 2022-08-18 09:11:07.112 :: ERROR at >> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit >> code. >> >> 2022-08-18 09:11:07.112 :: pkgresult = >> exec_script(pkg_config_script, args, "value") >> 2022-08-18 09:11:07.113 :: ^-- >> >> 2022-08-18 09:11:07.113 :: Current dir: >> /root/snaps/snap-from-source/parts/chromium/build/out/Release/ >> 2022-08-18 09:11:07.113 :: Command: python3 >> /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py >> -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb >> >> 2022-08-18 09:11:07.113 :: Returned 1. >> >> 2022-08-18 09:11:07.113 :: stderr: >> >> 2022-08-18 09:11:07.113 :: >> >> 2022-08-18 09:11:07.113 :: Could not run pkg-config. >> >> 2022-08-18 09:11:07.113 :: >> >> 2022-08-18 09:11:07.113 :: See >> //third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called. >> 2022-08-18
Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.
A comprehensive grep includes the lines:
parts/launcher/state/build: - libwayland-client0=1.20.0-1
parts/va-drivers/state/build: - libwayland-client0=1.20.0-1
parts/pipewire/state/build: - libwayland-client0=1.20.0-1
parts/chromium-build/state/build: - libwayland-client0=1.20.0-1
parts/manpage/state/build: - libwayland-client0=1.20.0-1
Oh, wait, there we
go:
parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json
appears to be a version manifest that does not include anything for 22.04.
Does that sound like the problem?
P.S. Thanks for your patience with all of this.
On Thu, Aug 18, 2022 at 3:30 PM Nathan Teodosio <1986...@bugs.launchpad.net>
wrote:
> What is libwayland-client0 version in your logs? Focal has 1.18.0, but
>
> wayland-1.21.0/debian/libwayland-client0.symbols:
> wl_proxy_marshal_flags@Base 1.20.0
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1986925
>
> Title:
> [snap] Trying to build chromium snap for core22: pkg-config fails.
>
> Status in chromium-browser package in Ubuntu:
> New
>
> Bug description:
> I checked out the "dev" branch of chromium-browser from launchpad and
> did what seemed necessary to update snapcraft.yaml to build with
> snapcraft 7 for core22. The only change of any significance was to
> change the extension from "gnome-3-38" to the core22-specific "gnome"
> extension. I started the build and it ran for quite some time (in a
> persistent 22.04 LXD container) until:
>
> 2022-08-18 09:11:00.869 :: + OUT=out/Release
>
> 2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>
> 2022-08-18 09:11:00.888 :: + cp /root/snaps/snap-from-source/stage/build/
> args.gn out/Release/
> 2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
> 2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
> 2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>
> 2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>
> 2022-08-18 09:11:00.935 :: + cd -
>
> 2022-08-18 09:11:00.935 ::
> /root/snaps/snap-from-source/parts/chromium/build
>
> 2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
>
> 2022-08-18 09:11:07.112 :: ERROR at
> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
> code.
>
> 2022-08-18 09:11:07.112 :: pkgresult =
> exec_script(pkg_config_script, args, "value")
> 2022-08-18 09:11:07.113 :: ^--
>
> 2022-08-18 09:11:07.113 :: Current dir:
> /root/snaps/snap-from-source/parts/chromium/build/out/Release/
> 2022-08-18 09:11:07.113 :: Command: python3
> /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
> -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
>
> 2022-08-18 09:11:07.113 :: Returned 1.
>
> 2022-08-18 09:11:07.113 :: stderr:
>
> 2022-08-18 09:11:07.113 ::
>
> 2022-08-18 09:11:07.113 :: Could not run pkg-config.
>
> 2022-08-18 09:11:07.113 ::
>
> 2022-08-18 09:11:07.113 :: See
> //third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
> 2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
>
> 2022-08-18 09:11:07.113 :: ^--
>
> 2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file
> to be included.
> 2022-08-18 09:11:07.114 ::
> "//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan",
> 2022-08-18 09:11:07.114 ::
> ^---
> 2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with
> code 1.
> Review the scriptlet and make sure it's correct.
>
> I verified that the pkg-config utility is installed in the container;
> I can only suspect that this error is related to switching to the
> core22 gnome extension. I am open to suggestions.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986925/+subscriptions
>
>
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1986925
Title:
[snap] Trying to build chromium snap for core22: pkg-config fails.
Status in chromium-browser package in Ubuntu:
New
Bug description:
I checked out the "dev" branch of chromium-browser from launchpad and
did what seemed necessary to update snapcraft.yaml to build with
snapcraft 7 for core22. The only change of any significance was to
change the extension from "gnome-3-38" to the core22-specific "gnome"
extension. I started the build and it ran for quite some time (in a
persistent 22.04 LXD container) until:
2022-08-18 09:11:00.869 :: + OUT=out/Release
2022-08-18 09:11:00.869 :: + mkdir -p out/Release
2022-08-18 09:11:00.888 :: + cp
[Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.
What is libwayland-client0 version in your logs? Focal has 1.18.0, but
wayland-1.21.0/debian/libwayland-client0.symbols:
wl_proxy_marshal_flags@Base 1.20.0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1986925
Title:
[snap] Trying to build chromium snap for core22: pkg-config fails.
Status in chromium-browser package in Ubuntu:
New
Bug description:
I checked out the "dev" branch of chromium-browser from launchpad and
did what seemed necessary to update snapcraft.yaml to build with
snapcraft 7 for core22. The only change of any significance was to
change the extension from "gnome-3-38" to the core22-specific "gnome"
extension. I started the build and it ran for quite some time (in a
persistent 22.04 LXD container) until:
2022-08-18 09:11:00.869 :: + OUT=out/Release
2022-08-18 09:11:00.869 :: + mkdir -p out/Release
2022-08-18 09:11:00.888 :: + cp
/root/snaps/snap-from-source/stage/build/args.gn out/Release/
2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
2022-08-18 09:11:00.935 :: + cd -
2022-08-18 09:11:00.935 :: /root/snaps/snap-from-source/parts/chromium/build
2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
2022-08-18 09:11:07.112 :: ERROR at
//build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit code.
2022-08-18 09:11:07.112 :: pkgresult = exec_script(pkg_config_script,
args, "value")
2022-08-18 09:11:07.113 :: ^--
2022-08-18 09:11:07.113 :: Current dir:
/root/snaps/snap-from-source/parts/chromium/build/out/Release/
2022-08-18 09:11:07.113 :: Command: python3
/root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
-p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
2022-08-18 09:11:07.113 :: Returned 1.
2022-08-18 09:11:07.113 :: stderr:
2022-08-18 09:11:07.113 ::
2022-08-18 09:11:07.113 :: Could not run pkg-config.
2022-08-18 09:11:07.113 ::
2022-08-18 09:11:07.113 :: See
//third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
2022-08-18 09:11:07.113 :: ^--
2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file to be
included.
2022-08-18 09:11:07.114 ::
"//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan",
2022-08-18 09:11:07.114 ::
^---
2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with code
1.
Review the scriptlet and make sure it's correct.
I verified that the pkg-config utility is installed in the container;
I can only suspect that this error is related to switching to the
core22 gnome extension. I am open to suggestions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986925/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897369] Re: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)
This is not a disconnect between the capability framework (which is integrated into the LSM), nor the devs who implemented AppArmor. Calls to capable() can have side effects, it is an LSM hook and linux capabilities are implemented as an LSM module that is stacked with the other LSMs. So if an LSM chooses to mediate a capability, it can. AppArmor, Smack, and SELinux all mediate capable calls, which is done in addition to the regular capable subsystem check. Unless the call to capable() is marked with the option CAP_OPT_NOAUDIT, an LSM may generate audit messages. The solution is that the caller of capable() needs to pass the option CAP_OPT_NOAUDIT if there really shouldn't be an audit message generated. If userspace code doesn't want an audit message generated then it needs to work with the LSMs policy to make sure an audit message is not generated. AppArmor policy by default quiets auditing of capability messages if the capability is granted by policy, it also allows disabling of auditing of a message if the capability should be denied. -- 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/1897369 Title: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE) Status in cups-filters package in Ubuntu: Triaged Status in cups-filters package in Debian: New Bug description: In Ubuntu 20.04.1 with *cups-browsed* 1.27.4-1, apparmor prevents `/usr/sbin/cups-browsed` to change its nice value. $ sudo dmesg | grep apparmor [541870.509461] audit: type=1400 audit(1600898428.089:60): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=62030 comm="cups-browsed" capability=23 capname="sys_nice" [628298.779668] audit: type=1400 audit(1600984854.115:61): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=66850 comm="cups-browsed" capability=23 capname="sys_nice" [714667.424963] audit: type=1400 audit(1601071220.527:62): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=76828 comm="cups-browsed" capability=23 capname="sys_nice" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1897369/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984233] Re: Please remove nautilus extensions incompatible with Nautilus 43
** Tags removed: block-proposed ** Tags added: update-excuse ** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Changed in: nautilus (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/1984233 Title: Please remove nautilus extensions incompatible with Nautilus 43 Status in eiciel package in Ubuntu: Fix Released Status in folder-color package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Fix Committed Status in nautilus-dropbox package in Ubuntu: Fix Released Status in nautilus-filename-repairer package in Ubuntu: Fix Released Status in nautilus-ideviceinfo package in Ubuntu: Fix Released Status in nautilus-image-converter package in Ubuntu: Fix Released Status in nautilus-share package in Ubuntu: New Status in nautilus-wipe package in Ubuntu: Fix Released Status in seahorse-nautilus package in Ubuntu: Fix Released Bug description: nautilus python 4.0~alpha is a major API update along with nautilus 43 which had a major API update. Please remove these extensions since they are currently incompatible with the Nautilus and nautilus-python versions we are including in Kinetic - eiciel -- Needs to be ported from GTK3 Debian maintainer thinks the package is not worth keeping without the extension https://salsa.debian.org/debian/eiciel/-/merge_requests/2 - folder-color -- Needs to be ported from GTK3 https://github.com/costales/folder-color/issues/17 Ubuntu-specific package - nautilus-dropbox -- Needs to be ported from GTK3 https://github.com/dropbox/nautilus-dropbox/issues/101 - nautilus-filename-repairer -- Needs to be ported from GTK3 - nautilus-ideviceinfo -- Needs to be ported from GTK3 Ubuntu-specific package - nautilus-image-converter -- Needs to be ported from GTK3 Debian removal bug filed. Unmaintained in Debian or upstream - nautilus-share -- Needs to be ported from GTK3 - nautilus-wipe -- Needs to be ported from GTK3 - seahorse-nautilus -- Needs to be ported from GTK3 Transition tracker -- We are going to try to fix several of the other affected source packages (not listed above) to either drop their Nautilus extension or port them to work with Nautilus 43. https://people.canonical.com/~ubuntu-archive/transitions/html/auto- nautilus.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eiciel/+bug/1984233/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983638] Re: Ubuntu 22.10 Settings-sound-output-test does not work
This bug was fixed in the package gnome-control-center - 1:42.3-2ubuntu1 --- gnome-control-center (1:42.3-2ubuntu1) kinetic; urgency=medium * Merge with Debian - Fix GNOME version number with latest gnome-desktop (LP: #1986616) * Recommend libcanberra-pulse for Test Sound Output feature (Closes: #676234) (LP: #1983638) (LP: #1004973) * Refresh patches gnome-control-center (1:42.3-2) unstable; urgency=medium * Lower gnome-remote-desktop from Depends to Recommends (Closes: #1014879) * Cherry-pick patches to use gnome-shell version number as the GNOME Version in the About page gnome-control-center (1:42.3-1) unstable; urgency=medium [ Jeremy Bicha ] * New upstream release * debian/control.in: Depend on gnome-remote-desktop (LP: #1980606) [ Marco Trevisan (Treviño) ] * debian/patches: Use Fedora patch to handle distro logo -- Jeremy Bicha Thu, 18 Aug 2022 09:16:02 -0400 ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1983638 Title: Ubuntu 22.10 Settings-sound-output-test does not work Status in gnome-control-center package in Ubuntu: Fix Released Bug description: Open settings. select sound. System Volume and Volume for System Sounds are at maximum, Output Device is HDMI / DisplayPort2 - Built-in Audio click on Test and then on Left or Right speaker has no effect (no sound) but clicking on Alert Sound works fine. Playing a movie.MOV with totem sound is ok. On the same PC different partition I have Ubuntu 22.04 and problem does not occur. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:42.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Aug 5 07:06:31 2022 InstallationDate: Installed on 2022-07-19 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1983638/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986616] Re: Wrong gnome version
This bug was fixed in the package gnome-control-center - 1:42.3-2ubuntu1 --- gnome-control-center (1:42.3-2ubuntu1) kinetic; urgency=medium * Merge with Debian - Fix GNOME version number with latest gnome-desktop (LP: #1986616) * Recommend libcanberra-pulse for Test Sound Output feature (Closes: #676234) (LP: #1983638) (LP: #1004973) * Refresh patches gnome-control-center (1:42.3-2) unstable; urgency=medium * Lower gnome-remote-desktop from Depends to Recommends (Closes: #1014879) * Cherry-pick patches to use gnome-shell version number as the GNOME Version in the About page gnome-control-center (1:42.3-1) unstable; urgency=medium [ Jeremy Bicha ] * New upstream release * debian/control.in: Depend on gnome-remote-desktop (LP: #1980606) [ Marco Trevisan (Treviño) ] * debian/patches: Use Fedora patch to handle distro logo -- Jeremy Bicha Thu, 18 Aug 2022 09:16:02 -0400 ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1986616 Title: Wrong gnome version Status in gnome-control-center package in Ubuntu: Fix Released Bug description: If I run in a terminal: $ gnome-control-center info-overview Gnome version 3.0 is shown in window. My current gnome version is: $ gnome-shell --version GNOME Shell 42.4 My ubuntu version: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:42.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Aug 16 07:48:18 2022 InstallationDate: Installed on 2018-09-22 (1423 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to kinetic on 2021-02-17 (544 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1986616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983381] Re: Enable the restic backend
https://gitlab.gnome.org/World/deja-dup/-/blob/main/PACKAGING.md has some advice for packagers around enabling restic support. (Though note that it references the new `-Dpackagekit=enabled` flag which only exists in 44.x. Just ignore that for 43.x. PackageKit is automatically used as long as it exists at build time in 43.x) -- 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/1983381 Title: Enable the restic backend Status in deja-dup package in Ubuntu: New Bug description: https://discourse.gnome.org/t/call-for-testing-deja-dup-43-alpha/7602 Even though it's flagged as experimental, there is a lot of excitement around it, and it's still opt-in. It looks like it requires rclone, which is not in main, but the same trick used for pydrive can be used, and then it can be installed at run-time if the user selects restic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1983381/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986450] Re: Visual artifact 1px vertical white line right side of the wallpaper
Single monitor examples. The same happens when I activate the second monitor, with the exception that the white lines are both on the second display before closing the Settings (if I recall correctly). Would you like pictures of the two monitor setup, as well? Or do these two pictures demonstrate the artifact well enough so that they are not needed? -- 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/1986450 Title: Visual artifact 1px vertical white line right side of the wallpaper Status in gnome-shell package in Ubuntu: New Bug description: After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that there is a 1px wide vertical white line on the desktop that appears whenever an application has focus. It is on the right side of the monitor, covering the background wallpaper but not the menu. Workaround: in Displays, change scale to something else than 100% and then change back to 100%. That white vertical line will stay at the former 100% window size location until the Settings window is closed. It disappears when the Settings is closed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-27 (1570 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: gnome-shell 42.2-0ubuntu0.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: wayland-session jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1986450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1975935] Re: Key input repeated unintendedly
This is happening on a default Jammy GNOME install. No extra extensions. This starts when the machine reaches high uptime usually 2 weeks+ journalctl is full of: Aug 18 11:28:09 veloci gnome-shell[2558]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Aug 18 11:28:09 veloci gnome-shell[2558]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Aug 18 11:28:09 veloci gnome-shell[2558]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Aug 18 11:28:09 veloci gnome-shell[2558]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Aug 18 11:28:09 veloci gnome-shell[2134]: Window manager warning: last_user_time (2482182490) is greater than comparison timestamp (2482182213). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Aug 18 11:28:09 veloci gnome-shell[2134]: Window manager warning: 0x23e appears to be one of the offending windows with a timestamp of 2482182490. Working around... lspci: 00:00.0 Host bridge: Intel Corporation Comet Lake-U v1 4c Host Bridge/DRAM Controller (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation CometLake-U GT2 [UHD Graphics] (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem 00:14.0 USB controller: Intel Corporation Comet Lake PCH-LP USB 3.1 xHCI Host Controller 00:14.2 RAM memory: Intel Corporation Comet Lake PCH-LP Shared SRAM 00:14.3 Network controller: Intel Corporation Comet Lake PCH-LP CNVi WiFi 00:15.0 Serial bus controller: Intel Corporation Serial IO I2C Host Controller 00:15.1 Serial bus controller: Intel Corporation Comet Lake Serial IO I2C Host Controller 00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface 00:19.0 Serial bus controller: Intel Corporation Comet Lake Serial IO I2C Host Controller 00:1c.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #1 (rev f0) 00:1c.4 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #5 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #13 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Comet Lake PCH-LP LPC Premium Controller/eSPI Controller 00:1f.3 Audio device: Intel Corporation Comet Lake PCH-LP cAVS 00:1f.4 SMBus: Intel Corporation Comet Lake PCH-LP SMBus Host Controller 00:1f.5 Serial bus controller: Intel Corporation Comet Lake SPI (flash) Controller 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (10) I219-LM 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 02:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06) 03:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06) 03:01.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06) 03:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06) 04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) 3b:00.0 Non-Volatile memory controller: KIOXIA Corporation Device 0001 ** Changed in: gnome-shell (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1975935 Title: Key input repeated unintendedly Status in gnome-shell package in Ubuntu: New Bug description: gnome-shell[3502]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! syslog above. sometimes keys repeat(and slight system freeze / hitch) whithout holding key. like; $ helllo (of cource I typed just h, e, l, l, o ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 27 20:29:17 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-18 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log
[Desktop-packages] [Bug 1986450] Re: Visual artifact 1px vertical white line right side of the wallpaper
Picture two, after the desktop was scaled to 125% and then back to 100%, and the Settings window is not closed, yet (the white line disappears after the Settings window is closed). ** Attachment added: "Screenshot from 2022-08-18 21-36-55.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1986450/+attachment/5609711/+files/Screenshot%20from%202022-08-18%2021-36-55.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/1986450 Title: Visual artifact 1px vertical white line right side of the wallpaper Status in gnome-shell package in Ubuntu: New Bug description: After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that there is a 1px wide vertical white line on the desktop that appears whenever an application has focus. It is on the right side of the monitor, covering the background wallpaper but not the menu. Workaround: in Displays, change scale to something else than 100% and then change back to 100%. That white vertical line will stay at the former 100% window size location until the Settings window is closed. It disappears when the Settings is closed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-27 (1570 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: gnome-shell 42.2-0ubuntu0.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: wayland-session jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1986450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986450] Re: Visual artifact 1px vertical white line right side of the wallpaper
Picture one, default when the desktop is no focused. ** Attachment added: "Screenshot from 2022-08-18 21-35-56.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1986450/+attachment/5609710/+files/Screenshot%20from%202022-08-18%2021-35-56.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/1986450 Title: Visual artifact 1px vertical white line right side of the wallpaper Status in gnome-shell package in Ubuntu: New Bug description: After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that there is a 1px wide vertical white line on the desktop that appears whenever an application has focus. It is on the right side of the monitor, covering the background wallpaper but not the menu. Workaround: in Displays, change scale to something else than 100% and then change back to 100%. That white vertical line will stay at the former 100% window size location until the Settings window is closed. It disappears when the Settings is closed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-27 (1570 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: gnome-shell 42.2-0ubuntu0.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: wayland-session jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1986450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969891] Re: Firefox snap can't be added to Dock favorites
The /usr/bin/firefox script in 22.04 launches the firefox snap, but prior to that it rewrites existing launcher/dock favourites. For GNOME Shell for example (which you appear to be running), if the output of $(gsettings get org.gnome.shell favorite-apps) contains an entry pointing to "firefox.desktop", it will rewrite it to "firefox_firefox.desktop". Can you share the output of $(gsettings get org.gnome.shell favorite- apps) here (possibly redacted to avoid leaking your personal preferences other than firefox)? ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1969891 Title: Firefox snap can't be added to Dock favorites Status in firefox package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: After upgrading from 21.10 to 22.04 the old Firefox was removed from my Dock favorites. I readded Firefox to my favorites which adds the Firefox icon to the favorites as expected. However, clicking on it will open the Firefox snap on the bottom of the Dock. So now I have 2 Firefox symbols in my Dock. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 Uname: Linux 5.17.0-4.1-liquorix-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:49:32 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-05-31 (325 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1969891/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973441] Re: Printing does not work on Ubuntu 22.04 - cups-pki-invalid
Deleting the certificate also worked for me. To do this user needs admin privileges. I guess this breaks basic printing functionality for regular users. This is my printer: HP_Smart_Tank_530_series_21D133 -- 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/1973441 Title: Printing does not work on Ubuntu 22.04 - cups-pki-invalid Status in cups package in Ubuntu: Confirmed Bug description: After upgrading to 22.04 printing did not work. There is cups-pki- invalid error and printer goes to paused state. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4 Uname: Linux 5.17.7-051707-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: ubuntu:GNOME Date: Sun May 15 15:34:47 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2021-10-12 (214 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010) Lpstat: device for HP_Color_LaserJet_M552_5F80BF: implicitclass://HP_Color_LaserJet_M552_5F80BF/ MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.7-051707-generic root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-04-24 (21 days ago) dmi.bios.date: 03/29/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G513QY.318 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G513QY dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.81 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.318:bd03/29/2022:br5.19:efr0.81:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G513QY_G513QY dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973441/+subscriptions -- Mailing list: https://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 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.
This appears to describe precisely this issue: https://github.com/libsdl-org/SDL/pull/5092 On Thu, Aug 18, 2022 at 1:06 PM Robert Day wrote: > Yup, same errors ... lots of "wl "and "marshal" undefined references. > Here's just a small sample: > > 2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1038:13: > error: use of undeclared identifier 'wl_proxy_marshal_flags' > > > 2022-08-18 17:03:57.646 :: callback = > wl_proxy_marshal_flags((struct wl_proxy *) wl_display, > > > 2022-08-18 17:03:57.646 ::^ > > > > 2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1062:13: > error: use of undeclared identifier 'wl_proxy_marshal_flags' > > > 2022-08-18 17:03:57.646 :: registry = > wl_proxy_marshal_flags((struct wl_proxy *) wl_display, > > > 2022-08-18 17:03:57.646 ::^ > > > > 2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1175:7: > error: use of undeclared identifier 'wl_proxy_marshal_flags' > > > 2022-08-18 17:03:57.646 :: id = wl_proxy_marshal_flags((struct > wl_proxy *) wl_registry, > > > 2022-08-18 17:03:57.646 :: ^ > > > > 2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1291:7: > error: use of undeclared identifier 'wl_proxy_marshal_flags' > > > 2022-08-18 17:03:57.646 :: id = wl_proxy_marshal_flags((struct > wl_proxy *) wl_compositor, > > > 2022-08-18 17:03:57.647 :: ^ > > > > 2022-08-18 17:03:57.647 :: /usr/include/wayland-client-protocol.h:1307:7: > error: use of undeclared identifier 'wl_proxy_marshal_flags' > > > 2022-08-18 17:03:57.647 :: id = wl_proxy_marshal_flags((struct > wl_proxy *) wl_compositor, > > > 2022-08-18 17:03:57.647 :: ^ > > > > 2022-08-18 17:03:57.647 :: /usr/include/wayland-client-protocol.h:1371:7: > error: use of undeclared identifier 'wl_proxy_marshal_flags' > > > 2022-08-18 17:03:57.647 :: id = wl_proxy_marshal_flags((struct > wl_proxy *) wl_shm_pool, > > > 2022-08-18 17:03:57.647 :: ^ > > > On Thu, Aug 18, 2022 at 1:04 PM Robert Day > wrote: > >> That's what I did, but that's also when I got the errors I included in my >> previous comment. I'm rebuilding just to make sure those errors are >> reproducible. >> >> On Thu, Aug 18, 2022 at 12:45 PM Nathan Teodosio < >> 1986...@bugs.launchpad.net> wrote: >> >>> > but that appears to be because this newer gnome does not supply such >>> an executable; there is no "pkg-config" under >>> /snap/gnome-42-2204/current/usr/bin/, as I assume there must have been >>> under gnome-3-38. >>> >>> Oh, so this time pkg-config in build-packages could solve it? Probably >>> you will have to remove the pkg_config line from args.gn, though. >>> >>> -- >>> You received this bug notification because you are subscribed to the bug >>> report. >>> https://bugs.launchpad.net/bugs/1986925 >>> >>> Title: >>> [snap] Trying to build chromium snap for core22: pkg-config fails. >>> >>> Status in chromium-browser package in Ubuntu: >>> New >>> >>> Bug description: >>> I checked out the "dev" branch of chromium-browser from launchpad and >>> did what seemed necessary to update snapcraft.yaml to build with >>> snapcraft 7 for core22. The only change of any significance was to >>> change the extension from "gnome-3-38" to the core22-specific "gnome" >>> extension. I started the build and it ran for quite some time (in a >>> persistent 22.04 LXD container) until: >>> >>> 2022-08-18 09:11:00.869 :: + OUT=out/Release >>> >>> 2022-08-18 09:11:00.869 :: + mkdir -p out/Release >>> >>> 2022-08-18 09:11:00.888 :: + cp >>> /root/snaps/snap-from-source/stage/build/args.gn out/Release/ >>> >>> 2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']' >>> >>> 2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']' >>> >>> 2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig >>> >>> 2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc >>> >>> 2022-08-18 09:11:00.935 :: + cd - >>> >>> 2022-08-18 09:11:00.935 :: >>> /root/snaps/snap-from-source/parts/chromium/build >>> >>> 2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release >>> >>> 2022-08-18 09:11:07.112 :: ERROR at >>> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit >>> code. >>> >>> 2022-08-18 09:11:07.112 :: pkgresult = >>> exec_script(pkg_config_script, args, "value") >>> 2022-08-18 09:11:07.113 :: ^-- >>> >>> 2022-08-18 09:11:07.113 :: Current dir: >>> /root/snaps/snap-from-source/parts/chromium/build/out/Release/ >>> 2022-08-18 09:11:07.113 :: Command: python3 >>> /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py >>> -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb >>> >>> 2022-08-18 09:11:07.113 :: Returned 1. >>> >>> 2022-08-18 09:11:07.113 :: stderr: >>> >>> 2022-08-18 09:11:07.113 :: >>> >>> 2022-08-18 09:11:07.113 :: Could not run pkg-config.
Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.
Yup, same errors ... lots of "wl "and "marshal" undefined references.
Here's just a small sample:
2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1038:13:
error: use of undeclared identifier 'wl_proxy_marshal_flags'
2022-08-18 17:03:57.646 :: callback =
wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
2022-08-18 17:03:57.646 ::^
2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1062:13:
error: use of undeclared identifier 'wl_proxy_marshal_flags'
2022-08-18 17:03:57.646 :: registry =
wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
2022-08-18 17:03:57.646 ::^
2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1175:7:
error: use of undeclared identifier 'wl_proxy_marshal_flags'
2022-08-18 17:03:57.646 :: id = wl_proxy_marshal_flags((struct
wl_proxy *) wl_registry,
2022-08-18 17:03:57.646 :: ^
2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1291:7:
error: use of undeclared identifier 'wl_proxy_marshal_flags'
2022-08-18 17:03:57.646 :: id = wl_proxy_marshal_flags((struct
wl_proxy *) wl_compositor,
2022-08-18 17:03:57.647 :: ^
2022-08-18 17:03:57.647 :: /usr/include/wayland-client-protocol.h:1307:7:
error: use of undeclared identifier 'wl_proxy_marshal_flags'
2022-08-18 17:03:57.647 :: id = wl_proxy_marshal_flags((struct
wl_proxy *) wl_compositor,
2022-08-18 17:03:57.647 :: ^
2022-08-18 17:03:57.647 :: /usr/include/wayland-client-protocol.h:1371:7:
error: use of undeclared identifier 'wl_proxy_marshal_flags'
2022-08-18 17:03:57.647 :: id = wl_proxy_marshal_flags((struct
wl_proxy *) wl_shm_pool,
2022-08-18 17:03:57.647 :: ^
On Thu, Aug 18, 2022 at 1:04 PM Robert Day wrote:
> That's what I did, but that's also when I got the errors I included in my
> previous comment. I'm rebuilding just to make sure those errors are
> reproducible.
>
> On Thu, Aug 18, 2022 at 12:45 PM Nathan Teodosio <
> 1986...@bugs.launchpad.net> wrote:
>
>> > but that appears to be because this newer gnome does not supply such
>> an executable; there is no "pkg-config" under
>> /snap/gnome-42-2204/current/usr/bin/, as I assume there must have been
>> under gnome-3-38.
>>
>> Oh, so this time pkg-config in build-packages could solve it? Probably
>> you will have to remove the pkg_config line from args.gn, though.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1986925
>>
>> Title:
>> [snap] Trying to build chromium snap for core22: pkg-config fails.
>>
>> Status in chromium-browser package in Ubuntu:
>> New
>>
>> Bug description:
>> I checked out the "dev" branch of chromium-browser from launchpad and
>> did what seemed necessary to update snapcraft.yaml to build with
>> snapcraft 7 for core22. The only change of any significance was to
>> change the extension from "gnome-3-38" to the core22-specific "gnome"
>> extension. I started the build and it ran for quite some time (in a
>> persistent 22.04 LXD container) until:
>>
>> 2022-08-18 09:11:00.869 :: + OUT=out/Release
>>
>> 2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>>
>> 2022-08-18 09:11:00.888 :: + cp
>> /root/snaps/snap-from-source/stage/build/args.gn out/Release/
>>
>> 2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>>
>> 2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>>
>> 2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>>
>> 2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>>
>> 2022-08-18 09:11:00.935 :: + cd -
>>
>> 2022-08-18 09:11:00.935 ::
>> /root/snaps/snap-from-source/parts/chromium/build
>>
>> 2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
>>
>> 2022-08-18 09:11:07.112 :: ERROR at
>> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
>> code.
>>
>> 2022-08-18 09:11:07.112 :: pkgresult =
>> exec_script(pkg_config_script, args, "value")
>> 2022-08-18 09:11:07.113 :: ^--
>>
>> 2022-08-18 09:11:07.113 :: Current dir:
>> /root/snaps/snap-from-source/parts/chromium/build/out/Release/
>> 2022-08-18 09:11:07.113 :: Command: python3
>> /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
>> -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
>>
>> 2022-08-18 09:11:07.113 :: Returned 1.
>>
>> 2022-08-18 09:11:07.113 :: stderr:
>>
>> 2022-08-18 09:11:07.113 ::
>>
>> 2022-08-18 09:11:07.113 :: Could not run pkg-config.
>>
>> 2022-08-18 09:11:07.113 ::
>>
>> 2022-08-18 09:11:07.113 :: See
>> //third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
>> 2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
>>
>> 2022-08-18 09:11:07.113 :: ^--
>>
>> 2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which
[Desktop-packages] [Bug 1970081] Re: The background image of the login window cannot be changed
I was hasty, I didn't realize I just found a way to add the missing setup in the "Control Center". I'm stuck at the default image as well, though the setup actually writes the image I've chosen in a file in /etc. I'm working on it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1970081 Title: The background image of the login window cannot be changed Status in Ubuntu MATE: New Status in arctica-greeter package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 20.04 Mate to 22.04 Mate, my custom wallpaper was replaced with the default one. I can make a change via the menu, but it stays with the default background image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970081/+subscriptions -- Mailing list: https://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 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.
That's what I did, but that's also when I got the errors I included in my
previous comment. I'm rebuilding just to make sure those errors are
reproducible.
On Thu, Aug 18, 2022 at 12:45 PM Nathan Teodosio <1986...@bugs.launchpad.net>
wrote:
> > but that appears to be because this newer gnome does not supply such
> an executable; there is no "pkg-config" under
> /snap/gnome-42-2204/current/usr/bin/, as I assume there must have been
> under gnome-3-38.
>
> Oh, so this time pkg-config in build-packages could solve it? Probably
> you will have to remove the pkg_config line from args.gn, though.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1986925
>
> Title:
> [snap] Trying to build chromium snap for core22: pkg-config fails.
>
> Status in chromium-browser package in Ubuntu:
> New
>
> Bug description:
> I checked out the "dev" branch of chromium-browser from launchpad and
> did what seemed necessary to update snapcraft.yaml to build with
> snapcraft 7 for core22. The only change of any significance was to
> change the extension from "gnome-3-38" to the core22-specific "gnome"
> extension. I started the build and it ran for quite some time (in a
> persistent 22.04 LXD container) until:
>
> 2022-08-18 09:11:00.869 :: + OUT=out/Release
>
> 2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>
> 2022-08-18 09:11:00.888 :: + cp /root/snaps/snap-from-source/stage/build/
> args.gn out/Release/
> 2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
> 2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
> 2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>
> 2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>
> 2022-08-18 09:11:00.935 :: + cd -
>
> 2022-08-18 09:11:00.935 ::
> /root/snaps/snap-from-source/parts/chromium/build
>
> 2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
>
> 2022-08-18 09:11:07.112 :: ERROR at
> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
> code.
>
> 2022-08-18 09:11:07.112 :: pkgresult =
> exec_script(pkg_config_script, args, "value")
> 2022-08-18 09:11:07.113 :: ^--
>
> 2022-08-18 09:11:07.113 :: Current dir:
> /root/snaps/snap-from-source/parts/chromium/build/out/Release/
> 2022-08-18 09:11:07.113 :: Command: python3
> /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
> -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
>
> 2022-08-18 09:11:07.113 :: Returned 1.
>
> 2022-08-18 09:11:07.113 :: stderr:
>
> 2022-08-18 09:11:07.113 ::
>
> 2022-08-18 09:11:07.113 :: Could not run pkg-config.
>
> 2022-08-18 09:11:07.113 ::
>
> 2022-08-18 09:11:07.113 :: See
> //third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
> 2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
>
> 2022-08-18 09:11:07.113 :: ^--
>
> 2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file
> to be included.
> 2022-08-18 09:11:07.114 ::
> "//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan",
> 2022-08-18 09:11:07.114 ::
> ^---
> 2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with
> code 1.
> Review the scriptlet and make sure it's correct.
>
> I verified that the pkg-config utility is installed in the container;
> I can only suspect that this error is related to switching to the
> core22 gnome extension. I am open to suggestions.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986925/+subscriptions
>
>
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1986925
Title:
[snap] Trying to build chromium snap for core22: pkg-config fails.
Status in chromium-browser package in Ubuntu:
New
Bug description:
I checked out the "dev" branch of chromium-browser from launchpad and
did what seemed necessary to update snapcraft.yaml to build with
snapcraft 7 for core22. The only change of any significance was to
change the extension from "gnome-3-38" to the core22-specific "gnome"
extension. I started the build and it ran for quite some time (in a
persistent 22.04 LXD container) until:
2022-08-18 09:11:00.869 :: + OUT=out/Release
2022-08-18 09:11:00.869 :: + mkdir -p out/Release
2022-08-18 09:11:00.888 :: + cp
/root/snaps/snap-from-source/stage/build/args.gn out/Release/
2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
[Desktop-packages] [Bug 1970148] Re: Brave & Chrome browsers freezes on download and print to pdf
I can confirm the issue and that xdg-desktop-portal-gnome solved the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1970148 Title: Brave & Chrome browsers freezes on download and print to pdf Status in chromium-browser package in Ubuntu: Invalid Bug description: Whenever any file is downloaded, the browser will freeze. Download files, from any page does not work. Same issue with Firefox. Similarly, the browser will freeze when a page is printed to pdf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970148/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970081] Re: The background image of the login window cannot be changed
Here's the supposedly final solution: (sudo) apt-get install lightdm-settings slick-greeter and then killall -HUP mate-panel "Login Window" will automagically appear in the "Administration" section of "Control Center". Thanks @ubucolors for confirming it was a matter of something no more available. ** Attachment added: "The Control Center as expected" https://bugs.launchpad.net/ubuntu-mate/+bug/1970081/+attachment/5609683/+files/Screenshot%20at%202022-08-18%2018-39-14.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1970081 Title: The background image of the login window cannot be changed Status in Ubuntu MATE: New Status in arctica-greeter package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 20.04 Mate to 22.04 Mate, my custom wallpaper was replaced with the default one. I can make a change via the menu, but it stays with the default background image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.
> but that appears to be because this newer gnome does not supply such
an executable; there is no "pkg-config" under
/snap/gnome-42-2204/current/usr/bin/, as I assume there must have been
under gnome-3-38.
Oh, so this time pkg-config in build-packages could solve it? Probably
you will have to remove the pkg_config line from args.gn, though.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1986925
Title:
[snap] Trying to build chromium snap for core22: pkg-config fails.
Status in chromium-browser package in Ubuntu:
New
Bug description:
I checked out the "dev" branch of chromium-browser from launchpad and
did what seemed necessary to update snapcraft.yaml to build with
snapcraft 7 for core22. The only change of any significance was to
change the extension from "gnome-3-38" to the core22-specific "gnome"
extension. I started the build and it ran for quite some time (in a
persistent 22.04 LXD container) until:
2022-08-18 09:11:00.869 :: + OUT=out/Release
2022-08-18 09:11:00.869 :: + mkdir -p out/Release
2022-08-18 09:11:00.888 :: + cp
/root/snaps/snap-from-source/stage/build/args.gn out/Release/
2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
2022-08-18 09:11:00.935 :: + cd -
2022-08-18 09:11:00.935 :: /root/snaps/snap-from-source/parts/chromium/build
2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
2022-08-18 09:11:07.112 :: ERROR at
//build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit code.
2022-08-18 09:11:07.112 :: pkgresult = exec_script(pkg_config_script,
args, "value")
2022-08-18 09:11:07.113 :: ^--
2022-08-18 09:11:07.113 :: Current dir:
/root/snaps/snap-from-source/parts/chromium/build/out/Release/
2022-08-18 09:11:07.113 :: Command: python3
/root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
-p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
2022-08-18 09:11:07.113 :: Returned 1.
2022-08-18 09:11:07.113 :: stderr:
2022-08-18 09:11:07.113 ::
2022-08-18 09:11:07.113 :: Could not run pkg-config.
2022-08-18 09:11:07.113 ::
2022-08-18 09:11:07.113 :: See
//third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
2022-08-18 09:11:07.113 :: ^--
2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file to be
included.
2022-08-18 09:11:07.114 ::
"//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan",
2022-08-18 09:11:07.114 ::
^---
2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with code
1.
Review the scriptlet and make sure it's correct.
I verified that the pkg-config utility is installed in the container;
I can only suspect that this error is related to switching to the
core22 gnome extension. I am open to suggestions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986925/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1595538] Re: Wrong packages sugestions
This still happens in kinetic packages, and this is not exclusive of libreoffice-l10n-pt-br (all libreoffice-l10n-* packages should be reviewed). FYI, hunspell-dictionary-pt-br is now hunspell-pt-br and myspell- dictionary-pt-br is now myspell-pt-br (I didn't check about the rest). This issue still exists upstream (Debian), and should probably be reported and solved there. -- 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/1595538 Title: Wrong packages sugestions Status in libreoffice package in Ubuntu: Confirmed Bug description: The package libreoffice-l10n-pt-br (for Brazilian Portuguese) for Xenial defines this packages as suggestions for installation: hunspell-dictionary-pt-br | myspell-dictionary-pt-br hyphen-pt-br libreoffice-grammarcheck-pt-br libreoffice-help-pt-br mythes-pt-br The problem is: some of this packages don't exist on repository: libreoffice-grammarcheck-pt-br and mythes-pt-br don't exist at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1595538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1595538] Re: Wrong packages sugestions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- 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/1595538 Title: Wrong packages sugestions Status in libreoffice package in Ubuntu: Confirmed Bug description: The package libreoffice-l10n-pt-br (for Brazilian Portuguese) for Xenial defines this packages as suggestions for installation: hunspell-dictionary-pt-br | myspell-dictionary-pt-br hyphen-pt-br libreoffice-grammarcheck-pt-br libreoffice-help-pt-br mythes-pt-br The problem is: some of this packages don't exist on repository: libreoffice-grammarcheck-pt-br and mythes-pt-br don't exist at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1595538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986979] Re: Ubuntu 22.04 English input language duplicates twice when switching input language
*** This bug is a duplicate of bug 1956916 *** https://bugs.launchpad.net/bugs/1956916 Thanks for your report. Try to switch layout using +Space instead. Marking this bug as a duplicate. ** This bug has been marked a duplicate of bug 1956916 Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1986979 Title: Ubuntu 22.04 English input language duplicates twice when switching input language Status in gnome-control-center package in Ubuntu: New Bug description: I have only two input languages and I used Gnome Tweak tools to make alt+shift switching input languages. But when I cycle through them - I get English language selected twice. I did many tests and it can not be a coincidence or misclick. Pattern repeats many times. `asdas dasdas фвівфі adsasd dsasda Фівфів adsdas Adsasdas Фівфівф sdasad dasdas вфівфі asdasd Adsasdas вфівфі' See? I typed it just one time, it is impossible that I failed to switch to English 5 times in a row. There is got to be some bug or what? Did anybody encounter this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1986979/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986979] [NEW] Ubuntu 22.04 English input language duplicates twice when switching input language
Public bug reported: I have only two input languages and I used Gnome Tweak tools to make alt+shift switching input languages. But when I cycle through them - I get English language selected twice. I did many tests and it can not be a coincidence or misclick. Pattern repeats many times. `asdas dasdas фвівфі adsasd dsasda Фівфів adsdas Adsasdas Фівфівф sdasad dasdas вфівфі asdasd Adsasdas вфівфі' See? I typed it just one time, it is impossible that I failed to switch to English 5 times in a row. There is got to be some bug or what? Did anybody encounter this? ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1986979 Title: Ubuntu 22.04 English input language duplicates twice when switching input language Status in gnome-control-center package in Ubuntu: New Bug description: I have only two input languages and I used Gnome Tweak tools to make alt+shift switching input languages. But when I cycle through them - I get English language selected twice. I did many tests and it can not be a coincidence or misclick. Pattern repeats many times. `asdas dasdas фвівфі adsasd dsasda Фівфів adsdas Adsasdas Фівфівф sdasad dasdas вфівфі asdasd Adsasdas вфівфі' See? I typed it just one time, it is impossible that I failed to switch to English 5 times in a row. There is got to be some bug or what? Did anybody encounter this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1986979/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1979919] Re: package firefox 101.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: el subproceso nuevo paquete firefox script pre-installation devolvió el código de salida
Relevant logging from DpkgTerminalLog.txt: error: cannot perform the following tasks: - Descargar snap "firefox" (1443) del canal "stable" (unexpected EOF) That looks like a temporary network failure. Can you try reinstalling firefox? sudo apt reinstall firefox ** Changed in: firefox (Ubuntu) Status: Confirmed => Incomplete -- 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/1979919 Title: package firefox 101.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: el subproceso nuevo paquete firefox script pre- installation devolvió el código de salida de error 1 Status in firefox package in Ubuntu: Incomplete Bug description: Package stopped installing when upgrading from 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 101.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-51.58~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-51-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: arturo 1425 F pulseaudio /dev/snd/controlC0: arturo 1425 F pulseaudio BuildID: 20220608170832 CasperMD5CheckResult: unknown Channel: Unavailable Date: Sun Jun 26 15:24:06 2022 ErrorMessage: el subproceso nuevo paquete firefox script pre-installation devolvió el código de salida de error 1 ForcedLayersAccel: False InstallationDate: Installed on 2022-01-02 (174 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IpRoute: default via 192.168.0.1 dev enp2s0 proto dhcp metric 100 169.254.0.0/16 dev enp2s0 scope link metric 1000 192.168.0.0/24 dev enp2s0 proto kernel scope link src 192.168.0.104 metric 100 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.5 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 101.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: el subproceso nuevo paquete firefox script pre-installation devolvió el código de salida de error 1 UpgradeStatus: Upgraded to jammy on 2022-06-26 (0 days ago) dmi.bios.date: 12/04/2019 dmi.bios.release: 1.16 dmi.bios.vendor: LENOVO dmi.bios.version: 8UCN16WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15AST dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvr8UCN16WW:bd12/04/2019:br1.16:efr1.16:svnLENOVO:pn81D6:pvrLenovoideapad330-15AST:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15AST:skuLENOVO_MT_81D6_BU_idea_FM_ideapad330-15AST: dmi.product.family: ideapad 330-15AST dmi.product.name: 81D6 dmi.product.sku: LENOVO_MT_81D6_BU_idea_FM_ideapad 330-15AST dmi.product.version: Lenovo ideapad 330-15AST dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1979919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 511670] Re: Gedit displays shadow on top of edit window in fullscreen mode
This issue was closed upstream on 2010/01/24 as "RESOLVED WONTFIX" and refers to a very old version of gedit. After a review of outstanding '100 Papercuts' issues I'm closing this as it is no longer useful to leave this issue open. ** Changed in: gedit (Ubuntu) Status: Triaged => Invalid ** Changed in: hundredpapercuts Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/511670 Title: Gedit displays shadow on top of edit window in fullscreen mode Status in gedit: Won't Fix Status in One Hundred Papercuts: Invalid Status in gedit package in Ubuntu: Invalid Bug description: Binary package hint: gedit When in fullscreen mode, the top line of the editor has a shadow on top of it making it difficult to read. Steps to reproduce. 1. Open Gedit 2. Press F11 to go to fullscreen mode. Actual result: There is a shadow on the top line of text. Expected result: All text should be unobscured. Reproducibility: Always To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/511670/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986415] Re: package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
>From DpkgTerminalLog.txt: error: cannot perform the following tasks: - Download snap "firefox" (1635) from channel "stable" (download too slow: 2170.17 bytes/sec) This sounds like a transient network error, unless you are on a very slow connection. Can you try reinstalling firefox? sudo apt reinstall firefox ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- 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/1986415 Title: package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 Status in firefox package in Ubuntu: Incomplete Bug description: driver issues,,, i also cant launch genymotion ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox (not installed) ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: firefox:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Aug 8 00:23:36 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-16 (27 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.5 SourcePackage: firefox Title: package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1986415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1985987] Re: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: o subprocesso do pacote firefox, novo script pre-installation retornou erro do status de s
DpkgTerminalLog.txt has this weird Gtk warning that I've never seen before: cache version is different 1 != 2 Not sure what might have caused this. I would advise to try reinstalling firefox: sudo apt reinstall firefox ** 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/1985987 Title: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: o subprocesso do pacote firefox, novo script pre- installation retornou erro do status de saída 1 Status in firefox package in Ubuntu: Invalid Bug description: Firefox with installation problems. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 103.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: alexandre 27846 F pulseaudio /dev/snd/controlC0: alexandre 27846 F pulseaudio /dev/snd/controlC1: alexandre 27846 F pulseaudio BuildID: 20220718155818 CasperMD5CheckResult: unknown Channel: Unavailable Date: Thu Aug 11 22:28:31 2022 ErrorMessage: o subprocesso do pacote firefox, novo script pre-installation retornou erro do status de saída 1 ForcedLayersAccel: False IpRoute: default via 192.168.0.1 dev enp3s0 proto dhcp metric 100 169.254.0.0/16 dev enp3s0 scope link metric 1000 192.168.0.0/24 dev enp3s0 proto kernel scope link src 192.168.0.80 metric 100 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: o subprocesso do pacote firefox, novo script pre-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2007 dmi.bios.release: 8.10 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0208 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5LD2-X dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: Rev 1.xx dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0208:bd06/01/2007:br8.10:svnSystemmanufacturer:pnSystemProductName:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5LD2-X:rvrRevx.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx: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: Rev 1.xx dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1985987/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986468] Re: right click on icon does not always show bookmarks
Other pictures, showing both states of right click on Nautilus icon. One might think that the whole list should be shown while Nautilus is *not* launched ( since once launched that same list sits in its side pane. ) ** Attachment added: "right click on nautilus icon, when launched or not." https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1986468/+attachment/5609673/+files/nautilus_liste_signets_clic_droit.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1986468 Title: right click on icon does not always show bookmarks Status in nautilus package in Ubuntu: New Bug description: Hi, Ubuntu 22.04 here. A right click on Nautilus icon ( in the dock ) does not always show the list of bookmarks ( automatic and manually added ). Nautilus has to be already launched and running in order to show that list. This list of « shortcuts » was ago always accessible on right click - in Unity. It's a very convenient list of shortcuts, non-intrusive, calm on the eyes, and fast. On Xorg I may be able to launch Nautilus as a minimized window, using xdotools or wmctrl or devilspie. On Wayland I don't know how to do that : starting Nautilus as a minimized window with my session might be a workaround for that missing list. But ideally an option for Nautilus to start minimized sounds cleaner ( but options like -u or --start-minimized are not offered by Nautilus afaik ). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1986468/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 602265] Re: The defaut firefox bookmarks could do with updating.
Following a review of '100 Papercuts' bug reports I conclude that as Firefox is now a snap package provided by Mozilla in Ubuntu 22.04 (and other releases in due course) then bookmarks will be as provided by Mozilla and not by Ubuntu. ** Changed in: hundredpapercuts Status: Confirmed => Won't Fix -- 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/602265 Title: The defaut firefox bookmarks could do with updating. Status in One Hundred Papercuts: Won't Fix Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Following a chat with the mozilla team, Chrisccoulson has ask me to raise a bug report to include this shortlist. My suggestions, in no particular order are:- http://ubuntuforums.org/ https://help.ubuntu.com/community/GraphicalInstall https://help.ubuntu.com/community http://www.ubuntu.com/support http://ubuntuguide.org/ http://gnome-look.org/ http://kde-look.org http://medibuntu.org/ https://help.ubuntu.com/community/RestrictedFormats http://www.psychocats.net/ubuntu/ I think it would be good to include the link to ubuntuforums.org on the bookmarks toolbar. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.3+nobinonly-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.34-5.14-generic 2.6.34 Uname: Linux 2.6.34-5-generic x86_64 Architecture: amd64 Date: Tue Jul 6 13:30:21 2010 FirefoxPackages: firefox 3.6.3+nobinonly-0ubuntu4 firefox-gnome-support 3.6.3+nobinonly-0ubuntu4 firefox-branding 3.6.3+nobinonly-0ubuntu4 abroswer N/A abrowser-branding N/A LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100605) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/602265/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1985137] Re: Millions of syslog messages about: Creating shared memory in /dev/shm/.org.chromium.Chromium failed: Too many open files (24)
There's an old upstream bug report with similar symptoms (https://bugs.chromium.org/p/chromium/issues/detail?id=351897), but it hasn't seen any recent activity. I wonder whether this could be caused by an extension maybe? Can you try disabling all your extensions, and see if this alleviates the problem? ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1985137 Title: Millions of syslog messages about: Creating shared memory in /dev/shm/.org.chromium.Chromium failed: Too many open files (24) Status in chromium-browser package in Ubuntu: Incomplete Bug description: My /var/log/syslog file is 35 GB in size. 96234480/192463600 (50%) lines contain something like that: Aug 8 15:45:34 compiz[8153]: [8153:0100/00.390316:ERROR:platform_shared_memory_region_posix.cc(250)] Creating shared memory in /dev/shm/.org.chromium.Chromium.wRKl7F failed: Too many open files (24) Aug 8 15:45:34 compiz[8153]: [8153:0100/00.390320:ERROR:command_buffer_proxy_impl.cc(93)] ContextResult::kFatalFailure: AllocateAndMapSharedMemory failed Aug 8 15:45:34 compiz[8153]: [8153:0100/00.390338:ERROR:platform_shared_memory_region_posix.cc(250)] Creating shared memory in /dev/shm/.org.chromium.Chromium.SRkCeH failed: Too many open files (24) Aug 8 15:45:34 compiz[8153]: [8153:0100/00.390342:ERROR:command_buffer_proxy_impl.cc(93)] ContextResult::kFatalFailure: AllocateAndMapSharedMemory failed ProblemType: Bug DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.2ppa8 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Aug 11 18:09:15 2022 InstallationDate: Installed on 2022-03-20 (144 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. Snap: chromium 104.0.5112.79 (latest/stable) Snap.Changes: keine Änderungen gefunden SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to jammy on 2022-04-14 (119 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1985137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984132] Re: chromium-browser snap for armv7 does not read from .config/chromium-flags.conf
The file ~/.config/chromium-flags.conf isn't read by the snap, so this won't work on any architecture. However you can use ~/.chromium-browser.init for that purpose (that's for compatibility with the old deb package). ** Changed in: chromium-browser (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1984132 Title: chromium-browser snap for armv7 does not read from .config/chromium- flags.conf Status in chromium-browser package in Ubuntu: Won't Fix Bug description: Running Ubuntu 22.04 LTS and the chromium-browser snap on ARMv7 version 104.0.5112.79. Added --ozone-platform-hint=auto to .config/chromium-flags.conf Start the chromium browser and it expects X11 components. Manually starting chromium-browser with --ozone-platform=wayland works. On ARMv8/arm64 this works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1984132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986510] Re: No settings options for "Dock" under setting>>appearance
** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1986510 Title: No settings options for "Dock" under setting>>appearance Status in gnome-control-center package in Ubuntu: Invalid Bug description: There are no options for customizing the Dock under settings>>appearance. Even withe gnome-tweaks installed, the options don't show up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Aug 15 11:01:15 2022 InstallationDate: Installed on 2020-02-03 (924 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1986510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1108977] Re: "Videos" is a very confusing name for a video player
The upstream issue was closed on 2014-01-06 as "RESOLVED NOTABUG" and with no further discussion for over eight years I'm closing this after reviewing the outstanding '100 Papercuts' bug reports. ** Changed in: totem (Ubuntu) Status: Confirmed => Invalid ** Changed in: hundredpapercuts Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1108977 Title: "Videos" is a very confusing name for a video player Status in One Hundred Papercuts: Won't Fix Status in Totem: Invalid Status in totem package in Ubuntu: Invalid Bug description: Ubuntu Ringtail daily 20130128 1. Right-click on a video file in the file manager. 2. After opening the file, choose "Help" > "About". What you see: 1. "Open With Videos" 2. "Videos" "Videos" "Totem Website". What's wrong with this: 1. Open a video with videos? That doesn't make any sense. I have a Videos folder, but this video is not in that folder. 2. The window is titled "About Videos", but doesn't tell me anything about videos. And then a wild Totem appears. This is a regression: In Ubuntu 12.10 and earlier, the program was called "Movie Player", which was pretty accurate. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1108977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.
Just deleting that line seemed to allow the build to progress further, but now I have a slew of errors; I'll post a snippet here, then must run off but will be back in a bit: 2022-08-18 14:42:14.617 :: In file included from ../../third_party/angle/src/gpu_info_util/SystemInfo_vulkan.cpp:10: 2022-08-18 14:42:14.617 :: In file included from ../../third_party/angle/src/gpu_info_util/SystemInfo_vulkan.h:12: 2022-08-18 14:42:14.617 :: In file included from ../../third_party/angle/src/common/vulkan/vulkan_icd.h:15: 2022-08-18 14:42:14.617 :: In file included from ../../third_party/angle/src/common/vulkan/vk_headers.h:14: 2022-08-18 14:42:14.617 :: In file included from ../../third_party/angle/src/third_party/volk/volk.h:50: 2022-08-18 14:42:14.617 :: In file included from ../../third_party/vulkan-deps/vulkan-headers/src/include/vulkan/vulkan.h:41: 2022-08-18 14:42:14.617 :: In file included from ../../third_party/wayland/src/src/wayland-client.h:40: 2022-08-18 14:42:14.617 :: /usr/include/wayland-client-protocol.h:1038:13: error: use of undeclared identifier 'wl_proxy_marshal_flags' 2022-08-18 14:42:14.618 :: callback = wl_proxy_marshal_flags((struct wl_proxy *) wl_display, 2022-08-18 14:42:14.618 ::^ 2022-08-18 14:42:14.618 :: /usr/include/wayland-client-protocol.h:1062:13: error: use of undeclared identifier 'wl_proxy_marshal_flags' 2022-08-18 14:42:14.618 :: registry = wl_proxy_marshal_flags((struct wl_proxy *) wl_display, 2022-08-18 14:42:14.618 ::^ 2022-08-18 14:42:14.618 :: /usr/include/wayland-client-protocol.h:1175:7: error: use of undeclared identifier 'wl_proxy_marshal_flags' 2022-08-18 14:42:14.618 :: id = wl_proxy_marshal_flags((struct wl_proxy *) wl_registry, 2022-08-18 14:42:14.618 :: ^ 2022-08-18 14:42:14.618 :: /usr/include/wayland-client-protocol.h:1291:7: error: use of undeclared identifier 'wl_proxy_marshal_flags' 2022-08-18 14:42:14.618 :: id = wl_proxy_marshal_flags((struct wl_proxy *) wl_compositor, 2022-08-18 14:42:14.618 :: ^ 2022-08-18 14:42:14.618 :: /usr/include/wayland-client-protocol.h:1307:7: error: use of undeclared identifier 'wl_proxy_marshal_flags' 2022-08-18 14:42:14.618 :: id = wl_proxy_marshal_flags((struct wl_proxy *) wl_compositor,
[Desktop-packages] [Bug 1986922] Re: snapcraft build fails on second run as "ln -s libdrm.pc libdrm-uninstalled.pc" already done
That workaround might not be necessary any longer (see the original commit that introduced it: https://git.launchpad.net/~chromium- team/chromium-browser/+git/snap-from- source/commit/?id=6aacaab9c675b0f099c8fa4d0c783b1c7b8d0c15). Can you try removing it altogether? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1986922 Title: snapcraft build fails on second run as "ln -s libdrm.pc libdrm- uninstalled.pc" already done Status in chromium-browser package in Ubuntu: New Bug description: I'm trying to migrate the chromium browser snapcraft.yaml file to core22 and Snapcraft 7 and, after a build error on the first test (more on that later), I cleaned and re-ran the build to make sure the build error was reproducible, and got: ... big snip ... 2022-08-18 08:50:45.224 :: + OUT=out/Release 2022-08-18 08:50:45.224 :: + mkdir -p out/Release 2022-08-18 08:50:45.243 :: + cp /root/snaps/snap-from-source/stage/build/args.gn out/Release/ 2022-08-18 08:50:45.259 :: + '[' amd64 = armhf ']' 2022-08-18 08:50:45.260 :: + '[' amd64 = armhf ']' 2022-08-18 08:50:45.260 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig 2022-08-18 08:50:45.260 :: + ln -s libdrm.pc libdrm-uninstalled.pc 2022-08-18 08:50:45.269 :: ln: failed to create symbolic link 'libdrm-uninstalled.pc': File exists 2022-08-18 08:50:45.431 'override-build' in part 'chromium' failed with code 1. Review the scriptlet and make sure it's correct. Naturally, since that symlink had been created during the first run (in a persistent 22.04 LXD container), it was still there for the second run. Operations like that should be idempotent so one can run multiple builds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986922/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.
I made that change, it still failed:
2022-08-18 14:31:54.099 :: Current dir:
/root/snaps/snap-from-source/parts/chromium/build/out/Release/
2022-08-18 14:31:54.099 :: Command: python3
/root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
-p /snap/gnome-42-2204/current/usr/bin/pkg-config x11-xcb
2022-08-18 14:31:54.099 :: Returned 1.
2022-08-18 14:31:54.099 :: stderr:
2022-08-18 14:31:54.099 ::
2022-08-18 14:31:54.099 :: Could not run pkg-config.
but that appears to be because this newer gnome does not supply such an
executable; there is no "pkg-config" under
/snap/gnome-42-2204/current/usr/bin/, as I assume there must have been
under gnome-3-38. What about just deleting that line from build/args.gn,
and assuming pkg-config is run from the standard package?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1986925
Title:
[snap] Trying to build chromium snap for core22: pkg-config fails.
Status in chromium-browser package in Ubuntu:
New
Bug description:
I checked out the "dev" branch of chromium-browser from launchpad and
did what seemed necessary to update snapcraft.yaml to build with
snapcraft 7 for core22. The only change of any significance was to
change the extension from "gnome-3-38" to the core22-specific "gnome"
extension. I started the build and it ran for quite some time (in a
persistent 22.04 LXD container) until:
2022-08-18 09:11:00.869 :: + OUT=out/Release
2022-08-18 09:11:00.869 :: + mkdir -p out/Release
2022-08-18 09:11:00.888 :: + cp
/root/snaps/snap-from-source/stage/build/args.gn out/Release/
2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
2022-08-18 09:11:00.935 :: + cd -
2022-08-18 09:11:00.935 :: /root/snaps/snap-from-source/parts/chromium/build
2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
2022-08-18 09:11:07.112 :: ERROR at
//build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit code.
2022-08-18 09:11:07.112 :: pkgresult = exec_script(pkg_config_script,
args, "value")
2022-08-18 09:11:07.113 :: ^--
2022-08-18 09:11:07.113 :: Current dir:
/root/snaps/snap-from-source/parts/chromium/build/out/Release/
2022-08-18 09:11:07.113 :: Command: python3
/root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
-p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
2022-08-18 09:11:07.113 :: Returned 1.
2022-08-18 09:11:07.113 :: stderr:
2022-08-18 09:11:07.113 ::
2022-08-18 09:11:07.113 :: Could not run pkg-config.
2022-08-18 09:11:07.113 ::
2022-08-18 09:11:07.113 :: See
//third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
2022-08-18 09:11:07.113 ::
[Desktop-packages] [Bug 1574035] Re: Menu duplicates in GNOME apps
Removing 'Papercuts' task as Unity is no longer the default Ubuntu desktop. ** No longer affects: hundredpapercuts -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to baobab in Ubuntu. https://bugs.launchpad.net/bugs/1574035 Title: Menu duplicates in GNOME apps Status in baobab package in Ubuntu: New Status in cheese package in Ubuntu: New Status in gnome-calculator package in Ubuntu: New Status in gnome-disk-utility package in Ubuntu: New Status in gnome-screenshot package in Ubuntu: New Status in gnome-software package in Ubuntu: New Status in gnome-sudoku package in Ubuntu: New Status in gnome-system-monitor package in Ubuntu: New Status in yelp package in Ubuntu: New Bug description: In the window header, there are two menus with identical contents: "Ubuntu Software" and "App". Ubuntu Xenial Xerus. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 23 18:43:18 2016 InstallationDate: Installed on 2014-08-22 (609 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: gnome-software UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/1574035/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986922] Re: snapcraft build fails on second run as "ln -s libdrm.pc libdrm-uninstalled.pc" already done
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1986922 Title: snapcraft build fails on second run as "ln -s libdrm.pc libdrm- uninstalled.pc" already done Status in chromium-browser package in Ubuntu: New Bug description: I'm trying to migrate the chromium browser snapcraft.yaml file to core22 and Snapcraft 7 and, after a build error on the first test (more on that later), I cleaned and re-ran the build to make sure the build error was reproducible, and got: ... big snip ... 2022-08-18 08:50:45.224 :: + OUT=out/Release 2022-08-18 08:50:45.224 :: + mkdir -p out/Release 2022-08-18 08:50:45.243 :: + cp /root/snaps/snap-from-source/stage/build/args.gn out/Release/ 2022-08-18 08:50:45.259 :: + '[' amd64 = armhf ']' 2022-08-18 08:50:45.260 :: + '[' amd64 = armhf ']' 2022-08-18 08:50:45.260 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig 2022-08-18 08:50:45.260 :: + ln -s libdrm.pc libdrm-uninstalled.pc 2022-08-18 08:50:45.269 :: ln: failed to create symbolic link 'libdrm-uninstalled.pc': File exists 2022-08-18 08:50:45.431 'override-build' in part 'chromium' failed with code 1. Review the scriptlet and make sure it's correct. Naturally, since that symlink had been created during the first run (in a persistent 22.04 LXD container), it was still there for the second run. Operations like that should be idempotent so one can run multiple builds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986922/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.
Yes, you will need to update build/args.gn where there's a hardcoded
path to the pkg-config binary (https://git.launchpad.net/~chromium-
team/chromium-browser/+git/snap-from-
source/tree/build/args.gn?h=stable#n39).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1986925
Title:
[snap] Trying to build chromium snap for core22: pkg-config fails.
Status in chromium-browser package in Ubuntu:
New
Bug description:
I checked out the "dev" branch of chromium-browser from launchpad and
did what seemed necessary to update snapcraft.yaml to build with
snapcraft 7 for core22. The only change of any significance was to
change the extension from "gnome-3-38" to the core22-specific "gnome"
extension. I started the build and it ran for quite some time (in a
persistent 22.04 LXD container) until:
2022-08-18 09:11:00.869 :: + OUT=out/Release
2022-08-18 09:11:00.869 :: + mkdir -p out/Release
2022-08-18 09:11:00.888 :: + cp
/root/snaps/snap-from-source/stage/build/args.gn out/Release/
2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
2022-08-18 09:11:00.935 :: + cd -
2022-08-18 09:11:00.935 :: /root/snaps/snap-from-source/parts/chromium/build
2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
2022-08-18 09:11:07.112 :: ERROR at
//build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit code.
2022-08-18 09:11:07.112 :: pkgresult = exec_script(pkg_config_script,
args, "value")
2022-08-18 09:11:07.113 :: ^--
2022-08-18 09:11:07.113 :: Current dir:
/root/snaps/snap-from-source/parts/chromium/build/out/Release/
2022-08-18 09:11:07.113 :: Command: python3
/root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
-p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
2022-08-18 09:11:07.113 :: Returned 1.
2022-08-18 09:11:07.113 :: stderr:
2022-08-18 09:11:07.113 ::
2022-08-18 09:11:07.113 :: Could not run pkg-config.
2022-08-18 09:11:07.113 ::
2022-08-18 09:11:07.113 :: See
//third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
2022-08-18 09:11:07.113 :: ^--
2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file to be
included.
2022-08-18 09:11:07.114 ::
"//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan",
2022-08-18 09:11:07.114 ::
^---
2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with code
1.
Review the scriptlet and make sure it's correct.
I verified that the pkg-config utility is installed in the container;
I can only suspect that this error is related to switching to the
core22 gnome extension. I am open to suggestions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986925/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984233] Re: Please remove nautilus extensions incompatible with Nautilus 43
** Description changed: nautilus python 4.0~alpha is a major API update along with nautilus 43 which had a major API update. Please remove these extensions since they are currently incompatible with the Nautilus and nautilus-python versions we are including in Kinetic - eiciel -- Needs to be ported from GTK3 Debian maintainer thinks the package is not worth keeping without the extension https://salsa.debian.org/debian/eiciel/-/merge_requests/2 - folder-color -- Needs to be ported from GTK3 https://github.com/costales/folder-color/issues/17 Ubuntu-specific package - nautilus-dropbox -- Needs to be ported from GTK3 https://github.com/dropbox/nautilus-dropbox/issues/101 - nautilus-filename-repairer -- Needs to be ported from GTK3 - nautilus-ideviceinfo -- Needs to be ported from GTK3 Ubuntu-specific package - nautilus-image-converter -- Needs to be ported from GTK3 Debian removal bug filed. Unmaintained in Debian or upstream + - nautilus-share -- Needs to be ported from GTK3 + - nautilus-wipe -- Needs to be ported from GTK3 - seahorse-nautilus -- Needs to be ported from GTK3 Transition tracker -- We are going to try to fix several of the other affected source packages (not listed above) to either drop their Nautilus extension or port them to work with Nautilus 43. https://people.canonical.com/~ubuntu-archive/transitions/html/auto- nautilus.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/1984233 Title: Please remove nautilus extensions incompatible with Nautilus 43 Status in eiciel package in Ubuntu: Fix Released Status in folder-color package in Ubuntu: Fix Released Status in nautilus-dropbox package in Ubuntu: Fix Released Status in nautilus-filename-repairer package in Ubuntu: Fix Released Status in nautilus-ideviceinfo package in Ubuntu: Fix Released Status in nautilus-image-converter package in Ubuntu: Fix Released Status in nautilus-share package in Ubuntu: New Status in nautilus-wipe package in Ubuntu: Fix Released Status in seahorse-nautilus package in Ubuntu: Fix Released Bug description: nautilus python 4.0~alpha is a major API update along with nautilus 43 which had a major API update. Please remove these extensions since they are currently incompatible with the Nautilus and nautilus-python versions we are including in Kinetic - eiciel -- Needs to be ported from GTK3 Debian maintainer thinks the package is not worth keeping without the extension https://salsa.debian.org/debian/eiciel/-/merge_requests/2 - folder-color -- Needs to be ported from GTK3 https://github.com/costales/folder-color/issues/17 Ubuntu-specific package - nautilus-dropbox -- Needs to be ported from GTK3 https://github.com/dropbox/nautilus-dropbox/issues/101 - nautilus-filename-repairer -- Needs to be ported from GTK3 - nautilus-ideviceinfo -- Needs to be ported from GTK3 Ubuntu-specific package - nautilus-image-converter -- Needs to be ported from GTK3 Debian removal bug filed. Unmaintained in Debian or upstream - nautilus-share -- Needs to be ported from GTK3 - nautilus-wipe -- Needs to be ported from GTK3 - seahorse-nautilus -- Needs to be ported from GTK3 Transition tracker -- We are going to try to fix several of the other affected source packages (not listed above) to either drop their Nautilus extension or port them to work with Nautilus 43. https://people.canonical.com/~ubuntu-archive/transitions/html/auto- nautilus.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eiciel/+bug/1984233/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 18250] Re: file-roller's progress bar does not indicate amount of progress
** Changed in: hundredpapercuts Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/18250 Title: file-roller's progress bar does not indicate amount of progress Status in File Roller: Confirmed Status in One Hundred Papercuts: Triaged Status in file-roller package in Ubuntu: Triaged Bug description: I was putting together a .rar archive that was split up in 14mb snippets, and noticed that the progress bar does not indicate progress at all. It just indicates activity as of now, with a sort of rolling motion rather than a true progress bar. This is annoying because it won't give a ETA, nor a progress done percentage. http://bugzilla.gnome.org/show_bug.cgi?id=153281: http://bugzilla.gnome.org/show_bug.cgi?id=153281 To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/18250/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986922] Re: snapcraft build fails on second run as "ln -s libdrm.pc libdrm-uninstalled.pc" already done
Ah: build/args.gn:pkg_config = "/snap/gnome-3-38-2004/current/usr/bin/pkg- config" In my container, it's now /snap/gnome-42-2204; I'll change that and see what happens. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1986922 Title: snapcraft build fails on second run as "ln -s libdrm.pc libdrm- uninstalled.pc" already done Status in chromium-browser package in Ubuntu: New Bug description: I'm trying to migrate the chromium browser snapcraft.yaml file to core22 and Snapcraft 7 and, after a build error on the first test (more on that later), I cleaned and re-ran the build to make sure the build error was reproducible, and got: ... big snip ... 2022-08-18 08:50:45.224 :: + OUT=out/Release 2022-08-18 08:50:45.224 :: + mkdir -p out/Release 2022-08-18 08:50:45.243 :: + cp /root/snaps/snap-from-source/stage/build/args.gn out/Release/ 2022-08-18 08:50:45.259 :: + '[' amd64 = armhf ']' 2022-08-18 08:50:45.260 :: + '[' amd64 = armhf ']' 2022-08-18 08:50:45.260 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig 2022-08-18 08:50:45.260 :: + ln -s libdrm.pc libdrm-uninstalled.pc 2022-08-18 08:50:45.269 :: ln: failed to create symbolic link 'libdrm-uninstalled.pc': File exists 2022-08-18 08:50:45.431 'override-build' in part 'chromium' failed with code 1. Review the scriptlet and make sure it's correct. Naturally, since that symlink had been created during the first run (in a persistent 22.04 LXD container), it was still there for the second run. Operations like that should be idempotent so one can run multiple builds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986922/+subscriptions -- Mailing list: https://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 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.
OK, I'm trying that now, but I would be astonished if that was the solution
as pkg-config is already installed, either because I installed it manually
at some point, or maybe it was installed by an earlier snap, who knows? But
it's definitely there so adding it to "build-packages" should make no
difference.
On Thu, Aug 18, 2022 at 9:30 AM Nathan Teodosio <1986...@bugs.launchpad.net>
wrote:
> Thanks for the bug report, Robert.
>
> My first attempt would be adding a pkg-config line to the build-packages
> of chromium. Does it make sense to you? If yes, could you please try
> that?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1986925
>
> Title:
> [snap] Trying to build chromium snap for core22: pkg-config fails.
>
> Status in chromium-browser package in Ubuntu:
> New
>
> Bug description:
> I checked out the "dev" branch of chromium-browser from launchpad and
> did what seemed necessary to update snapcraft.yaml to build with
> snapcraft 7 for core22. The only change of any significance was to
> change the extension from "gnome-3-38" to the core22-specific "gnome"
> extension. I started the build and it ran for quite some time (in a
> persistent 22.04 LXD container) until:
>
> 2022-08-18 09:11:00.869 :: + OUT=out/Release
>
> 2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>
> 2022-08-18 09:11:00.888 :: + cp /root/snaps/snap-from-source/stage/build/
> args.gn out/Release/
> 2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
> 2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
> 2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>
> 2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>
> 2022-08-18 09:11:00.935 :: + cd -
>
> 2022-08-18 09:11:00.935 ::
> /root/snaps/snap-from-source/parts/chromium/build
>
> 2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
>
> 2022-08-18 09:11:07.112 :: ERROR at
> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
> code.
>
> 2022-08-18 09:11:07.112 :: pkgresult =
> exec_script(pkg_config_script, args, "value")
> 2022-08-18 09:11:07.113 :: ^--
>
> 2022-08-18 09:11:07.113 :: Current dir:
> /root/snaps/snap-from-source/parts/chromium/build/out/Release/
> 2022-08-18 09:11:07.113 :: Command: python3
> /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
> -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
>
> 2022-08-18 09:11:07.113 :: Returned 1.
>
> 2022-08-18 09:11:07.113 :: stderr:
>
> 2022-08-18 09:11:07.113 ::
>
> 2022-08-18 09:11:07.113 :: Could not run pkg-config.
>
> 2022-08-18 09:11:07.113 ::
>
> 2022-08-18 09:11:07.113 :: See
> //third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
> 2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
>
> 2022-08-18 09:11:07.113 :: ^--
>
> 2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file
> to be included.
> 2022-08-18 09:11:07.114 ::
> "//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan",
> 2022-08-18 09:11:07.114 ::
> ^---
> 2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with
> code 1.
> Review the scriptlet and make sure it's correct.
>
> I verified that the pkg-config utility is installed in the container;
> I can only suspect that this error is related to switching to the
> core22 gnome extension. I am open to suggestions.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986925/+subscriptions
>
>
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1986925
Title:
[snap] Trying to build chromium snap for core22: pkg-config fails.
Status in chromium-browser package in Ubuntu:
New
Bug description:
I checked out the "dev" branch of chromium-browser from launchpad and
did what seemed necessary to update snapcraft.yaml to build with
snapcraft 7 for core22. The only change of any significance was to
change the extension from "gnome-3-38" to the core22-specific "gnome"
extension. I started the build and it ran for quite some time (in a
persistent 22.04 LXD container) until:
2022-08-18 09:11:00.869 :: + OUT=out/Release
2022-08-18 09:11:00.869 :: + mkdir -p out/Release
2022-08-18 09:11:00.888 :: + cp
/root/snaps/snap-from-source/stage/build/args.gn out/Release/
2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.
Hang on, look at that hard-coded directory name: "/snap/gnome-3-38-2004".
Since the gnome extension under core 22 is named just "gnome", any
hardcoded names to the old extension should fail.
On Thu, Aug 18, 2022 at 10:15 AM Robert Day
wrote:
> Same result:
>
> 2022-08-18 14:13:31.315 :: + OUT=out/Release
>
> 2022-08-18 14:13:31.316 :: + mkdir -p out/Release
>
> 2022-08-18 14:13:31.335 :: + cp /root/snaps/snap-from-source/stage/build/
> args.gn out/Release/
> 2022-08-18 14:13:31.367 :: + '[' amd64 = armhf ']'
>
> 2022-08-18 14:13:31.367 :: + '[' amd64 = armhf ']'
>
> 2022-08-18 14:13:31.368 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>
> 2022-08-18 14:13:31.368 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>
> 2022-08-18 14:13:31.389 :: + cd -
>
> 2022-08-18 14:13:31.389 ::
> /root/snaps/snap-from-source/parts/chromium/build
>
> 2022-08-18 14:13:31.389 :: + out/Release/gn gen out/Release
>
> 2022-08-18 14:13:37.548 :: ERROR at
> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
> code.
>
> 2022-08-18 14:13:37.549 :: pkgresult = exec_script(pkg_config_script,
> args, "value")
> 2022-08-18 14:13:37.549 :: ^--
>
> 2022-08-18 14:13:37.549 :: Current dir:
> /root/snaps/snap-from-source/parts/chromium/build/out/Release/
> 2022-08-18 14:13:37.549 :: Command: python3
> /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
> -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
>
> 2022-08-18 14:13:37.549 :: Returned 1.
>
> 2022-08-18 14:13:37.549 :: stderr:
>
> 2022-08-18 14:13:37.549 ::
>
> 2022-08-18 14:13:37.550 :: Could not run pkg-config.
>
> 2022-08-18 14:13:37.550 ::
>
> 2022-08-18 14:13:37.550 :: See
> //third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
> 2022-08-18 14:13:37.550 :: pkg_config("x11-xcb") {
>
> 2022-08-18 14:13:37.550 :: ^--
>
> 2022-08-18 14:13:37.550 :: See //BUILD.gn:529:7: which caused the file to
> be included.
> 2022-08-18 14:13:37.550 ::
> "//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan",
> 2022-08-18 14:13:37.550 ::
> ^---
> 2022-08-18 14:13:37.782 'override-build' in part 'chromium' failed with
> code 1.
> Review the scriptlet and make sure it's correct.
>
> 2022-08-18 14:13:37.867 Traceback (most recent call last):
>
> 2022-08-18 14:13:37.867 File
> "/snap/snapcraft/8122/lib/python3.8/site-packages/snapcraft/parts/parts.py",
> line 170, in run
>
> 2022-08-18 14:13:37.867 aex.execute(action, stdout=stream,
> stderr=stream)
> 2022-08-18 14:13:37.867 File
> "/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/executor.py",
> line 301, in execute
>
> 2022-08-18 14:13:37.867 self._executor.execute(actions, stdout=stdout,
> stderr=stderr)
> 2022-08-18 14:13:37.867 File
> "/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/executor.py",
> line 126, in execute
>
> 2022-08-18 14:13:37.867 self._run_action(act, stdout=stdout,
> stderr=stderr)
> 2022-08-18 14:13:37.868 File
> "/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/executor.py",
> line 189, in _run_action
>
> 2022-08-18 14:13:37.868 handler.run_action(action, stdout=stdout,
> stderr=stderr)
> 2022-08-18 14:13:37.868 File
> "/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/part_handler.py",
> line 161, in run_action
>
> 2022-08-18 14:13:37.868 state = handler(step_info, stdout=stdout,
> stderr=stderr)
> 2022-08-18 14:13:37.868 File
> "/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/part_handler.py",
> line 297, in _run_build
>
> 2022-08-18 14:13:37.868 self._run_step(
>
> 2022-08-18 14:13:37.868 File
> "/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/part_handler.py",
> line 469, in _run_step
>
> 2022-08-18 14:13:37.868 step_handler.run_scriptlet(
>
> 2022-08-18 14:13:37.868 File
> "/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/step_handler.py",
> line 265, in run_scriptlet
>
> 2022-08-18 14:13:37.868 raise errors.ScriptletRunError(
>
> 2022-08-18 14:13:37.868 craft_parts.errors.ScriptletRunError:
> 'override-build' in part 'chromium' failed with code 1.
>
>
> 2022-08-18 14:13:37.869 Review the scriptlet and make sure it's correct.
>
> 2022-08-18 14:13:37.869 Full execution log:
> '/root/.cache/snapcraft/log/snapcraft-20220818-140941.486880.log'
>
>
&g
Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.
Same result:
2022-08-18 14:13:31.315 :: + OUT=out/Release
2022-08-18 14:13:31.316 :: + mkdir -p out/Release
2022-08-18 14:13:31.335 :: + cp /root/snaps/snap-from-source/stage/build/
args.gn out/Release/
2022-08-18 14:13:31.367 :: + '[' amd64 = armhf ']'
2022-08-18 14:13:31.367 :: + '[' amd64 = armhf ']'
2022-08-18 14:13:31.368 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
2022-08-18 14:13:31.368 :: + ln -s libdrm.pc libdrm-uninstalled.pc
2022-08-18 14:13:31.389 :: + cd -
2022-08-18 14:13:31.389 ::
/root/snaps/snap-from-source/parts/chromium/build
2022-08-18 14:13:31.389 :: + out/Release/gn gen out/Release
2022-08-18 14:13:37.548 :: ERROR at
//build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
code.
2022-08-18 14:13:37.549 :: pkgresult = exec_script(pkg_config_script,
args, "value")
2022-08-18 14:13:37.549 :: ^--
2022-08-18 14:13:37.549 :: Current dir:
/root/snaps/snap-from-source/parts/chromium/build/out/Release/
2022-08-18 14:13:37.549 :: Command: python3
/root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
-p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
2022-08-18 14:13:37.549 :: Returned 1.
2022-08-18 14:13:37.549 :: stderr:
2022-08-18 14:13:37.549 ::
2022-08-18 14:13:37.550 :: Could not run pkg-config.
2022-08-18 14:13:37.550 ::
2022-08-18 14:13:37.550 :: See
//third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
2022-08-18 14:13:37.550 :: pkg_config("x11-xcb") {
2022-08-18 14:13:37.550 :: ^--
2022-08-18 14:13:37.550 :: See //BUILD.gn:529:7: which caused the file to
be included.
2022-08-18 14:13:37.550 ::
"//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan",
2022-08-18 14:13:37.550 ::
^---
2022-08-18 14:13:37.782 'override-build' in part 'chromium' failed with
code 1.
Review the scriptlet and make sure it's correct.
2022-08-18 14:13:37.867 Traceback (most recent call last):
2022-08-18 14:13:37.867 File
"/snap/snapcraft/8122/lib/python3.8/site-packages/snapcraft/parts/parts.py",
line 170, in run
2022-08-18 14:13:37.867 aex.execute(action, stdout=stream,
stderr=stream)
2022-08-18 14:13:37.867 File
"/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/executor.py",
line 301, in execute
2022-08-18 14:13:37.867 self._executor.execute(actions, stdout=stdout,
stderr=stderr)
2022-08-18 14:13:37.867 File
"/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/executor.py",
line 126, in execute
2022-08-18 14:13:37.867 self._run_action(act, stdout=stdout,
stderr=stderr)
2022-08-18 14:13:37.868 File
"/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/executor.py",
line 189, in _run_action
2022-08-18 14:13:37.868 handler.run_action(action, stdout=stdout,
stderr=stderr)
2022-08-18 14:13:37.868 File
"/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/part_handler.py",
line 161, in run_action
2022-08-18 14:13:37.868 state = handler(step_info, stdout=stdout,
stderr=stderr)
2022-08-18 14:13:37.868 File
"/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/part_handler.py",
line 297, in _run_build
2022-08-18 14:13:37.868 self._run_step(
2022-08-18 14:13:37.868 File
"/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/part_handler.py",
line 469, in _run_step
2022-08-18 14:13:37.868 step_handler.run_scriptlet(
2022-08-18 14:13:37.868 File
"/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/step_handler.py",
line 265, in run_scriptlet
2022-08-18 14:13:37.868 raise errors.ScriptletRunError(
2022-08-18 14:13:37.868 craft_parts.errors.ScriptletRunError:
'override-build' in part 'chromium' failed with code 1.
2022-08-18 14:13:37.869 Review the scriptlet and make sure it's correct.
2022-08-18 14:13:37.869 Full execution log:
'/root/.cache/snapcraft/log/snapcraft-20220818-140941.486880.log'
I think pkg-config is being invoked, it's just failing based on what it's
being asked to do.
On Thu, Aug 18, 2022 at 10:11 AM Robert Day
wrote:
> OK, I'm trying that now, but I would be astonished if that was the
> solution as pkg-config is already installed, either because I installed it
> manually at some point, or maybe it was installed by an earlier snap, who
> knows? But it's definitely there so adding it to "build-packages" should
> make no difference.
>
> On Thu, Aug 18, 2022 at 9:30 AM Nathan Teodosio <
> 1986...@bugs.launchpad.net> wrote:
>
>> Thanks for the bug report, Robert.
>>
>> My first attempt would be adding a pkg-config line to the build-packages
>> of chromium. Does it make sense to you? If yes, could you please try
>> that?
>>
&
Re: [Desktop-packages] [Bug 1986510] Re: No settings options for "Dock" under setting>>appearance
This solved the problem. Thank you On Thu, Aug 18, 2022 at 4:11 PM Jeremy Bicha <1986...@bugs.launchpad.net> wrote: > Please run this command in a terminal: > > sudo apt install ubuntu-desktop > > Then log out and log back in. > > ** Changed in: gnome-control-center (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1986510 > > Title: > No settings options for "Dock" under setting>>appearance > > Status in gnome-control-center package in Ubuntu: > Incomplete > > Bug description: > There are no options for customizing the Dock under > settings>>appearance. > > Even withe gnome-tweaks installed, the options don't show up. > > ProblemType: Bug > DistroRelease: Ubuntu 22.04 > Package: ubuntu-release-upgrader-core 1:22.04.13 > ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 > Uname: Linux 5.15.0-46-generic x86_64 > NonfreeKernelModules: wl nvidia_modeset nvidia > ApportVersion: 2.20.11-0ubuntu82.1 > Architecture: amd64 > CasperMD5CheckResult: unknown > CrashDB: ubuntu > CurrentDesktop: ubuntu:GNOME > Date: Mon Aug 15 11:01:15 2022 > InstallationDate: Installed on 2020-02-03 (924 days ago) > InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > PackageArchitecture: all > SourcePackage: ubuntu-release-upgrader > Symptom: release-upgrade > UpgradeStatus: No upgrade log present (probably fresh install) > VarLogDistupgradeTermlog: > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1986510/+subscriptions > > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1986510 Title: No settings options for "Dock" under setting>>appearance Status in gnome-control-center package in Ubuntu: Incomplete Bug description: There are no options for customizing the Dock under settings>>appearance. Even withe gnome-tweaks installed, the options don't show up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Aug 15 11:01:15 2022 InstallationDate: Installed on 2020-02-03 (924 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1986510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983638] Re: Ubuntu 22.10 Settings-sound-output-test does not work
This was caused because I had gnome-control-center stop recommending libcanberra-pulse. I am reverting that change now. The source package libcanberra is still in main so we just need to get this binary package re-promoted to main. ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1983638 Title: Ubuntu 22.10 Settings-sound-output-test does not work Status in gnome-control-center package in Ubuntu: Fix Committed Bug description: Open settings. select sound. System Volume and Volume for System Sounds are at maximum, Output Device is HDMI / DisplayPort2 - Built-in Audio click on Test and then on Left or Right speaker has no effect (no sound) but clicking on Alert Sound works fine. Playing a movie.MOV with totem sound is ok. On the same PC different partition I have Ubuntu 22.04 and problem does not occur. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:42.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Aug 5 07:06:31 2022 InstallationDate: Installed on 2022-07-19 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1983638/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984327] Re: Component mismatch: new lerc support requires universe package
Uploaded: Uploading tiff_4.4.0-4ubuntu2.dsc Uploading tiff_4.4.0-4ubuntu2.debian.tar.xz Uploading tiff_4.4.0-4ubuntu2_source.buildinfo Uploading tiff_4.4.0-4ubuntu2_source.changes I decided to retain the ubuntu suffix (see discussion at [1]), and will sync the package the next time there is a debian upload. 1. https://lists.ubuntu.com/archives/ubuntu-devel/2022-May/042099.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1984327 Title: Component mismatch: new lerc support requires universe package Status in tiff package in Ubuntu: Fix Released Bug description: tiff is in sync with debian, and version tiff 4.4.0-1[1] enabled lerc support. Unfortunately lerc[2] is in ubuntu universe, and tiff is in main, so we either MIR lerc, or disable it in tiff. For now, let's disable lerc support. 1. https://launchpad.net/ubuntu/+source/tiff/4.4.0-1 2. https://launchpad.net/ubuntu/+source/lerc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1984327/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984327] Re: Component mismatch: new lerc support requires universe package
Yes, will do today -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1984327 Title: Component mismatch: new lerc support requires universe package Status in tiff package in Ubuntu: Fix Released Bug description: tiff is in sync with debian, and version tiff 4.4.0-1[1] enabled lerc support. Unfortunately lerc[2] is in ubuntu universe, and tiff is in main, so we either MIR lerc, or disable it in tiff. For now, let's disable lerc support. 1. https://launchpad.net/ubuntu/+source/tiff/4.4.0-1 2. https://launchpad.net/ubuntu/+source/lerc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1984327/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1980606] Re: gnome-control-centre crashes after enabling "Sharing"
** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1980606 Title: gnome-control-centre crashes after enabling "Sharing" Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: Fix Committed Bug description: Impact -- gnome-control-center uses gsettings schemas from the gnome-remote-desktop package without being able to handle if those schemas are not installed. Because gnome-control-center keeps track of which page was last opened, it's not possible to simply ignore the Sharing page, a user would need to manually open the Settings app to a different page or else the Settings app won't run at all. ubuntu-desktop and gnome-shell already Recommend gnome-remote-desktop so most people won't experience this issue. Test Case - sudo apt remove gnome-remote-desktop Run gnome-control-center From the left sidebar, click Sharing (The app crashes) Install the update. The update will install gnome-remote-desktop. Run gnome-control-center The app should work like normal What Could Go Wrong --- This only adds a hard dependency on gnome-remote-desktop. Without this fix, the Sharing panel didn't work at all. Original Bug Report --- After the crash, gnome-control-centre fails to launch again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sun Jul 3 20:39:04 2022 InstallationDate: Installed on 2017-05-24 (1866 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-05-31 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1980606/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.
Thanks for the bug report, Robert.
My first attempt would be adding a pkg-config line to the build-packages
of chromium. Does it make sense to you? If yes, could you please try
that?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1986925
Title:
[snap] Trying to build chromium snap for core22: pkg-config fails.
Status in chromium-browser package in Ubuntu:
New
Bug description:
I checked out the "dev" branch of chromium-browser from launchpad and
did what seemed necessary to update snapcraft.yaml to build with
snapcraft 7 for core22. The only change of any significance was to
change the extension from "gnome-3-38" to the core22-specific "gnome"
extension. I started the build and it ran for quite some time (in a
persistent 22.04 LXD container) until:
2022-08-18 09:11:00.869 :: + OUT=out/Release
2022-08-18 09:11:00.869 :: + mkdir -p out/Release
2022-08-18 09:11:00.888 :: + cp
/root/snaps/snap-from-source/stage/build/args.gn out/Release/
2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
2022-08-18 09:11:00.935 :: + cd -
2022-08-18 09:11:00.935 :: /root/snaps/snap-from-source/parts/chromium/build
2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
2022-08-18 09:11:07.112 :: ERROR at
//build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit code.
2022-08-18 09:11:07.112 :: pkgresult = exec_script(pkg_config_script,
args, "value")
2022-08-18 09:11:07.113 :: ^--
2022-08-18 09:11:07.113 :: Current dir:
/root/snaps/snap-from-source/parts/chromium/build/out/Release/
2022-08-18 09:11:07.113 :: Command: python3
/root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
-p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
2022-08-18 09:11:07.113 :: Returned 1.
2022-08-18 09:11:07.113 :: stderr:
2022-08-18 09:11:07.113 ::
2022-08-18 09:11:07.113 :: Could not run pkg-config.
2022-08-18 09:11:07.113 ::
2022-08-18 09:11:07.113 :: See
//third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
2022-08-18 09:11:07.113 :: ^--
2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file to be
included.
2022-08-18 09:11:07.114 ::
"//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan",
2022-08-18 09:11:07.114 ::
^---
2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with code
1.
Review the scriptlet and make sure it's correct.
I verified that the pkg-config utility is installed in the container;
I can only suspect that this error is related to switching to the
core22 gnome extension. I am open to suggestions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986925/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986922] Re: snapcraft build fails on second run as "ln -s libdrm.pc libdrm-uninstalled.pc" already done
I know I don't need to suggest this, but the seeming solution is to just replace "ln -s" with "ln -sf", unless there's something more subtle going on. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1986922 Title: snapcraft build fails on second run as "ln -s libdrm.pc libdrm- uninstalled.pc" already done Status in chromium-browser package in Ubuntu: New Bug description: I'm trying to migrate the chromium browser snapcraft.yaml file to core22 and Snapcraft 7 and, after a build error on the first test (more on that later), I cleaned and re-ran the build to make sure the build error was reproducible, and got: ... big snip ... 2022-08-18 08:50:45.224 :: + OUT=out/Release 2022-08-18 08:50:45.224 :: + mkdir -p out/Release 2022-08-18 08:50:45.243 :: + cp /root/snaps/snap-from-source/stage/build/args.gn out/Release/ 2022-08-18 08:50:45.259 :: + '[' amd64 = armhf ']' 2022-08-18 08:50:45.260 :: + '[' amd64 = armhf ']' 2022-08-18 08:50:45.260 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig 2022-08-18 08:50:45.260 :: + ln -s libdrm.pc libdrm-uninstalled.pc 2022-08-18 08:50:45.269 :: ln: failed to create symbolic link 'libdrm-uninstalled.pc': File exists 2022-08-18 08:50:45.431 'override-build' in part 'chromium' failed with code 1. Review the scriptlet and make sure it's correct. Naturally, since that symlink had been created during the first run (in a persistent 22.04 LXD container), it was still there for the second run. Operations like that should be idempotent so one can run multiple builds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986922/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1945321] Re: umockdev 0.16.3-1 breaks autopkgtest of bolt
** Changed in: bolt (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bolt in Ubuntu.
https://bugs.launchpad.net/bugs/1945321
Title:
umockdev 0.16.3-1 breaks autopkgtest of bolt
Status in bolt package in Ubuntu:
Fix Released
Status in umockdev package in Ubuntu:
Invalid
Status in umockdev package in Debian:
Fix Released
Bug description:
The test of bolt fails with the new version due to a crash:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/b/bolt/20210917_063952_c9336@/log.gz
...
Trace/breakpoint trap (core dumped)
The bolt test really uses umockdev, d/t/control has gir1.2-umockdev-1.0 and
python3-dbusmock and the new version causes this.
Retrying autopkgtest locally with no, all and just umockdev from proposed
and it seems reproducible.
- impish-release - works
- impish-all-proposed - crashes
- impish-release + umockdev+libc6 from proposed - crashes
Repro:
$ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power
FYI:
Downgrading to umockdev 0.16.2-1 in the same environment does not
eliminate the issue. So it might happen at the bolt test-build time.
Debian has the same issue in:
https://ci.debian.net/data/autopkgtest/testing/amd64/b/bolt/15587717/log.gz
The new mockdev fails to create /sys/bus which is requested by the test.
From there the error path is what crashes, but the root cause is why we enter
the error-path in the first place.
One should be aware, this fail is "normal" if the environment is not mocked.
Even in the good case the different calls with/without umockdev lead to
exactly the same crash.
# good
$ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power
# same crash as the new version has with umockdev-wrapper
$ gdb /usr/libexec/installed-tests/bolt/test-power
This is based on ldpreload.
$ cat /usr/bin/umockdev-wrapper
#!/bin/sh
# Wrapper program to preload the libumockdev library, so that test programs
can
# set $UMOCKDEV_DIR for redirecting sysfs and other queries to a test bed.
exec env LD_PRELOAD=libumockdev-preload.so.0:$LD_PRELOAD "$@"
Gut feeling: it seems the mocking no more happens, and due to that
it runs into the non-mocked crash
Debugging with that:
$ pull-lp-source bolt
$ cd bolt-0.9.1/tests
$ gdb /usr/libexec/installed-tests/bolt/test-power
(gdb) set environment LD_PRELOAD libumockdev-preload.so.0
(gdb) b mock_sysfs_init
(gdb) run
With that we can see that while the crash is somewhere inside g_warning the
reason is in the g_mkdir failing with the new umockdev.
Good-case
Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165
165 {
(gdb) n
171 ms->bed = umockdev_testbed_new ();
(gdb)
[New Thread 0x76e65640 (LWP 11444)]
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used
after threads are created
# DEBUG: umockdev.vala:104: Created udev test bed /tmp/umockdev.RQBNA1
172 ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal,
(gdb)
[New Thread 0x76664640 (LWP 11445)]
175 ms->devices = g_hash_table_new (g_str_hash, g_str_equal);
(gdb)
180 sys = umockdev_testbed_get_sys_dir (ms->bed);
(gdb)
182 bus = g_build_filename (sys, "bus", NULL);
(gdb) p sys
$1 = 0x555b99a0 "/tmp/umockdev.RQBNA1/sys"
(gdb) n
183 r = g_mkdir (bus, 0744);
(gdb) p bus
$2 = 0x555be330 "/tmp/umockdev.RQBNA1/sys/bus"
(gdb) n
185 if (r < 0)
(gdb) p r
$3 = 0
(gdb) n
188 cls = g_build_filename (sys, "class", NULL);
Bad-Case
Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165
165 {
(gdb) n
171 ms->bed = umockdev_testbed_new ();
(gdb)
[New Thread 0x76e65640 (LWP 17082)]
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used
after threads are created
# DEBUG: umockdev.vala:110: Created udev test bed /tmp/umockdev.TK2VA1
172 ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal,
(gdb)
[New Thread 0x76664640 (LWP 17083)]
175 ms->devices = g_hash_table_new (g_str_hash, g_str_equal);
(gdb)
180 sys = umockdev_testbed_get_sys_dir (ms->bed);
(gdb)
182 bus = g_build_filename (sys, "bus", NULL);
(gdb) p sys
$1 = 0x555a98b0 "/tmp/umockdev.TK2VA1/sys"
(gdb) n
183 r = g_mkdir (bus, 0744);
(gdb) p bus
$2 = 0x555be560 "/tmp/umockdev.TK2VA1/sys/bus"
(gdb) n
185 if (r < 0)
(gdb) p r
$3 = -1
(gdb) n
186 g_warning ("could not create %s", bus);
(gdb) n
** (/usr/libexec/installed-tests/bolt/test-power:17078): WARNING **:
15:11:06.614: could not create /tmp/umockdev.TK2VA1/sys/bus
Thread 1 "test-power" received signal SIGTRAP, Trace/breakpoint trap.
I'll tag this update-excuse and FYI-subscribe Martin who has done the
[Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.
Let me know if there's anything you want me to test; I have the
container sitting here, ready for further experimentation.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1986925
Title:
[snap] Trying to build chromium snap for core22: pkg-config fails.
Status in chromium-browser package in Ubuntu:
New
Bug description:
I checked out the "dev" branch of chromium-browser from launchpad and
did what seemed necessary to update snapcraft.yaml to build with
snapcraft 7 for core22. The only change of any significance was to
change the extension from "gnome-3-38" to the core22-specific "gnome"
extension. I started the build and it ran for quite some time (in a
persistent 22.04 LXD container) until:
2022-08-18 09:11:00.869 :: + OUT=out/Release
2022-08-18 09:11:00.869 :: + mkdir -p out/Release
2022-08-18 09:11:00.888 :: + cp
/root/snaps/snap-from-source/stage/build/args.gn out/Release/
2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
2022-08-18 09:11:00.935 :: + cd -
2022-08-18 09:11:00.935 :: /root/snaps/snap-from-source/parts/chromium/build
2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
2022-08-18 09:11:07.112 :: ERROR at
//build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit code.
2022-08-18 09:11:07.112 :: pkgresult = exec_script(pkg_config_script,
args, "value")
2022-08-18 09:11:07.113 :: ^--
2022-08-18 09:11:07.113 :: Current dir:
/root/snaps/snap-from-source/parts/chromium/build/out/Release/
2022-08-18 09:11:07.113 :: Command: python3
/root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
-p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
2022-08-18 09:11:07.113 :: Returned 1.
2022-08-18 09:11:07.113 :: stderr:
2022-08-18 09:11:07.113 ::
2022-08-18 09:11:07.113 :: Could not run pkg-config.
2022-08-18 09:11:07.113 ::
2022-08-18 09:11:07.113 :: See
//third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
2022-08-18 09:11:07.113 :: ^--
2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file to be
included.
2022-08-18 09:11:07.114 ::
"//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan",
2022-08-18 09:11:07.114 ::
^---
2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with code
1.
Review the scriptlet and make sure it's correct.
I verified that the pkg-config utility is installed in the container;
I can only suspect that this error is related to switching to the
core22 gnome extension. I am open to suggestions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986925/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986510] Re: No settings options for "Dock" under setting>>appearance
Please run this command in a terminal: sudo apt install ubuntu-desktop Then log out and log back in. ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1986510 Title: No settings options for "Dock" under setting>>appearance Status in gnome-control-center package in Ubuntu: Incomplete Bug description: There are no options for customizing the Dock under settings>>appearance. Even withe gnome-tweaks installed, the options don't show up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Aug 15 11:01:15 2022 InstallationDate: Installed on 2020-02-03 (924 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1986510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969891] Re: Firefox snap can't be added to Dock favorites
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- ubuntu-dock (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1969891 Title: Firefox snap can't be added to Dock favorites Status in firefox package in Ubuntu: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: After upgrading from 21.10 to 22.04 the old Firefox was removed from my Dock favorites. I readded Firefox to my favorites which adds the Firefox icon to the favorites as expected. However, clicking on it will open the Firefox snap on the bottom of the Dock. So now I have 2 Firefox symbols in my Dock. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 Uname: Linux 5.17.0-4.1-liquorix-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:49:32 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-05-31 (325 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1969891/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.
** Summary changed:
- Trying to build chromium snap for core22: pkg-config fails.
+ [snap] Trying to build chromium snap for core22: pkg-config fails.
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1986925
Title:
[snap] Trying to build chromium snap for core22: pkg-config fails.
Status in chromium-browser package in Ubuntu:
New
Bug description:
I checked out the "dev" branch of chromium-browser from launchpad and
did what seemed necessary to update snapcraft.yaml to build with
snapcraft 7 for core22. The only change of any significance was to
change the extension from "gnome-3-38" to the core22-specific "gnome"
extension. I started the build and it ran for quite some time (in a
persistent 22.04 LXD container) until:
2022-08-18 09:11:00.869 :: + OUT=out/Release
2022-08-18 09:11:00.869 :: + mkdir -p out/Release
2022-08-18 09:11:00.888 :: + cp
/root/snaps/snap-from-source/stage/build/args.gn out/Release/
2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
2022-08-18 09:11:00.935 :: + cd -
2022-08-18 09:11:00.935 :: /root/snaps/snap-from-source/parts/chromium/build
2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
2022-08-18 09:11:07.112 :: ERROR at
//build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit code.
2022-08-18 09:11:07.112 :: pkgresult = exec_script(pkg_config_script,
args, "value")
2022-08-18 09:11:07.113 :: ^--
2022-08-18 09:11:07.113 :: Current dir:
/root/snaps/snap-from-source/parts/chromium/build/out/Release/
2022-08-18 09:11:07.113 :: Command: python3
/root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
-p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
2022-08-18 09:11:07.113 :: Returned 1.
2022-08-18 09:11:07.113 :: stderr:
2022-08-18 09:11:07.113 ::
2022-08-18 09:11:07.113 :: Could not run pkg-config.
2022-08-18 09:11:07.113 ::
2022-08-18 09:11:07.113 :: See
//third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
2022-08-18 09:11:07.113 :: ^--
2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file to be
included.
2022-08-18 09:11:07.114 ::
"//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan",
2022-08-18 09:11:07.114 ::
^---
2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with code
1.
Review the scriptlet and make sure it's correct.
I verified that the pkg-config utility is installed in the container;
I can only suspect that this error is related to switching to the
core22 gnome extension. I am open to suggestions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986925/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982455] Re: An application replaces Files (Nautilus) icon
I can confirm this issue with Ubuntu 22.04 in as much as any attempt to open a further Files window will show on the dock as a PyCharm window. Once the Files window that was opened by PyCharm has been closed then the dock displays the 'dot' against Files correctly. ** Description changed: Here is everything you need to know: https://youtrack.jetbrains.com/issue/IDEA-298262. + + From the above link: + + Steps to Reproduce + + Open a project + + In the "explorer" panel click "Open In" on something, then "Files" + + Actual Result + + The Files window is opened with it's icon being PyCharm's icon, and all + subsequent folder openings now have PyCharm's icon until I reboot. So, + "Open In" is unusable, and I have to open folders manually. + + Ubuntu 20.04.4 LTS ** Tags added: focal jammy ** Package changed: ubuntu => gnome-shell-extension-ubuntu-dock (Ubuntu) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Confirmed ** Summary changed: - An application replaces Files (Nautilus) icon + An application replaces Files (Nautilus) indicator on Ubuntu Dock -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1982455 Title: An application replaces Files (Nautilus) indicator on Ubuntu Dock Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Here is everything you need to know: https://youtrack.jetbrains.com/issue/IDEA-298262. From the above link: Steps to Reproduce Open a project In the "explorer" panel click "Open In" on something, then "Files" Actual Result The Files window is opened with it's icon being PyCharm's icon, and all subsequent folder openings now have PyCharm's icon until I reboot. So, "Open In" is unusable, and I have to open folders manually. Ubuntu 20.04.4 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1982455/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986456] Re: Firefox fails to start after update
Should add that this is fixable with: sudo snap remove firefox sudo snap install firefox All firefox data, up to and including open tabs, etc, is retained through the reinstall of the snap. Ideally things like this should 'just work' and perhaps best to push an update that fixes rather than relying on users to manually reinstall after the upgrade. -- 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/1986456 Title: Firefox fails to start after update Status in firefox package in Ubuntu: Incomplete Bug description: After system Updates today (14.08.2022) firefox did not start anymore. It's Ubuntu 22.04 Error Message: mikey@mikey-notebook:~$ firefox /snap/firefox/1670/snap/command-chain/desktop-launch: line 52: /home/mikey/.config/user-dirs.dirs: Permission denied sed: can't read /home/mikey/.config/user-dirs.dirs: Permission denied /snap/firefox/1670/snap/command-chain/desktop-launch: line 264: /home/mikey/.config/user-dirs.dirs: Permission denied cp: cannot open '/home/mikey/.config/user-dirs.locale' for reading: Permission denied /snap/firefox/1670/snap/command-chain/desktop-launch: line 269: /home/mikey/.config/user-dirs.locale: Permission denied /snap/firefox/1670/snap/command-chain/desktop-launch: line 20: /snap/firefox/1670/gnome-platform/usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: No such file or directory ERROR: /snap/firefox/1670/gnome-platform/usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 exited abnormally with status 127 XPCOMGlueLoad error for file /snap/firefox/1670/usr/lib/firefox/libmozgtk.so: libgtk-3.so.0: cannot open shared object file: No such file or directory Couldn't load XPCOM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1986456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982455] [NEW] An application replaces Files (Nautilus) icon
You have been subscribed to a public bug: Here is everything you need to know: https://youtrack.jetbrains.com/issue/IDEA-298262. >From the above link: Steps to Reproduce Open a project In the "explorer" panel click "Open In" on something, then "Files" Actual Result The Files window is opened with it's icon being PyCharm's icon, and all subsequent folder openings now have PyCharm's icon until I reboot. So, "Open In" is unusable, and I have to open folders manually. Ubuntu 20.04.4 LTS ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment focal jammy -- An application replaces Files (Nautilus) icon https://bugs.launchpad.net/bugs/1982455 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock 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 1986456] Re: Firefox fails to start after update
I can confirm this on a recently updated (20.04 --> 22.04) AMD64 install of Ubuntu Mate. XPCOMGlueLoad error for file /snap/firefox/1670/usr/lib/firefox/libmozgtk.so: libgtk-3.so.0: cannot open shared object file: No such file or directory Couldn't load XPCOM. The distro was updated and as part of the process the installed firefox replaced with the snap. It initially worked, but after about a day, including a couple of reboots, it now fails to start with the above error. -- 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/1986456 Title: Firefox fails to start after update Status in firefox package in Ubuntu: Incomplete Bug description: After system Updates today (14.08.2022) firefox did not start anymore. It's Ubuntu 22.04 Error Message: mikey@mikey-notebook:~$ firefox /snap/firefox/1670/snap/command-chain/desktop-launch: line 52: /home/mikey/.config/user-dirs.dirs: Permission denied sed: can't read /home/mikey/.config/user-dirs.dirs: Permission denied /snap/firefox/1670/snap/command-chain/desktop-launch: line 264: /home/mikey/.config/user-dirs.dirs: Permission denied cp: cannot open '/home/mikey/.config/user-dirs.locale' for reading: Permission denied /snap/firefox/1670/snap/command-chain/desktop-launch: line 269: /home/mikey/.config/user-dirs.locale: Permission denied /snap/firefox/1670/snap/command-chain/desktop-launch: line 20: /snap/firefox/1670/gnome-platform/usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: No such file or directory ERROR: /snap/firefox/1670/gnome-platform/usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 exited abnormally with status 127 XPCOMGlueLoad error for file /snap/firefox/1670/usr/lib/firefox/libmozgtk.so: libgtk-3.so.0: cannot open shared object file: No such file or directory Couldn't load XPCOM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1986456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986925] [NEW] Trying to build chromium snap for core22: pkg-config fails.
Public bug reported:
I checked out the "dev" branch of chromium-browser from launchpad and
did what seemed necessary to update snapcraft.yaml to build with
snapcraft 7 for core22. The only change of any significance was to
change the extension from "gnome-3-38" to the core22-specific "gnome"
extension. I started the build and it ran for quite some time (in a
persistent 22.04 LXD container) until:
2022-08-18 09:11:00.869 :: + OUT=out/Release
2022-08-18 09:11:00.869 :: + mkdir -p out/Release
2022-08-18 09:11:00.888 :: + cp
/root/snaps/snap-from-source/stage/build/args.gn out/Release/
2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
2022-08-18 09:11:00.935 :: + cd -
2022-08-18 09:11:00.935 :: /root/snaps/snap-from-source/parts/chromium/build
2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
2022-08-18 09:11:07.112 :: ERROR at //build/config/linux/pkg_config.gni:104:17:
Script returned non-zero exit code.
2022-08-18 09:11:07.112 :: pkgresult = exec_script(pkg_config_script, args,
"value")
2022-08-18 09:11:07.113 :: ^--
2022-08-18 09:11:07.113 :: Current dir:
/root/snaps/snap-from-source/parts/chromium/build/out/Release/
2022-08-18 09:11:07.113 :: Command: python3
/root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
-p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
2022-08-18 09:11:07.113 :: Returned 1.
2022-08-18 09:11:07.113 :: stderr:
2022-08-18 09:11:07.113 ::
2022-08-18 09:11:07.113 :: Could not run pkg-config.
2022-08-18 09:11:07.113 ::
2022-08-18 09:11:07.113 :: See
//third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
2022-08-18 09:11:07.113 :: ^--
2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file to be
included.
2022-08-18 09:11:07.114 ::
"//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan",
2022-08-18 09:11:07.114 ::
^---
2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with code 1.
Review the scriptlet and make sure it's correct.
I verified that the pkg-config utility is installed in the container; I
can only suspect that this error is related to switching to the core22
gnome extension. I am open to suggestions.
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1986925
Title:
Trying to build chromium snap for core22: pkg-config fails.
Status in chromium-browser package in Ubuntu:
New
Bug description:
I checked out the "dev" branch of chromium-browser from launchpad and
did what seemed necessary to update snapcraft.yaml to build with
snapcraft 7 for core22. The only change of any significance was to
change the extension from "gnome-3-38" to the core22-specific "gnome"
extension. I started the build and it ran for quite some time (in a
persistent 22.04 LXD container) until:
2022-08-18 09:11:00.869 :: + OUT=out/Release
2022-08-18 09:11:00.869 :: + mkdir -p out/Release
2022-08-18 09:11:00.888 :: + cp
/root/snaps/snap-from-source/stage/build/args.gn out/Release/
2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
[Desktop-packages] [Bug 1986922] [NEW] snapcraft build fails on second run as "ln -s libdrm.pc libdrm-uninstalled.pc" already done
Public bug reported: I'm trying to migrate the chromium browser snapcraft.yaml file to core22 and Snapcraft 7 and, after a build error on the first test (more on that later), I cleaned and re-ran the build to make sure the build error was reproducible, and got: ... big snip ... 2022-08-18 08:50:45.224 :: + OUT=out/Release 2022-08-18 08:50:45.224 :: + mkdir -p out/Release 2022-08-18 08:50:45.243 :: + cp /root/snaps/snap-from-source/stage/build/args.gn out/Release/ 2022-08-18 08:50:45.259 :: + '[' amd64 = armhf ']' 2022-08-18 08:50:45.260 :: + '[' amd64 = armhf ']' 2022-08-18 08:50:45.260 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig 2022-08-18 08:50:45.260 :: + ln -s libdrm.pc libdrm-uninstalled.pc 2022-08-18 08:50:45.269 :: ln: failed to create symbolic link 'libdrm-uninstalled.pc': File exists 2022-08-18 08:50:45.431 'override-build' in part 'chromium' failed with code 1. Review the scriptlet and make sure it's correct. Naturally, since that symlink had been created during the first run (in a persistent 22.04 LXD container), it was still there for the second run. Operations like that should be idempotent so one can run multiple builds. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1986922 Title: snapcraft build fails on second run as "ln -s libdrm.pc libdrm- uninstalled.pc" already done Status in chromium-browser package in Ubuntu: New Bug description: I'm trying to migrate the chromium browser snapcraft.yaml file to core22 and Snapcraft 7 and, after a build error on the first test (more on that later), I cleaned and re-ran the build to make sure the build error was reproducible, and got: ... big snip ... 2022-08-18 08:50:45.224 :: + OUT=out/Release 2022-08-18 08:50:45.224 :: + mkdir -p out/Release 2022-08-18 08:50:45.243 :: + cp /root/snaps/snap-from-source/stage/build/args.gn out/Release/ 2022-08-18 08:50:45.259 :: + '[' amd64 = armhf ']' 2022-08-18 08:50:45.260 :: + '[' amd64 = armhf ']' 2022-08-18 08:50:45.260 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig 2022-08-18 08:50:45.260 :: + ln -s libdrm.pc libdrm-uninstalled.pc 2022-08-18 08:50:45.269 :: ln: failed to create symbolic link 'libdrm-uninstalled.pc': File exists 2022-08-18 08:50:45.431 'override-build' in part 'chromium' failed with code 1. Review the scriptlet and make sure it's correct. Naturally, since that symlink had been created during the first run (in a persistent 22.04 LXD container), it was still there for the second run. Operations like that should be idempotent so one can run multiple builds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986922/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1719143] Re: Unable to calibrate monitors through Gnome Control Center->Color [calibration failed with code 1: no sensor->get_sample]
Getting the same issue with x-rite i1|Display Pro on Ubuntu 22.04 LTS -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1719143 Title: Unable to calibrate monitors through Gnome Control Center->Color [calibration failed with code 1: no sensor->get_sample] Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Fresh install of Artful, using gnome-session to access vanilla GNOME session on Wayland (also tried on xorg). Attempting to calibrate monitors through Gnome Control Center->Devices->Color. All attempts ended at the point where I was asked to put the device onto the monitor, with the error: Calibration failed! An internal error occurred that could not be recovered. You can remove the calibration device. Syslog: Sep 24 12:19:31 desktop kernel: [ 262.849675] usb 3-6: new full-speed USB device number 7 using xhci_hcd Sep 24 12:19:32 desktop kernel: [ 262.990880] usb 3-6: New USB device found, idVendor=0971, idProduct=2007 Sep 24 12:19:32 desktop kernel: [ 262.990882] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Sep 24 12:19:32 desktop kernel: [ 262.990884] usb 3-6: Product: colormunki Sep 24 12:19:32 desktop kernel: [ 262.990885] usb 3-6: Manufacturer: X-Rite Sep 24 12:19:32 desktop pulseaudio[953]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Sep 24 12:19:32 desktop gnome-shell[876]: drmModeSetCursor2 failed with (Permission denied), drawing cursor with OpenGL from now on Sep 24 12:19:32 desktop pulseaudio[953]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libEGL warning: wayland-egl: could not open /dev/dri/card0 (Permission denied) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libEGL warning: wayland-egl: could not open /dev/dri/card0 (Permission denied) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: VA error: wayland: failed to open /dev/dri/card0: Permission denied (errno 13) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: VA error: wayland: failed to open /dev/dri/card0: Permission denied (errno 13) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) I attempted to fix the permissions error for /dev/dri/card0. Current permissions: rwh@desktop:~$ ls -l /dev/dri/card0 crw-rw+ 1 root video 226, 0 Sep 24 12:15 /dev/dri/card0 Tried adding my user to video group, which made no difference. Then made file world r/w: rwh@desktop:~$ sudo chmod o+rw /dev/dri/card0 Which fixed that problem. Now, in the calibrate wizard, on the second step (Display Type) I am offered three options (LCD, CRT, Projector) where I only saw LCD previously. However, the calibration step failed the same as before. Syslog: Sep 24 12:36:46 desktop kernel: [ 1298.430546] usb 3-6: new full-speed USB device number 12 using xhci_hcd Sep 24 12:36:46 desktop kernel: [ 1298.571756] usb 3-6: New USB device found, idVendor=0971, idProduct=2007 Sep 24 12:36:46 desktop kernel: [ 1298.571759] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Sep 24 12:36:46 desktop kernel: [ 1298.571760] usb 3-6: Product: colormunki Sep 24 12:36:46 desktop kernel: [ 1298.571762] usb 3-6: Manufacturer: X-Rite Sep 24 12:36:46 desktop pulseaudio[953]: message repeated 3 times: [ W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended.] Sep 24 12:36:47 desktop gnome-control-c[5206]: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found. Sep 24 12:36:47 desktop gnome-control-c[5201]: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found. Sep 24 12:36:47 desktop gnome-control-c[5201]: Error 71 (Protocol error) dispatching to Wayland display. Sep 24 12:36:47 desktop gnome-control-c[5206]: Error 71 (Protocol error) dispatching to Wayland display. Sep 24 12:37:21 desktop dbus-daemon[4121]: Activating via systemd: service name='org.freedesktop.ColorHelper' unit='colord-session.service' Sep 24 12:37:21 desktop systemd[3601]: Starting Color management helper... Sep 24 12:37:21 desktop dbus-daemon[4121]: Successfully activated service 'org.freedesktop.ColorHelper' Sep 24 12:37:21 desktop systemd[3601]: Started Color management helper. Sep
[Desktop-packages] [Bug 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(
** Changed in: oem-priority Importance: High => Critical -- 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/1969422 Title: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object() Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 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/mutter/+bug/1969422/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922414] Re: ssh-agent fails to start (has_option: command not found)
Upgraded from 20.04 LTS to 22.04 LTS and still got the same issue: Aug 18 08:35:14 redacted /usr/libexec/gdm-x-session[6714]: /etc/X11/Xsession.d/30x11-common_xresources: line 16: has_option: command not found Aug 18 08:35:14 redacted /usr/libexec/gdm-x-session[6749]: /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command not found Aug 18 08:35:14 redacted /usr/libexec/gdm-x-session[6780]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in Light Display Manager: New Status in gdm3 package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Confirmed Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1922414/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
