[Desktop-packages] [Bug 1967182] [NEW] windows change desktop after lock screen
Public bug reported: Hello, So I have a dual screen setup where my primary monitor isn't the laptop built-in but an external wide screen. So I would have 2 or 3 virtual desktop with various content organized (mail, development, personal) After a long break with the screen locked when I come back to my computer, my windows have moved from Virtual desktop to another and sometime from one monitor to another. let me know if you need more information Matthieu ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 30 16:44:57 2022 DisplayManager: gdm3 InstallationDate: Installed on 2020-01-05 (815 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-01-27 (62 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages uec-images wayland-session -- 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/1967182 Title: windows change desktop after lock screen Status in gnome-shell package in Ubuntu: New Bug description: Hello, So I have a dual screen setup where my primary monitor isn't the laptop built-in but an external wide screen. So I would have 2 or 3 virtual desktop with various content organized (mail, development, personal) After a long break with the screen locked when I come back to my computer, my windows have moved from Virtual desktop to another and sometime from one monitor to another. let me know if you need more information Matthieu ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 30 16:44:57 2022 DisplayManager: gdm3 InstallationDate: Installed on 2020-01-05 (815 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-01-27 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967182/+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 1967593] Re: kernel modules going missing after reboot
** Tags added: fr-2225 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1967593 Title: kernel modules going missing after reboot Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: EDIT: There are no accurate results in the package search, but it is for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it is not kernel specific. It must be a problem with configuration, but reinstalling doesnt fix it. EDIT2: it turns out this is caused by the cloud-initramfs-copymods package mounting over modules locations. Removed it and reinstalled kernel modules package (extras didnt seem necessary, but probably prudent too). This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_h
[Desktop-packages] [Bug 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04
** Tags added: fr-2226 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1926860 Title: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04 Status in systemd package in Ubuntu: In Progress Status in xserver-xorg-input-libinput package in Ubuntu: Invalid Status in xserver-xorg-input-libinput package in Arch Linux: New Bug description: The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no longer working in any other Version of Ubuntu released afterwards. I tested 20.04 and am currently running 21.04. it is recognized but in the system settings it says not tablet and not stylus found. The terminal gives me the info that the UC-Logic TABLET 1060N is plugged in. In the system settings it shows "Wacom Tablet" but says not tablet and stylus pen are recognized. It works perfectly fine on my 18.04 install. I found a few reports on the internet with the exact same issue. They installed some evdev driver and somehow managed to resolve. I was not able to do so yet. If the tablet used to work out of the box with Ubuntu 18.04 I wonder why it is no longer working. There is also a XP Pen Star 03 V2 by now. The tablet look identical but the hardware or firmware must be different. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 2 03:16:00 2021 InstallationDate: Installed on 2021-04-15 (16 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926860/+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 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container
** Tags added: fr-2592 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1981109 Title: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container Status in fwupd package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: New Status in fwupd source package in Jammy: Invalid Status in livecd-rootfs source package in Jammy: Triaged Status in modemmanager source package in Jammy: New Status in ubuntu-meta source package in Jammy: New Bug description: Looking at memory utilization in a pristine Ubuntu lxd container (top -o RES), I see that ModemManager is running, which I was surprised to see is present at all in the stock image. Tracking this I find that fwupd depends on libmm-glib0, which in turn Recommends: modemmanager. Libraries in general should not recommend daemons, so it's possible this should be fixed by libmm-glib0 dropping this Recommends. It certainly doesn't seem to be a deliberate decision by the Server Team to have modemmanager installed and running by default on all systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+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 1974483] Re: autoinstall ssh:install-server:false is misleading in 22.04
** Tags added: foundations-todo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1974483 Title: autoinstall ssh:install-server:false is misleading in 22.04 Status in subiquity: Triaged Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-meta source package in Jammy: Confirmed Bug description: With 22.04, openssh-server is baked into the image curtin copies to the target. The ssh:install-server key no longer controls whether openssh-server gets installed. It should be easy enough to have the bit of code that installs openssh-server when the key is true also remove it when the key is false. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1974483/+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 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container
** Tags added: foundations-todo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1981109 Title: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container Status in fwupd package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: New Status in fwupd source package in Jammy: Invalid Status in livecd-rootfs source package in Jammy: Triaged Status in modemmanager source package in Jammy: New Status in ubuntu-meta source package in Jammy: New Bug description: Looking at memory utilization in a pristine Ubuntu lxd container (top -o RES), I see that ModemManager is running, which I was surprised to see is present at all in the stock image. Tracking this I find that fwupd depends on libmm-glib0, which in turn Recommends: modemmanager. Libraries in general should not recommend daemons, so it's possible this should be fixed by libmm-glib0 dropping this Recommends. It certainly doesn't seem to be a deliberate decision by the Server Team to have modemmanager installed and running by default on all systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+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 1891623] Re: LO segfaults in one test on armhf when built with GCC 10
** Tags added: fr-208 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1891623 Title: LO segfaults in one test on armhf when built with GCC 10 Status in gcc-10 package in Ubuntu: Invalid Status in libreoffice package in Ubuntu: Incomplete Status in gcc-10 source package in Groovy: Invalid Status in libreoffice source package in Groovy: Incomplete Bug description: I don't think we've had a successful build of Libreoffce on armhf in Ubuntu since gcc-10, it always eventually segfaults after 24 hours or so /<>/toolkit/source/controls/tkscrollbar.cxx: In member function ‘virtual void toolkit::UnoScrollBarControl::adjustmentValueChanged(const com::sun::star::awt::AdjustmentEvent&)’: /<>/toolkit/source/controls/tkscrollbar.cxx:175:5: internal compiler error: Segmentation fault 175 | } | ^ Please submit a full bug report, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1891623/+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 1726124] Re: DNS domain search paths not updated when VPN started
** Tags added: fr-13 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1726124 Title: DNS domain search paths not updated when VPN started Status in network-manager package in Ubuntu: Confirmed Status in network-manager-openvpn package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I connect to work with openvpn through network-manager-openvpn. I'm selecting automatic (DHCP) to get an IP address, and "Use this connection only for resources on its network" to support split tunneling. In the last few versions of Ubuntu I used, this all worked fine. In Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both my VPN network and the internet, BUT I have to use FQDN for my VPN network hosts: the updates to the DNS search path provided by my VPN DHCP server are never being applied. Investigating the system I see that /etc/resolv.conf is pointing to /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not have any of the VPN's search path settings in it: # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home In previous versions of Ubuntu, where NetworkManager controlled the resolver not systemd, /etc/resolv.conf pointed to /run/NetworkManager/resolv.conf and there was a local dnsmasq instance that managed all the complexity. In Ubuntu 17.10 when I look in /run/NetworkManager/resolv.conf file, I see that the search paths ARE properly updated there: $ cat /run/NetworkManager/resolv.conf # Generated by NetworkManager search internal.mycorp.com other.mycorp.com home nameserver 127.0.1.1 However this file isn't being used, and also there's no dnsmasq running on the system so if I switch my /etc/resolv.conf to point to this file instead, then all lookups fail. Strangely, if I look at the systemd-resolv status I see that in theory systemd-resolve does seem to know about the proper search paths: $ systemd-resolve --status ... Link 3 (tun0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 10.3.0.10 10.8.42.2 DNS Domain: ~internal.mycorp.com ~other.mycorp.com but for whatever reason the search domains are not getting put into the resolv.conf file: $ host mydesk ;; connection timed out; no servers could be reached $ host mydesk.internal.mycorp.com mydesk.internal.mycorp.com has address 10.8.37.74 (BTW, the timeout in the failed attempt above takes 10s: it is SUPER frustrating when all your host lookups are taking that long just to fail). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 22 15:08:57 2017 InstallationDate: Installed on 2017-10-21 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about thi
[Desktop-packages] [Bug 1807749] Re: NFS V4 does not mount at system start
** Tags added: fr-631 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1807749 Title: NFS V4 does not mount at system start Status in network-manager package in Ubuntu: Triaged Status in systemd package in Ubuntu: New Bug description: Hi, i'm running a view Ubuntu 18.10 Clients on a Ubuntu 18.04 NFS V4 Server. I'm using Kerberos for user authentication and LDAP for user and group synchronisation. The shares are added to the /etc/fstab on my clients and they should be mounted automatically at system boot. Here is an example line from fstab: nfs.server:/users /home nfs4 sec=krb5i,soft,_netdev,auto 0 0 But after the system has booted and the Login-Screen appears the nfs shares are not mounted on the client. Attached to this bug, you can find an export of my journald entries from my last boot. When I read this log carefully I find the following start order of relevant services: Begin start nss_ldap (from line 822 on) Begin start NetworkManager (from line 1198) Get IP from DHCP (line 2542) NetworkManager Online (line 2551) Try to mount NFS Shares (from line 2253) nss_ldap connected (line 2761) As far as I understand my setup, I do not have DNS before nss_ldap is started. But since mounting the NFS shares needs DNS, the NFS mount sequence should start after nss_ldap is fully started. Thanks for your help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1807749/+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 1821415] Re: pkexec fails in a non-graphical environment
** Tags added: fr-279 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1821415 Title: pkexec fails in a non-graphical environment Status in PolicyKit: New Status in apport package in Ubuntu: Triaged Status in policykit-1 package in Ubuntu: Triaged Bug description: The plymouth apport source package hooks wants to gather log files as the root user and apport provides a policy kit policy for collecting that information. This works fine in a graphical environment but not in a non-graphical one. N.B. you first need to create a /var/log/plymouth-debug.log file for the plymouth apport package hook to actually trigger this. ubuntu@disco:~$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. Subsequently, bug reports from servers will contain less information. To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1821415/+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 1901253] [NEW] Screen refresh create flicker with groovy
Public bug reported: Since I updated to Groovy I noticed screen flickering It happens when I use terminator with heavy text update like output of apt-update or find / it also sometimes happen when I get a notification I was able to capture it with terminator and take a screenshot I picked gnome-shell because I do't think it is only happening with terminator It also happens when I move the terminator window around ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 23 16:26:43 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-01-05 (291 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: linux-image-5.8.0-25-generic linux-base RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-10-19 (4 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Attachment added: "Screenshot 2020-10-23 at 4.25.10 PM.png" https://bugs.launchpad.net/bugs/1901253/+attachment/5426176/+files/Screenshot%202020-10-23%20at%204.25.10%20PM.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1901253 Title: Screen refresh create flicker with groovy Status in gnome-shell package in Ubuntu: New Bug description: Since I updated to Groovy I noticed screen flickering It happens when I use terminator with heavy text update like output of apt-update or find / it also sometimes happen when I get a notification I was able to capture it with terminator and take a screenshot I picked gnome-shell because I do't think it is only happening with terminator It also happens when I move the terminator window around ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 23 16:26:43 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-01-05 (291 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: linux-image-5.8.0-25-generic linux-base RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-10-19 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1901253/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Tags added: fr-1460 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Incomplete Status in gnome-shell source package in Focal: Invalid Status in accountsservice source package in Groovy: New Status in dbus source package in Groovy: New Status in gnome-shell source package in Groovy: New Status in accountsservice source package in Hirsute: New Status in dbus source package in Hirsute: New Status in gnome-shell source package in Hirsute: New Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Incomplete Status in gnome-shell source package in Impish: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error
[Desktop-packages] [Bug 1922712] Re: add metric for new glibc hwcaps
** Tags added: fr-1265
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-report in Ubuntu.
https://bugs.launchpad.net/bugs/1922712
Title:
add metric for new glibc hwcaps
Status in ubuntu-report package in Ubuntu:
New
Bug description:
we want to collect information which most recent hwcap is supported by
a machine. The result should be a string like "x86-64-v2",
"x86-64-v3", "x86-64-v4", "z13", "z14", "p9", "p10" depending on "ld-
linux --help" output. The string should be empty for architectures
without glibc hwcaps (currently armhf, arm64, i386, riscv64). The
string should be empty if no specific hwcaps is supported (e.g. on a
power8 machine). The string should be "N/A" (not available), when
trying to run ld-linux on a release with glibc (<< 2.33).
Note that lexical sorting won't work for "p9", "p10".
if test -x /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2; then
lddynload=/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
elif test -x /lib/powerpc64le-linux-gnu/ld64.so.2; then
lddynload=/lib/powerpc64le-linux-gnu/ld64.so.2
elif test -x /lib/s390x-linux-gnu/ld64.so.1; then
lddynload=/lib/s390x-linux-gnu/ld64.so.1
fi
supported=
if [ -n "$lddynload" ]; then
$lddynload --help 2>&1 | awk '/^Subdirectories/,/^$/'
supported=$($lddynload --help 2>&1 | awk '/^Subdirectories/,/^$/' | awk
'/supported/ {print $1}')
fi
Here, $supported has listed all supported hwcaps, not just the best
supported one.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1922712/+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 1938588] Re: Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata
** Tags added: fr-1551 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1938588 Title: Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata Status in ubuntu-meta package in Ubuntu: New Bug description: We have several factory-fresh Mitac industrial motherboards (https://www.mitacmct.com/IndustrialMotherboard_PH13FEI_PH13FEI) that we are unable to install Ubuntu Server 18.04.5 on. When we boot from the installation media we get the following error and the installation hangs (see attached screenshot, I've transcribed the error below too) ``` [0.00] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x52 (or later) [0.157025] ACPI Exception: AE_BAD_PARAMETER, Could not install PciConfig handler for Root Bridge PCI0 (20170831/evrgnini-241) ``` Googling the microcode bug, the normal advice appears to be "boot into an older, functioning kernel, update the `intel-microcode` package, and then reboot." But in this situation there is no older kernel to boot into; there is no OS installed _at all_ on these boards yet. I'm booting from a USB drive loaded with the latest version of Ubuntu Server 18.04. The only work-around I've found that works so far is to install Ubuntu Desktop 18.04, which can boot successfully on these boards, perform the minimal desktop installation, then use the desktop install to update the `intel-microcode` package, reboot, and then finally install Ubuntu Server. This is obviously not convenient needing to install a complete desktop OS just so I can update the microcode, and then immediately wiping it to install what I wanted in the first place. I have not tried Ubuntu 20.x or 21.x; I need to use Ubuntu 18.04 because these motherboards are being installed into robots that will be running ROS Melodic (ROS Noetic runs on 20.04, but these robots don't have Noetic support yet). I have tried the following to modify the Ubuntu Server ISO, without success: 1- Adding the microcode to initrd --- I unpacked the contents of the Ubuntu Server ISO, decompressed install/initrd.gz, and used the bash script here https://www.kernel.org/doc/html/latest/x86/microcode.html to add the intel-microcode firmware to the image. Then I recompressed initrd.gz, and rebuild the ISO using xorisso. This did not have any effect: Ubuntu Server still encountered the same error when trying to install. 2- Using initrd from Ubuntu Desktop 18.04.5 -- I downloaded & unpacked Ubuntu Desktop 18.04.5 and replaced Ubuntu Server's install/initrd.gz with Ubuntu Desktop's casper/initrd (updating txt.cfg and grub.cfg to load the uncompressed initrd instead of the .gz that Ubuntu Server normally uses). Then I rebuilt the Ubuntu Server with xorisso again. The resulted in the system booting, but immediately dropping into an initramfs busybox shell, saying boot files were missing. I assume this is because Ubuntu Server uses the `boot=casper` flag in order to boot into the live desktop session. At this point I'm running out of ideas for how to be able to make Ubuntu Server's installation media work with these boards. Ubuntu Desktop has no problem booting on them, so it's obviously something specific to the Ubuntu Server image, but I'm not sure exactly what or how to fix it. If you need any additional information/logs/etc... please let me know and I'll be happy to provide them. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1938588/+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 1866092] [NEW] GDM login input isn't centered
Public bug reported: Updated to latest focal devel branch as of 2020/03/04 at 4pm When you enter your password, the input text isn't centered I will attach a screenshot ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-17.21-lowlatency 5.4.22 Uname: Linux 5.4.0-17-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 4 16:57:22 2020 InstallationDate: Installed on 2020-01-05 (58 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, user) SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-01-23 (41 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug champagne focal ** Attachment added: "gdm.png" https://bugs.launchpad.net/bugs/1866092/+attachment/5333558/+files/gdm.png ** Tags added: champagne -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1866092 Title: GDM login input isn't centered Status in gdm3 package in Ubuntu: New Bug description: Updated to latest focal devel branch as of 2020/03/04 at 4pm When you enter your password, the input text isn't centered I will attach a screenshot ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-17.21-lowlatency 5.4.22 Uname: Linux 5.4.0-17-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 4 16:57:22 2020 InstallationDate: Installed on 2020-01-05 (58 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, user) SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-01-23 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1866092/+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 1950488] Re: brltty ftbfs in jammy
** Tags added: fr-1853 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1950488 Title: brltty ftbfs in jammy Status in brltty package in Ubuntu: Confirmed Bug description: brltty ftbfs in jammy, new version in Debian unstable [...] config.status: executing build-configure commands configure: WARNING: unrecognized options: --without-viavoice dh_testdir /usr/bin/make -C build-py3.10/Bindings/Python make[1]: Entering directory '/<>/brltty-6.3+dfsg/build-py3.10/Bindings/Python' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory '/<>/brltty-6.3+dfsg/build-py3.10/Bindings/Python' make: *** [debian/rules:136: build-py3.10-stamp] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1950488/+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 1964036] Re: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04
** Tags removed: foundations-triage-discuss ** Tags added: foundations-todo -- 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/1964036 Title: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04 Status in firefox package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: 1) lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 (Kubuntu Jammy live session in QEMU VM) 2) apt-cache policy ubuntu-release-upgrader-core ubuntu-release-upgrader-core: Installed: 1:22.04.6 3) expected (upgrade from Kubuntu 20.04.3 -> 22.04. Reboot.) * Firefox icon on panel to be intact. * Clicked icon launches browser. * Icon tooltip/mouse hover to describe application. 4) happened instead * Icon is missing/replaced with a generic icon * Icon click produces error notification "Plasma Workspace - preferred://browser" * Icon tooltip/mouse hover appears, though is blank. Additional info: * firefox is still installed, works as expected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-07 (2 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy dist-upgrade Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964036/+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 1964036] Re: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04
** Tags removed: foundations-triage-discuss -- 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/1964036 Title: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04 Status in firefox package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: 1) lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 (Kubuntu Jammy live session in QEMU VM) 2) apt-cache policy ubuntu-release-upgrader-core ubuntu-release-upgrader-core: Installed: 1:22.04.6 3) expected (upgrade from Kubuntu 20.04.3 -> 22.04. Reboot.) * Firefox icon on panel to be intact. * Clicked icon launches browser. * Icon tooltip/mouse hover to describe application. 4) happened instead * Icon is missing/replaced with a generic icon * Icon click produces error notification "Plasma Workspace - preferred://browser" * Icon tooltip/mouse hover appears, though is blank. Additional info: * firefox is still installed, works as expected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-07 (2 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy dist-upgrade Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964036/+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
