[Desktop-packages] [Bug 2045375] [NEW] Sound Output Device : Dummy Output
Public bug reported: Fresh install and there is no sound. The only option in Sound Output Device settings is `Dummy Output`. I attempted a fix described at https://askubuntu.com/a/1236100 which revealed different output devices, but still no sound. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3 Uname: Linux 6.5.0-13-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nils 1388 F wireplumber /dev/snd/seq:nils 1378 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 30 21:49:16 2023 InstallationDate: Installed on 2023-11-30 (0 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2023 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 522.0.0.0.0 dmi.board.name: Mac-4B682C642B45593E dmi.board.vendor: Apple Inc. dmi.board.version: iMac18,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-4B682C642B45593E dmi.modalias: dmi:bvnAppleInc.:bvr522.0.0.0.0:bd08/17/2023:br0.1:svnAppleInc.:pniMac18,1:pvr1.0:rvnAppleInc.:rnMac-4B682C642B45593E:rvriMac18,1:cvnAppleInc.:ct9:cvrMac-4B682C642B45593E:sku: dmi.product.family: iMac dmi.product.name: iMac18,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2023-11-30T21:48:48.924029 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- 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/2045375 Title: Sound Output Device : Dummy Output Status in alsa-driver package in Ubuntu: New Bug description: Fresh install and there is no sound. The only option in Sound Output Device settings is `Dummy Output`. I attempted a fix described at https://askubuntu.com/a/1236100 which revealed different output devices, but still no sound. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3 Uname: Linux 6.5.0-13-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nils 1388 F wireplumber /dev/snd/seq:nils 1378 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 30 21:49:16 2023 InstallationDate: Installed on 2023-11-30 (0 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2023 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 522.0.0.0.0 dmi.board.name: Mac-4B682C642B45593E dmi.board.vendor: Apple Inc. dmi.board.version: iMac18,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-4B682C642B45593E dmi.modalias: dmi:bvnAppleInc.:bvr522.0.0.0.0:bd08/17/2023:br0.1:svnAppleInc.:pniMac18,1:pvr1.0:rvnAppleInc.:rnMac-4B682C642B45593E:rvriMac18,1:cvnAppleInc.:ct9:cvrMac-4B682C642B45593E:sku: dmi.product.family: iMac dmi.product.name: iMac18,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2023-11-30T21:48:48.924029 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2045375/+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 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
Attached is a debdiff that resolves the issue on Jammy. Version 5. ** Patch added: "Debdiff for tracker-miners on Jammy v5" https://bugs.launchpad.net/ubuntu/noble/+source/tracker-miners/+bug/1779890/+attachment/5725475/+files/lp1779890_jammy_v5.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in gvfs package in Ubuntu: Invalid Status in tracker-miners package in Ubuntu: In Progress Status in gvfs source package in Bionic: Invalid Status in tracker-miners source package in Bionic: Won't Fix Status in gvfs source package in Focal: Invalid Status in tracker-miners source package in Focal: In Progress Status in gvfs source package in Jammy: Invalid Status in tracker-miners source package in Jammy: In Progress Status in gvfs source package in Kinetic: Invalid Status in tracker-miners source package in Kinetic: Won't Fix Status in gvfs source package in Lunar: Invalid Status in tracker-miners source package in Lunar: In Progress Status in gvfs source package in Mantic: Invalid Status in tracker-miners source package in Mantic: In Progress Status in gvfs source package in Noble: Invalid Status in tracker-miners source package in Noble: In Progress Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search operations in Gnome. The tracker-miners is the indexing daemon that populates the database with information, so changing its start does not affect the system behavior. This changes fix the startup of gvfs-daemon.service, which could delay services that relied on it running to be executed. [ Other info ] This was fixed upstream by the following commit:
[Desktop-packages] [Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
Attached is a debdiff that resolves the issue on Focal. Version 5. ** Patch added: "Debdiff for tracker-miners on Focal v5" https://bugs.launchpad.net/ubuntu/noble/+source/tracker-miners/+bug/1779890/+attachment/5725476/+files/lp1779890_focal_v5.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in gvfs package in Ubuntu: Invalid Status in tracker-miners package in Ubuntu: In Progress Status in gvfs source package in Bionic: Invalid Status in tracker-miners source package in Bionic: Won't Fix Status in gvfs source package in Focal: Invalid Status in tracker-miners source package in Focal: In Progress Status in gvfs source package in Jammy: Invalid Status in tracker-miners source package in Jammy: In Progress Status in gvfs source package in Kinetic: Invalid Status in tracker-miners source package in Kinetic: Won't Fix Status in gvfs source package in Lunar: Invalid Status in tracker-miners source package in Lunar: In Progress Status in gvfs source package in Mantic: Invalid Status in tracker-miners source package in Mantic: In Progress Status in gvfs source package in Noble: Invalid Status in tracker-miners source package in Noble: In Progress Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search operations in Gnome. The tracker-miners is the indexing daemon that populates the database with information, so changing its start does not affect the system behavior. This changes fix the startup of gvfs-daemon.service, which could delay services that relied on it running to be executed. [ Other info ] This was fixed upstream by the following commit:
[Desktop-packages] [Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
Attached is a debdiff that resolves the issue on lunar. Version 5. ** Patch added: "Debdiff for tracker-miners on Lunar v5" https://bugs.launchpad.net/ubuntu/noble/+source/tracker-miners/+bug/1779890/+attachment/5725474/+files/lp1779890_lunar_v5.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in gvfs package in Ubuntu: Invalid Status in tracker-miners package in Ubuntu: In Progress Status in gvfs source package in Bionic: Invalid Status in tracker-miners source package in Bionic: Won't Fix Status in gvfs source package in Focal: Invalid Status in tracker-miners source package in Focal: In Progress Status in gvfs source package in Jammy: Invalid Status in tracker-miners source package in Jammy: In Progress Status in gvfs source package in Kinetic: Invalid Status in tracker-miners source package in Kinetic: Won't Fix Status in gvfs source package in Lunar: Invalid Status in tracker-miners source package in Lunar: In Progress Status in gvfs source package in Mantic: Invalid Status in tracker-miners source package in Mantic: In Progress Status in gvfs source package in Noble: Invalid Status in tracker-miners source package in Noble: In Progress Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search operations in Gnome. The tracker-miners is the indexing daemon that populates the database with information, so changing its start does not affect the system behavior. This changes fix the startup of gvfs-daemon.service, which could delay services that relied on it running to be executed. [ Other info ] This was fixed upstream by the following commit:
[Desktop-packages] [Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
Attached is a debdiff that resolves the issue on mantic. Version 5. ** Patch added: "Debdiff for tracker-miners on Mantic v5" https://bugs.launchpad.net/ubuntu/noble/+source/tracker-miners/+bug/1779890/+attachment/5725473/+files/lp1779890_mantic_v5.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in gvfs package in Ubuntu: Invalid Status in tracker-miners package in Ubuntu: In Progress Status in gvfs source package in Bionic: Invalid Status in tracker-miners source package in Bionic: Won't Fix Status in gvfs source package in Focal: Invalid Status in tracker-miners source package in Focal: In Progress Status in gvfs source package in Jammy: Invalid Status in tracker-miners source package in Jammy: In Progress Status in gvfs source package in Kinetic: Invalid Status in tracker-miners source package in Kinetic: Won't Fix Status in gvfs source package in Lunar: Invalid Status in tracker-miners source package in Lunar: In Progress Status in gvfs source package in Mantic: Invalid Status in tracker-miners source package in Mantic: In Progress Status in gvfs source package in Noble: Invalid Status in tracker-miners source package in Noble: In Progress Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search operations in Gnome. The tracker-miners is the indexing daemon that populates the database with information, so changing its start does not affect the system behavior. This changes fix the startup of gvfs-daemon.service, which could delay services that relied on it running to be executed. [ Other info ] This was fixed upstream by the following commit:
[Desktop-packages] [Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
Attached is a debdiff that resolves this issue on debian unstable / noble. ** Patch removed: "Debdiff for tracker-miners on Focal V3" https://bugs.launchpad.net/ubuntu/noble/+source/tracker-miners/+bug/1779890/+attachment/5679384/+files/lp1779890_focal_v3.debdiff ** Patch removed: "Debdiff for tracker-miners on Kinetic V3" https://bugs.launchpad.net/ubuntu/noble/+source/tracker-miners/+bug/1779890/+attachment/5679386/+files/lp1779890_kinetic_v3.debdiff ** Patch removed: "Debdiff for tracker-miners on Lunar V3" https://bugs.launchpad.net/ubuntu/noble/+source/tracker-miners/+bug/1779890/+attachment/5679387/+files/lp1779890_lunar_v3.debdiff ** Patch removed: "Debdiff for tracker-miners on Mantic V3" https://bugs.launchpad.net/ubuntu/noble/+source/tracker-miners/+bug/1779890/+attachment/5679388/+files/lp1779890_mantic_v3.debdiff ** Patch removed: "Debdiff for tracker-miners on Jammy V4" https://bugs.launchpad.net/ubuntu/noble/+source/tracker-miners/+bug/1779890/+attachment/5680090/+files/lp1779890_jammy_v4.debdiff ** Patch added: "Debdiff for tracker-miners on unstable v5" https://bugs.launchpad.net/ubuntu/noble/+source/tracker-miners/+bug/1779890/+attachment/5725472/+files/tracker-miners_unstable.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in gvfs package in Ubuntu: Invalid Status in tracker-miners package in Ubuntu: In Progress Status in gvfs source package in Bionic: Invalid Status in tracker-miners source package in Bionic: Won't Fix Status in gvfs source package in Focal: Invalid Status in tracker-miners source package in Focal: In Progress Status in gvfs source package in Jammy: Invalid Status in tracker-miners source package in Jammy: In Progress Status in gvfs source package in Kinetic: Invalid Status in tracker-miners source package in Kinetic: Won't Fix Status in gvfs source package in Lunar: Invalid Status in tracker-miners source package in Lunar: In Progress Status in gvfs source package in Mantic: Invalid Status in tracker-miners source package in Mantic: In Progress Status in gvfs source package in Noble: Invalid Status in tracker-miners source package in Noble: In Progress Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is
[Desktop-packages] [Bug 1958019]
Created attachment 305523 alsa-info.txt Thanks Cameron! Adding those files to /lib/firmware didn't work (I copied the files directly), so I'm probably out of luck for now. I've attached my alsa-info.txt in case it helps. On Thu, Nov 30, 2023 at 10:45 AM wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > --- Comment #788 from Cameron Berkenpas (c...@neo-zeon.de) --- > Andrew, the verb approach doesn't work here as smart amps are being used. > > The tas2781 smart amp is generally supported as of kernel 6.6... but now > it's a > question of if firmware for your laptop is available. > > Without your alsa-info, I can't tell if your laptop is supported... > > But you can just try the firmware for yourself from here: > https://neo-zeon.de/~hiryu/tas/firmware-6.6.tar.bz2 > > Just copy the files into /lib/firmware/ and reboot. Hopefully you have > sound. > > A number of Lenovo laptops with tas2781 are supported, but I don't think > the > list is anywhere near comprehensive so we'll see..? > > Good luck! > > I'm not sure if these firmware files are yet in the pipeline to be commonly > redistributed at this time... I'll see if there's something I can do to get > that process started. > > (In reply to Andrew from comment #787) > > > From lsmod: > > snd_soc_tas2781_fmwlib53248 1 snd_hda_scodec_tas2781_i2c > > snd_soc_tas2781_comlib24576 2 > > snd_soc_tas2781_fmwlib,snd_hda_scodec_tas2781_i2c > > > > From dmesg (1f.3 is the device, I think): > > [0.709119] pci :00:1f.0: [8086:519f] type 00 class 0x060100 > > [0.709450] pci :00:1f.3: [8086:51cf] type 00 class 0x040100 > > [0.709492] pci :00:1f.3: reg 0x10: [mem 0x620319-0x6203193fff > > 64bit] > > [0.709546] pci :00:1f.3: reg 0x20: [mem 0x620300-0x62030f > > 64bit] > > [0.709651] pci :00:1f.3: PME# supported from D3hot D3cold > > [0.709735] pci :00:1f.4: [8086:51a3] type 00 class 0x0c0500 > > [0.709756] pci :00:1f.4: reg 0x10: [mem 0x620319c000-0x620319c0ff > > 64bit] > > [0.709778] pci :00:1f.4: reg 0x20: [io 0xefa0-0xefbf] > > [0.710013] pci :00:1f.5: [8086:51a4] type 00 class 0x0c8000 > > [0.710035] pci :00:1f.5: reg 0x10: [mem 0xfe01-0xfe010fff] > > > > I have a separate grub entry to boot without sound (for qemu sniffing) > using > > these flags: modprobe.blacklist=snd_hda_intel,snd_sof_pci_intel_tgl > > pci-stub.ids=8086:51cf iommu=pt intel_iommu=on > > > > I'm not sure if that's enough. Happy to help in any way! > > -- > You may reply to this email to add a comment. > > You are receiving this mail because: > You are on the CC list for the bug. -- 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
[Desktop-packages] [Bug 1958019]
Andrew, the verb approach doesn't work here as smart amps are being used. The tas2781 smart amp is generally supported as of kernel 6.6... but now it's a question of if firmware for your laptop is available. Without your alsa-info, I can't tell if your laptop is supported... But you can just try the firmware for yourself from here: https://neo-zeon.de/~hiryu/tas/firmware-6.6.tar.bz2 Just copy the files into /lib/firmware/ and reboot. Hopefully you have sound. A number of Lenovo laptops with tas2781 are supported, but I don't think the list is anywhere near comprehensive so we'll see..? Good luck! I'm not sure if these firmware files are yet in the pipeline to be commonly redistributed at this time... I'll see if there's something I can do to get that process started. (In reply to Andrew from comment #787) > From lsmod: > snd_soc_tas2781_fmwlib53248 1 snd_hda_scodec_tas2781_i2c > snd_soc_tas2781_comlib24576 2 > snd_soc_tas2781_fmwlib,snd_hda_scodec_tas2781_i2c > > From dmesg (1f.3 is the device, I think): > [0.709119] pci :00:1f.0: [8086:519f] type 00 class 0x060100 > [0.709450] pci :00:1f.3: [8086:51cf] type 00 class 0x040100 > [0.709492] pci :00:1f.3: reg 0x10: [mem 0x620319-0x6203193fff > 64bit] > [0.709546] pci :00:1f.3: reg 0x20: [mem 0x620300-0x62030f > 64bit] > [0.709651] pci :00:1f.3: PME# supported from D3hot D3cold > [0.709735] pci :00:1f.4: [8086:51a3] type 00 class 0x0c0500 > [0.709756] pci :00:1f.4: reg 0x10: [mem 0x620319c000-0x620319c0ff > 64bit] > [0.709778] pci :00:1f.4: reg 0x20: [io 0xefa0-0xefbf] > [0.710013] pci :00:1f.5: [8086:51a4] type 00 class 0x0c8000 > [0.710035] pci :00:1f.5: reg 0x10: [mem 0xfe01-0xfe010fff] > > I have a separate grub entry to boot without sound (for qemu sniffing) using > these flags: modprobe.blacklist=snd_hda_intel,snd_sof_pci_intel_tgl > pci-stub.ids=8086:51cf iommu=pt intel_iommu=on > > I'm not sure if that's enough. Happy to help in any way! -- 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
[Desktop-packages] [Bug 1958019]
Is there some way I can help to get Realtek/tas working for the Lenovo Slim Pro 9i (named Yoga Slim 9i outside of the US)? On my Manjaro install, the top speakers work (although I don't think they're amplified?) and the bottom subwoofers are off. I've managed to get qemu working for sniffing following this guide: https://github.com/ryanprescott/realtek-verb-tools/wiki/How-to-sniff-verbs-from-a-Windows-sound-driver At one point, Win10 in qemu had sound working similar to Linux (only top-firing, maybe unamplified), and I saw event logs, but I don't remember the driver. I might need to do a clean install at this point. When I try to install the driver in qemu in win10 or win11, I get a bluescreen. Windows is using Realtek Semi Corp ver 6.0.9553.1. uname: Linux andrew-slim 6.6.2-1-MANJARO #1 SMP PREEMPT_DYNAMIC Mon Nov 20 13:00:47 UTC 2023 x86_64 GNU/Linux lspci shows: 00:1f.3 Multimedia audio controller: Intel Corporation Device 51cf (rev 01) Subsystem: Lenovo Device 3802 Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: Data: Kernel driver in use: vfio-pci Kernel modules: snd_hda_intel, snd_sof_pci_intel_tg >From lsmod: snd_soc_tas2781_fmwlib53248 1 snd_hda_scodec_tas2781_i2c snd_soc_tas2781_comlib24576 2 snd_soc_tas2781_fmwlib,snd_hda_scodec_tas2781_i2c >From dmesg (1f.3 is the device, I think): [0.709119] pci :00:1f.0: [8086:519f] type 00 class 0x060100 [0.709450] pci :00:1f.3: [8086:51cf] type 00 class 0x040100 [0.709492] pci :00:1f.3: reg 0x10: [mem 0x620319-0x6203193fff 64bit] [0.709546] pci :00:1f.3: reg 0x20: [mem 0x620300-0x62030f 64bit] [0.709651] pci :00:1f.3: PME# supported from D3hot D3cold [0.709735] pci :00:1f.4: [8086:51a3] type 00 class 0x0c0500 [0.709756] pci :00:1f.4: reg 0x10: [mem 0x620319c000-0x620319c0ff 64bit] [0.709778] pci :00:1f.4: reg 0x20: [io 0xefa0-0xefbf] [0.710013] pci :00:1f.5: [8086:51a4] type 00 class 0x0c8000 [0.710035] pci :00:1f.5: reg 0x10: [mem 0xfe01-0xfe010fff] I have a separate grub entry to boot without sound (for qemu sniffing) using these flags: modprobe.blacklist=snd_hda_intel,snd_sof_pci_intel_tgl pci- stub.ids=8086:51cf iommu=pt intel_iommu=on I'm not sure if that's enough. Happy to help in any way! -- 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
[Desktop-packages] [Bug 1787103] Re: app crashes during start
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1787103 Title: app crashes during start Status in firefox package in Ubuntu: Expired Bug description: Hello there! Im using ARMbian Ubuntu 16.04 LTS, this might not supported, but Chrome starts without any problem. Starting the browser shows: p@orangepiplus2e:~/Desktop$ /usr/lib/firefox/firefox ExceptionHandler::GenerateDump cloned child 7346 ExceptionHandler::WaitForContinueSignal waiting for continue signal... ExceptionHandler::SendContinueSignalToChild sent continue signal to child Using GDB: (gdb) run The program being debugged has been started already. Start it from the beginning? (y or n) y Starting program: /usr/lib/firefox/firefox Program received signal SIGSEGV, Segmentation fault. 0xb6fd9dde in ?? () from /lib/ld-linux-armhf.so.3 Regards ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 61.0.1+build1-0ubuntu0.16.04.1 Uname: Linux 3.4.113-sun8i armv7l AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. ApportVersion: 2.20.1-0ubuntu2.18 Architecture: armhf AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: p 1606 F pulseaudio /dev/snd/controlC0: p 1606 F pulseaudio BuildID: 2018070541 Card0.Amixer.info: Card hw:0 'audiocodec'/'audiocodec' Mixer name : '' Components : '' Controls : 12 Simple ctrls : 12 Card1.Amixer.info: Card hw:1 'sndhdmi'/'sndhdmi' Mixer name : '' Components : '' Controls : 1 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'hdmi audio format Function',0 Capabilities: enum Items: 'null' 'pcm' 'AC3' 'MPEG1' 'MP3' 'MPEG2' 'AAC' 'DTS' 'ATRAC' 'ONE_BIT_AUDIO' 'DOLBY_DIGITAL_PLUS' 'DTS_HD' 'MAT' 'WMAPRO' Item0: 'pcm' Channel: Unavailable CurrentDesktop: XFCE Date: Wed Aug 15 06:29:01 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 10.42.0.1 dev eth0 proto static metric 100 169.254.0.0/16 dev eth0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-ccb6ac7a-cf58-469b-945a-391e30180815 PciMultimedia: PciNetwork: PrefErrors: Unexpected character ',' whilst parsing int @ /usr/lib/firefox/defaults/pref/vendor-gre.js:8 Profiles: Profile0 (Default) - LastVersion=61.0.1/2018070541 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-ccb6ac7a-cf58-469b-945a-391e30180815 bp-7f85f181-dd31-4fd2-bb1c-9c1b70180815 bp-10cd0009-5b48-4b1e-b72b-edda10180815 bp-7128a1c0-d973-41a3-98c5-1dd130180815 Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1787103/+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 1834217] Re: Firefox restarts occasionally
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1834217 Title: Firefox restarts occasionally Status in firefox package in Ubuntu: Expired Bug description: Description: Ubuntu 18.04.2 LTS Release: 18.04 firefox: Installed: 67.0.4+build1-0ubuntu0.18.04.1 Candidate: 67.0.4+build1-0ubuntu0.18.04.1 Version table: *** 67.0.4+build1-0ubuntu0.18.04.1 500 500 http://se.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 59.0.2+build1-0ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu bionic/main amd64 Packages I got somewhat frustrated the other day when it happened - again, Firefox restarted without me updating it or anything like that. So I lashed out on Twitter (https://twitter.com/tmhanssonit/status/1142370265042685952) and ended up here. I don't know what the casue is, but some background information: I have multiple tabs open, some of them are standard tabs like email, Github, my webshop and so on. At any given time I have maximum 10-15 tabs open, but usually only around 5. Sometimes when opening a new tab Firefox greets me with this little thing: https://i.imgur.com/zLD8o9x.png and I need to restart Firefox (which never opens automatically again btw) and all my login cache are cleaned (that's how my settings are) which means I have to enter my 2FA in all the tabs again. I would be totally fine with this if I was the one deciding when to restart and when not to, but when Firefox makes the decisions over my head, sometimes several times per day, I get frustrated. When using Windows I noticed that Firefox asks the user something like "do you want to do this now" with an option to do it later. Why isn't that implemented in Ubuntu as well? Thanks for all your hard work btw. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 67.0.4+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: daniel 3119 F pulseaudio /dev/snd/controlC0: daniel 3119 F pulseaudio BuildID: 20190620092152 Channel: Unavailable Date: Tue Jun 25 17:51:16 2019 ForcedLayersAccel: False InstallationDate: Installed on 2018-11-17 (220 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) IpRoute: default via 192.168.2.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.2.0/24 dev wlp2s0 proto kernel scope link src 192.168.2.10 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1834217/+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 1816090] Re: Firefox does not play YouTube anymore after some update
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1816090 Title: Firefox does not play YouTube anymore after some update Status in firefox package in Ubuntu: Expired Bug description: After some update Firefox 65.0 does not play YouTube videos anymore in some virtual machines of Virtualbox 6.04. The following VM were tested and found wrong Xubuntu 18.04.2, Ubuntu Mate 18.04.2 both with Linux 4.18 and Ubuntu 16.04 with Linux 4.15. The same Firefox release does play those video correctly using real hardware with Ubuntu Mate 18.04.2 and Linux 4.15 and in the Virtual machines of Linux Mint 19.1 and Peppermint 9, both with Linux 4.15. Also the Firefox Development 66.0b7 edition has that same problem. Opera, Chrome and Chromium still do play those videos correctly in the Virtual Machines, which do not play with Firefox. On starting the YouTube video, it starts, it buffers to get the normal 2 minutes. But after a approx. 9 frames, it halts displaying the video. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 65.0+build2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bertadmin 1776 F pulseaudio /dev/snd/pcmC0D0p: bertadmin 1776 F...m pulseaudio /dev/snd/timer: bertadmin 1776 f pulseaudio BuildID: 20190128144255 Channel: Unavailable CurrentDesktop: MATE Date: Fri Feb 15 10:55:10 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.0.1 dev enp0s3 proto dhcp metric 100 169.254.0.0/16 dev enp0s3 scope link metric 1000 192.168.0.0/24 dev enp0s3 proto kernel scope link src 192.168.0.109 metric 100 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile0 - LastVersion=66.0/20190211185957 (Out of date) Profile1 (Default) - LastVersion=65.0/20190128144255 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1816090/+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 1909145] Re: Part of the application window becomes transparent and/or pixelated
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1909145 Title: Part of the application window becomes transparent and/or pixelated Status in firefox package in Ubuntu: Expired Bug description: 1 When I open Firefox. There are many graphical bugs: some part of the window become pixelated and/or transparent ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 84.0+build3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-7630.32~1607010078~20.04~383a644~dev-generic 5.8.17 Uname: Linux 5.8.0-7630-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vtfrisari 1874 F pulseaudio BuildID: 20201211215739 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Dec 23 21:45:30 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IpRoute: default via 192.168.43.1 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.43.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.43.105 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=84.0/20201211215739 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2020 dmi.bios.release: 4.13 dmi.bios.vendor: coreboot dmi.bios.version: 2020-12-15_79d6fa7 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp5 dmi.chassis.type: 9 dmi.chassis.vendor: System76 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr2020-12-15_79d6fa7:bd12/15/2020:br4.13:efr0.0:svnSystem76:pnGalagoPro:pvrgalp5:rvnSystem76:rnGalagoPro:rvrgalp5:cvnSystem76:ct9:cvr: dmi.product.name: Galago Pro dmi.product.version: galp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1909145/+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 1858280] Re: Firefox reports "cannot connect to internet" message
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1858280 Title: Firefox reports "cannot connect to internet" message Status in firefox package in Ubuntu: Expired Bug description: Upon initial start-up, when opening Firefox browser, a "cannot connect to internet message" is displayed on-screen. It suggest to check wiring, but wiring is fine but I checked it still. I run the diagnostics and go to submit trouble report and the bug clears out. The diagnostics do a list of program files that I have submitted numerous times alreadyToday the disconnect happened on 2nd startup after computer was shut down for a bit. I always use Firefox browser, and never had problems before these incidents. I am always able to recover after diagnostics are run. Is there a bug clearing program that I can run to clear out this nuisance problem?? Thank you for your time, J. Chosta ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Jan 4 10:33:13 2020 DistUpgraded: 2018-12-25 11:16:26,692 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 2400 Pro [1028:0302] InstallationDate: Installed on 2016-08-03 (1249 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Dell XPS420 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=e737e1ac-8869-44b7-a03f-477223f8 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-25 (374 days ago) dmi.bios.date: 03/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TP406 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/27/2008:svnDellInc.:pnDellXPS420:pvr:rvnDellInc.:rn0TP406:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dell XPS420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Dec 25 08:33:58 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Logitech USB Speaker KEYBOARD, id 8 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 9 inputDell Dell USB Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1858280/+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 1909846] Re: firefox 84.0 lagging a lot
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1909846 Title: firefox 84.0 lagging a lot Status in firefox package in Ubuntu: Expired Bug description: i dual booted ubuntu 20.04 a week ago. but just after 2-3 days, firefox started lagging and a lot. by lagging , i mean when i open a new tab it opens but doesn't show on the screen that it has. when changing opened tabs it doesn't show till i change 2 or more tabs (sometimes it doesn't even do that). when i type something in address bar it doesn't show anything until i press enter and it shows everything on that website. same problem with scrolling. result of neofetch: `:+ss+:` - -+ssyy+- OS: Ubuntu 20.04.1 LTS x86_64 .ossdMMMNyo. Host: Inspiron 3558 /ssshdmmNNmmyNhss/ Kernel: 5.4.0-58-generic +shmydMMMNy+ Uptime: 52 mins /hNMMMyhhhmNMMMNh/Packages: 1808 (dpkg), 6 (flatpak), .dMMMNhsshNMMMd. Shell: bash 5.0.17 +hhhyNMMNyyNMMMysss+ Resolution: 1366x768 ossyNMMMNyMMhsshmmmhssso DE: GNOME ossyNMMMNyMMhsshmmmhssso WM: Mutter +hhhyNMMNyyNMMMysss+ WM Theme: Adwaita .dMMMNhsshNMMMd. Theme: Yaru [GTK2/3] /hNMMMyhhhdNMMMNh/Icons: Yaru [GTK2/3] +sdmydy+ Terminal: gnome-terminal /ssshdmmyNhss/ CPU: Intel i3-5005U (4) @ 1.900GHz .ossdMMMNyo. GPU: Intel HD Graphics 5500 -+syyy+- Memory: 3031MiB / 11891MiB ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 84.0+build3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: schnyd3r 2786 F pulseaudio /dev/snd/controlC0: schnyd3r 2786 F pulseaudio BuildID: 20201211215739 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sat Jan 2 11:49:27 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-12-30 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.42.129 dev usb0 proto dhcp metric 100 default via 192.168.1.1 dev wlp6s0 proto dhcp metric 600 169.254.0.0/16 dev wlp6s0 scope link metric 1000 192.168.1.0/24 dev wlp6s0 proto kernel scope link src 192.168.1.39 metric 600 192.168.42.0/24 dev usb0 proto kernel scope link src 192.168.42.61 metric 100 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=84.0/20201211215739 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: A21 dmi.board.name: 0XCR91 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA21:bd07/09/2020:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XCR91:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.product.sku: 06B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1909846/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1922686] Re: Can't log in every time lightdm Xubuntu 20.04.2.1
[Expired for lightdm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lightdm (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1922686 Title: Can't log in every time lightdm Xubuntu 20.04.2.1 Status in lightdm package in Ubuntu: Expired Bug description: I select my username on the login screen, enter my password, the password field becomes inactive and nothing happens. If I try a second time by switching to "other user" and then back to myself, filling in the password again, it sometimes logs in and other times prints a message saying login failed. Then I have to restart via the console, which also takes an unreasonable amount of time. Also, there is a mysterious "Guest" account that I didn't create, which is not in the user list, and also requires a password, which I couldn't find anywhere on the internet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1922686/+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 1937957] Re: external hyperlink keyboard freeze
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1937957 Title: external hyperlink keyboard freeze Status in firefox package in Ubuntu: Expired Bug description: When no FireFox windows are currently open and an external hyperlink, specifically those opened with Evince, is used then the created window freezes the keyboard. New tabs as well as new opened windows experience the same issue as long as the original window is still open. Windows key + F9 and Windows key + Shift have no effect. Some of the Ctrl functions still work in the window/s and the keyboard freeze is only localized to FireFox. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 90.0+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.4.0-80.90~18.04.1-generic 5.4.124 Uname: Linux 5.4.0-80-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: denmark1731 F pulseaudio /dev/snd/pcmC0D0p: denmark1731 F...m pulseaudio BuildID: 20210705185941 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Jul 25 22:31:20 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:355 DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2021-01-08 (198 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) IpRoute: default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.115 metric 600 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:355 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=90.0/20210705185941 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2012 dmi.bios.vendor: Acer dmi.bios.version: V1.08 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5733 dmi.board.vendor: Acer dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnAcer:bvrV1.08:bd03/21/2012:svnAcer:pnAspire5733:pvrV1.08:rvnAcer:rnAspire5733:rvrV1.08:cvnAcer:ct10:cvrV1.08: dmi.product.family: Intel_Mobile dmi.product.name: Aspire 5733 dmi.product.sku: Calpella_CRB dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1937957/+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 2045349] [NEW] cheese not working properly image shattring
Public bug reported: when i open cheese it image shattering and display the smae image it capured first it act like not ending loop ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 1 09:23:21 2023 InstallationDate: Installed on 2023-01-08 (326 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20YG004YUE RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: cheese UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2022 dmi.bios.release: 1.12 dmi.bios.vendor: LENOVO dmi.bios.version: R1OET33W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20YG004YUE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR1OET33W(1.12):bd05/07/2022:br1.12:efr1.12:svnLENOVO:pn20YG004YUE:pvrThinkPadE15Gen3:rvnLENOVO:rn20YG004YUE:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20YG_BU_Think_FM_ThinkPadE15Gen3: dmi.product.family: ThinkPad E15 Gen 3 dmi.product.name: 20YG004YUE dmi.product.sku: LENOVO_MT_20YG_BU_Think_FM_ThinkPad E15 Gen 3 dmi.product.version: ThinkPad E15 Gen 3 dmi.sys.vendor: LENOVO ** Affects: cheese (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gstreamer-ok jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/2045349 Title: cheese not working properly image shattring Status in cheese package in Ubuntu: New Bug description: when i open cheese it image shattering and display the smae image it capured first it act like not ending loop ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 1 09:23:21 2023 InstallationDate: Installed on 2023-01-08 (326 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20YG004YUE RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: cheese UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2022 dmi.bios.release: 1.12 dmi.bios.vendor: LENOVO dmi.bios.version: R1OET33W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20YG004YUE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR1OET33W(1.12):bd05/07/2022:br1.12:efr1.12:svnLENOVO:pn20YG004YUE:pvrThinkPadE15Gen3:rvnLENOVO:rn20YG004YUE:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20YG_BU_Think_FM_ThinkPadE15Gen3: dmi.product.family: ThinkPad E15 Gen 3 dmi.product.name: 20YG004YUE dmi.product.sku: LENOVO_MT_20YG_BU_Think_FM_ThinkPad E15 Gen 3 dmi.product.version: ThinkPad E15 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/2045349/+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 1933027] Re: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled
By default GDM switches to smartcard mode once one is plugged in, smartcard auth can be disabled at gdm level though, by changing the gsettings. sudo -u gdm env -u XDG_RUNTIME_DIR -u DISPLAY DCONF_PROFILE=gdm dbus-run-session \ gsettings set org.gnome.login-screen enable-smartcard-authentication false -- 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/1933027 Title: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: I use my Ubuntu PC with Yubikey almost always plugged in. It provides several security token interfaces, such as U2F, GPG smartcard, proprieritary Yubico interfaces (of which I mostly use TOTP codes), and also PIV smartcard. However, I haven't configured a PIV smartcard on it. Whenever I login into the system having Yubikey plugged in, I'm prompted for login name, and then for PIN for some smartcard while also being asked to plug in one. This is very misleading on several layers: 1. I have the device providing smartcard plugged id, 2. But it's not the smartcard GDM would think it is as it's not configured properly, 3. There are no local smartcard-authenticating users right now in the system, 3. There are no remote authentication systems configured on the system (so no ActiveDirectory-smartcard logins or such). If I unplug the token UX goes back on old good track. Given the circumstances above, I'd consider that GDM (and, on my bet, any PAM configuration it uses) shouldn't offer to login using smartcard if there is no way to actually do so. I feel something is off here, so I'm reporting a bug. It could be an upstream problem though; it also could be an upstream SSSD problem, or all combined. I believe there is a more clear user experience: 1. GDM should display users that can login into the system, as it always does (if configured). It may also provide entering other login name (also if configured). This is GDM usually does without smartcards altogether. 2. When user is chosen (from the list or manually typed in), check can this user even authenticate with smartcards (i.e. if any of available smartcards is actually recognised for this user). If so, then ask for PIN. Else, don't show anything about smartcards at all (this includes when SSSD is not configured for any AD or related and this user has no local smartcard configuration). This can switch there & back based on device events. I've seen other OS doing this. Ubuntu/Gnome session doesn't ask me for PIN for a smartcard on a lock screen, so I guess it doesn't support it at all or correctly finds out it can't be used. Even more, I couldn't find a way to actually add my smartcard as a local login method. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jun 20 14:02:02 2021 InstallationDate: Installed on 2017-03-05 (1567 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to hirsute on 2021-05-13 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1933027/+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 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
** Also affects: gvfs (Ubuntu Noble) Importance: Unknown Status: New ** Also affects: tracker-miners (Ubuntu Noble) Importance: High Assignee: Denison Barbosa (justdenis) Status: Fix Released ** Changed in: tracker-miners (Ubuntu Jammy) Assignee: Denison Barbosa (justdenis) => Matthew Ruffell (mruffell) ** Changed in: gvfs (Ubuntu Mantic) Importance: Unknown => Undecided ** Changed in: gvfs (Ubuntu Mantic) Status: Confirmed => Invalid ** Changed in: gvfs (Ubuntu Noble) Importance: Unknown => Undecided ** Changed in: gvfs (Ubuntu Noble) Status: New => Invalid ** Changed in: tracker-miners (Ubuntu Lunar) Importance: High => Medium ** Changed in: tracker-miners (Ubuntu Lunar) Status: Confirmed => In Progress ** Changed in: tracker-miners (Ubuntu Lunar) Assignee: Denison Barbosa (justdenis) => Matthew Ruffell (mruffell) ** Changed in: tracker-miners (Ubuntu Mantic) Status: Fix Released => In Progress ** Changed in: tracker-miners (Ubuntu Noble) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in gvfs package in Ubuntu: Invalid Status in tracker-miners package in Ubuntu: In Progress Status in gvfs source package in Bionic: Invalid Status in tracker-miners source package in Bionic: Won't Fix Status in gvfs source package in Focal: Invalid Status in tracker-miners source package in Focal: In Progress Status in gvfs source package in Jammy: Invalid Status in tracker-miners source package in Jammy: In Progress Status in gvfs source package in Kinetic: Invalid Status in tracker-miners source package in Kinetic: Won't Fix Status in gvfs source package in Lunar: Invalid Status in tracker-miners source package in Lunar: In Progress Status in gvfs source package in Mantic: Invalid Status in tracker-miners source package in Mantic: In Progress Status in gvfs source package in Noble: Invalid Status in tracker-miners source package in Noble: In Progress Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with:
[Desktop-packages] [Bug 2045329] Re: The 'Files Selecting' window shows Asia fonts incompletely.
** Attachment added: "Screenshot from 2023-12-01 08-49-33.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2045329/+attachment/5725402/+files/Screenshot%20from%202023-12-01%2008-49-33.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2045329 Title: The 'Files Selecting' window shows Asia fonts incompletely. Status in nautilus package in Ubuntu: New Bug description: The 'Files Selecting' windows shows Asia fonts incompletely. Please view the image I uploaded of it. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3 Uname: Linux 6.5.0-13-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 1 08:51:46 2023 GsettingsChanges: InstallationDate: Installed on 2023-10-26 (35 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color SourcePackage: nautilus UpgradeStatus: Upgraded to mantic on 2023-10-26 (35 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2045329/+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 2045329] [NEW] The 'Files Selecting' window shows Asia fonts incompletely.
Public bug reported: The 'Files Selecting' windows shows Asia fonts incompletely. Please view the image I uploaded of it. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3 Uname: Linux 6.5.0-13-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 1 08:51:46 2023 GsettingsChanges: InstallationDate: Installed on 2023-10-26 (35 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color SourcePackage: nautilus UpgradeStatus: Upgraded to mantic on 2023-10-26 (35 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- 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/2045329 Title: The 'Files Selecting' window shows Asia fonts incompletely. Status in nautilus package in Ubuntu: New Bug description: The 'Files Selecting' windows shows Asia fonts incompletely. Please view the image I uploaded of it. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3 Uname: Linux 6.5.0-13-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 1 08:51:46 2023 GsettingsChanges: InstallationDate: Installed on 2023-10-26 (35 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color SourcePackage: nautilus UpgradeStatus: Upgraded to mantic on 2023-10-26 (35 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2045329/+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 1992498] Re: Disable offline update feature
Please open a new bug if you have a current issue instead of replying to a closed bug. -- 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/1992498 Title: Disable offline update feature Status in gnome-software package in Ubuntu: Fix Released Bug description: Impact -- The GNOME Software app has a feature to install updates when powering off the computer. (Screenshot attached.) This is unnecessary in Ubuntu since we already ask to restart when there are updates that we know need a restart to be applied. GNOME Software may also prevent installing updates except by restarting the computer which is frustrating to people who don't want to restart immediately. GNOME Software does not provide an option to turn this feature off. Years ago, Ubuntu's version of the GNOME Software .deb disabled this feature, but it was (unintentionally?) dropped when we resynced our packaging with Debian after switching the Ubuntu Store to be provided by a snap instead of a .deb. This issue affects Ubuntu Budgie and Xubuntu which ship the .deb version of GNOME Software. It also affects people who have uninstalled the snap and installed the .deb. This patch actually disables all apt updates. This is ok for Ubuntu because we use update-manager for apt updates and all non-KDE official desktop flavors depend on update-manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1992498/+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 1992498] Re: Disable offline update feature
"This is ok for Ubuntu" This is no OK for Ubuntu and is perceived as a regression for users (like myself and many others) that use gnome-software as a one stop shop for managing installation and updates of debs, snaps, and flatpaks. With this patch added now we have to use a separate software to update debs and this is not communicated to the users. -- 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/1992498 Title: Disable offline update feature Status in gnome-software package in Ubuntu: Fix Released Bug description: Impact -- The GNOME Software app has a feature to install updates when powering off the computer. (Screenshot attached.) This is unnecessary in Ubuntu since we already ask to restart when there are updates that we know need a restart to be applied. GNOME Software may also prevent installing updates except by restarting the computer which is frustrating to people who don't want to restart immediately. GNOME Software does not provide an option to turn this feature off. Years ago, Ubuntu's version of the GNOME Software .deb disabled this feature, but it was (unintentionally?) dropped when we resynced our packaging with Debian after switching the Ubuntu Store to be provided by a snap instead of a .deb. This issue affects Ubuntu Budgie and Xubuntu which ship the .deb version of GNOME Software. It also affects people who have uninstalled the snap and installed the .deb. This patch actually disables all apt updates. This is ok for Ubuntu because we use update-manager for apt updates and all non-KDE official desktop flavors depend on update-manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1992498/+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 2045290] Re: cracklib2 FTBFS against python 3.12
** Changed in: cracklib2 (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cracklib2 in Ubuntu. https://bugs.launchpad.net/bugs/2045290 Title: cracklib2 FTBFS against python 3.12 Status in cracklib2 package in Ubuntu: New Status in cracklib2 package in Debian: New Bug description: Build against Python 3.12 is red. The build-time test-suite uses the obsolete function unittest.TestCase.assertEquals - which was dropped from Python 3.12. ...E == ERROR: test_simple_combinations (test_cracklib.TestModuleFunctions.test_simple_combinations) -- Traceback (most recent call last): File "/<>/debian/buildtmp/python3.12/python/build/lib.linux-x86_64-cpython-312/test_cracklib.py", line 122, in test_simple_combinations self.assertEquals( ^ AttributeError: 'TestModuleFunctions' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? == ERROR: test_simple_digit (test_cracklib.TestModuleFunctions.test_simple_digit) -- Traceback (most recent call last): File "/<>/debian/buildtmp/python3.12/python/build/lib.linux-x86_64-cpython-312/test_cracklib.py", line 99, in test_simple_digit self.assertEquals( ^ AttributeError: 'TestModuleFunctions' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? == ERROR: test_simple_lower (test_cracklib.TestModuleFunctions.test_simple_lower) -- Traceback (most recent call last): File "/<>/debian/buildtmp/python3.12/python/build/lib.linux-x86_64-cpython-312/test_cracklib.py", line 79, in test_simple_lower self.assertEquals( ^ AttributeError: 'TestModuleFunctions' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? == ERROR: test_simple_other (test_cracklib.TestModuleFunctions.test_simple_other) -- Traceback (most recent call last): File "/<>/debian/buildtmp/python3.12/python/build/lib.linux-x86_64-cpython-312/test_cracklib.py", line 109, in test_simple_other self.assertEquals( ^ AttributeError: 'TestModuleFunctions' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? == ERROR: test_simple_upper (test_cracklib.TestModuleFunctions.test_simple_upper) -- Traceback (most recent call last): File "/<>/debian/buildtmp/python3.12/python/build/lib.linux-x86_64-cpython-312/test_cracklib.py", line 89, in test_simple_upper self.assertEquals( ^ AttributeError: 'TestModuleFunctions' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/2045290/+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 2045290] Re: cracklib2 FTBFS against python 3.12
Adding debdiff. The package is uploaded to the following PPA: https://launchpad.net/~ogayot/+archive/ubuntu/noble-proposed/ ** Changed in: cracklib2 (Ubuntu) Importance: Undecided => High ** Patch added: "1-2.9.6-5build2__2.9.6-5ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/2045290/+attachment/5725326/+files/1-2.9.6-5build2__2.9.6-5ubuntu1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cracklib2 in Ubuntu. https://bugs.launchpad.net/bugs/2045290 Title: cracklib2 FTBFS against python 3.12 Status in cracklib2 package in Ubuntu: New Status in cracklib2 package in Debian: Unknown Bug description: Build against Python 3.12 is red. The build-time test-suite uses the obsolete function unittest.TestCase.assertEquals - which was dropped from Python 3.12. ...E == ERROR: test_simple_combinations (test_cracklib.TestModuleFunctions.test_simple_combinations) -- Traceback (most recent call last): File "/<>/debian/buildtmp/python3.12/python/build/lib.linux-x86_64-cpython-312/test_cracklib.py", line 122, in test_simple_combinations self.assertEquals( ^ AttributeError: 'TestModuleFunctions' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? == ERROR: test_simple_digit (test_cracklib.TestModuleFunctions.test_simple_digit) -- Traceback (most recent call last): File "/<>/debian/buildtmp/python3.12/python/build/lib.linux-x86_64-cpython-312/test_cracklib.py", line 99, in test_simple_digit self.assertEquals( ^ AttributeError: 'TestModuleFunctions' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? == ERROR: test_simple_lower (test_cracklib.TestModuleFunctions.test_simple_lower) -- Traceback (most recent call last): File "/<>/debian/buildtmp/python3.12/python/build/lib.linux-x86_64-cpython-312/test_cracklib.py", line 79, in test_simple_lower self.assertEquals( ^ AttributeError: 'TestModuleFunctions' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? == ERROR: test_simple_other (test_cracklib.TestModuleFunctions.test_simple_other) -- Traceback (most recent call last): File "/<>/debian/buildtmp/python3.12/python/build/lib.linux-x86_64-cpython-312/test_cracklib.py", line 109, in test_simple_other self.assertEquals( ^ AttributeError: 'TestModuleFunctions' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? == ERROR: test_simple_upper (test_cracklib.TestModuleFunctions.test_simple_upper) -- Traceback (most recent call last): File "/<>/debian/buildtmp/python3.12/python/build/lib.linux-x86_64-cpython-312/test_cracklib.py", line 89, in test_simple_upper self.assertEquals( ^ AttributeError: 'TestModuleFunctions' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/2045290/+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 2045290] [NEW] cracklib2 FTBFS against python 3.12
Public bug reported: Build against Python 3.12 is red. The build-time test-suite uses the obsolete function unittest.TestCase.assertEquals - which was dropped from Python 3.12. ...E == ERROR: test_simple_combinations (test_cracklib.TestModuleFunctions.test_simple_combinations) -- Traceback (most recent call last): File "/<>/debian/buildtmp/python3.12/python/build/lib.linux-x86_64-cpython-312/test_cracklib.py", line 122, in test_simple_combinations self.assertEquals( ^ AttributeError: 'TestModuleFunctions' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? == ERROR: test_simple_digit (test_cracklib.TestModuleFunctions.test_simple_digit) -- Traceback (most recent call last): File "/<>/debian/buildtmp/python3.12/python/build/lib.linux-x86_64-cpython-312/test_cracklib.py", line 99, in test_simple_digit self.assertEquals( ^ AttributeError: 'TestModuleFunctions' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? == ERROR: test_simple_lower (test_cracklib.TestModuleFunctions.test_simple_lower) -- Traceback (most recent call last): File "/<>/debian/buildtmp/python3.12/python/build/lib.linux-x86_64-cpython-312/test_cracklib.py", line 79, in test_simple_lower self.assertEquals( ^ AttributeError: 'TestModuleFunctions' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? == ERROR: test_simple_other (test_cracklib.TestModuleFunctions.test_simple_other) -- Traceback (most recent call last): File "/<>/debian/buildtmp/python3.12/python/build/lib.linux-x86_64-cpython-312/test_cracklib.py", line 109, in test_simple_other self.assertEquals( ^ AttributeError: 'TestModuleFunctions' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? == ERROR: test_simple_upper (test_cracklib.TestModuleFunctions.test_simple_upper) -- Traceback (most recent call last): File "/<>/debian/buildtmp/python3.12/python/build/lib.linux-x86_64-cpython-312/test_cracklib.py", line 89, in test_simple_upper self.assertEquals( ^ AttributeError: 'TestModuleFunctions' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? ** Affects: cracklib2 (Ubuntu) Importance: Undecided Status: New ** Affects: cracklib2 (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #1055571 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055571 ** Also affects: cracklib2 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055571 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cracklib2 in Ubuntu. https://bugs.launchpad.net/bugs/2045290 Title: cracklib2 FTBFS against python 3.12 Status in cracklib2 package in Ubuntu: New Status in cracklib2 package in Debian: Unknown Bug description: Build against Python 3.12 is red. The build-time test-suite uses the obsolete function unittest.TestCase.assertEquals - which was dropped from Python 3.12. ...E == ERROR: test_simple_combinations (test_cracklib.TestModuleFunctions.test_simple_combinations) -- Traceback (most recent call last): File "/<>/debian/buildtmp/python3.12/python/build/lib.linux-x86_64-cpython-312/test_cracklib.py", line 122, in test_simple_combinations self.assertEquals( ^ AttributeError: 'TestModuleFunctions' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? == ERROR: test_simple_digit (test_cracklib.TestModuleFunctions.test_simple_digit) -- Traceback (most recent call last): File "/<>/debian/buildtmp/python3.12/python/build/lib.linux-x86_64-cpython-312/test_cracklib.py", line 99, in test_simple_digit self.assertEquals( ^ AttributeError: 'TestModuleFunctions' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?
[Desktop-packages] [Bug 2041831] Re: /usr/bin/update-manager:11:g_type_check_instance_is_fundamentally_a:g_object_ref:gdk_event_copy:pygi_boxed_copy_in_place:arg_boxed_to_py_cleanup
I believe this seems like a pygobject issue for desktop to investigate, probably a type declared wrong somewhere? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/2041831 Title: /usr/bin/update- manager:11:g_type_check_instance_is_fundamentally_a:g_object_ref:gdk_event_copy:pygi_boxed_copy_in_place:arg_boxed_to_py_cleanup Status in pygobject package in Ubuntu: New Status in update-manager package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:23.10.1, the problem page at https://errors.ubuntu.com/problem/dff72cd5c27c916b2d887a56311ba08ef15b0dff contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/2041831/+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 1799675] Re: /usr/bin/gnome-control-center:ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid)
** Changed in: gnome-control-center Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1799675 Title: /usr/bin/gnome-control-center:ERROR:../shell/cc-shell- model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid) Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-control-center package in Fedora: Unknown Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.30.1-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/8de5ebcde9e4492a3bc570a4caa376cefbdfcbec contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1799675/+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 1827154] Re: [wacom] gnome-control-center crashed with SIGSEGV in _gdk_event_queue_handle_motion_compression()
** Changed in: gnome-control-center Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827154 Title: [wacom] gnome-control-center crashed with SIGSEGV in _gdk_event_queue_handle_motion_compression() Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: Triaged Bug description: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503 --- [Impact] When I try to set the pen on my touch screen. gnome-control-center crashes. [Fix] That you can configure the pencil to later occupy it with my touch screen. [Test Case] 1. Open gnome-control-center 2. Click on Wacom tablet 3. Press the buttons of the pencil, touching the screen 4. gnome-control-center crashes ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.32.1-1ubuntu5 Uname: Linux 5.1.0-050100rc7-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 19:28:42 2019 InstallationDate: Installed on 2018-12-02 (149 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2018-12-02 (149 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1827154/+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 1973226] Re: UI doesn't allow setting Left Ctrl as Compose
** Changed in: gnome-control-center
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1973226
Title:
UI doesn't allow setting Left Ctrl as Compose
Status in gnome-control-center:
Fix Released
Status in gnome-control-center package in Ubuntu:
Confirmed
Bug description:
In Ubuntu 20.04, I was able to set Left Ctrl as my Compose key using
gnome-tweaks. I just upgraded to 22.04, where the Compose key settings
have been removed from gnome-tweaks and moved into control-center, but
Left Ctrl is not in the list of options for Compose.
I was able to restore Left Ctrl as my Compose key using:
$ gsettings set org.gnome.desktop.input-sources xkb-options ...
adding 'compose:lctrl' to that list, but it would be nice to expose it
in the GUI.
For context, my modifier settings are:
* Caps Lock is Ctrl ('ctrl:nocaps')
* Left Ctrl is Compose ('compose:lctrl')
* Both Shift keys enable/disable Caps Lock ('shift:both_capslock')
which gives me both a Ctrl key on both sides of the keyboard and an
easily-accessible Compose key.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1973226/+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 2045259] [NEW] package libgpod-common 0.8.3-18 failed to install/upgrade: problemas de dependência - deixando desconfigurado
Public bug reported: Apenas trava e fecha um programa ProblemType: Package DistroRelease: Ubuntu 23.10 Package: libgpod-common 0.8.3-18 ProcVersionSignature: Ubuntu 6.2.0-37.38-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 AptOrdering: libraw20:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Nov 30 08:42:17 2023 ErrorMessage: problemas de dependência - deixando desconfigurado InstallationDate: Installed on 2023-04-19 (225 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: libgpod Title: package libgpod-common 0.8.3-18 failed to install/upgrade: problemas de dependência - deixando desconfigurado UpgradeStatus: Upgraded to mantic on 2023-11-28 (2 days ago) ** Affects: libgpod (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgpod in Ubuntu. https://bugs.launchpad.net/bugs/2045259 Title: package libgpod-common 0.8.3-18 failed to install/upgrade: problemas de dependência - deixando desconfigurado Status in libgpod package in Ubuntu: New Bug description: Apenas trava e fecha um programa ProblemType: Package DistroRelease: Ubuntu 23.10 Package: libgpod-common 0.8.3-18 ProcVersionSignature: Ubuntu 6.2.0-37.38-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 AptOrdering: libraw20:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Nov 30 08:42:17 2023 ErrorMessage: problemas de dependência - deixando desconfigurado InstallationDate: Installed on 2023-04-19 (225 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: libgpod Title: package libgpod-common 0.8.3-18 failed to install/upgrade: problemas de dependência - deixando desconfigurado UpgradeStatus: Upgraded to mantic on 2023-11-28 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgpod/+bug/2045259/+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 2042796] Re: Ubuntu 20.04 The edge of the touchscreen is not sensitive
** Changed in: mutter Status: Unknown => New -- 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/2042796 Title: Ubuntu 20.04 The edge of the touchscreen is not sensitive Status in Mutter: New Status in OEM Priority Project: Triaged Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in gnome-shell source package in Focal: New Status in gnome-shell-extension-ubuntu-dock source package in Focal: In Progress Bug description: On Dell OptiPlex 7400 AIO, go to gnome-control-center > appearance, adjust the dock icon-size to 24. It is hard to launch corner app like firefox, or trigger the launcher. The app icon gets focus but not clicked. 1. Ubuntu version 20.04.6 2. gnome-shell 3.36.9-0ubuntu0.20.04.2 3. The app or launcher is launched after a click 4. Only see focus but no app launched To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2042796/+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 2042796] Re: Ubuntu 20.04 The edge of the touchscreen is not sensitive
Reported upstream what seems to be the issue: https://gitlab.gnome.org/GNOME/mutter/-/issues/3183 But I might be wrong and there might be multiple issues. ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3183 https://gitlab.gnome.org/GNOME/mutter/-/issues/3183 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/3183 Importance: Unknown Status: Unknown ** No longer affects: gnome-shell (Ubuntu Jammy) ** No longer affects: gnome-shell (Ubuntu Mantic) ** No longer affects: gnome-shell (Ubuntu Noble) ** No longer affects: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) ** No longer affects: gnome-shell-extension-ubuntu-dock (Ubuntu Mantic) ** No longer affects: gnome-shell-extension-ubuntu-dock (Ubuntu Noble) -- 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/2042796 Title: Ubuntu 20.04 The edge of the touchscreen is not sensitive Status in Mutter: Unknown Status in OEM Priority Project: Triaged Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in gnome-shell source package in Focal: New Status in gnome-shell-extension-ubuntu-dock source package in Focal: In Progress Bug description: On Dell OptiPlex 7400 AIO, go to gnome-control-center > appearance, adjust the dock icon-size to 24. It is hard to launch corner app like firefox, or trigger the launcher. The app icon gets focus but not clicked. 1. Ubuntu version 20.04.6 2. gnome-shell 3.36.9-0ubuntu0.20.04.2 3. The app or launcher is launched after a click 4. Only see focus but no app launched To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2042796/+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 2045245] Re: ubuntu22.04 ibus Chinese pinying input not response
Thanks for your report. It's hard to comment on without more info. Possibly there is a need to clean the cache in ~/.cache/ibus/libpinyin . ** Changed in: ibus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2045245 Title: ubuntu22.04 ibus Chinese pinying input not response Status in ibus package in Ubuntu: Incomplete Bug description: I have used 22.04 many times, and I encountered this problem every time. During the first period of installing the system, everything was fine, but once I used the system for more than a few months, the ibus started to stop responding and I could not enter. There is no response when pressing any keys on the keyboard. The only solution is to manually click the input method icon in the upper right corner, switch to English, and then enter `ibus restart`. But this problem of input method not responding is too frequent and occurs every few minutes. I can't stand this torture anymore, and I now use a third-party input method. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2045245/+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 2039433] Re: Please sync duplicity 1.2.2-2 from Debian
This bug was fixed in the package duplicity - 1.2.2-2 Sponsored for Nathan Teodosio (nteodosio) --- duplicity (1.2.2-2) unstable; urgency=medium * minor build adjustments (closes: #1052878) -- Alexander Zangerl Mon, 02 Oct 2023 10:39:40 +0200 ** Changed in: duplicity (Ubuntu) Assignee: (unassigned) => Graham Inggs (ginggs) ** Changed in: duplicity (Ubuntu) Status: New => In Progress ** Changed in: duplicity (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/2039433 Title: Please sync duplicity 1.2.2-2 from Debian Status in duplicity package in Ubuntu: Fix Released Bug description: Duplicity 1.2.2-1 did not build from source due to new setuptools, thus 1.2.2-1ubuntu1 was uploaded. 1.2.2-2 no longer has that problem and closes the corresponding bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052878, so we can synchronize with Debian now. I attach the build log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/2039433/+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 2031096] Re: udisks2 daemon fails to start
Might be related to https://github.com/storaged-project/udisks/issues/1198 Issues with nvme affecting udisks 2.10.1 ** Bug watch added: github.com/storaged-project/udisks/issues #1198 https://github.com/storaged-project/udisks/issues/1198 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/2031096 Title: udisks2 daemon fails to start Status in udisks: New Status in udisks2 package in Ubuntu: Fix Released Bug description: udisks2 2.10.0 fails to start in Ubuntu Mantic (23.10) Error status is: Aug 11 10:36:37 nodename systemd[1]: Starting udisks2.service - Disk Manager... Aug 11 10:36:37 nodename udisksd[232247]: udisks daemon version 2.10.0 starting Aug 11 10:36:38 nodename udisksd[232247]: Error getting 'loop28' information: Failed to open device loop28: No such file o> Aug 11 10:36:38 nodename udisksd[232247]: Error getting 'loop28' information: Failed to open device loop28: No such file o> Aug 11 10:36:38 nodename udisksd[232247]: *** stack smashing detected ***: terminated Aug 11 10:36:38 nodename systemd[1]: udisks2.service: Main process exited, code=dumped, status=6/ABRT Aug 11 10:36:38 nodename systemd[1]: udisks2.service: Failed with result 'core-dump'. Aug 11 10:36:38 nodename systemd[1]: Failed to start udisks2.service - Disk Manager. This bug seems to refer: https://github.com/storaged- project/udisks/issues/1139 To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/2031096/+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 2042796] Re: Ubuntu 20.04 The edge of the touchscreen is not sensitive
Fix Released → Invalid for newer releases, to clarify that we haven't yet found evidence for a fix that was released and can be backported. Just that the bug doesn't happen in newer releases. ** Changed in: gnome-shell (Ubuntu Jammy) Status: Fix Released => Invalid ** Changed in: gnome-shell (Ubuntu Mantic) Status: Fix Released => Invalid ** Changed in: gnome-shell (Ubuntu Noble) Status: Fix Released => Invalid ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Status: Fix Released => Invalid ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Mantic) Status: Fix Released => Invalid ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Noble) Status: Fix Released => Invalid -- 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/2042796 Title: Ubuntu 20.04 The edge of the touchscreen is not sensitive Status in OEM Priority Project: Triaged Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in gnome-shell source package in Focal: New Status in gnome-shell-extension-ubuntu-dock source package in Focal: In Progress Status in gnome-shell source package in Jammy: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Invalid Status in gnome-shell source package in Mantic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Invalid Status in gnome-shell source package in Noble: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Noble: Invalid Bug description: On Dell OptiPlex 7400 AIO, go to gnome-control-center > appearance, adjust the dock icon-size to 24. It is hard to launch corner app like firefox, or trigger the launcher. The app icon gets focus but not clicked. 1. Ubuntu version 20.04.6 2. gnome-shell 3.36.9-0ubuntu0.20.04.2 3. The app or launcher is launched after a click 4. Only see focus but no app launched To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042796/+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 2043119] Re: screen color calibration : no start button
** Description changed: I try to calibrate my screen using the utility of gnome-control-center, color section. I have a Spyder3 Express probe connected by USB and the Calibrate… button become active. So I click this button and the process begin with a dialog box giving several informations until it ask for the name of the further colour profile. After that, a small window appears asking to put the probe on this window and to press "Start"… but there is no Start button. I tried the same on Ubuntu 22.04 (on a VM) : the same window occupied all the screen and we can see a Start button at the bottom right and a - Cancel one on the button left. + Cancel one on the bottom left. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 9 15:58:51 2023 InstallationDate: Installed on 2020-04-10 (1308 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-10-13 (27 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2043119 Title: screen color calibration : no start button Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I try to calibrate my screen using the utility of gnome-control-center, color section. I have a Spyder3 Express probe connected by USB and the Calibrate… button become active. So I click this button and the process begin with a dialog box giving several informations until it ask for the name of the further colour profile. After that, a small window appears asking to put the probe on this window and to press "Start"… but there is no Start button. I tried the same on Ubuntu 22.04 (on a VM) : the same window occupied all the screen and we can see a Start button at the bottom right and a Cancel one on the bottom left. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 9 15:58:51 2023 InstallationDate: Installed on 2020-04-10 (1308 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-10-13 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2043119/+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 2042796] Re: Ubuntu 20.04 The edge of the touchscreen is not sensitive
My current theory is that when icons are sufficiently small or close to the edge of the screen, it's too easy for the touch "gesture" to start outside of the icon area (e.g. finger touching the display bezel). The pressure then increases and the touch moves into the icon area. But that's much the same as dragging your finger onto an icon. Try it in the app grid and you'll get the same behaviour (icon thinks you're hovering, not clicking). Such touches may work more often in later Ubuntu releases just by virtue of the actor/theme padding in ubuntu-dock. But I can reproduce the same issue even in newer Ubuntu releases by sliding a finger onto an icon. So I think that's probably the issue -- not really a bug but it feels like a bug if you don't know the touch started outside the icon's sensitive area. Short term I just suggest good UI design - if it's a touch UI then make sure the icons and buttons are big. Longer term we'll see what we can do about making 20.04 more reliable, but we're busy supporting a lot of different releases. ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Focal) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu Jammy) Status: New => Fix Released ** Changed in: gnome-shell (Ubuntu Mantic) Status: New => Fix Released ** Changed in: gnome-shell (Ubuntu Noble) Status: New => 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/2042796 Title: Ubuntu 20.04 The edge of the touchscreen is not sensitive Status in OEM Priority Project: Triaged Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: New Status in gnome-shell-extension-ubuntu-dock source package in Focal: In Progress Status in gnome-shell source package in Jammy: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Released Status in gnome-shell source package in Mantic: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Released Status in gnome-shell source package in Noble: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Noble: Fix Released Bug description: On Dell OptiPlex 7400 AIO, go to gnome-control-center > appearance, adjust the dock icon-size to 24. It is hard to launch corner app like firefox, or trigger the launcher. The app icon gets focus but not clicked. 1. Ubuntu version 20.04.6 2. gnome-shell 3.36.9-0ubuntu0.20.04.2 3. The app or launcher is launched after a click 4. Only see focus but no app launched To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042796/+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 2027904] Re: LibreOffice Snap extremely slow to launch.
Same problem here across all LibreOffice apps. Snap version several seconds slower to start and is slower when handling large files. -- 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/2027904 Title: LibreOffice Snap extremely slow to launch. Status in libreoffice package in Ubuntu: Confirmed Bug description: It takes around 3 to 4 seconds to launch even post start-up launching. Other snaps are snappy ! No logs indicate any errors or warnings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2027904/+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 2041664] Re: Webkit 2.42 and nvidia(?) drivers
*** This bug is a duplicate of bug 2023322 *** https://bugs.launchpad.net/bugs/2023322 Although this might also be https://bugs.webkit.org/show_bug.cgi?id=261874 ** Bug watch added: bugs.webkit.org/ #261874 https://bugs.webkit.org/show_bug.cgi?id=261874 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2041664 Title: Webkit 2.42 and nvidia(?) drivers Status in webkit2gtk package in Ubuntu: Incomplete Bug description: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy My machine recently installed updates to webkit and since doing that some packages using webkit are not rendering the display correctly. For example, running /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/MiniBrowser results in the output on the shell of KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied Failed to create GBM buffer of size 2048x1464: Permission denied KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied Failed to create GBM buffer of size 2048x1464: Permission denied KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied Failed to create GBM buffer of size 2048x1464: Permission denied Failed to create EGL images for DMABufs with file descriptors -1, -1 and -1 And a display with just a blank window (attachment image-1.png). There is a work-around, which is to force of the DMABUF, by running WEBKIT_DISABLE_DMABUF_RENDERER=1 /usr/lib/x86_64-linux- gnu/webkit2gtk-4.0/MiniBrowser which results in the correct display output (attachment image-2.png). Some searching on the web suggests this is related to a bad interaction with the Nvida graphics driver. See eg: https://aur.archlinux.org/cgit/aur.git/tree/GTK-Disable-DMABuf- renderer-for-NVIDIA-proprietary-drivers.patch?h=webkit2gtk-imgpaste To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2041664/+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 2023322] Re: GTK internal browser does not render with Nvidia drivers
Apparently you need to have libnvidia-egl-gbm1 for the fix to work? I'm not so sure about that because I verified the fix on 23.10 and it looks like libnvidia-egl-gbm1 wasn't installed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: GTK internal browser does not render with Nvidia drivers Status in Webkit: Confirmed Status in gnome-control-center package in Ubuntu: Invalid Status in gnome-online-accounts package in Ubuntu: Invalid Status in webkit2gtk package in Ubuntu: Fix Released Status in yelp package in Ubuntu: Invalid Status in webkit2gtk package in Debian: Fix Released Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. Jun 08 11:17:42 CCW-HAL systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully. Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR
[Desktop-packages] [Bug 2045245] [NEW] ubuntu22.04 ibus Chinese pinying input not response
Public bug reported: I have used 22.04 many times, and I encountered this problem every time. During the first period of installing the system, everything was fine, but once I used the system for more than a few months, the ibus started to stop responding and I could not enter. There is no response when pressing any keys on the keyboard. The only solution is to manually click the input method icon in the upper right corner, switch to English, and then enter `ibus restart`. But this problem of input method not responding is too frequent and occurs every few minutes. I can't stand this torture anymore, and I now use a third-party input method. ** Affects: ibus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2045245 Title: ubuntu22.04 ibus Chinese pinying input not response Status in ibus package in Ubuntu: New Bug description: I have used 22.04 many times, and I encountered this problem every time. During the first period of installing the system, everything was fine, but once I used the system for more than a few months, the ibus started to stop responding and I could not enter. There is no response when pressing any keys on the keyboard. The only solution is to manually click the input method icon in the upper right corner, switch to English, and then enter `ibus restart`. But this problem of input method not responding is too frequent and occurs every few minutes. I can't stand this torture anymore, and I now use a third-party input method. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2045245/+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 2041664] Re: Webkit 2.42 and nvidia(?) drivers
*** This bug is a duplicate of bug 2023322 *** https://bugs.launchpad.net/bugs/2023322 What is the version of webkit2gtk? ** Changed in: webkit2gtk (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2041664 Title: Webkit 2.42 and nvidia(?) drivers Status in webkit2gtk package in Ubuntu: Incomplete Bug description: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy My machine recently installed updates to webkit and since doing that some packages using webkit are not rendering the display correctly. For example, running /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/MiniBrowser results in the output on the shell of KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied Failed to create GBM buffer of size 2048x1464: Permission denied KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied Failed to create GBM buffer of size 2048x1464: Permission denied KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied Failed to create GBM buffer of size 2048x1464: Permission denied Failed to create EGL images for DMABufs with file descriptors -1, -1 and -1 And a display with just a blank window (attachment image-1.png). There is a work-around, which is to force of the DMABUF, by running WEBKIT_DISABLE_DMABUF_RENDERER=1 /usr/lib/x86_64-linux- gnu/webkit2gtk-4.0/MiniBrowser which results in the correct display output (attachment image-2.png). Some searching on the web suggests this is related to a bad interaction with the Nvida graphics driver. See eg: https://aur.archlinux.org/cgit/aur.git/tree/GTK-Disable-DMABuf- renderer-for-NVIDIA-proprietary-drivers.patch?h=webkit2gtk-imgpaste To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2041664/+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 2041664] Re: Webkit 2.42 and nvidia(?) drivers
*** This bug is a duplicate of bug 2023322 *** https://bugs.launchpad.net/bugs/2023322 Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2041664 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2041664 Title: Webkit 2.42 and nvidia(?) drivers Status in webkit2gtk package in Ubuntu: Incomplete Bug description: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy My machine recently installed updates to webkit and since doing that some packages using webkit are not rendering the display correctly. For example, running /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/MiniBrowser results in the output on the shell of KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied Failed to create GBM buffer of size 2048x1464: Permission denied KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied Failed to create GBM buffer of size 2048x1464: Permission denied KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied Failed to create GBM buffer of size 2048x1464: Permission denied Failed to create EGL images for DMABufs with file descriptors -1, -1 and -1 And a display with just a blank window (attachment image-1.png). There is a work-around, which is to force of the DMABUF, by running WEBKIT_DISABLE_DMABUF_RENDERER=1 /usr/lib/x86_64-linux- gnu/webkit2gtk-4.0/MiniBrowser which results in the correct display output (attachment image-2.png). Some searching on the web suggests this is related to a bad interaction with the Nvida graphics driver. See eg: https://aur.archlinux.org/cgit/aur.git/tree/GTK-Disable-DMABuf- renderer-for-NVIDIA-proprietary-drivers.patch?h=webkit2gtk-imgpaste To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2041664/+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 2021956] Re: crash cups-proxyd
I'm getting this error on 23.10: cups-proxyd[2415]: segfault at 18 ip 55efd95e6d75 sp 7ffc3ee0d810 error 4 in cups-proxyd[55efd95e3000+7000] likely on CPU 1 (core 1, socket 0) ** Changed in: cups (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2021956 Title: crash cups-proxyd Status in cups package in Ubuntu: New Bug description: Ubuntu IOT Desktop 22.04 LTS # cat /etc/os-release PRETTY_NAME="Ubuntu 22.04.2 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.2 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy Kernel Version: 5.15.0-1028-intel-iotg # journalctl --no-hostname -b --no-pager | grep cups-proxyd mai 31 11:51:22 cups.cupsd[949]: + PROXY_DAEMON=cups-proxyd mai 31 11:51:22 cups.cupsd[3032]: exec cups-proxyd /var/snap/cups/common/run/cups.sock /run/cups/cups.sock -l --logdir /var/snap/cups/872/var/log mai 31 11:51:23 audit[3032]: SECCOMP auid=4294967295 uid=0 gid=0 ses=4294967295 subj=snap.cups.cupsd pid=3032 comm="cups-proxyd" exe="/snap/cups/872/sbin/cups-proxyd" sig=0 arch=c03e syscall=314 compat=0 ip=0x7fb050c2973d code=0x5 mai 31 11:51:23 kernel: audit: type=1326 audit(1685523083.773:85): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=snap.cups.cupsd pid=3032 comm="cups-proxyd" exe="/snap/cups/872/sbin/cups-proxyd" sig=0 arch=c03e syscall=314 compat=0 ip=0x7fb050c2973d code=0x5 mai 31 11:51:24 kernel: cups-proxyd[3032]: segfault at 18 ip 558e95990d6e sp 7ffe2436a230 error 4 in cups-proxyd[558e9598d000+7000] Error: cups-proxyd[3032]: segfault at 18 ip 558e95990d6e sp 7ffe2436a230 error 4 in cups-proxyd[558e9598d000+7000] Snap list: # snap list Name Version RevTracking Publisher Notes bare 1.0 5 latest/stable canonical✓ base chromium 113.0.5672.1262477 latest/stable canonical✓ - core20 20230503 1891 latest/stable canonical✓ base core22 20230503 634latest/stable canonical✓ base cups 2.4.2-5 872latest/stable openprinting✓ - firefox111.0-2 2432 latest/stable/… mozilla✓ - gnome-3-38-20040+git.6f39565 140latest/stable/… canonical✓ - gnome-42-2204 0+git.587e965 102latest/stable canonical✓ - gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - snap-store 41.3-71-g709398e 959latest/stable/… canonical✓ - snapd 2.59.219122 latest/stable canonical✓ snapd snapd-desktop-integration 0.9 83 latest/stable/… canonical✓ - Reproduced: At every boot OS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2021956/+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 2041664] Re: Webkit 2.42 and nvidia(?) drivers
*** This bug is a duplicate of bug 2023322 *** https://bugs.launchpad.net/bugs/2023322 Nevermind. Let's keep the conversation in bug 2023322. ** This bug has been marked a duplicate of bug 2023322 GTK internal browser does not render with Nvidia drivers -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2041664 Title: Webkit 2.42 and nvidia(?) drivers Status in webkit2gtk package in Ubuntu: Incomplete Bug description: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy My machine recently installed updates to webkit and since doing that some packages using webkit are not rendering the display correctly. For example, running /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/MiniBrowser results in the output on the shell of KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied Failed to create GBM buffer of size 2048x1464: Permission denied KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied Failed to create GBM buffer of size 2048x1464: Permission denied KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied Failed to create GBM buffer of size 2048x1464: Permission denied Failed to create EGL images for DMABufs with file descriptors -1, -1 and -1 And a display with just a blank window (attachment image-1.png). There is a work-around, which is to force of the DMABUF, by running WEBKIT_DISABLE_DMABUF_RENDERER=1 /usr/lib/x86_64-linux- gnu/webkit2gtk-4.0/MiniBrowser which results in the correct display output (attachment image-2.png). Some searching on the web suggests this is related to a bad interaction with the Nvida graphics driver. See eg: https://aur.archlinux.org/cgit/aur.git/tree/GTK-Disable-DMABuf- renderer-for-NVIDIA-proprietary-drivers.patch?h=webkit2gtk-imgpaste To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2041664/+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 2041664] Re: Webkit 2.42 and nvidia(?) drivers
*** This bug is a duplicate of bug 2023322 *** https://bugs.launchpad.net/bugs/2023322 Sounds related to bug 2023322 and/or bug 1967488. ** Tags added: jammy nvidia nvidia-wayland wayland -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2041664 Title: Webkit 2.42 and nvidia(?) drivers Status in webkit2gtk package in Ubuntu: Incomplete Bug description: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy My machine recently installed updates to webkit and since doing that some packages using webkit are not rendering the display correctly. For example, running /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/MiniBrowser results in the output on the shell of KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied Failed to create GBM buffer of size 2048x1464: Permission denied KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied Failed to create GBM buffer of size 2048x1464: Permission denied KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied Failed to create GBM buffer of size 2048x1464: Permission denied Failed to create EGL images for DMABufs with file descriptors -1, -1 and -1 And a display with just a blank window (attachment image-1.png). There is a work-around, which is to force of the DMABUF, by running WEBKIT_DISABLE_DMABUF_RENDERER=1 /usr/lib/x86_64-linux- gnu/webkit2gtk-4.0/MiniBrowser which results in the correct display output (attachment image-2.png). Some searching on the web suggests this is related to a bad interaction with the Nvida graphics driver. See eg: https://aur.archlinux.org/cgit/aur.git/tree/GTK-Disable-DMABuf- renderer-for-NVIDIA-proprietary-drivers.patch?h=webkit2gtk-imgpaste To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2041664/+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 2042796] Re: Ubuntu 20.04 The edge of the touchscreen is not sensitive
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Focal) Importance: Undecided => Low -- 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/2042796 Title: Ubuntu 20.04 The edge of the touchscreen is not sensitive Status in OEM Priority Project: Triaged Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Focal: In Progress Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Noble: Fix Released Bug description: On Dell OptiPlex 7400 AIO, go to gnome-control-center > appearance, adjust the dock icon-size to 24. It is hard to launch corner app like firefox, or trigger the launcher. The app icon gets focus but not clicked. 1. Ubuntu version 20.04.6 2. gnome-shell 3.36.9-0ubuntu0.20.04.2 3. The app or launcher is launched after a click 4. Only see focus but no app launched To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042796/+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
