[Desktop-packages] [Bug 1986450] Re: Visual artifact 1px vertical white line right side of the wallpaper
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- 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/1986450 Title: Visual artifact 1px vertical white line right side of the wallpaper Status in gnome-shell package in Ubuntu: New Bug description: After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that there is a 1px wide vertical white line on the desktop that appears whenever an application has focus. It is on the right side of the monitor, covering the background wallpaper but not the menu. Workaround: in Displays, change scale to something else than 100% and then change back to 100%. That white vertical line will stay at the former 100% window size location until the Settings window is closed. It disappears when the Settings is closed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-27 (1570 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: gnome-shell 42.2-0ubuntu0.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: wayland-session jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1986450/+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 1872475] Re: Wine programs in the dock don't get the orange circle when executed, but get duplicated at the bottom of the dock instead.
This is a classic bug, the point is that the developer did not add the parameter StartupWMClass in .desktop file. Basically there are 3 ways to solve the problem. 1) Download snap app version 2) Create your custom shortcut (where do you add StartupWMClass) 3)Tell the developer to add StartupWMClass. Also watch this video: https://www.youtube.com/watch?v=xZ_M3Q-U-J0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1872475 Title: Wine programs in the dock don't get the orange circle when executed, but get duplicated at the bottom of the dock instead. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: I really don't know whether to file this bug report with wine or with gnome-shell, but it used to work, so I suspect it is a gnome-shell thing. How to duplicate it: -Install a wine program, and put its icon in the gnome dock. -Click on the wine program icon in the dock. -An identical icon appears at the bottom of your list of running programs, with an orange dot, but the original one has no orange dot to indicate it is running. What should happen: -No duplicate icon should be displayed at the bottom of your dock, and the orange dot should appear beside the original icon. See my screenshot included. The icon to look at is the LTSpice one, 11 from the top, and then find it also near the bottom of the dock with an orange dot. Thanks for your good work! Rob ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 13 07:30:50 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-04-19 (360 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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-extension-ubuntu-dock/+bug/1872475/+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 1980408] Re: Update glib to 2.72.3
Hello Jeremy, or anyone else affected, Accepted glib2.0 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.72.3-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: glib2.0 (Ubuntu Jammy) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1980408 Title: Update glib to 2.72.3 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 2.72 series https://gitlab.gnome.org/GNOME/glib/-/blob/2.72.3/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopgktest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1980408/+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 1986750] [NEW] gdm-smartcard pam config denies legitimate users, prompts for username
Public bug reported: I'm encountering three issues when using a smartcard to login into gdm3. The root of the issues is gdm-smartcard-sssd-exclusive PAM configuration for authentication: 1. The gdm-smartcard denies access to legitimate users as no success control value is configured. 2. Because pam_succeed_if is first in the authentication stack, it will invoke the pam_get_user when the user is NULL. As gdm3 doesn't supply a user when invoking pam_start, pam_get_user invokes a conversation, causing gdm3 to collect a username. 3. If a Username of '' (empty string) is inputed, pam_succeed_if will succeed, assuming a success=ok control value. If configured with allow- missing-name, pam_sss will use the certificate on a smartcard to identify the user. If so configured, this may map to root, which defeats the pam_succeed_if.so check. I'm attaching a pam config that seems to addresses these issues by reordering the pam stack for authentication. By performing pam_sss before pam_succeed_if, pam_sss uses the certificate when the supplied user is NULL or the empty string. GDM3 only prompts for the smartcard PIN. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Aug 16 20:39:44 2022 InstallationDate: Installed on 2022-08-12 (5 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "gdm-smartcard pam config" https://bugs.launchpad.net/bugs/1986750/+attachment/5609220/+files/gdm3.gdm-smartcard-sssd-exclusive.pam -- 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/1986750 Title: gdm-smartcard pam config denies legitimate users, prompts for username Status in gdm3 package in Ubuntu: New Bug description: I'm encountering three issues when using a smartcard to login into gdm3. The root of the issues is gdm-smartcard-sssd-exclusive PAM configuration for authentication: 1. The gdm-smartcard denies access to legitimate users as no success control value is configured. 2. Because pam_succeed_if is first in the authentication stack, it will invoke the pam_get_user when the user is NULL. As gdm3 doesn't supply a user when invoking pam_start, pam_get_user invokes a conversation, causing gdm3 to collect a username. 3. If a Username of '' (empty string) is inputed, pam_succeed_if will succeed, assuming a success=ok control value. If configured with allow-missing-name, pam_sss will use the certificate on a smartcard to identify the user. If so configured, this may map to root, which defeats the pam_succeed_if.so check. I'm attaching a pam config that seems to addresses these issues by reordering the pam stack for authentication. By performing pam_sss before pam_succeed_if, pam_sss uses the certificate when the supplied user is NULL or the empty string. GDM3 only prompts for the smartcard PIN. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Aug 16 20:39:44 2022 InstallationDate: Installed on 2022-08-12 (5 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1986750/+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 1986450] Re: Visual artifact 1px vertical white line right side of the wallpaper
In the past I had seen a 1px gap down the right side of the wallpaper on Intel, but I think that was only during desktop zoom and I can't reproduce it today. Whatever the cause was might still be present and might only be manifesting with AMD graphics. Just a theory. -- 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/1986450 Title: Visual artifact 1px vertical white line right side of the wallpaper Status in gnome-shell package in Ubuntu: Incomplete Bug description: After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that there is a 1px wide vertical white line on the desktop that appears whenever an application has focus. It is on the right side of the monitor, covering the background wallpaper but not the menu. Workaround: in Displays, change scale to something else than 100% and then change back to 100%. That white vertical line will stay at the former 100% window size location until the Settings window is closed. It disappears when the Settings is closed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-27 (1570 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: gnome-shell 42.2-0ubuntu0.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: wayland-session jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1986450/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1784977 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: New Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 1986583] Re: Screen after some time get shifted and starts to overlap
That config section you mention needs to be removed entirely because the "intel" driver is buggy, unsupported and was only designed to handle much older Intel GPUs. Sadly that does mean you lose the "TearFree" option. It has been requested in the new driver for some time (https://gitlab.freedesktop.org/xorg/xserver/-/issues/244) but there aren't many Xorg developers left these days... Wayland sessions are always tear-free already. I would suggest trying a Wayland session with desktop sharing enabled in settings, which would use RDP instead of VNC. ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #244 https://gitlab.freedesktop.org/xorg/xserver/-/issues/244 ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1986583 Title: Screen after some time get shifted and starts to overlap Status in xserver-xorg-video-intel package in Ubuntu: Won't Fix Bug description: problem resembles a lot this one: https://askubuntu.com/questions/07/ubuntu-desktop-shifted-to-right "I am encountering a strange problem, my whole desktop has shifted to right." But different in a way, that when pc is started it shows everything just fine. But when computer is powered on a few days straight, display gets shifted. Some times just cca 1/4 of screen, sometimes it shifts over half of the screen. Computer should be used to run 8hours straight (it is intended for customer) When i switch from graphic display to tty (ctrl+alt+num) and back, display gets "restarted" and problem is fixed. But it is just temporary. Restart fixes it also. Last time i encountered this behavior today between 17-18hour. But have no idea what or where to look for. yes, and when one connects to display over X11 or teamviewer screen appears to be okay, so one will notice this problem if using pc remotely 1) lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 2) xorg: Installed: 1:7.7+23ubuntu2 Candidate: 1:7.7+23ubuntu2 Version table: *** 1:7.7+23ubuntu2 500 500 http://cz.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 3) expect that display will stay where it is on the start of computer 4) display gets shifted to some distance from unknown reason (Maybe x11vnc or teamviewer usage or something). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 15 22:27:55 2022 DistUpgraded: 2022-08-02 14:36:41,704 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2015] InstallationDate: Installed on 2022-02-17 (179 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 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=582fb3cc-8ef6-460b-b9ae-a16f81c604a7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-08-02 (13 days ago) dmi.bios.date: 10/07/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GSKU0504.V54 dmi.board.asset.tag: Default string dmi.board.name: SKYBAY dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGSKU0504.V54:bd10/07/2021:br5.12:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1
[Desktop-packages] [Bug 1970148] Re: Brave & Chrome browsers freezes on download and print to pdf
I can confirm #29 -- 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/1970148 Title: Brave & Chrome browsers freezes on download and print to pdf Status in chromium-browser package in Ubuntu: Invalid Bug description: Whenever any file is downloaded, the browser will freeze. Download files, from any page does not work. Same issue with Firefox. Similarly, the browser will freeze when a page is printed to pdf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970148/+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 1984233] Re: Please remove nautilus extensions incompatible with Nautilus 43
** Also affects: nautilus-share (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/1984233 Title: Please remove nautilus extensions incompatible with Nautilus 43 Status in eiciel package in Ubuntu: Fix Released Status in folder-color package in Ubuntu: Fix Released Status in nautilus-dropbox package in Ubuntu: Fix Released Status in nautilus-filename-repairer package in Ubuntu: Fix Released Status in nautilus-ideviceinfo package in Ubuntu: Fix Released Status in nautilus-image-converter package in Ubuntu: Fix Released Status in nautilus-share package in Ubuntu: New Status in nautilus-wipe package in Ubuntu: Fix Released Status in seahorse-nautilus package in Ubuntu: Fix Released Bug description: nautilus python 4.0~alpha is a major API update along with nautilus 43 which had a major API update. Please remove these extensions since they are currently incompatible with the Nautilus and nautilus-python versions we are including in Kinetic - eiciel -- Needs to be ported from GTK3 Debian maintainer thinks the package is not worth keeping without the extension https://salsa.debian.org/debian/eiciel/-/merge_requests/2 - folder-color -- Needs to be ported from GTK3 https://github.com/costales/folder-color/issues/17 Ubuntu-specific package - nautilus-dropbox -- Needs to be ported from GTK3 https://github.com/dropbox/nautilus-dropbox/issues/101 - nautilus-filename-repairer -- Needs to be ported from GTK3 - nautilus-ideviceinfo -- Needs to be ported from GTK3 Ubuntu-specific package - nautilus-image-converter -- Needs to be ported from GTK3 Debian removal bug filed. Unmaintained in Debian or upstream - nautilus-wipe -- Needs to be ported from GTK3 - seahorse-nautilus -- Needs to be ported from GTK3 Transition tracker -- We are going to try to fix several of the other affected source packages (not listed above) to either drop their Nautilus extension or port them to work with Nautilus 43. https://people.canonical.com/~ubuntu-archive/transitions/html/auto- nautilus.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eiciel/+bug/1984233/+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 1984233] Re: Please remove nautilus extensions incompatible with Nautilus 43
** No longer affects: nautilus (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1984233 Title: Please remove nautilus extensions incompatible with Nautilus 43 Status in eiciel package in Ubuntu: Fix Released Status in folder-color package in Ubuntu: Fix Released Status in nautilus-dropbox package in Ubuntu: Fix Released Status in nautilus-filename-repairer package in Ubuntu: Fix Released Status in nautilus-ideviceinfo package in Ubuntu: Fix Released Status in nautilus-image-converter package in Ubuntu: Fix Released Status in nautilus-wipe package in Ubuntu: Fix Released Status in seahorse-nautilus package in Ubuntu: Fix Released Bug description: nautilus python 4.0~alpha is a major API update along with nautilus 43 which had a major API update. Please remove these extensions since they are currently incompatible with the Nautilus and nautilus-python versions we are including in Kinetic - eiciel -- Needs to be ported from GTK3 Debian maintainer thinks the package is not worth keeping without the extension https://salsa.debian.org/debian/eiciel/-/merge_requests/2 - folder-color -- Needs to be ported from GTK3 https://github.com/costales/folder-color/issues/17 Ubuntu-specific package - nautilus-dropbox -- Needs to be ported from GTK3 https://github.com/dropbox/nautilus-dropbox/issues/101 - nautilus-filename-repairer -- Needs to be ported from GTK3 - nautilus-ideviceinfo -- Needs to be ported from GTK3 Ubuntu-specific package - nautilus-image-converter -- Needs to be ported from GTK3 Debian removal bug filed. Unmaintained in Debian or upstream - nautilus-wipe -- Needs to be ported from GTK3 - seahorse-nautilus -- Needs to be ported from GTK3 Transition tracker -- We are going to try to fix several of the other affected source packages (not listed above) to either drop their Nautilus extension or port them to work with Nautilus 43. https://people.canonical.com/~ubuntu-archive/transitions/html/auto- nautilus.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eiciel/+bug/1984233/+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 1984233] Re: Please remove nautilus extensions incompatible with Nautilus 43
Removing packages from kinetic: eiciel 0.9.13.1-1 in kinetic eiciel 0.9.13.1-1 in kinetic amd64 eiciel 0.9.13.1-1 in kinetic arm64 eiciel 0.9.13.1-1 in kinetic armhf eiciel 0.9.13.1-1 in kinetic ppc64el eiciel 0.9.13.1-1 in kinetic riscv64 eiciel 0.9.13.1-1 in kinetic s390x Comment: Incompatible with new nautilus based on GTK4 and blocks library transition; LP: #1984233 1 package successfully removed. ** Changed in: eiciel (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1984233 Title: Please remove nautilus extensions incompatible with Nautilus 43 Status in eiciel package in Ubuntu: Fix Released Status in folder-color package in Ubuntu: Fix Released Status in nautilus-dropbox package in Ubuntu: Fix Released Status in nautilus-filename-repairer package in Ubuntu: Fix Released Status in nautilus-ideviceinfo package in Ubuntu: Fix Released Status in nautilus-image-converter package in Ubuntu: Fix Released Status in nautilus-wipe package in Ubuntu: Fix Released Status in seahorse-nautilus package in Ubuntu: Fix Released Bug description: nautilus python 4.0~alpha is a major API update along with nautilus 43 which had a major API update. Please remove these extensions since they are currently incompatible with the Nautilus and nautilus-python versions we are including in Kinetic - eiciel -- Needs to be ported from GTK3 Debian maintainer thinks the package is not worth keeping without the extension https://salsa.debian.org/debian/eiciel/-/merge_requests/2 - folder-color -- Needs to be ported from GTK3 https://github.com/costales/folder-color/issues/17 Ubuntu-specific package - nautilus-dropbox -- Needs to be ported from GTK3 https://github.com/dropbox/nautilus-dropbox/issues/101 - nautilus-filename-repairer -- Needs to be ported from GTK3 - nautilus-ideviceinfo -- Needs to be ported from GTK3 Ubuntu-specific package - nautilus-image-converter -- Needs to be ported from GTK3 Debian removal bug filed. Unmaintained in Debian or upstream - nautilus-wipe -- Needs to be ported from GTK3 - seahorse-nautilus -- Needs to be ported from GTK3 Transition tracker -- We are going to try to fix several of the other affected source packages (not listed above) to either drop their Nautilus extension or port them to work with Nautilus 43. https://people.canonical.com/~ubuntu-archive/transitions/html/auto- nautilus.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eiciel/+bug/1984233/+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 1984233] Re: Please remove nautilus extensions incompatible with Nautilus 43
Removing packages from kinetic: nautilus-wipe 0.3.1-2 in kinetic nautilus-wipe 0.3.1-2 in kinetic amd64 nautilus-wipe 0.3.1-2 in kinetic arm64 nautilus-wipe 0.3.1-2 in kinetic armhf nautilus-wipe 0.3.1-2 in kinetic ppc64el nautilus-wipe 0.3.1-2 in kinetic riscv64 nautilus-wipe 0.3.1-2 in kinetic s390x Comment: Incompatible with new nautilus based on GTK4 and blocks library transition; LP: #1984233 1 package successfully removed. ** Changed in: nautilus-wipe (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1984233 Title: Please remove nautilus extensions incompatible with Nautilus 43 Status in eiciel package in Ubuntu: Fix Released Status in folder-color package in Ubuntu: Fix Released Status in nautilus-dropbox package in Ubuntu: Fix Released Status in nautilus-filename-repairer package in Ubuntu: Fix Released Status in nautilus-ideviceinfo package in Ubuntu: Fix Released Status in nautilus-image-converter package in Ubuntu: Fix Released Status in nautilus-wipe package in Ubuntu: Fix Released Status in seahorse-nautilus package in Ubuntu: Fix Released Bug description: nautilus python 4.0~alpha is a major API update along with nautilus 43 which had a major API update. Please remove these extensions since they are currently incompatible with the Nautilus and nautilus-python versions we are including in Kinetic - eiciel -- Needs to be ported from GTK3 Debian maintainer thinks the package is not worth keeping without the extension https://salsa.debian.org/debian/eiciel/-/merge_requests/2 - folder-color -- Needs to be ported from GTK3 https://github.com/costales/folder-color/issues/17 Ubuntu-specific package - nautilus-dropbox -- Needs to be ported from GTK3 https://github.com/dropbox/nautilus-dropbox/issues/101 - nautilus-filename-repairer -- Needs to be ported from GTK3 - nautilus-ideviceinfo -- Needs to be ported from GTK3 Ubuntu-specific package - nautilus-image-converter -- Needs to be ported from GTK3 Debian removal bug filed. Unmaintained in Debian or upstream - nautilus-wipe -- Needs to be ported from GTK3 - seahorse-nautilus -- Needs to be ported from GTK3 Transition tracker -- We are going to try to fix several of the other affected source packages (not listed above) to either drop their Nautilus extension or port them to work with Nautilus 43. https://people.canonical.com/~ubuntu-archive/transitions/html/auto- nautilus.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eiciel/+bug/1984233/+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 1984233] Re: Please remove nautilus extensions incompatible with Nautilus 43
Removing packages from kinetic: seahorse-nautilus 3.11.92-4 in kinetic seahorse-nautilus 3.11.92-4 in kinetic amd64 seahorse-nautilus 3.11.92-4 in kinetic arm64 seahorse-nautilus 3.11.92-4 in kinetic armhf seahorse-nautilus 3.11.92-4 in kinetic ppc64el seahorse-nautilus 3.11.92-4 in kinetic riscv64 seahorse-nautilus 3.11.92-4 in kinetic s390x Comment: Incompatible with new nautilus based on GTK4 and blocks library transition; LP: #1984233 1 package successfully removed. ** Changed in: seahorse-nautilus (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1984233 Title: Please remove nautilus extensions incompatible with Nautilus 43 Status in eiciel package in Ubuntu: Fix Released Status in folder-color package in Ubuntu: Fix Released Status in nautilus-dropbox package in Ubuntu: Fix Released Status in nautilus-filename-repairer package in Ubuntu: Fix Released Status in nautilus-ideviceinfo package in Ubuntu: Fix Released Status in nautilus-image-converter package in Ubuntu: Fix Released Status in nautilus-wipe package in Ubuntu: Fix Released Status in seahorse-nautilus package in Ubuntu: Fix Released Bug description: nautilus python 4.0~alpha is a major API update along with nautilus 43 which had a major API update. Please remove these extensions since they are currently incompatible with the Nautilus and nautilus-python versions we are including in Kinetic - eiciel -- Needs to be ported from GTK3 Debian maintainer thinks the package is not worth keeping without the extension https://salsa.debian.org/debian/eiciel/-/merge_requests/2 - folder-color -- Needs to be ported from GTK3 https://github.com/costales/folder-color/issues/17 Ubuntu-specific package - nautilus-dropbox -- Needs to be ported from GTK3 https://github.com/dropbox/nautilus-dropbox/issues/101 - nautilus-filename-repairer -- Needs to be ported from GTK3 - nautilus-ideviceinfo -- Needs to be ported from GTK3 Ubuntu-specific package - nautilus-image-converter -- Needs to be ported from GTK3 Debian removal bug filed. Unmaintained in Debian or upstream - nautilus-wipe -- Needs to be ported from GTK3 - seahorse-nautilus -- Needs to be ported from GTK3 Transition tracker -- We are going to try to fix several of the other affected source packages (not listed above) to either drop their Nautilus extension or port them to work with Nautilus 43. https://people.canonical.com/~ubuntu-archive/transitions/html/auto- nautilus.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eiciel/+bug/1984233/+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 1984233] Re: Please remove nautilus extensions incompatible with Nautilus 43
Removing packages from kinetic: nautilus-image-converter 0.3.1~git20110416-2 in kinetic nautilus-image-converter 0.3.1~git20110416-2 in kinetic amd64 nautilus-image-converter 0.3.1~git20110416-2 in kinetic arm64 nautilus-image-converter 0.3.1~git20110416-2 in kinetic armhf nautilus-image-converter 0.3.1~git20110416-2 in kinetic ppc64el nautilus-image-converter 0.3.1~git20110416-2 in kinetic riscv64 nautilus-image-converter 0.3.1~git20110416-2 in kinetic s390x Comment: Incompatible with new nautilus based on GTK4 and blocks library transition; LP: #1984233 1 package successfully removed. ** Changed in: nautilus-image-converter (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1984233 Title: Please remove nautilus extensions incompatible with Nautilus 43 Status in eiciel package in Ubuntu: Fix Released Status in folder-color package in Ubuntu: Fix Released Status in nautilus-dropbox package in Ubuntu: Fix Released Status in nautilus-filename-repairer package in Ubuntu: Fix Released Status in nautilus-ideviceinfo package in Ubuntu: Fix Released Status in nautilus-image-converter package in Ubuntu: Fix Released Status in nautilus-wipe package in Ubuntu: Fix Released Status in seahorse-nautilus package in Ubuntu: Fix Released Bug description: nautilus python 4.0~alpha is a major API update along with nautilus 43 which had a major API update. Please remove these extensions since they are currently incompatible with the Nautilus and nautilus-python versions we are including in Kinetic - eiciel -- Needs to be ported from GTK3 Debian maintainer thinks the package is not worth keeping without the extension https://salsa.debian.org/debian/eiciel/-/merge_requests/2 - folder-color -- Needs to be ported from GTK3 https://github.com/costales/folder-color/issues/17 Ubuntu-specific package - nautilus-dropbox -- Needs to be ported from GTK3 https://github.com/dropbox/nautilus-dropbox/issues/101 - nautilus-filename-repairer -- Needs to be ported from GTK3 - nautilus-ideviceinfo -- Needs to be ported from GTK3 Ubuntu-specific package - nautilus-image-converter -- Needs to be ported from GTK3 Debian removal bug filed. Unmaintained in Debian or upstream - nautilus-wipe -- Needs to be ported from GTK3 - seahorse-nautilus -- Needs to be ported from GTK3 Transition tracker -- We are going to try to fix several of the other affected source packages (not listed above) to either drop their Nautilus extension or port them to work with Nautilus 43. https://people.canonical.com/~ubuntu-archive/transitions/html/auto- nautilus.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eiciel/+bug/1984233/+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 1984233] Re: Please remove nautilus extensions incompatible with Nautilus 43
Removing packages from kinetic: nautilus-ideviceinfo 0.1.0-0ubuntu14 in kinetic nautilus-ideviceinfo 0.1.0-0ubuntu14 in kinetic amd64 nautilus-ideviceinfo 0.1.0-0ubuntu14 in kinetic arm64 nautilus-ideviceinfo 0.1.0-0ubuntu14 in kinetic armhf nautilus-ideviceinfo 0.1.0-0ubuntu14 in kinetic ppc64el nautilus-ideviceinfo 0.1.0-0ubuntu14 in kinetic riscv64 nautilus-ideviceinfo 0.1.0-0ubuntu14 in kinetic s390x Comment: Incompatible with new nautilus based on GTK4 and blocks library transition; LP: #1984233 1 package successfully removed. ** Changed in: nautilus-ideviceinfo (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1984233 Title: Please remove nautilus extensions incompatible with Nautilus 43 Status in eiciel package in Ubuntu: Fix Released Status in folder-color package in Ubuntu: Fix Released Status in nautilus-dropbox package in Ubuntu: Fix Released Status in nautilus-filename-repairer package in Ubuntu: Fix Released Status in nautilus-ideviceinfo package in Ubuntu: Fix Released Status in nautilus-image-converter package in Ubuntu: Fix Released Status in nautilus-wipe package in Ubuntu: Fix Released Status in seahorse-nautilus package in Ubuntu: Fix Released Bug description: nautilus python 4.0~alpha is a major API update along with nautilus 43 which had a major API update. Please remove these extensions since they are currently incompatible with the Nautilus and nautilus-python versions we are including in Kinetic - eiciel -- Needs to be ported from GTK3 Debian maintainer thinks the package is not worth keeping without the extension https://salsa.debian.org/debian/eiciel/-/merge_requests/2 - folder-color -- Needs to be ported from GTK3 https://github.com/costales/folder-color/issues/17 Ubuntu-specific package - nautilus-dropbox -- Needs to be ported from GTK3 https://github.com/dropbox/nautilus-dropbox/issues/101 - nautilus-filename-repairer -- Needs to be ported from GTK3 - nautilus-ideviceinfo -- Needs to be ported from GTK3 Ubuntu-specific package - nautilus-image-converter -- Needs to be ported from GTK3 Debian removal bug filed. Unmaintained in Debian or upstream - nautilus-wipe -- Needs to be ported from GTK3 - seahorse-nautilus -- Needs to be ported from GTK3 Transition tracker -- We are going to try to fix several of the other affected source packages (not listed above) to either drop their Nautilus extension or port them to work with Nautilus 43. https://people.canonical.com/~ubuntu-archive/transitions/html/auto- nautilus.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eiciel/+bug/1984233/+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 1984233] Re: Please remove nautilus extensions incompatible with Nautilus 43
Removing packages from kinetic: nautilus-filename-repairer 0.2.0-3 in kinetic nautilus-filename-repairer 0.2.0-3 in kinetic amd64 nautilus-filename-repairer 0.2.0-3 in kinetic arm64 nautilus-filename-repairer 0.2.0-3 in kinetic armhf nautilus-filename-repairer 0.2.0-3 in kinetic ppc64el nautilus-filename-repairer 0.2.0-3 in kinetic riscv64 nautilus-filename-repairer 0.2.0-3 in kinetic s390x Comment: Incompatible with new nautilus based on GTK4 and blocks library transition; LP: #1984233 1 package successfully removed. ** Changed in: nautilus-filename-repairer (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1984233 Title: Please remove nautilus extensions incompatible with Nautilus 43 Status in eiciel package in Ubuntu: Fix Released Status in folder-color package in Ubuntu: Fix Released Status in nautilus-dropbox package in Ubuntu: Fix Released Status in nautilus-filename-repairer package in Ubuntu: Fix Released Status in nautilus-ideviceinfo package in Ubuntu: Fix Released Status in nautilus-image-converter package in Ubuntu: Fix Released Status in nautilus-wipe package in Ubuntu: Fix Released Status in seahorse-nautilus package in Ubuntu: Fix Released Bug description: nautilus python 4.0~alpha is a major API update along with nautilus 43 which had a major API update. Please remove these extensions since they are currently incompatible with the Nautilus and nautilus-python versions we are including in Kinetic - eiciel -- Needs to be ported from GTK3 Debian maintainer thinks the package is not worth keeping without the extension https://salsa.debian.org/debian/eiciel/-/merge_requests/2 - folder-color -- Needs to be ported from GTK3 https://github.com/costales/folder-color/issues/17 Ubuntu-specific package - nautilus-dropbox -- Needs to be ported from GTK3 https://github.com/dropbox/nautilus-dropbox/issues/101 - nautilus-filename-repairer -- Needs to be ported from GTK3 - nautilus-ideviceinfo -- Needs to be ported from GTK3 Ubuntu-specific package - nautilus-image-converter -- Needs to be ported from GTK3 Debian removal bug filed. Unmaintained in Debian or upstream - nautilus-wipe -- Needs to be ported from GTK3 - seahorse-nautilus -- Needs to be ported from GTK3 Transition tracker -- We are going to try to fix several of the other affected source packages (not listed above) to either drop their Nautilus extension or port them to work with Nautilus 43. https://people.canonical.com/~ubuntu-archive/transitions/html/auto- nautilus.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eiciel/+bug/1984233/+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 1984233] Re: Please remove nautilus extensions incompatible with Nautilus 43
** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Changed in: nautilus (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1984233 Title: Please remove nautilus extensions incompatible with Nautilus 43 Status in eiciel package in Ubuntu: Fix Released Status in folder-color package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Triaged Status in nautilus-dropbox package in Ubuntu: Fix Released Status in nautilus-filename-repairer package in Ubuntu: Fix Released Status in nautilus-ideviceinfo package in Ubuntu: Fix Released Status in nautilus-image-converter package in Ubuntu: Fix Released Status in nautilus-wipe package in Ubuntu: Fix Released Status in seahorse-nautilus package in Ubuntu: Fix Released Bug description: nautilus python 4.0~alpha is a major API update along with nautilus 43 which had a major API update. Please remove these extensions since they are currently incompatible with the Nautilus and nautilus-python versions we are including in Kinetic - eiciel -- Needs to be ported from GTK3 Debian maintainer thinks the package is not worth keeping without the extension https://salsa.debian.org/debian/eiciel/-/merge_requests/2 - folder-color -- Needs to be ported from GTK3 https://github.com/costales/folder-color/issues/17 Ubuntu-specific package - nautilus-dropbox -- Needs to be ported from GTK3 https://github.com/dropbox/nautilus-dropbox/issues/101 - nautilus-filename-repairer -- Needs to be ported from GTK3 - nautilus-ideviceinfo -- Needs to be ported from GTK3 Ubuntu-specific package - nautilus-image-converter -- Needs to be ported from GTK3 Debian removal bug filed. Unmaintained in Debian or upstream - nautilus-wipe -- Needs to be ported from GTK3 - seahorse-nautilus -- Needs to be ported from GTK3 Transition tracker -- We are going to try to fix several of the other affected source packages (not listed above) to either drop their Nautilus extension or port them to work with Nautilus 43. https://people.canonical.com/~ubuntu-archive/transitions/html/auto- nautilus.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eiciel/+bug/1984233/+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 1972045] Re: package install-info 6.8-4build1 failed to install/upgrade: installed install-info package post-installation script subprocess returned error exit status 2
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: texinfo (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texinfo in Ubuntu. https://bugs.launchpad.net/bugs/1972045 Title: package install-info 6.8-4build1 failed to install/upgrade: installed install-info package post-installation script subprocess returned error exit status 2 Status in texinfo package in Ubuntu: Confirmed Bug description: that is with update problem ProblemType: Package DistroRelease: Ubuntu 22.04 Package: install-info 6.8-4build1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat May 7 10:03:59 2022 DuplicateSignature: package:install-info:6.8-4build1 Processing triggers for install-info (6.8-4build1) ... /usr/sbin/update-info-dir: 3: export: JAVA_HOMEbash:: bad variable name dpkg: error processing package install-info (--configure): installed install-info package post-installation script subprocess returned error exit status 2 ErrorMessage: installed install-info package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2022-04-25 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.4.5 SourcePackage: texinfo Title: package install-info 6.8-4build1 failed to install/upgrade: installed install-info package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1972045/+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 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: snapd (Ubuntu Jammy) Status: New => Confirmed -- 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/1951210 Title: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html) Status in libreoffice package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Confirmed Status in libreoffice source package in Jammy: Fix Released Status in snapd source package in Jammy: Confirmed Bug description: Ubuntu jammy live QA-test on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) Opened LibreOffice Writer as random apps in QA-test. Hit F1 to call help, and all I get is an error URL: file:///tmp/lu417531j7po.tmp/NewHelp0.html --- File not found Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- Firefox opens as a snap; but it isn't accessing the data from LibreOffice. Reported first at https://forum.snapcraft.io/t/firefox-snap-breaks- libreoffice-deb/27537 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465+canary3.3 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 17 04:46:33 2021 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/+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 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: snapd (Ubuntu) Status: New => Confirmed -- 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/1951210 Title: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html) Status in libreoffice package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Confirmed Status in libreoffice source package in Jammy: Fix Released Status in snapd source package in Jammy: Confirmed Bug description: Ubuntu jammy live QA-test on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) Opened LibreOffice Writer as random apps in QA-test. Hit F1 to call help, and all I get is an error URL: file:///tmp/lu417531j7po.tmp/NewHelp0.html --- File not found Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- Firefox opens as a snap; but it isn't accessing the data from LibreOffice. Reported first at https://forum.snapcraft.io/t/firefox-snap-breaks- libreoffice-deb/27537 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465+canary3.3 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 17 04:46:33 2021 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/+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 1986450] Re: Visual artifact 1px vertical white line right side of the wallpaper
Done. There is no change. The artifact is still present. -- 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/1986450 Title: Visual artifact 1px vertical white line right side of the wallpaper Status in gnome-shell package in Ubuntu: Incomplete Bug description: After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that there is a 1px wide vertical white line on the desktop that appears whenever an application has focus. It is on the right side of the monitor, covering the background wallpaper but not the menu. Workaround: in Displays, change scale to something else than 100% and then change back to 100%. That white vertical line will stay at the former 100% window size location until the Settings window is closed. It disappears when the Settings is closed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-27 (1570 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: gnome-shell 42.2-0ubuntu0.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: wayland-session jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1986450/+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 1954970] Re: remmina "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version"
I can confirm that the remmina-next PPA (currently offering version 1.4.27) provides a TLS Security Level drop down in the Advanced tab and that by choosing the option "0 - Windows 7 compatible" works to connect to a Windows Server 2008 R2 (which does not have ssl3 enabled) from an Ubuntu 22.04.1 client as per: https://gitlab.com/Remmina/Remmina/-/wikis/home Packages updated for me by this PPA were: freerdp2-x11 libfreerdp-client2-2 libfreerdp-server2-2 libfreerdp2-2 libwinpr2-2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp2 in Ubuntu. https://bugs.launchpad.net/bugs/1954970 Title: remmina "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version" Status in freerdp2 package in Ubuntu: Incomplete Status in freerdp2 source package in Jammy: Incomplete Bug description: Xubuntu Jammy (21.04) after upgrade libfreerdp-client2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1) libfreerdp2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1) Remmina can't connect to any RDP server (Win2008 R2) with error: "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version" Rollback to Impish version of libs libfreerdp-client2-2 2.3.0+dfsg1-2ubuntu2 libfreerdp2-2 2.3.0+dfsg1-2ubuntu2 makes it work normal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1954970/+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 1983788] Re: Update gnome-remote-desktop to 42.4
** Changed in: gnome-remote-desktop (Ubuntu Jammy) Status: Triaged => In Progress ** Description changed: Impact -- This is a new stable release in the GNOME 42 series + + It fixes some crashes reported to errors.ubuntu.com + + https://gitlab.gnome.org/GNOME/gnome-remote- + desktop/-/commit/4998bdf4ef58d4a384c93fd7543bedb7411e5854 + + https://gitlab.gnome.org/GNOME/gnome-remote- + desktop/-/commit/665f734ab7cdd52b9b2340e00f42f91a919baca7 + + https://gitlab.gnome.org/GNOME/gnome-remote- + desktop/-/compare/42.3...42.4 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1983788 Title: Update gnome-remote-desktop to 42.4 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: In Progress Bug description: Impact -- This is a new stable release in the GNOME 42 series It fixes some crashes reported to errors.ubuntu.com https://gitlab.gnome.org/GNOME/gnome-remote- desktop/-/commit/4998bdf4ef58d4a384c93fd7543bedb7411e5854 https://gitlab.gnome.org/GNOME/gnome-remote- desktop/-/commit/665f734ab7cdd52b9b2340e00f42f91a919baca7 https://gitlab.gnome.org/GNOME/gnome-remote- desktop/-/compare/42.3...42.4 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1983788/+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 1968522] Re: Remmina can't connect to windows 2008 R2
*** This bug is a duplicate of bug 1954970 *** https://bugs.launchpad.net/bugs/1954970 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: remmina (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1968522 Title: Remmina can't connect to windows 2008 R2 Status in remmina package in Ubuntu: Confirmed Bug description: Remmina on Ubuntu 22.04 can't connect to windows server 2008 R2 error: Could not connect to the RDP server "***" via TLS. See the DEBUG traces for more information. Remmina Version: 1.4.25 (git n/a) i think remmina on ubuntu 22.04 doesn't support TLS 1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1968522/+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 1001035] Re: lightdm uses a hardcoded path to .xsession-errors, please make it configurable
Upstream feature request: https://github.com/canonical/lightdm/issues/95
** Bug watch added: github.com/canonical/lightdm/issues #95
https://github.com/canonical/lightdm/issues/95
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1001035
Title:
lightdm uses a hardcoded path to .xsession-errors, please make it
configurable
Status in Light Display Manager:
Triaged
Status in lightdm package in Ubuntu:
Triaged
Bug description:
LightDM uses always $HOME/.xsession-errors as the log file because is
harcoded in xsession.c. But sometimes you want to use a logfile
outside your $HOME, suposse your $HOME is in an SSD and you want to
minimize writes, so you want to put it in /tmp/${USER}_xsession-errors
for example. If you try to make a $HOME/.xsession_errors ->
/tmp/{$USER}_xsession-errors symlink to cheat LightDM, then LightDM
will recreate the $HOME/.xsession_errors file and the hack will not
work.
LightDM _always_ recreates $HOME/.xsession_errors and you can't change
it without recompiling. So, I think this log file needs to be
configurable, or at least preserve the symlink if one is present.
Ubuntu 12.04 LTS
LightDM 1.2.1-0ubuntu1
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1001035/+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 1986510] Re: No settings options for "Dock" under setting>>appearance
** Package changed: ubuntu-release-upgrader (Ubuntu) => gnome-control- center (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1986510 Title: No settings options for "Dock" under setting>>appearance Status in gnome-control-center package in Ubuntu: New Bug description: There are no options for customizing the Dock under settings>>appearance. Even withe gnome-tweaks installed, the options don't show up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Aug 15 11:01:15 2022 InstallationDate: Installed on 2020-02-03 (924 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1986510/+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 1986510] [NEW] No settings options for "Dock" under setting>>appearance
You have been subscribed to a public bug: There are no options for customizing the Dock under settings>>appearance. Even withe gnome-tweaks installed, the options don't show up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Aug 15 11:01:15 2022 InstallationDate: Installed on 2020-02-03 (924 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy -- No settings options for "Dock" under setting>>appearance https://bugs.launchpad.net/bugs/1986510 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center 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 1986456] Re: Firefox fails to start after update
There's something wrong with the connections indeed. The platform snaps are connected, but essential plugs such as browser-support aren't. Can you try uninstalling and installing again the firefox snap? sudo snap remove firefox sudo snap install firefox -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1986456 Title: Firefox fails to start after update Status in firefox package in Ubuntu: Incomplete Bug description: After system Updates today (14.08.2022) firefox did not start anymore. It's Ubuntu 22.04 Error Message: mikey@mikey-notebook:~$ firefox /snap/firefox/1670/snap/command-chain/desktop-launch: line 52: /home/mikey/.config/user-dirs.dirs: Permission denied sed: can't read /home/mikey/.config/user-dirs.dirs: Permission denied /snap/firefox/1670/snap/command-chain/desktop-launch: line 264: /home/mikey/.config/user-dirs.dirs: Permission denied cp: cannot open '/home/mikey/.config/user-dirs.locale' for reading: Permission denied /snap/firefox/1670/snap/command-chain/desktop-launch: line 269: /home/mikey/.config/user-dirs.locale: Permission denied /snap/firefox/1670/snap/command-chain/desktop-launch: line 20: /snap/firefox/1670/gnome-platform/usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: No such file or directory ERROR: /snap/firefox/1670/gnome-platform/usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 exited abnormally with status 127 XPCOMGlueLoad error for file /snap/firefox/1670/usr/lib/firefox/libmozgtk.so: libgtk-3.so.0: cannot open shared object file: No such file or directory Couldn't load XPCOM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1986456/+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 1980386] Re: `radeonsi_dri.so` driver missing on riscv64
I suppose we may need to work with a PPA then. @xypron what do you think? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1980386 Title: `radeonsi_dri.so` driver missing on riscv64 Status in llvm-toolchain-14 package in Ubuntu: New Status in mesa package in Ubuntu: Confirmed Status in llvm-toolchain-14 source package in Jammy: New Status in mesa source package in Jammy: Confirmed Status in llvm-toolchain-14 source package in Kinetic: New Status in mesa source package in Kinetic: Confirmed Bug description: The package is missing the `radeonsi` driver, with the reasoning that LLVM is not implemented on the architecture: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995618 That said, it works just fine on focal, where it is still enabled. Without this driver there's no way to use AMD graphics cards on RISC-V. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.0.1-1ubuntu2 ProcVersionSignature: User Name 5.15.0-1007.7-generic 5.15.30 Uname: Linux 5.15.0-1007-generic riscv64 ApportVersion: 2.20.11-0ubuntu82 Architecture: riscv64 CasperMD5CheckResult: unknown Date: Thu Jun 30 15:48:11 2022 ProcCpuinfoMinimal: processor: 3 hart : 4 isa : rv64imafdc mmu : sv39 uarch: sifive,u74-mc ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-14/+bug/1980386/+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 1973644] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-utils-470 470.10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1973644 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-utils-470 470.103.01-0ubuntu0.20.04.1 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: I am having video problems ever since I tried to fix the problem with the dimmer controls ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 16 16:41:03 2022 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.108-0ubuntu5.20.04.2) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-340_340.108-0ubuntu5.20.04.2_amd64.deb (--unpack): trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-utils-470 470.103.01-0ubuntu0.20.04.1 ErrorMessage: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-utils-470 470.103.01-0ubuntu0.20.04.1 InstallationDate: Installed on 2022-01-14 (122 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-utils-470 470.103.01-0ubuntu0.20.04.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1973644/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
The issue exists in the Firefox snap as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1784977 ** Bug watch added: Mozilla Bugzilla #1784977 https://bugzilla.mozilla.org/show_bug.cgi?id=1784977 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in chromium-browser package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1949340/+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 1980937] Re: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1980937 Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise Status in alsa-driver package in Ubuntu: Confirmed Bug description: New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake- LP audio controller. When playing any audio, the internal speaker plays no sound except periodic loud crackling noise. The 3.5mm jack does not work either, producing the same craclking noise alongside some eletrical noise. HDMI audio skimmishly tested, but also gave no sound. Curiously, USB headphone (along with microphone) works perfectly, also the internal microphone. As attempts to fix the problem, I have tried the following separately, with no avail: - Installing some Ubuntu OEM version of the 5.17 kernel - Updating to the v2.2 firmware from Sound Open Firmware Project (thesofproject on github), reverted afterwards I found exactly the same problem reported in the Fedora community: https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound=1860086 As the pre-installed Windows has been destroyed, no further test on Windows has been done. Since USB headphone and internal microphone work, I think that there is no problem on the Intel Tiger Lake-LP controller and its driver. The bug probably lies elsewhere, like in the handling of ALC245 on this new laptop model. Thank you very much for your time and effort in advance. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Jul 7 10:59:22 2022 InstallationDate: Installed on 2022-06-29 (7 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2022 dmi.bios.release: 9.1 dmi.bios.vendor: HP dmi.bios.version: T37 Ver. 01.09.01 dmi.board.name: 8AB8 dmi.board.vendor: HP dmi.board.version: KBC Version 58.03.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 88.3 dmi.modalias: dmi:bvnHP:bvrT37Ver.01.09.01:bd05/05/2022:br9.1:efr88.3:svnHP:pnHPEliteBook840G8NotebookPC:pvr:rvnHP:rn8AB8:rvrKBCVersion58.03.00:cvnHP:ct10:cvr:sku6A3P3AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G8 Notebook PC dmi.product.sku: 6A3P3AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-07-02T17:07:35.783239 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1980937/+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 1986456] Re: Firefox fails to start after update
mikey@mikey-notebook:~$ snap connections firefox Schnittstelle PlugSlot Notizen audio-playbackfirefox:audio-playback - - audio-record firefox:audio-record- - avahi-observe firefox:avahi-observe - - browser-support firefox:browser-sandbox - - camerafirefox:camera - - content[gnome-3-38-2004] firefox:gnome-3-38-2004 gnome-3-38-2004:gnome-3-38-2004 - content[gtk-3-themes] firefox:gtk-3-themes gtk-common-themes:gtk-3-themes - content[icon-themes] firefox:icon-themes gtk-common-themes:icon-themes- content[sound-themes] firefox:sound-themes gtk-common-themes:sound-themes - cups-control firefox:cups-control- - dbus - firefox:dbus-daemon - desktop firefox:desktop - - desktop-legacyfirefox:desktop-legacy - - gsettings firefox:gsettings - - hardware-observe firefox:hardware-observe- - home firefox:home- - joystick firefox:joystick- - mpris - firefox:mpris - network firefox:network - - network-bind firefox:network-bind- - network-observe firefox:network-observe - - openglfirefox:opengl - - personal-filesfirefox:dot-mozilla-firefox - - removable-media firefox:removable-media - - screen-inhibit-controlfirefox:screen-inhibit-control - - system-files firefox:etc-firefox-policies- - system-packages-doc firefox:system-packages-doc - - u2f-devices firefox:u2f-devices - - unity7firefox:unity7 - - upower-observefirefox:upower-observe - - wayland firefox:wayland - - x11 firefox:x11 - -- 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/1986456 Title: Firefox fails to start after update Status in firefox package in Ubuntu: Incomplete Bug description: After system Updates today (14.08.2022) firefox did not start anymore. It's Ubuntu 22.04 Error Message: mikey@mikey-notebook:~$ firefox /snap/firefox/1670/snap/command-chain/desktop-launch: line 52: /home/mikey/.config/user-dirs.dirs: Permission denied sed: can't read /home/mikey/.config/user-dirs.dirs: Permission denied /snap/firefox/1670/snap/command-chain/desktop-launch: line 264: /home/mikey/.config/user-dirs.dirs: Permission denied cp: cannot open '/home/mikey/.config/user-dirs.locale' for reading: Permission denied /snap/firefox/1670/snap/command-chain/desktop-launch: line 269: /home/mikey/.config/user-dirs.locale: Permission denied /snap/firefox/1670/snap/command-chain/desktop-launch: line 20: /snap/firefox/1670/gnome-platform/usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: No such file or directory ERROR: /snap/firefox/1670/gnome-platform/usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 exited abnormally with status 127 XPCOMGlueLoad error for file /snap/firefox/1670/usr/lib/firefox/libmozgtk.so: libgtk-3.so.0: cannot open shared object file: No such file or directory Couldn't load XPCOM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1986456/+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 1980386] Re: `radeonsi_dri.so` driver missing on riscv64
oh right, 22.0.5 hasn't been backported yet anyway, if llvm is enabled, it'll essentially break swrast for riscv64.. if that's a tradeoff you can live with, then okay -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1980386 Title: `radeonsi_dri.so` driver missing on riscv64 Status in llvm-toolchain-14 package in Ubuntu: New Status in mesa package in Ubuntu: Confirmed Status in llvm-toolchain-14 source package in Jammy: New Status in mesa source package in Jammy: Confirmed Status in llvm-toolchain-14 source package in Kinetic: New Status in mesa source package in Kinetic: Confirmed Bug description: The package is missing the `radeonsi` driver, with the reasoning that LLVM is not implemented on the architecture: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995618 That said, it works just fine on focal, where it is still enabled. Without this driver there's no way to use AMD graphics cards on RISC-V. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.0.1-1ubuntu2 ProcVersionSignature: User Name 5.15.0-1007.7-generic 5.15.30 Uname: Linux 5.15.0-1007-generic riscv64 ApportVersion: 2.20.11-0ubuntu82 Architecture: riscv64 CasperMD5CheckResult: unknown Date: Thu Jun 30 15:48:11 2022 ProcCpuinfoMinimal: processor: 3 hart : 4 isa : rv64imafdc mmu : sv39 uarch: sifive,u74-mc ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-14/+bug/1980386/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
A user reported VDAVideoDecoder in testing this under Wayland, but if he
tries to play a Youtube video on fullscreen on 3 4K displays, it stops
playing after ~10 s; Unmaximizing it resumes it.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. If on Xorg (`echo $WAYLAND_DISPLAY` is empty),
snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
If on Wayland (`echo $WAYLAND_DISPLAY` is not empty),
chromium --enable-features=VaapiVideoDecoder --disable-
features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1986616] Re: Wrong gnome version
Yes, we need to copy the gnome-desktop fix that we applied to Debian's gnome-control-center. ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1986616 Title: Wrong gnome version Status in gnome-control-center package in Ubuntu: Triaged Bug description: If I run in a terminal: $ gnome-control-center info-overview Gnome version 3.0 is shown in window. My current gnome version is: $ gnome-shell --version GNOME Shell 42.4 My ubuntu version: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:42.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Aug 16 07:48:18 2022 InstallationDate: Installed on 2018-09-22 (1423 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to kinetic on 2021-02-17 (544 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1986616/+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 1973084] Re: transmission-daemon high RAM usage
This issue is still available in x86_64 build also. Fixed in upstream, but consume more CPU now than it should. https://github.com/transmission/transmission/issues/3536 https://github.com/transmission/transmission/issues/3494 ** Bug watch added: github.com/transmission/transmission/issues #3536 https://github.com/transmission/transmission/issues/3536 ** Bug watch added: github.com/transmission/transmission/issues #3494 https://github.com/transmission/transmission/issues/3494 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Confirmed Bug description: Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
It is, but since that bug targets both Chromium and Firefox, I believe
it would be significantly harder to keep track of context of each piece
of feedback (unfortunately we don't have threading here), judging by the
interactions we have had in this one, both for developers and users.
Also, I consider the bug description with the test case key for quickly
identifying testing instructions.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. If on Xorg (`echo $WAYLAND_DISPLAY` is empty),
snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
If on Wayland (`echo $WAYLAND_DISPLAY` is not empty),
chromium --enable-features=VaapiVideoDecoder --disable-
features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1986583] Re: Screen after some time get shifted and starts to overlap
yeah, I added config to xorg.conf which contains this: Section "Device" Identifier "Card0" Driver "intel" BusID "PCI:0:2:0" Option "DRI" "3" Option "TearFree" "true" EndSection I have no deep understanding about how to switch drivers or how to use another one(which one?), but without this config, I had following problems: a) Option "DRI" "3" when this is not present it causes that strip of screen from time to time flicker - i would describe it like subset of pixels in some rectangle area are swapped to another color for a period of half seconds, and then it turns back to normal. It does not happen often but occasionally. b) "TearFree" "True" - without this when window is moved from up to bottom it is clearly seen that left part of screen is updated earlier then the right one. Is there a way to switch to another driver without losing this configuration? also in Wayland does not work x11vnc, and I did not found suitable replacement. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1986583 Title: Screen after some time get shifted and starts to overlap Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: problem resembles a lot this one: https://askubuntu.com/questions/07/ubuntu-desktop-shifted-to-right "I am encountering a strange problem, my whole desktop has shifted to right." But different in a way, that when pc is started it shows everything just fine. But when computer is powered on a few days straight, display gets shifted. Some times just cca 1/4 of screen, sometimes it shifts over half of the screen. Computer should be used to run 8hours straight (it is intended for customer) When i switch from graphic display to tty (ctrl+alt+num) and back, display gets "restarted" and problem is fixed. But it is just temporary. Restart fixes it also. Last time i encountered this behavior today between 17-18hour. But have no idea what or where to look for. yes, and when one connects to display over X11 or teamviewer screen appears to be okay, so one will notice this problem if using pc remotely 1) lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 2) xorg: Installed: 1:7.7+23ubuntu2 Candidate: 1:7.7+23ubuntu2 Version table: *** 1:7.7+23ubuntu2 500 500 http://cz.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 3) expect that display will stay where it is on the start of computer 4) display gets shifted to some distance from unknown reason (Maybe x11vnc or teamviewer usage or something). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 15 22:27:55 2022 DistUpgraded: 2022-08-02 14:36:41,704 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2015] InstallationDate: Installed on 2022-02-17 (179 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 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=582fb3cc-8ef6-460b-b9ae-a16f81c604a7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-08-02 (13 days ago) dmi.bios.date: 10/07/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GSKU0504.V54 dmi.board.asset.tag: Default string dmi.board.name: SKYBAY dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGSKU0504.V54:bd10/07/2021:br5.12:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku:
[Desktop-packages] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding
** Description changed: This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux browsers. We will close this bug when both browsers will have Va-api decoding working OOTB without user interaction like in WinOS and MacOS August 2022 : - * Ubuntu 22.04 :Launch firefox snap on Intel Tiger lake -> Check with + * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1 ) - -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding - works + -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works +-> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need to fix this as most youtube is AV1 now. * In july 2020, things are getting better : - Chromium : A patch is used on most distro packages. , more info here https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497 - Firefox : Firefox team has done a great job and now Va-api decoding in Wayland is possible and X11 is possible in nightly ! Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 * In 2015 I opened this bug , no easy solution was available and battery drained when playing video in browser was crazy. -- 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/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux browsers. We will close this bug when both browsers will have Va-api decoding working OOTB without user interaction like in WinOS and MacOS August 2022 : * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1 ) -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need to fix this as most youtube is AV1 now. * In july 2020, things are getting better : - Chromium : A patch is used on most distro packages. , more info here https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1816497 - Firefox : Firefox team has done a great job and now Va-api decoding in Wayland is possible and X11 is possible in nightly ! Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 * In 2015 I opened this bug , no easy solution was available and battery drained when playing video in browser was crazy. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+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 1979891] Re: Firefox becomes unusable when adjusting window size
Sorry for the lack of feedback until now. This sounds like a potential upstream issue. Would you mind filing it at https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox, and sharing the link to the upstream bug here? Thanks! -- 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/1979891 Title: Firefox becomes unusable when adjusting window size Status in firefox package in Ubuntu: New Bug description: OS version: Ubuntu 22.04 LTS Firefox version: 1:1snap1-0ubuntu2 - 101.0.1 (64-bit) Sometimes when I adjust the size of a Firefox window, that window becomes messed up: the contents don't fill the window, not all the controls are visible, and clicks are offset, so if I click on one spot, the window behaves as if I clicked on a different spot (so it's impossible to use Firefox in that window anymore). I seem to remember being able to fix this by dragging and dropping the window onto a different monitor or workspace in the GNOME Activities view, but I'm currently experiencing the problem and that is not helping. I took a screenshot of what's currently going on (attached) which happened when I tried to maximize the window. This is on a laptop with an external monitor that I'm using in portrait mode, via a USB-C connection that's converted to HDMI. I had plugged in to the external monitor a few minutes before this happens, and plugging in or possibly unplugging seems to make this bug more likely. This is a relatively new problem, starting within the last few weeks. (Maybe after I switched to the snap version of Firefox? I guess that was when I upgraded from the previous LTS version of Ubuntu.) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 25 15:23:13 2022 DistUpgraded: 2022-05-27 14:03:05,108 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-39-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07e6] InstallationDate: Installed on 2018-11-23 (1309 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS 13 9370 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-40-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-05-27 (29 days ago) dmi.bios.date: 03/22/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0H0VG3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd03/22/2022:br1.19:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0H0VG3:rvrA00:cvnDellInc.:ct10:cvr:sku07E6: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1979891/+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 1980386] Re: `radeonsi_dri.so` driver missing on riscv64
@tjaalton it's 21.2.6-0ubuntu0.1~20.04.2 in focal: https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/23235579 https://launchpad.net/ubuntu/+source/mesa -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1980386 Title: `radeonsi_dri.so` driver missing on riscv64 Status in llvm-toolchain-14 package in Ubuntu: New Status in mesa package in Ubuntu: Confirmed Status in llvm-toolchain-14 source package in Jammy: New Status in mesa source package in Jammy: Confirmed Status in llvm-toolchain-14 source package in Kinetic: New Status in mesa source package in Kinetic: Confirmed Bug description: The package is missing the `radeonsi` driver, with the reasoning that LLVM is not implemented on the architecture: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995618 That said, it works just fine on focal, where it is still enabled. Without this driver there's no way to use AMD graphics cards on RISC-V. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.0.1-1ubuntu2 ProcVersionSignature: User Name 5.15.0-1007.7-generic 5.15.30 Uname: Linux 5.15.0-1007-generic riscv64 ApportVersion: 2.20.11-0ubuntu82 Architecture: riscv64 CasperMD5CheckResult: unknown Date: Thu Jun 30 15:48:11 2022 ProcCpuinfoMinimal: processor: 3 hart : 4 isa : rv64imafdc mmu : sv39 uarch: sifive,u74-mc ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-14/+bug/1980386/+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 1986456] Re: Firefox fails to start after update
It looks like the gnome platform snap isn't connected to firefox, somehow. Can you please share the output of `snap connections firefox` ? ** Changed in: firefox (Ubuntu) Status: Confirmed => Incomplete -- 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/1986456 Title: Firefox fails to start after update Status in firefox package in Ubuntu: Incomplete Bug description: After system Updates today (14.08.2022) firefox did not start anymore. It's Ubuntu 22.04 Error Message: mikey@mikey-notebook:~$ firefox /snap/firefox/1670/snap/command-chain/desktop-launch: line 52: /home/mikey/.config/user-dirs.dirs: Permission denied sed: can't read /home/mikey/.config/user-dirs.dirs: Permission denied /snap/firefox/1670/snap/command-chain/desktop-launch: line 264: /home/mikey/.config/user-dirs.dirs: Permission denied cp: cannot open '/home/mikey/.config/user-dirs.locale' for reading: Permission denied /snap/firefox/1670/snap/command-chain/desktop-launch: line 269: /home/mikey/.config/user-dirs.locale: Permission denied /snap/firefox/1670/snap/command-chain/desktop-launch: line 20: /snap/firefox/1670/gnome-platform/usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: No such file or directory ERROR: /snap/firefox/1670/gnome-platform/usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 exited abnormally with status 127 XPCOMGlueLoad error for file /snap/firefox/1670/usr/lib/firefox/libmozgtk.so: libgtk-3.so.0: cannot open shared object file: No such file or directory Couldn't load XPCOM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1986456/+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 1946345] Re: Chromium 94 snap for 21.10 beta flickering and unusable for Nvidia Wayland session
Ubuntu 21.10 is no longer supported but please see bug 1967488 and bug 1968610. ** Changed in: chromium-browser (Ubuntu) Status: New => Won't Fix -- 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/1946345 Title: Chromium 94 snap for 21.10 beta flickering and unusable for Nvidia Wayland session Status in chromium-browser package in Ubuntu: Won't Fix Bug description: Launching chromium 94 with Nvidia Wayland session under 21.10 Beta open a transparent and flickering window where you can draw something with the mouse cursor. mv@i56400:~$ chromium (chrome:19496): Gtk-WARNING **: 11:26:41.116: Theme parsing error: gtk.css:1418:23: 'font-feature-settings' is not a valid property name (chrome:19496): Gtk-WARNING **: 11:26:41.120: Theme parsing error: gtk.css:3295:25: 'font-feature-settings' is not a valid property name (chrome:19496): Gtk-WARNING **: 11:26:41.121: Theme parsing error: gtk.css:3757:23: 'font-feature-settings' is not a valid property name (chrome:19496): dbind-WARNING **: 11:26:41.208: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-HsiwuTsGUv: No such file or directory libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) [19496:19582:1007/112643.593254:ERROR:chrome_browser_main_extra_parts_metrics.cc(228)] crbug.com/1216328: Checking Bluetooth availability started. Please report if there is no report that this ends. [19496:19582:1007/112643.593278:ERROR:chrome_browser_main_extra_parts_metrics.cc(231)] crbug.com/1216328: Checking Bluetooth availability ended. [19496:19582:1007/112643.593296:ERROR:chrome_browser_main_extra_parts_metrics.cc(234)] crbug.com/1216328: Checking default browser status started. Please report if there is no report that this ends. [19496:19582:1007/112643.633735:ERROR:chrome_browser_main_extra_parts_metrics.cc(238)] crbug.com/1216328: Checking default browser status ended. [19496:19607:1007/112643.649276:ERROR:udev_watcher.cc(98)] Failed to begin udev enumeration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1946345/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
This appears to be a duplicate of bug 1424201. Can we close this bug?
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Incomplete
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. If on Xorg (`echo $WAYLAND_DISPLAY` is empty),
snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
If on Wayland (`echo $WAYLAND_DISPLAY` is not empty),
chromium --enable-features=VaapiVideoDecoder --disable-
features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1983638] Re: Ubuntu 22.10 Settings-sound-output-test does not work
Seems like a general GNOME problem since the gnome-shell volume button sounds no longer work in 22.10 either. ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1983638 Title: Ubuntu 22.10 Settings-sound-output-test does not work Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Open settings. select sound. System Volume and Volume for System Sounds are at maximum, Output Device is HDMI / DisplayPort2 - Built-in Audio click on Test and then on Left or Right speaker has no effect (no sound) but clicking on Alert Sound works fine. Playing a movie.MOV with totem sound is ok. On the same PC different partition I have Ubuntu 22.04 and problem does not occur. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:42.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Aug 5 07:06:31 2022 InstallationDate: Installed on 2022-07-19 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1983638/+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 1986616] Re: Wrong gnome version
** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1986616 Title: Wrong gnome version Status in gnome-control-center package in Ubuntu: Confirmed Bug description: If I run in a terminal: $ gnome-control-center info-overview Gnome version 3.0 is shown in window. My current gnome version is: $ gnome-shell --version GNOME Shell 42.4 My ubuntu version: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:42.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Aug 16 07:48:18 2022 InstallationDate: Installed on 2018-09-22 (1423 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to kinetic on 2021-02-17 (544 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1986616/+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 1983638] Re: Ubuntu 22.10 Settings-sound-output-test does not work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1983638 Title: Ubuntu 22.10 Settings-sound-output-test does not work Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Open settings. select sound. System Volume and Volume for System Sounds are at maximum, Output Device is HDMI / DisplayPort2 - Built-in Audio click on Test and then on Left or Right speaker has no effect (no sound) but clicking on Alert Sound works fine. Playing a movie.MOV with totem sound is ok. On the same PC different partition I have Ubuntu 22.04 and problem does not occur. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:42.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Aug 5 07:06:31 2022 InstallationDate: Installed on 2022-07-19 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1983638/+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 1986616] Re: Wrong gnome version
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1986616 Title: Wrong gnome version Status in gnome-control-center package in Ubuntu: Confirmed Bug description: If I run in a terminal: $ gnome-control-center info-overview Gnome version 3.0 is shown in window. My current gnome version is: $ gnome-shell --version GNOME Shell 42.4 My ubuntu version: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:42.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Aug 16 07:48:18 2022 InstallationDate: Installed on 2018-09-22 (1423 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to kinetic on 2021-02-17 (544 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1986616/+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 1986584] Re: Nautilus crashes when i pluh-in iphone se
** Summary changed: - nautilun crashes when i pluh-in iphone se + Nautilus crashes when i pluh-in iphone se -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1986584 Title: Nautilus crashes when i pluh-in iphone se Status in nautilus package in Ubuntu: New Bug description: Stack trace: https://termbin.com/pd8x3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1986584/+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 1986606] Re: When locking computer with Win+L, screen goes black permanently
Thanks for the bug report. Next time the problem happens, after rebooting please run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1986606 Title: When locking computer with Win+L, screen goes black permanently Status in Ubuntu: Incomplete Bug description: I had a workaround for this in 20.04, press and hold Win+L so it types letters into the input field as you lock the computer. This kept the screen from going black, and I could manually dim the laptop screen (fn+brightness) and walk away. In 22.04 the screen now fades to black immediately when I press Win+L, even though I can see the first few characters being entered on the input field as the screen fades to black. Black screen (as in fade to black for inactivity) seems to be irreversible on this computer, no amount of mouse-wiggling, 3 finger salute (ctrl-alt-delete), or usb dongle removal and reattachment will cause the display to wake up. In 20.04 I could get around this on computer lock by continuing to press Win+L until the input box had lots of input. That seemed to stop the screen from dimming in 20.04. Not working in 22.04. The only way I have found out of this is to do a hard power down (7+ seconds pressing power button). For obvious reasons I prefer not to do this often. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 15 22:03:08 2022 DistUpgraded: 2022-08-15 15:36:20,169 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 620 [1025:121a] InstallationDate: Installed on 2022-03-14 (154 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0408:a030 Quanta Computer, Inc. HD WebCam Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros QCA9377 Bluetooth Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-576 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-08-15 (0 days ago) dmi.bios.date: 10/24/2017 dmi.bios.release: 0.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: KBL dmi.board.version: V1.32 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.32:bd10/24/2017:br0.0:efr1.10:svnAcer:pnAspireE5-576:pvrV1.32:rvnKBL:rnIronman_SK:rvrV1.32:cvnChassisManufacturer:ct10:cvrChassisVersion:sku: dmi.product.family: Aspire E 15 dmi.product.name: Aspire E5-576 dmi.product.sku: dmi.product.version: V1.32 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1986606/+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 1986583] Re: Screen after some time get shifted and starts to overlap
Thanks for the bug report. It appears you're using the old unsupported (and buggy) 'intel' graphics driver. Please remove any config files you have loading that and even consider removing the entire driver: sudo apt remove xserver-xorg-video-intel Alternatively, please just log into 'Ubuntu' to get a Wayland session instead of logging into 'Ubuntu on Xorg'. ** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu) ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Incomplete -- 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/1986583 Title: Screen after some time get shifted and starts to overlap Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: problem resembles a lot this one: https://askubuntu.com/questions/07/ubuntu-desktop-shifted-to-right "I am encountering a strange problem, my whole desktop has shifted to right." But different in a way, that when pc is started it shows everything just fine. But when computer is powered on a few days straight, display gets shifted. Some times just cca 1/4 of screen, sometimes it shifts over half of the screen. Computer should be used to run 8hours straight (it is intended for customer) When i switch from graphic display to tty (ctrl+alt+num) and back, display gets "restarted" and problem is fixed. But it is just temporary. Restart fixes it also. Last time i encountered this behavior today between 17-18hour. But have no idea what or where to look for. yes, and when one connects to display over X11 or teamviewer screen appears to be okay, so one will notice this problem if using pc remotely 1) lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 2) xorg: Installed: 1:7.7+23ubuntu2 Candidate: 1:7.7+23ubuntu2 Version table: *** 1:7.7+23ubuntu2 500 500 http://cz.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 3) expect that display will stay where it is on the start of computer 4) display gets shifted to some distance from unknown reason (Maybe x11vnc or teamviewer usage or something). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 15 22:27:55 2022 DistUpgraded: 2022-08-02 14:36:41,704 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2015] InstallationDate: Installed on 2022-02-17 (179 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 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=582fb3cc-8ef6-460b-b9ae-a16f81c604a7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-08-02 (13 days ago) dmi.bios.date: 10/07/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GSKU0504.V54 dmi.board.asset.tag: Default string dmi.board.name: SKYBAY dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGSKU0504.V54:bd10/07/2021:br5.12:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati
[Desktop-packages] [Bug 1986450] Re: Visual artifact 1px vertical white line right side of the wallpaper
Thanks. Please try removing your extensions in case they are the cause: cd ~/.local/share/gnome-shell/ rm -rf extensions and then log in again. ** Tags added: amdgpu -- 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/1986450 Title: Visual artifact 1px vertical white line right side of the wallpaper Status in gnome-shell package in Ubuntu: Incomplete Bug description: After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that there is a 1px wide vertical white line on the desktop that appears whenever an application has focus. It is on the right side of the monitor, covering the background wallpaper but not the menu. Workaround: in Displays, change scale to something else than 100% and then change back to 100%. That white vertical line will stay at the former 100% window size location until the Settings window is closed. It disappears when the Settings is closed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-27 (1570 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: gnome-shell 42.2-0ubuntu0.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: wayland-session jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1986450/+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 1986607] Re: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1986607 Title: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 Status in firefox package in Ubuntu: Confirmed Bug description: Not an expert in this field, I just want to report the problem to the developers. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 103.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-124.140-generic 5.4.195 Uname: Linux 5.4.0-124-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: farooq 1591 F pulseaudio BuildID: 20220718155818 CasperMD5CheckResult: unknown Channel: Unavailable Date: Tue Aug 16 06:48:51 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-09-12 (1068 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 192.168.43.199 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.43.0/24 dev wlp3s0 proto kernel scope link src 192.168.43.99 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-08-16 (0 days ago) dmi.bios.date: 10/14/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M50Vm dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr212:bd10/14/2009:svnASUSTeKComputerInc.:pnM50Vm:pvr1.0:rvnASUSTeKComputerInc.:rnM50Vm:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M50Vm dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1986607/+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 1986616] [NEW] Wrong gnome version
Public bug reported: If I run in a terminal: $ gnome-control-center info-overview Gnome version 3.0 is shown in window. My current gnome version is: $ gnome-shell --version GNOME Shell 42.4 My ubuntu version: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Kinetic Kudu (development branch) Release:22.10 Codename: kinetic ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:42.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Aug 16 07:48:18 2022 InstallationDate: Installed on 2018-09-22 (1423 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to kinetic on 2021-02-17 (544 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1986616 Title: Wrong gnome version Status in gnome-control-center package in Ubuntu: New Bug description: If I run in a terminal: $ gnome-control-center info-overview Gnome version 3.0 is shown in window. My current gnome version is: $ gnome-shell --version GNOME Shell 42.4 My ubuntu version: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:42.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Aug 16 07:48:18 2022 InstallationDate: Installed on 2018-09-22 (1423 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to kinetic on 2021-02-17 (544 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1986616/+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
