[Desktop-packages] [Bug 1990749] [NEW] package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1
Public bug reported: - ProblemType: Package DistroRelease: Ubuntu 18.04 Package: tex-common 6.09 ProcVersionSignature: Ubuntu 4.15.0-192.203-generic 4.15.18 Uname: Linux 4.15.0-192-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.28 AptOrdering: libtiff5:i386: Install libtiff5:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Sep 23 07:27:57 2022 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-10-22 (1798 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.4 apt 1.6.12ubuntu0.2 SourcePackage: tex-common Title: package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1990749 Title: package tex-common 6.09 failed to install/upgrade: installed tex- common package post-installation script subprocess returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: - ProblemType: Package DistroRelease: Ubuntu 18.04 Package: tex-common 6.09 ProcVersionSignature: Ubuntu 4.15.0-192.203-generic 4.15.18 Uname: Linux 4.15.0-192-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.28 AptOrdering: libtiff5:i386: Install libtiff5:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Sep 23 07:27:57 2022 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-10-22 (1798 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.4 apt 1.6.12ubuntu0.2 SourcePackage: tex-common Title: package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1990749/+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 1990747] Re: gnome-shell crashed with SIGSEGV in __GI_getenv()
*** This bug is a duplicate of bug 199 ***
https://bugs.launchpad.net/bugs/199
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 #199, 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/1990747/+attachment/5618721/+files/CoreDump.gz
** Attachment removed: "Disassembly.txt"
https://bugs.launchpad.net/bugs/1990747/+attachment/5618723/+files/Disassembly.txt
** Attachment removed: "ProcMaps.txt"
https://bugs.launchpad.net/bugs/1990747/+attachment/5618727/+files/ProcMaps.txt
** Attachment removed: "ProcStatus.txt"
https://bugs.launchpad.net/bugs/1990747/+attachment/5618728/+files/ProcStatus.txt
** Attachment removed: "Registers.txt"
https://bugs.launchpad.net/bugs/1990747/+attachment/5618729/+files/Registers.txt
** Attachment removed: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1990747/+attachment/5618731/+files/Stacktrace.txt
** Attachment removed: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1990747/+attachment/5618732/+files/ThreadStacktrace.txt
** This bug has been marked a duplicate of bug 199
gnome-shell crashed with SIGSEGV in getenv("STEMD_DEVICE_VERIFY_SYSFS")
** 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-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1990747
Title:
gnome-shell crashed with SIGSEGV in __GI_getenv()
Status in gnome-shell package in Ubuntu:
New
Bug description:
bug
ProblemType: Crash
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sun Sep 25 06:43:22 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
InstallationDate: Installed on 2022-09-20 (5 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220919)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 43.0-1ubuntu1
SegvAnalysis:
Segfault happened at: 0x7f5376e3f13d <__GI_getenv+173>: cmp
(%rbx),%r12w
PC (0x7f5376e3f13d) ok
source "(%rbx)" (0x557dc02e8308) not located in a known VMA region (needed
readable region)!
destination "%r12w" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
__GI_getenv (name=0x7f53741d443b "STEMD_DEVICE_VERIFY_SYSFS") at
./stdlib/getenv.c:84
?? () from /lib/x86_64-linux-gnu/libudev.so.1
?? () from /lib/x86_64-linux-gnu/libudev.so.1
udev_device_new_from_syspath () from /lib/x86_64-linux-gnu/libudev.so.1
g_udev_client_query_by_subsystem () from
/lib/x86_64-linux-gnu/libgudev-1.0.so.0
Title: gnome-shell crashed with SIGSEGV in __GI_getenv()
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-shell/+bug/1990747/+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 1879137] Re: The snap-store is using hundreds of MiBs of RAM.
I found that snap-store was consuming fully 1 GB of RAM on my system when I checked it just now. Such a huge memory use for something I *never* used. I would like to think that core elements of the a default Ubuntu system would be designed more carefully for low memory use. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1879137 Title: The snap-store is using hundreds of MiBs of RAM. Status in GNOME Software: New Status in snap-store-desktop: Confirmed Status in gnome-software package in Ubuntu: Confirmed Bug description: The snap-store process is intermittently using hundreds of megabytes of RAM. Is this normal? Is there a solution? Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1879137/+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 1990736] Re: Xorg crash
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1990736 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: J'ai des crash répétitif depuis longtemps. Et parfois l'écran se fige je ne peux plus rien faire. J'ai déjà réinstallé 3 x. Impossible de trouver le problème. Merci beaucoup. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 22:02:01 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK107 [GeForce GTX 650] [3842:2650] InstallationDate: Installed on 2022-09-08 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=fr_CH:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_CH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=30b5da29-5676-4f0b-bf23-d79eef14a3c5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX 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.:bvr2501:bd07/21/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1990736/+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 1990736] [NEW] Xorg crash
You have been subscribed to a public bug: J'ai des crash répétitif depuis longtemps. Et parfois l'écran se fige je ne peux plus rien faire. J'ai déjà réinstallé 3 x. Impossible de trouver le problème. Merci beaucoup. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 22:02:01 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK107 [GeForce GTX 650] [3842:2650] InstallationDate: Installed on 2022-09-08 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=fr_CH:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_CH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=30b5da29-5676-4f0b-bf23-d79eef14a3c5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX 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.:bvr2501:bd07/21/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash jammy ubuntu wayland-session -- Xorg crash https://bugs.launchpad.net/bugs/1990736 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987976]
Created attachment 9295261 about:support json from running MOZ_ENABLE_WAYLAND=1 ./firefox-104.0.2/firefox/firefox -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1987976 Title: firefox black window Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987976]
Created attachment 9295260 about:support json from running ./firefox-104.0.2/firefox/firefox -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1987976 Title: firefox black window Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987976]
> It seems not to happen if instead of the "firefox" launcher binary, I run "firefox-bin" directly. What's the difference? Nevermind. I think it can happen with either. It's just a bit random whether it happens or not. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1987976 Title: firefox black window Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987976]
Sorry, I can't deal with the randomness. Let's simplify - $ sudo snap disable firefox firefox disabled $ cat ~/.local/share/applications/firefox2.desktop [Desktop Entry] Version=1.0 Name=Firefox Web Browser 2 Exec=/bin/bash -c "/home/alan/firefox-104.0.2/firefox/firefox" Terminal=false X-MultipleArgs=false Type=Application Icon=firefox Categories=GNOME;GTK;Network;WebBrowser; MimeType=text/html;text/xml;application/xhtml+xml;application/xml;application/rss+xml;application/rdf+xml;image/gif;image/jpeg;image/png;x-scheme-handler/http;x-scheme-handler/https;video/webm;application/x-xpinstall; StartupNotify=true StartupWMClass=firefox $ With the above, if I log in and click firefox, I get stuck at the black window. If I quit firefox and try again, I get a *temporary* black window, and then a working firefox. If I edit the file and change it to "MOZ_ENABLE_WAYLAND=1 /home/alan/firefox-104.0.2/firefox/firefox", then two things change: 1. When I log in and click firefox, firefox works the first time. I don't have to quit it and click it again before I can use firefox. 2. When firefox starts, there is no *temporary* black screen either. --- When I *was* trying to launch firefox from the terminal, I also noticed a difference in debug messages: $ /bin/bash -c "/home/alan/firefox-104.0.2/firefox/firefox" ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. [2022-09-19T12:44:36Z ERROR viaduct::backend::ffi] Missing HTTP status [2022-09-19T12:44:36Z ERROR viaduct::backend::ffi] Missing HTTP status $ $ /bin/bash -c "MOZ_ENABLE_WAYLAND=1 /home/alan/firefox-104.0.2/firefox/firefox" Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed [2022-09-19T12:44:43Z ERROR viaduct::backend::ffi] Missing HTTP status [2022-09-19T12:44:43Z ERROR viaduct::backend::ffi] Missing HTTP status $ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1987976 Title: firefox black window Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987976]
The severity field is not set for this bug. :gerard-majax, could you have a look please? For more information, please visit [auto_nag documentation](https://wiki.mozilla.org/Release_Management/autonag#workflow.2Fno_severity.py). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1987976 Title: firefox black window Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987976]
(In reply to Alan Jenkins from comment #20) > > It seems not to happen if instead of the "firefox" launcher binary, I run > > "firefox-bin" directly. What's the difference? > > Nevermind. I think it can happen with either. It's just a bit random whether > it happens or not. Just to clavify, you reproduce with both Snap and tarball downloaded from mozilla.org ? Can you share `about:support` ? Can you verify with `MOZ_ENABLE_WAYLAND=1 firefox` if the issue disappears? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1987976 Title: firefox black window Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987976]
I have the same black window problem. Can I help? I can reproduce it with upstream "firefox" unpacked from firefox-104.0.2.tar.bz2 ! (As well as by using the snap) It seems *not* to happen if instead of the "firefox" launcher binary, I run "firefox-bin" directly. What's the difference? It happens the first time I start firefox after logging in. If I quit firefox and start it again, it works. (The window may *start* black, but it changes after a few seconds. As reported here: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1838963 ) My GPU description is "Mesa DRI Intel(R) HD Graphics 2000 (SNB GT1)". (No secondary GPU). I use Ubuntu 22.04.1 (x86_64). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1987976 Title: firefox black window Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990742] [NEW] screen not consistently locking when lid is closed
Public bug reported: I have GNOME configured to lock the screen when the screen is blanked, and to blank the screen when the lid is closed: org.gnome.settings-daemon.plugins.power lid-close-battery-action 'blank' org.gnome.desktop.screensaver lock-delay uint32 0 org.gnome.desktop.screensaver lock-enabled true This worked fine in Jammy: whenever my screen was unlocked and I closed my laptop lid, it locked immediately, i.e., if I immediately reopened my lid, the screen was locked. After having just upgraded to Kinetic, however, sometimes when I close the lid it locks as described above, and sometimes it just... doesn't, i.e., when I open the lid again the screen is unlocked and I can just keep working. I have been unable to determine what the factors are which control whether the screen locks when I close the lid. There is a moderate security implication here, as it's problematic for someone's screen not to lock when they think that it did. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 17:57:37 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (1135 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 43.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages -- 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/1990742 Title: screen not consistently locking when lid is closed Status in gnome-shell package in Ubuntu: New Bug description: I have GNOME configured to lock the screen when the screen is blanked, and to blank the screen when the lid is closed: org.gnome.settings-daemon.plugins.power lid-close-battery-action 'blank' org.gnome.desktop.screensaver lock-delay uint32 0 org.gnome.desktop.screensaver lock-enabled true This worked fine in Jammy: whenever my screen was unlocked and I closed my laptop lid, it locked immediately, i.e., if I immediately reopened my lid, the screen was locked. After having just upgraded to Kinetic, however, sometimes when I close the lid it locks as described above, and sometimes it just... doesn't, i.e., when I open the lid again the screen is unlocked and I can just keep working. I have been unable to determine what the factors are which control whether the screen locks when I close the lid. There is a moderate security implication here, as it's problematic for someone's screen not to lock when they think that it did. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 17:57:37 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (1135 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 43.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1990742/+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 1990591] Re: Green artifacts when using VAAPI decoding of H.265 video on amd GPU
** Description changed: (Sorry if this is filed against the wrong package, I don't know enough graphics stuff to guess which) + When decoding H.265 (HEVC) video on an amd GPU (here, a 6600xt), green + corruption-y artifacts appear in the top left corner and persist the + whole time. The problem persists across video players (totem and VLC), + but does not occur for h.264 encoded video, and goes away if decoding in + vlc is set to VDPAU, VAAPI with DRM, or no hardware acceleration (that + is, it exists only for h.265 video decoded with VAAPI acceleration + without DRM). There's a random thread at + https://www.reddit.com/r/linux_gaming/comments/x15rn4/found_cause_and_resolution_to_vaapi_h265/ + by someone else describing the same exact problem. - When decoding H.265 (HEVC) video on an amd GPU (here, a 6600xt), green corruption-y artifacts appear in the top left corner and persist the whole time. The problem persists across video players (totem and VLC), but does not occur for h.264 encoded video, and goes away if decoding in vlc is set to VDPAU, VAAPI with DRM, or no hardware acceleration (that is, it exists only for h.265 video decoded with VAAPI acceleration without DRM). There's a random thread at https://www.reddit.com/r/linux_gaming/comments/x15rn4/found_cause_and_resolution_to_vaapi_h265/ by someone else describing the same exact problem. + To reproduce: + On a computer with an AMD discrete GPU, play a HEVC encoded video with any video player using VAAPI (the default GNOME player and VLC both exhibit the bug) to decode, and then look in the top left corner of the video. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-video-amdgpu 22.0.0-1ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 22 19:29:47 2022 DistUpgraded: 2022-04-30 00:07:10,213 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] [1002:73ff] (rev c1) (prog-if 00 [VGA controller]) -Subsystem: Sapphire Technology Limited Navi 23 [Radeon RX 6600/6600 XT/6600M] [1da2:448e] + Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] [1002:73ff] (rev c1) (prog-if 00 [VGA controller]) + Subsystem: Sapphire Technology Limited Navi 23 [Radeon RX 6600/6600 XT/6600M] [1da2:448e] InstallationDate: Installed on 2020-04-25 (880 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=78160ce3-0a32-48d4-b13f-866e6d975edc ro SourcePackage: xserver-xorg-video-amdgpu UpgradeStatus: Upgraded to jammy on 2022-04-30 (145 days ago) dmi.bios.date: 11/12/2021 dmi.bios.release: 6.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0605 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z690M-PLUS D4 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0605:bd11/12/2021:br6.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ690M-PLUSD4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1990591 Title: Green artifacts when using VAAPI decoding of H.265 video on amd GPU Status in
[Desktop-packages] [Bug 1990732] [NEW] Nautilus not opening quickly, sometimes doesn't open at all
Public bug reported: Nautilus takes very time to load. It was working fine, but before 2 days the problem started to occur. Other apps open instantly, including dolphin file manager. The time to load is causing lot of other issues like, upload button not working in sites (though I have installed dolphin file manager). Kindly rectify the issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 Uname: Linux 5.19.0-051900-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 22:46:46 2022 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'" b'org.gnome.nautilus.window-state' b'initial-size' b'(715, 327)' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.window-state' b'sidebar-width' b'227' InstallationDate: Installed on 2022-08-05 (50 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 ** Affects: nautilus (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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1990732 Title: Nautilus not opening quickly, sometimes doesn't open at all Status in nautilus package in Ubuntu: New Bug description: Nautilus takes very time to load. It was working fine, but before 2 days the problem started to occur. Other apps open instantly, including dolphin file manager. The time to load is causing lot of other issues like, upload button not working in sites (though I have installed dolphin file manager). Kindly rectify the issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 Uname: Linux 5.19.0-051900-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 22:46:46 2022 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'" b'org.gnome.nautilus.window-state' b'initial-size' b'(715, 327)' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.window-state' b'sidebar-width' b'227' InstallationDate: Installed on 2022-08-05 (50 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1990732/+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 1554652] Re: nautilus-share broken with libpam-smbpass removed
** Changed in: nautilus-share (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/1554652 Title: nautilus-share broken with libpam-smbpass removed Status in nautilus-share package in Ubuntu: Confirmed Status in nautilus-share package in Debian: New Bug description: Package libpam-smbpass is removed from 16.04 archives because of bug causing segfault. This makes nautilus-share very confusing since you won't be able to access the shares if they are set with authentication. Users might be stuck thinking file sharing simply doesn't work because of this. Perhaps nautilus-share should have a dialog explaining that a samba password has to be set or have it only with guest access for shares unless the issue with libpam-smbpass is fixed and back in archive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/1554652/+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 1554652] Re: nautilus-share broken with libpam-smbpass removed
** Bug watch added: Debian Bug tracker #760342 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760342 ** Also affects: nautilus-share (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760342 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/1554652 Title: nautilus-share broken with libpam-smbpass removed Status in nautilus-share package in Ubuntu: Confirmed Status in nautilus-share package in Debian: Unknown Bug description: Package libpam-smbpass is removed from 16.04 archives because of bug causing segfault. This makes nautilus-share very confusing since you won't be able to access the shares if they are set with authentication. Users might be stuck thinking file sharing simply doesn't work because of this. Perhaps nautilus-share should have a dialog explaining that a samba password has to be set or have it only with guest access for shares unless the issue with libpam-smbpass is fixed and back in archive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/1554652/+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 1958019]
The TAS2563 works without the firmware (tuning file). Documentation: https://www.ti.com/product/TAS2553 However there is an android driver with firmware loading support. https://git.ti.com/cgit/tas256xsw-android/tas2563-android-driver/ Or a mainline RFC: https://lkml.org/lkml/2020/6/9/800 The bass speakers can be enabled with: i2cset 3 0x4c 0x2 0 i2cset 3 0x4d 0x2 0 they are listening on 0x48 too, so in one turn: i2cset 3 0x48 0x2 0 I don't know how safe it is to use it this way. They have to be enabled after suspend, and if you plug in-out the headphone (only if auto mute is enabled). -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
Created attachment 301857 attachment-28445-0.html I am currently out of the office on holiday I will be returning on Monday September 26, I will not have access to email so replies will be delayed -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
I have a Lenovo Yoga 7 14ARB7 too.
I think it uses an TAS2563 amplifier chip. According to the windows driver it
has a firmware too. There is some support in the kernel too.
https://github.com/torvalds/linux/blob/master/sound/soc/codecs/tas2562.c
The ACPI part:
```
Scope (_SB.I2CD)
{
Device (TAS)
{
Name (_HID, "INT8866") // _HID: Hardware ID
Name (_UID, Zero) // _UID: Unique ID
Method (_CRS, 0, NotSerialized) // _CRS: Current Resource Settings
{
Name (RBUF, ResourceTemplate ()
{
I2cSerialBusV2 (0x004C, ControllerInitiated, 0x00061A80,
AddressingMode7Bit, "\\_SB.I2CD",
0x00, ResourceConsumer, , Exclusive,
)
I2cSerialBusV2 (0x004D, ControllerInitiated, 0x00061A80,
AddressingMode7Bit, "\\_SB.I2CD",
0x00, ResourceConsumer, , Exclusive,
)
GpioInt (Edge, ActiveLow, SharedAndWake, PullNone, 0x,
"\\_SB.GPIO", 0x00, ResourceConsumer, ,
)
{ // Pin list
0x0020
}
})
Return (RBUF) /* \_SB_.I2CD.TAS_._CRS.RBUF */
}
Method (_STA, 0, NotSerialized) // _STA: Status
{
Return (0x0F)
}
}
}
```
--
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/1958019
Title:
[Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
sound at all
Status in sound-2.6 (alsa-kernel):
Confirmed
Status in alsa-driver package in Ubuntu:
Confirmed
Bug description:
On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
internal speakers, but it work by headphones connected to standard
jack aux.
uname -r
5.11.0-44-generic
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-44-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: i3draven 1266 F pulseaudio
/dev/snd/controlC0: i3draven 1266 F pulseaudio
/dev/snd/controlC1: i3draven 1266 F pulseaudio
/dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan 15 15:10:53 2022
InstallationDate: Installed on 2021-10-11 (96 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio
Generic
Symptom_DevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: i3draven 1266 F pulseaudio
/dev/snd/controlC0: i3draven 1266 F pulseaudio
/dev/snd/controlC1: i3draven 1266 F pulseaudio
/dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/08/2021
dmi.bios.release: 1.49
dmi.bios.vendor: LENOVO
dmi.bios.version: GKCN49WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion 7 16ACHg6
dmi.ec.firmware.release: 1.49
dmi.modalias:
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
dmi.product.family: Legion 7 16ACHg6
dmi.product.name: 82N6
dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
dmi.product.version: Legion 7 16ACHg6
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1989587] Re: Cannot print to autodiscovered printers
Digging journalctl: lot of Apparmor "DENIED" sept. 24 14:17:15 ub64 audit[1007]: AVC apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=1007 comm="cupsd" capability=12 capname="net_admin" sept. 24 14:17:16 ub64 audit[1182]: AVC apparmor="DENIED" operation="connect" profile="/usr/sbin/cups-browsed" name="/run/systemd/resolve/io.systemd.Resolve" pid=1182 comm="cups-browsed" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=101 sept. 24 14:17:16 ub64 audit[1182]: AVC apparmor="DENIED" operation="connect" profile="/usr/sbin/cups-browsed" name="/run/systemd/resolve/io.systemd.Resolve" pid=1182 comm="cups-browsed" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=101 sept. 24 14:19:41 ub64 audit[4318]: AVC apparmor="DENIED" operation="capable" profile="/usr/lib/snapd/snap-confine" pid=4318 comm="snap-confine" capability=12 capname="net_admin" sept. 24 14:19:41 ub64 audit[4318]: AVC apparmor="DENIED" operation="capable" profile="/usr/lib/snapd/snap-confine" pid=4318 comm="snap-confine" capability=38 capname="perfmon" sept. 24 14:19:41 ub64 kernel: audit: type=1400 audit(1664021981.797:49): apparmor="DENIED" operation="capable" profile="/usr/lib/snapd/snap-confine" pid=4318 comm="snap-confine" capability=12 capname="net_admin" sept. 24 14:19:41 ub64 kernel: audit: type=1400 audit(1664021981.797:50): apparmor="DENIED" operation="capable" profile="/usr/lib/snapd/snap-confine" pid=4318 comm="snap-confine" capability=38 capname="perfmon" sept. 24 14:19:41 ub64 audit[4318]: AVC apparmor="DENIED" operation="capable" profile="/usr/lib/snapd/snap-confine" pid=4318 comm="snap-confine" capability=4 capname="fsetid" sept. 24 14:19:41 ub64 kernel: audit: type=1400 audit(1664021981.825:51): apparmor="DENIED" operation="capable" profile="/usr/lib/snapd/snap-confine" pid=4318 comm="snap-confine" capability=4 capname="fsetid" sept. 24 14:19:42 ub64 audit[4337]: AVC apparmor="DENIED" operation="mkdir" profile="snap-update-ns.firefox" name="/usr/share/cups/doc-root/" pid=4337 comm="5" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 sept. 24 14:19:42 ub64 kernel: audit: type=1400 audit(1664021982.073:52): apparmor="DENIED" operation="mkdir" profile="snap-update-ns.firefox" name="/usr/share/cups/doc-root/" pid=4337 comm="5" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 sept. 24 14:19:42 ub64 kernel: audit: type=1400 audit(1664021982.077:53): apparmor="DENIED" operation="mkdir" profile="snap-update-ns.firefox" name="/usr/share/gimp/2.0/" pid=4337 comm="5" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 sept. 24 14:19:42 ub64 kernel: audit: type=1400 audit(1664021982.077:54): apparmor="DENIED" operation="mkdir" profile="snap-update-ns.firefox" name="/usr/share/libreoffice/help/" pid=4337 comm="5" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 sept. 24 14:19:42 ub64 kernel: audit: type=1400 audit(1664021982.077:55): apparmor="DENIED" operation="open" profile="snap-update-ns.firefox" name="/var/lib/" pid=4337 comm="5" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 sept. 24 14:19:42 ub64 audit[4337]: AVC apparmor="DENIED" operation="mkdir" profile="snap-update-ns.firefox" name="/usr/share/gimp/2.0/" pid=4337 comm="5" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 sept. 24 14:19:42 ub64 audit[4337]: AVC apparmor="DENIED" operation="mkdir" profile="snap-update-ns.firefox" name="/usr/share/libreoffice/help/" pid=4337 comm="5" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 sept. 24 14:19:42 ub64 audit[4337]: AVC apparmor="DENIED" operation="open" profile="snap-update-ns.firefox" name="/var/lib/" pid=4337 comm="5" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Looks like the latest cups version has to be blame , due to: cups (2.4.2-1ubuntu2) kinetic; urgency=medium * Add patch to build with snapd-glib-2 -- Jeremy Bicha Thu, 25 Aug 2022 21:54:33 -0400 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1989587 Title: Cannot print to autodiscovered printers Status in cups-filters package in Ubuntu: Confirmed Bug description: I have issues when trying to print on autodiscovered printers. In some cases, cups reports a "permission denied". In other cases, the local queue is not created at all, so that it is impossible to print. However, these printers do appear in the kde print dialog for applications like okular, etc. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups-browsed 1.28.15-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 14 15:53:59 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (941 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType:
[Desktop-packages] [Bug 1989587] Re: Cannot print to autodiscovered printers
Looks related to https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1886653 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1989587 Title: Cannot print to autodiscovered printers Status in cups-filters package in Ubuntu: Confirmed Bug description: I have issues when trying to print on autodiscovered printers. In some cases, cups reports a "permission denied". In other cases, the local queue is not created at all, so that it is impossible to print. However, these printers do appear in the kde print dialog for applications like okular, etc. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups-browsed 1.28.15-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 14 15:53:59 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (941 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/VG_NVMe-root ro quiet splash zswap.enabled=1 vt.handoff=7 SourcePackage: cups-filters UpgradeStatus: Upgraded to jammy on 2022-06-03 (103 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER modified.conffile..etc.cups.cups-browsed.conf: [modified] mtime.conffile..etc.cups.cups-browsed.conf: 2022-09-14T15:52:48.888330 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1989587/+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 1966167] Re: Ubuntu Dock icons not clickable at the edge of the screen
This bug was fixed in the package yaru-theme - 22.10.3 --- yaru-theme (22.10.3) kinetic; urgency=medium * dock: Sync theme with upstream d2d fixes. This includes fixes coming from: - https://github.com/micheleg/dash-to-dock/pull/1826 - https://github.com/micheleg/dash-to-dock/pull/1827 And more importantly: - Increase apps tooltips margins - Set margin for default app-running dots - Remove upstream defined dash-item-container's children margin (LP: #1966167) - Do not add edge padding to edge elements - Fix definition for dash-separator in shrink mode - Take in account side margin and opposite padding in separators - Explicitly use border radius and spacing from upstream - Simplify dash separator definition based on upstream one - Use unique function to handle padding/margin on internal children - avoid computing the shrunk dash padding multiple times - Use generic style generator for shrink mode too - Move mixins to the top of the file for easier re-usage - Use dock-container-style to define the extended cases too - Support shrink and position-based style for labels - Move dock specific variables to dock namespace - Sync global variable definitions with upstream -- Marco Trevisan (Treviño) Sat, 24 Sep 2022 11:11:01 +0200 ** 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 gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1966167 Title: Ubuntu Dock icons not clickable at the edge of the screen Status in Dash to dock: New Status in Yaru Theme: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: New Status in yaru-theme source package in Jammy: New Bug description: If you go to the bottom left corner of the dock and click, the All Apps button doesn't get triggered or highlighted. Check attached video for details. Ubuntu 21.10. Live mode. 1920x1080 screen. To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1966167/+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 1990709] Re: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- 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/1990709 Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 Status in firefox package in Ubuntu: Confirmed Bug description: Snap fails to install during do-release-upgrade from 20.04 to 22.04. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 104.0+build3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203 Uname: Linux 5.4.0-126-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kristv 802 F pulseaudio /dev/snd/controlC1: kristv 802 F pulseaudio BuildID: 20220818191623 CasperMD5CheckResult: unknown Channel: Unavailable Date: Fri Sep 23 22:01:11 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-07-28 (1518 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp2s0 proto dhcp metric 100 169.254.0.0/16 dev enp2s0 scope link metric 1000 192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.10 metric 100 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-09-24 (0 days ago) dmi.bios.date: 02/21/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.name: NC99D3 dmi.board.vendor: Jetway Information Co., Ltd dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: Jetway Information Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/21/2012:svnJetwayInformationCo.,Ltd:pnNC99D3:pvr1.0:rvnJetwayInformationCo.,Ltd:rnNC99D3:rvr1.0:cvnJetwayInformationCo.,Ltd:ct10:cvr1.0: dmi.product.name: NC99D3 dmi.product.version: 1.0 dmi.sys.vendor: Jetway Information Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1990709/+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 1990382] Re: [BPO] libreoffice 7.3.6 for bionic
** Changed in: libreoffice (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1990382 Title: [BPO] libreoffice 7.3.6 for bionic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Bionic: Fix Released Bug description: [Impact] * LibreOffice 7.3.6 is in its sixth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.6_release * This source packages matches the processed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1988744 and a test build is currently available at https://launchpad.net/~libreoffice/+archive/ubuntu/experimental/+packages * Similar backport of 7.3.6 for focal handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1989418 * LibreOffice 6.0.7 (EOL since November 26, 2018) is currently released in bionic. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.6-0ubuntu0.22.04.1 * Backport target is Bionci/18.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/1900/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/amd64/libr/libreoffice/20220921_023821_f6636@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/arm64/libr/libreoffice/20220921_015824_12ef6@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/armhf/libr/libreoffice/20220922_104328_3c444@/log.gz * [i386] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/i386/libr/libreoffice/20220921_150152_8877b@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/ppc64el/libr/libreoffice/20220921_140441_6e26b@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/s390x/libr/libreoffice/20220921_134627_506c7@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1990382/+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 1966167] Re: Ubuntu Dock icons not clickable at the edge of the screen
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 74ubuntu1 --- gnome-shell-extension-ubuntu-dock (74ubuntu1) kinetic; urgency=medium [ Marco Trevisan (Treviño) ] * New EGO upstream bugfix release 74 * debian/control: Bump dependency on gnome-shell << 44 (LP: #1990423) * docking: Respect St.Settings for animation duration * stylesheet: Increase apps tooltips margins * stylesheet: Set margin for default app-running dots * stylesheet: Remove upstream defined dash-item-container's children margins (LP: #1966167) * stylesheet: Do not add edge padding to edge elements * stylesheet: Fix definition for dash-separator in shrink mode * appIcons: Add missing implementation of _setPoupTimeout to wrapped toggle * appIcons: Also redirect arguments, to called methods if any * appIcons: Implement setForcedHighlight function in DockShowAppsIcons * appIcons: Modernize and cleanup DockShowAppsIcon code * docking: Fix arguments for overridden _getAppDisplayBoxForState * Settings: Move the Shrink option to the global theme settings * prefs: Do not request resizing of our root widget on startup * prefs: Never use a scrolled window in newer GNOME Shell * appIcons: Monitor windows workspace changes when isolating workspaces * locations: Make FileManagerApp emit windows-changed on workspace switches (LP: #1971012) * stylesheet: Take in account side margin and opposite padding in separators * stylesheet: Explicitly use border radius and spacing from upstream * stylesheet: Simplify dash separator definition based on upstream one * stylesheet: Use unique function to handle padding/margin on internal children * stylesheet: avoid computing the shrunk dash padding multiple times * stylesheet: Use generic style generator for shrink mode too * stylesheet: Move mixins to the top of the file for easier re-usage * stylesheet: Use dock-container-style to define the extended cases too * docking: Move style classes names to Theming * dash, stylesheet: Support shrink and position-based style for labels * stylesheet: Move dock specific variables to dock namespace * stylesheet: Sync global variable definitions with upstream [ David Astillero Pérez ] * Update Spanish translation [ Jose Riha ] * Update Slovak translation [ rene-coty ] * Updated French Translation -- Marco Trevisan (Treviño) Sat, 24 Sep 2022 10:02:45 +0200 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: In Progress => Fix Released -- 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/1966167 Title: Ubuntu Dock icons not clickable at the edge of the screen Status in Dash to dock: New Status in Yaru Theme: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock source package in Jammy: New Status in yaru-theme source package in Jammy: New Bug description: If you go to the bottom left corner of the dock and click, the All Apps button doesn't get triggered or highlighted. Check attached video for details. Ubuntu 21.10. Live mode. 1920x1080 screen. To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1966167/+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 1971012] Re: Nautilus windows not respecting workspace isolation
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 74ubuntu1 --- gnome-shell-extension-ubuntu-dock (74ubuntu1) kinetic; urgency=medium [ Marco Trevisan (Treviño) ] * New EGO upstream bugfix release 74 * debian/control: Bump dependency on gnome-shell << 44 (LP: #1990423) * docking: Respect St.Settings for animation duration * stylesheet: Increase apps tooltips margins * stylesheet: Set margin for default app-running dots * stylesheet: Remove upstream defined dash-item-container's children margins (LP: #1966167) * stylesheet: Do not add edge padding to edge elements * stylesheet: Fix definition for dash-separator in shrink mode * appIcons: Add missing implementation of _setPoupTimeout to wrapped toggle * appIcons: Also redirect arguments, to called methods if any * appIcons: Implement setForcedHighlight function in DockShowAppsIcons * appIcons: Modernize and cleanup DockShowAppsIcon code * docking: Fix arguments for overridden _getAppDisplayBoxForState * Settings: Move the Shrink option to the global theme settings * prefs: Do not request resizing of our root widget on startup * prefs: Never use a scrolled window in newer GNOME Shell * appIcons: Monitor windows workspace changes when isolating workspaces * locations: Make FileManagerApp emit windows-changed on workspace switches (LP: #1971012) * stylesheet: Take in account side margin and opposite padding in separators * stylesheet: Explicitly use border radius and spacing from upstream * stylesheet: Simplify dash separator definition based on upstream one * stylesheet: Use unique function to handle padding/margin on internal children * stylesheet: avoid computing the shrunk dash padding multiple times * stylesheet: Use generic style generator for shrink mode too * stylesheet: Move mixins to the top of the file for easier re-usage * stylesheet: Use dock-container-style to define the extended cases too * docking: Move style classes names to Theming * dash, stylesheet: Support shrink and position-based style for labels * stylesheet: Move dock specific variables to dock namespace * stylesheet: Sync global variable definitions with upstream [ David Astillero Pérez ] * Update Spanish translation [ Jose Riha ] * Update Slovak translation [ rene-coty ] * Updated French Translation -- Marco Trevisan (Treviño) Sat, 24 Sep 2022 10:02:45 +0200 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: In Progress => Fix Released -- 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/1971012 Title: Nautilus windows not respecting workspace isolation Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: New Bug description: In settings, under multitasking > application switching, setting "include applications from the current workspace only" is supposed to provide workspace isolation, making only apps in the current workspace show in the dock. For example, if I have 2 firefox windows in workspace 1, and a terminal window in workspace 2, terminal should not show as open in the dock in workspace 1, and firefox should not show as open in the dock in workspace 2. Additionally, quitting all windows from right click in the dock should close only all windows of that app in the current workspace. This mostly works correctly, but for some reason some apps, including nautilus and software and updates, do not respect it. If you switch workspaces with them open, the new workspace shows them as having the same number of open windows as the previous workspace, even though no windows are open in that workspace. If you quit with right click from the dock, it sometimes quits all instances across all workspaces. If you open a separate window in the new workspace with right click on the dock, it then updates to the correct number, but the problem then returns on switching back to the previous workspace. If you open and close a window in the new workspace, then switch back to the old one, it is possible to get to a point where despite several windows of the app being open in that workspace, it shows as not open in the dock. The problem persists across different installs and machines To reproduce: Open ubuntu (a live version is fine). Turn on workspace isolation in settings. Pin nautilus to favorites so it shows in the dock. Open a window of nautilus, and a window of some other app (firefox works). Switch workspaces. Observe that an orange dot is still present under nautilus, and it still acts like it is open in the new workspace --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop:
[Desktop-packages] [Bug 1990423] Re: gnome-shell >> 43
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 74ubuntu1 --- gnome-shell-extension-ubuntu-dock (74ubuntu1) kinetic; urgency=medium [ Marco Trevisan (Treviño) ] * New EGO upstream bugfix release 74 * debian/control: Bump dependency on gnome-shell << 44 (LP: #1990423) * docking: Respect St.Settings for animation duration * stylesheet: Increase apps tooltips margins * stylesheet: Set margin for default app-running dots * stylesheet: Remove upstream defined dash-item-container's children margins (LP: #1966167) * stylesheet: Do not add edge padding to edge elements * stylesheet: Fix definition for dash-separator in shrink mode * appIcons: Add missing implementation of _setPoupTimeout to wrapped toggle * appIcons: Also redirect arguments, to called methods if any * appIcons: Implement setForcedHighlight function in DockShowAppsIcons * appIcons: Modernize and cleanup DockShowAppsIcon code * docking: Fix arguments for overridden _getAppDisplayBoxForState * Settings: Move the Shrink option to the global theme settings * prefs: Do not request resizing of our root widget on startup * prefs: Never use a scrolled window in newer GNOME Shell * appIcons: Monitor windows workspace changes when isolating workspaces * locations: Make FileManagerApp emit windows-changed on workspace switches (LP: #1971012) * stylesheet: Take in account side margin and opposite padding in separators * stylesheet: Explicitly use border radius and spacing from upstream * stylesheet: Simplify dash separator definition based on upstream one * stylesheet: Use unique function to handle padding/margin on internal children * stylesheet: avoid computing the shrunk dash padding multiple times * stylesheet: Use generic style generator for shrink mode too * stylesheet: Move mixins to the top of the file for easier re-usage * stylesheet: Use dock-container-style to define the extended cases too * docking: Move style classes names to Theming * dash, stylesheet: Support shrink and position-based style for labels * stylesheet: Move dock specific variables to dock namespace * stylesheet: Sync global variable definitions with upstream [ David Astillero Pérez ] * Update Spanish translation [ Jose Riha ] * Update Slovak translation [ rene-coty ] * Updated French Translation -- Marco Trevisan (Treviño) Sat, 24 Sep 2022 10:02:45 +0200 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Fix Committed => Fix Released -- 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/1990423 Title: gnome-shell >> 43 Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: Wondering if will it be still supported for gnome-shell version 43 and above? especially in kinetic kudu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1990423/+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 1988315] Re: gnome-shell crashed with SIGABRT [Clutter:ERROR:../clutter/clutter/clutter-actor.c:11749:clutter_actor_destroy_all_children: assertion failed: (self->priv->n_child
Could someone test if the changes in https://github.com/ubuntu/gnome- shell-extension-appindicator/pull/364 help with this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1988315 Title: gnome-shell crashed with SIGABRT [Clutter:ERROR:../clutter/clutter/clutter- actor.c:11749:clutter_actor_destroy_all_children: assertion failed: (self->priv->n_children < prev_n_children)] in indicatorStatusIcon.js:317 Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Fedora: Confirmed Bug description: After upgrading to kinetic gnome-shell is crashing on start when using wayland. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 31 10:28:31 2022 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20200511-23+sutton-knuth-bionic-amd64+iso InstallationDate: Installed on 2020-05-18 (834 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20200511-12:31 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-08-30 (0 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-05-11T08:18:53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1988315/+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 1990719] [NEW] After switching the workspace, the taskbar icon of nautilus displays abnormally
Public bug reported: After switches the workspace, the taskbar icon of nautilus displays abnormally. 1. The number of windows(the number of the orange dots) of nautilus is incorrect. 2. After left clicking on the icon, nothing happened. 3. After clicking middle mouse button on the icon, all the things will be OK. 4. After closing a window of nautilus, the icon in other workspaces is incorrect. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470.1 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 16:16:16 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" LiveMediaBuild: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- 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/1990719 Title: After switching the workspace, the taskbar icon of nautilus displays abnormally Status in nautilus package in Ubuntu: New Bug description: After switches the workspace, the taskbar icon of nautilus displays abnormally. 1. The number of windows(the number of the orange dots) of nautilus is incorrect. 2. After left clicking on the icon, nothing happened. 3. After clicking middle mouse button on the icon, all the things will be OK. 4. After closing a window of nautilus, the icon in other workspaces is incorrect. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470.1 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 16:16:16 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" LiveMediaBuild: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1990719/+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 1990423] Re: gnome-shell >> 43
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => Fix Committed -- 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/1990423 Title: gnome-shell >> 43 Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Committed Bug description: Wondering if will it be still supported for gnome-shell version 43 and above? especially in kinetic kudu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1990423/+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 1966167] Re: Ubuntu Dock icons not clickable at the edge of the screen
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: yaru-theme (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: yaru-theme (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: yaru-theme (Ubuntu Jammy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1966167 Title: Ubuntu Dock icons not clickable at the edge of the screen Status in Dash to dock: New Status in Yaru Theme: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Status in yaru-theme package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock source package in Jammy: New Status in yaru-theme source package in Jammy: New Bug description: If you go to the bottom left corner of the dock and click, the All Apps button doesn't get triggered or highlighted. Check attached video for details. Ubuntu 21.10. Live mode. 1920x1080 screen. To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1966167/+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 1971012] Re: Nautilus windows not respecting workspace isolation
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => In Progress ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1971012 Title: Nautilus windows not respecting workspace isolation Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock source package in Jammy: New Bug description: In settings, under multitasking > application switching, setting "include applications from the current workspace only" is supposed to provide workspace isolation, making only apps in the current workspace show in the dock. For example, if I have 2 firefox windows in workspace 1, and a terminal window in workspace 2, terminal should not show as open in the dock in workspace 1, and firefox should not show as open in the dock in workspace 2. Additionally, quitting all windows from right click in the dock should close only all windows of that app in the current workspace. This mostly works correctly, but for some reason some apps, including nautilus and software and updates, do not respect it. If you switch workspaces with them open, the new workspace shows them as having the same number of open windows as the previous workspace, even though no windows are open in that workspace. If you quit with right click from the dock, it sometimes quits all instances across all workspaces. If you open a separate window in the new workspace with right click on the dock, it then updates to the correct number, but the problem then returns on switching back to the previous workspace. If you open and close a window in the new workspace, then switch back to the old one, it is possible to get to a point where despite several windows of the app being open in that workspace, it shows as not open in the dock. The problem persists across different installs and machines To reproduce: Open ubuntu (a live version is fine). Turn on workspace isolation in settings. Pin nautilus to favorites so it shows in the dock. Open a window of nautilus, and a window of some other app (firefox works). Switch workspaces. Observe that an orange dot is still present under nautilus, and it still acts like it is open in the new workspace --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-04-25 (735 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-30 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1971012/+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 1966167] Re: Ubuntu Dock icons not clickable at the edge of the screen
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => In Progress ** Changed in: yaru-theme (Ubuntu) Status: Confirmed => Triaged ** Changed in: yaru-theme (Ubuntu) Status: Triaged => In Progress -- 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/1966167 Title: Ubuntu Dock icons not clickable at the edge of the screen Status in Dash to dock: New Status in Yaru Theme: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Status in yaru-theme package in Ubuntu: In Progress Bug description: If you go to the bottom left corner of the dock and click, the All Apps button doesn't get triggered or highlighted. Check attached video for details. Ubuntu 21.10. Live mode. 1920x1080 screen. To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1966167/+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
