[Desktop-packages] [Bug 1936907] Re: [MIR] ADSys
Thanks Seth for the review and the overall positive comments! :) Some answers: 1. the potential race is fixed after our discussion and pending some reviews 2. the pam modulefixes are done and merged already (even if upstream don’t deallocate, let’s do it on our side) 3. on the conditions that can be added to adsys-boot.service to make it less likely to spam the journal every five seconds for ten hours when on an airplane? -> We can’t rely on network being up (maybe we never had the network, or the interface is on but not connected yet, or the interface is on, has no Internet, but local network is enough to reach AD). Depending on all those conditions, we can’t link it to the network, it may be too early or too late. Also, we support offline mode once we have a valid cache. Considering that this case only happen the first time you boot your machine (no local cache for offline usage) and don’t have access to AD, this doesn’t seem a big issue and rather something you want to be alerted on, what do you think? 4. on the doc and examples containing a socket in /tmp -> This is more a debug example to run adsysd as non root. The issue with putting real values is then, if you do that on a system where adsysd is running, you end up erroring out on the systemd existing socket and then, it’s a nightmare to recover on the systemd side (you need to reset the state of the .socket unit). This is why the example carefully avoid using the real system socket (in addition to require root to read it). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1936907 Title: [MIR] ADSys Status in adsys package in Ubuntu: In Progress Bug description: [Availability] Available on all archs, available starting hirsute. It will be backported to Focal once an FFe has been accepted. [Rationale] We are supporting GPO Active Directory support on ubuntu starting hirsute. This features allows for an administrator to configure their Active Directory server to deploy per-machine and per-user configurations, enforce rules and other domain policies. Right now, dconf keys, sudo administration rights and computer and user scripts are supported. This feature is built and use the krb5 tickets which are provided by SSSD. Basically: - SSSD is dealing with user and machine registration/authentification and enforce password policies - ADSys is handling GPO enforcement and support. The Ubuntu specific policies needs to be installed on the Active Directory server (they are contained in the daemon). [Security] The daemon is started is running as a root user to be able to enforce machine policies, like rebuilding dconf databases, setting profiles. User only interacts with the client side (both sides communicates over GRPC), which can be ran as any user. Polkit is used to restrain access to some part of the API. There is a PAM module to build on demand per-user policy once authenticated with SSSD. They are rejected if the authentication or not all affected policies could be downloaded. [Quality assurance] Joining a domain in the ubiquity desktop installer makes the machine joining the AD domain and install adsys functionality. The package will be seeded directly on the desktop ISO. An extensive testsuite (more than 1k) is included and available as autopkgtests for rdepends. The whole stack is tested (even the client/daemon interaction) and coverage is measured (including in the small python script). However, tests with a real Active Directory server can only be done manually as there is no setup available in the autopkgtests infrastructure. [Dependencies] Main dependencies are libsmbclient, python3 (an embeeded script allows, via samba, connecting to AD LDAP) and SSSD/KRB5. This is a Go package, and all dependencies are vendored, and versions are controlled via go.mod. We are using dependabot (from Github) to automatically get notified of any dependencies updates (and security issues), which opens a PR, rebuild and run all tests to report it there. We are thus able to quickly merge them. [Standards compliance] Standard debhelper packaging, including a systemd service. [Maintenance] The desktop team will maintain it. * we commit to test no-change-rebuilds triggered by a dependent library/compiler and to fix any issues found for the lifetime of the release (including ESM when included) * we will provide timely testing of no-change-rebuilds from the security team, fixing the rebuilt package as necessary * we commit to provide updates to the security team for any affected vendored code for the lifetime of the release (including ESM when included) * we will provide timely, high quality updates for the security team to sponsor to fix issues in the affected vendored code [Background information] ADSys is composed o
[Desktop-packages] [Bug 1962293] [NEW] fps drop with on-demand profile
Public bug reported: Hi, I have Lenovo Ideapad S540 with a NVIDIA GeForce GTX 1650 with Max-Q Design (GPU 0) and Ubuntu 20.04, when I choose the on-demand profile, everything is fine except bothering fps drop, when moving curser or opening a window and etc. So with the last update which power saving is disabled, I have to downgrade to the previous version, because of high power usage with the performance profile. I have this problem with ubuntu 18.04 and continues till now. ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1962293 Title: fps drop with on-demand profile Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Hi, I have Lenovo Ideapad S540 with a NVIDIA GeForce GTX 1650 with Max-Q Design (GPU 0) and Ubuntu 20.04, when I choose the on-demand profile, everything is fine except bothering fps drop, when moving curser or opening a window and etc. So with the last update which power saving is disabled, I have to downgrade to the previous version, because of high power usage with the performance profile. I have this problem with ubuntu 18.04 and continues till now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1962293/+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 662840]
There is some work happening here currently. See bug 1402822 -- 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/662840 Title: Spell checking more than one language in Firefox Status in Mozilla Firefox: Invalid Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox capability to spell check for multiple languages in text forms. This is very annoying as I use two or three different languages in a single form when composing emails for example, and also switch between tabs/firefox windows to fill out forms in different languages, and now I have to switch between dictionaries back and forth. Never was an issue before. There is a need to set up multiple dictionaries/languages to be used at once for seamless spell check on a text form. Am I missing something? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 18 21:59:46 2010 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+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 662840]
I know this is older, but there is a more active issue about this. *** This bug has been marked as a duplicate of bug 1402822 *** -- 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/662840 Title: Spell checking more than one language in Firefox Status in Mozilla Firefox: Invalid Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox capability to spell check for multiple languages in text forms. This is very annoying as I use two or three different languages in a single form when composing emails for example, and also switch between tabs/firefox windows to fill out forms in different languages, and now I have to switch between dictionaries back and forth. Never was an issue before. There is a need to set up multiple dictionaries/languages to be used at once for seamless spell check on a text form. Am I missing something? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 18 21:59:46 2010 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+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 662840] Re: Spell checking more than one language in Firefox
** Changed in: firefox Status: New => Invalid -- 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/662840 Title: Spell checking more than one language in Firefox Status in Mozilla Firefox: Invalid Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox capability to spell check for multiple languages in text forms. This is very annoying as I use two or three different languages in a single form when composing emails for example, and also switch between tabs/firefox windows to fill out forms in different languages, and now I have to switch between dictionaries back and forth. Never was an issue before. There is a need to set up multiple dictionaries/languages to be used at once for seamless spell check on a text form. Am I missing something? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 18 21:59:46 2010 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+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 1961565] Re: Package in bionic installs unnecessary build artifacts
** Branch linked: lp:~chromium-team/chromium-browser/bionic-dev -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1961565 Title: Package in bionic installs unnecessary build artifacts Status in chromium-browser package in Ubuntu: In Progress Status in chromium-browser source package in Bionic: New Bug description: Not sure when this started happening, but today I noticed while testing chromium-browser 98.0.4758.102-0ubuntu0.18.04.1 that the chromium-browser binary package installs a lot of build artifacts that increase unnecessarily the size of the package. These artifacts include *.runtime_deps files, as well as binaries such as transport_security_state_generator or protozero_plugin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1961565/+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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** No longer affects: systemd (Ubuntu Groovy) ** No longer affects: systemd (Ubuntu Hirsute) ** Also affects: dbus (Ubuntu Jammy) Importance: High Status: Incomplete ** Also affects: gnome-shell (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: accountsservice (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Changed in: dbus (Ubuntu Impish) Status: Incomplete => Invalid ** Changed in: dbus (Ubuntu Jammy) Status: Incomplete => Invalid ** Changed in: dbus (Ubuntu Groovy) Status: Incomplete => Invalid ** Changed in: dbus (Ubuntu Focal) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: New Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: New Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: New Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNO
[Desktop-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Description changed: + [Impact] + + * There's currently a deadlock between PID 1 and dbus-daemon: in some + cases dbus-daemon will do NSS lookups (which are blocking) at the same + time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break + that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, + which will disable synchronously blocking varlink calls from nss-systemd + to PID 1. + + * This can lead to delayed boot times + + * It can also lead to dbus-daemon being killed/re-started, taking down + other services with it, like GDM, killing user sessions on the way (e.g. + on installing updates) + + [Test Plan] + + * This bug is really hard to reproduce, as can be seen from the multi- + year long discussion at https://github.com/systemd/systemd/issues/15316 + + * Canonical's CPC team has the ability to reproduce this issue (with a + relatively high probability) in their Azure test environment, due to the + specific setup they are using + + * So our test plan is to ask CPC (@gjolly) for confirmation if the + issue is fixed. + + [Where problems could occur] + + * This fix touches the communication between systemd and dbus daemon, + especially the NSS lookup, so if something is broken the (user-)name + resolution could be broken. + + * As a workaround dbus-daemon could be replaced by dbus-broker, which + never showed this issue or the behaviour could be changed back by using + the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: + + #/etc/systemd/system/dbus.service.d/override.conf + [Service] + Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 + + [Other Info] + + * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 + + + === Original Description === + + + This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash - rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 - - But that already was only triggered by a gnome restart that kicked of earlier: + But that already was only triggered by a gnome restart that kicked of + earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). - X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeic
[Desktop-packages] [Bug 1960621] Re: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers
I've built Metacity 3.42 for Ubuntu 21.10 with Xpresent support, which is behind a gsettings option that defaults to xrender. When Metacity is set as the required window manager in MATE with Xpresent set as the compositor the same failure to bring up a desktop session is encountered. I have also built Marco without Xpresent and as expected it fallsback to Xrender which works with the new NVIDIA drivers and also preserves compositor support. ** Summary changed: - Nvidia 510 drivers result in failure to start GUI on GeForce GTX 1050 Ti + MATE Desktop session fails to start with NVIDIA 495 & 510 drivers ** Also affects: metacity (Ubuntu) Importance: Undecided Status: New ** Also affects: metacity (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: marco (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-510 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: metacity (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: marco (Ubuntu Jammy) Importance: High Assignee: Martin Wimpress (flexiondotorg) Status: Triaged ** Also affects: nvidia-graphics-drivers-510 (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Also affects: metacity (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: marco (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-510 (Ubuntu Impish) Importance: Undecided Status: New ** No longer affects: metacity (Ubuntu Focal) ** No longer affects: metacity (Ubuntu Impish) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1960621 Title: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers Status in marco package in Ubuntu: Triaged Status in metacity package in Ubuntu: New Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in marco source package in Focal: New Status in nvidia-graphics-drivers-510 source package in Focal: New Status in marco source package in Impish: New Status in nvidia-graphics-drivers-510 source package in Impish: New Status in marco source package in Jammy: Triaged Status in metacity source package in Jammy: New Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Bug description: I have been using nvidia-graphics-drivers-470 for a while. In January, I tried the 495 drivers, but this resulted in failing to start the GUI when booting: the mouse cursor would appear, but then the screen would clear and the switch to graphics would be attempted again. This would repeat until restarted, so I used recovery mode to test that a) it still happened with that (yes) and b) to go back to the 470 drivers via the root terminal. For some reason, yesterday xscreensaver had a problem getting the right GLcontext. I noticed that the 510 drivers were available, so used Software & Updates's Additional Drivers to install those. Exactly the same issue as with the 495 drivers: the mouse cursor appears for a second, then disappears, and reappears, and.. until I reboot and go back to 470. I am using Ubuntu MATE 21.10 with a GeForce GTX 1050 Ti card. $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1960621/+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 1960621] Re: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: metacity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1960621 Title: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers Status in marco package in Ubuntu: Triaged Status in metacity package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in marco source package in Focal: Confirmed Status in nvidia-graphics-drivers-510 source package in Focal: Confirmed Status in marco source package in Impish: Confirmed Status in nvidia-graphics-drivers-510 source package in Impish: Confirmed Status in marco source package in Jammy: Triaged Status in metacity source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Bug description: I have been using nvidia-graphics-drivers-470 for a while. In January, I tried the 495 drivers, but this resulted in failing to start the GUI when booting: the mouse cursor would appear, but then the screen would clear and the switch to graphics would be attempted again. This would repeat until restarted, so I used recovery mode to test that a) it still happened with that (yes) and b) to go back to the 470 drivers via the root terminal. For some reason, yesterday xscreensaver had a problem getting the right GLcontext. I noticed that the 510 drivers were available, so used Software & Updates's Additional Drivers to install those. Exactly the same issue as with the 495 drivers: the mouse cursor appears for a second, then disappears, and reappears, and.. until I reboot and go back to 470. I am using Ubuntu MATE 21.10 with a GeForce GTX 1050 Ti card. $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1960621/+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 1960621] Re: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-510 (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1960621 Title: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers Status in marco package in Ubuntu: Triaged Status in metacity package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in marco source package in Focal: Confirmed Status in nvidia-graphics-drivers-510 source package in Focal: Confirmed Status in marco source package in Impish: Confirmed Status in nvidia-graphics-drivers-510 source package in Impish: Confirmed Status in marco source package in Jammy: Triaged Status in metacity source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Bug description: I have been using nvidia-graphics-drivers-470 for a while. In January, I tried the 495 drivers, but this resulted in failing to start the GUI when booting: the mouse cursor would appear, but then the screen would clear and the switch to graphics would be attempted again. This would repeat until restarted, so I used recovery mode to test that a) it still happened with that (yes) and b) to go back to the 470 drivers via the root terminal. For some reason, yesterday xscreensaver had a problem getting the right GLcontext. I noticed that the 510 drivers were available, so used Software & Updates's Additional Drivers to install those. Exactly the same issue as with the 495 drivers: the mouse cursor appears for a second, then disappears, and reappears, and.. until I reboot and go back to 470. I am using Ubuntu MATE 21.10 with a GeForce GTX 1050 Ti card. $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1960621/+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 1960621] Re: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: marco (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1960621 Title: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers Status in marco package in Ubuntu: Triaged Status in metacity package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in marco source package in Focal: Confirmed Status in nvidia-graphics-drivers-510 source package in Focal: Confirmed Status in marco source package in Impish: Confirmed Status in nvidia-graphics-drivers-510 source package in Impish: Confirmed Status in marco source package in Jammy: Triaged Status in metacity source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Bug description: I have been using nvidia-graphics-drivers-470 for a while. In January, I tried the 495 drivers, but this resulted in failing to start the GUI when booting: the mouse cursor would appear, but then the screen would clear and the switch to graphics would be attempted again. This would repeat until restarted, so I used recovery mode to test that a) it still happened with that (yes) and b) to go back to the 470 drivers via the root terminal. For some reason, yesterday xscreensaver had a problem getting the right GLcontext. I noticed that the 510 drivers were available, so used Software & Updates's Additional Drivers to install those. Exactly the same issue as with the 495 drivers: the mouse cursor appears for a second, then disappears, and reappears, and.. until I reboot and go back to 470. I am using Ubuntu MATE 21.10 with a GeForce GTX 1050 Ti card. $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1960621/+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 1960621] Re: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: marco (Ubuntu Impish) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1960621 Title: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers Status in marco package in Ubuntu: Triaged Status in metacity package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in marco source package in Focal: Confirmed Status in nvidia-graphics-drivers-510 source package in Focal: Confirmed Status in marco source package in Impish: Confirmed Status in nvidia-graphics-drivers-510 source package in Impish: Confirmed Status in marco source package in Jammy: Triaged Status in metacity source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Bug description: I have been using nvidia-graphics-drivers-470 for a while. In January, I tried the 495 drivers, but this resulted in failing to start the GUI when booting: the mouse cursor would appear, but then the screen would clear and the switch to graphics would be attempted again. This would repeat until restarted, so I used recovery mode to test that a) it still happened with that (yes) and b) to go back to the 470 drivers via the root terminal. For some reason, yesterday xscreensaver had a problem getting the right GLcontext. I noticed that the 510 drivers were available, so used Software & Updates's Additional Drivers to install those. Exactly the same issue as with the 495 drivers: the mouse cursor appears for a second, then disappears, and reappears, and.. until I reboot and go back to 470. I am using Ubuntu MATE 21.10 with a GeForce GTX 1050 Ti card. $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1960621/+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 1960621] Re: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-510 (Ubuntu Impish) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1960621 Title: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers Status in marco package in Ubuntu: Triaged Status in metacity package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in marco source package in Focal: Confirmed Status in nvidia-graphics-drivers-510 source package in Focal: Confirmed Status in marco source package in Impish: Confirmed Status in nvidia-graphics-drivers-510 source package in Impish: Confirmed Status in marco source package in Jammy: Triaged Status in metacity source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Bug description: I have been using nvidia-graphics-drivers-470 for a while. In January, I tried the 495 drivers, but this resulted in failing to start the GUI when booting: the mouse cursor would appear, but then the screen would clear and the switch to graphics would be attempted again. This would repeat until restarted, so I used recovery mode to test that a) it still happened with that (yes) and b) to go back to the 470 drivers via the root terminal. For some reason, yesterday xscreensaver had a problem getting the right GLcontext. I noticed that the 510 drivers were available, so used Software & Updates's Additional Drivers to install those. Exactly the same issue as with the 495 drivers: the mouse cursor appears for a second, then disappears, and reappears, and.. until I reboot and go back to 470. I am using Ubuntu MATE 21.10 with a GeForce GTX 1050 Ti card. $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1960621/+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 1960621] Re: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers
** Changed in: marco (Ubuntu Jammy) Status: Triaged => Fix Committed ** Changed in: marco (Ubuntu Impish) Status: Confirmed => In Progress ** Changed in: marco (Ubuntu Focal) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1960621 Title: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers Status in marco package in Ubuntu: Fix Committed Status in metacity package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in marco source package in Focal: In Progress Status in nvidia-graphics-drivers-510 source package in Focal: Confirmed Status in marco source package in Impish: In Progress Status in nvidia-graphics-drivers-510 source package in Impish: Confirmed Status in marco source package in Jammy: Fix Committed Status in metacity source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Bug description: I have been using nvidia-graphics-drivers-470 for a while. In January, I tried the 495 drivers, but this resulted in failing to start the GUI when booting: the mouse cursor would appear, but then the screen would clear and the switch to graphics would be attempted again. This would repeat until restarted, so I used recovery mode to test that a) it still happened with that (yes) and b) to go back to the 470 drivers via the root terminal. For some reason, yesterday xscreensaver had a problem getting the right GLcontext. I noticed that the 510 drivers were available, so used Software & Updates's Additional Drivers to install those. Exactly the same issue as with the 495 drivers: the mouse cursor appears for a second, then disappears, and reappears, and.. until I reboot and go back to 470. I am using Ubuntu MATE 21.10 with a GeForce GTX 1050 Ti card. $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1960621/+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 1960621] Re: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers
I've uploaded Marco to Jammy with Xpresent disabled. I've created a PPA for users of Ubuntu MATE 20.04 and 21.10 that hosts rebuilds of Marco with Xpresent disabled. * https://launchpad.net/~ubuntu-mate-dev/+archive/ubuntu/marco These packages are what I propose to upload as bug fixes to the 20.04 and 21.10 archives. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1960621 Title: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers Status in marco package in Ubuntu: Fix Committed Status in metacity package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in marco source package in Focal: In Progress Status in nvidia-graphics-drivers-510 source package in Focal: Confirmed Status in marco source package in Impish: In Progress Status in nvidia-graphics-drivers-510 source package in Impish: Confirmed Status in marco source package in Jammy: Fix Committed Status in metacity source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Bug description: I have been using nvidia-graphics-drivers-470 for a while. In January, I tried the 495 drivers, but this resulted in failing to start the GUI when booting: the mouse cursor would appear, but then the screen would clear and the switch to graphics would be attempted again. This would repeat until restarted, so I used recovery mode to test that a) it still happened with that (yes) and b) to go back to the 470 drivers via the root terminal. For some reason, yesterday xscreensaver had a problem getting the right GLcontext. I noticed that the 510 drivers were available, so used Software & Updates's Additional Drivers to install those. Exactly the same issue as with the 495 drivers: the mouse cursor appears for a second, then disappears, and reappears, and.. until I reboot and go back to 470. I am using Ubuntu MATE 21.10 with a GeForce GTX 1050 Ti card. $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1960621/+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 1945776] Re: Firefox freezes continuously on Ubuntu 20.04
Thanks for the info. It would be very helpful if you could try upstream builds and let us know whether they are similarly affected. -- 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/1945776 Title: Firefox freezes continuously on Ubuntu 20.04 Status in firefox package in Ubuntu: Incomplete Bug description: Similar to other bug in my notebook with Ubuntu 16.04: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1792329 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 92.0+build3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stefano1615 F pulseaudio BuildID: 20210903235534 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Oct 1 13:41:19 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:358 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2021-05-12 (141 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IpRoute: default via 192.168.1.1 dev enp8s0 proto dhcp metric 100 169.254.0.0/16 dev enp8s0 scope link metric 1000 192.168.1.0/24 dev enp8s0 proto kernel scope link src 192.168.1.47 metric 100 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.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:358 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=92.0/20210903235534 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/30/2012 dmi.bios.release: 0.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0RW199 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd04/30/2012:br0.0:svnDellInc.:pnPrecisionWorkStationT7400:pvr:sku:rvnDellInc.:rn0RW199:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T7400 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1945776/+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 1951698] Re: [upstream] under wayland items in menu bar sub-menus cannot be moved
Thanks for following up Henning. Would you mind filing a new upstream bug at https://bugzilla.mozilla.org/enter_bug.cgi with all these details, and share the link to it here? -- 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/1951698 Title: [upstream] under wayland items in menu bar sub-menus cannot be moved Status in Mozilla Firefox: Invalid Status in firefox package in Ubuntu: Incomplete Bug description: When running firefox on wayland, it appears to be impossible to move bookmark items in the menu bar sub menus. How to reproduce: * haver a gnome session with wayland * have the menu bar toolbar activated * have a folder in the menu bar * have multiple bookmarks in that folder * click on the folder icon in the menu bar, when it opens, try to drag and drop the item to put it into another position - e.g. from the last to the first Expected result: * the bookmark item is move to the new position - this is waht happens when doing these steps with firefox on gnome with an xorg sessions. Actual result: the item stays where it was. similarly, i cannot drag and drop a new bookmark into a folder and out it into the position where I want to have it. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: firefox 94.0+build3-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18 Uname: Linux 5.13.0-21-lowlatency x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: henning 63267 F pulseaudio /dev/snd/controlC1: henning 63267 F pulseaudio BuildID: 20211028161635 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Sat Nov 20 21:21:03 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:363 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-04-12 (586 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) 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:363 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=84.0.2/20210105180113 (Out of date) Profile0 - LastVersion=94.0/20211028161635 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to impish on 2021-11-14 (5 days ago) dmi.bios.date: 08/17/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET53W (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET53W(1.40):bd08/17/2021:br1.40:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QV00CEGE dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1951698/+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 1962327] [NEW] VERTICAL FRACTION FEATURE PRESENT IN FONT NOT APPLIED BY WRITER
Public bug reported: ~ $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 ~$ apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:6.4.7-0ubuntu0.20.04.2 Candidate: 1:6.4.7-0ubuntu0.20.04.2 Version table: *** 1:6.4.7-0ubuntu0.20.04.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 1:6.4.2-0ubuntu3 500 500 http://in.archive.ubuntu.com/ubuntu focal/main amd64 Packages ~$ apt-show-versions -r libreoffice* liblibreofficekitgtk:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-base-core:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-calc:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-common:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-core:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-draw:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gnome:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk2:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk3:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-impress:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-java-common:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-l10n-bn:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-math:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-colibre:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-elementary:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-tango:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-writer:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreofficekit-data:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate What is expected to happen in Writer is My font has vertical fraction look up for Bengali script. On selecting Format > Characters > CTL Font > Features Alternate (vertical) Fraction Feature is visible in options. Selecting the option should apply the feature on selected fraction see screenshot http://cloud.atipra.in/index.php/s/YosGiyFSoTQeW8i What happened instead is.. The feature is not applied, and the selected text is unchanged It should change as happens in firefox on selecting alternate (Vertical) fraction lookup in css see screenshot http://cloud.atipra.in/index.php/s/MxYbEisyFT3KnKT Extension installed : None ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-writer 1:6.4.7-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 20:33:24 2022 InstallationDate: Installed on 2020-01-03 (783 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2021-09-16 (162 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- 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/1962327 Title: VERTICAL FRACTION FEATURE PRESENT IN FONT NOT APPLIED BY WRITER Status in libreoffice package in Ubuntu: New Bug description: ~ $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ~$ apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:6.4.7-0ubuntu0.20.04.2 Candidate: 1:6.4.7-0ubuntu0.20.04.2 Version table: *** 1:6.4.7-0ubuntu0.20.04.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 1:6.4.2-0ubuntu3 500 500 http://in.archive.ubuntu.com/ubuntu focal/main amd64 Packages ~$ apt-show-versions -r libreoffice* liblibreofficekitgtk:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-base-core:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-calc:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-common:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-core:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-draw:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gnome:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk2:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk3:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-impress:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 u
[Desktop-packages] [Bug 1960621] Re: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers
The root cause of this issue appears to be a bug in Xorg Xserver for which a patch exists: * https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275 * https://salsa.debian.org/xorg-team/xserver/xorg-server/-/commit/4aa04b0377a5b916575792c81fd2e6551913f589 * https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1959995 ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1275 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1960621 Title: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers Status in marco package in Ubuntu: Fix Committed Status in metacity package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in marco source package in Focal: In Progress Status in nvidia-graphics-drivers-510 source package in Focal: Confirmed Status in marco source package in Impish: In Progress Status in nvidia-graphics-drivers-510 source package in Impish: Confirmed Status in marco source package in Jammy: Fix Committed Status in metacity source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Bug description: I have been using nvidia-graphics-drivers-470 for a while. In January, I tried the 495 drivers, but this resulted in failing to start the GUI when booting: the mouse cursor would appear, but then the screen would clear and the switch to graphics would be attempted again. This would repeat until restarted, so I used recovery mode to test that a) it still happened with that (yes) and b) to go back to the 470 drivers via the root terminal. For some reason, yesterday xscreensaver had a problem getting the right GLcontext. I noticed that the 510 drivers were available, so used Software & Updates's Additional Drivers to install those. Exactly the same issue as with the 495 drivers: the mouse cursor appears for a second, then disappears, and reappears, and.. until I reboot and go back to 470. I am using Ubuntu MATE 21.10 with a GeForce GTX 1050 Ti card. $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1960621/+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 1955500] Re: firefox crashes often
One of these crashes (the first in the list of submitted crash IDs) is https://crash- stats.mozilla.org/report/index/6d5c31fc-1b33-459b-bfab-9d3b20211216 (crash in _XEventsQueued). I cannot access the other submitted crashes, so I can't check whether they have a similar signature. -- 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/1955500 Title: firefox crashes often Status in firefox package in Ubuntu: Incomplete Bug description: Recently (since ~2021-12-15) firefox has been crashing a lot, often daily. There's no obvious pattern that I can see. Most recent crash logs: Dec 21 12:37:51 cerberus firefox.desktop[755990]: Sandbox: Unexpected EOF, op 0 flags 0200 path /proc/755990/cgroup Dec 21 12:37:51 cerberus firefox.desktop[756121]: Exiting due to channel error. Dec 21 12:37:51 cerberus firefox.desktop[755809]: Exiting due to channel error. Dec 21 12:37:51 cerberus firefox.desktop[755990]: Exiting due to channel error. ... Dec 21 12:37:51 cerberus firefox.desktop[745228]: [GFX1-]: Receive IPC close with reason=AbnormalShutdown Dec 21 12:37:51 cerberus firefox.desktop[744870]: Exiting due to channel error. ... Previous crash: Dec 20 12:56:53 cerberus kernel: traps: GeckoMain[613052] trap int3 ip:7fa351cc1295 sp:7fff6ba7eea0 error:0 in libglib-2.> Dec 20 12:56:53 cerberus gnome-shell[722119]: Exiting due to channel error. Dec 20 12:56:53 cerberus gnome-shell[722386]: Exiting due to channel error. Dec 20 12:56:53 cerberus gnome-shell[615970]: Exiting due to channel error. Dec 20 12:56:53 cerberus gnome-shell[717612]: Exiting due to channel error. ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 95.0.1+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: jlquinn2641 F pulseaudio /dev/snd/controlC0: jlquinn2641 F pulseaudio /dev/snd/controlC2: jlquinn2641 F pulseaudio /dev/snd/controlC1: jlquinn2641 F pulseaudio BuildID: 20211215221728 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Dec 21 13:17:24 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:363 DefaultProfilePrefSources: 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 InstallationDate: Installed on 2020-05-29 (570 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IpRoute: default via 192.168.1.1 dev enp4s0 proto dhcp metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.1.0/24 dev enp4s0 proto kernel scope link src 192.168.1.10 metric 100 MostRecentCrashID: bp-6d5c31fc-1b33-459b-bfab-9d3b20211216 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:363 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=54.0/20170612122310 (Out of date) Profile0 (Default) - LastVersion=95.0.1/20211215221728 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to focal on 2020-11-04 (412 days ago) dmi.bios.date: 12/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X10DAI dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.2:bd12/16/2019:svnSupermicro:pnX10DAi:pvr123456789:rvnSupermicro:rnX10DAI:rvr1.01:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.: dmi.product.family: SMC X10 dmi.product.name: X10DAi
[Desktop-packages] [Bug 1959995] Re: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46)
I confirm this issue affects users of NVIDIA 495 and 510 drivers if they use an Xpresent compositor such as Marco (the MATE Windows Manager) or Metacity 3.42. It affects Ubuntu MATE 20.04 and 21.10 users. ** Also affects: xorg-server (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Impish) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1959995 Title: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46) Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Triaged Status in xorg-server source package in Focal: New Status in xorg-server source package in Impish: New Bug description: This bug causes xserver to crash when using newer Nvidia drivers (NVIDIA 495.46+) with Optimus. It's apparently triggered when using the MATE desktop environment. It has been noticed on xorg-server-21.1, but it's likely affecting version 1.20.13 as well. It has been fixed already, but could you please backport the fix? Patch that fixes it is here: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/841/diffs?commit_id=22d5818851967408bb7c903cb345b7ca8766094c The bug report at freedesktop.org is here: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275 Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1959995/+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 1954765] Re: Firefox instance opens with an unusable window that has the content area filled with the frozen image of the window/desktop image in the background
Thanks for following up! If you don't mind switching back to 'Intel (Power saving mode)' and testing again, that would be helpful. When you do that, can you please test an upstream build (downloaded from https://www.mozilla.org/en-US/firefox/download/thanks/) to see whether it's an Ubuntu-specific problem? Otherwise, feel free to close the bug. -- 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/1954765 Title: Firefox instance opens with an unusable window that has the content area filled with the frozen image of the window/desktop image in the background Status in firefox package in Ubuntu: Confirmed Bug description: After a recent Firefox update (I think this started after the Firefox 95 upgrade), opening Firefox often opens a window with a visible title bar that indicates that the application in focus is Firefox but the content area is invisible because it has the frozen image/background of either the windows/application behind the Firefox window or the desktop background image if there are no windows behind Firefox. The Firefox shortcut keys work and I am able to open a site by pressing Ctrl+L to focus the address bar and type a domain name/URL. The website/URL loads okay but nothing is visible because of the content area being hidden by the frozen image. Resizing/minimizing+maximizing the Firefox window doesn't resolve this issue. However, when I launch Firefox from the terminal, it works properly every single time. So it looks like there might be some issue only when launching from the Firefox application launcher (.desktop file). ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: firefox 95.0+build1-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guruprasad 4057 F pulseaudio BuildID: 20211129150630 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: KDE Date: Tue Dec 14 17:17:46 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:363 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2021-12-02 (12 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 192.168.0.1 dev wlp59s0 proto dhcp metric 600 10.154.85.0/24 dev lxdbr0 proto kernel scope link src 10.154.85.1 169.254.0.0/16 dev lxdbr0 scope link metric 1000 192.168.0.0/24 dev wlp59s0 proto kernel scope link src 192.168.0.102 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:363 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:363 Profile2PrefSources: prefs.js Profile2Themes: extensions.sqlite corrupt or missing Profile3Extensions: extensions.sqlite corrupt or missing Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile3Locales: extensions.sqlite corrupt or missing Profile3PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:363 Profile3PrefSources: prefs.js Profile3Themes: extensions.sqlite corrupt or missing Profiles: Profile3 - LastVersion=94.0/20211028161635 (Out of date) Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=95.0/20211129150630 (In use) Profile2 - LastVersion=95.0/20211129150630 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2021 dmi.bios.release: 1.22 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.22.1 dmi.board.name: 0N0DK2 dmi.board.vendor: Dell
[Desktop-packages] [Bug 1962327] Re: VERTICAL FRACTION FEATURE PRESENT IN FONT NOT APPLIED BY WRITER
** Attachment added: "How feature is selected in Libreoffice but not applied" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1962327/+attachment/5563714/+files/Screenshot%20from%202022-02-25%2021-21-27.png -- 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/1962327 Title: VERTICAL FRACTION FEATURE PRESENT IN FONT NOT APPLIED BY WRITER Status in libreoffice package in Ubuntu: New Bug description: ~ $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ~$ apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:6.4.7-0ubuntu0.20.04.2 Candidate: 1:6.4.7-0ubuntu0.20.04.2 Version table: *** 1:6.4.7-0ubuntu0.20.04.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 1:6.4.2-0ubuntu3 500 500 http://in.archive.ubuntu.com/ubuntu focal/main amd64 Packages ~$ apt-show-versions -r libreoffice* liblibreofficekitgtk:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-base-core:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-calc:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-common:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-core:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-draw:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gnome:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk2:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk3:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-impress:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-java-common:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-l10n-bn:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-math:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-colibre:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-elementary:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-tango:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-writer:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreofficekit-data:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate What is expected to happen in Writer is My font has vertical fraction look up for Bengali script. On selecting Format > Characters > CTL Font > Features Alternate (vertical) Fraction Feature is visible in options. Selecting the option should apply the feature on selected fraction see screenshot http://cloud.atipra.in/index.php/s/YosGiyFSoTQeW8i What happened instead is.. The feature is not applied, and the selected text is unchanged It should change as happens in firefox on selecting alternate (Vertical) fraction lookup in css see screenshot http://cloud.atipra.in/index.php/s/MxYbEisyFT3KnKT Extension installed : None ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-writer 1:6.4.7-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 20:33:24 2022 InstallationDate: Installed on 2020-01-03 (783 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2021-09-16 (162 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1962327/+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 1962327] Re: VERTICAL FRACTION FEATURE PRESENT IN FONT NOT APPLIED BY WRITER
** Attachment added: "How should it look if feature applied properly (as in firefox)" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1962327/+attachment/5563715/+files/Screenshot%20from%202022-02-25%2021-22-41.png -- 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/1962327 Title: VERTICAL FRACTION FEATURE PRESENT IN FONT NOT APPLIED BY WRITER Status in libreoffice package in Ubuntu: New Bug description: ~ $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ~$ apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:6.4.7-0ubuntu0.20.04.2 Candidate: 1:6.4.7-0ubuntu0.20.04.2 Version table: *** 1:6.4.7-0ubuntu0.20.04.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 1:6.4.2-0ubuntu3 500 500 http://in.archive.ubuntu.com/ubuntu focal/main amd64 Packages ~$ apt-show-versions -r libreoffice* liblibreofficekitgtk:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-base-core:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-calc:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-common:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-core:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-draw:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gnome:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk2:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk3:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-impress:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-java-common:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-l10n-bn:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-math:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-colibre:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-elementary:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-tango:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-writer:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreofficekit-data:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate What is expected to happen in Writer is My font has vertical fraction look up for Bengali script. On selecting Format > Characters > CTL Font > Features Alternate (vertical) Fraction Feature is visible in options. Selecting the option should apply the feature on selected fraction see screenshot http://cloud.atipra.in/index.php/s/YosGiyFSoTQeW8i What happened instead is.. The feature is not applied, and the selected text is unchanged It should change as happens in firefox on selecting alternate (Vertical) fraction lookup in css see screenshot http://cloud.atipra.in/index.php/s/MxYbEisyFT3KnKT Extension installed : None ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-writer 1:6.4.7-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 20:33:24 2022 InstallationDate: Installed on 2020-01-03 (783 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2021-09-16 (162 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1962327/+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 1939058] Re: autopkgtest failure "stacking/override-redirect.metatest" on armhf
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1939058 Title: autopkgtest failure "stacking/override-redirect.metatest" on armhf Status in mutter package in Ubuntu: Confirmed Bug description: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/m/mutter/20210805_091629_afb25@/log.gz Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x43 not ok 18 stacking/override-redirect.metatest 15: stacking: expected='1/2 | 1/1', actual='| 1/1 1/2' From the test history on armhf, it appears this particular test case intermittently passes or fails about half the time. Other architectures have been passing all tests reliably without errors. Presumably the stacking order is non-deterministic on armhf for some reason? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1939058/+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 1959995] Re: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu Impish) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1959995 Title: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46) Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Triaged Status in xorg-server source package in Focal: Confirmed Status in xorg-server source package in Impish: Confirmed Bug description: This bug causes xserver to crash when using newer Nvidia drivers (NVIDIA 495.46+) with Optimus. It's apparently triggered when using the MATE desktop environment. It has been noticed on xorg-server-21.1, but it's likely affecting version 1.20.13 as well. It has been fixed already, but could you please backport the fix? Patch that fixes it is here: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/841/diffs?commit_id=22d5818851967408bb7c903cb345b7ca8766094c The bug report at freedesktop.org is here: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275 Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1959995/+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 1959995] Re: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1959995 Title: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46) Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Triaged Status in xorg-server source package in Focal: Confirmed Status in xorg-server source package in Impish: Confirmed Bug description: This bug causes xserver to crash when using newer Nvidia drivers (NVIDIA 495.46+) with Optimus. It's apparently triggered when using the MATE desktop environment. It has been noticed on xorg-server-21.1, but it's likely affecting version 1.20.13 as well. It has been fixed already, but could you please backport the fix? Patch that fixes it is here: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/841/diffs?commit_id=22d5818851967408bb7c903cb345b7ca8766094c The bug report at freedesktop.org is here: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275 Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1959995/+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 1962237] Re: blue tooth/wireless mouse not working
Ran this hack: https://www.youtube.com/watch?v=I2rHRi2ll9Q and rebooted in recovery mode and mouse is at least temporarily functional. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1962237 Title: blue tooth/wireless mouse not working Status in xdiagnose package in Ubuntu: New Bug description: The mouse can occasionally be made to work by going back through settings, etc. but then very shortly stops again. I recently updated the system and had to interrupt the update as it was in an infinite loop while install was running. I am also running a bitcoin node that is not remembering where I was on the last run of bitcoin core. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1962237/+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 1962340] [NEW] Printer rarely actually prints after processing the file.
Public bug reported: My printer is a Brother HL-L2320D laser printer connected via USB with no option for wifi-printing as it's not supported by this printer. It is connected via a USB 3.0 port on my laptop. I'm logged in via regular user, not admin. It is odd that it acts as though it's going to print, then when it's done processing it just disappears from the print que as if the print has been completed. This isn't specific to my Brother printer. I also had this problem with an HP printer prior to replacing the old HP printer. I had this happen in Lubuntu and also in Ubuntu. Description:Ubuntu 20.04.3 LTS Release:20.04 cups: Installed: 2.3.1-9ubuntu1.1 Candidate: 2.3.1-9ubuntu1.1 Version table: *** 2.3.1-9ubuntu1.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages I expected my files to print, but they didn't. I did successfully print two of the 6 documents, but what's different about them versus the others, I have no idea. I tried printing via Eye of MATE (which was the default program to open some of the files), and I tried printing them via Firefox, and another file via Libre Office Writer. LO Writer won't print. Eye of Mate won't print. Firefox won't print. I restarted cups via the terminal with "service cups restart" and tried printing via Eye of MATE. It didn't work. I then tried to print via LO Writer. Of the six page document, only the first page printed. What the heck is going on? I then exported that Writer document (which was saved both as .odt and as .docx (neither would print properly or at all) as PDF and opened that with Atril Document Viewer, and it also wouldn't print. It acted like it was processing then disappeared from the Document Printer Status window as if it had completed. Clicking the checkbox it appears as though it was completed. I've never had so many problems trying to print before. I know it's not specific to HP printers, because it's my current printer that's behaving the same way as my old HP and this is Brother. I hoped restarting cups again would fix it, it has not. Switching to a USB 2.0 port didn't resolve the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: CurrentDesktop: MATE Date: Fri Feb 25 09:54:20 2022 InstallationDate: Installed on 2022-01-06 (50 days ago) InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Lpstat: device for HL-L2320D-series: usb://Brother/HL-L2320D%20series?serial=U63877M0N488610 MachineType: Acer Aspire R5-471T Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HL-L2320D-series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HL-L2320D-series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=f217636e-4924-4eb3-8c0e-bde536732ded ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2018 dmi.bios.release: 1.13 dmi.bios.vendor: Acer dmi.bios.version: V1.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Luffy dmi.board.vendor: Acer dmi.board.version: V1.13 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnAcer:bvrV1.13:bd03/07/2018:br1.13:efr1.9:svnAcer:pnAspireR5-471T:pvrV1.13:rvnAcer:rnLuffy:rvrV1.13:cvnAcer:ct10:cvrChassisVersion:skuAspireR5-471T_105A_1.13: dmi.product.family: SKL dmi.product.name: Aspire R5-471T dmi.product.sku: Aspire R5-471T_105A_1.13 dmi.product.version: V1.13 dmi.sys.vendor: Acer ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1962340 Title: Printer rarely actually prints after processing the file. Status in cups package in Ubuntu: New Bug description: My printer is a Brother HL-L2320D laser printer connected via USB with no option for wifi-printing as it's not supported by this printer. It is connected via a USB 3.0 port on my laptop. I'm logged in via regular user, not admin. It is odd that it acts as though it's going to print, then when it's done processing it just disappears from the print que as if the print has been completed. This isn't specific to my Brother printer. I also had this problem with an HP printer prior to replacing the old HP printer. I had this happen in Lubuntu
[Desktop-packages] [Bug 1962043] Re: libwacom9 : depends on : libwacom-common
It's not ARM-specific; x86-64 is also affected for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwacom in Ubuntu. https://bugs.launchpad.net/bugs/1962043 Title: libwacom9 : depends on : libwacom-common Status in libwacom package in Ubuntu: Confirmed Bug description: Broken denpendency on ARM64: (rpi4 @ ubuntu 22.04 test) libwacom9 : depend on: libwacom-common (= 2.1.0-2) but will be installed 1.12-1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libwacom-common 1.12-1 ProcVersionSignature: Ubuntu 5.15.0-1002.2-raspi 5.15.12 Uname: Linux 5.15.0-1002-raspi aarch64 ApportVersion: 2.20.11-0ubuntu78 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: GNOME Date: Wed Feb 23 21:03:57 2022 Dependencies: DistUpgraded: 2022-02-11 12:31:30,541 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: wireguard/1.0.20210606: added GraphicsCard: ImageMediaBuild: 20201022 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sk_SK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:7D:95:B4 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc SourcePackage: libwacom UpgradeStatus: Upgraded to jammy on 2022-02-11 (12 days ago) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1962043/+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 1870829] Re: AptX and AptX HD unavailable as Bluetooth audio quality options
** Changed in: pulseaudio (Debian) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1870829 Title: AptX and AptX HD unavailable as Bluetooth audio quality options Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Debian: Fix Released Bug description: Current situation: When one connects a Bluetooth audio device, at best one can choose between "Headset Head Unit (HSP/HFP)" and "High Fidelity Playback (A2DP Sink)". That is sad when the audio device supports AptX or AptX HD. Expected situation: One can select AptX or AptX HD as the Bluetooth audio output profile. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870829/+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 1962337] [NEW] Pointer,Prospekt Mail
You have been subscribed to a public bug: My Mouse sometimes jumps from left to right and presses down the right and left buttons. Restarting helps. It opens apps and i am unable to use the computer. Prospekt Mail refuses to open. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 18:05:27 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80dd] InstallationDate: Installed on 2022-01-29 (27 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b50c Chicony Electronics Co., Ltd HP Truevision HD Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY m6 Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=4e8d5df3-3d45-48d0-a629-0d7e3fa05d7e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2015 dmi.bios.release: 15.34 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DD dmi.board.vendor: HP dmi.board.version: 64.31 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 64.31 dmi.modalias: dmi:bvnInsyde:bvrF.22:bd10/16/2015:br15.34:efr64.31:svnHP:pnHPENVYm6Notebook:pvrType1ProductConfigId:rvnHP:rn80DD:rvr64.31:cvnHP:ct10:cvrChassisVersion:skuT0U83UA#ABA: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY m6 Notebook dmi.product.sku: T0U83UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- Pointer,Prospekt Mail https://bugs.launchpad.net/bugs/1962337 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962337] Re: Pointer,Prospekt Mail
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1962337 Title: Pointer,Prospekt Mail Status in xorg package in Ubuntu: New Bug description: My Mouse sometimes jumps from left to right and presses down the right and left buttons. Restarting helps. It opens apps and i am unable to use the computer. Prospekt Mail refuses to open. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 18:05:27 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80dd] InstallationDate: Installed on 2022-01-29 (27 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b50c Chicony Electronics Co., Ltd HP Truevision HD Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY m6 Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=4e8d5df3-3d45-48d0-a629-0d7e3fa05d7e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2015 dmi.bios.release: 15.34 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DD dmi.board.vendor: HP dmi.board.version: 64.31 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 64.31 dmi.modalias: dmi:bvnInsyde:bvrF.22:bd10/16/2015:br15.34:efr64.31:svnHP:pnHPENVYm6Notebook:pvrType1ProductConfigId:rvnHP:rn80DD:rvr64.31:cvnHP:ct10:cvrChassisVersion:skuT0U83UA#ABA: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY m6 Notebook dmi.product.sku: T0U83UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1962337/+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 1962344] [NEW] fprintd fails to start through core-dump
Public bug reported: some more info : feb 25 21:14:03 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Main process exited, code=dumped, status=11/SEGV ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit fprintd.service has exited. ░░ ░░ The process' exit code is 'dumped' and its exit status is 11. feb 25 21:14:03 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Failed with result 'core-dump'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit fprintd.service has entered the 'failed' state with result 'core-dump'. feb 25 21:14:03 ubuntu-inspiron-5482 systemd[1]: Failed to start Fingerprint Authentication Daemon. ░░ Subject: A start job for unit fprintd.service has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit fprintd.service has finished with a failure. ░░ ░░ The job identifier is 4596 and the job result is failed. ubuntu@ubuntu-inspiron-5482:~$ dpkg -l fprintd Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== ii fprintd1.94.2-1 amd64D-Bus daemon for fingerprint reader access if the fprintd package is installed and fprintd-enroll is run, it times out. That triggers a bug in gdm3 at login, where the user account is not visibe and one cannot login. I have a goodix fingerprint reader: Bus 001 Device 002: ID 27c6:538c Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: fprintd 1.94.2-1 Uname: Linux 5.12.19-051219-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 21:19:31 2022 InstallationDate: Installed on 2019-12-17 (801 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: fprintd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fprintd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1962344 Title: fprintd fails to start through core-dump Status in fprintd package in Ubuntu: New Bug description: some more info : feb 25 21:14:03 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Main process exited, code=dumped, status=11/SEGV ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit fprintd.service has exited. ░░ ░░ The process' exit code is 'dumped' and its exit status is 11. feb 25 21:14:03 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Failed with result 'core-dump'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit fprintd.service has entered the 'failed' state with result 'core-dump'. feb 25 21:14:03 ubuntu-inspiron-5482 systemd[1]: Failed to start Fingerprint Authentication Daemon. ░░ Subject: A start job for unit fprintd.service has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit fprintd.service has finished with a failure. ░░ ░░ The job identifier is 4596 and the job result is failed. ubuntu@ubuntu-inspiron-5482:~$ dpkg -l fprintd Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== ii fprintd1.94.2-1 amd64D-Bus daemon for fingerprint reader access if the fprintd package is installed and fprintd-enroll is run, it times out. That triggers a bug in gdm3 at login, where the user account is not visibe and one cannot login. I have a goodix fingerprint reader: Bus 001 Device 002: ID 27c6:538c Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: fprintd 1.94.2-1 Uname: Linux 5.12.19-051219-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 21:19:31 2022 InstallationDate: Installed on 2019-12-17 (801 days ago) InstallationMedia: Ubuntu 19.10 "Eoan
[Desktop-packages] [Bug 1960621] Re: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers
This bug was fixed in the package marco - 1.26.0-1ubuntu0 --- marco (1.26.0-1ubuntu0) jammy; urgency=medium * debian/control: + Drop B-D: libxpresent-dev (LP: #1960621) -- Martin Wimpress Fri, 25 Feb 2022 11:21:33 + ** Changed in: marco (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1960621 Title: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers Status in marco package in Ubuntu: Fix Released Status in metacity package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in marco source package in Focal: In Progress Status in nvidia-graphics-drivers-510 source package in Focal: Confirmed Status in marco source package in Impish: In Progress Status in nvidia-graphics-drivers-510 source package in Impish: Confirmed Status in marco source package in Jammy: Fix Released Status in metacity source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Bug description: I have been using nvidia-graphics-drivers-470 for a while. In January, I tried the 495 drivers, but this resulted in failing to start the GUI when booting: the mouse cursor would appear, but then the screen would clear and the switch to graphics would be attempted again. This would repeat until restarted, so I used recovery mode to test that a) it still happened with that (yes) and b) to go back to the 470 drivers via the root terminal. For some reason, yesterday xscreensaver had a problem getting the right GLcontext. I noticed that the 510 drivers were available, so used Software & Updates's Additional Drivers to install those. Exactly the same issue as with the 495 drivers: the mouse cursor appears for a second, then disappears, and reappears, and.. until I reboot and go back to 470. I am using Ubuntu MATE 21.10 with a GeForce GTX 1050 Ti card. $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1960621/+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 1962170] Re: DEP8 failure with samba 4.15.5
** Changed in: adsys (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1962170 Title: DEP8 failure with samba 4.15.5 Status in adsys package in Ubuntu: In Progress Bug description: The DEP8 tests of adsys started to fail[1] with my samba 4.15.5 upload. Some hints: ahasenack: it seems we can’t start our smbd local daemon to simulate Active Directory smb server ahasenack: yeah, I’m puzzled because on smbd start failure, we do print stderr (not stdout though): https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L16 https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L43 in particular you can see here how we start it: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L21 and the config template is at https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/internal/testutils/samba.go#L55 2022/02/24 03:13:59 Setup: smbd hasn’t started successfully that's here: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L129 you wait for the port to be open? which port is that, 445/tcp? we wait on the port to be opened, and this one is passed as a parameter, see the template. For the argument we pass in ad tests, once sec, looking 1446 https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/cmd/integration_tests/adsys_test.go#L47 you just need to run go test . in internal/ad/ the failure is as the pre-test setup 1. https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/a/adsys/20220224_031434_4d453@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1962170/+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 1960621] Re: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers
Thank you, Martin. I do indeed have Marco with the 'adaptive compositor' (it's the default, I think...) It's been ages since I used Compiz, but... :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1960621 Title: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers Status in marco package in Ubuntu: Fix Released Status in metacity package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in marco source package in Focal: In Progress Status in nvidia-graphics-drivers-510 source package in Focal: Confirmed Status in marco source package in Impish: In Progress Status in nvidia-graphics-drivers-510 source package in Impish: Confirmed Status in marco source package in Jammy: Fix Released Status in metacity source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Bug description: I have been using nvidia-graphics-drivers-470 for a while. In January, I tried the 495 drivers, but this resulted in failing to start the GUI when booting: the mouse cursor would appear, but then the screen would clear and the switch to graphics would be attempted again. This would repeat until restarted, so I used recovery mode to test that a) it still happened with that (yes) and b) to go back to the 470 drivers via the root terminal. For some reason, yesterday xscreensaver had a problem getting the right GLcontext. I noticed that the 510 drivers were available, so used Software & Updates's Additional Drivers to install those. Exactly the same issue as with the 495 drivers: the mouse cursor appears for a second, then disappears, and reappears, and.. until I reboot and go back to 470. I am using Ubuntu MATE 21.10 with a GeForce GTX 1050 Ti card. $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1960621/+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 1962346] [NEW] Ubuntu reboots instead of powering off if a software updates exists
Public bug reported: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages wayland-session ** Attachment added: "Снимок экрана от 2022-02-01 11-25-20.png" https://bugs.launchpad.net/bugs/1962346/+attachment/5563780/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202022-02-01%2011-25-20.png -- 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/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+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 1962170] Re: DEP8 failure with samba 4.15.5
I capture calls to smbd: PCOMMPIDPPID RET ARGS smbd 9605 9598 0 /usr/sbin/smbd -FS -s /tmp/adsys_smbd_3503406889/smbd.conf smbd 9699 9460 0 /usr/sbin/smbd -FS -s /tmp/adsys_smbd_3503406889/smbd.conf Ran them by hand: # /usr/sbin/smbd -FS -s /tmp/adsys_smbd_3503406889/smbd.conf Invalid option -FS: unknown option -F still exists, but not -S apparently. The manpage confirms -S is gone. It is mentioned in the context of -i, but -S itself is no longer there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1962170 Title: DEP8 failure with samba 4.15.5 Status in adsys package in Ubuntu: In Progress Bug description: The DEP8 tests of adsys started to fail[1] with my samba 4.15.5 upload. Some hints: ahasenack: it seems we can’t start our smbd local daemon to simulate Active Directory smb server ahasenack: yeah, I’m puzzled because on smbd start failure, we do print stderr (not stdout though): https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L16 https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L43 in particular you can see here how we start it: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L21 and the config template is at https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/internal/testutils/samba.go#L55 2022/02/24 03:13:59 Setup: smbd hasn’t started successfully that's here: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L129 you wait for the port to be open? which port is that, 445/tcp? we wait on the port to be opened, and this one is passed as a parameter, see the template. For the argument we pass in ad tests, once sec, looking 1446 https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/cmd/integration_tests/adsys_test.go#L47 you just need to run go test . in internal/ad/ the failure is as the pre-test setup 1. https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/a/adsys/20220224_031434_4d453@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1962170/+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 1959502] Re: U2F not connected in snap package
journalctl shows an apparmor issue: audit[9351]: AVC apparmor="DENIED" operation="open" profile="snap.thunderbird.thunderbird" name="/proc/sys/dev/i915/perf_stream_paranoid" pid=9351 comm=57656220436F6E74656E74 requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1959502 Title: U2F not connected in snap package Status in thunderbird package in Ubuntu: In Progress Bug description: U2F is not working for me when adding my gmail account to Thunderbird. I noticed that u2f-devices is not connected to the thunderbird snap. Running `snap connections thunderbird | grep u2f` returns nothing. Running `snap connect thunderbird:u2f-devices` returns: `error: snap "thunderbird" has no plug named "u2f-devices"` Because the apt version of Thunderbird works fine for me, I think this is just a simple matter of adding the u2f-devices connection to the snap package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1959502/+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 1962347] [NEW] firefox-trunk crashed with SIGSEGV in wl_display_read_events()
Public bug reported: After Installing Nvidia 510.54, The system may have some problems in detection of GPUs properly. No VAAPI after Nvidia installation, even if i set nvidia-drm.modeset=1 in grub and doing update-grub. The system contains Intel Integrated GPU and nvidia MX250 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: firefox-trunk 99.0~a1~hg20220224r608565-0ubuntu0.22.04.1~umd1 [origin: LP-PPA-ubuntu-mozilla-daily] Uname: Linux 5.15.25-xanmod1-tt x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: glados 1693 F pipewire-media- glados10070 F pulseaudio /dev/snd/pcmC0D0p: glados10070 F...m pulseaudio /dev/snd/seq:glados 1692 F pipewire BuildID: 20220224090316 CasperMD5CheckResult: pass Channel: nightly CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 22:25:56 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox-trunk/omni.ja:greprefs.js:365 DefaultProfilePrefSources: /usr/lib/firefox-trunk/defaults/pref/vendor-gre.js /usr/lib/firefox-trunk/defaults/pref/channel-prefs.js DefaultProfilePrefs: network.manage-offline-status: true (/usr/lib/firefox-trunk/defaults/pref/vendor-gre.js) DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/firefox-trunk/firefox-trunk ForcedLayersAccel: False InstallationDate: Installed on 2022-02-23 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.4 metric 100 ProcCmdline: /usr/lib/firefox-trunk/firefox-trunk 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-trunk/omni.ja:greprefs.js:365 Profile0PrefSources: /usr/lib/firefox-trunk/defaults/pref/vendor-gre.js /usr/lib/firefox-trunk/defaults/pref/channel-prefs.js prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=99.0a1/20220224090316 RunningIncompatibleAddons: False SegvAnalysis: Segfault happened at: 0x7f5b27582f48 :cmp 0x18(%rax),%r14d PC (0x7f5b27582f48) ok source "0x18(%rax)" (0x7f5b1da1ecf8) not located in a known VMA region (needed readable region)! destination "%r14d" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: firefox StacktraceTop: wl_display_read_events () from /lib/x86_64-linux-gnu/libwayland-client.so.0 wl_display_dispatch_queue () from /lib/x86_64-linux-gnu/libwayland-client.so.0 wl_display_roundtrip_queue () from /lib/x86_64-linux-gnu/libwayland-client.so.0 ?? () from /usr/lib/firefox-trunk/libxul.so ?? () from /usr/lib/firefox-trunk/libxul.so Title: firefox-trunk crashed with SIGSEGV in wl_display_read_events() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 09/03/2021 dmi.bios.release: 15.15 dmi.bios.vendor: Insyde dmi.bios.version: F.15 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 86E2 dmi.board.vendor: HP dmi.board.version: 95.36 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.36 dmi.modalias: dmi:bvnInsyde:bvrF.15:bd09/03/2021:br15.15:efr95.36:svnHP:pnHPPavilionLaptop15-cs3xxx:pvrType1ProductConfigId:rvnHP:rn86E2:rvr95.36:cvnHP:ct10:cvrChassisVersion:sku5SU52EA#BH4: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs3xxx dmi.product.sku: 5SU52EA#BH4 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP separator: ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash jammy need-amd64-retrace nightly-channel third-party-packages wayland-session ** Information type changed from Private to Public -- 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/1962347 Title: firefox-trunk crashed with SIGSEGV in wl_display_read_events() Status in firefox package in Ubuntu: New Bug description: After Installing Nvidia 510.54, The system may have some problems
[Desktop-packages] [Bug 1960621] Re: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers
** Tags added: impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1960621 Title: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers Status in marco package in Ubuntu: Fix Released Status in metacity package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in marco source package in Focal: In Progress Status in nvidia-graphics-drivers-510 source package in Focal: Confirmed Status in marco source package in Impish: In Progress Status in nvidia-graphics-drivers-510 source package in Impish: Confirmed Status in marco source package in Jammy: Fix Released Status in metacity source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Bug description: I have been using nvidia-graphics-drivers-470 for a while. In January, I tried the 495 drivers, but this resulted in failing to start the GUI when booting: the mouse cursor would appear, but then the screen would clear and the switch to graphics would be attempted again. This would repeat until restarted, so I used recovery mode to test that a) it still happened with that (yes) and b) to go back to the 470 drivers via the root terminal. For some reason, yesterday xscreensaver had a problem getting the right GLcontext. I noticed that the 510 drivers were available, so used Software & Updates's Additional Drivers to install those. Exactly the same issue as with the 495 drivers: the mouse cursor appears for a second, then disappears, and reappears, and.. until I reboot and go back to 470. I am using Ubuntu MATE 21.10 with a GeForce GTX 1050 Ti card. $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1960621/+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 1962347] Re: firefox-trunk crashed with SIGSEGV in wl_display_read_events()
** Tags removed: need-amd64-retrace -- 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/1962347 Title: firefox-trunk crashed with SIGSEGV in wl_display_read_events() Status in firefox package in Ubuntu: New Bug description: After Installing Nvidia 510.54, The system may have some problems in detection of GPUs properly. No VAAPI after Nvidia installation, even if i set nvidia-drm.modeset=1 in grub and doing update-grub. The system contains Intel Integrated GPU and nvidia MX250 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: firefox-trunk 99.0~a1~hg20220224r608565-0ubuntu0.22.04.1~umd1 [origin: LP-PPA-ubuntu-mozilla-daily] Uname: Linux 5.15.25-xanmod1-tt x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: glados 1693 F pipewire-media- glados10070 F pulseaudio /dev/snd/pcmC0D0p: glados10070 F...m pulseaudio /dev/snd/seq:glados 1692 F pipewire BuildID: 20220224090316 CasperMD5CheckResult: pass Channel: nightly CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 22:25:56 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox-trunk/omni.ja:greprefs.js:365 DefaultProfilePrefSources: /usr/lib/firefox-trunk/defaults/pref/vendor-gre.js /usr/lib/firefox-trunk/defaults/pref/channel-prefs.js DefaultProfilePrefs: network.manage-offline-status: true (/usr/lib/firefox-trunk/defaults/pref/vendor-gre.js) DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/firefox-trunk/firefox-trunk ForcedLayersAccel: False InstallationDate: Installed on 2022-02-23 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.4 metric 100 ProcCmdline: /usr/lib/firefox-trunk/firefox-trunk 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-trunk/omni.ja:greprefs.js:365 Profile0PrefSources: /usr/lib/firefox-trunk/defaults/pref/vendor-gre.js /usr/lib/firefox-trunk/defaults/pref/channel-prefs.js prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=99.0a1/20220224090316 RunningIncompatibleAddons: False SegvAnalysis: Segfault happened at: 0x7f5b27582f48 : cmp 0x18(%rax),%r14d PC (0x7f5b27582f48) ok source "0x18(%rax)" (0x7f5b1da1ecf8) not located in a known VMA region (needed readable region)! destination "%r14d" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: firefox StacktraceTop: wl_display_read_events () from /lib/x86_64-linux-gnu/libwayland-client.so.0 wl_display_dispatch_queue () from /lib/x86_64-linux-gnu/libwayland-client.so.0 wl_display_roundtrip_queue () from /lib/x86_64-linux-gnu/libwayland-client.so.0 ?? () from /usr/lib/firefox-trunk/libxul.so ?? () from /usr/lib/firefox-trunk/libxul.so Title: firefox-trunk crashed with SIGSEGV in wl_display_read_events() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 09/03/2021 dmi.bios.release: 15.15 dmi.bios.vendor: Insyde dmi.bios.version: F.15 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 86E2 dmi.board.vendor: HP dmi.board.version: 95.36 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.36 dmi.modalias: dmi:bvnInsyde:bvrF.15:bd09/03/2021:br15.15:efr95.36:svnHP:pnHPPavilionLaptop15-cs3xxx:pvrType1ProductConfigId:rvnHP:rn86E2:rvr95.36:cvnHP:ct10:cvrChassisVersion:sku5SU52EA#BH4: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs3xxx dmi.product.sku: 5SU52EA#BH4 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1962347/+su
[Desktop-packages] [Bug 1960621] Re: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers
It turns out that I may have misunderstood - the same thing happens for me when telling MATE Tweak that I want to use Compiz rather than Marco as my window manager. The switch to Compiz certainly happens (I am reminded of why I stopped using it..) and it is sticky between reboots. So either it's not just a Marco thing or some part of Marco is retained when using Compiz. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1960621 Title: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers Status in marco package in Ubuntu: Fix Released Status in metacity package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in marco source package in Focal: In Progress Status in nvidia-graphics-drivers-510 source package in Focal: Confirmed Status in marco source package in Impish: In Progress Status in nvidia-graphics-drivers-510 source package in Impish: Confirmed Status in marco source package in Jammy: Fix Released Status in metacity source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Bug description: I have been using nvidia-graphics-drivers-470 for a while. In January, I tried the 495 drivers, but this resulted in failing to start the GUI when booting: the mouse cursor would appear, but then the screen would clear and the switch to graphics would be attempted again. This would repeat until restarted, so I used recovery mode to test that a) it still happened with that (yes) and b) to go back to the 470 drivers via the root terminal. For some reason, yesterday xscreensaver had a problem getting the right GLcontext. I noticed that the 510 drivers were available, so used Software & Updates's Additional Drivers to install those. Exactly the same issue as with the 495 drivers: the mouse cursor appears for a second, then disappears, and reappears, and.. until I reboot and go back to 470. I am using Ubuntu MATE 21.10 with a GeForce GTX 1050 Ti card. $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1960621/+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 1962344] Re: fprintd fails to start through core-dump
I found the issue, I had this installed from the Dell repo for 20.04 LTS: libfprint-2-tod1-goodix more specifically: libfprint-2-tod1-goodix_0.0.6-0ubuntu1_somerville1_amd64.deb This worked great with 20.04 and the fprintd version in there, but apparently it breaks the current version. Seems I have to wait untill Dell/goodix releases a new version. I will close this one since the issue is not with fprintd itself. ** Changed in: fprintd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1962344 Title: fprintd fails to start through core-dump Status in fprintd package in Ubuntu: Invalid Bug description: some more info : feb 25 21:14:03 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Main process exited, code=dumped, status=11/SEGV ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit fprintd.service has exited. ░░ ░░ The process' exit code is 'dumped' and its exit status is 11. feb 25 21:14:03 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Failed with result 'core-dump'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit fprintd.service has entered the 'failed' state with result 'core-dump'. feb 25 21:14:03 ubuntu-inspiron-5482 systemd[1]: Failed to start Fingerprint Authentication Daemon. ░░ Subject: A start job for unit fprintd.service has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit fprintd.service has finished with a failure. ░░ ░░ The job identifier is 4596 and the job result is failed. ubuntu@ubuntu-inspiron-5482:~$ dpkg -l fprintd Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== ii fprintd1.94.2-1 amd64D-Bus daemon for fingerprint reader access if the fprintd package is installed and fprintd-enroll is run, it times out. That triggers a bug in gdm3 at login, where the user account is not visibe and one cannot login. I have a goodix fingerprint reader: Bus 001 Device 002: ID 27c6:538c Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: fprintd 1.94.2-1 Uname: Linux 5.12.19-051219-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 21:19:31 2022 InstallationDate: Installed on 2019-12-17 (801 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: fprintd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1962344/+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 1962349] [NEW] Bolt doesn't work with native USB4 hosts
Public bug reported: [Impact] * AMD Yellow Carp provides integrated USB4 host controllers * When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring" [Test Plan] * Plug in USB4 device or TBT3 to AMD Yellow Carp host * Ensure that PCI topology has populated * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0" * Try to run `boltctl enroll $UUID` [Where problems could occur] * Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt. * This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on Intel controllers for a long time. [Other Info] * This bug also occurs on Intel controllers from ICL, TGL or ALD, but in many cases they are automatically authorized to an iommu DMA policy. * It is fixed in bolt 0.9.1 or later release. * To solve the SRU, will backport 0.9.1 release from Impish. ** Affects: bolt (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: bolt (Ubuntu Focal) Importance: Undecided Status: New ** Affects: bolt (Ubuntu Impish) Importance: Undecided Status: Fix Released ** Affects: bolt (Ubuntu Jammy) Importance: Undecided Status: Fix Released ** Also affects: bolt (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: bolt (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: bolt (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: bolt (Ubuntu Jammy) Status: New => Fix Released ** Description changed: [Impact] - * AMD Yellow Carp provides integrated USB4 host controllers - * When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring" + * AMD Yellow Carp provides integrated USB4 host controllers + * When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring" [Test Plan] - * Plug in USB4 device or TBT3 to AMD Yellow Carp host - * Ensure that PCI topology has populated - * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0" - * Try to run `boltctl enroll $UUID` + * Plug in USB4 device or TBT3 to AMD Yellow Carp host + * Ensure that PCI topology has populated + * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0" + * Try to run `boltctl enroll $UUID` [Where problems could occur] - * Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt. - * This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on Intel controllers for a long time. + * Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt. + * This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on Intel controllers for a long time. [Other Info] - * This bug also occurs on Intel controllers from ICL, TGL or ALD, but in many cases they are automatically authorized to an iommu DMA policy. - * It is fixed in bolt 0.9.1 or later release. - * To solve the SRU, will backport 0.9.2 release from Jammy. + * This bug also occurs on Intel controllers from ICL, TGL or ALD, but in many cases they are automatically authorized to an iommu DMA policy. + * It is fixed in bolt 0.9.1 or later release. + * To solve the SRU, will backport 0.9.1 release from Impish. ** Changed in: bolt (Ubuntu Impish) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bolt in Ubuntu. https://bugs.launchpad.net/bugs/1962349 Title: Bolt doesn't work with native USB4 hosts Status in bolt package in Ubuntu: Fix Released Status in bolt source package in Focal: New Status in bolt source package in Impish: Fix Released Status in bolt source package in Jammy: Fix Released Bug description: [Impact] * AMD Yellow Carp provides integrated USB4 host controllers * When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring" [Test Plan] * Plug in USB4 device or TBT3 to AMD Yellow Carp host * Ensure that PCI topology has populated * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0" * Try to run `boltctl enroll $UUID` [Where problems could occur] * Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt. * This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on I
[Desktop-packages] [Bug 1962237] Re: blue tooth/wireless mouse not working
never mind. Batteries replaced work wonders. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1962237 Title: blue tooth/wireless mouse not working Status in xdiagnose package in Ubuntu: New Bug description: The mouse can occasionally be made to work by going back through settings, etc. but then very shortly stops again. I recently updated the system and had to interrupt the update as it was in an infinite loop while install was running. I am also running a bitcoin node that is not remembering where I was on the last run of bitcoin core. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1962237/+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 1962351] [NEW] login screen shown on inactive monitor
Public bug reported: My laptop is docked with the lid closed and connected to 2 external monitors. After upgrading a bunch of packages from jammy in the last 24 hours I notice that when logging in, both of my external monitors just show the purple background whilst the login dialog was actually displayed on the closed lid of my laptop. Wasn't sure if this should be filed against some other package as it doesn't look like gnome-shell or gdm3 have changed lately (I only see gnome-shell-extension-appindicator and gnome-shell-extension-ubuntu-dock in my apt history that could be related...) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 41.3-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 09:52:39 2022 InstallationDate: Installed on 2021-08-03 (206 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-01-14 (42 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1962351 Title: login screen shown on inactive monitor Status in gdm3 package in Ubuntu: New Bug description: My laptop is docked with the lid closed and connected to 2 external monitors. After upgrading a bunch of packages from jammy in the last 24 hours I notice that when logging in, both of my external monitors just show the purple background whilst the login dialog was actually displayed on the closed lid of my laptop. Wasn't sure if this should be filed against some other package as it doesn't look like gnome-shell or gdm3 have changed lately (I only see gnome-shell-extension-appindicator and gnome-shell-extension-ubuntu- dock in my apt history that could be related...) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 41.3-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 09:52:39 2022 InstallationDate: Installed on 2021-08-03 (206 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-01-14 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1962351/+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 1955745] Re: Sending file to GCP using SSH window from Google Cloud Platform freezes and corrupts both local and remote systems
I did this test twice now, using Chromium 98.0.4758.102 snap, firstly with a VM and then with the host system. Gladly, everything worked correctly: no system crash on the host and the file was uploaded successfully to the GCP instance (sha256 matched). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1955745 Title: Sending file to GCP using SSH window from Google Cloud Platform freezes and corrupts both local and remote systems Status in chromium-browser package in Ubuntu: Incomplete Bug description: I started setting a Factorio server on Google Cloud Platform. I opened a SSH session using the button on the Google Cloud Platform page, the page opened, the session started and then I chose the save file to upload (choosing the gear on top right and then upload file). It's a 64 MB save. After 2% upload, the local system freezes entirely. Nothing responds, even REISUB don't work any more. After forcefully shutting down the local computer, on the next boot, the local computer's root file system is corrupted. On the remote machine, the file was partially send but it was also corrupted. ProblemType: Bug DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-13.13-generic 5.15.5 Uname: Linux 5.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sat Dec 25 17:41:41 2021 InstallationDate: Installed on 2017-06-13 (1655 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Snap: chromium 96.0.4664.110 (latest/candidate) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to jammy on 2019-12-22 (733 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1955745/+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 1953376] Re: Severe graphical glitches when restoring the window
Recently, I have no longer observed this problem, and after Firefox updated from deb to snap, it hasn't reappeared, so it seems fixed to me now. -- 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/1953376 Title: Severe graphical glitches when restoring the window Status in firefox package in Ubuntu: Incomplete Bug description: When restoring the Firefox window, sometimes graphical glitches occur before the window content appears properly. Sometimes it is just a tiny bit of the previous content on the Firefox window that was rendered correctly, sometimes it's a severely corrupted screen. The attached screenshot shows the second case. Steps to reproduce: 1) Have a Firefox window open; 2) Minimize all Firefox windows; 3) Try to restore and minimize one window repeatedly; 4) Notice graphical corruption. I still haven't figured out what is causing this issue, but sometimes it will stop happening, and later it starts again. It seems to be retaining some content that was open before. I'm reporting this against Firefox because it is the only program where I have noticed this particular problem, but this may a problem with something else (it could be xfwm4, for example). While the attached files have more details, here are some system specifications. OS: Xubuntu 22.04; CPU: Intel Core i3-6100U; GPU: Intel HD Graphics 520; Mesa: 21.2.6; Xorg: intel 2.99.917; RAM: 20 GB. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 95.0+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-13.13-generic 5.15.5 Uname: Linux 5.15.0-13-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario2024 F pipewire usuario2025 F wireplumber /dev/snd/pcmC0D0p: usuario2024 F...m pipewire /dev/snd/seq:usuario2024 F pipewire BuildID: 20211129150630 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: XFCE Date: Mon Dec 6 13:44:43 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:363 DefaultProfilePrefSources: 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 InstallationDate: Installed on 2017-06-13 (1636 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wg0 scope link metric 1000 172.16.0.0/24 dev wg0 proto kernel scope link src 172.16.0.5 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.50 metric 600 MostRecentCrashID: bp-503ae7fd-820e-46e7-b595-808330180209 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:363 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=76.0a1/20200312215313 (Out of date) Profile0 (Default) - LastVersion=95.0/20211129150630 (In use) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-503ae7fd-820e-46e7-b595-808330180209 UpgradeStatus: Upgraded to jammy on 2019-12-22 (714 days ago) dmi.bios.date: 08/09/2018 dmi.bios.release: 1.45 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.ec.firmware.release: 1.45 dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:br1.45:efr1.45:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:skuLENOVO_MT_80UG_BU_idea_FM_Lenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.ve
[Desktop-packages] [Bug 1959995] Re: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46)
Same issue here. Two systems running Mint Mate 20.3. System #1: GeForce GTX 1050 Ti System #2: RTX A4000 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1959995 Title: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46) Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Triaged Status in xorg-server source package in Focal: Confirmed Status in xorg-server source package in Impish: Confirmed Bug description: This bug causes xserver to crash when using newer Nvidia drivers (NVIDIA 495.46+) with Optimus. It's apparently triggered when using the MATE desktop environment. It has been noticed on xorg-server-21.1, but it's likely affecting version 1.20.13 as well. It has been fixed already, but could you please backport the fix? Patch that fixes it is here: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/841/diffs?commit_id=22d5818851967408bb7c903cb345b7ca8766094c The bug report at freedesktop.org is here: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275 Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1959995/+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 1962357] [NEW] gnome-shell takes a lot of ram
Public bug reported: gnome-shell takes a lot of ram ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-64.72-generic 5.8.18 Uname: Linux 5.8.0-64-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 10:41:29 2022 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-26 (640 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1962357 Title: gnome-shell takes a lot of ram Status in gnome-shell package in Ubuntu: New Bug description: gnome-shell takes a lot of ram ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-64.72-generic 5.8.18 Uname: Linux 5.8.0-64-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 10:41:29 2022 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-26 (640 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962357/+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
