[Desktop-packages] [Bug 1945856] Re: Need update to 3.21.8 for ARM
Okay, I will wait for the version with the ability to scan) Thank's) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1945856 Title: Need update to 3.21.8 for ARM Status in hplip package in Ubuntu: New Bug description: Need update to 3.21.8 for ARM because in this version HP added HP Smart Tank 500 and more printers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1945856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1945513] Re: Error when changing regional format
For the record, this is related to bug #930785. I think the fix of that bug is as far as we will get. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1945513 Title: Error when changing regional format Status in language-selector package in Ubuntu: Incomplete Bug description: Using the daily iso, but the same with focal, groovy, hirsute. When I choose a new locale, Occitan, it gets installed and everything. But when I click the Regional formats tab to choose Occitan from France, the overview is buggy. Here with Ubuntu Mate, but the same everywhere else it's the same. I have to restart, maybe log out and in again would be enough, to have the correct display. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1945513/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1945880] [NEW] [X570 AORUS ELITE, Realtek ALCS1200A, Green Line Out, Rear] Playback problem
Public bug reported: Ground noise when starting system - only goes away when I play back something or when there are system sounds. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 3 02:17:32 2021 InstallationDate: Installed on 2021-10-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: LANGUAGE=de_CH:de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_CH.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [X570 AORUS ELITE, Realtek ALCS1200A, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33h dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33h:bd04/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:skuDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1945880 Title: [X570 AORUS ELITE, Realtek ALCS1200A, Green Line Out, Rear] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: Ground noise when starting system - only goes away when I play back something or when there are system sounds. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 3 02:17:32 2021 InstallationDate: Installed on 2021-10-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: LANGUAGE=de_CH:de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_CH.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [X570 AORUS ELITE, Realtek ALCS1200A, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33h dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33h:bd04/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:skuDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1945880/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1945853] Re: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref()
*** This bug is a duplicate of bug 1943369 *** https://bugs.launchpad.net/bugs/1943369 Norbert, I tested an .iso image with VirtualBox and saw Apport window when I was going to turn off the virtual machine. -- 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/1945853 Title: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref() Status in glib2.0 package in Ubuntu: Confirmed Status in mate-screensaver package in Ubuntu: Confirmed Bug description: I found this casually when I was testing the latest Ubuntu MATE 21.10 Beta. I have no idea what may cause the crash. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: mate-screensaver 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: MATE Date: Sat Oct 2 07:53:08 2021 ExecutablePath: /usr/bin/mate-screensaver ExecutableTimestamp: 1629565330 LiveMediaBuild: Ubuntu-MATE 21.10 "Impish Indri" - Beta amd64 (20211002) ProcCmdline: mate-screensaver ProcCwd: /home/ubuntu-mate ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fc222155b07 : lock addl $0x1,(%rdi) PC (0x7fc222155b07) ok source "$0x1" ok destination "(%rdi)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: mate-screensaver StacktraceTop: matemenu_tree_item_ref () from /lib/x86_64-linux-gnu/libmate-menu.so.2 gs_theme_manager_lookup_theme_info () ?? () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1945853/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1945100] Re: Widevine violates the sandbox and crashes
Still broken in firefox 93.0+build1-0ubuntu2 (Impish). -- 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/1945100 Title: Widevine violates the sandbox and crashes Status in firefox package in Ubuntu: Confirmed Bug description: I just updated for Impish Indri beta release but Firefox's Widevine is always crashing. When I disable the GMP sandbox (setting the environment variable MOZ_DISABLE_GMP_SANDBOX to 1) it works fine. I'm using Firefox 92.0.1 installed via .deb package. Here is some console logs showing the violations: ➜ firefox --ProfileManager Gtk-Message: 09:58:02.539: Failed to load module "appmenu-gtk-module" ###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost Gtk-Message: 09:58:10.435: Failed to load module "appmenu-gtk-module" Sandbox: attempt to open unexpected file /usr/lib/firefox/librt.so.1 Sandbox: attempt to open unexpected file /lib/x86_64-linux-gnu/librt.so.1 Sandbox: attempt to open unexpected file /lib/x86_64-linux-gnu/glibc-hwcaps/x86-64-v3/librt.so.1 Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 4294967196 140721817045120 140721817045312 0 4294967295 140721817045120. Sandbox: attempt to open unexpected file /lib/x86_64-linux-gnu/glibc-hwcaps/x86-64-v2/librt.so.1 Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 4294967196 140721817045120 140721817045312 0 4294967295 140721817045120. Sandbox: attempt to open unexpected file /lib/x86_64-linux-gnu/tls/haswell/x86_64/librt.so.1 Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 4294967196 140721817045120 140721817045312 0 4294967295 140721817045120. Sandbox: attempt to open unexpected file /lib/x86_64-linux-gnu/tls/haswell/librt.so.1 Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 4294967196 140721817045120 140721817045312 0 4294967295 140721817045120. Sandbox: attempt to open unexpected file /lib/x86_64-linux-gnu/tls/x86_64/librt.so.1 Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 4294967196 140721817045120 140721817045312 0 4294967295 140721817045120. Sandbox: attempt to open unexpected file /lib/x86_64-linux-gnu/tls/librt.so.1 Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 4294967196 140721817045120 140721817045312 0 4294967295 140721817045120. Sandbox: attempt to open unexpected file /lib/x86_64-linux-gnu/haswell/x86_64/librt.so.1 Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 4294967196 140721817045120 140721817045312 0 4294967295 140721817045120. Sandbox: attempt to open unexpected file /lib/x86_64-linux-gnu/haswell/librt.so.1 Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 4294967196 140721817045120 140721817045312 0 4294967295 140721817045120. Sandbox: attempt to open unexpected file /lib/x86_64-linux-gnu/x86_64/librt.so.1 Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 4294967196 140721817045120 140721817045312 0 4294967295 140721817045120. Sandbox: attempt to open unexpected file /lib/x86_64-linux-gnu/librt.so.1 Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 4294967196 140721817045120 140721817045312 0 4294967295 140721817045120. Sandbox: attempt to open unexpected file /usr/lib/x86_64-linux-gnu/glibc-hwcaps/x86-64-v3/librt.so.1 Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 4294967196 140721817045120 140721817045312 0 4294967295 140721817045120. Sandbox: attempt to open unexpected file /usr/lib/x86_64-linux-gnu/glibc-hwcaps/x86-64-v2/librt.so.1 Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 4294967196 140721817045120 140721817045312 0 4294967295 140721817045120. Sandbox: attempt to open unexpected file /usr/lib/x86_64-linux-gnu/tls/haswell/x86_64/librt.so.1 Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 4294967196 140721817045120 140721817045312 0 4294967295 140721817045120. Sandbox: attempt to open unexpected file /usr/lib/x86_64-linux-gnu/tls/haswell/librt.so.1 Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 4294967196 140721817045120 140721817045312 0 4294967295 140721817045120. Sandbox: attempt to open unexpected file /usr/lib/x86_64-linux-gnu/tls/x86_64/librt.so.1 Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 4294967196 140721817045120 140721817045312 0 4294967295 140721817045120. Sandbox: attempt to open unexpected file /usr/lib/x86_64-linux-gnu/tls/librt.so.1 Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 4294967196 140721817045120 140721817045312 0 4294967295 140721817045120. Sandbox: attempt
[Desktop-packages] [Bug 1873365] Re: gedit icon is too pale
** Changed in: yaru-theme (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1873365 Title: gedit icon is too pale Status in yaru-theme package in Ubuntu: Fix Released Bug description: The grey lines representing text on the paper sheet and the tip of the pencil in the icon are too pale. They are almost invisible so that the gedit icon is seen as a white rectangle crossed by a blue bar. Before focal, the icons of gedit and Evince used to have similar design, that is they both were pale. Now in focal, the Evince icon is redesigned and it is more clear with more contrast. The suggestion is to apply similar modifications to the gedit icon to make it more clear. For example, it can use the same dark gray color of the text lines as Evince icon. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-icon 20.04.5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 01:10:13 2020 Dependencies: InstallationDate: Installed on 2019-04-25 (357 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1873365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thunderbird (Ubuntu) Status: New => Confirmed -- 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/1849346 Title: [snap] kerberos GSSAPI no longer works after deb->snap transition Status in chromium-browser package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: I configure AuthServerWhitelist as documented: https://www.chromium.org/developers/design-documents/http- authentication and can see my whitelisted domains in chrome://policy/ but websites that used to work with SPNEGO/GSSAPI/kerberos no longer work. I'm guessing the snap needs some sort of permission to use the kerberos ticket cache (or the plumbing to do so doesn't exist...). I can confirm that Chrome has the desired behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921963] Re: SRU 3.36.9
** Changed in: yaru-theme (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1921963 Title: SRU 3.36.9 Status in gnome-shell package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Released Status in yaru-theme source package in Focal: Fix Released Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.36.9 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse [ Regression potential ] Login a11y changed and so the usage of icons for notifications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1921963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930101] Re: gnome-shell calendar week numbers may not be vertically centered
** Changed in: yaru-theme (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1930101 Title: gnome-shell calendar week numbers may not be vertically centered Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Focal: Fix Released Bug description: [ Impact ] Week numbers in gnome shell calendar are not vertically centered, with some fonts configurations (as in [1]). [ Test case ] 1. Open the gnome-shell calendar 2. Ensure that week numbers are vertically centered [ Regression potential ] Week numbers have wrong padding [1] https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1415 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1930101/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1945871] [NEW] Right-clicking in Chrome's "Save As" dialog crashes xdg-desktop-portal-gtk
Public bug reported: Ubuntu version: Ubuntu 21.04 xdg-desktop-portal-gtk version: 1.8.0-1 google-chrome-stable version: 94.0.4606.61-1 Reproduction: 1. Open Google Chrome - this has been occurring for several months, so different versions, but currently the one I have installed is: 94.0.4606.61 (Official Build) (64-bit) 2. Right-click on any page, click "Save As" (or download a file, which opens the same dialog) Expected behavior: A context menu with items such as "Open With File Manager", "Rename", etc. Actual behavior: "Save As" dialog is closed, and apport is triggered for /usr/libexec/xdg-desktop-portal-gtk (I *think* I attached a stack trace here). Other apps (firefox, gedit) work as expected here, the problem appears specific to Chrome - but Chrome isn't crashing - xdg-desktop-portal-gtk is. Therefore I'm starting by filing a bug report here. Unfortunately Chrome isn't reporting anything to stdout/stderr about this (only some unrelated messages about bluetooth). Note: I've attached /var/crash/_usr_libexec_xdg-desktop-portal- gtk.1000.crash. However, /var/crash/_usr_libexec_xdg-desktop-portal- gtk.1000.uploaded exists, with contents 68511cc2-2374-11ec-b3f5-fa163e6cac46. I don't see that this actually opened a bug anywhere though. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xdg-desktop-portal-gtk 1.8.0-1 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 2 18:06:52 2021 InstallationDate: Installed on 2019-06-25 (829 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xdg-desktop-portal-gtk UpgradeStatus: Upgraded to hirsute on 2021-07-30 (63 days ago) ** Affects: xdg-desktop-portal-gtk (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session ** Attachment added: "Crash report" https://bugs.launchpad.net/bugs/1945871/+attachment/5530166/+files/_usr_libexec_xdg-desktop-portal-gtk.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1945871 Title: Right-clicking in Chrome's "Save As" dialog crashes xdg-desktop- portal-gtk Status in xdg-desktop-portal-gtk package in Ubuntu: New Bug description: Ubuntu version: Ubuntu 21.04 xdg-desktop-portal-gtk version: 1.8.0-1 google-chrome-stable version: 94.0.4606.61-1 Reproduction: 1. Open Google Chrome - this has been occurring for several months, so different versions, but currently the one I have installed is: 94.0.4606.61 (Official Build) (64-bit) 2. Right-click on any page, click "Save As" (or download a file, which opens the same dialog) Expected behavior: A context menu with items such as "Open With File Manager", "Rename", etc. Actual behavior: "Save As" dialog is closed, and apport is triggered for /usr/libexec/xdg-desktop-portal-gtk (I *think* I attached a stack trace here). Other apps (firefox, gedit) work as expected here, the problem appears specific to Chrome - but Chrome isn't crashing - xdg-desktop-portal- gtk is. Therefore I'm starting by filing a bug report here. Unfortunately Chrome isn't reporting anything to stdout/stderr about this (only some unrelated messages about bluetooth). Note: I've attached /var/crash/_usr_libexec_xdg-desktop-portal- gtk.1000.crash. However, /var/crash/_usr_libexec_xdg-desktop-portal- gtk.1000.uploaded exists, with contents 68511cc2-2374-11ec-b3f5-fa163e6cac46. I don't see that this actually opened a bug anywhere though. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xdg-desktop-portal-gtk 1.8.0-1 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 2 18:06:52 2021 InstallationDate: Installed on 2019-06-25 (829 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xdg-desktop-portal-gtk UpgradeStatus: Upgraded to hirsute on 2021-07-30 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1945871/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1945853] Re: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref()
*** This bug is a duplicate of bug 1943369 *** https://bugs.launchpad.net/bugs/1943369 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: glib2.0 (Ubuntu) Status: New => 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/1945853 Title: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref() Status in glib2.0 package in Ubuntu: Confirmed Status in mate-screensaver package in Ubuntu: Confirmed Bug description: I found this casually when I was testing the latest Ubuntu MATE 21.10 Beta. I have no idea what may cause the crash. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: mate-screensaver 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: MATE Date: Sat Oct 2 07:53:08 2021 ExecutablePath: /usr/bin/mate-screensaver ExecutableTimestamp: 1629565330 LiveMediaBuild: Ubuntu-MATE 21.10 "Impish Indri" - Beta amd64 (20211002) ProcCmdline: mate-screensaver ProcCwd: /home/ubuntu-mate ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fc222155b07 : lock addl $0x1,(%rdi) PC (0x7fc222155b07) ok source "$0x1" ok destination "(%rdi)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: mate-screensaver StacktraceTop: matemenu_tree_item_ref () from /lib/x86_64-linux-gnu/libmate-menu.so.2 gs_theme_manager_lookup_theme_info () ?? () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1945853/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1945853] Re: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref()
*** This bug is a duplicate of bug 1943369 *** https://bugs.launchpad.net/bugs/1943369 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mate-screensaver (Ubuntu) Status: New => 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/1945853 Title: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref() Status in glib2.0 package in Ubuntu: Confirmed Status in mate-screensaver package in Ubuntu: Confirmed Bug description: I found this casually when I was testing the latest Ubuntu MATE 21.10 Beta. I have no idea what may cause the crash. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: mate-screensaver 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: MATE Date: Sat Oct 2 07:53:08 2021 ExecutablePath: /usr/bin/mate-screensaver ExecutableTimestamp: 1629565330 LiveMediaBuild: Ubuntu-MATE 21.10 "Impish Indri" - Beta amd64 (20211002) ProcCmdline: mate-screensaver ProcCwd: /home/ubuntu-mate ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fc222155b07 : lock addl $0x1,(%rdi) PC (0x7fc222155b07) ok source "$0x1" ok destination "(%rdi)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: mate-screensaver StacktraceTop: matemenu_tree_item_ref () from /lib/x86_64-linux-gnu/libmate-menu.so.2 gs_theme_manager_lookup_theme_info () ?? () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1945853/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1945853] Re: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref()
*** This bug is a duplicate of bug 1943369 *** https://bugs.launchpad.net/bugs/1943369 @Nicholas Guriev just curious which hardware do you use? I see the same behavior on old Lenovo SL500 with Core2Duo T9550. ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- 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/1945853 Title: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref() Status in glib2.0 package in Ubuntu: Confirmed Status in mate-screensaver package in Ubuntu: Confirmed Bug description: I found this casually when I was testing the latest Ubuntu MATE 21.10 Beta. I have no idea what may cause the crash. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: mate-screensaver 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: MATE Date: Sat Oct 2 07:53:08 2021 ExecutablePath: /usr/bin/mate-screensaver ExecutableTimestamp: 1629565330 LiveMediaBuild: Ubuntu-MATE 21.10 "Impish Indri" - Beta amd64 (20211002) ProcCmdline: mate-screensaver ProcCwd: /home/ubuntu-mate ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fc222155b07 : lock addl $0x1,(%rdi) PC (0x7fc222155b07) ok source "$0x1" ok destination "(%rdi)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: mate-screensaver StacktraceTop: matemenu_tree_item_ref () from /lib/x86_64-linux-gnu/libmate-menu.so.2 gs_theme_manager_lookup_theme_info () ?? () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1945853/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1945856] Re: Need update to 3.21.8 for ARM
If you only need printing (and not scanning) functionality, you can also switch to the HPLIP Snap: https://snapcraft.io/hplip-printer-app This works with all (not too old, Snap must be supported) Ubuntu versions and many other distributions. It will also be regularly updated and the updates continue to work with the same wide range of distribution. Especially you can by this use an HPLIP which was released later than the release of your distro. Support for the proprietary plugin and for scanning is in the works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1945856 Title: Need update to 3.21.8 for ARM Status in hplip package in Ubuntu: New Bug description: Need update to 3.21.8 for ARM because in this version HP added HP Smart Tank 500 and more printers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1945856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883608] Re: [USB-Audio - UMC204HD 192k, playback] Playback problem
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1883608 Title: [USB-Audio - UMC204HD 192k, playback] Playback problem Status in pulseaudio package in Ubuntu: Confirmed Bug description: I want to split the 4.0 output into 2x2.0 outputs. This is my config for /etc/pulse/default.pa load-module module-remap-sink sink_name=behringera sink_properties="device.description='Behringer Output A (1 and 2)'" remix=no master=alsa_output.usb-BEHRINGER_UMC204HD_192k-00.analog-surround-40 channels=2 master_channel_map=front-left,front-right channel_map=left,right load-module module-remap-sink sink_name=behringerb sink_properties="device.description='Behringer Output B (3 and 4)'" remix=no master=alsa_output.usb-BEHRINGER_UMC204HD_192k-00.analog-surround-40 channels=2 master_channel_map=rear-left,rear-right channel_map=left,right I have tested this config on Ubuntu 18.04, Debian, Fedora 30, it works on all of them. But does not work on Ubuntu 20.04, nor Fedora 32. Both 20.04 and f32 use version 13.99.1 of Pulseaudio, so I suspect the problem to be with this version. When I speak about A and B, I am referring to the device description given in the 2 lines above, line 1 being A and line 2 being B. What is happening on 20.04 and f32 is if I comment out A, then B will work. If I comment out B, A will work, but both A and B are defined, then only A will work. If B is defined first, and then A, something else weird happens where A will work, but is sent out through B, and B will work as expected. A discussion on Reddit, another user has version 13.0 on NixOS and his similar UMC404HD works fine. Here is a link to the info on Reddit: https://www.reddit.com/r/linuxaudio/comments/fqmhbe/pulseaudio_and_multichannel_interfaces/ftkq7ov I know this is probably a pulseaudio bug, but I could not figure out how to submit a bug report to them. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: angus 5429 F pulseaudio /dev/snd/pcmC0D0p: angus 5429 F...m pulseaudio /dev/snd/controlC3: angus 5429 F pulseaudio /dev/snd/controlC2: angus 5429 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 15 23:14:49 2020 InstallationDate: Installed on 2020-04-25 (51 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:U192k successful Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio Generic Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [USB-Audio - UMC204HD 192k, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.H0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 KRAIT GAMING (MS-7A33) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.H0:bd01/21/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A33:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX370KRAITGAMING(MS-7A33):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A33 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1883608/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1945645] Re: cups-pdf prints blank pages
Thanks. That confirms my suspicions. Debian already has a patch for CUPS-PDF (pending import into Ubuntu) that removes the warning about deprecated Ghostscript options. However, it seems that Ghostscript 9.54 brought in even more unexpected changes that somehow break CUPS-PDF. This will require additional investigation. -- 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/1945645 Title: cups-pdf prints blank pages Status in cups package in Ubuntu: Confirmed Status in cups-pdf package in Ubuntu: Confirmed Status in ghostscript package in Ubuntu: Confirmed Status in ghostscript package in Debian: New Bug description: after updating from ubuntu 21.04 to ubuntu 21.10 the virtual pdf printer started to print blank pages (to create washed pdf files) printer-driver-cups-pdf, version 3.0.1-10 Description:Ubuntu Impish Indri (development branch) Release:21.10 printer-driver-cups-pdf: Installed: 3.0.1-10 Candidate: 3.0.1-10 Version table: *** 3.0.1-10 500 500 http://bg.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: printer-driver-cups-pdf 3.0.1-10 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 30 15:56:51 2021 InstallationDate: Installed on 2020-03-17 (561 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200205) Lpstat: device for PDF: cups-pdf:/ Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied SourcePackage: cups-pdf UpgradeStatus: Upgraded to impish on 2021-09-28 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1945645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1945645] Re: cups-pdf prints blank pages
With the versions from 21.04 everything works fine ghostscript: Installed: 9.53.3~dfsg-7ubuntu0.1 Candidate: 9.54.0~dfsg1-0ubuntu2 Version table: 9.54.0~dfsg1-0ubuntu2 500 500 http://bg.archive.ubuntu.com/ubuntu impish/main amd64 Packages *** 9.53.3~dfsg-7ubuntu0.1 100 100 /var/lib/dpkg/status libgs9: Installed: 9.53.3~dfsg-7ubuntu0.1 Candidate: 9.54.0~dfsg1-0ubuntu2 Version table: 9.54.0~dfsg1-0ubuntu2 500 500 http://bg.archive.ubuntu.com/ubuntu impish/main amd64 Packages *** 9.53.3~dfsg-7ubuntu0.1 100 100 /var/lib/dpkg/status libgs9-common: Installed: 9.53.3~dfsg-7ubuntu0.1 Candidate: 9.54.0~dfsg1-0ubuntu2 Version table: 9.54.0~dfsg1-0ubuntu2 500 500 http://bg.archive.ubuntu.com/ubuntu impish/main amd64 Packages 500 http://bg.archive.ubuntu.com/ubuntu impish/main i386 Packages *** 9.53.3~dfsg-7ubuntu0.1 100 100 /var/lib/dpkg/status -- 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/1945645 Title: cups-pdf prints blank pages Status in cups package in Ubuntu: Confirmed Status in cups-pdf package in Ubuntu: Confirmed Status in ghostscript package in Ubuntu: Confirmed Status in ghostscript package in Debian: New Bug description: after updating from ubuntu 21.04 to ubuntu 21.10 the virtual pdf printer started to print blank pages (to create washed pdf files) printer-driver-cups-pdf, version 3.0.1-10 Description:Ubuntu Impish Indri (development branch) Release:21.10 printer-driver-cups-pdf: Installed: 3.0.1-10 Candidate: 3.0.1-10 Version table: *** 3.0.1-10 500 500 http://bg.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: printer-driver-cups-pdf 3.0.1-10 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 30 15:56:51 2021 InstallationDate: Installed on 2020-03-17 (561 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200205) Lpstat: device for PDF: cups-pdf:/ Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied SourcePackage: cups-pdf UpgradeStatus: Upgraded to impish on 2021-09-28 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1945645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1945856] [NEW] Need update to 3.21.8 for ARM
Public bug reported: Need update to 3.21.8 for ARM because in this version HP added HP Smart Tank 500 and more printers ** Affects: hplip (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1945856 Title: Need update to 3.21.8 for ARM Status in hplip package in Ubuntu: New Bug description: Need update to 3.21.8 for ARM because in this version HP added HP Smart Tank 500 and more printers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1945856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1943849] Re: improve the apearance-page in gnome-control-center
After: - GtkFlowBoxChild does not move to next line when resized and stays in center - GtkFlowBoxChild does not have orange over Text(light) when selected. Orange is only around border of GtkFlowBoxChild. - GtkFlowBoxChild uses new-Yaru look screenshot and removes Purple- gradient as background. - Dock section now has rounded corners for GtkListBox ** Attachment added: "after the MR" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1943849/+attachment/5530080/+files/Peek%202021-10-02%2015-11.mp4 ** Summary changed: - improve the apearance-page in gnome-control-center + [FFe] improve the appearance-page in gnome-control-center -- 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/1943849 Title: [FFe] improve the appearance-page in gnome-control-center Status in gnome-control-center package in Ubuntu: In Progress Bug description: [Changes:] 1. The Appearance-panel in gnome-control-center uses 2 GtkBox to center the Windows color one at the start and one at end. The problem in behavior arises when the window is resized one of the GtkFlowBoxChild moves to next line even though there is plenty of space in the current line or when the Window is maximized. Specially noticed with lower-resolution dispalys With the use of HdyPrefrencesPage and HdyPrefrencesGroup, the Window colors section stays fixed even when the window is resized or maximized. 2. The Appearance-panel has extra border around the Page, HdyPrefrencesPage removes the extra-border 3. The Window colors section uses thumbnails that do not resemble with current Yaru's look offered in 21.10 and have purple-gradient color as the background. With the use of style=content-view and icon-dropshadow the thumbnails stand out better in the absence of purple gardient background. 4. The Window colors section has orange as the color for the selected GtkFlowBoxChild, With the use of margin as 2px the selected GtkFlowBoxChild has a 2px orange-color border. 5. The Dock-section makes use of rounded corners around GtkListBox by using style=content 6. The Dock-section makes use of HdyActionRow to replace the use of GtkGrid, GtkLabel, GtkListBoxRow. Orignal-issue: https://gitlab.gnome.org/Community/Ubuntu/gnome-control-center/-/issues/3 MR: https://gitlab.gnome.org/Community/Ubuntu/gnome-control- center/-/merge_requests/4 see: screenshots and screen-recordings below for before and after To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1943849/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1943849] Re: improve the apearance-page in gnome-control-center
Before: - GtkFlowBoxChild moves to next-line when resizing. - GtkFlowBoxChild has orange over Text(light) when selected - GtkFlowBoxChild has old-Yaru look for screenshots - Appearance has extra-border around the page ** Description changed: - Context: - - The current Appearance page in ubuntu 21.10 development-builds has few issues as brought-up in the Ubuntu's gitlab repository: https://gitlab.gnome.org/Community/Ubuntu/gnome-control-center/-/issues/3 + [Changes:] - Proposal: - - MR for this issue is also created on Ubuntu's gitlab repository: https://gitlab.gnome.org/Community/Ubuntu/gnome-control-center/-/merge_requests/4 + 1. The Appearance-panel in gnome-control-center uses 2 GtkBox to center + the Windows color one at the start and one at end. The problem in + behavior arises when the window is resized one of the GtkFlowBoxChild + moves to next line even though there is plenty of space in the current + line or when the Window is maximized. Specially noticed with lower- + resolution dispalys + + With the use of HdyPrefrencesPage and HdyPrefrencesGroup, the Window + colors section stays fixed even when the window is resized or maximized. + + 2. The Appearance-panel has extra border around the Page, + HdyPrefrencesPage removes the extra-border + + 3. The Window colors section uses thumbnails that do not resemble with + current Yaru's look offered in 21.10 and have purple-gradient color as + the background. + + With the use of style=content-view and icon-dropshadow the thumbnails + stand out better in the absence of purple gardient background. + + 4. The Window colors section has orange as the color for the selected + GtkFlowBoxChild, With the use of margin as 2px the selected + GtkFlowBoxChild has a 2px orange-color border. + + + 5. The Dock-section makes use of rounded corners around GtkListBox by using style=content + + 6. The Dock-section makes use of HdyActionRow to replace the use of + GtkGrid, GtkLabel, GtkListBoxRow. + + + Orignal-issue: https://gitlab.gnome.org/Community/Ubuntu/gnome-control-center/-/issues/3 + + MR: https://gitlab.gnome.org/Community/Ubuntu/gnome-control- + center/-/merge_requests/4 + + see: screenshots and screen-recordings below for before and after ** Attachment added: "before the MR" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1943849/+attachment/5530075/+files/Peek%202021-10-02%2015-12.mp4 -- 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/1943849 Title: [FFe] improve the appearance-page in gnome-control-center Status in gnome-control-center package in Ubuntu: In Progress Bug description: [Changes:] 1. The Appearance-panel in gnome-control-center uses 2 GtkBox to center the Windows color one at the start and one at end. The problem in behavior arises when the window is resized one of the GtkFlowBoxChild moves to next line even though there is plenty of space in the current line or when the Window is maximized. Specially noticed with lower-resolution dispalys With the use of HdyPrefrencesPage and HdyPrefrencesGroup, the Window colors section stays fixed even when the window is resized or maximized. 2. The Appearance-panel has extra border around the Page, HdyPrefrencesPage removes the extra-border 3. The Window colors section uses thumbnails that do not resemble with current Yaru's look offered in 21.10 and have purple-gradient color as the background. With the use of style=content-view and icon-dropshadow the thumbnails stand out better in the absence of purple gardient background. 4. The Window colors section has orange as the color for the selected GtkFlowBoxChild, With the use of margin as 2px the selected GtkFlowBoxChild has a 2px orange-color border. 5. The Dock-section makes use of rounded corners around GtkListBox by using style=content 6. The Dock-section makes use of HdyActionRow to replace the use of GtkGrid, GtkLabel, GtkListBoxRow. Orignal-issue: https://gitlab.gnome.org/Community/Ubuntu/gnome-control-center/-/issues/3 MR: https://gitlab.gnome.org/Community/Ubuntu/gnome-control- center/-/merge_requests/4 see: screenshots and screen-recordings below for before and after To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1943849/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1945852] [NEW] sound strange noise - pulseaudio
Public bug reported: The sound from the speakers and headphones is distorted when the system startup. Has some strange disturbance in sound. If I issue "pulseausio -k; pulseaudio --start" the sound is correct but when another startup problem is come back. Reinstalling pulseaudio and alsa does not help. Actually my pulseaudio version is 1:13.99.1-1ubuntu3.11. I try under ubuntu 20.04.3 LTS and 21.04 but it is the same bug. Installing another newer kernel doesn't help either. The card is HDA Intel PCH, Cirrus Logic CS8409 / CS42L42 chip (Dell Vostro 3500). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bartek 3166 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 2 09:02:58 2021 InstallationDate: Installed on 2021-10-02 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0GGCMJ dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3500:pvr:sku0A24:rvnDellInc.:rn0GGCMJ:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3500 dmi.product.sku: 0A24 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1945852 Title: sound strange noise - pulseaudio Status in pulseaudio package in Ubuntu: New Bug description: The sound from the speakers and headphones is distorted when the system startup. Has some strange disturbance in sound. If I issue "pulseausio -k; pulseaudio --start" the sound is correct but when another startup problem is come back. Reinstalling pulseaudio and alsa does not help. Actually my pulseaudio version is 1:13.99.1-1ubuntu3.11. I try under ubuntu 20.04.3 LTS and 21.04 but it is the same bug. Installing another newer kernel doesn't help either. The card is HDA Intel PCH, Cirrus Logic CS8409 / CS42L42 chip (Dell Vostro 3500). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bartek 3166 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 2 09:02:58 2021 InstallationDate: Installed on 2021-10-02 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0GGCMJ dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3500:pvr:sku0A24:rvnDellInc.:rn0GGCMJ:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3500 dmi.product.sku: 0A24 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1945852/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923052] Re: screen reader does not read ubiquity window
Impish is still affected, tested on Ubuntu-MATE 21.10 "Impish Indri" - Beta amd64 (20211002) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1923052 Title: screen reader does not read ubiquity window Status in at-spi2-core package in Ubuntu: Confirmed Status in orca package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Run Ubuntu MATE 21.04 installation media 2. Try to follow http://iso.qa.ubuntu.com/qatracker/testcases/1309/info testcase by pressing ++ to activate screenreader with shown Ubiquity window, press to select some button Expected result: * screen reader reads ubiquity window Actual result: * screen reader does not read ubiquity window Note: screen reader actually works, it reads other windows - for example the terminal opened by ++. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.14 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Thu Apr 8 13:01:30 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210407.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1923052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1945645] Re: cups-pdf prints blank pages
As a quick test, can you check if downgrading ghostscript (ghostscript, libgs9, libgs9-common) to the previous version fixes it or not? -- 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/1945645 Title: cups-pdf prints blank pages Status in cups package in Ubuntu: Confirmed Status in cups-pdf package in Ubuntu: Confirmed Status in ghostscript package in Ubuntu: Confirmed Status in ghostscript package in Debian: New Bug description: after updating from ubuntu 21.04 to ubuntu 21.10 the virtual pdf printer started to print blank pages (to create washed pdf files) printer-driver-cups-pdf, version 3.0.1-10 Description:Ubuntu Impish Indri (development branch) Release:21.10 printer-driver-cups-pdf: Installed: 3.0.1-10 Candidate: 3.0.1-10 Version table: *** 3.0.1-10 500 500 http://bg.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: printer-driver-cups-pdf 3.0.1-10 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 30 15:56:51 2021 InstallationDate: Installed on 2020-03-17 (561 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200205) Lpstat: device for PDF: cups-pdf:/ Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied SourcePackage: cups-pdf UpgradeStatus: Upgraded to impish on 2021-09-28 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1945645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772859] Re: Network Manager is not able to manage the devices on Ubuntu 18.04
While working on a remote server, it took me 2-3 hours to locate this bug report and apply its workarounds. It's certainly not a good default behavior. In case someone has already removed netplan, the recommended steps to get network-manager to manage the interfaces, as I understood them, are: ``` sudo -i apt install ubuntu-minimal echo "# Let NetworkManager manage all devices on this system network: version: 2 renderer: NetworkManager" >/etc/netplan/01-network-manager-all.yaml update-initramfs -u # Not sure if this is needed or not reboot ``` I.e. I think that /etc/netplan/01-network-manager-all.yaml comes from some installer and it's not part of some package and it needs to be manually re-created. -- 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/1772859 Title: Network Manager is not able to manage the devices on Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: NetworkManager is not able to manage the devices on latest Ubuntu(18.04) ---uname output--- Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = z14 s390 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4). 2. Configure a network device and login to the partition through ssh. 3. Now you can see the following output root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el s390x The userspace tool has the following bit modes: 64-bit Userspace rpm: NetworkManager --version 1.10.4 Userspace tool obtained from project website: na Some more information about the issue: Network device has been configured manually after the image is up from Support Element(SE): - znetconf -a - cat /sys/bus/ccwgroup/drivers/qeth//if_name - ifconfig netmask 255.255.255.0 - route add default gw - SSH service has been configured This helped us to login to the Lpar. In Lpar - output of znetconf -c Device IDs TypeCard Type CHPID Drv. Name State - 0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0 online 0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000 D0 qeth eth1 online - output of nmcli c s root@(none):~# nmcli c s NAME UUID TYPE DEVICE - output of nmcli d s root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- * The above output shows that devices are not managed by nmcli After some investigation we found couple of suggestions like 1. Ubuntu(version <17.04): Creating an empty file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and restarting NM, solved the issue. 2. Ubuntu(version 17.10): Copying the said file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the "unmanaged-devices" to none, resolved the issue. * link for reference: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842 For the latest version(18.04), none of the above solutions worked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
