[Desktop-packages] [Bug 736153] Re: Unicode variation selectors not supported
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pango1.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/736153 Title: Unicode variation selectors not supported Status in LibreOffice: New Status in pango1.0 package in Ubuntu: Confirmed Bug description: I'm trying to typeset some texts in ancient Mongolian and Phags-pa, both of which have been included in Unicode. For Mongolian, I've installed the ttf-manchufont package. For Phags-pa, I've used the font available here: http://babelstone.blogspot.com/2006/12/phags-pa- shaping-behaviour.html Both languages use the Unicode Variation Selectors. In a nutshell, the combination character + variation selector should change the representation of the character to a different variant. See the table of Standardised Unicode variants here: http://www.unicode.org/Public/UNIDATA/StandardizedVariants.html The expected behavior does not work in any of the packages I've tried (gedit, gimp and OpenOffice). Instead, the variation selector remains as it's own character and the preceding character is unmodified (see attachment). This is NOT an issue with the fonts because: a. The fonts have the appropriate substitutions defined, as can be observed by editing the fonts in e.g. fontforge. b. The expected behavior happens in WIndows 7 using these fonts. This is an issue with whatever package handles Unicode glyph substitution. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: xorg 1:7.5+6ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-27.48-generic 2.6.35.11 Uname: Linux 2.6.35-27-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Wed Mar 16 10:30:20 2011 InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7576 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-27-generic root=UUID=136a2918-79f6-4777-a8b5-b9d86515a24b ro quiet splash ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display dmi.bios.date: 12/17/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.0 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 790GX-G65 (MS-7576) 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.:bvrV4.0:bd12/17/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7576:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rn790GX-G65(MS-7576):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.name: MS-7576 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: maverick architecture: x86_64 kernel: 2.6.35-27-generic To manage notifications about this bug go to: https://bugs.launchpad.net/libreoffice/+bug/736153/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903896] Re: [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound at all
I have a vivobook m7400qe and have similar problem. Audio never worked from speakers or headphones jack. Mic does work. The solution at this link worked ONCE, then never again https://askubuntu.com/questions/1394452/sound-not-working-on-ubuntu-20-04-asus-vivobook-pro So it should be a configuration related issue. Any other solutions found over the web don't work. -- 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/1903896 Title: [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: The sound was working just fine. I didn't work with my laptop for about half an hour and I didn't change anything that I can think of. But suddenly, there were no sounds anymore. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a_roudgar 1713 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 21:20:12 2020 InstallationDate: Installed on 2020-10-14 (27 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:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a_roudgar 1713 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP410UF.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP410UF dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP410UF.302:bd07/26/2018:svnASUSTeKCOMPUTERINC.:pnVivoBookFlip14TP410UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP410UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: VivoBook Flip dmi.product.name: VivoBook Flip 14 TP410UF dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1903896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961508] Re: Dock displaying over window after resuming from blank screen
no fix in sight? :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have Blank Screen set to happen after 2 minutes of inactivity. When resuming from a Blank Screen (by moving the mouse or touching the keyboard), the Dock is displayed over the top of the current program. To get it back to normal I need to click "Restore Down" on the current programs window and then "Maximize" so that the Dock no longer overlaps it. (Note: I have Auto-hide dock turned off.) This only happens sometimes. I can't reproduce the bug it every time. - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - Ubuntu 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - Not sure (I guess the Dock is part of the Gnome interface?) 3) What you expected to happen - Dock should not overlap the current program on resume from screen blank. 4) What happened instead - The Dock overlaps the current program on resume from screen blank. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2022-02-18 (24 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 Tags: wayland-session impish Uname: Linux 5.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1961508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1980934] Re: Backup fail with unknown error
Michael, the above logs are already the output of the command you now ask me to launch ! Anyway, I run it again, same issue DUPLICITY: DEBUG 1 DUPLICITY: . Found manifest volume 842 DUPLICITY: DEBUG 1 DUPLICITY: . Found manifest volume 843 DUPLICITY: DEBUG 1 DUPLICITY: . Found manifest volume 844 DUPLICITY: DEBUG 1 DUPLICITY: . Found manifest volume 845 DUPLICITY: INFO 1 DUPLICITY: . Found 845 volumes in manifest DUPLICITY: DEBUG 1 DUPLICITY: . Releasing lockfile b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile' DUPLICITY: DEBUG 1 DUPLICITY: . Removing still remembered temporary file /tmp/duplicity-7f89gyml-tempdir/mkstemp-v0hu88gh-1 DUPLICITY: DEBUG 1 DUPLICITY: . Releasing lockfile b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile' DUPLICITY: DEBUG 1 DUPLICITY: . Releasing lockfile b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile' Attached the final printscreen ** Attachment added: "Capture d’écran du 2022-07-29 12-28-41.png" https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1980934/+attachment/5605832/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202022-07-29%2012-28-41.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1980934 Title: Backup fail with unknown error Status in deja-dup package in Ubuntu: Incomplete Bug description: I removed the cache and start a backup in console like DEJA_DUP_DEBUG=1 deja-dup and got during verification the Unknown Error with following final outputs DUPLICITY: DEBUG 1 DUPLICITY: . Found manifest volume 845 DUPLICITY: INFO 1 DUPLICITY: . Found 845 volumes in manifest DUPLICITY: DEBUG 1 DUPLICITY: . Releasing lockfile b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile' DUPLICITY: DEBUG 1 DUPLICITY: . Removing still remembered temporary file /tmp/duplicity-7zeqbwou-tempdir/mkstemp-oc2otu7o-1 DUPLICITY: DEBUG 1 DUPLICITY: . Releasing lockfile b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile' DUPLICITY: DEBUG 1 DUPLICITY: . Releasing lockfile b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile' I than checked the cache which still contains all files including the lockfile ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: deja-dup 40.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 7 10:55:01 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+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-12-07 (942 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: Upgraded to focal on 2020-10-04 (640 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1980934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1978838] Re: Couldn't connect to accessibility bus
This bug was fixed in the package evince - 42.3-2 --- evince (42.3-2) unstable; urgency=medium [ Sebastien Bacher ] * debian/apparmor-profile: - authorize the new at-spi socket location (LP: #1978838) [ Jeremy Bicha ] * Cherry-pick patch to fix build with gnome-desktop 43 -- Jeremy Bicha Thu, 28 Jul 2022 09:45:11 -0400 ** Changed in: evince (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1978838 Title: Couldn't connect to accessibility bus Status in evince package in Ubuntu: Fix Released Status in evince source package in Jammy: Fix Released Bug description: * Impact the apparmor profile blocks the connection to the accessibility bus since it hasn't been updated for the new socket location, https://gitlab.gnome.org/GNOME/at-spi2-core/-/issues/43 * Test Case start evince, it shouldn't print the warning dbind-WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /run/user/UID/at-spi/bus_0: Permission denied start orca, it should be able to read the content of evince * Regression potential The change is only allowing an extra location in the apparmor profile, we kept also the old path for compatibility reasons and for making the profile easier to share between series. Allowing the extra location shouldn't create a regression but if the change was incorrect it is possible that evince would still bot be able to connect to the bus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1978838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983108] [NEW] Boot issue
Public bug reported: It caused my pc to get stuck during boot time. At rebooting, all worked fine ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: plymouth 0.9.4git20200323-0ubuntu6.2 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Jul 29 16:13:04 2022 DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth InstallationDate: Installed on 2020-10-02 (664 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2009 dmi.bios.release: 4.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0408:bd07/20/2009:br4.8:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: plymouth (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 plymouth in Ubuntu. https://bugs.launchpad.net/bugs/1983108 Title: Boot issue Status in plymouth package in Ubuntu: New Bug description: It caused my pc to get stuck during boot time. At rebooting, all worked fine ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: plymouth 0.9.4git20200323-0ubuntu6.2 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Jul 29 16:13:04 2022 DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth InstallationDate: Installed on 2020-10-02 (664 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2009 dmi.bios.release: 4.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0408:bd07/20/2009:br4.8:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1983108/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983112] [NEW] Appstream does not install config file
Public bug reported: After performing an Ubuntu automated server install, and installing the ubuntu-desktop-minimal package (which includes appstream as a dependency) then the snap-store, the snap-store will fail to display search results for .deb packages in the Ubuntu apt repositories. This is due to a missing config file (/etc/apt/apt.conf.d/50appstream) which is supposed to be installed as part of the appstream package. The issue can be fixed by re-installing appstream with the following command-line: apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: appstream 0.15.2-2 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 15:25:44 2022 InstallationDate: Installed on 2022-07-27 (1 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: appstream UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: appstream (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy uec-images wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1983112 Title: Appstream does not install config file Status in appstream package in Ubuntu: New Bug description: After performing an Ubuntu automated server install, and installing the ubuntu-desktop-minimal package (which includes appstream as a dependency) then the snap-store, the snap-store will fail to display search results for .deb packages in the Ubuntu apt repositories. This is due to a missing config file (/etc/apt/apt.conf.d/50appstream) which is supposed to be installed as part of the appstream package. The issue can be fixed by re-installing appstream with the following command-line: apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: appstream 0.15.2-2 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 15:25:44 2022 InstallationDate: Installed on 2022-07-27 (1 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: appstream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970594] Re: "xdg-settings check default-web-browser something.desktop" fails in Kubuntu 22.04: Bad substitution
@diddledani The error does have an impact on the Firefox snap running
under KDE, which I can only presume does some poor parsing of xdg-
settings output (including stderr?) when determining if it is itself the
default browser.
BTW, the patch in https://gitlab.freedesktop.org/xdg/xdg-
utils/-/merge_requests/52 is wrong (see my comment at
https://gitlab.freedesktop.org/xdg/xdg-
utils/-/merge_requests/52#note_1488548), use the attached patch instead.
With this, the Firefox snap recognizes itself as the default browser for
me.
** Patch added: "Fix comparison (== is not a valid operator in Dash)"
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1970594/+attachment/5605898/+files/comparison-fix.diff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1970594
Title:
"xdg-settings check default-web-browser something.desktop" fails in
Kubuntu 22.04: Bad substitution
Status in Xdg-utils:
New
Status in xdg-utils package in Ubuntu:
Fix Released
Status in xdg-utils source package in Jammy:
Fix Released
Bug description:
[Impact]
The firefox snap (default in 22.04) will always report that it thinks
it's not the default browser (even when it actually is) for KDE users
(this can be seen when browsing to about:preferences).
This is caused by an upstream bug in xdg-utils (using bashisms in KDE-
specific functions whereas the default interpreter is dash).
The fix is rather trivial and will visibly improve the UX for those
users.
[Test Plan]
In Kubuntu 22.04:
- make sure firefox isn't your default browser (by changing the setting to a
different browser)
- run the firefox snap, browse to "about:preferences", and observe that
firefox claims NOT to be the default browser
- click the "Set default" button
- refresh the page (F5)
- observe that now firefox claims to be the default browser
- in a terminal, execute `xdg-open https://example.org`, and verify that the
page is open in the firefox snap
[Where problems could occur]
The patch is changing KDE-specific functions (check_browser_kde and
check_url_scheme_handler_kde), so in theory it shouldn't affect
running xdg-utils in any other desktop environment.
If the proposed patch is incorrect, it would affect the functionality
of `xdg-settings check default-web-browser` and `xdg-settings check
default-url-scheme-handler`, so this is what needs to be thoroughly
tested in KDE.
In the event of a regression, these functions wouldn't work as
expected (they already don't, so the user wouldn't observe a
functional regression, merely the absence of a fix).
[Original description]
I'm reporting this issue from stock Ubuntu, but the problem is
observed only in Kubuntu (can be reliably reproduced in a Kubuntu
22.04 VM). The version of xdg-utils is identical.
This problem was initially reported on the snapcraft forum:
https://forum.snapcraft.io/t/firefox-wont-set-as-my-default-
browser/29708.
$ xdg-settings check default-web-browser firefox_firefox.desktop
/usr/bin/xdg-settings: 734: Bad substitution
The offending line is:
if [ x"!" == x"${browser:0:1}" ]; then
If I modify /usr/bin/xdg-settings in place to set the interpreter to
/bin/bash on the first line of the script, the problem goes away.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xdg-utils 1.1.3-4.1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 27 11:21:31 2022
InstallationDate: Installed on 2020-09-16 (587 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
PackageArchitecture: all
SourcePackage: xdg-utils
UpgradeStatus: Upgraded to jammy on 2022-03-19 (38 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-utils/+bug/1970594/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967963] Re: Firefox snap cannot be set as default browser under KDE
I had this problem and the attached patch for xdg-settings worked for me (see my comment at https://gitlab.freedesktop.org/xdg/xdg- utils/-/merge_requests/52#note_1488548). With this, the Firefox snap recognizes itself as the default browser for me (Kubuntu 22.04), whereas previously it would not. ** Patch added: "Fix comparison (== is not a valid operator in Dash)" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967963/+attachment/5605901/+files/comparison-fix.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1967963 Title: Firefox snap cannot be set as default browser under KDE Status in firefox package in Ubuntu: Incomplete Bug description: I was unable to set Firefox as the default browser by going to Settings -> Applications -> Default Applications -> Web browser. It was set to Other... and web links opened in Kate. In addition, I was unable to report a bug against Firefox because "it is provided by a snap provided by Mozilla." ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Tue Apr 5 19:54:54 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2022-03-30 (6 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. Card Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56a6 IMC Networks Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20L50067US ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 1.41 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET66W (1.41 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L50067US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrN24ET66W(1.41):bd10/20/2021:br1.41:efr1.22:svnLENOVO:pn20L50067US:pvrThinkPadT480:rvnLENOVO:rn20L50067US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L5_BU_Think_FM_ThinkPadT480: dmi.product.family: ThinkPad T480 dmi.product.name: 20L50067US dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983115] [NEW] Keybinding "Lower window below other windows" lowers windows below the desktop icons
Public bug reported: Steps to reproduce on Jammy LTS: 1. Create an new empty user 2. Login using Wayland 3. Open "Settings" -> "Keyboard" -> "View and Customize Shortcuts" -> "Windows" -> "Lower window below other windows" 4. Click on the setting "Lower window below other windows" and assign a keybinding, eg Alt-Down 5. Close settings 3. Find the "Home" icon on the desktop 5. Open a terminal and place it over the home icon 6. Press the keybinding "Lower window below other windows" and observe that the terminal window is lowered below the Home icon. eg the Home icon becomes visible on top of the terminal window 7. Try click on the Hamburger Menu in terminal and observe the menu does not open but the window raises above the Home icon. Logout, login under X mode and repeat. Notice that the window does not lower below the home icon and that the Hamburger Menu works on the first click. This is the expected behaviour of this feature going back at least 10 years. For Ubuntu users coming from the previous LTS (using X) this is a behaviour regression. I'm guessing this is mutter because it is wayland specific and mutter src has the "lower" keybinding which is described as the same "Lower window below other windows" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 11:58:21 2022 InstallationDate: Installed on 2022-06-25 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/1983115 Title: Keybinding "Lower window below other windows" lowers windows below the desktop icons Status in mutter package in Ubuntu: New Bug description: Steps to reproduce on Jammy LTS: 1. Create an new empty user 2. Login using Wayland 3. Open "Settings" -> "Keyboard" -> "View and Customize Shortcuts" -> "Windows" -> "Lower window below other windows" 4. Click on the setting "Lower window below other windows" and assign a keybinding, eg Alt-Down 5. Close settings 3. Find the "Home" icon on the desktop 5. Open a terminal and place it over the home icon 6. Press the keybinding "Lower window below other windows" and observe that the terminal window is lowered below the Home icon. eg the Home icon becomes visible on top of the terminal window 7. Try click on the Hamburger Menu in terminal and observe the menu does not open but the window raises above the Home icon. Logout, login under X mode and repeat. Notice that the window does not lower below the home icon and that the Hamburger Menu works on the first click. This is the expected behaviour of this feature going back at least 10 years. For Ubuntu users coming from the previous LTS (using X) this is a behaviour regression. I'm guessing this is mutter because it is wayland specific and mutter src has the "lower" keybinding which is described as the same "Lower window below other windows" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 11:58:21 2022 InstallationDate: Installed on 2022-06-25 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1983115/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983117] [NEW] "Focus Follow Mouse" auto-raises windows when it shouldn't
Public bug reported: Steps to reproduce on Jammy LTS: 1. Create a new empty user and login under Wayland 2. Using gnome-tweaks select "Windows" -> "Window Focus" -> "Focus on Hover" 3. Notice that "Raise Windows When Focused" is disabled Windows auto-raise when changing workspaces: 1. Open two terminal windows and partially overlap them 2. Place the mouse over the lower terminal window so that it remains lowered 3. Do not move the mouse: Press Super-End to change to another workspace, then Super-Begin to go back 4. Observe that the terminal window the mouse is over has been raised The expected behaviour is that windows are not auto-raised when changing workspaces Windows auto-raise when closing windows: 1. Open three terminal windows such that parts of all windows are visible but all windows overlap. 2. Place the mouse inside the topmost terminal so that it is within the visible lowest terminal 3. Without moving the mouse Ctrl-D the terminal to close it 4. Observe that the lowest terminal window the mouse is over has been raised to the top. The expected behaviour is that windows are not auto-raised when closing windows Logout/Login using X and repeat these actions. Notice that window ordering remains fixed in order. This has been the expected behaviour of gnome for the last 10 years or so. This is a behaviour regression for Ubuntu users upgrading from the last LTS (using X). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 12:11:27 2022 InstallationDate: Installed on 2022-06-25 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/1983117 Title: "Focus Follow Mouse" auto-raises windows when it shouldn't Status in mutter package in Ubuntu: New Bug description: Steps to reproduce on Jammy LTS: 1. Create a new empty user and login under Wayland 2. Using gnome-tweaks select "Windows" -> "Window Focus" -> "Focus on Hover" 3. Notice that "Raise Windows When Focused" is disabled Windows auto-raise when changing workspaces: 1. Open two terminal windows and partially overlap them 2. Place the mouse over the lower terminal window so that it remains lowered 3. Do not move the mouse: Press Super-End to change to another workspace, then Super-Begin to go back 4. Observe that the terminal window the mouse is over has been raised The expected behaviour is that windows are not auto-raised when changing workspaces Windows auto-raise when closing windows: 1. Open three terminal windows such that parts of all windows are visible but all windows overlap. 2. Place the mouse inside the topmost terminal so that it is within the visible lowest terminal 3. Without moving the mouse Ctrl-D the terminal to close it 4. Observe that the lowest terminal window the mouse is over has been raised to the top. The expected behaviour is that windows are not auto-raised when closing windows Logout/Login using X and repeat these actions. Notice that window ordering remains fixed in order. This has been the expected behaviour of gnome for the last 10 years or so. This is a behaviour regression for Ubuntu users upgrading from the last LTS (using X). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 12:11:27 2022 InstallationDate: Installed on 2022-06-25 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1983117/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970594] Re: "xdg-settings check default-web-browser something.desktop" fails in Kubuntu 22.04: Bad substitution
> [...] which I can only presume does some poor parsing of xdg-settings
output (including stderr?) when determining if it is itself the default
browser.
I had a look (https://searchfox.org/mozilla-
central/source/browser/components/shell/nsGNOMEShellService.cpp#184-204)
and it does suppress stderr, but the problem is the non-zero exit status
that the error results in. Firefox will only consider itself the default
browser if the command exits with 0 exit status *and* prints "yes".
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1970594
Title:
"xdg-settings check default-web-browser something.desktop" fails in
Kubuntu 22.04: Bad substitution
Status in Xdg-utils:
New
Status in xdg-utils package in Ubuntu:
Fix Released
Status in xdg-utils source package in Jammy:
Fix Released
Bug description:
[Impact]
The firefox snap (default in 22.04) will always report that it thinks
it's not the default browser (even when it actually is) for KDE users
(this can be seen when browsing to about:preferences).
This is caused by an upstream bug in xdg-utils (using bashisms in KDE-
specific functions whereas the default interpreter is dash).
The fix is rather trivial and will visibly improve the UX for those
users.
[Test Plan]
In Kubuntu 22.04:
- make sure firefox isn't your default browser (by changing the setting to a
different browser)
- run the firefox snap, browse to "about:preferences", and observe that
firefox claims NOT to be the default browser
- click the "Set default" button
- refresh the page (F5)
- observe that now firefox claims to be the default browser
- in a terminal, execute `xdg-open https://example.org`, and verify that the
page is open in the firefox snap
[Where problems could occur]
The patch is changing KDE-specific functions (check_browser_kde and
check_url_scheme_handler_kde), so in theory it shouldn't affect
running xdg-utils in any other desktop environment.
If the proposed patch is incorrect, it would affect the functionality
of `xdg-settings check default-web-browser` and `xdg-settings check
default-url-scheme-handler`, so this is what needs to be thoroughly
tested in KDE.
In the event of a regression, these functions wouldn't work as
expected (they already don't, so the user wouldn't observe a
functional regression, merely the absence of a fix).
[Original description]
I'm reporting this issue from stock Ubuntu, but the problem is
observed only in Kubuntu (can be reliably reproduced in a Kubuntu
22.04 VM). The version of xdg-utils is identical.
This problem was initially reported on the snapcraft forum:
https://forum.snapcraft.io/t/firefox-wont-set-as-my-default-
browser/29708.
$ xdg-settings check default-web-browser firefox_firefox.desktop
/usr/bin/xdg-settings: 734: Bad substitution
The offending line is:
if [ x"!" == x"${browser:0:1}" ]; then
If I modify /usr/bin/xdg-settings in place to set the interpreter to
/bin/bash on the first line of the script, the problem goes away.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xdg-utils 1.1.3-4.1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 27 11:21:31 2022
InstallationDate: Installed on 2020-09-16 (587 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
PackageArchitecture: all
SourcePackage: xdg-utils
UpgradeStatus: Upgraded to jammy on 2022-03-19 (38 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-utils/+bug/1970594/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983112] Re: Appstream does not install config file
Did you manually remove the config file before attempting to restore it? Because AFAIK `--force-confmiss` will only make the file show up again if it was modified compared to the previously deleted version, but otherwise leave it deleted in case the user has removed it. I think you need the whole triplet of `--force-confask,confnew,confmiss` to actually get the file back. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1983112 Title: Appstream does not install config file Status in appstream package in Ubuntu: New Bug description: After performing an Ubuntu automated server install, and installing the ubuntu-desktop-minimal package (which includes appstream as a dependency) then the snap-store, the snap-store will fail to display search results for .deb packages in the Ubuntu apt repositories. This is due to a missing config file (/etc/apt/apt.conf.d/50appstream) which is supposed to be installed as part of the appstream package. The issue can be fixed by re-installing appstream with the following command-line: apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: appstream 0.15.2-2 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 15:25:44 2022 InstallationDate: Installed on 2022-07-27 (1 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: appstream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970594] Re: "xdg-settings check default-web-browser something.desktop" fails in Kubuntu 22.04: Bad substitution
I've updated the MR on the freedesktop gitlab instance. Olivier, it
might be worth updating again with a new SRU to include Elvis' further
patch?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1970594
Title:
"xdg-settings check default-web-browser something.desktop" fails in
Kubuntu 22.04: Bad substitution
Status in Xdg-utils:
New
Status in xdg-utils package in Ubuntu:
Fix Released
Status in xdg-utils source package in Jammy:
Fix Released
Bug description:
[Impact]
The firefox snap (default in 22.04) will always report that it thinks
it's not the default browser (even when it actually is) for KDE users
(this can be seen when browsing to about:preferences).
This is caused by an upstream bug in xdg-utils (using bashisms in KDE-
specific functions whereas the default interpreter is dash).
The fix is rather trivial and will visibly improve the UX for those
users.
[Test Plan]
In Kubuntu 22.04:
- make sure firefox isn't your default browser (by changing the setting to a
different browser)
- run the firefox snap, browse to "about:preferences", and observe that
firefox claims NOT to be the default browser
- click the "Set default" button
- refresh the page (F5)
- observe that now firefox claims to be the default browser
- in a terminal, execute `xdg-open https://example.org`, and verify that the
page is open in the firefox snap
[Where problems could occur]
The patch is changing KDE-specific functions (check_browser_kde and
check_url_scheme_handler_kde), so in theory it shouldn't affect
running xdg-utils in any other desktop environment.
If the proposed patch is incorrect, it would affect the functionality
of `xdg-settings check default-web-browser` and `xdg-settings check
default-url-scheme-handler`, so this is what needs to be thoroughly
tested in KDE.
In the event of a regression, these functions wouldn't work as
expected (they already don't, so the user wouldn't observe a
functional regression, merely the absence of a fix).
[Original description]
I'm reporting this issue from stock Ubuntu, but the problem is
observed only in Kubuntu (can be reliably reproduced in a Kubuntu
22.04 VM). The version of xdg-utils is identical.
This problem was initially reported on the snapcraft forum:
https://forum.snapcraft.io/t/firefox-wont-set-as-my-default-
browser/29708.
$ xdg-settings check default-web-browser firefox_firefox.desktop
/usr/bin/xdg-settings: 734: Bad substitution
The offending line is:
if [ x"!" == x"${browser:0:1}" ]; then
If I modify /usr/bin/xdg-settings in place to set the interpreter to
/bin/bash on the first line of the script, the problem goes away.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xdg-utils 1.1.3-4.1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 27 11:21:31 2022
InstallationDate: Installed on 2020-09-16 (587 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
PackageArchitecture: all
SourcePackage: xdg-utils
UpgradeStatus: Upgraded to jammy on 2022-03-19 (38 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-utils/+bug/1970594/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967963] Re: Firefox snap cannot be set as default browser under KDE
The attachment "Fix comparison (== is not a valid operator in Dash)" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1967963 Title: Firefox snap cannot be set as default browser under KDE Status in firefox package in Ubuntu: Incomplete Bug description: I was unable to set Firefox as the default browser by going to Settings -> Applications -> Default Applications -> Web browser. It was set to Other... and web links opened in Kate. In addition, I was unable to report a bug against Firefox because "it is provided by a snap provided by Mozilla." ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Tue Apr 5 19:54:54 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2022-03-30 (6 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. Card Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56a6 IMC Networks Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20L50067US ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 1.41 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET66W (1.41 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L50067US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrN24ET66W(1.41):bd10/20/2021:br1.41:efr1.22:svnLENOVO:pn20L50067US:pvrThinkPadT480:rvnLENOVO:rn20L50067US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L5_BU_Think_FM_ThinkPadT480: dmi.product.family: ThinkPad T480 dmi.product.name: 20L50067US dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1947698] Re: window buttons alignment is wrong in RTL locales
This bug was fixed with the language pack updates that were just pushed to jammy-updates. I verified the bug fix by installing language-pack-gnome-he from jammy- updates (I force-enabled Phased Updates to get the 1:22.04+20220721 version). I installed gnome-text-editor and gnome-shell-extension-manager. I ran LANGUAGE=he gnome-text-editor and LANGUAGE=he extension-manager and verified that the window buttons were on the left side like they were supposed to be. I also checked Arabic but gnome-text-editor hasn't been translated to Arabic yet so its buttons were still on the right side. We don't actually need the updated gtk4 version in jammy-updates to fix this bug. But the gtk4 update is still wanted for other fixes. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/1947698 Title: window buttons alignment is wrong in RTL locales Status in gtk4 package in Ubuntu: Fix Released Status in gtk4 source package in Jammy: Fix Committed Bug description: Impact -- gtk4 is completely untranslated. For RTL locales (such as Farsi, Arabic, and Hebrew), GTK4 apps also have the wrong alignment because of this bug. Test Case - https://translations.launchpad.net/ubuntu/jammy/+source/gtk4/+pots/gtk40 will look similar to https://translations.launchpad.net/ubuntu/kinetic/+source/gtk4/+pots/gtk40 and https://translations.launchpad.net/ubuntu/jammy/+source/gtk4/+pots/gtk40-properties will look similar to https://translations.launchpad.net/ubuntu/kinetic/+source/gtk4/+pots/gtk40-properties They will show long lists of languages, many partially translated Other Info -- This bug won't be fully fixed until a new language pack is built and published. That will happen shortly before the Ubuntu 22.04.1 milestone (so approximately late July). Original Bug Report --- In RTL locales (e.g. fa_IR.UTF-8), the alignment of window buttons (close, min, max) is reverted. For example, in the `gnome-chess` or `extensions`, window buttons are in the right corner, when all other windows has buttons on the left. 21.10 - This bug also affects Ubuntu 21.10 but there just isn't time to get this bug fixed there before End of Life on July 14. If you're affected, please upgrade to Ubuntu 22.04 LTS which will be supported for many more years. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libgtk-4-1 4.4.0+ds1-5 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 19 12:57:21 2021 InstallationDate: Installed on 2021-07-13 (98 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fa_IR SHELL=/bin/bash SourcePackage: gtk4 UpgradeStatus: Upgraded to impish on 2021-10-16 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/1947698/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1980742] Re: Update gtk4 to 4.6.6
I install gtk4 4.6.6+ds-0ubuntu1 and verified that I was able to open and save files from both the Firefox and Chromium snaps. The portal-test snap appears to work as well as it did before. I also installed gnome-text-editor and gnome-shell-extension-manager and those GTK4 apps continued to work fine after installing the updated gtk4. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/1980742 Title: Update gtk4 to 4.6.6 Status in gtk4 package in Ubuntu: Fix Released Status in gtk4 source package in Jammy: Fix Committed Bug description: Impact -- There is a new point release in the stable GTK 4.6 series. https://gitlab.gnome.org/GNOME/gtk/-/blob/4.6.6/NEWS Test Case 1 --- Make sure that opening and saving files from the Firefox and Chromium snaps still work Test Case 2 --- snap install portal-test snap run portal-test Verify that the app seems to still work ok What Could Go Wrong --- Ubuntu includes xdg-desktop-portal-gnome by default which is used for many snap actions like providing a file chooser. This is critical functionality for our snaps. The Ubuntu flavors use a different portal backend, most commonly xdg- desktop-portal-gtk which uses GTK3 so it's not affected by this SRU. The other gtk4 apps installed by default in Ubuntu are gnome-chess and gnome-shell-extension-prefs. gtk4 is part of core GNOME and is in my latest proposed update to the microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME https://discourse.ubuntu.com/t/scope-of-gnome-mru/18041/42 gtk4 has extensive build tests and autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/1980742/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983144] [NEW] Make thunderbird recognize irc: system-handler
Public bug reported: Ubuntu 22.04 @ 29/07/2022 Current case: Thunderbird is installed by default on ubuntu and has a built-in chat/irc client but when clicking irc/ircs links on a browser system-handler does not recognize thunderbird as default irc client Wishlist: Please make Thunderbird open irc links to open with its built-in chat client so users can find their favorite irc (support) channels easy ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thunderbird 1:91.11.0+build2-0ubuntu0.22.04.1 Uname: Linux 5.17.7-051707-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1007 F pulseaudio BuildID: 20220628000715 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 20:25:54 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IpRoute: default via 192.168.1.1 dev enp1s0f1 proto dhcp metric 100 default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev enp1s0f1 scope link metric 1000 192.168.1.0/24 dev enp1s0f1 proto kernel scope link src 192.168.1.34 metric 100 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.63 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 Profile0PrefSources: prefs.js Profile0Prefs: extensions.lastAppVersion: "91.11.0" (prefs.js) network.trr.blocklist_cleanup_done: true (prefs.js) Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=91.11.0/20220628000715 RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** Affects: thunderbird (Ubuntu) Importance: Wishlist 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 thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1983144 Title: Make thunderbird recognize irc: system-handler Status in thunderbird package in Ubuntu: New Bug description: Ubuntu 22.04 @ 29/07/2022 Current case: Thunderbird is installed by default on ubuntu and has a built-in chat/irc client but when clicking irc/ircs links on a browser system-handler does not recognize thunderbird as default irc client Wishlist: Please make Thunderbird open irc links to open with its built-in chat client so users can find their favorite irc (support) channels easy ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thunderbird 1:91.11.0+build2-0ubuntu0.22.04.1 Uname: Linux 5.17.7-051707-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1007 F pulseaudio BuildID: 20220628000715 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 20:25:54 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IpRoute: d
[Desktop-packages] [Bug 1983144] Re: Make thunderbird recognize irc: system-handler
setting as WISHLIST per request from OP on#ubuntu-discuss ** Changed in: thunderbird (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1983144 Title: Make thunderbird recognize irc: system-handler Status in thunderbird package in Ubuntu: New Bug description: Ubuntu 22.04 @ 29/07/2022 Current case: Thunderbird is installed by default on ubuntu and has a built-in chat/irc client but when clicking irc/ircs links on a browser system-handler does not recognize thunderbird as default irc client Wishlist: Please make Thunderbird open irc links to open with its built-in chat client so users can find their favorite irc (support) channels easy ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thunderbird 1:91.11.0+build2-0ubuntu0.22.04.1 Uname: Linux 5.17.7-051707-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1007 F pulseaudio BuildID: 20220628000715 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 20:25:54 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IpRoute: default via 192.168.1.1 dev enp1s0f1 proto dhcp metric 100 default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev enp1s0f1 scope link metric 1000 192.168.1.0/24 dev enp1s0f1 proto kernel scope link src 192.168.1.34 metric 100 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.63 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 Profile0PrefSources: prefs.js Profile0Prefs: extensions.lastAppVersion: "91.11.0" (prefs.js) network.trr.blocklist_cleanup_done: true (prefs.js) Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=91.11.0/20220628000715 RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1983144/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983130] [NEW] Ubuntu dock set to auto-hide hides after a right-click menu is closed even when there are no reasons for it to do so.
You have been subscribed to a public bug: Description:Ubuntu 22.04 LTS Release:22.04 Expected behavior: Dock set to auto-hide would remain shown after either a right-click menu option is selected, or a right-click menu is cancelled. Actual behavior: Dock hides after a right-click menu closes even when there are no windows in its space. Additional notes: Dock can be temporarily reset to its normal behavior when one of these actions are performed: - when a window enters the dock's usual space - when the "show applications" menu is opened and closed - when a maximized window is opened and closed/minimized ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: auto-hide bot-comment dock -- Ubuntu dock set to auto-hide hides after a right-click menu is closed even when there are no reasons for it to do so. https://bugs.launchpad.net/bugs/1983130 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983130] Re: Ubuntu dock set to auto-hide hides after a right-click menu is closed even when there are no reasons for it to do so.
** Package changed: ubuntu => gnome-shell-extension-ubuntu-dock (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1983130 Title: Ubuntu dock set to auto-hide hides after a right-click menu is closed even when there are no reasons for it to do so. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Description: Ubuntu 22.04 LTS Release: 22.04 Expected behavior: Dock set to auto-hide would remain shown after either a right-click menu option is selected, or a right-click menu is cancelled. Actual behavior: Dock hides after a right-click menu closes even when there are no windows in its space. Additional notes: Dock can be temporarily reset to its normal behavior when one of these actions are performed: - when a window enters the dock's usual space - when the "show applications" menu is opened and closed - when a maximized window is opened and closed/minimized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1983130/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983161] [NEW] gnome-shell memory leak
Public bug reported: As I use it more and more, the memory used by gnome-shell is also increasing. I've tested it in Xorg and Wayland and both result in a gradual increase in memory. I also tested with all my extensions turned off and the result was also a gradual increase in memory ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 30 09:15:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-23 (97 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1983161 Title: gnome-shell memory leak Status in gnome-shell package in Ubuntu: New Bug description: As I use it more and more, the memory used by gnome-shell is also increasing. I've tested it in Xorg and Wayland and both result in a gradual increase in memory. I also tested with all my extensions turned off and the result was also a gradual increase in memory ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 30 09:15:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-23 (97 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1983161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976179] Re: evince does not print
[Expired for evince (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evince (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1976179 Title: evince does not print Status in evince package in Ubuntu: Expired Bug description: Since Update from 20.04 -> 22.04, I am not able to print via evince, ocular is working. $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" When starting evince in terminal, it produces the following output: $ evince ./reise_scheng_formular.pdf\;jsessionid\=581D11B486915D0476F672CBA29B8143.pdf (evince:48073): dbind-WARNING **: 11:51:05.921: Couldn't connect to accessibility bus: Failed to connect to socket /run/user/1000/at-spi/bus_1: Permission denied Gtk-Message: 11:51:05.959: Failed to load module "unity-gtk-module" Gtk-Message: 11:51:05.960: Failed to load module "unity-gtk-module" When I print, I see a small blinking of the lcd display of CANON MX PIXMA 920 printer. The printer dialog says: processing stopped. It could not be restarted. Printing from OCULAR or LibreOffice works still fine. Assumed some rights problems?? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1976179/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958333] Re: Progress Bar should disappear from icon after file operations cease, but it lingers fora few minutes after
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- 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/1958333 Title: Progress Bar should disappear from icon after file operations cease, but it lingers fora few minutes after Status in nautilus package in Ubuntu: Expired Bug description: This happens after copying files or extracting every time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 19 00:14:54 2022 GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1038, 552)' b'org.gnome.nautilus.preferences' b'fts-enabled' b'false' InstallationDate: Installed on 2021-10-03 (108 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=en_US.UTF-8 SHELL=/bin/bash 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/ubuntu/+source/nautilus/+bug/1958333/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1955697] Re: file-roller fails to extract zip|rar|tar to symlinked directories
[Expired for file-roller (Ubuntu) because there has been no activity for 60 days.] ** Changed in: file-roller (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1955697 Title: file-roller fails to extract zip|rar|tar to symlinked directories Status in file-roller package in Ubuntu: Expired Bug description: File-roller fails to extract rar, zip, xz and tar archives when 1) the output folder is or is below a symbolic link and 2) extraction is run from the context menu (Extract Here) The typical error message is: "There was an error while extracting ". The file is not a directory." Extraction does work when I 1) navigate to the actual location of the output folder or move the archive(s) to a location that is not a symbolic link or 2) open the archive and run "Extract to" from its menu (which is quite cumbersome when there are dozens of archives to process...). I am dual booting 20.04 and 21.10 with a single home directory (which is where the problematic symlink is located). The issue I am reporting occurs only when I am using 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: file-roller 3.40.0-2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 24 07:29:37 2021 InstallationDate: Installed on 2021-10-12 (73 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1955697/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908358] Re: gnome-control-center crashes on start
[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/1908358 Title: gnome-control-center crashes on start Status in gnome-control-center package in Ubuntu: Expired Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 gnome-control-center: Installed: 1:3.36.4-0ubuntu2 Candidate: 1:3.36.4-0ubuntu2 Version table: *** 1:3.36.4-0ubuntu2 500 500 http://ru.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages samba-libs: Installed: 2:4.11.6+dfsg-0ubuntu1.6 Candidate: 2:4.11.6+dfsg-0ubuntu1.6 Version table: *** 2:4.11.6+dfsg-0ubuntu1.6 500 500 http://ru.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2:4.11.6+dfsg-0ubuntu1 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages When I start gnome-control-center it crashes with error: $ gnome-control-center gnome-control-center: symbol lookup error: /usr/lib/x86_64-linux-gnu/samba/libclidns.so.0: undefined symbol: ndr_pull_dns_name_packet, version NDR_NBT_0.0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1908358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887270] Re: brisk-menu crashed with SIGSEGV in g_slice_free_chain_with_offset()
[Expired for glib2.0 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: glib2.0 (Ubuntu) Status: Incomplete => Expired -- 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/1887270 Title: brisk-menu crashed with SIGSEGV in g_slice_free_chain_with_offset() Status in brisk-menu package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Expired Bug description: Happened on MATE groovy live. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: mate-applet-brisk-menu 0.6.0-2 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-0ubuntu42 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: MATE Date: Sun Jul 12 08:25:47 2020 ExecutablePath: /usr/lib/x86_64-linux-gnu/brisk-menu/brisk-menu LiveMediaBuild: Ubuntu-MATE 20.10 "Groovy Gorilla" - Alpha amd64 (20200712) ProcCmdline: /usr/lib/x86_64-linux-gnu/brisk-menu//brisk-menu ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f07befc5d3e : mov(%r15,%rax,1),%r15 PC (0x7f07befc5d3e) ok source "(%r15,%rax,1)" (0x3ff8) not located in a known VMA region (needed readable region)! destination "%r15" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: brisk-menu StacktraceTop: g_slice_free_chain_with_offset () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: brisk-menu crashed with SIGSEGV in g_slice_free_chain_with_offset() 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/brisk-menu/+bug/1887270/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983166] Re: gnome-session-binary crashed with SIGSEGV in g_variant_builder_add_value()
*** This bug is a duplicate of bug 1968001 *** https://bugs.launchpad.net/bugs/1968001 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1968001, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1983166/+attachment/5605934/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1983166/+attachment/5605936/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1983166/+attachment/5605940/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1983166/+attachment/5605941/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1983166/+attachment/5605942/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1983166/+attachment/5605943/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1983166/+attachment/5605944/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1968001 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1983166 Title: gnome-session-binary crashed with SIGSEGV in g_variant_builder_add_value() Status in gnome-session package in Ubuntu: New Bug description: Ubuntu identified the issue itself, and asked me to report it. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-session-bin 42.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-9.9-generic 5.19.0-rc5 Uname: Linux 5.19.0-9-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Jul 30 06:06:16 2022 ExecutablePath: /usr/libexec/gnome-session-binary InstallationDate: Installed on 2022-01-27 (183 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcCmdline: /usr/libexec/gnome-session-binary --autostart /usr/share/gdm/greeter/autostart SegvAnalysis: Segfault happened at: 0x7f7a34257bdd : mov0x20(%rbp),%ecx PC (0x7f7a34257bdd) ok source "0x20(%rbp)" (0x0020) not located in a known VMA region (needed readable region)! destination "%ecx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-session StacktraceTop: g_variant_builder_add_value () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_new_va () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_new () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () Title: gnome-session-binary crashed with SIGSEGV in g_variant_builder_add_value() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1983166/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916055] Re: XML parse error: cannot load more than 200000 XML elements
Maybe helpful to reproduce: The output of `systemd-analyze dot | dot -Tsvg > systemd.svg` have in my case 2.2M and 20611 lines (wc -l, same if prepiped to `xmllint --format -`). I have the same symptoms except for the error message. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1916055 Title: XML parse error: cannot load more than 20 XML elements Status in librsvg package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have really big SVG file as in the https://askubuntu.com/q/1317267/66509 question 2. Open the file using for example Eye of MATE Expected result: * file is opened Actual result: * file is not opened, EoM shows error instead: Could not load image 'NOSTOC2.svg'. XML parse error: cannot load more than 20 XML elements ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: librsvg2-2:amd64 2.48.9-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18 Uname: Linux 4.15.0-135-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Thu Feb 18 19:49:00 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: librsvg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1916055/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
