[Desktop-packages] [Bug 1981872] [NEW] package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 10
Public bug reported: I find this bug when i install firefox ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: firefox:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jul 16 13:05:30 2022 Dependencies: ErrorMessage: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 10 InstallationDate: Installed on 2022-07-16 (0 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 RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.5 SourcePackage: firefox Title: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/1981872 Title: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 10 Status in firefox package in Ubuntu: New Bug description: I find this bug when i install firefox ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: firefox:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jul 16 13:05:30 2022 Dependencies: ErrorMessage: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 10 InstallationDate: Installed on 2022-07-16 (0 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 RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.5 SourcePackage: firefox Title: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1981872/+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 1972059] Re: One screen does not come back from lock
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1972059 Title: One screen does not come back from lock Status in mutter package in Ubuntu: Expired Bug description: I have 2 screen (Dell). Since having upgraded to 22.04, one of them struggles to come back after a lock. Sometimes takes a few seconds, sometimes it is ok and sometimes it takes longer. I have found that if I do Ctrl-Alt-F1... the screen comes back. I have a DP and HDMI cable and tried to switch them around, it is always the same screen: a Dell U2415 UltraSharp 24. Never happened with any other version since about 18.04. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 7 13:39:19 2022 DistUpgraded: 2022-04-29 21:19:33,557 WARNING no activity on terminal for 300 seconds (Configuring libpam-systemd (amd64)) DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.3.0, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2020-02-01 (825 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-29 (7 days ago) dmi.bios.date: 11/11/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 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/mutter/+bug/1972059/+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 1972889] Re: Screen reader reads the data while computer is locked
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1972889 Title: Screen reader reads the data while computer is locked Status in gnome-shell package in Ubuntu: Expired Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-shell gnome-shell: Installed: 42.0-2ubuntu1 Candidate: 42.0-2ubuntu1 Version table: *** 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Ubuntu is installed on a laptop. Within five minutes of inactivity, the screen lock activates and locks the system. Computer is secured. 10 minutes later, my cat (her name is Loaf) comes up to the laptop and sits down on the keyboard. This activates a screen reader. (Shortcut is Alt + Super + S) What I've expected: Screen reader would start reading the contents of a lock screen What happened: Screen reader app started reading contents of a Brave Browser window that was opened on my desktop. It read all tabs and proceeded reading the opened web page. I've reported this bug at secur...@ubuntu.org and got the following answer: > Nice find - I am able to reproduce this locally in Ubuntu 22.04 LTS too > - I suspect this is a vulnerability in gnome-shell as it is > responsible for handling the lock screen in standard Ubuntu. As per further directions, I'm posting this bug here and in gnome repo. P.S. I expect Loaf being credited for this find. She really likes treats. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-10-24 (201 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: wayland-session jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972889/+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 1972812] Re: gnome-shell (X11, nvidia-390) crashes with SIGSEGV when unlocking the screen
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1972812 Title: gnome-shell (X11, nvidia-390) crashes with SIGSEGV when unlocking the screen Status in gnome-shell package in Ubuntu: Expired Bug description: I found a security vulnerability in Ubuntu 22.04 LTS operating system (Laptops only) It is reproduced like this (in steps): 1. I lock the screen Win + L 2. Close the laptop lid 3. Then I open the lid of the laptop 4. I get a vulnerability, the operating system does not ask for a password, but immediately shows the desktop without the need to unlock it. that is, closing and opening the laptop lid leads to unlocking the screen without asking for a password. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 10 12:20:28 2022 InstallationDate: Installed on 2022-04-21 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972812/+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 1973435] Re: libfprint-2-2:armhf
[Expired for fprintd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: fprintd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1973435 Title: libfprint-2-2:armhf Status in fprintd package in Ubuntu: Expired Bug description: What is the problem with libfprintd-2-2:armhf? why the setup process takes too long to hours. Until in the end I decided to kill the session Description:Ubuntu 20.04.4 LTS Release:20.0 fprintd: Installed: (none) Candidate: 1.90.9-1~ubuntu20.04.1 Version table: 1.90.9-1~ubuntu20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main armhf Packages 100 /var/lib/dpkg/status 1.90.1-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main armhf Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1973435/+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 1973393] Re: auto go to left or first page
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1973393 Title: auto go to left or first page Status in gnome-shell package in Ubuntu: Expired Bug description: Bug is "auto go to left or first page". It's occurs on Ubuntu work space, text input, and whrn I use Brave browser multiple tabs when I click on second tab I's always go to first tab automatically. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CrashReports: 640:1000:124:25922520:2022-05-12 20:48:18.083328485 +0700:2022-05-12 20:48:19.171324152 +0700:/var/crash/_usr_bin_gnome-shell.1000.crash 664:1000:124:0:2022-05-12 20:48:19.083328559 +0700:2022-05-12 20:48:19.083328559 +0700:/var/crash/_usr_bin_gnome-shell.1000.upload 600:117:124:37:2022-05-12 20:48:28.158915588 +0700:2022-05-12 20:48:28.158915588 +0700:/var/crash/_usr_bin_gnome-shell.1000.uploaded CurrentDesktop: ubuntu:GNOME Date: Sat May 14 12:46:55 2022 InstallationDate: Installed on 2022-05-11 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973393/+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 1973428] Re: Totem crashes when started (segmentation fault) in Ubuntu 22.04
[Expired for totem (Ubuntu) because there has been no activity for 60 days.] ** Changed in: totem (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1973428 Title: Totem crashes when started (segmentation fault) in Ubuntu 22.04 Status in totem package in Ubuntu: Expired Bug description: When I start totem (by clicking its icon in the dock or when I double click a video file or when I run it from CLI), it immediately crashes. This issue occurs since I upgraded from 21.10 to 22.04. When run from CLI with debug emssages activated, the following messages appear: $ G_MESSAGES_DEBUG=all totem (totem:1015458): GLib-GIO-DEBUG: 19:14:57.264: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ (totem:1015458): dconf-DEBUG: 19:14:57.264: watch_fast: "/org/gnome/Totem/" (establishing: 0, active: 0) Gtk-Message: 19:14:57.266: Failed to load module "xapp-gtk3-module" (totem:1015458): dconf-DEBUG: 19:14:57.267: watch_established: "/org/gnome/Totem/" (establishing: 1) (totem:1015458): GLib-GIO-DEBUG: 19:14:57.293: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ (totem:1015458): GLib-DEBUG: 19:14:57.339: unsetenv() is not thread-safe and should not be used after threads are created (totem:1015458): Gtk-DEBUG: 19:14:57.339: Connecting to session manager (totem:1015458): Handy-DEBUG: 19:14:57.341: Trying to initialize portal (totem:1015458): dconf-DEBUG: 19:14:57.520: watch_fast: "/org/gnome/Totem/" (establishing: 0, active: 1) (totem:1015458): dconf-DEBUG: 19:14:57.520: watch_fast: "/org/gnome/desktop/lockdown/" (establishing: 0, active: 0) (totem:1015458): dconf-DEBUG: 19:14:57.520: watch_established: "/org/gnome/desktop/lockdown/" (establishing: 1) (totem:1015458): dconf-DEBUG: 19:14:57.636: watch_fast: "/org/gnome/desktop/thumbnailers/" (establishing: 0, active: 0) (totem:1015458): dconf-DEBUG: 19:14:57.636: watch_established: "/org/gnome/desktop/thumbnailers/" (establishing: 1) (totem:1015458): GLib-GIO-DEBUG: 19:14:57.639: Failed to initialize portal (GNetworkMonitorPortal) for gio-network-monitor: Not using portals (totem:1015458): GLib-GIO-DEBUG: 19:14:57.643: _g_io_module_get_default: Found default implementation networkmanager (GNetworkMonitorNM) for ‘gio-network-monitor’ (totem:1015458): dconf-DEBUG: 19:14:57.643: watch_fast: "/org/gnome/Totem/" (establishing: 0, active: 2) (totem:1015458): dconf-DEBUG: 19:14:57.643: unwatch_fast: "/org/gnome/Totem/" (active: 3, establishing: 0) (totem:1015458): GLib-GIO-DEBUG: 19:14:57.657: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’ (totem:1015458): dconf-DEBUG: 19:14:57.744: change_fast (totem:1015458): dconf-DEBUG: 19:14:57.744: watch_fast: "/org/gnome/Totem/" (establishing: 0, active: 2) (totem:1015458): dconf-DEBUG: 19:14:57.744: unwatch_fast: "/org/gnome/Totem/" (active: 3, establishing: 0) (totem:1015458): dconf-DEBUG: 19:14:57.745: watch_fast: "/org/gnome/Totem/" (establishing: 0, active: 2) (totem:1015458): dconf-DEBUG: 19:14:57.753: watch_fast: "/org/gnome/Totem/" (establishing: 0, active: 3) (totem:1015458): dconf-DEBUG: 19:14:57.768: watch_fast: "/org/gnome/desktop/lockdown/" (establishing: 0, active: 1) (totem:1015458): Totem-DEBUG: 19:14:57.769: totem_playlist_add_one_mrl (): Akira (1988).mkv (null) (null) (null) 0 true (totem:1015458): Totem-DEBUG: 19:14:57.844: TotemGrilo: Pausing videos thumbnailing (totem:1015458): Totem-DEBUG: 19:14:57.889: Adding popup busy for reason opening file (totem:1015458): Totem-DEBUG: 19:14:57.889: emitting PlaybackStatus change (totem:1015458): Totem-DEBUG: 19:14:57.889: Not enabling offline save, as 'file:///home/raffaele/Video/Film/Akira/Akira%20(1988).mkv' already in $HOME, and native (totem:1015458): Totem-DEBUG: 19:14:57.890: TotemGrilo: Pausing videos thumbnailing (totem:1015458): Totem-DEBUG: 19:14:57.890: TotemGrilo: Pausing videos thumbnailing (totem:1015458): Totem-DEBUG: 19:14:57.898: successfully acquired dbus name org.mpris.MediaPlayer2.totem (totem:1015458): GStreamer-CRITICAL **: 19:14:58.367: gst_caps_from_string: assertion 'string' failed (totem:1015458): GStreamer-CRITICAL **: 19:14:58.367: gst_pad_template_new: assertion 'caps != NULL' failed (totem:1015458): GStreamer-CRITICAL **: 19:14:58.367: gst_mini_object_unref: assertion 'mini_object != NULL' failed (totem:1015458): GStreamer-CRITICAL **: 19:14:58.367: gst_element_class_add_pad_template: assertion 'GST_IS_PAD_TEMPLATE (templ)' failed (totem:1015458): GStreamer-Video-CRITICAL **: 19:14:58.367: gst_video_decoder_init: assertion 'pad_template != NULL' failed (totem:1015458): GStreamer-WARNING **: 19:14:58.367: Element
[Desktop-packages] [Bug 1973472] Re: Vea la página de manual apt-secure(8) para los detalles sobre la creación de repositorios y la configuración de usuarios. W: El objetivo Sources (main/source/Sour
[Expired for duplicity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: duplicity (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1973472 Title: Vea la página de manual apt-secure(8) para los detalles sobre la creación de repositorios y la configuración de usuarios. W: El objetivo Sources (main/source/Sources) está configurado varias veces en /etc/apt/sources.list:2 y /etc/apt/sources.list:7 W: El objetivo Sources (main/source/Sources) está configurado varias veces en /etc/apt/sources.list:2 y /etc/apt/sources.list:7 Status in duplicity package in Ubuntu: Expired Bug description: Error de GPG: https://packages.microsoft.com/repos/edge stable InRelease: Las firmas siguientes no se pudieron verificar porque su clave pública no está disponible: NO_PUBKEY EB3E94ADBE1229CF E: El repositorio «https://packages.microsoft.com/repos/edge stable InRelease» no está firmado. Vea la página de manual apt-secure(8) para los detalles sobre la creación de repositorios y la configuración de usuarios. W: El objetivo Sources (main/source/Sources) está configurado varias veces en /etc/apt/sources.list:2 y /etc/apt/sources.list:7 W: El objetivo Sources (main/source/Sources) está configurado varias veces en /etc/apt/sources.list:2 y /etc/apt/sources.list:7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1973472/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933027] Re: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled
Also hitting this issue after upgrade to Ubuntu 22.04. The proposed workaround doesn't work for me either. I always have a Yubikey 5 Nano plugged into my device. The workaround to be able to login is to remove the Yubikey, then I can use the username and password, very annoying procedure for each login. PS: By mistake I changed the status to "Fix Released" and not able to rollback. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1933027 Title: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Fix Released Bug description: I use my Ubuntu PC with Yubikey almost always plugged in. It provides several security token interfaces, such as U2F, GPG smartcard, proprieritary Yubico interfaces (of which I mostly use TOTP codes), and also PIV smartcard. However, I haven't configured a PIV smartcard on it. Whenever I login into the system having Yubikey plugged in, I'm prompted for login name, and then for PIN for some smartcard while also being asked to plug in one. This is very misleading on several layers: 1. I have the device providing smartcard plugged id, 2. But it's not the smartcard GDM would think it is as it's not configured properly, 3. There are no local smartcard-authenticating users right now in the system, 3. There are no remote authentication systems configured on the system (so no ActiveDirectory-smartcard logins or such). If I unplug the token UX goes back on old good track. Given the circumstances above, I'd consider that GDM (and, on my bet, any PAM configuration it uses) shouldn't offer to login using smartcard if there is no way to actually do so. I feel something is off here, so I'm reporting a bug. It could be an upstream problem though; it also could be an upstream SSSD problem, or all combined. I believe there is a more clear user experience: 1. GDM should display users that can login into the system, as it always does (if configured). It may also provide entering other login name (also if configured). This is GDM usually does without smartcards altogether. 2. When user is chosen (from the list or manually typed in), check can this user even authenticate with smartcards (i.e. if any of available smartcards is actually recognised for this user). If so, then ask for PIN. Else, don't show anything about smartcards at all (this includes when SSSD is not configured for any AD or related and this user has no local smartcard configuration). This can switch there & back based on device events. I've seen other OS doing this. Ubuntu/Gnome session doesn't ask me for PIN for a smartcard on a lock screen, so I guess it doesn't support it at all or correctly finds out it can't be used. Even more, I couldn't find a way to actually add my smartcard as a local login method. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jun 20 14:02:02 2021 InstallationDate: Installed on 2017-03-05 (1567 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to hirsute on 2021-05-13 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1933027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933027] Re: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1933027 Title: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Fix Released Bug description: I use my Ubuntu PC with Yubikey almost always plugged in. It provides several security token interfaces, such as U2F, GPG smartcard, proprieritary Yubico interfaces (of which I mostly use TOTP codes), and also PIV smartcard. However, I haven't configured a PIV smartcard on it. Whenever I login into the system having Yubikey plugged in, I'm prompted for login name, and then for PIN for some smartcard while also being asked to plug in one. This is very misleading on several layers: 1. I have the device providing smartcard plugged id, 2. But it's not the smartcard GDM would think it is as it's not configured properly, 3. There are no local smartcard-authenticating users right now in the system, 3. There are no remote authentication systems configured on the system (so no ActiveDirectory-smartcard logins or such). If I unplug the token UX goes back on old good track. Given the circumstances above, I'd consider that GDM (and, on my bet, any PAM configuration it uses) shouldn't offer to login using smartcard if there is no way to actually do so. I feel something is off here, so I'm reporting a bug. It could be an upstream problem though; it also could be an upstream SSSD problem, or all combined. I believe there is a more clear user experience: 1. GDM should display users that can login into the system, as it always does (if configured). It may also provide entering other login name (also if configured). This is GDM usually does without smartcards altogether. 2. When user is chosen (from the list or manually typed in), check can this user even authenticate with smartcards (i.e. if any of available smartcards is actually recognised for this user). If so, then ask for PIN. Else, don't show anything about smartcards at all (this includes when SSSD is not configured for any AD or related and this user has no local smartcard configuration). This can switch there & back based on device events. I've seen other OS doing this. Ubuntu/Gnome session doesn't ask me for PIN for a smartcard on a lock screen, so I guess it doesn't support it at all or correctly finds out it can't be used. Even more, I couldn't find a way to actually add my smartcard as a local login method. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jun 20 14:02:02 2021 InstallationDate: Installed on 2017-03-05 (1567 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to hirsute on 2021-05-13 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1933027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981724] Re: Update mutter to 42.3
This bug was fixed in the package mutter - 42.3-1ubuntu1 --- mutter (42.3-1ubuntu1) kinetic; urgency=medium * Merge from Debian unstable (LP: #1981724). Remaining changes: - Add triple-buffering patch - Add x11-Add-support-for-fractional-scaling-using-Randr.patch: + X11: Add support for fractional scaling using Randr - Add ubuntu/wayland-data-device-Allow-any-drag-timestamppatch + Allow any drag timestamp as drag start serial - Add backends-native-kms-crtc-Don-t-compare-gamma-values-on-un.patch + Avoid memory errors when comparing gamma values - Add monitor-manager-Ensure-monitors-settings-after-backend-ha.patch + Ensure privacy screen settings are applied on startup - Add patches from GNOME !2364 + Fix X11 selection related crash when Xwayland died - debian/libmutter-10-0.symbols: Add symbols for triple buffering patch * Drop patches applied in new release mutter (42.3-1) unstable; urgency=medium * New upstream release -- Jeremy Bicha Thu, 14 Jul 2022 17:26:15 +0200 ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1981724 Title: Update mutter to 42.3 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: In Progress Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/42.3/NEWS It's hoped that this update will be included in Ubuntu 22.04.1 LTS. Test Case - sudo apt install budgie-desktop gnome-session gnome-shell-extensions Install the update. Log out. Select your name on the login screen. Click the gear button to choose a session to log in to. Finish logging in. Verify that things continue to work well for all these sessions: Budgie GNOME GNOME Classic Ubuntu Ubuntu on Xorg What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1981724/+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 1963767] Re: Microphone not working after suspend
Actually I have tested it on a different laptop this time: Purism Libre 13 Version 4. So this shouldn't be laptop-specific either. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+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 1963767] Re: Microphone not working after suspend
Just tested the same Logitech BRIO on Ubuntu 22.04 LTS, still the same issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+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 1981602] Re: Update gnome-desktop to 42.3
This bug was fixed in the package gnome-desktop - 42.3-1 --- gnome-desktop (42.3-1) unstable; urgency=medium * New upstream release (LP: #1981602) -- Jeremy Bicha Wed, 13 Jul 2022 17:28:09 +0200 ** Changed in: gnome-desktop (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1981602 Title: Update gnome-desktop to 42.3 Status in gnome-desktop package in Ubuntu: Fix Released Status in gnome-desktop source package in Jammy: In Progress Bug description: Impact -- The only thing this update does is update the GNOME version number shown in the GNOME Settings > About dialog from 42.2 to 42.3 This is desired for Ubuntu 22.04.1 since we are mostly use GNOME 42.3 Test Case - Install the updated packages Open the Settings app. Scroll down in the left sidebar and click About The GNOME Version should be 42.3 What Could Go Wrong --- Because this is part of core GNOME, it falls under the https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1981602/+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 1981863] Re: gnome calendar does not sync with google calendar
And see this: https://askubuntu.com/questions/1411856/synchronization-issues-with-google-accounts-and-gnome-online-accounts -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1981863 Title: gnome calendar does not sync with google calendar Status in gnome-calendar package in Ubuntu: New Bug description: In the newest Ubuntu stable release (22.04), gnome 42.2, gnome calendar 41.2 does not sync calendar events from google calendar through GOA. But when an event is created in gnome calendar, it is synchronized with google calendar. So the synchronization works only in one direction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1981863/+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 1981863] Re: gnome calendar does not sync with google calendar
As I read in other forums, this works fine in Fedora. So this bug is Ubuntu specific. https://askubuntu.com/questions/1408669/gnome-calendar-not-working-in- ubuntu-22-04lts -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1981863 Title: gnome calendar does not sync with google calendar Status in gnome-calendar package in Ubuntu: New Bug description: In the newest Ubuntu stable release (22.04), gnome 42.2, gnome calendar 41.2 does not sync calendar events from google calendar through GOA. But when an event is created in gnome calendar, it is synchronized with google calendar. So the synchronization works only in one direction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1981863/+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 1981863] [NEW] gnome calendar does not sync with google calendar
Public bug reported: In the newest Ubuntu stable release (22.04), gnome 42.2, gnome calendar 41.2 does not sync calendar events from google calendar through GOA. But when an event is created in gnome calendar, it is synchronized with google calendar. So the synchronization works only in one direction. ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags: gnome-calendar google-online-account sync ** Tags added: gnome-calendar ** Tags added: google-online-account sync -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1981863 Title: gnome calendar does not sync with google calendar Status in gnome-calendar package in Ubuntu: New Bug description: In the newest Ubuntu stable release (22.04), gnome 42.2, gnome calendar 41.2 does not sync calendar events from google calendar through GOA. But when an event is created in gnome calendar, it is synchronized with google calendar. So the synchronization works only in one direction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1981863/+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 1872778] Re: update-crypto-policies not affecting Gnome Online Accounts
Thunderbird has gotten really balky, so I decided to try Evolution. Bad News. I have no trouble with Thunderbird, which Autoconfigures accounts nicely, but Evolution pops up this error, so I can NOT set up any accounts and my solution is: I'm NOT changing from Thunderbird. Evolution not working is NOT an option and I am NOT messing around wasting time to try to make it work. Linux Mint 20.2 Mate 64-bit LiveMedia in ROM (Locked Kanguru USB drive) Thunderbird78.8.1 (64-bit) Evolution 3.36.5-0ubuntu1 Art in Carlisle, PA USA -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1872778 Title: update-crypto-policies not affecting Gnome Online Accounts Status in gnome-online-accounts package in Ubuntu: Incomplete Status in gnutls28 package in Ubuntu: Confirmed Bug description: -crypto-policies 20190816git-1 -gnome-online-accounts 3.36.0-1ubuntu1 Changing between DEFAULT, LEGACY, and EMPTY has no affect on attempts to connect to accounts through Online Accounts. Changing to LEGACY or EMPTY should at least change the following error: Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough). Under either LEGACY or EMPTY the (not long enough) error is nonsensical. The persistence of the incorrect error message could imply that gnome-online-accounts is not respecting settings made by crypto-policies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1872778/+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 1981839] Re: Unable to save a bookmark
** Changed in: firefox (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1981839 Title: Unable to save a bookmark Status in firefox package in Ubuntu: Invalid Bug description: On Ubuntu 22.10 I'm unable to save a bookmark. Same problem with Firefox snap installed: 102.0.1-1 (1551) firefox-trunk: Installed: 104.0~a1~hg20220712r623561-0ubuntu0.22.10.1~umd1 both with X11 and Wayland session. After saving a bookmark the star on right of the bar becomes red, but bookmark does not appear in the bookmark list. corrado@corrado-n3-kk-0512:~$ inxi -Fxx System: Host: corrado-n3-kk-0512 Kernel: 5.15.0-27-generic arch: x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME v: 42.2 tk: GTK v: 3.24.34 wm: gnome-shell dm: GDM3 Distro: Ubuntu 22.10 (Kinetic Kudu) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Info: dual core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 800 min/max: 800/3900 cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 31199 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel arch: Gen9.5 ports: active: HDMI-A-1 empty: DP-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5912 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-7:4 chip-ID: 046d:0990 Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.2 compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: 0 Monitor-1: HDMI-A-1 model: LG (GoldStar) FULL HD res: 1920x1080 dpi: 102 diag: 551mm (21.7") OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 22.1.3 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel bus-ID: 1-7:4 v: kernel chip-ID: 046d:0990 bus-ID: 00:1f.3 chip-ID: 8086:a170 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo Sound Server-1: ALSA v: k5.15.0-27-generic running: yes Sound Server-2: PulseAudio v: 16.1 running: no Sound Server-3: PipeWire v: 0.3.53 running: yes Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 IF: enp0s31f6 state: down mac: 70:85:c2:44:7b:86 Device-2: Ralink RT2501/RT2573 Wireless Adapter type: USB driver: rt73usb bus-ID: 3-1.3.3:4 chip-ID: 148f:2573 IF: wlx000ee8f7f7e6 state: up mac: 00:0e:e8:f7:f7:e6 Drives: Local Storage: total: 2.05 TiB used: 34.8 GiB (1.7%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB speed: 31.6 Gb/s lanes: 4 serial: 50026B72823D1475 temp: 29.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB speed: 6.0 Gb/s serial: 21122DB99114 ID-3: /dev/sdb vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB speed: 6.0 Gb/s serial: 21122DA80425 ID-4: /dev/sdc vendor: Toshiba model: DT01ACA100 size: 931.51 GiB speed: 6.0 Gb/s serial: 37PYNGAFS Partition: ID-1: / size: 39.08 GiB used: 34.79 GiB (89.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 252 MiB used: 5.2 MiB (2.1%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda2 Sensors: System Temperatures: cpu: 29.0 C pch: 49.0 C mobo: 33.5 C Fan Speeds (RPM): fan-1: 0 fan-2: 2389 fan-3: 0 fan-4: 2500 fan-5: 0 fan-6: 0 Power: 12v: N/A 5v: N/A 3.3v: 3.41 vbat: 3.15 Info: Processes: 242 Uptime: 11h 5m Memory: 7.47 GiB used: 2.69 GiB (36.0%) Init: systemd v: 251 target: graphical (5) default: graphical Compilers: gcc: N/A Packages: 1901 apt: 1892 snap: 9 Shell: Bash v: 5.1.16 running-in: kgx inxi: 3.3.19 corrado@corrado-n3-kk-0512:~$ ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: firefox-trunk 104.0~a1~hg20220712r623561-0ubuntu0.22.10.1~umd1 [origin: LP-PPA-ubuntu-mozilla-daily] ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corrado 32626 F wireplumber /dev/snd/controlC1: corrado 32626 F wireplumber /dev/snd/seq:corrado 32623 F pipewire BuildID: 20220712070743 CasperMD5CheckResult: pass Channel: nightly CurrentDesktop: ubuntu:GNOME Date: Fri Jul
[Desktop-packages] [Bug 1981839] Re: Unable to save a bookmark
Thank you for taking the time to report this bug and help make Ubuntu better. Firefox is provided by a snap published by Mozilla, and they may not be aware of this issue. Please contact them via https://support.mozilla.org/kb/file-bug-report-or-feature-request- mozilla and link the bug report here so it can be further tracked. Thank you! ** Changed in: firefox (Ubuntu) Status: New => 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/1981839 Title: Unable to save a bookmark Status in firefox package in Ubuntu: Incomplete Bug description: On Ubuntu 22.10 I'm unable to save a bookmark. Same problem with Firefox snap installed: 102.0.1-1 (1551) firefox-trunk: Installed: 104.0~a1~hg20220712r623561-0ubuntu0.22.10.1~umd1 both with X11 and Wayland session. After saving a bookmark the star on right of the bar becomes red, but bookmark does not appear in the bookmark list. corrado@corrado-n3-kk-0512:~$ inxi -Fxx System: Host: corrado-n3-kk-0512 Kernel: 5.15.0-27-generic arch: x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME v: 42.2 tk: GTK v: 3.24.34 wm: gnome-shell dm: GDM3 Distro: Ubuntu 22.10 (Kinetic Kudu) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Info: dual core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 800 min/max: 800/3900 cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 31199 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel arch: Gen9.5 ports: active: HDMI-A-1 empty: DP-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5912 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-7:4 chip-ID: 046d:0990 Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.2 compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: 0 Monitor-1: HDMI-A-1 model: LG (GoldStar) FULL HD res: 1920x1080 dpi: 102 diag: 551mm (21.7") OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 22.1.3 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel bus-ID: 1-7:4 v: kernel chip-ID: 046d:0990 bus-ID: 00:1f.3 chip-ID: 8086:a170 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo Sound Server-1: ALSA v: k5.15.0-27-generic running: yes Sound Server-2: PulseAudio v: 16.1 running: no Sound Server-3: PipeWire v: 0.3.53 running: yes Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 IF: enp0s31f6 state: down mac: 70:85:c2:44:7b:86 Device-2: Ralink RT2501/RT2573 Wireless Adapter type: USB driver: rt73usb bus-ID: 3-1.3.3:4 chip-ID: 148f:2573 IF: wlx000ee8f7f7e6 state: up mac: 00:0e:e8:f7:f7:e6 Drives: Local Storage: total: 2.05 TiB used: 34.8 GiB (1.7%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB speed: 31.6 Gb/s lanes: 4 serial: 50026B72823D1475 temp: 29.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB speed: 6.0 Gb/s serial: 21122DB99114 ID-3: /dev/sdb vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB speed: 6.0 Gb/s serial: 21122DA80425 ID-4: /dev/sdc vendor: Toshiba model: DT01ACA100 size: 931.51 GiB speed: 6.0 Gb/s serial: 37PYNGAFS Partition: ID-1: / size: 39.08 GiB used: 34.79 GiB (89.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 252 MiB used: 5.2 MiB (2.1%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda2 Sensors: System Temperatures: cpu: 29.0 C pch: 49.0 C mobo: 33.5 C Fan Speeds (RPM): fan-1: 0 fan-2: 2389 fan-3: 0 fan-4: 2500 fan-5: 0 fan-6: 0 Power: 12v: N/A 5v: N/A 3.3v: 3.41 vbat: 3.15 Info: Processes: 242 Uptime: 11h 5m Memory: 7.47 GiB used: 2.69 GiB (36.0%) Init: systemd v: 251 target: graphical (5) default: graphical Compilers: gcc: N/A Packages: 1901 apt: 1892 snap: 9 Shell: Bash v: 5.1.16 running-in: kgx inxi: 3.3.19 corrado@corrado-n3-kk-0512:~$ ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: firefox-trunk 104.0~a1~hg20220712r623561-0ubuntu0.22.10.1~umd1 [origin: LP-PPA-ubuntu-mozilla-daily] ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64
[Desktop-packages] [Bug 1959507] Re: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f)
** Tags added: kinetic -- 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/1959507 Title: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f) Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hi, I'm starting a VM Ubuntu 22.04 on QEMU/KVM and this alert appears. It seems to myself there is an issue between Wayland and spice-vdagent. Regards, Michel ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 29 09:52:12 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-01-28 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 41.3-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: __pthread_kill_implementation (no_tid=0, signo=6, threadid=140083783699840) at pthread_kill.c:44 __pthread_kill_internal (signo=6, threadid=140083783699840) at pthread_kill.c:80 __GI___pthread_kill (threadid=140083783699840, signo=signo@entry=6) at pthread_kill.c:91 __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 __GI_abort () at abort.c:79 Title: gnome-shell crashed with SIGABRT in __pthread_kill_implementation() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959507/+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 1981839] Re: Unable to save a bookmark
That's fine, it happens. Is it OK if I mark this as Invalid, or is the problem still there? -- 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/1981839 Title: Unable to save a bookmark Status in firefox package in Ubuntu: Incomplete Bug description: On Ubuntu 22.10 I'm unable to save a bookmark. Same problem with Firefox snap installed: 102.0.1-1 (1551) firefox-trunk: Installed: 104.0~a1~hg20220712r623561-0ubuntu0.22.10.1~umd1 both with X11 and Wayland session. After saving a bookmark the star on right of the bar becomes red, but bookmark does not appear in the bookmark list. corrado@corrado-n3-kk-0512:~$ inxi -Fxx System: Host: corrado-n3-kk-0512 Kernel: 5.15.0-27-generic arch: x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME v: 42.2 tk: GTK v: 3.24.34 wm: gnome-shell dm: GDM3 Distro: Ubuntu 22.10 (Kinetic Kudu) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Info: dual core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 800 min/max: 800/3900 cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 31199 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel arch: Gen9.5 ports: active: HDMI-A-1 empty: DP-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5912 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-7:4 chip-ID: 046d:0990 Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.2 compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: 0 Monitor-1: HDMI-A-1 model: LG (GoldStar) FULL HD res: 1920x1080 dpi: 102 diag: 551mm (21.7") OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 22.1.3 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel bus-ID: 1-7:4 v: kernel chip-ID: 046d:0990 bus-ID: 00:1f.3 chip-ID: 8086:a170 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo Sound Server-1: ALSA v: k5.15.0-27-generic running: yes Sound Server-2: PulseAudio v: 16.1 running: no Sound Server-3: PipeWire v: 0.3.53 running: yes Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 IF: enp0s31f6 state: down mac: 70:85:c2:44:7b:86 Device-2: Ralink RT2501/RT2573 Wireless Adapter type: USB driver: rt73usb bus-ID: 3-1.3.3:4 chip-ID: 148f:2573 IF: wlx000ee8f7f7e6 state: up mac: 00:0e:e8:f7:f7:e6 Drives: Local Storage: total: 2.05 TiB used: 34.8 GiB (1.7%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB speed: 31.6 Gb/s lanes: 4 serial: 50026B72823D1475 temp: 29.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB speed: 6.0 Gb/s serial: 21122DB99114 ID-3: /dev/sdb vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB speed: 6.0 Gb/s serial: 21122DA80425 ID-4: /dev/sdc vendor: Toshiba model: DT01ACA100 size: 931.51 GiB speed: 6.0 Gb/s serial: 37PYNGAFS Partition: ID-1: / size: 39.08 GiB used: 34.79 GiB (89.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 252 MiB used: 5.2 MiB (2.1%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda2 Sensors: System Temperatures: cpu: 29.0 C pch: 49.0 C mobo: 33.5 C Fan Speeds (RPM): fan-1: 0 fan-2: 2389 fan-3: 0 fan-4: 2500 fan-5: 0 fan-6: 0 Power: 12v: N/A 5v: N/A 3.3v: 3.41 vbat: 3.15 Info: Processes: 242 Uptime: 11h 5m Memory: 7.47 GiB used: 2.69 GiB (36.0%) Init: systemd v: 251 target: graphical (5) default: graphical Compilers: gcc: N/A Packages: 1901 apt: 1892 snap: 9 Shell: Bash v: 5.1.16 running-in: kgx inxi: 3.3.19 corrado@corrado-n3-kk-0512:~$ ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: firefox-trunk 104.0~a1~hg20220712r623561-0ubuntu0.22.10.1~umd1 [origin: LP-PPA-ubuntu-mozilla-daily] ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corrado 32626 F wireplumber /dev/snd/controlC1: corrado 32626 F wireplumber /dev/snd/seq:corrado 32623 F pipewire BuildID: 20220712070743 CasperMD5CheckResult: pass Channel: nightly CurrentDesktop:
[Desktop-packages] [Bug 1981848] Re: gnome-shell crashed with SIGABRT
*** This bug is a duplicate of bug 1959507 *** https://bugs.launchpad.net/bugs/1959507 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1959507, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1981848/+attachment/5603370/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1981848/+attachment/5603372/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1981848/+attachment/5603377/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1981848/+attachment/5603378/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1981848/+attachment/5603379/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1981848/+attachment/5603381/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1981848/+attachment/5603382/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1959507 gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f) ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1981848 Title: gnome-shell crashed with SIGABRT Status in gnome-shell package in Ubuntu: New Bug description: In a Ubuntu Kinetic VM, gnome-shell crashed with SIGABRT a few seconds after reporting a bug about this. I am reporting this bug from the host system. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-shell 42.2-0ubuntu2 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 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Jul 15 19:02:55 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-06-26 (19 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220624) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 42.2-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libmutter-10.so.0 g_slist_foreach () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libmutter-10.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1981848/+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 1981849] Re: Xorg freeze
One more note: While booting, my external (USB) monitor was disconnected. -- 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/1981849 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Although I filed this against X11, this might be a kernel issue. I upgraded packages on 7/13/22 & rebooted today (7/15/22 -- I hadn't noted the "reboot required pop-up). After reboot, the screen was blank/black and unresponsive. Looking at indicator lights, I believe that the system had booted OK. The syslog supports this. Included in the update: xserver-xorg-core:amd64 2:1.20.13-1ubuntu1~20.04.3 linux-libc-dev:amd64 5.4.0-122.138 linux-image-5.15.0-41-generic:amd64 5.15.0-41.44~20.04.1 Repeated attempts to boot all ended the same -- blank unresponsive screen. I could boot in recovery mode and with the 5.13 kernel (which I'm running now and was used for the bug report). > lsb_release -a LSB Version: core-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch Distributor ID: Ubuntu Description: Ubuntu 20.04.4 LTS Release: 20.04 Code> uname -a Linux turk 5.13.0-52-generic #59~20.04.1-Ubuntu SMP Thu Jun 16 21:21:28 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux name: focal Again, note that the problem occurred when booting to the 5.15 kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 15 13:51:44 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: NVIDIA Corporation GM107GLM [Quadro M2000M] [10de:13b0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Dell GM107GLM [Quadro M2000M] [1028:16d9] InstallationDate: Installed on 2021-10-28 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Precision 7510 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-52-generic root=UUID=b611bb21-5970-4191-bf68-230392700099 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2021 dmi.bios.release: 1.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.25.3 dmi.board.name: 0M91XC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: 0010333 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.25.3:bd12/18/2021:br1.25:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn0M91XC:rvrA00:cvnDellInc.:ct9:cvr:sku06D9: dmi.product.family: Precision dmi.product.name: Precision 7510 dmi.product.sku: 06D9 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Fri Jul 15 10:40:20 2022 xserver.configfile: default xserver.errors: [drm] Failed to open DRM device for pci::01:00.0: -19 open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.13-1ubuntu1~20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1981849/+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 1981849] [NEW] Xorg freeze
Public bug reported: Although I filed this against X11, this might be a kernel issue. I upgraded packages on 7/13/22 & rebooted today (7/15/22 -- I hadn't noted the "reboot required pop-up). After reboot, the screen was blank/black and unresponsive. Looking at indicator lights, I believe that the system had booted OK. The syslog supports this. Included in the update: xserver-xorg-core:amd64 2:1.20.13-1ubuntu1~20.04.3 linux-libc-dev:amd64 5.4.0-122.138 linux-image-5.15.0-41-generic:amd64 5.15.0-41.44~20.04.1 Repeated attempts to boot all ended the same -- blank unresponsive screen. I could boot in recovery mode and with the 5.13 kernel (which I'm running now and was used for the bug report). > lsb_release -a LSB Version:core-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch Distributor ID: Ubuntu Description:Ubuntu 20.04.4 LTS Release:20.04 Code> uname -a Linux turk 5.13.0-52-generic #59~20.04.1-Ubuntu SMP Thu Jun 16 21:21:28 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux name: focal Again, note that the problem occurred when booting to the 5.15 kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 15 13:51:44 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: NVIDIA Corporation GM107GLM [Quadro M2000M] [10de:13b0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Dell GM107GLM [Quadro M2000M] [1028:16d9] InstallationDate: Installed on 2021-10-28 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Precision 7510 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-52-generic root=UUID=b611bb21-5970-4191-bf68-230392700099 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2021 dmi.bios.release: 1.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.25.3 dmi.board.name: 0M91XC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: 0010333 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.25.3:bd12/18/2021:br1.25:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn0M91XC:rvrA00:cvnDellInc.:ct9:cvr:sku06D9: dmi.product.family: Precision dmi.product.name: Precision 7510 dmi.product.sku: 06D9 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Fri Jul 15 10:40:20 2022 xserver.configfile: default xserver.errors: [drm] Failed to open DRM device for pci::01:00.0: -19 open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.13-1ubuntu1~20.04.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1981849 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Although I filed this against X11, this might be a kernel issue. I upgraded packages on 7/13/22 & rebooted today (7/15/22 -- I hadn't noted the "reboot required pop-up). After reboot, the screen was blank/black and unresponsive. Looking at indicator lights, I believe that the system had booted OK. The syslog supports this. Included in the update: xserver-xorg-core:amd64 2:1.20.13-1ubuntu1~20.04.3 linux-libc-dev:amd64 5.4.0-122.138 linux-image-5.15.0-41-generic:amd64 5.15.0-41.44~20.04.1 Repeated
[Desktop-packages] [Bug 1981349] Re: wslu prevents from opening files and folders on some situations
** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1981349 Title: wslu prevents from opening files and folders on some situations Status in wslu package in Ubuntu: New Bug description: With wslu installed, files and locations can't be opened from Gnome Activities View on a Wayland session or on a Xorg one. The same happens when I try to go to a location on Places Status Indicator.In fact, I filed a bug some time ago against this extension, but that bug was expired. Now I found the reason and then I create a bug report against the proper package. The bug report against Places Status Indicator is this one: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extensions/+bug/1970181 And I realized the cause of the bug against the extension when I saw this thread: https://answers.launchpad.net/ubuntu/+question/701579 Once I removed wslu from my system (on two different pc's) the problem with the extension has gone and I can open files and folders from Activities view. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1981349/+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 1981839] Re: Unable to save a bookmark
Sorry: MY ERROR I had 2 bookmarks folders with the same name!!! -- 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/1981839 Title: Unable to save a bookmark Status in firefox package in Ubuntu: New Bug description: On Ubuntu 22.10 I'm unable to save a bookmark. Same problem with Firefox snap installed: 102.0.1-1 (1551) firefox-trunk: Installed: 104.0~a1~hg20220712r623561-0ubuntu0.22.10.1~umd1 both with X11 and Wayland session. After saving a bookmark the star on right of the bar becomes red, but bookmark does not appear in the bookmark list. corrado@corrado-n3-kk-0512:~$ inxi -Fxx System: Host: corrado-n3-kk-0512 Kernel: 5.15.0-27-generic arch: x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME v: 42.2 tk: GTK v: 3.24.34 wm: gnome-shell dm: GDM3 Distro: Ubuntu 22.10 (Kinetic Kudu) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Info: dual core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 800 min/max: 800/3900 cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 31199 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel arch: Gen9.5 ports: active: HDMI-A-1 empty: DP-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5912 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-7:4 chip-ID: 046d:0990 Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.2 compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: 0 Monitor-1: HDMI-A-1 model: LG (GoldStar) FULL HD res: 1920x1080 dpi: 102 diag: 551mm (21.7") OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 22.1.3 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel bus-ID: 1-7:4 v: kernel chip-ID: 046d:0990 bus-ID: 00:1f.3 chip-ID: 8086:a170 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo Sound Server-1: ALSA v: k5.15.0-27-generic running: yes Sound Server-2: PulseAudio v: 16.1 running: no Sound Server-3: PipeWire v: 0.3.53 running: yes Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 IF: enp0s31f6 state: down mac: 70:85:c2:44:7b:86 Device-2: Ralink RT2501/RT2573 Wireless Adapter type: USB driver: rt73usb bus-ID: 3-1.3.3:4 chip-ID: 148f:2573 IF: wlx000ee8f7f7e6 state: up mac: 00:0e:e8:f7:f7:e6 Drives: Local Storage: total: 2.05 TiB used: 34.8 GiB (1.7%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB speed: 31.6 Gb/s lanes: 4 serial: 50026B72823D1475 temp: 29.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB speed: 6.0 Gb/s serial: 21122DB99114 ID-3: /dev/sdb vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB speed: 6.0 Gb/s serial: 21122DA80425 ID-4: /dev/sdc vendor: Toshiba model: DT01ACA100 size: 931.51 GiB speed: 6.0 Gb/s serial: 37PYNGAFS Partition: ID-1: / size: 39.08 GiB used: 34.79 GiB (89.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 252 MiB used: 5.2 MiB (2.1%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda2 Sensors: System Temperatures: cpu: 29.0 C pch: 49.0 C mobo: 33.5 C Fan Speeds (RPM): fan-1: 0 fan-2: 2389 fan-3: 0 fan-4: 2500 fan-5: 0 fan-6: 0 Power: 12v: N/A 5v: N/A 3.3v: 3.41 vbat: 3.15 Info: Processes: 242 Uptime: 11h 5m Memory: 7.47 GiB used: 2.69 GiB (36.0%) Init: systemd v: 251 target: graphical (5) default: graphical Compilers: gcc: N/A Packages: 1901 apt: 1892 snap: 9 Shell: Bash v: 5.1.16 running-in: kgx inxi: 3.3.19 corrado@corrado-n3-kk-0512:~$ ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: firefox-trunk 104.0~a1~hg20220712r623561-0ubuntu0.22.10.1~umd1 [origin: LP-PPA-ubuntu-mozilla-daily] ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corrado 32626 F wireplumber /dev/snd/controlC1: corrado 32626 F wireplumber /dev/snd/seq:corrado 32623 F pipewire BuildID: 20220712070743 CasperMD5CheckResult: pass Channel: nightly CurrentDesktop: ubuntu:GNOME Date: Fri Jul 15
[Desktop-packages] [Bug 1981839] [NEW] Unable to save a bookmark
Public bug reported: On Ubuntu 22.10 I'm unable to save a bookmark. Same problem with Firefox snap installed: 102.0.1-1 (1551) firefox-trunk: Installed: 104.0~a1~hg20220712r623561-0ubuntu0.22.10.1~umd1 both with X11 and Wayland session. After saving a bookmark the star on right of the bar becomes red, but bookmark does not appear in the bookmark list. corrado@corrado-n3-kk-0512:~$ inxi -Fxx System: Host: corrado-n3-kk-0512 Kernel: 5.15.0-27-generic arch: x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME v: 42.2 tk: GTK v: 3.24.34 wm: gnome-shell dm: GDM3 Distro: Ubuntu 22.10 (Kinetic Kudu) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Info: dual core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 800 min/max: 800/3900 cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 31199 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel arch: Gen9.5 ports: active: HDMI-A-1 empty: DP-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5912 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-7:4 chip-ID: 046d:0990 Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.2 compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: 0 Monitor-1: HDMI-A-1 model: LG (GoldStar) FULL HD res: 1920x1080 dpi: 102 diag: 551mm (21.7") OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 22.1.3 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel bus-ID: 1-7:4 v: kernel chip-ID: 046d:0990 bus-ID: 00:1f.3 chip-ID: 8086:a170 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo Sound Server-1: ALSA v: k5.15.0-27-generic running: yes Sound Server-2: PulseAudio v: 16.1 running: no Sound Server-3: PipeWire v: 0.3.53 running: yes Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 IF: enp0s31f6 state: down mac: 70:85:c2:44:7b:86 Device-2: Ralink RT2501/RT2573 Wireless Adapter type: USB driver: rt73usb bus-ID: 3-1.3.3:4 chip-ID: 148f:2573 IF: wlx000ee8f7f7e6 state: up mac: 00:0e:e8:f7:f7:e6 Drives: Local Storage: total: 2.05 TiB used: 34.8 GiB (1.7%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB speed: 31.6 Gb/s lanes: 4 serial: 50026B72823D1475 temp: 29.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB speed: 6.0 Gb/s serial: 21122DB99114 ID-3: /dev/sdb vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB speed: 6.0 Gb/s serial: 21122DA80425 ID-4: /dev/sdc vendor: Toshiba model: DT01ACA100 size: 931.51 GiB speed: 6.0 Gb/s serial: 37PYNGAFS Partition: ID-1: / size: 39.08 GiB used: 34.79 GiB (89.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 252 MiB used: 5.2 MiB (2.1%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda2 Sensors: System Temperatures: cpu: 29.0 C pch: 49.0 C mobo: 33.5 C Fan Speeds (RPM): fan-1: 0 fan-2: 2389 fan-3: 0 fan-4: 2500 fan-5: 0 fan-6: 0 Power: 12v: N/A 5v: N/A 3.3v: 3.41 vbat: 3.15 Info: Processes: 242 Uptime: 11h 5m Memory: 7.47 GiB used: 2.69 GiB (36.0%) Init: systemd v: 251 target: graphical (5) default: graphical Compilers: gcc: N/A Packages: 1901 apt: 1892 snap: 9 Shell: Bash v: 5.1.16 running-in: kgx inxi: 3.3.19 corrado@corrado-n3-kk-0512:~$ ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: firefox-trunk 104.0~a1~hg20220712r623561-0ubuntu0.22.10.1~umd1 [origin: LP-PPA-ubuntu-mozilla-daily] ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corrado 32626 F wireplumber /dev/snd/controlC1: corrado 32626 F wireplumber /dev/snd/seq:corrado 32623 F pipewire BuildID: 20220712070743 CasperMD5CheckResult: pass Channel: nightly CurrentDesktop: ubuntu:GNOME Date: Fri Jul 15 17:47:26 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox-trunk/omni.ja:greprefs.js:301 DefaultProfilePrefSources: /usr/lib/firefox-trunk/defaults/pref/vendor-gre.js
[Desktop-packages] [Bug 1981837] [NEW] Using DiNG triggers ubuntu-dock opacity
Public bug reported: Hi, Ubuntu 22.04 LTS jammy Linux 5.15.0-40-generic x86_64 x86_64 ubuntu-xorg / x11 I prefer panel and dock to become fully opaque only when windows are maximized. So I use this extension for panel : Transparent Top Bar (Adjustable transparency) which JustWorks™ in both Xorg and Wayland. In ubuntu-dock, dynamic-transparency is set through dconf-editor ( transparency-mode, min-alpha, max-alpha. ) When using DiNG under Wayland, opacity is triggered as if « desktop » was considered as a maximized window. Under Xorg, DiNG does not trigger dock opacity, as expected. ** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/1981837 Title: Using DiNG triggers ubuntu-dock opacity Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Bug description: Hi, Ubuntu 22.04 LTS jammy Linux 5.15.0-40-generic x86_64 x86_64 ubuntu-xorg / x11 I prefer panel and dock to become fully opaque only when windows are maximized. So I use this extension for panel : Transparent Top Bar (Adjustable transparency) which JustWorks™ in both Xorg and Wayland. In ubuntu-dock, dynamic-transparency is set through dconf-editor ( transparency-mode, min-alpha, max-alpha. ) When using DiNG under Wayland, opacity is triggered as if « desktop » was considered as a maximized window. Under Xorg, DiNG does not trigger dock opacity, as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1981837/+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 1971051] Re: Minimize window animation artefacts
*** This bug is a duplicate of bug 1969140 *** https://bugs.launchpad.net/bugs/1969140 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1971051 Title: Minimize window animation artefacts Status in xorg package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 AMD rx-460 card. Minimize window animation artefacts. Occurs in about 70% of cases when the application window is minimized. A demonstration of the problem is on the screencast - https://disk.yandex.ru/i/GdSWT1-LO2i7kA ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 30 21:40:13 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] [1002:67ef] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] [1462:809d] InstallationDate: Installed on 2022-04-30 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7A38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=185613a0-8b25-4d40-9d32-b0dbac7e4bf1 ro quiet splash amdgpu.dc=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: B.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M PRO-VDH MAX (MS-7A38) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 8.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 8.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrB.C0:bd05/14/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A38:pvr8.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-VDHMAX(MS-7A38):rvr8.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr8.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A38 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 8.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1971051/+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 1979053] Re: UI glitches (coloured squares) in GTK application with AMDGPU
Ok, I created this issue: https://gitlab.freedesktop.org/drm/amd/-/issues/2088 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2088 https://gitlab.freedesktop.org/drm/amd/-/issues/2088 -- 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/1979053 Title: UI glitches (coloured squares) in GTK application with AMDGPU Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: After updating to (K)ubuntu 22.04, I see user interface glitches in GTK application. Most obviously affected is Gimp, but Evolution and Eclipse IDE are affected, too. The glitches don't appear on a notebook with Intel graphics, so maybe the problem is caused by a weird interaction between the AMDGPU X.Org driver (I use a Radeon RX5600XT) and GTK. But as the KDE desktop itself isn't affected and only GTK application show these glitches, I think it's not a general problem with AMDGPU. I also booted both Kubunutu and Ubuntu live images and installed Gimp: The effect shows up there, too. So it's not only a problem of my current installation. I will upload some Gimp screenshots, so you can see what I mean... I'm not sure, but I tried to find the library used by all affected application: Maybe it's libcairo2, maybe not... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libcairo2 1.16.0-5ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Jun 17 12:36:26 2022 InstallationDate: Installed on 2022-04-27 (50 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: cairo UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: stieler1622 F pulseaudio /dev/snd/pcmC3D0p: stieler1622 F...m pulseaudio /dev/snd/controlC2: stieler1622 F pulseaudio /dev/snd/controlC1: stieler1622 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: jammy DistroRelease: Ubuntu 22.04 DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev ca) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [148c:2402] InstallationDate: Installed on 2022-04-27 (55 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7B98 Package: mesa (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=2186bb5d-f2f0-4775-97ef-066ee5c2d05d ro quiet splash nosgx vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Tags: jammy ubuntu Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/17/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.E1 dmi.board.asset.tag: Default string dmi.board.name: Z390-A PRO (MS-7B98) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.E1:bd11/17/2021:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7B98 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri
[Desktop-packages] [Bug 1716301] Re: wifi driver: mt7601u not work on 16.04
Thank you for reporting this bug to Ubuntu. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. (reverted; duplicate report https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885985 shows focal) ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch-data in Ubuntu. https://bugs.launchpad.net/bugs/1716301 Title: wifi driver: mt7601u not work on 16.04 Status in linux package in Ubuntu: Confirmed Status in usb-modeswitch-data package in Ubuntu: Confirmed Bug description: In the beginning, when the adapter is pluged in, it's mounted as a disk including driver files for Windows, and $> lsusb Bus 003 Device 010: ID 148f:2878 Ralink Technology, Corp. after eject the disk, $> lsusb Bus 003 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter I tried following 3 drivers: 1) the default mt7601u included in the kernel: 4.4.0-91-generic after eject the disk, $> lsmod|grep mt mt7601u 102400 0 mac80211 737280 1 mt7601u cfg80211 565248 2 mac80211,mt7601u binfmt_misc 20480 1 $> modinfo mt7601u filename: /lib/modules/4.4.0-91-generic/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko srcversion: E8B632D369E0C2A9F1CF7D8 alias: usb:v7392p7710d*dc*dsc*dp*ic*isc*ip*in* .. depends: mac80211,cfg80211 intree: Y vermagic: 4.4.0-91-generic SMP mod_unload modversions $> dmesg // begin [ 4581.094119] usb 3-4: USB disconnect, device number 6 [ 4584.872751] usb 3-4: new high-speed USB device number 7 using xhci_hcd [ 4585.001408] usb 3-4: New USB device found, idVendor=148f, idProduct=2878 [ 4585.001413] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4585.001416] usb 3-4: Product: Љ [ 4585.001418] usb 3-4: Manufacturer: Љ [ 4585.001753] usb-storage 3-4:1.0: USB Mass Storage device detected [ 4585.001873] scsi host6: usb-storage 3-4:1.0 [ 4586.001122] scsi 6:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 CCS [ 4586.001978] sr 6:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray [ 4586.002529] sr 6:0:0:0: Attached scsi CD-ROM sr0 [ 4586.002716] sr 6:0:0:0: Attached scsi generic sg1 type 5 [ 4619.658385] ISO 9660 Extensions: Microsoft Joliet Level 3 [ 4619.691737] ISOFS: changing to secondary root [ 4691.563347] usb 3-4: USB disconnect, device number 7 [ 4693.638315] usb 3-4: new high-speed USB device number 8 using xhci_hcd [ 4693.766896] usb 3-4: New USB device found, idVendor=148f, idProduct=2878 [ 4693.766901] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4693.766903] usb 3-4: Product: Љ [ 4693.766905] usb 3-4: Manufacturer: Љ [ 4693.767338] usb-storage 3-4:1.0: USB Mass Storage device detected [ 4693.768063] scsi host7: usb-storage 3-4:1.0 [ 4694.766737] scsi 7:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 CCS [ 4694.767423] sr 7:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray [ 4694.767908] sr 7:0:0:0: Attached scsi CD-ROM sr0 [ 4694.768147] sr 7:0:0:0: Attached scsi generic sg1 type 5 [ 4728.418255] ISO 9660 Extensions: Microsoft Joliet Level 3 [ 4728.427856] ISOFS: changing to secondary root [ 4733.824182] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 4733.824190] sr 7:0:0:0: [sr0] tag#0 CDB: Start/Stop Unit 1b 00 00 00 02 00 [ 4733.824218] usb 3-4: USB disconnect, device number 8 [ 4733.824281] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 4733.824291] sr 7:0:0:0: [sr0] tag#0 CDB: Prevent/Allow Medium Removal 1e 00 00 00 00 00 [ 4734.099901] usb 3-4: new high-speed USB device number 9 using xhci_hcd [ 4734.238749] usb 3-4: New USB device found, idVendor=148f, idProduct=7601 [ 4734.238754] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4734.238757] usb 3-4: Product: 802.11 n WLAN [ 4734.238772] usb 3-4: Manufacturer: MediaTek [ 4734.238775] usb 3-4: SerialNumber: 1.0 [ 4735.432096] usb 3-4: reset high-speed USB device number 9 using xhci_hcd [ 4735.562543] mt7601u 3-4:1.0: ASIC revision: 76010001 MAC revision: 76010500 [ 4735.563089] mt7601u 3-4:1.0: Firmware Version: 0.1.00 Build: 7640 Build time: 201302052146 [ 4739.011624] mt7601u 3-4:1.0: Vendor request req:07 off:09a8 failed:-110 [ 4742.131399] mt7601u 3-4:1.0: Vendor request req:02 off:09a8 failed:-110 [ 4745.251254] mt7601u 3-4:1.0: Vendor request
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
I tried this https://launchpad.net/~nteodosio/+snap/chromium-browser-
hwacc/+build/1821034
Good snap package, my old N3450 works.
##
Gtk-Message: 17:56:38.503: Failed to load module "canberra-gtk-module"
Gtk-Message: 17:56:38.507: Failed to load module "canberra-gtk-module"
[16395:16490:0715/175638.574596:ERROR:object_proxy.cc(623)] Failed to call
method: org.freedesktop.DBus.ListActivatableNames: object_path=
/org/freedesktop/DBus: org.freedesktop.DBus.Error.AccessDenied: An AppArmor
policy prevents this sender from sending this message to this recipient;
type="method_call", sender=":1.188" (uid=1000 pid=16395
comm="/snap/chromium/x1/usr/lib/chromium-browser/chrome "
label="snap.chromium.chromium (enforce)") interface="org.freedesktop.DBus"
member="ListActivatableNames" error name="(unset)" requested_reply="0"
destination="org.freedesktop.DBus" (bus)
[16395:16395:0715/175638.601987:WARNING:account_consistency_mode_manager.cc(70)]
Desktop Identity Consistency cannot be enabled as no OAuth client ID and
client secret have been configured.
libva info: VA-API version 1.14.0
libva info: Trying to open
/snap/chromium/x1/usr/lib/x86_64-linux-gnu/dri//iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_14
libva info: va_openDriver() returns 0
[16503:16503:0715/175638.861107:WARNING:sandbox_linux.cc(376)]
InitializeSandbox() called with multiple threads in process gpu-process.
WARNING: Kernel has no file descriptor comparison support: Operation not
permitted
[16395:16395:0715/175639.046619:WARNING:bluez_dbus_manager.cc(247)] Floss
manager not present, cannot set Floss enable/disable.
[16503:16503:0715/175639.744267:WARNING:angle_platform_impl.cc(48)]
MemoryProgramCache.cpp:174 (getProgram): Failed to load binary from cache.
[16503:16503:0715/175639.748909:WARNING:angle_platform_impl.cc(48)]
MemoryProgramCache.cpp:174 (getProgram): Failed to load binary from cache.
[16395:16484:0715/175642.349375:ERROR:udev_watcher.cc(98)] Failed to begin udev
enumeration.
^C[16395:16395:0715/175649.380723:INFO:render_frame_host_impl.cc(11505)]
RenderFrameHostImpl::MaybeGenerateCrashReport url = , status = 4, exit_code = 0
[16395:16395:0715/175649.541305:WARNING:pref_notifier_impl.cc(41)] Pref
observer for media_router.cast_allow_all_ips found at shutdown.
###
My T460P because of Nvida CPU, does not work, the same as before.
Thank you for help. I at least do not need take time on the old PC.
Install and works, that is what I wanted.
--
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:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the snap with
sudo snap install --channel candidate/hwacc chromium
2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
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;
- Distro version (if in doubt, `grep VERSION= /etc/os_release`);
- GPU (if in doubt, attach the output of `lscpu`);
- CPU generation (if in doubt, attach the output of `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 :
[Desktop-packages] [Bug 1981761] Re: Settings -> Sound sets conflicting sample rates for Playback and Capture
Thank you for your bug report. Could you also submit it upstream on https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/ ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1981761 Title: Settings -> Sound sets conflicting sample rates for Playback and Capture Status in pulseaudio package in Ubuntu: New Bug description: I've looked around but cannot figure out where this problem originates, but if I go into Ubuntu Settings -> Sound, and set both Output Device and Input Device to my USB Audio device, it starts showing a level meter, recording at 44100 Hz. If I then press the Test button for the Output Device, it plays at 48000 Hz: ~> cat /proc/asound/card1/pcm0p/sub0/hw_params access: MMAP_INTERLEAVED format: S16_LE subformat: STD channels: 2 rate: 48000 (48000/1) period_size: 44100 buffer_size: 88200 ~> cat /proc/asound/card1/pcm0c/sub0/hw_params access: MMAP_INTERLEAVED format: S16_LE subformat: STD channels: 2 rate: 44100 (44100/1) period_size: 44100 buffer_size: 88200 My hardware cannot handle different input and output sample rates at the same time. It should pick one or the other and use it for both. macOS always uses the same sample rate for the entire device, for instance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1981761/+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 1969709] Re: libreoffice font selection unusably slow
Okay so we know we have a bug. Is this just going to sit here forever without further investigation and resolution? Ubuntu took Debian's testing fontconfig package and patched it without any change log. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1969709 Title: libreoffice font selection unusably slow Status in fontconfig package in Ubuntu: New Status in libreoffice package in Ubuntu: Confirmed Bug description: Trying to scroll through the font list in the menu bar, I experience an unacceptable degree of lagging. Just popping up the dropdown list takes 7-10 seconds and the system takes the same amount of time to respond to perform individidual scrolling gestures. The CPU jumps to 100% and the whole system becomes unresponsive. I have tried deb, snap and even the packages offered on the site of the LibreOffice project. They all manifest the same behaviour. The only thing that works is disabling font previews. I have downgraded to 7.2 for now, which appears to be unaffected. I have contacted the LibreOffice team and they tell me that this should be solved by fontconfig 2.14. Unfortunately, Ubuntu 22.04 is shipping 2.13... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-core 1:7.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 05:01:24 2022 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2022-03-27 (24 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1969709/+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 means chromium is bind the old libva 2.6. It is a little strange.
Not really. It's just that the vainfo bundled in the snap is from the
focal deb which is 2.6 and what it reports as 'libva version' is just
its own version. If you wget the vainfo from impish in the snap it will
tell libva 2.10.
We should remove vainfo from the snap, it's just confusing. The libva
version now is correct and chromium is correctly loading 2.14 despite
what vainfo is reporting
> Current both my two machines are unable to work with the good snap
package. But the native chromium version could.
Could you give details on that. Is Chromium failing to use VDA for you
even use --disable-features=UseChromeOSDirectVideoDecoder (which you
didn't it seems in your previous comments?). If so could you copy the
output of the command and maybe the log from --enable-logging=stderr ?
--
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:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the snap with
sudo snap install --channel candidate/hwacc chromium
2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
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;
- Distro version (if in doubt, `grep VERSION= /etc/os_release`);
- GPU (if in doubt, attach the output of `lscpu`);
- CPU generation (if in doubt, attach the output of `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 1971001] Re: Multiple vulnerabilities in Trusty, Xenial, Bionic, Focal and Jammy
Impish reached end-of-life yesterday. ** Summary changed: - Multiple vulnerabilities in Trusty, Xenial, Bionic, Focal, Impish and Jammy + Multiple vulnerabilities in Trusty, Xenial, Bionic, Focal and Jammy ** Description changed: - The versions in Trusty, Xenial, Bionic, Focal, Impish and Jammy may be + The versions in Trusty, Xenial, Bionic, Focal and Jammy may be vulnerable to all CVEs below. Debian released an advisory on March 24. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1971001 Title: Multiple vulnerabilities in Trusty, Xenial, Bionic, Focal and Jammy Status in tiff package in Ubuntu: In Progress Bug description: The versions in Trusty, Xenial, Bionic, Focal and Jammy may be vulnerable to all CVEs below. Debian released an advisory on March 24. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1971001/+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
