[Desktop-packages] [Bug 1980551] Re: gnome-control-center crashed with SIGSEGV in gtk_icon_theme_lookup_icon()
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- 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/1980551 Title: gnome-control-center crashed with SIGSEGV in gtk_icon_theme_lookup_icon() Status in gnome-control-center package in Ubuntu: Expired Bug description: No further info ProblemType: Crash 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-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jul 1 16:26:36 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-05-28 (33 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526) JournalErrors: jul 01 16:26:28 hostname gnome-control-c[2812]: Finalizing AdwPreferencesPage 0x55ec09908810, but it still has children left: jul 01 16:26:28 hostname gnome-control-c[2812]:- GtkCenterBox 0x55ec0994e170 jul 01 16:26:36 hostname gnome-control-c[2812]: g_object_ref: assertion '!object_already_finalized' failed jul 01 16:26:38 hostname gnome-shell[1695]: setup_framebuffers: assertion 'width > 0' failed ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x7f22930efdbe:cmpl $0x80,0x50(%rax) PC (0x7f22930efdbe) ok source "$0x80" ok destination "0x50(%rax)" (0x0050) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1 gtk_icon_theme_lookup_icon () from /lib/x86_64-linux-gnu/libgtk-4.so.1 gtk_icon_theme_lookup_by_gicon () from /lib/x86_64-linux-gnu/libgtk-4.so.1 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1 Title: gnome-control-center crashed with SIGSEGV in gtk_icon_theme_lookup_icon() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1980551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988611] [NEW] when my bluetooth headset is connected, i cant switch on the mic on it with A2DP sink on, without ubuntu automatically setting it to HFP.
Public bug reported: when i want high quality audio and also use my mic, i just cant. on A2DP sink i havve to set the input to something else then the mic on my headset, otherwise it automatically goes to HFP and the audio quality is horrible ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 3 04:48:21 2022 InstallationDate: Installed on 2022-08-25 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire A515-44G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=b7acbbd9-e24f-4b33-af26-650900f1b301 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2021 dmi.bios.release: 1.12 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: V1.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Calla_RN dmi.board.vendor: RO dmi.board.version: V1.12 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.12:bd03/15/2021:br1.12:efr1.2:svnAcer:pnAspireA515-44G:pvrV1.12:rvnRO:rnCalla_RN:rvrV1.12:cvnChassisManufacturer:ct10:cvrChassisVersion:sku: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-44G dmi.product.sku: dmi.product.version: V1.12 dmi.sys.vendor: Acer hciconfig: hci0: Type: Primary Bus: USB BD Address: 80:30:49:1F:54:EC ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING RX bytes:3179363 acl:174 sco:114063 events:11963 errors:0 TX bytes:10704828 acl:11543 sco:113336 commands:228 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1988611 Title: when my bluetooth headset is connected, i cant switch on the mic on it with A2DP sink on, without ubuntu automatically setting it to HFP. Status in bluez package in Ubuntu: New Bug description: when i want high quality audio and also use my mic, i just cant. on A2DP sink i havve to set the input to something else then the mic on my headset, otherwise it automatically goes to HFP and the audio quality is horrible ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 3 04:48:21 2022 InstallationDate: Installed on 2022-08-25 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire A515-44G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=b7acbbd9-e24f-4b33-af26-650900f1b301 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2021 dmi.bios.release: 1.12 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: V1.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Calla_RN dmi.board.vendor: RO dmi.board.version: V1.12 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.12:bd03/15/2021:br1.12:efr1.2:svnAcer:pnAspireA515-44G:pvrV1.12:rvnRO:rnCalla_RN:rvrV1.12:cvnChassisManufacturer:ct10:cvrChassisVersion:sku: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-44G dmi.product.sku: dmi.product.version: V1.12 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 80:30:49:1F:54:EC ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING RX bytes:3179363 acl:174 sco:114063 events:11963 errors:0 TX bytes:10704828 acl:11543 sco:113336 commands:228 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1988611/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875671] Re: wayland: desktop folder missing in Nautilus sidebar
Still true and broken in 22.04 duplicate → https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1986463 -- 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/1875671 Title: wayland: desktop folder missing in Nautilus sidebar Status in Mutter: New Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: Using Wayland session nautilus home window does not show Desktop folder in sidebar while is dispayed using X11 session. see attachment. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 Uname: Linux 5.7.0-050700rc3-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 17:24:45 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1059, 852)' InstallationDate: Installed on 2020-04-23 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1875671/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986463] Re: no Desktop bookmark in side pane under Wayland
*** This bug is a duplicate of bug 1875671 *** https://bugs.launchpad.net/bugs/1875671 ** This bug has been marked a duplicate of bug 1875671 wayland: desktop folder missing in Nautilus sidebar -- 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/1986463 Title: no Desktop bookmark in side pane under Wayland Status in nautilus package in Ubuntu: Invalid Bug description: Hi, Ubuntu 22.04 here. On a Wayland session, Nautilus shows no bookmark for desktop in side pane. It does ( from the same user session ) while under Xorg. Picture attached shows 2 different users session ( as I first thought of different settings users' side ) but I firmly confirm the only « culprit » is using Wayland vs. using Xorg. So the Nautilus window on the left of the picture comes from a Wayland session ( no desktop bookmark in side pane, bad ), and the one on the right side comes from a Xorg session ( with desktop bookmark in side pane, good. ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1986463/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988558] Re: locale order of date not correct in lock screen
** Package changed: language-pack-el (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1988558 Title: locale order of date not correct in lock screen Status in gnome-shell package in Ubuntu: New Bug description: 1)lsb_release -rd Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 2)apt-cache policy locale-package-el language-pack-el: Installed: 1:22.10+20220827 Candidate: 1:22.10+20220827 Version table: *** 1:22.10+20220827 500 500 http://gr.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 500 http://gr.archive.ubuntu.com/ubuntu kinetic/main i386 Packages 100 /var/lib/dpkg/status 3)in lock screen it is expected to have: day(weekday)-number(day of month)-month e.g. Friday 2 September (in greek Παρασκευή 2 Σεπτεμβρίου) 4)instead we see: day-month-number e.g. Friday September 2 (Παρασκευή Σεπτεμβρίου 2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988558/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971434] Re: Display powersave only blanks, but does not turn off
I have the same issue. 22.04 LTS (though Pop!_OS 22.04) Display server: X11 Display driver: Nvidia 515.48.07 gjs is already installed. OS is installed on an iMac 14,2 from late 2013 (not dual boot, Linux is the sole operating system) ‘xset dpms force off’ does not turn off the monitor, it just blanks the screen. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-07-04 (667 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: gnome-settings-daemon 42.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers video wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988558] [NEW] locale order of date not correct in lock screen
You have been subscribed to a public bug: 1)lsb_release -rd Description:Ubuntu Kinetic Kudu (development branch) Release:22.10 2)apt-cache policy locale-package-el language-pack-el: Installed: 1:22.10+20220827 Candidate: 1:22.10+20220827 Version table: *** 1:22.10+20220827 500 500 http://gr.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 500 http://gr.archive.ubuntu.com/ubuntu kinetic/main i386 Packages 100 /var/lib/dpkg/status 3)in lock screen it is expected to have: day(weekday)-number(day of month)-month e.g. Friday 2 September (in greek Παρασκευή 2 Σεπτεμβρίου) 4)instead we see: day-month-number e.g. Friday September 2 (Παρασκευή Σεπτεμβρίου 2) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: date lock order screen -- locale order of date not correct in lock screen https://bugs.launchpad.net/bugs/1988558 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell 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 1911655] Re: Can't enter period if one already exists
This was fixed in gnome-calculator 40 and newer so this is fixed in Ubuntu 22.04 LTS. ** Changed in: gnome-calculator (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1911655 Title: Can't enter period if one already exists Status in GNOME Calculator: Fix Released Status in gnome-calculator package in Ubuntu: Fix Released Bug description: I've pasted a number withe decimals in Calculator, and I want to calculate 1.5 minus that number, so I press Home, then start typing "1.5". That stops after "1". My input looks like this, where "|" is the cursor: 0.230179408 |0.230179408 1|0.230179408 At that point, I can't type the decimal point. I have to type "-", then arrow left, then the decimal point. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calculator/+bug/1911655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988333] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1988333/+attachment/5613357/+files/monitors.xml.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1988333 Title: Ubuntu Gnome Dock Randomly Dies Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 22.04, I have noticed that the dock (which I have at the bottom) will randomly die. When this happens: * The dock is reduced to just the "Show Applications" icon * One or more open applications will no longer accept events (mouse or keyboard) * Ctrl-` (and sometimes Ctrl-TAB) cease working I can restore it by hitting Alt-F2 and then "r" in the dialog. When this happens, icons on my status bar (Slack, Dropbox, etc.) are doubled. The extra icons go away after the screensaver kicks in and is then unlocked. $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5.22.04.1 Candidate: 72~ubuntu5.22.04.1 Version table: *** 72~ubuntu5.22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 72~ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 42.4-0ubuntu0.22.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-20 (13 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988333/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988333] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1988333/+attachment/5613354/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1988333 Title: Ubuntu Gnome Dock Randomly Dies Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 22.04, I have noticed that the dock (which I have at the bottom) will randomly die. When this happens: * The dock is reduced to just the "Show Applications" icon * One or more open applications will no longer accept events (mouse or keyboard) * Ctrl-` (and sometimes Ctrl-TAB) cease working I can restore it by hitting Alt-F2 and then "r" in the dialog. When this happens, icons on my status bar (Slack, Dropbox, etc.) are doubled. The extra icons go away after the screensaver kicks in and is then unlocked. $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5.22.04.1 Candidate: 72~ubuntu5.22.04.1 Version table: *** 72~ubuntu5.22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 72~ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 42.4-0ubuntu0.22.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-20 (13 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988333/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988333] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1988333/+attachment/5613356/+files/ShellJournal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1988333 Title: Ubuntu Gnome Dock Randomly Dies Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 22.04, I have noticed that the dock (which I have at the bottom) will randomly die. When this happens: * The dock is reduced to just the "Show Applications" icon * One or more open applications will no longer accept events (mouse or keyboard) * Ctrl-` (and sometimes Ctrl-TAB) cease working I can restore it by hitting Alt-F2 and then "r" in the dialog. When this happens, icons on my status bar (Slack, Dropbox, etc.) are doubled. The extra icons go away after the screensaver kicks in and is then unlocked. $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5.22.04.1 Candidate: 72~ubuntu5.22.04.1 Version table: *** 72~ubuntu5.22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 72~ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 42.4-0ubuntu0.22.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-20 (13 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988333/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988333] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1988333/+attachment/5613355/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1988333 Title: Ubuntu Gnome Dock Randomly Dies Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 22.04, I have noticed that the dock (which I have at the bottom) will randomly die. When this happens: * The dock is reduced to just the "Show Applications" icon * One or more open applications will no longer accept events (mouse or keyboard) * Ctrl-` (and sometimes Ctrl-TAB) cease working I can restore it by hitting Alt-F2 and then "r" in the dialog. When this happens, icons on my status bar (Slack, Dropbox, etc.) are doubled. The extra icons go away after the screensaver kicks in and is then unlocked. $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5.22.04.1 Candidate: 72~ubuntu5.22.04.1 Version table: *** 72~ubuntu5.22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 72~ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 42.4-0ubuntu0.22.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-20 (13 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988333/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988333] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1988333/+attachment/5613353/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1988333 Title: Ubuntu Gnome Dock Randomly Dies Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 22.04, I have noticed that the dock (which I have at the bottom) will randomly die. When this happens: * The dock is reduced to just the "Show Applications" icon * One or more open applications will no longer accept events (mouse or keyboard) * Ctrl-` (and sometimes Ctrl-TAB) cease working I can restore it by hitting Alt-F2 and then "r" in the dialog. When this happens, icons on my status bar (Slack, Dropbox, etc.) are doubled. The extra icons go away after the screensaver kicks in and is then unlocked. $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5.22.04.1 Candidate: 72~ubuntu5.22.04.1 Version table: *** 72~ubuntu5.22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 72~ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 42.4-0ubuntu0.22.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-20 (13 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988333/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988333] Re: Ubuntu Gnome Dock Randomly Dies
apport information ** Tags added: apport-collected ** Description changed: Since upgrading to Ubuntu 22.04, I have noticed that the dock (which I have at the bottom) will randomly die. When this happens: * The dock is reduced to just the "Show Applications" icon * One or more open applications will no longer accept events (mouse or keyboard) * Ctrl-` (and sometimes Ctrl-TAB) cease working I can restore it by hitting Alt-F2 and then "r" in the dialog. When this happens, icons on my status bar (Slack, Dropbox, etc.) are doubled. The extra icons go away after the screensaver kicks in and is then unlocked. $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5.22.04.1 Candidate: 72~ubuntu5.22.04.1 Version table: *** 72~ubuntu5.22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 72~ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 22.04 + NonfreeKernelModules: nvidia_modeset nvidia + Package: gnome-shell 42.4-0ubuntu0.22.04.1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 + RebootRequiredPkgs: Error: path contained symlinks. + RelatedPackageVersions: mutter-common 42.2-0ubuntu1 + Tags: jammy + Uname: Linux 5.15.0-46-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-08-20 (13 days ago) + UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1988333/+attachment/5613352/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1988333 Title: Ubuntu Gnome Dock Randomly Dies Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 22.04, I have noticed that the dock (which I have at the bottom) will randomly die. When this happens: * The dock is reduced to just the "Show Applications" icon * One or more open applications will no longer accept events (mouse or keyboard) * Ctrl-` (and sometimes Ctrl-TAB) cease working I can restore it by hitting Alt-F2 and then "r" in the dialog. When this happens, icons on my status bar (Slack, Dropbox, etc.) are doubled. The extra icons go away after the screensaver kicks in and is then unlocked. $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5.22.04.1 Candidate: 72~ubuntu5.22.04.1 Version table: *** 72~ubuntu5.22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 72~ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 42.4-0ubuntu0.22.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-20 (13 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988333/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988554] Re: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
** Package changed: ubuntu => firefox (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1988554 Title: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 Status in firefox package in Ubuntu: New Bug description: After upgrade 20 to 22 LTS and uncomment WaylandEnable=false to let screenshare works on Teams, Chrome, etc.. ProblemType: Package DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Aug 30 20:09:53 2022 DuplicateSignature: package:firefox:1:1snap1-0ubuntu2 Preparing to unpack .../14-firefox_1%3a1snap1-0ubuntu2_amd64.deb ... => Installing the firefox snap dpkg: error processing archive /tmp/apt-dpkg-install-8w07o6/14-firefox_1%3a1snap1-0ubuntu2_amd64.deb (--unpack): new firefox package pre-installation script subprocess returned error exit status 1 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-10-31 (670 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) 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 Snap: firefox 104.0.1-1 (stable) Snap.Changes: no changes found Title: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-08-30 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1988554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988554] [NEW] package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
You have been subscribed to a public bug: After upgrade 20 to 22 LTS and uncomment WaylandEnable=false to let screenshare works on Teams, Chrome, etc.. ProblemType: Package DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Aug 30 20:09:53 2022 DuplicateSignature: package:firefox:1:1snap1-0ubuntu2 Preparing to unpack .../14-firefox_1%3a1snap1-0ubuntu2_amd64.deb ... => Installing the firefox snap dpkg: error processing archive /tmp/apt-dpkg-install-8w07o6/14-firefox_1%3a1snap1-0ubuntu2_amd64.deb (--unpack): new firefox package pre-installation script subprocess returned error exit status 1 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-10-31 (670 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) 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 Snap: firefox 104.0.1-1 (stable) Snap.Changes: no changes found Title: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-08-30 (2 days ago) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 https://bugs.launchpad.net/bugs/1988554 You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox 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 1988588] Re: Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller Drivers missing
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1988588 Title: Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller Drivers missing Status in xorg package in Ubuntu: New Bug description: Please upgrade the Ubuntu OS and provide Graphics drivers for Ubuntu 22. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 2 20:59:09 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:204d] InstallationDate: Installed on 2022-09-02 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=85140ee7-0511-45cd-aa7c-903f11fd90d1 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2012 dmi.bios.release: 4.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: MLZ7510H.86A.0006.2012.0907.1307 dmi.board.name: DZ75ML-45K dmi.board.vendor: Intel Corporation dmi.board.version: AAG75008-102 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrMLZ7510H.86A.0006.2012.0907.1307:bd09/07/2012:br4.6:svn:pn:pvr:rvnIntelCorporation:rnDZ75ML-45K:rvrAAG75008-102:cvn:ct3:cvr:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110.5+1038 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A 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/1988588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1738774]
So just need to do it manually when UI is scaled >= 175%, the automated resampling and rendering of the SVG *remains* inferior to the project's deployed PNG at the default 100%, i.e. 96dpi resolution. When and if the project can refactor to more effectively use the SVG icon sets, the real issue here, that will change. -- 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/1738774 Title: Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: LibreOffice 5.1.6.2 shipped with Ubuntu 16.04.3 LTS shows pixeled icons on a HiDPI/4K monitor like used in the Dell XPS 13 9360. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1738774/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1738774]
(In reply to bugzilla2 from comment #44) > Ok,time for an update here too :) > I use SVG-Icons quite a long time now, and for me those always look better > than the png versions. I just did an comparison, and the png-version really > looks terrible on an high-dpi monitor with 175% scale. > > As far as I remember, SVG primarily was an issue on Linux? So can't we just > make SVG default on Windows? Not at all! There is no means currently to directly render the SVG into the GUI, meaning they will always be rendered to a bitmap and held in config (per user profile) for the display resolution in use. Look in %APPDATA%\LibreOffice\4\cache for the entire SVG icon theme rendered to PNG at scale. For performance the entire SVG of the active icon theme is parsed and the corresponding PNGs built on first launch. The project deploys resolution appropriate 100% (so 96pdi) scaled PNG at three icon sizes small (sc 16x16) large (lc 24x24) and extra large (32 32x32). They are hand lay ups from the source SVG. They render correctly for most non-HDPI/non-scaledUI and remain appropriate for UI or os/DE scaling up to about 150%. They then start to look pixelated at 150% or above. Since 96-120dpi displays remains the norm for the vast majority of users there is no justification for doing more with the SVG. Only if your os/DE is being scaled (as response to HiDPI, or by user setting) does it make sense to use SVG. Do it manually, the automated resampling and rendering of the SVG is inferior to the system deployed PNG at the default 100%, i.e. 96dpi resolution. The mechanism for "detection" of HiDPI (and so automated use of a resampled set of SVG icons)is "thresholded" at 168 dpi. -- 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/1738774 Title: Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: LibreOffice 5.1.6.2 shipped with Ubuntu 16.04.3 LTS shows pixeled icons on a HiDPI/4K monitor like used in the Dell XPS 13 9360. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1738774/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965563] Re: gnome-extensions-app fails to start [Error reading events from display: Protocol error]
Looks like the bug is fixed in 1.1.10 and what's needed is just an update. -- 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/1965563 Title: gnome-extensions-app fails to start [Error reading events from display: Protocol error] Status in NVIDIA / egl-wayland: New Status in GTK+: Fix Released Status in egl-wayland package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: $ dpkg-query -W gnome-shell-extension-prefs gnome-shell-extension-prefs 42~beta-1ubuntu3 $ gnome-extensions-app Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error Caveat: I currently have a mix of packages from jammy-release and jammy-proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/egl-wayland/+bug/1965563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983794] Re: Evolution not deleting autosave files
** Changed in: evolution (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Triaged
Bug description:
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
This bug was fixed in the package linux - 5.19.0-15.15 --- linux (5.19.0-15.15) kinetic; urgency=medium * kinetic/linux: 5.19.0-15.15 -proposed tracker (LP: #1983335) * Miscellaneous Ubuntu changes - [Config] update annotations to support both gcc-11 and gcc-12 -- Andrea Righi Tue, 02 Aug 2022 09:23:01 +0200 ** Changed in: linux (Ubuntu Kinetic) Status: Invalid => 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/1971418 Title: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 Status in linux package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Invalid Status in urfkill package in Ubuntu: New Status in linux source package in Jammy: Fix Released Status in network-manager source package in Jammy: Invalid Status in urfkill source package in Jammy: New Status in linux source package in Kinetic: Fix Released Status in network-manager source package in Kinetic: Invalid Status in urfkill source package in Kinetic: New Bug description: This is a scripted bug report about ADT failures while running network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971418/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988433] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1988433/+attachment/5613321/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1988433 Title: gnome-software crashed with SIGABRT when clicking on any application to see its details and install Status in gnome-software package in Ubuntu: Invalid Bug description: Clicking on the Install tab followed by the Firefox snap to display more info, gnome-software immediately crashes without displaying more info. Clicking on a deb package like gnome-calculator sometimes the more info is displayed - sometimes it is briefly displayed before crashing again. In-fact this issue occurs on any tab including the front page - it basically stops any application from being installed. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-software 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Thu Sep 1 14:07:02 2022 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2022-07-27 (36 days ago) InstallationMedia: Ubuntu-Budgie 22.10 "Kinetic Kudu" - Alpha amd64 (20220726) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap43~beta-1ubuntu2 JournalErrors: -- No entries -- ProcCmdline: gnome-software RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: gnome-software StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 gs_utils_format_size () () Title: gnome-software crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1988433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988433] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1988433/+attachment/5613322/+files/ThreadStacktrace.txt ** Changed in: gnome-software (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1988433 Title: gnome-software crashed with SIGABRT when clicking on any application to see its details and install Status in gnome-software package in Ubuntu: Invalid Bug description: Clicking on the Install tab followed by the Firefox snap to display more info, gnome-software immediately crashes without displaying more info. Clicking on a deb package like gnome-calculator sometimes the more info is displayed - sometimes it is briefly displayed before crashing again. In-fact this issue occurs on any tab including the front page - it basically stops any application from being installed. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-software 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Thu Sep 1 14:07:02 2022 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2022-07-27 (36 days ago) InstallationMedia: Ubuntu-Budgie 22.10 "Kinetic Kudu" - Alpha amd64 (20220726) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap43~beta-1ubuntu2 JournalErrors: -- No entries -- ProcCmdline: gnome-software RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: gnome-software StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 gs_utils_format_size () () Title: gnome-software crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1988433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988433] Crash report cannot be processed
Thank you for your report! However, processing it in order to get sufficient information for the developers failed (it does not generate a useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report: no debug symbol package found for dbus-user-session no debug symbol package found for fwupd-signed no debug symbol package found for gir1.2-atk-1.0 no debug symbol package found for gir1.2-freedesktop no debug symbol package found for gir1.2-gdkpixbuf-2.0 no debug symbol package found for gir1.2-glib-2.0 no debug symbol package found for gir1.2-goa-1.0 no debug symbol package found for gir1.2-gtk-3.0 no debug symbol package found for gir1.2-handy-1 no debug symbol package found for gir1.2-harfbuzz-0.0 no debug symbol package found for gir1.2-packagekitglib-1.0 no debug symbol package found for gir1.2-pango-1.0 no debug symbol package found for libavahi-common-data no debug symbol package found for libjpeg-turbo8 no debug symbol package found for libperl5.34 no debug symbol package found for perl no debug symbol package found for perl-base no debug symbol package found for policykit-1 no debug symbol package found for secureboot-db no debug symbol package found for systemd-sysv no debug symbol package found for tcl no debug symbol package found for ubuntu-advantage-tools no debug symbol package found for libjpeg-turbo8 outdated debug symbol package for ibus-gtk4: package version 1.5.27-1 dbgsym version 1.5.27-2 outdated debug symbol package for libibus-1.0-5: package version 1.5.27-1 dbgsym version 1.5.27-2 Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report. Thank you for your understanding, and sorry for the inconvenience! ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1988433/+attachment/5612941/+files/CoreDump.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1988433 Title: gnome-software crashed with SIGABRT when clicking on any application to see its details and install Status in gnome-software package in Ubuntu: Invalid Bug description: Clicking on the Install tab followed by the Firefox snap to display more info, gnome-software immediately crashes without displaying more info. Clicking on a deb package like gnome-calculator sometimes the more info is displayed - sometimes it is briefly displayed before crashing again. In-fact this issue occurs on any tab including the front page - it basically stops any application from being installed. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-software 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Thu Sep 1 14:07:02 2022 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2022-07-27 (36 days ago) InstallationMedia: Ubuntu-Budgie 22.10 "Kinetic Kudu" - Alpha amd64 (20220726) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap43~beta-1ubuntu2 JournalErrors: -- No entries -- ProcCmdline: gnome-software RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: gnome-software StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 gs_utils_format_size () () Title: gnome-software crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1988433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988433] gnome-software crashed with SIGABRT when clicking on any application to see its details and install
StacktraceTop: ?? () ?? () ?? () ?? () ?? () -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1988433 Title: gnome-software crashed with SIGABRT when clicking on any application to see its details and install Status in gnome-software package in Ubuntu: Invalid Bug description: Clicking on the Install tab followed by the Firefox snap to display more info, gnome-software immediately crashes without displaying more info. Clicking on a deb package like gnome-calculator sometimes the more info is displayed - sometimes it is briefly displayed before crashing again. In-fact this issue occurs on any tab including the front page - it basically stops any application from being installed. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-software 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Thu Sep 1 14:07:02 2022 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2022-07-27 (36 days ago) InstallationMedia: Ubuntu-Budgie 22.10 "Kinetic Kudu" - Alpha amd64 (20220726) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap43~beta-1ubuntu2 JournalErrors: -- No entries -- ProcCmdline: gnome-software RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: gnome-software StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 gs_utils_format_size () () Title: gnome-software crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1988433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988433] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1988433/+attachment/5613320/+files/Stacktrace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1988433 Title: gnome-software crashed with SIGABRT when clicking on any application to see its details and install Status in gnome-software package in Ubuntu: Invalid Bug description: Clicking on the Install tab followed by the Firefox snap to display more info, gnome-software immediately crashes without displaying more info. Clicking on a deb package like gnome-calculator sometimes the more info is displayed - sometimes it is briefly displayed before crashing again. In-fact this issue occurs on any tab including the front page - it basically stops any application from being installed. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-software 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Thu Sep 1 14:07:02 2022 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2022-07-27 (36 days ago) InstallationMedia: Ubuntu-Budgie 22.10 "Kinetic Kudu" - Alpha amd64 (20220726) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap43~beta-1ubuntu2 JournalErrors: -- No entries -- ProcCmdline: gnome-software RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: gnome-software StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 gs_utils_format_size () () Title: gnome-software crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1988433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988583] Re: ubuntu 18.04 cups network printer not working
also seems that /etc/cups/printer.conf is not being populated with Canon printer info. -- 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/1988583 Title: ubuntu 18.04 cups network printer not working Status in cups package in Ubuntu: New Bug description: all debug info from the ubuntu cup help page looks correct except that none of the snmp command work. netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.1.254 0.0.0.0 UG0 0 0 wlo1 10.0.0.0192.168.168.54 255.255.0.0 UG0 0 0 ppp0 10.0.0.00.0.0.0 255.255.0.0 U 0 0 0 eno2 66.196.209.178 192.168.1.254 255.255.255.255 UGH 0 0 0 wlo1 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eno2 172.16.0.0 192.168.168.54 255.255.0.0 UG0 0 0 ppp0 192.0.2.1 0.0.0.0 255.255.255.255 UH0 0 0 ppp0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlo1 192.168.1.254 0.0.0.0 255.255.255.255 UH0 0 0 wlo1 tbuckley@tbuckley-OptiPlex-7070:/mnt/sda/tbuckley/imxDevopment/sources$ ping 1892.168.1.102 ^C tbuckley@tbuckley-OptiPlex-7070:/mnt/sda/tbuckley/imxDevopment/sources$ ping 192.168.1.102 PING 192.168.1.102 (192.168.1.102) 56(84) bytes of data. 64 bytes from 192.168.1.102: icmp_seq=1 ttl=64 time=50.6 ms 64 bytes from 192.168.1.102: icmp_seq=2 ttl=64 time=5.60 ms 64 bytes from 192.168.1.102: icmp_seq=3 ttl=64 time=5.75 ms ^C --- 192.168.1.102 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 5.603/20.676/50.675/21.212 ms tbuckley@tbuckley-OptiPlex-7070:/mnt/sda/tbuckley/imxDevopment/sources$ nmap 192.168.1.102 Starting Nmap 7.60 ( https://nmap.org ) at 2022-09-02 10:11 CDT Nmap scan report for 192.168.1.102 Host is up (0.035s latency). Not shown: 996 closed ports PORTSTATE SERVICE 80/tcp open http 443/tcp open https 515/tcp open printer 631/tcp open ipp lpinfo -v gives network ipp file cups-brf:/ network https network beh serial serial:/dev/ttyS0?baud=115200 serial serial:/dev/ttyS4?baud=115200 serial serial:/dev/ttyUSB0?baud=230400 serial serial:/dev/ttyUSB1?baud=230400 serial serial:/dev/ttyUSB2?baud=230400 network lpd network http direct hp network socket network ipps direct hpfax network dnssd://Canon%20MG3600%20series._ipp._tcp.local/?uuid=--1000-8000-F4A997389B3C network ipp://389B3C00.local:631/ipp/print network cnijbe2://Canon/?port=net=F4-A9-97-38-9B-3C lpoptions -d Canon_MG3600_series device-uri=ipps://Canon%20MG3600%20series._ipps._tcp.local/ printer-info='Canon MG3600 series' printer-location printer-make-and-model='Canon MG3600 series' printer-type=83890204 tbuckley@tbuckley-OptiPlex-7070:/tmp$ lpoptions device-uri=ipps://Canon%20MG3600%20series._ipps._tcp.local/ printer-info='Canon MG3600 series' printer-location printer-make-and-model='Canon MG3600 series' printer-type=83890204 tbuckley@tbuckley-OptiPlex-7070:/tmp$ lpoptions -l lpoptions: Unable to get PPD file for Canon_MG3600_series: The printer or class does not exist. tbuckley@tbuckley-OptiPlex-7070:/tmp$ lpq lpq: Error - no default destination available. tbuckley@tbuckley-OptiPlex-7070:/tmp$ this use to work but now it seems that cups is not setting the default printer using lpoption or something is failing in the setup. This is happening on a product and on my person ubuntu 18.04 home machine Thanks, Terry 972-814-9422(c) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.9 ProcVersionSignature: Ubuntu 5.4.0-124.140~18.04.1-generic 5.4.195 Uname: Linux 5.4.0-124-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 2 10:13:02 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+bison-elk-cougar-mlk+X53 InstallationDate: Installed on 2019-10-16 (1051 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lpstat: device for SMT300i: bluetooth://00150ee747b7 device for Woosim-WSP-i450: bluetooth://00150ee8b0a7 MachineType: Dell Inc. OptiPlex 7070 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/SMT300i.ppd', '/etc/cups/ppd/Woosim-WSP-i450.ppd'] failed with exit code 2: grep: /etc/cups/ppd/SMT300i.ppd: Permission denied grep: /etc/cups/ppd/Woosim-WSP-i450.ppd: Permission denied
[Desktop-packages] [Bug 1988583] [NEW] ubuntu 18.04 cups network printer not working
Public bug reported: all debug info from the ubuntu cup help page looks correct except that none of the snmp command work. netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.1.254 0.0.0.0 UG0 0 0 wlo1 10.0.0.0192.168.168.54 255.255.0.0 UG0 0 0 ppp0 10.0.0.00.0.0.0 255.255.0.0 U 0 0 0 eno2 66.196.209.178 192.168.1.254 255.255.255.255 UGH 0 0 0 wlo1 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eno2 172.16.0.0 192.168.168.54 255.255.0.0 UG0 0 0 ppp0 192.0.2.1 0.0.0.0 255.255.255.255 UH0 0 0 ppp0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlo1 192.168.1.254 0.0.0.0 255.255.255.255 UH0 0 0 wlo1 tbuckley@tbuckley-OptiPlex-7070:/mnt/sda/tbuckley/imxDevopment/sources$ ping 1892.168.1.102 ^C tbuckley@tbuckley-OptiPlex-7070:/mnt/sda/tbuckley/imxDevopment/sources$ ping 192.168.1.102 PING 192.168.1.102 (192.168.1.102) 56(84) bytes of data. 64 bytes from 192.168.1.102: icmp_seq=1 ttl=64 time=50.6 ms 64 bytes from 192.168.1.102: icmp_seq=2 ttl=64 time=5.60 ms 64 bytes from 192.168.1.102: icmp_seq=3 ttl=64 time=5.75 ms ^C --- 192.168.1.102 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 5.603/20.676/50.675/21.212 ms tbuckley@tbuckley-OptiPlex-7070:/mnt/sda/tbuckley/imxDevopment/sources$ nmap 192.168.1.102 Starting Nmap 7.60 ( https://nmap.org ) at 2022-09-02 10:11 CDT Nmap scan report for 192.168.1.102 Host is up (0.035s latency). Not shown: 996 closed ports PORTSTATE SERVICE 80/tcp open http 443/tcp open https 515/tcp open printer 631/tcp open ipp lpinfo -v gives network ipp file cups-brf:/ network https network beh serial serial:/dev/ttyS0?baud=115200 serial serial:/dev/ttyS4?baud=115200 serial serial:/dev/ttyUSB0?baud=230400 serial serial:/dev/ttyUSB1?baud=230400 serial serial:/dev/ttyUSB2?baud=230400 network lpd network http direct hp network socket network ipps direct hpfax network dnssd://Canon%20MG3600%20series._ipp._tcp.local/?uuid=--1000-8000-F4A997389B3C network ipp://389B3C00.local:631/ipp/print network cnijbe2://Canon/?port=net=F4-A9-97-38-9B-3C lpoptions -d Canon_MG3600_series device-uri=ipps://Canon%20MG3600%20series._ipps._tcp.local/ printer-info='Canon MG3600 series' printer-location printer-make-and-model='Canon MG3600 series' printer-type=83890204 tbuckley@tbuckley-OptiPlex-7070:/tmp$ lpoptions device-uri=ipps://Canon%20MG3600%20series._ipps._tcp.local/ printer-info='Canon MG3600 series' printer-location printer-make-and-model='Canon MG3600 series' printer-type=83890204 tbuckley@tbuckley-OptiPlex-7070:/tmp$ lpoptions -l lpoptions: Unable to get PPD file for Canon_MG3600_series: The printer or class does not exist. tbuckley@tbuckley-OptiPlex-7070:/tmp$ lpq lpq: Error - no default destination available. tbuckley@tbuckley-OptiPlex-7070:/tmp$ this use to work but now it seems that cups is not setting the default printer using lpoption or something is failing in the setup. This is happening on a product and on my person ubuntu 18.04 home machine Thanks, Terry 972-814-9422(c) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.9 ProcVersionSignature: Ubuntu 5.4.0-124.140~18.04.1-generic 5.4.195 Uname: Linux 5.4.0-124-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 2 10:13:02 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+bison-elk-cougar-mlk+X53 InstallationDate: Installed on 2019-10-16 (1051 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lpstat: device for SMT300i: bluetooth://00150ee747b7 device for Woosim-WSP-i450: bluetooth://00150ee8b0a7 MachineType: Dell Inc. OptiPlex 7070 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/SMT300i.ppd', '/etc/cups/ppd/Woosim-WSP-i450.ppd'] failed with exit code 2: grep: /etc/cups/ppd/SMT300i.ppd: Permission denied grep: /etc/cups/ppd/Woosim-WSP-i450.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-124-generic root=UUID=f6d606fa-5095-4c4c-8db8-a34f6acb2fd9 ro mem_sleep_default=deep quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0YNVJG dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
@vanvugt actually my issue must have been different, I'm not using mirror mode and it was happening to me without an external display (as well as with). The workaround did work though. -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923841] Re: [SRU] Increase recording quality
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1923841 Title: [SRU] Increase recording quality Status in HWE Next: Fix Released Status in alsa-utils package in Ubuntu: Fix Released Status in alsa-utils source package in Focal: Fix Released Bug description: [Impact] Audio gets recorded by "arecord" has really bad sound quality when the volume is low. [Fix] https://github.com/alsa-project/alsa-utils/pull/69 Switch the default audio format from 8 bits to 16 bits if hardware supports it. [Test] 1. Plug a microphone. 2. Run `arecord | aplay` and say something to the microphone. 3. Only noise can be heard. With the fix applied, the recording is clear. [Where problems could occur] If there's any hardware falsely advertised to support 16 bits, this change will break them. However, this is effectively using `arecord -f cd` or `arecord -f cdr`, so that's not likely. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1923841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988341] Re: Libreoffice does not recognize OpenJDK installation
** Changed in: libreoffice (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1988341 Title: Libreoffice does not recognize OpenJDK installation Status in libreoffice package in Ubuntu: Invalid Bug description: I want to use the Libreoffice Writer bibliography built-feature which is dependent on a Java installation. After installing the openjdk JRE and JDK packages successfully LO still doesn't recognize it and I cannot use the feature. output of java --version: martin@martin-Inspiron-3542:~$ java --version openjdk 11.0.16 2022-07-19 OpenJDK Runtime Environment (build 11.0.16+8-post-Ubuntu-0ubuntu122.04) OpenJDK 64-Bit Server VM (build 11.0.16+8-post-Ubuntu-0ubuntu122.04, mixed mode, sharing) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Aug 31 22:24:27 2022 InstallationDate: Installed on 2022-08-18 (13 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1988341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988462] Re: Overview search box height is too small at scale 300%
I tried to change resolution and DPI, it didn't help, after that I found the reason: The setting 'Show panel in overview' of the gnome shell extension 'Hide Top Bar'. Should have figured it out long before. -- 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/1988462 Title: Overview search box height is too small at scale 300% Status in gnome-shell package in Ubuntu: New Bug description: I think this part of the software is called unity dash, there is a search field and this field has a broken layout, I can enter text and see results, but I cannot see what was entered. This bug is very severe, an OS that does not allow finding and starting applications isn't very useful, a hotfix or workaround would be very helpful. All distros have severe high DPI bugs in my experience. My screen is 4K and zoom is 300 %, I tried to reduce zoom, but it didn't help. Ubuntu version 22.04. Screenshot is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988462/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951667] Re: [SRU] pulseaudio: restore hdmi audio be active output after resume
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1951667 Title: [SRU] pulseaudio: restore hdmi audio be active output after resume Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in pulseaudio source package in Hirsute: Won't Fix Status in pulseaudio source package in Impish: Fix Released Status in pulseaudio source package in Jammy: Fix Released Bug description: [Impact] On the machines with legacy HDA audio driver, when users plug a hdmi/dp monitor, the active output device is still speaker, need users to manually select the hdmi, then the hdmi audio will be the users' preference, once it is plugged, it should become the active output automatically. But with the current PA, after reboot and suspend/resume, the hdmi can't change to be active output automatically anymore. [Fix] Backport an upstream fix, this will fix the issue of "preferred ports being cleaned by a mistake" [Test] On a machine with legacy HDA audio driver, install the patched pulseaudio, then run 'rm ~/.config/pulse/*; reboot', plug a hdmi monitor, select the hdmi audio to be active, with the hdmi monitor plugged and reboot, suspend and resume, check what is the active output, it is still the hdmi audio. [Where problems could occur] This patch is in the card-restore.c, if it could introduce regression, it will be on the default active input/output devices, for example, users select a input or output device to be active, after reboot, if those devices are available, they should be active, but they could be replaced by other devices if a regression is introduced. But this possibility is very low since we tested the patch on a couple of desktop and laptop machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951667/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
@vanvugt actually my issue must have been different, I'm not using mirror mode and it was happening to me without an external display (as well as with). The workaround did work though. -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938747] Re: [SRU] can't adjust output volume through volume-slider after changing output-device
** Changed in: hwe-next Status: New => 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/1938747 Title: [SRU] can't adjust output volume through volume-slider after changing output-device Status in HWE Next: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Released Status in gnome-control-center source package in Hirsute: Fix Released Status in gnome-control-center source package in Impish: Fix Released Bug description: [Impact] On the machine with the legacy HDA audio driver, suppose the current output device is Speaker, users plug a HDMI monitor and select the HDMI audio as the current output device in the g-c-c, after that the output volume can't be adjusted through the volume-slider in the g-c-c. The UI of the volume-slider could be changed, but the output volume doesn't change. [Fix] Backport 1 upstream commit 0f18a662be6ee0d225249d1ad003dfef69294449. The root cause of this issue is the stream is not got when changing the output-device, the patch adds the getting stream in the update_sink callback, this could fix this bug. [Test] run the patches g-c-c, plug a hdmi monitor, select the HDMI audio from g-c-c, then change the output volume via volume-slider, play music, the sound could be changed with the adjustment with the volume-slider. [Where problems will occur] This patch brings the change to the output and input volume adjustment in the cc-sound-panel, this could make the output/input volume changing not work anymore, for example, the internal speaker or internal mic work well, after plugging a headset, the output device changes to headphone, the intput device changes to Mic, then the volume adjustment doesn't work on headphone and Mic anymore. But this possibility is very low since I tested the patch on different Lenovo and Dell machines, no regression found so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1938747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987038] Re: Fix slow refresh rate when AMD GPU screen in reverse prime mode
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1987038 Title: Fix slow refresh rate when AMD GPU screen in reverse prime mode Status in HWE Next: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu source package in Focal: Confirmed Status in xserver-xorg-video-amdgpu source package in Jammy: Fix Committed Status in xserver-xorg-video-amdgpu source package in Kinetic: Fix Released Bug description: [Impact] When AMD GPU is a GPU screen using reverse prime and its the only display, the fresh rate is very slow. [Fix] Enable present extension for GPU screen so it can be a viable CRTC to be selected. [Test] On a I+A laptop and external displays are routed to AMDGPU, disable internal display like closing lid can observe the issue. With the fix applied, the external display becomes very smooth. [Where problems could occur] I personally don't see why GPU screen can't use present extension, but this is Xorg so there might be some arcane reasons I didn't think of. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987038/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959469] Re: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)
** Changed in: nettle (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nettle in Ubuntu. https://bugs.launchpad.net/bugs/1959469 Title: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto) Status in Ubuntu on IBM z Systems: Fix Released Status in nettle package in Ubuntu: Fix Released Status in nettle package in Debian: Fix Released Bug description: Upgrade nettle to latest version >= 3.7.4 (crypto) Description Upgrade nettle to latest version >= 3.7.4 to provide CPACF Support for Crypto Libraries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1643812] Re: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70].
** Changed in: pulseaudio (Ubuntu) Status: New => Fix Released ** Changed in: pulseaudio (Ubuntu Trusty) Status: In Progress => Won't Fix ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1643812 Title: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70]. Status in HWE Next: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Trusty: Won't Fix Bug description: [Impact] * When plug in headset jack, you can't view any item in unity- control-center, so you can't change the volume. * For the situation of one pulseaudio port has 2 or more jacks, it will bring some change, in the past, if one of the jacks is plugged and other jacks are not plugged, the pulseaudio will print out "Availability of port '%s' is inconsistent!" and will not set this pulseaudio port to available, this is a bug for pulseaudio. * After applying this patch, this issue can be addressed by this patch. [Test Case] * Reproduce steps: 1. Install 14.04.5 image on P50s 2. Login system 3. $ sudo apt-get update 4. $ apt-get dist-upgrade sudo apt-get install --install-recommends linux-generic-lts-xenial xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial libwayland-egl1-mesa-lts-xenial 5. Reboot the system 6. Login system 7. Open Sound setting window 8. Plug headset jack, unplug headset jack. [Regression Potential] * For most of the situations like one pulseaudio port only has one jack, this patch will not bring any change. So there is no potential regression. [Other Info] * The kernel is 4.4.0-47, and the pulseaudio is 1:4.0-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1643812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1715586] Re: Fix shrinking behavior in rrCheckPixmapBounding
** Changed in: xorg-server (Ubuntu Xenial) Status: Fix Committed => Won't Fix ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1715586 Title: Fix shrinking behavior in rrCheckPixmapBounding Status in HWE Next: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Xenial: Won't Fix Bug description: [Impact] When using extended mode on an slave-output connected external monitor, RRSetCrtc calls rrCheckPixmapBounding, which shrinks the output area. It makes the slave-output configured to scan-out an area which completely falls outside of the screen-pixmap, and end up with a black display on the external monitor. We need these two commits: a46afee84d45fbff4e4dad9376afc95bbcc31d7c randr: rrCheckPixmapBounding: do not shrink the screen_pixmap 3b624aa9a9df86dc7d48149e0f18ca223b4355f1 randr: rrCheckPixmapBounding: Do not substract crtc non 0 x,y from screen size [Test Case] Enable NVIDIA PRIME, plug an external monitor, and change to extended mode. [Regression Potential] There should be none, the shrinking behavior wasn't right at the first place. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1715586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968377] Re: [snap] New Chromium icon, not yet used by Snap
Great to see you successfully submitted it! Thank you for your contribution. ** Changed in: chromium-browser (Ubuntu) Status: In Progress => Fix Committed -- 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/1968377 Title: [snap] New Chromium icon, not yet used by Snap Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Google updated the Chrome/Chromium icons recently (see more at https://twitter.com/elvin_not_11/status/1489647032201465861), but I don't think the Snap icon has been updated. Here's the Chromium icons on the Chromium source GitHub mirror, which was easier for me to search: https://github.com/chromium/chromium/tree/main/chrome/app/theme/chromium/linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1968377/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988433] Re: gnome-software crashed with SIGABRT when clicking on any application to see its details and install
This issue occurs on any tab - it basically stops any application from being installed, kind of a critical issue for a software center! ** Summary changed: - gnome-software crashed with SIGABRT when clicking on the firefox snap + gnome-software crashed with SIGABRT when clicking on any application to see its details and install ** Description changed: Clicking on the Install tab followed by the Firefox snap to display more info, gnome-software immediately crashes without displaying more info. Clicking on a deb package like gnome-calculator sometimes the more info is displayed - sometimes it is briefly displayed before crashing again. + + In-fact this issue occurs on any tab including the front page - it + basically stops any application from being installed. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-software 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Thu Sep 1 14:07:02 2022 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2022-07-27 (36 days ago) InstallationMedia: Ubuntu-Budgie 22.10 "Kinetic Kudu" - Alpha amd64 (20220726) InstalledPlugins: - gnome-software-plugin-flatpak N/A - gnome-software-plugin-snap43~beta-1ubuntu2 + gnome-software-plugin-flatpak N/A + gnome-software-plugin-snap43~beta-1ubuntu2 JournalErrors: -- No entries -- ProcCmdline: gnome-software RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: gnome-software StacktraceTop: - () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 - () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 - gs_utils_format_size () - () + () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 + () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 + gs_utils_format_size () + () Title: gnome-software crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo separator: ** Changed in: gnome-software (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1988433 Title: gnome-software crashed with SIGABRT when clicking on any application to see its details and install Status in gnome-software package in Ubuntu: Confirmed Bug description: Clicking on the Install tab followed by the Firefox snap to display more info, gnome-software immediately crashes without displaying more info. Clicking on a deb package like gnome-calculator sometimes the more info is displayed - sometimes it is briefly displayed before crashing again. In-fact this issue occurs on any tab including the front page - it basically stops any application from being installed. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-software 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Thu Sep 1 14:07:02 2022 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2022-07-27 (36 days ago) InstallationMedia: Ubuntu-Budgie 22.10 "Kinetic Kudu" - Alpha amd64 (20220726) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap43~beta-1ubuntu2 JournalErrors: -- No entries -- ProcCmdline: gnome-software RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: gnome-software StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 gs_utils_format_size () () Title: gnome-software crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1988433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1977666] Re: [amdgpu] gnome-shell crash when a monitor is connected
maarten, Please open a new bug by running: ubuntu-bug gnome-shell -- 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/1977666 Title: [amdgpu] gnome-shell crash when a monitor is connected Status in gnome-shell package in Ubuntu: Expired Bug description: Hi, I have just installed Ubuntu 22.04, and I have found a bug when I connect an external monitor to my laptop. Gnome-shell crash, and it seems to be linked with Wayland, the problem doesn't appear with Xorg. Here is my syslog when the crash occurs : Jun 4 23:23:02 Ubuntu-Principal gnome-shell[29275]: g_object_get_qdata: assertion 'G_IS_OBJECT (object)' failed Jun 4 23:23:02 Ubuntu-Principal gnome-shell[29275]: GNOME Shell crashed with signal 11 Jun 4 23:23:02 Ubuntu-Principal gnome-shell[29275]: == Stack trace for context 0x562d4c9ca4b0 == Jun 4 23:23:04 Ubuntu-Principal psensor[31395]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal xdg-desktop-por[29992]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal evolution-alarm[29692]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal xdg-desktop-por[30039]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal gsd-media-keys[29633]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal gsd-wacom[29665]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal gsd-keyboard[29631]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal gsd-power[29638]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal nautilus[29574]: Error reading events from display: Connexion ré-initialisée par le correspondant Jun 4 23:23:04 Ubuntu-Principal xpad[29711]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal update-notifier[31948]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.MediaKeys.service: Main process exited, code=exited, status=1/FAILURE Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.Keyboard.service: Main process exited, code=exited, status=1/FAILURE Jun 4 23:23:04 Ubuntu-Principal gnome-shell[29781]: (EE) failed to write to Xwayland fd: Broken pipe Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.Power.service: Main process exited, code=exited, status=1/FAILURE Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.Wacom.service: Main process exited, code=exited, status=1/FAILURE Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.Shell@wayland.service: Main process exited, code=dumped, status=11/SEGV Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: xdg-desktop-portal-gnome.service: Main process exited, code=exited, status=1/FAILURE Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: xdg-desktop-portal-gnome.service: Failed with result 'exit-code'. Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'. Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.MediaKeys.service: Failed with result 'exit-code'. Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.Keyboard.service: Failed with result 'exit-code'. Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.Power.service: Failed with result 'exit-code'. Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.Wacom.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 4 23:31:50 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-06-06 (363 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1977666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1988230] Re: glib 2.73 breaks modemmanager
** Changed in: glib2.0 (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1988230 Title: glib 2.73 breaks modemmanager Status in GLib: New Status in glib2.0 package in Ubuntu: Triaged Status in modemmanager package in Ubuntu: Triaged Status in glib2.0 package in Debian: Confirmed Bug description: I'm filing this bug in case we want to fix it before letting glib 2.73 in to kinetic. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1988230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1977666] Re: [amdgpu] gnome-shell crash when a monitor is connected
I very much have the same issues still now after the latest updates on 2022-09-02. Is there a way to reopen this bug? I want to help! -- 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/1977666 Title: [amdgpu] gnome-shell crash when a monitor is connected Status in gnome-shell package in Ubuntu: Expired Bug description: Hi, I have just installed Ubuntu 22.04, and I have found a bug when I connect an external monitor to my laptop. Gnome-shell crash, and it seems to be linked with Wayland, the problem doesn't appear with Xorg. Here is my syslog when the crash occurs : Jun 4 23:23:02 Ubuntu-Principal gnome-shell[29275]: g_object_get_qdata: assertion 'G_IS_OBJECT (object)' failed Jun 4 23:23:02 Ubuntu-Principal gnome-shell[29275]: GNOME Shell crashed with signal 11 Jun 4 23:23:02 Ubuntu-Principal gnome-shell[29275]: == Stack trace for context 0x562d4c9ca4b0 == Jun 4 23:23:04 Ubuntu-Principal psensor[31395]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal xdg-desktop-por[29992]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal evolution-alarm[29692]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal xdg-desktop-por[30039]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal gsd-media-keys[29633]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal gsd-wacom[29665]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal gsd-keyboard[29631]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal gsd-power[29638]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal nautilus[29574]: Error reading events from display: Connexion ré-initialisée par le correspondant Jun 4 23:23:04 Ubuntu-Principal xpad[29711]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal update-notifier[31948]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.MediaKeys.service: Main process exited, code=exited, status=1/FAILURE Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.Keyboard.service: Main process exited, code=exited, status=1/FAILURE Jun 4 23:23:04 Ubuntu-Principal gnome-shell[29781]: (EE) failed to write to Xwayland fd: Broken pipe Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.Power.service: Main process exited, code=exited, status=1/FAILURE Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.Wacom.service: Main process exited, code=exited, status=1/FAILURE Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.Shell@wayland.service: Main process exited, code=dumped, status=11/SEGV Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: xdg-desktop-portal-gnome.service: Main process exited, code=exited, status=1/FAILURE Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: xdg-desktop-portal-gnome.service: Failed with result 'exit-code'. Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'. Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.MediaKeys.service: Failed with result 'exit-code'. Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.Keyboard.service: Failed with result 'exit-code'. Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.Power.service: Failed with result 'exit-code'. Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.Wacom.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 4 23:31:50 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-06-06 (363 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-04 (0 days ago) To manage notifications about this bug go to:
[Desktop-packages] [Bug 1987976] Re: firefox black window
Better in bugzilla, please. -- 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/1987976 Title: firefox black window Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 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 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988536] [NEW] Importing Gtk in Python without a valid DISPLAY gives error message
Public bug reported:
Seen on Ubuntu 20.04
libgtk-3-0 version 3.24.20
Use case
We want to check if Gtk is available without actually using it. Once we confirm
that it is available we can start using it, or take another route if it is
unavailable.
Steps to reproduce
==
The display must be unset, which is the default behaviour when ssh:ing to a
machine. Then import Gtk in Python to get the error message.
cendio@ubuntu2004:~$ DISPLAY= python3
Python 3.8.10 (default, Jun 22 2022, 20:18:18)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gi
>>> gi.require_version("Gtk", "3.0")
>>> from gi.repository import Gtk
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
Expected result
===
Importing Gtk should not give error messages.
In Ubuntu 22.04, this issue is not present:
cendio@ubuntu-22:~$ DISPLAY= python3
Python 3.10.4 (main, Apr 2 2022, 09:04:19) [GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gi
>>> gi.require_version("Gtk", "3.0")
>>> from gi.repository import Gtk
Other comments
==
Aside from the error message, everything seem to be working as expected. The
errors are not Gtk errors, so it is unclear how they can be silenced.
** Affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
** Package changed: snapd (Ubuntu) => gtk+3.0 (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1988536
Title:
Importing Gtk in Python without a valid DISPLAY gives error message
Status in gtk+3.0 package in Ubuntu:
New
Bug description:
Seen on Ubuntu 20.04
libgtk-3-0 version 3.24.20
Use case
We want to check if Gtk is available without actually using it. Once we
confirm that it is available we can start using it, or take another route if it
is unavailable.
Steps to reproduce
==
The display must be unset, which is the default behaviour when ssh:ing to a
machine. Then import Gtk in Python to get the error message.
cendio@ubuntu2004:~$ DISPLAY= python3
Python 3.8.10 (default, Jun 22 2022, 20:18:18)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gi
>>> gi.require_version("Gtk", "3.0")
>>> from gi.repository import Gtk
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
Expected result
===
Importing Gtk should not give error messages.
In Ubuntu 22.04, this issue is not present:
cendio@ubuntu-22:~$ DISPLAY= python3
Python 3.10.4 (main, Apr 2 2022, 09:04:19) [GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gi
>>> gi.require_version("Gtk", "3.0")
>>> from gi.repository import Gtk
Other comments
==
Aside from the error message, everything seem to be working as expected. The
errors are not Gtk errors, so it is unclear how they can be silenced.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1988536/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988536] [NEW] Importing Gtk in Python without a valid DISPLAY gives error message
You have been subscribed to a public bug:
Seen on Ubuntu 20.04
libgtk-3-0 version 3.24.20
Use case
We want to check if Gtk is available without actually using it. Once we confirm
that it is available we can start using it, or take another route if it is
unavailable.
Steps to reproduce
==
The display must be unset, which is the default behaviour when ssh:ing to a
machine. Then import Gtk in Python to get the error message.
cendio@ubuntu2004:~$ DISPLAY= python3
Python 3.8.10 (default, Jun 22 2022, 20:18:18)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gi
>>> gi.require_version("Gtk", "3.0")
>>> from gi.repository import Gtk
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
Expected result
===
Importing Gtk should not give error messages.
In Ubuntu 22.04, this issue is not present:
cendio@ubuntu-22:~$ DISPLAY= python3
Python 3.10.4 (main, Apr 2 2022, 09:04:19) [GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gi
>>> gi.require_version("Gtk", "3.0")
>>> from gi.repository import Gtk
Other comments
==
Aside from the error message, everything seem to be working as expected. The
errors are not Gtk errors, so it is unclear how they can be silenced.
** Affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
--
Importing Gtk in Python without a valid DISPLAY gives error message
https://bugs.launchpad.net/bugs/1988536
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 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 1972654] Re: [security review] Sync policykit-1 0.120-6 (main) from Debian experimental
> I do not intend to take further action to modify those packages. If it is a > blocker for Ubuntu > that they are fixed, then someone from Ubuntu will need to do that work. Given the relationship between the packages has now changed - ie. polkitd-pkla is not mutually exclusive from the javascript backend and then allows both legacy pkla policies as well as the "new" javascript policies to be handled - then this is not a blocker anymore from my point of view. I suspect Marc may also agree (especially given the relatively small number of packages in this category). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1972654 Title: [security review] Sync policykit-1 0.120-6 (main) from Debian experimental Status in policykit-1 package in Ubuntu: Confirmed Bug description: Please sync policykit-1 0.120-6 (main) from Debian experimental Changelog entries since current kinetic version 0.105-33: https://tracker.debian.org/media/packages/p/policykit-1/changelog-0.120-6 In particular, see the 0.120-4 changelog entry. I am filing a bug for Security Team review. Previously, Debian and Ubuntu developers agreed to keep using the last version of policykit before it switched to using JavaScript rules. But that was years ago. I believe Debian & Ubuntu are the only distros to have opted out of the new policykit. It is harder to maintain the old style rules when upstream rules use the new format. And it is a challenge to backport security and other bugfixes from the new series, without making mistakes or missing important details. There was a proposal to use duktape instead of mozjs for the JavaScript interpreter but I don't think that's been merged yet. It appears the Debian maintainer is considering switching Debian to the updated version in time for the next Debian Stable release (so uploading to unstable later this year). My requested deadline is August 25, Ubuntu 22.10 Feature Freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1972654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987976] Re: firefox black window
I have two more things to tell you. Where should I write them? In launchpad or bugzilla? -- 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/1987976 Title: firefox black window Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 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 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988422] Re: device discoverable by default
Could you describe what you are doing exactly? The discoverability should be turned on only when the bluetooth settings are open, which is similar to how other platform at doing it... ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Incomplete ** Changed in: gnome-bluetooth (Ubuntu) Status: Confirmed => 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/1988422 Title: device discoverable by default Status in gnome-bluetooth package in Ubuntu: Incomplete Status in gnome-control-center package in Ubuntu: Incomplete Bug description: When bluetooth is turned on ubuntu it is discoverable to all nearby devices. It's strange that any "dumb" bluetooth device offers the option to be turned on but not be discoverable, but gnome bluetooth manager doesn't offer such option. Any device can be paired with a device using the gnome desktop, as long as the user gets the prompt to pair. After that, gnome desktop can receive any file to the downloads folder. There should be an option to make the gnome desktop device not show up to other devices, and another one to restrict what files can be sent via BT to the downloads folder ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgnome-bluetooth13 3.34.5-8 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 12:12:16 2022 InstallationDate: Installed on 2022-08-31 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1988422/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[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(
Hello @vanvugt, I tried with gnome-42.4 with steps below and gnome-shell works fine [Device] Laptop with iGPU (intel) and dGPU (amd) [steps] 1. Plug a monitor on iGPU (intel internal graphic) and plug the other monitor on dGPU (amd gpu) 2. Boot into system 3. Open gnome-settings-daemon and select `Displays` 4. Change the `Primary Display` to the other one [result] no crash with gnome-42.4 Test PPA: https://launchpad.net/~andch/+archive/ubuntu/experimental-package -- 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 1857191] Re: Dark themes don't work well with highlighted current line in gedit
Its still a bug in 22.04. as a normal user i can change the highlight active line setting as a "workaround" but that is not possible if gedit is started as root. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1857191 Title: Dark themes don't work well with highlighted current line in gedit Status in GtkSourceView: Fix Released Status in gtksourceview4 package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Confirmed Bug description: In order to checkout out an old bug report I started gedit, enabled "Highlight current line" and changed the application theme to "Yaru- dark" The current line is highlighted correctly but the text is unreadable because it is too light. The text needs to be much darker. This is not a theme that I would normally use so I'm not too bothered about how the problem is fixed but this configuration makes gedit very difficult to use as you can't actually see the text that you're adding, changing or deleting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 19.10.4 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 21 16:33:03 2019 InstallationDate: Installed on 2019-05-17 (218 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1857191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1979289] Re: Network icon in GNOME title bar flickers sporadically with network bridge
Some additional testing on several computers showed, that this has nothing to do with the network bridge but the flickering icon already appears once you install QEMU from the apt sources. -- 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/1979289 Title: Network icon in GNOME title bar flickers sporadically with network bridge Status in gnome-shell package in Ubuntu: New Bug description: After creating a network bridge (for QEMU), the network connection on the top right flickers, which means it sporadically disappears and then appears again after a short while. The time between the icon disappearing ranges between 5 minutes and 45 minutes, most of the time it's around 10 minutes. The time between the icon re-appearing ranges between 1 seconds and 2 minutes, most of the time it's gone for around 3 seconds. There's no apparent correlation to any user behaviour, it happens independent of the network being idle or under load. The physical network traffic is not affected, i.e. the network connection still works while the icon is gone. The network bridge was created with 'nmcli' according to this guide and works flawlessly: https://www.answertopia.com/ubuntu/creating-an- ubuntu-kvm-networked-bridge-interface/ Description: Ubuntu 22.04 LTS Release: 22.04 package and configuration details: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1979289/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
