[Desktop-packages] [Bug 1865371] Re: Mouse Cursor or Touchpad indicator/pointer not working
I noticed something like this on my desktop system after upgrading. It only seems to affect Wayland sessions (i.e. GDM login screen and Ubuntu on Wayland). The mouse still works (i.e. desktop responds to clicks), but no cursor is drawn. Everything seems fine on my laptop though. The main differences between the two systems are: 1. Radeon graphics on the desktop vs. Intel on the laptop 2. dual monitors on the desktop 3. The desktop is using a "Thinkpad Compact USB Keyboard" as the mouse (i.e. single USB device exposing two HID interfaces). Given that the reporter here is using an AMD APU, I wonder if this is an interaction between gnome-shell and the radeon driver? -- 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/1865371 Title: Mouse Cursor or Touchpad indicator/pointer not working Status in gnome-shell package in Ubuntu: Incomplete Bug description: after some updates this week, my mouse/touchapad cursor/indicator/pointer started not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 Uname: Linux 5.5.7-050507-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 20:29:07 2020 InstallationDate: Installed on 2017-07-14 (960 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170714) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-10-29T04:23:27.400327 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865371/+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 1864813] Re: As there is not built-in speaker, and not any output, the dummy output in g-c-c will disappear after plug headset once.
** Tags removed: focal ** Tags added: bionic ** Tags added: originate-1863700 ** Tags added: somerville -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1864813 Title: As there is not built-in speaker, and not any output, the dummy output in g-c-c will disappear after plug headset once. Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: The dummy output in gnome-contol-center (g-c-c) will exists if - no built-in speaker - no headphone/earphone plugged - using display (like VGA, DVI) without audio out is plugged. However, in bionic, it will disappear as the headset is plugged and selected. After it disappears, a reboot won't make it appear again. bionic: gnome-control-center: 1:3.28.2-0ubuntu0.18.04.6 pulseaudio: 1:11.1-1ubuntu7.4 In Focal, dummy output won't disappear. focal: pulseaudio 1:13.0-3ubuntu2 gnome-control-center 1:3.35.91-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864813/+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 1866936] [NEW] kernel package linux-headers-5.4.0-4-amd64 is not supported
Public bug reported: apt install nvidia-340 fails $ sudo apt install nvidia-340 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libcuda1-340 nvidia-settings screen-resolution-extra The following NEW packages will be installed: libcuda1-340 nvidia-340 nvidia-settings screen-resolution-extra 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/61.7 MB of archives. After this operation, 307 MB of additional disk space will be used. Do you want to continue? [Y/n] y Selecting previously unselected package libcuda1-340. (Reading database ... 452586 files and directories currently installed.) Preparing to unpack .../libcuda1-340_340.108-0ubuntu2_amd64.deb ... Unpacking libcuda1-340 (340.108-0ubuntu2) ... Selecting previously unselected package nvidia-340. Preparing to unpack .../nvidia-340_340.108-0ubuntu2_amd64.deb ... Adding 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to /usr/lib/x86_64-linux-gnu/libGL.so.1.distrib by nvidia-340' Adding 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340' Adding 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so to /usr/lib/x86_64-linux-gnu/libGL.so.distrib by nvidia-340' Adding 'diversion of /usr/lib/i386-linux-gnu/libGL.so to /usr/lib/i386-linux-gnu/libGL.so.distrib by nvidia-340' Adding 'diversion of /usr/lib/x86_64-linux-gnu/libEGL.so.1 to /usr/lib/x86_64-linux-gnu/libEGL.so.1.distrib by nvidia-340' Adding 'diversion of /usr/lib/i386-linux-gnu/libEGL.so.1 to /usr/lib/i386-linux-gnu/libEGL.so.1.distrib by nvidia-340' Adding 'diversion of /usr/lib/x86_64-linux-gnu/libEGL.so to /usr/lib/x86_64-linux-gnu/libEGL.so.distrib by nvidia-340' Adding 'diversion of /usr/lib/i386-linux-gnu/libEGL.so to /usr/lib/i386-linux-gnu/libEGL.so.distrib by nvidia-340' Adding 'diversion of /usr/lib/x86_64-linux-gnu/libGLESv2.so to /usr/lib/x86_64-linux-gnu/libGLESv2.so.distrib by nvidia-340' Adding 'diversion of /usr/lib/i386-linux-gnu/libGLESv2.so to /usr/lib/i386-linux-gnu/libGLESv2.so.distrib by nvidia-340' Adding 'diversion of /usr/lib/x86_64-linux-gnu/libGLESv2.so.2 to /usr/lib/x86_64-linux-gnu/libGLESv2.so.2.distrib by nvidia-340' Adding 'diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2 to /usr/lib/i386-linux-gnu/libGLESv2.so.2.distrib by nvidia-340' Adding 'diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so to /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.distrib by nvidia-340' Adding 'diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so to /usr/lib/i386-linux-gnu/libGLESv1_CM.so.distrib by nvidia-340' Adding 'diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1 to /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1.distrib by nvidia-340' Adding 'diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.distrib by nvidia-340' Unpacking nvidia-340 (340.108-0ubuntu2) ... Selecting previously unselected package screen-resolution-extra. Preparing to unpack .../screen-resolution-extra_0.18build1_all.deb ... Unpacking screen-resolution-extra (0.18build1) ... Selecting previously unselected package nvidia-settings. Preparing to unpack .../nvidia-settings_440.44-0ubuntu1_amd64.deb ... Unpacking nvidia-settings (440.44-0ubuntu1) ... Setting up nvidia-340 (340.108-0ubuntu2) ... dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-340 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude Adding system user `nvidia-persistenced' (UID 134) ... Adding new group `nvidia-persistenced' (GID 141) ... Adding new user `nvidia-persistenced' (UID 134) with group `nvidia-persistenced' ... Not creating home directory `/'. Loading new nvidia-340-340.108 DKMS files... Building for 5.4.0-4-amd64 Building for architecture x86_64 Building initial module for 5.4.0-4-amd64 ERROR (dkms apport): kernel package linux-headers-5.4.0-4-amd64 is not supported Error! Bad return status for module build on kernel: 5.4.0-4-amd64 (x86_64) Consult /var/lib/dkms/nvidia-340/340.108/build/make.log for more information. dpkg: error processing package nvidia-340 (--configure): installed nvidia-340 package post-installation script subprocess returned error exit status 10 Setting up screen-resolution-extra (0.18build1) ... Setting up nvidia-settings (440.44-0ubuntu1) ... Setting up libcuda1-340 (340.108-0ubuntu2) ... Processing triggers for desktop-file-utils (0.24-1ubuntu2) ... Processing triggers for mime-support (3.64ubuntu1) ... Processing triggers for gnome-menus (3.35.3-1ubuntu1) ... Processing triggers for libc-bin (2.30-0ubuntu3) ... Processing triggers for
[Desktop-packages] [Bug 1866933] [NEW] Xorg freeze
Public bug reported: when I click on the Activities button and try to start an application my X session freezes. I can move the mouse around and bring up the dock on the side of the screen, but no windows will come up. This problem does not come up if I open applications from the applications menu, dock, or terminal. I can only solve it by logging out and logging back in. Description:Ubuntu Focal Fossa (development branch) Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 10 20:12:16 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.4, 5.4.0-14-generic, x86_64: installed virtualbox-guest, 6.1.4, 5.4.0-14-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Iris Graphics 540 [8086:1926] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Graphics 540 [8086:2063] InstallationDate: Installed on 2017-10-19 (873 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: SYSKLi35.86A.0071.2019.0524.1102 dmi.board.asset.tag: � [� dmi.board.name: NUC6i5SYB dmi.board.vendor: Intel corporation dmi.board.version: H81131-505 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrSYSKLi35.86A.0071.2019.0524.1102:bd05/24/2019:svn:pn:pvr:rvnIntelcorporation:rnNUC6i5SYB:rvrH81131-505:cvn:ct3:cvr: version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze reproducible 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/1866933 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: when I click on the Activities button and try to start an application my X session freezes. I can move the mouse around and bring up the dock on the side of the screen, but no windows will come up. This problem does not come up if I open applications from the applications menu, dock, or terminal. I can only solve it by logging out and logging back in. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 10 20:12:16 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.4, 5.4.0-14-generic, x86_64: installed virtualbox-guest, 6.1.4, 5.4.0-14-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Iris Graphics 540 [8086:1926] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Graphics 540 [8086:2063] InstallationDate: Installed on 2017-10-19 (873 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: PATH=(custom, no user)
[Desktop-packages] [Bug 1866929] [NEW] gnome-shell crashes when typing on lock screen
Public bug reported: When the screen is locked, typing anything on the keyboard doesn't lead to the password prompt. Instead, the desktop / open applications are shown for a few seconds, but the session is not unlocked, the gnome- shell crashes and the lock screen is back on. After that, the kernel log says: [ 1253.059365] traps: gnome-shell[15914] trap int3 ip:7fa53d1000d5 sp:7fffdf2bbc50 error:0 in libglib-2.0.so.0.6400.0[7fa53d0c4000+84000] If libreoffice is open during this procedure, it is killed. The kernel log says: [ 1753.463495] audit: type=1400 audit(1583883878.179:44): apparmor="ALLOWED" operation="signal" profile="libreoffice-oopslash" pid=18520 comm="oosplash" requested_mask="send" denied_mask="send" signal=kill peer="libreoffice-soffice" [ 1753.463502] audit: type=1400 audit(1583883878.179:45): apparmor="ALLOWED" operation="signal" profile="libreoffice-soffice" pid=18520 comm="oosplash" requested_mask="receive" denied_mask="receive" signal=kill peer="libreoffice-oopslash" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 00:31:34 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-01-05 (64 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866929 Title: gnome-shell crashes when typing on lock screen Status in gnome-shell package in Ubuntu: New Bug description: When the screen is locked, typing anything on the keyboard doesn't lead to the password prompt. Instead, the desktop / open applications are shown for a few seconds, but the session is not unlocked, the gnome-shell crashes and the lock screen is back on. After that, the kernel log says: [ 1253.059365] traps: gnome-shell[15914] trap int3 ip:7fa53d1000d5 sp:7fffdf2bbc50 error:0 in libglib-2.0.so.0.6400.0[7fa53d0c4000+84000] If libreoffice is open during this procedure, it is killed. The kernel log says: [ 1753.463495] audit: type=1400 audit(1583883878.179:44): apparmor="ALLOWED" operation="signal" profile="libreoffice-oopslash" pid=18520 comm="oosplash" requested_mask="send" denied_mask="send" signal=kill peer="libreoffice-soffice" [ 1753.463502] audit: type=1400 audit(1583883878.179:45): apparmor="ALLOWED" operation="signal" profile="libreoffice-soffice" pid=18520 comm="oosplash" requested_mask="receive" denied_mask="receive" signal=kill peer="libreoffice-oopslash" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 00:31:34 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-01-05 (64 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866929/+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 1857809] Re: Cisco AnyConnect (VPN) username is not remembered
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1857809 Title: Cisco AnyConnect (VPN) username is not remembered Status in network-manager package in Ubuntu: Confirmed Bug description: On Ubuntu 19.10 (and previous versions) with openconnect 8.02-1build1, network-manager-openconnect and network-manager-openconnect-gnome 1.2.4-2ubuntu1 and libopenconnect5 8.02-1build1: The username is not saved although "save passwords" is chosen. When I connect to a Cisco AnyConnect VPN profile from the Network Manager it shows the connect to VPN dialog window, the password was saved and is automatically added to the field (from a previous connection) but the username has to be added every time the VPN is started. Is this a bug or just the way it is? Can this be changed? If yes, how? Thanks for any help in advance! (This problem is also reported here: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1857808) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1857809/+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 1866923] [NEW] Wifi connection says it's connected but this is not true after the computer goes into a sleep status
Public bug reported: The wifi is connected and working correctly when powered on, however when I close the laptop lid, which I think puts it to sleep, and then reopen it, it says it's connected according to the icon but this is not true. A workaround is turning on Airplane mode and then switching it back on again. It then reconnects and is then fine again. Unless I close the lid and then the process repeats again. I guess this is to do with the wifi driver but I don't know what package it is so I just picked network-manager, sorry - I'm trying :) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 10 19:29:03 2020 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.68.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.68.0/24 dev wlp1s0 proto kernel scope link src 192.168.68.18 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wifi -- 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/1866923 Title: Wifi connection says it's connected but this is not true after the computer goes into a sleep status Status in network-manager package in Ubuntu: New Bug description: The wifi is connected and working correctly when powered on, however when I close the laptop lid, which I think puts it to sleep, and then reopen it, it says it's connected according to the icon but this is not true. A workaround is turning on Airplane mode and then switching it back on again. It then reconnects and is then fine again. Unless I close the lid and then the process repeats again. I guess this is to do with the wifi driver but I don't know what package it is so I just picked network-manager, sorry - I'm trying :) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 10 19:29:03 2020 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.68.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.68.0/24 dev wlp1s0 proto kernel scope link src 192.168.68.18 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1866923/+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 1866919] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1858414 *** https://bugs.launchpad.net/bugs/1858414 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 #1858414, 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/1866919/+attachment/5335513/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1866919/+attachment/5335515/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1866919/+attachment/5335520/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1866919/+attachment/5335521/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1866919/+attachment/5335522/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1866919/+attachment/5335524/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1866919/+attachment/5335525/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1858414 gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() ** Information type changed from Private Security to Public Security ** 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/1866919 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: it happened after upgrading to ubuntu20.04 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 03:05:00 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-03-06 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: Upgraded to focal on 2020-03-10 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866919/+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 1866444] Re: [MacBook2, 1, SigmaTel STAC9221 A1, Mic, Internal] Recording problem
extra info: Audacity is able to access the microphone as "sysdefault: Mic:0" using ALSA (see screenshot) yet the default mic is not accessible in the Sound system setting in the Input tab. ** Attachment added: "Audacity - sysdefault: Mic:0.png" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1866444/+attachment/5335512/+files/Audacity%20-%20sysdefault%3A%20Mic%3A0.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1866444 Title: [MacBook2,1, SigmaTel STAC9221 A1, Mic, Internal] Recording problem Status in alsa-driver package in Ubuntu: New Bug description: What you expected to happen Settings -> Sound -> Input to list internal mic (to test orange bars for recording from internal mic) What actually happened Settings -> Sound -> Input only lists "Digital Input (S/PDIF)" (no bars move because no digital input connected) If possible, a minimal series of steps necessary to make it happen, where step 1 is "start the program" 1. Open Settings 2. Select Sound setting 3. Select Input tab -- NOTE: ultimately, I want recording to work in apps such as Chrome, Firefox, Zoom, etc. NOTE 2: mic recording was last working in Ubuntu 18.04.x (32-bit) instance on *same* MacBook hardware (this installation went corrupt so I can't reverify it still works unfortunately - I will add to this issue if I get the cycles to reinstall or at your request) NOTE 3: interestingly enough, while using "ubuntu-bug" it was able to record from the mic on the 1st (of 2 tests the bug collector initiated). -- $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 from "apt list --installed" alsa-base/bionic,bionic,bionic,bionic,now 1.0.25+dfsg-0ubuntu5 all [installed] alsa-utils/bionic,bionic,now 1.1.3-1ubuntu1 amd64 [installed] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_76_86_generic_63 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D1c: chinarut 1724 F...m pulseaudio /dev/snd/controlC0: chinarut 1724 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 6 22:41:25 2020 InstallationDate: Installed on 2020-01-24 (42 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:Intel failed Symptom_Type: Only some of inputs are working Title: [MacBook2,1, SigmaTel STAC9221 A1, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/07 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB21.88Z.00A5.B07.0706270922 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4208CAA dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4208CAA dmi.modalias: dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CAA:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CAA: dmi.product.family: MacBook dmi.product.name: MacBook2,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1866444/+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 1866918] [NEW] Following upgrade from 19.10 to 20.04 Synaptics touchpad does not work with XOrg, but does with Wayland KDE session
Public bug reported: Touchpad works correctly in wayland session Touchpad in system settings is shown in grey Device is recognised by OS, but does not move the cursor or respond to press or multi-touch gestures in KDE on X. USB mouse ios recognised and operates correctly. Problem identified immediately after upgrade (was working correctly prior to upgrade) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-input-libinput 0.29.0-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 CurrentDesktop: KDE Date: Tue Mar 10 21:33:46 2020 DistUpgraded: 2020-03-07 22:56:23,303 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu InstallationDate: Installed on 2018-01-02 (797 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=27d98ac5-3965-4693-8ca0-a5028c6eed60 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: Upgraded to focal on 2020-03-07 (2 days ago) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xserver-xorg-input-libinput (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal has-fix has-workaround single-occurrence ubuntu ** Attachment added: "cat /proc/bus/input/devices" https://bugs.launchpad.net/bugs/1866918/+attachment/5335494/+files/devices.txt -- 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/1866918 Title: Following upgrade from 19.10 to 20.04 Synaptics touchpad does not work with XOrg, but does with Wayland KDE session Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: Touchpad works correctly in wayland session Touchpad in system settings is shown in grey Device is recognised by OS, but does not move the cursor or respond to press or multi-touch gestures in KDE on X. USB mouse ios recognised and operates correctly. Problem identified immediately after upgrade (was working correctly prior to upgrade) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-input-libinput 0.29.0-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 CurrentDesktop: KDE Date: Tue Mar 10 21:33:46 2020 DistUpgraded: 2020-03-07 22:56:23,303 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu InstallationDate: Installed on 2018-01-02 (797 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=27d98ac5-3965-4693-8ca0-a5028c6eed60 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: Upgraded to focal on 2020-03-07 (2 days ago) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer version.compiz: compiz N/A
[Desktop-packages] [Bug 1866890] Re: audio card not detected after upgrade to 20.04 (Only Dummy Output appears)
Original fix suggestion came from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697/comments/6 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1866890 Title: audio card not detected after upgrade to 20.04 (Only Dummy Output appears) Status in alsa-driver package in Ubuntu: New Bug description: Since upgrading to 20.04 the sound card is no longer detected. This means that I can only see "Dummy Output" in the sound settings. The audio works if I use Bluetooth headphones but not if I try to use the speakers or the 3.5mm headphone jack. My machine is a Lenovo ThinkPad X1 Yoga (4th gen). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1866890/+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 1866890] Re: audio card not detected after upgrade to 20.04 (Only Dummy Output appears)
I added `options snd-hda-intel dmic_detect=0` at the end of /etc/modprobe.d/alsa-base.conf and after restarting the laptop I can now use the headphones and speakers. Although I managed to fix this, - could this be resolved for other users? Many thanks! Eduardo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1866890 Title: audio card not detected after upgrade to 20.04 (Only Dummy Output appears) Status in alsa-driver package in Ubuntu: New Bug description: Since upgrading to 20.04 the sound card is no longer detected. This means that I can only see "Dummy Output" in the sound settings. The audio works if I use Bluetooth headphones but not if I try to use the speakers or the 3.5mm headphone jack. My machine is a Lenovo ThinkPad X1 Yoga (4th gen). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1866890/+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 1866890] Re: audio card not detected after upgrade to 20.04 (Only Dummy Output appears)
Seems similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697 ** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1866890 Title: audio card not detected after upgrade to 20.04 (Only Dummy Output appears) Status in alsa-driver package in Ubuntu: New Bug description: Since upgrading to 20.04 the sound card is no longer detected. This means that I can only see "Dummy Output" in the sound settings. The audio works if I use Bluetooth headphones but not if I try to use the speakers or the 3.5mm headphone jack. My machine is a Lenovo ThinkPad X1 Yoga (4th gen). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1866890/+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 1866890] [NEW] audio card not detected after upgrade to 20.04 (Only Dummy Output appears)
You have been subscribed to a public bug: Since upgrading to 20.04 the sound card is no longer detected. This means that I can only see "Dummy Output" in the sound settings. The audio works if I use Bluetooth headphones but not if I try to use the speakers or the 3.5mm headphone jack. My machine is a Lenovo ThinkPad X1 Yoga (4th gen). ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: champagne focal -- audio card not detected after upgrade to 20.04 (Only Dummy Output appears) https://bugs.launchpad.net/bugs/1866890 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866900] [NEW] Javascript clipboard does not work
Public bug reported: Pressing the "copy to clipboard" buttons on websites does not work. (e. g. Gitlab / Github) Manual ctrl-c is necessary. (Wrorks in several other browsers on same system) Snap / connection ? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 74.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anders 2056 F pulseaudio /dev/snd/controlC0: anders 2056 F pulseaudio BuildID: 20200309095159 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Mar 10 19:45:10 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:729 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-03-03 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:729 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=74.0/20200304223017 (Out of date) Profile0 - LastVersion=74.0/20200309095159 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2013 dmi.bios.vendor: LENOVO dmi.bios.version: I1KT24AUS dmi.board.vendor: LENOVO dmi.board.version: 3193 STD dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrI1KT24AUS:bd07/24/2013:svnLENOVO:pn10120:pvrIdeaCentreK450:rvnLENOVO:rn:rvr3193STD:cvnLENOVO:ct3:cvr: dmi.product.family: IdeaCentre dmi.product.name: 10120 dmi.product.sku: LENOVO_MT_1012 dmi.product.version: IdeaCentre K450 dmi.sys.vendor: LENOVO ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1866900 Title: Javascript clipboard does not work Status in firefox package in Ubuntu: New Bug description: Pressing the "copy to clipboard" buttons on websites does not work. (e. g. Gitlab / Github) Manual ctrl-c is necessary. (Wrorks in several other browsers on same system) Snap / connection ? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 74.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anders 2056 F pulseaudio /dev/snd/controlC0: anders 2056 F pulseaudio BuildID: 20200309095159 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Mar 10 19:45:10 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:729 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-03-03 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:729 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=74.0/20200304223017 (Out of date) Profile0 - LastVersion=74.0/20200309095159 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No
[Desktop-packages] [Bug 1866888] Re: gnome-shell crashed with signal 5 in clutter_actor_allocate()
*** This bug is a duplicate of bug 1866044 *** https://bugs.launchpad.net/bugs/1866044 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 #1866044, 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/1866888/+attachment/5335440/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1866888/+attachment/5335442/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1866888/+attachment/5335446/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1866888/+attachment/5335447/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1866888/+attachment/5335448/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1866888/+attachment/5335450/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1866888/+attachment/5335451/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1866044 ** Information type changed from Private Security to Public Security ** 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/1866888 Title: gnome-shell crashed with signal 5 in clutter_actor_allocate() Status in gnome-shell package in Ubuntu: New Bug description: I'm on 20.04 When I lock the screen the login screen doesn't appear. Instead sometimes it just flashes and doesn't lock the screen or the machine freezes and needs to be restarted. I flagged this as security related because now as a user I can't lock my screen, so I either have to leave it unlocked or completely shut down my machine. Thank you very much in advance! Eduardo ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 10 19:24:39 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-09-04 (187 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/mutter-6/libmutter-clutter-6.so.0 ?? () from /usr/lib/gnome-shell/libst-1.0.so ?? () from /usr/lib/x86_64-linux-gnu/mutter-6/libmutter-clutter-6.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-6/libmutter-clutter-6.so.0 clutter_actor_allocate () from /usr/lib/x86_64-linux-gnu/mutter-6/libmutter-clutter-6.so.0 Title: gnome-shell crashed with signal 5 in clutter_actor_allocate() UpgradeStatus: Upgraded to focal on 2020-03-03 (7 days ago) UserGroups: adm cdrom dip libvirt lpadmin microk8s plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866888/+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 1866880] Re: Firefox Speech Synthesis Not Working in Kubuntu
** Description changed:
Modern web browsers, by spec, are supposed to support Speech Synthesis.
Although Firefox does indeed support it, it doesn't work in Kubuntu
19.10.
On this very page, you should be able to have Firefox read it aloud by
typing shift-ctrl-I and then entering this code-line into the console
(and pressing enter):
speechSynthesis.speak(new
SpeechSynthesisUtterance(document.getElementsByTagName("body")[0].innerText));
-
- Something shorter, that you could type into the console (for testing) is:
+ Something shorter, that you could type into the console (for testing)
+ is:
speechSynthesis.speak(new SpeechSynthesisUtterance("testing 1, 2, 3");
You should be able to hear the browser say "testing 1, 2, 3" after doing
this, but it doesn't working Kubuntu 19.10.
-
- This works in Ubuntu 19.10 and Windows 10, but doesn't work in Kubuntu 19.10.
I'm reporting this in hopes that it gets fixed before Kubuntu 20.04.
+ This works in Ubuntu 19.10 and Windows 10, but doesn't work in Kubuntu
+ 19.10. I'm reporting this in hopes that it gets fixed before Kubuntu
+ 20.04.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: firefox 73.0.1+build1-0ubuntu0.19.10.1
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu8.5
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC1: lonnie 1850 F pulseaudio
- /dev/snd/controlC0: lonnie 1850 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC1: lonnie 1850 F pulseaudio
+ /dev/snd/controlC0: lonnie 1850 F pulseaudio
BuildID: 20200217142647
Channel: Unavailable
CurrentDesktop: KDE
Date: Tue Mar 10 13:25:31 2020
ForcedLayersAccel: False
InstallationDate: Installed on 2020-02-03 (36 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
NoProfiles: True
ProcEnviron:
- TERM=xterm-256color
- PATH=(custom, no user)
- XDG_RUNTIME_DIR=
- LANG=en_US.UTF-8
- SHELL=/bin/bash
+ TERM=xterm-256color
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.04RSA5
dmi.board.asset.tag: Tag 12345
dmi.board.name: Bonobo WS
dmi.board.vendor: System76
dmi.board.version: bonw13
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: Bonobo WS
dmi.product.sku: Not Applicable
dmi.product.version: bonw13
dmi.sys.vendor: System76
--
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/1866880
Title:
Firefox Speech Synthesis Not Working in Kubuntu
Status in KDE Base:
New
Status in firefox package in Ubuntu:
New
Bug description:
Modern web browsers, by spec, are supposed to support Speech
Synthesis. Although Firefox does indeed support it, it doesn't work in
Kubuntu 19.10.
On this very page, you should be able to have Firefox read it aloud by
typing shift-ctrl-I and then entering this code-line into the console
(and pressing enter):
speechSynthesis.speak(new
SpeechSynthesisUtterance(document.getElementsByTagName("body")[0].innerText));
Something shorter, that you could type into the console (for testing)
is:
speechSynthesis.speak(new SpeechSynthesisUtterance("testing 1, 2, 3");
You should be able to hear the browser say "testing 1, 2, 3" after
doing this, but it doesn't working Kubuntu 19.10.
This works in Ubuntu 19.10 and Windows 10, but doesn't work in Kubuntu
19.10. I'm reporting this in hopes that it gets fixed before Kubuntu
20.04.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: firefox 73.0.1+build1-0ubuntu0.19.10.1
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu8.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: lonnie 1850 F pulseaudio
/dev/snd/controlC0: lonnie 1850 F pulseaudio
BuildID: 20200217142647
Channel: Unavailable
CurrentDesktop: KDE
Date: Tue Mar 10 13:25:31 2020
ForcedLayersAccel: False
InstallationDate: Installed on 2020-02-03 (36 days ago)
InstallationMedia: Kubuntu 19.10
[Desktop-packages] [Bug 1866880] Re: Firefox Speech Synthesis Not Working in Kubuntu
Another example:
Here's a card trick I made, where the browser should speak during the trick:
http://www.lonniebest.com/CardTrick/
This speaking can be heard in both Firefox and Chrome on Windows 10. It
also works in Ubuntu Firefox. However, it does NOT work in Kubuntu 19.10
Firefox (you don't hear anything). Hopefully this will be fixed by
Kubuntu 20.04 LTS.
** Also affects: kde-baseapps
Importance: Undecided
Status: New
** Tags added: focal
--
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/1866880
Title:
Firefox Speech Synthesis Not Working in Kubuntu
Status in KDE Base:
New
Status in firefox package in Ubuntu:
New
Bug description:
Modern web browsers, by spec, are supposed to support Speech
Synthesis. Although Firefox does indeed support it, it doesn't work in
Kubuntu 19.10.
On this very page, you should be able to have Firefox read it aloud by
typing shift-ctrl-I and then entering this code-line into the console
(and pressing enter):
speechSynthesis.speak(new
SpeechSynthesisUtterance(document.getElementsByTagName("body")[0].innerText));
Something shorter, that you could type into the console (for testing) is:
speechSynthesis.speak(new SpeechSynthesisUtterance("testing 1, 2, 3");
You should be able to hear the browser say "testing 1, 2, 3" after
doing this, but it doesn't working Kubuntu 19.10.
This works in Ubuntu 19.10 and Windows 10, but doesn't work in Kubuntu 19.10.
I'm reporting this in hopes that it gets fixed before Kubuntu 20.04.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: firefox 73.0.1+build1-0ubuntu0.19.10.1
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu8.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: lonnie 1850 F pulseaudio
/dev/snd/controlC0: lonnie 1850 F pulseaudio
BuildID: 20200217142647
Channel: Unavailable
CurrentDesktop: KDE
Date: Tue Mar 10 13:25:31 2020
ForcedLayersAccel: False
InstallationDate: Installed on 2020-02-03 (36 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
NoProfiles: True
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.04RSA5
dmi.board.asset.tag: Tag 12345
dmi.board.name: Bonobo WS
dmi.board.vendor: System76
dmi.board.version: bonw13
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: Bonobo WS
dmi.product.sku: Not Applicable
dmi.product.version: bonw13
dmi.sys.vendor: System76
To manage notifications about this bug go to:
https://bugs.launchpad.net/kde-baseapps/+bug/1866880/+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 1866880] [NEW] Firefox Speech Synthesis Not Working in Kubuntu
Public bug reported:
Modern web browsers, by spec, are supposed to support Speech Synthesis.
Although Firefox does indeed support it, it doesn't work in Kubuntu
19.10.
On this very page, you should be able to have Firefox read it aloud by
typing shift-ctrl-I and then entering this code-line into the console
(and pressing enter):
speechSynthesis.speak(new
SpeechSynthesisUtterance(document.getElementsByTagName("body")[0].innerText));
Something shorter, that you could type into the console (for testing) is:
speechSynthesis.speak(new SpeechSynthesisUtterance("testing 1, 2, 3");
You should be able to hear the browser say "testing 1, 2, 3" after doing
this, but it doesn't working Kubuntu 19.10.
This works in Ubuntu 19.10 and Windows 10, but doesn't work in Kubuntu 19.10.
I'm reporting this in hopes that it gets fixed before Kubuntu 20.04.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: firefox 73.0.1+build1-0ubuntu0.19.10.1
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu8.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: lonnie 1850 F pulseaudio
/dev/snd/controlC0: lonnie 1850 F pulseaudio
BuildID: 20200217142647
Channel: Unavailable
CurrentDesktop: KDE
Date: Tue Mar 10 13:25:31 2020
ForcedLayersAccel: False
InstallationDate: Installed on 2020-02-03 (36 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
NoProfiles: True
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.04RSA5
dmi.board.asset.tag: Tag 12345
dmi.board.name: Bonobo WS
dmi.board.vendor: System76
dmi.board.version: bonw13
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: Bonobo WS
dmi.product.sku: Not Applicable
dmi.product.version: bonw13
dmi.sys.vendor: System76
** Affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug eoan
--
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/1866880
Title:
Firefox Speech Synthesis Not Working in Kubuntu
Status in firefox package in Ubuntu:
New
Bug description:
Modern web browsers, by spec, are supposed to support Speech
Synthesis. Although Firefox does indeed support it, it doesn't work in
Kubuntu 19.10.
On this very page, you should be able to have Firefox read it aloud by
typing shift-ctrl-I and then entering this code-line into the console
(and pressing enter):
speechSynthesis.speak(new
SpeechSynthesisUtterance(document.getElementsByTagName("body")[0].innerText));
Something shorter, that you could type into the console (for testing) is:
speechSynthesis.speak(new SpeechSynthesisUtterance("testing 1, 2, 3");
You should be able to hear the browser say "testing 1, 2, 3" after
doing this, but it doesn't working Kubuntu 19.10.
This works in Ubuntu 19.10 and Windows 10, but doesn't work in Kubuntu 19.10.
I'm reporting this in hopes that it gets fixed before Kubuntu 20.04.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: firefox 73.0.1+build1-0ubuntu0.19.10.1
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu8.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: lonnie 1850 F pulseaudio
/dev/snd/controlC0: lonnie 1850 F pulseaudio
BuildID: 20200217142647
Channel: Unavailable
CurrentDesktop: KDE
Date: Tue Mar 10 13:25:31 2020
ForcedLayersAccel: False
InstallationDate: Installed on 2020-02-03 (36 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
NoProfiles: True
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.04RSA5
dmi.board.asset.tag: Tag 12345
dmi.board.name: Bonobo WS
dmi.board.vendor: System76
dmi.board.version: bonw13
[Desktop-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
As already mentioned... > Mouse-click/s do not work (no feedback) and produces an error in the terminal. > Keyboard navigation and 'Enter' works fine (Authentication window appears) -- 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/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in gnome-shell package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in gnome-shell source package in Bionic: Confirmed Status in software-properties source package in Bionic: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties 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/1727908/+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 1825710] Re: Remove "Application is ready" notification
I will add that when I see this in Pidgin, it leads me to believe someone has highlighted me, but no, no one has and I just spent some time context switching. And this keeps happening over and over again... @dean, indeed, but Pidgin is wasting lots of my time with this nonsense:) -- 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/1825710 Title: Remove "Application is ready" notification Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: The "Application is ready" notification is pointless, really. Say, I click on the open downloads folder button in Firefox and GNOME Shell gives me a notification saying "Application is ready" but doesn't open the notification. I'm totally expecting an app to open because I actively initiated it. As a workaround, I'm using a GNOME extensions "Focus my Window" which removes the "Application is ready" message and focuses the app window automatically. However, this cannot be treated as a solution. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1825710/+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 1825710] Re: Remove "Application is ready" notification
Yes, it's not just Pidgin - other apps do it as well. -- 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/1825710 Title: Remove "Application is ready" notification Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: The "Application is ready" notification is pointless, really. Say, I click on the open downloads folder button in Firefox and GNOME Shell gives me a notification saying "Application is ready" but doesn't open the notification. I'm totally expecting an app to open because I actively initiated it. As a workaround, I'm using a GNOME extensions "Focus my Window" which removes the "Application is ready" message and focuses the app window automatically. However, this cannot be treated as a solution. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1825710/+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 1825710] Re: Remove "Application is ready" notification
I'll add that since updating from 18.04 to 20.04, Pidgin has been doing this very consistently. Whenever I have Pidgin focused and then switch focus to another window, some time later, I get a notification saying: Pidgin Internet Messenger "#foo" is ready where #foo is the name of the last chat tab I had focused with Pidgin. This "new" behavior is atrocious. I'm not sure what changed in Pidgin and/or Gnome, but this is a terrible user experience. Also, this is related to https://bugs.launchpad.net/bugs/1861006. -- 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/1825710 Title: Remove "Application is ready" notification Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: The "Application is ready" notification is pointless, really. Say, I click on the open downloads folder button in Firefox and GNOME Shell gives me a notification saying "Application is ready" but doesn't open the notification. I'm totally expecting an app to open because I actively initiated it. As a workaround, I'm using a GNOME extensions "Focus my Window" which removes the "Application is ready" message and focuses the app window automatically. However, this cannot be treated as a solution. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1825710/+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 1864274] Re: crunchy pixels
I've added instructions in the mesa bug on how to correctly set the
environment variable to workaround the issue:
https://gitlab.freedesktop.org/mesa/mesa/issues/2552#note_432595
--
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/1864274
Title:
crunchy pixels
Status in Mesa:
Unknown
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Hello, after upgrading firefox (and many other packages) on focal
today, I've got some video artifacts in firefox.
When typing in text boxes and text fields, the new character is drawn
very slowly, pixel-by-pixel, and isn't complete until the cursor has
moved on. When larger portions of the screen are updated, it looks a
lot like the entire window is being run through a video codec or you
can see parts of the video memory from other processes. (But it looks
more deliberate and predictable than either of these descriptions.)
So far Firefox is the only application I've found that is affected.
urxvt, libreoffice, xfontsel, glxgears all seem to work as expected.
I did get cairo package update today, but the changelog is just:
pango1.0 (1.44.7-1ubuntu2) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
-- Matthias Klose Sat, 08 Feb 2020 11:15:23 +
And an xorg update:
xorg (1:7.7+19ubuntu14) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
-- Matthias Klose Sat, 08 Feb 2020 11:21:28 +
So I don't believe these are involved.
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620
(rev 07)
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 73.0.1+build1-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-14-generic.
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sarnold3296 F pulseaudio
/dev/snd/controlC0: sarnold3296 F pulseaudio
BuildID: 20200217142647
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 144'
Mixer name : 'Realtek ALC285'
Components : 'HDA:10ec0285,17aa225c,0012
HDA:8086280b,80860101,0010'
Controls : 53
Simple ctrls : 15
Card1.Amixer.info:
Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at
usb-:00:14.0-4.2.4, high speed'
Mixer name : 'USB Mixer'
Components : 'USB17ef:306f'
Controls : 9
Simple ctrls : 4
Channel: Unavailable
Date: Sat Feb 22 05:41:10 2020
ForcedLayersAccel: False
IncompatibleExtensions:
Pentadactyl - pentadac...@dactyl.googlecode.com
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
IpRoute:
default via 192.168.0.1 dev enp0s31f6 proto dhcp metric 100
10.23.231.0/24 dev lxdbr0 proto kernel scope link src 10.23.231.1
192.168.0.0/24 dev enp0s31f6 proto kernel scope link src 192.168.0.34 metric
100
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
linkdown
MostRecentCrashID: bp-ea952d4d-f25a-4ced-893c-8cabb2160112
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:737
PrefSources: prefs.js
ProcEnviron:
TERM=rxvt-unicode-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=73.0.1/20200217142647 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to focal on 2020-01-24 (28 days ago)
dmi.bios.date: 11/25/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N23ET69W (1.44 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KHCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 6th
dmi.product.name: 20KHCTO1WW
dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
dmi.product.version: ThinkPad X1 Carbon 6th
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1864274/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help :
[Desktop-packages] [Bug 1865226] Re: gdm3 fails to install /etc/pam.d/gdm-smartcard
reported to debian BTS, added link ** Bug watch added: Debian Bug tracker #953557 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953557 ** Also affects: gdm via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953557 Importance: Unknown Status: Unknown -- 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/1865226 Title: gdm3 fails to install /etc/pam.d/gdm-smartcard Status in gdm: Unknown Status in gdm3 package in Ubuntu: Confirmed Bug description: the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865226/+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 1855893] Re: Properly let PCM leave suspended state when hardware doesn't support PCM resume
I think it's okay to drop it since Focal is imminent. -- 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/1855893 Title: Properly let PCM leave suspended state when hardware doesn't support PCM resume Status in HWE Next: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: In Progress Bug description: [Impact] Headset Mic plugged into Dell WD19TB dock stops working after suspend/resume. [Fix] According to alia-lib's document, to make PCM properly leave suspended state, we only use snd_pcm_resume() if hardware support PCM resume. For hardware that doesn't support PCM resume, like snd-usb-audio on WD19TB dock, we should use snd_pcm_prepare(), snd_pcm_drop() or snd_pcm_drain() to make device leave suspended state. This patch defaults to use snd_pcm_drop() to achieve the goal. [Test] 1. See if microphone on snd-usb-audio works in gnome-control-center/cheese. 2. Suspend/resume. 3. See if microphone still works in those apps. I can the issue is fixed after each suspend/resume cycle. [Regression Potential] Low. This fix makes PCM suspend/resume more reliable. No functional change intended. I also don't find any regression during some smoke test. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1855893/+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 1866194] Re: After connecting a Bluetooth headset or speaker, it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker
This might be more of an issue with handing sound devices being added and removed that being bluetooth specific. Last week I experienced the same behavior when plugging in my USB headphones. Removing them and plugging them in again worked though. I haven't been able to reproduce this today though. I'll keep trying and report back. -- 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/1866194 Title: After connecting a Bluetooth headset or speaker, it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Device CID: 201704-25503 Steps to reproduce: 1. Go to Bluetooth settings panel 2. Pair a BT device 3. Make sure it's marked as Connected, and go to the Sound settings 4. Make sure it's the one selected as "Output device" 5. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 6. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 7. Try to switch back to the BT device and click Test -> same result as in step 5 Tested with 2 different BT devices (one headset and one speaker) Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1866194/+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 1864982] Re: Ubuntu desktop computer doesn't seem to lock correctly
Hi Team, Any updates here? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1864982 Title: Ubuntu desktop computer doesn't seem to lock correctly Status in lightdm package in Ubuntu: New Bug description: Ubuntu desktop computer doesn't seem to lock correctly if I click "Lock Screen" it does lock if I use shortcut. If I use the "lock screen" button then anyone can unlock it by merely pressing "ctrl+alt+f7". The problem is not that I cannot lock my screen, the problem is I was under the impression that my computer was being locked when it was not. now that I know that the "Lock Screen" button doesn't work correctly I know of other ways to lock my computer still the lock screen button should work and it looks like it locked my screen,but if I press "ctrl+alt+f7" then it magically unlocks So it is a security incident. Thanks in Advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1864982/+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 1864644] Re: I get logged out immediately after login to an X session (QXL Xorg driver on kernel 5.4)
** Package changed: linux (Ubuntu) => systemd (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/1864644 Title: I get logged out immediately after login to an X session (QXL Xorg driver on kernel 5.4) Status in systemd package in Ubuntu: Confirmed Status in xserver-xorg-video-qxl package in Ubuntu: Invalid Bug description: I just installed ubuntu 20.04 in a virtual machine and did 'apt-get update;apt-get upgrade' to get current (using Ctl-Alt-F2 to get a non-X session). After that, I tried logging in to a gnome session, and got logged out during login processing. This happened a few times; then I installed xfce4, rebooted, and got the same behaviour (logout during login processing) while trying to log in to an xfce session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 Date: Tue Feb 25 12:06:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] InstallationDate: Installed on 2020-02-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) 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 (i440FX + PIIX, 1996) ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=14c5cf63-466a-44d5-add6-bd5fc486c067 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-eoan dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-eoan:cvnQEMU:ct1:cvrpc-i440fx-eoan: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-eoan dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1864644/+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 1865222] Re: windows disappearing unless in Activities view
Thank for the report and upstream. There has been no other mention of the issue so far so we decided to not target it as a rls bug for now, we should revisit if we get new reports though ** Tags removed: champagne ** Tags added: rls-not-fixing -- 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/1865222 Title: windows disappearing unless in Activities view Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: It's happened to me twice after a recent update that I couldn't reach a window, even though it was visible in the Activities view and listed on the launcher. The windows seemed to take focus, but couldn't be seen. Alt+Tab switching didn't help either. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 22:00:29 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-10 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/usr/bin/zsh RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1865222/+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 1864644] Re: I get logged out immediately after login to an X session (QXL Xorg driver on kernel 5.4)
The messages Daniel found in comment #4 indicate a systemd issue that I fixed upstream a few months ago. I'm sorry, I thought we already had the fix in Ubuntu but it seems we don't - it's in v245. We need the commits 625077264ba01a108386eeea733ee244e6b7ff14 867af7282b2eccab53727714172b1081532ca8de (actually this is optional) d5016c21d7bb60f38aa461887cd843fabbc986ca 3a827125e70aa2cabbb97334f75576229efd6868 (also optional but we should take it) to fix this issue. You can read the upstream issue: https://github.com/systemd/systemd/issues/14322 for more information. ** Changed in: xserver-xorg-video-qxl (Ubuntu) Status: New => Invalid ** Bug watch added: github.com/systemd/systemd/issues #14322 https://github.com/systemd/systemd/issues/14322 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/1864644 Title: I get logged out immediately after login to an X session (QXL Xorg driver on kernel 5.4) Status in systemd package in Ubuntu: Confirmed Status in xserver-xorg-video-qxl package in Ubuntu: Invalid Bug description: I just installed ubuntu 20.04 in a virtual machine and did 'apt-get update;apt-get upgrade' to get current (using Ctl-Alt-F2 to get a non-X session). After that, I tried logging in to a gnome session, and got logged out during login processing. This happened a few times; then I installed xfce4, rebooted, and got the same behaviour (logout during login processing) while trying to log in to an xfce session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 Date: Tue Feb 25 12:06:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] InstallationDate: Installed on 2020-02-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) 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 (i440FX + PIIX, 1996) ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=14c5cf63-466a-44d5-add6-bd5fc486c067 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-eoan dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-eoan:cvnQEMU:ct1:cvrpc-i440fx-eoan: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-eoan dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1864644/+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 1825710] Re: Remove "Application is ready" notification
tagging rls-ff-notfixing that's an usability issue but not one we have the resources to address this cycle ** Tags removed: champagne ** Tags added: rls-ff-notfixing -- 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/1825710 Title: Remove "Application is ready" notification Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: The "Application is ready" notification is pointless, really. Say, I click on the open downloads folder button in Firefox and GNOME Shell gives me a notification saying "Application is ready" but doesn't open the notification. I'm totally expecting an app to open because I actively initiated it. As a workaround, I'm using a GNOME extensions "Focus my Window" which removes the "Application is ready" message and focuses the app window automatically. However, this cannot be treated as a solution. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1825710/+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 1862308] Re: Desktop wallpaper is slightly blurry in Gnome 3.34
** Tags removed: champagne ** Tags added: rls-ff-notfixing -- 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/1862308 Title: Desktop wallpaper is slightly blurry in Gnome 3.34 Status in mutter package in Ubuntu: In Progress Bug description: Desktop wallpaper is slightly blurry in Gnome 3.34. Upstream fix pending: https://gitlab.gnome.org/GNOME/mutter/merge_requests/1003 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Fri Feb 7 16:08:58 2020 DisplayManager: InstallationDate: Installed on 2020-02-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1862308/+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 1864052] Re: gnome-shell crashed with SIGABRT in src/core/window.c:1591:meta_window_unmanage: assertion failed: (g_list_find (workspace->windows, window) == NULL)
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
--
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/1864052
Title:
gnome-shell crashed with SIGABRT in
src/core/window.c:1591:meta_window_unmanage: assertion failed:
(g_list_find (workspace->windows, window) == NULL)
Status in gnome-shell package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/3e51baba6960038ed185034581cb83e4dd4776e6
---
gnome-shell crashes whenever in CHrome you pop out a video into a
floating video, or close the floating video (move the video back into
the main window).
To test, you can use
javascript:document.getElementsByTagName('video')[0].requestPictureInPicture();
to make a video float on any site, even if the site does not have a
button for it. I only tested Netflix.
ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.34.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Feb 20 15:36:33 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2018-03-14 (707 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
() at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
() at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0
() at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0
() at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0
Title: gnome-shell crashed with SIGABRT
UpgradeStatus: Upgraded to focal on 2019-11-25 (87 days ago)
UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild
sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1864052/+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 1859782] Re: Xwayland apps like glxgears or Chromium report 58 FPS on a 60Hz display
The issue is specific to wayland session which isn't the default -> not tracking for rls sorry ** Tags removed: champagne ** Tags added: rls-ff-notfixing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1859782 Title: Xwayland apps like glxgears or Chromium report 58 FPS on a 60Hz display Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Triaged Bug description: Xwayland apps like glxgears report 58 FPS on a 60Hz display. This does not happen in a native Xorg login. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xwayland 2:1.20.6-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Jan 15 18:18:00 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 630 [17aa:3102] InstallationDate: Installed on 2019-12-02 (44 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191201) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 17ef:6009 Lenovo ThinkPad Keyboard with TrackPoint Bus 001 Device 003: ID 045e:0823 Microsoft Corp. Microsoft® Classic IntelliMouse® Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 10M7CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=37e661a7-90ed-4c1c-b0f0-b564dbd4a532 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M16KT47A dmi.board.name: 3102 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259627060530 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710s dmi.product.name: 10M7CTO1WW dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s dmi.product.version: ThinkCentre M710s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1859782/+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 1866851] [NEW] lock screen scaled down backgound image in top left corner
Public bug reported: The new lock screen in gnome 3.36 looks strange, as if the blurred background image is being scaled down to the top left corner of the screen. background image being used is 1920x1440 pixel jpeg, display size is 3840x2160, with fractional scaling enabled and set to 175% on wayland. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 10 07:38:52 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (206 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-06 (3 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session ** Attachment added: "IMG_20200310_073917.jpg" https://bugs.launchpad.net/bugs/1866851/+attachment/5335362/+files/IMG_20200310_073917.jpg ** Description changed: - The new lock screen in gnome 3.26 looks strange, as if the blurred + The new lock screen in gnome 3.36 looks strange, as if the blurred background image is being scaled down to the top left corner of the screen. background image being used is 1920x1440 pixel jpeg, display size is 3840x2160, with fractional scaling enabled and set to 175% on wayland. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 10 07:38:52 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (206 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-06 (3 days ago) -- 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/1866851 Title: lock screen scaled down backgound image in top left corner Status in gnome-shell package in Ubuntu: New Bug description: The new lock screen in gnome 3.36 looks strange, as if the blurred background image is being scaled down to the top left corner of the screen. background image being used is 1920x1440 pixel jpeg, display size is 3840x2160, with fractional scaling enabled and set to 175% on wayland. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 10 07:38:52 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (206 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-06 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866851/+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 1855893] Re: Properly let PCM leave suspended state when hardware doesn't support PCM resume
@Kai-Heng, you unassigned yourself, does it mean it's not important anymore for bionic and the target should be dropped? -- 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/1855893 Title: Properly let PCM leave suspended state when hardware doesn't support PCM resume Status in HWE Next: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: In Progress Bug description: [Impact] Headset Mic plugged into Dell WD19TB dock stops working after suspend/resume. [Fix] According to alia-lib's document, to make PCM properly leave suspended state, we only use snd_pcm_resume() if hardware support PCM resume. For hardware that doesn't support PCM resume, like snd-usb-audio on WD19TB dock, we should use snd_pcm_prepare(), snd_pcm_drop() or snd_pcm_drain() to make device leave suspended state. This patch defaults to use snd_pcm_drop() to achieve the goal. [Test] 1. See if microphone on snd-usb-audio works in gnome-control-center/cheese. 2. Suspend/resume. 3. See if microphone still works in those apps. I can the issue is fixed after each suspend/resume cycle. [Regression Potential] Low. This fix makes PCM suspend/resume more reliable. No functional change intended. I also don't find any regression during some smoke test. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1855893/+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 1865838] Re: no error displayed on failed fingerprint authentification
** Also affects: gdm via https://gitlab.gnome.org/GNOME/gdm/issues/567 Importance: Unknown Status: Unknown ** Changed in: gdm3 (Ubuntu) Importance: Undecided => High ** Changed in: gdm3 (Ubuntu) Status: New => Triaged -- 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/1865838 Title: no error displayed on failed fingerprint authentification Status in gdm: Unknown Status in OEM Priority Project: New Status in gdm3 package in Ubuntu: Triaged Bug description: from journalctl, gdm-fingerprint shows error there after retried 5 times of fingerprint login failed, so I open this issue here. Steps to reproduce issue: 1. enroll fingerprint for your right index finger. 2. logout 3. login and try login by incorrect finger e.g. middle finger 4. after 5 times retry. There's no error popup, then re-try index finger still no any message remind users they can not try fingerprint anymore. It will confuse user. Suggest behavior: 1. Each time user try fingerprint failed, show error message to remind user. 2. When user exceed 5 time errors, show error message to remind user input password instead. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 15:32:00 2020 InstallationDate: Installed on 2020-03-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865838/+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 1725180] Re: Shell animations are not smooth
** Tags removed: champagne ** Tags added: rls-ff-notfixing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1725180 Title: Shell animations are not smooth Status in gjs: Fix Released Status in GNOME Shell: Fix Released Status in gjs package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Triaged Bug description: Upstream fixes required to make all the overview/window/icon animations much smoother (at least halving render times): https://gitlab.gnome.org/GNOME/gjs/merge_requests/390 https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/948 https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/936 https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/1002 __ +++UBUNTU RELEASE+++ Description: Ubuntu 17.10 Release: 17.10 +++PACKAGE VERSION+++ xwayland: Installed: 2:1.19.5-0ubuntu2 Candidate: 2:1.19.5-0ubuntu2 Version table: *** 2:1.19.5-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status Bug found on Dell XPS 9560 4K model with GTX1050/Intel HD 630. Currently using Intel HD Graphics 630 as Nvidia seems to have no support for xwayland. The window/dock/launcher animations are lagging/shaky (not smooth). __ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xwayland 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 19:09:27 2017 DistUpgraded: 2017-10-20 04:51:46,123 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-387, 387.12, 4.13.0-16-generic, x86_64: installed v4l2loopback, 0.10.0, 4.10.0-37-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-16-generic, x86_64: installed ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be] InstallationDate: Installed on 2017-05-24 (149 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=38514616-2735-4966-91f7-71f1d60beb73 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) dmi.bios.date: 08/30/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1725180/+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 1866574] Re: Update to 1.56
** Changed in: snapd-glib (Ubuntu Bionic) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: snapd-glib (Ubuntu Eoan) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1866574 Title: Update to 1.56 Status in snapd-glib package in Ubuntu: Fix Committed Status in snapd-glib source package in Bionic: New Status in snapd-glib source package in Eoan: New Status in snapd-glib source package in Focal: Fix Committed Bug description: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Any new release has a risk of introducing bugs, this is mitigated by automatic regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1866574/+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 1866842] Re: AppArmor prevents evince to open >1 PDF file
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: evince (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1866842 Title: AppArmor prevents evince to open >1 PDF file Status in evince package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04 (focal), evince 3.35.92-1 and 3.36.0-1 fail to open more than one PDF file via the command line: $ evince x.pdf y.pdf z.pdf Error launching evince file:///home/xyz/.../y.pdf: Failed to execute child process “/bin/sh” (Permission denied) Error launching evince file:///home/xyz/.../z.pdf: Failed to execute child process “/bin/sh” (Permission denied) Expected behavior: evince starts with one window each for x.pdf, y.pdf and z.pdf Actual behavior: evince starts with one window x.pdf dmesg output: [104866.021294] audit: type=1400 audit(1583846983.478:3714): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/bin/dash" pid=131016 comm="evince" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 [104866.022450] audit: type=1400 audit(1583846983.482:3715): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/bin/dash" pid=131019 comm="evince" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 CurrentDesktop: KDE Date: Tue Mar 10 14:20:38 2020 InstallationDate: Installed on 2016-11-26 (1199 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) SourcePackage: evince UpgradeStatus: Upgraded to focal on 2020-03-06 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1866842/+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 1786702] Re: List view content doubles whenever selected
Confirming fixed with gnome-characters 3.34.0-1 in Ubuntu 20.04. ** Changed in: gnome-characters (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/1786702 Title: List view content doubles whenever selected Status in gnome-characters package in Ubuntu: Fix Released Bug description: In gnome-characters, when selecting a category for the first time, the contents are fine. When selecting another category and then going back to the first one, the contents of the list view are doubled, all symbols are appended again to the list. This can most easily be seen in a category with only few symbols, like "Flags" (see attached screenshot). A restart of the app resets the list view contents to only a single set. 1) $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 2) $ apt-cache policy gnome-characters gnome-characters: Installed: (none) Candidate: 3.28.2-0ubuntu1 Version table: 3.28.2-0ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 3.28.0-3 500 500 http://ch.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) The categories should look the same whenever selected. 4) The categories expand whenever selected again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-characters/+bug/1786702/+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 1866842] [NEW] AppArmor prevents evince to open >1 PDF file
Public bug reported: On Ubuntu 20.04 (focal), evince 3.35.92-1 and 3.36.0-1 fail to open more than one PDF file via the command line: $ evince x.pdf y.pdf z.pdf Error launching evince file:///home/xyz/.../y.pdf: Failed to execute child process “/bin/sh” (Permission denied) Error launching evince file:///home/xyz/.../z.pdf: Failed to execute child process “/bin/sh” (Permission denied) Expected behavior: evince starts with one window each for x.pdf, y.pdf and z.pdf Actual behavior: evince starts with one window x.pdf dmesg output: [104866.021294] audit: type=1400 audit(1583846983.478:3714): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/bin/dash" pid=131016 comm="evince" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 [104866.022450] audit: type=1400 audit(1583846983.482:3715): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/bin/dash" pid=131019 comm="evince" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 CurrentDesktop: KDE Date: Tue Mar 10 14:20:38 2020 InstallationDate: Installed on 2016-11-26 (1199 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) SourcePackage: evince UpgradeStatus: Upgraded to focal on 2020-03-06 (4 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1866842 Title: AppArmor prevents evince to open >1 PDF file Status in evince package in Ubuntu: New Bug description: On Ubuntu 20.04 (focal), evince 3.35.92-1 and 3.36.0-1 fail to open more than one PDF file via the command line: $ evince x.pdf y.pdf z.pdf Error launching evince file:///home/xyz/.../y.pdf: Failed to execute child process “/bin/sh” (Permission denied) Error launching evince file:///home/xyz/.../z.pdf: Failed to execute child process “/bin/sh” (Permission denied) Expected behavior: evince starts with one window each for x.pdf, y.pdf and z.pdf Actual behavior: evince starts with one window x.pdf dmesg output: [104866.021294] audit: type=1400 audit(1583846983.478:3714): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/bin/dash" pid=131016 comm="evince" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 [104866.022450] audit: type=1400 audit(1583846983.482:3715): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/bin/dash" pid=131019 comm="evince" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 CurrentDesktop: KDE Date: Tue Mar 10 14:20:38 2020 InstallationDate: Installed on 2016-11-26 (1199 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) SourcePackage: evince UpgradeStatus: Upgraded to focal on 2020-03-06 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1866842/+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 1866222] Re: GNOME Shell crashed with signal 11
I will look into it. Here is how to reproduce the bug very easily: - open LibreOffice Writer - open Firefox - resize and move the windows so that they don't overlap - drag the Firefox tab (not window) over LibreOffice Then you instantly get the crash. -- 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/1866222 Title: GNOME Shell crashed with signal 11 Status in gnome-shell package in Ubuntu: Incomplete Bug description: gnome-shell has crashed twice on me today. Unfortunately there's nothing in /var/crash. There's nothing in the journalctl log prior to the crash that explains it. I've attached a log of everything between when the crash happened and when I logged back in (though I suspect most of it is not relevant). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 13:04:21 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (201 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-31 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+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 1832988] Re: Intel 8260 Bluetooth not working
Can you please test Focal daily: http://cdimages.ubuntu.com/daily-live/current/focal-desktop-amd64.iso -- 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/1832988 Title: Intel 8260 Bluetooth not working Status in gnome-bluetooth package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Bug description: Expected behaviour: I can enable bluetooth in the system settings, and pair with my other devices. Actual behaviour: Always displays as 'off' in the settings dialog, and won't turn on. Bluetooth worked on the same machine with previous Ubuntu releases (18.10) & no hardware changes. "dmesg | grep -i bluetooth" reports the following: ``` [ 14.445902] Bluetooth: Core ver 2.22 [ 14.445918] Bluetooth: HCI device and connection manager initialized [ 14.445921] Bluetooth: HCI socket layer initialized [ 14.445923] Bluetooth: L2CAP socket layer initialized [ 14.445929] Bluetooth: SCO socket layer initialized [ 14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 14.499050] Bluetooth: hci0: Device revision is 5 [ 14.499052] Bluetooth: hci0: Secure boot is enabled [ 14.499053] Bluetooth: hci0: OTP lock is enabled [ 14.499053] Bluetooth: hci0: API lock is enabled [ 14.499054] Bluetooth: hci0: Debug lock is disabled [ 14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38) [ 15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.497806] Bluetooth: BNEP filters: protocol multicast [ 15.497810] Bluetooth: BNEP socket layer initialized ``` "lsb_release -rd" reports the following: ``` Description: Ubuntu 19.04 Release: 19.04 ``` "cat /proc/version_signature" reports the following: ``` Ubuntu 5.0.0-16.17-generic 5.0.8 ``` "apt-cache policy linux-firmware" reports the following: ``` linux-firmware: Installed: 1.178.1 Candidate: 1.178.1 Version table: *** 1.178.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main i386 Packages 100 /var/lib/dpkg/status 1.178 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco/main i386 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 2314 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 12:31:07 2019 InstallationDate: Installed on 2019-06-02 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 003: ID 5986:066d Acer, Inc Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: PC Specialist Limited N15_17RD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N15_17RD dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.11:bd12/25/2015:svnPCSpecialistLimited:pnN15_17RD:pvrNotApplicable:rvnCLEVO:rnN15_17RD:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N15_17RD dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1832988/+subscriptions -- Mailing
[Desktop-packages] [Bug 1865499] Re: pulseaudio doesn't detect (new) USB headset
Quick update: the package updates from the proposed repository for
* libasound2-data,
* libasound2:amd64, and
* libasound2:i386
seemed to fixed the problems.
All affected USB headsets we use
* Logitech 960,
* SennHheiser PC8, and
* Plantronics Blackwire 3220
now are detected on every hot-plug.
When will the packages move from proposedto updates or security?
--
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/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in pulseaudio package in Ubuntu:
New
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+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 1832988] Re: Intel 8260 Bluetooth not working
As a workaround I'm currently doing rmmod btusb && modprobe btusb after every boot which seem to do the magic. Attaching the dmesg for that just in case. ** Attachment added: "dmesg2.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832988/+attachment/5335332/+files/dmesg2.log -- 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/1832988 Title: Intel 8260 Bluetooth not working Status in gnome-bluetooth package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Bug description: Expected behaviour: I can enable bluetooth in the system settings, and pair with my other devices. Actual behaviour: Always displays as 'off' in the settings dialog, and won't turn on. Bluetooth worked on the same machine with previous Ubuntu releases (18.10) & no hardware changes. "dmesg | grep -i bluetooth" reports the following: ``` [ 14.445902] Bluetooth: Core ver 2.22 [ 14.445918] Bluetooth: HCI device and connection manager initialized [ 14.445921] Bluetooth: HCI socket layer initialized [ 14.445923] Bluetooth: L2CAP socket layer initialized [ 14.445929] Bluetooth: SCO socket layer initialized [ 14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 14.499050] Bluetooth: hci0: Device revision is 5 [ 14.499052] Bluetooth: hci0: Secure boot is enabled [ 14.499053] Bluetooth: hci0: OTP lock is enabled [ 14.499053] Bluetooth: hci0: API lock is enabled [ 14.499054] Bluetooth: hci0: Debug lock is disabled [ 14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38) [ 15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.497806] Bluetooth: BNEP filters: protocol multicast [ 15.497810] Bluetooth: BNEP socket layer initialized ``` "lsb_release -rd" reports the following: ``` Description: Ubuntu 19.04 Release: 19.04 ``` "cat /proc/version_signature" reports the following: ``` Ubuntu 5.0.0-16.17-generic 5.0.8 ``` "apt-cache policy linux-firmware" reports the following: ``` linux-firmware: Installed: 1.178.1 Candidate: 1.178.1 Version table: *** 1.178.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main i386 Packages 100 /var/lib/dpkg/status 1.178 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco/main i386 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 2314 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 12:31:07 2019 InstallationDate: Installed on 2019-06-02 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 003: ID 5986:066d Acer, Inc Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: PC Specialist Limited N15_17RD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N15_17RD dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.11:bd12/25/2015:svnPCSpecialistLimited:pnN15_17RD:pvrNotApplicable:rvnCLEVO:rnN15_17RD:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N15_17RD dmi.product.sku: Not Applicable dmi.product.version: Not
[Desktop-packages] [Bug 1832988] Re: Intel 8260 Bluetooth not working
Still failing with the same error on latest Eoan (kernel 5.3.0-40-generic). Dmesg with default kernel and usbcore.dyndbg=+p attached. ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832988/+attachment/5335331/+files/dmesg.log -- 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/1832988 Title: Intel 8260 Bluetooth not working Status in gnome-bluetooth package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Bug description: Expected behaviour: I can enable bluetooth in the system settings, and pair with my other devices. Actual behaviour: Always displays as 'off' in the settings dialog, and won't turn on. Bluetooth worked on the same machine with previous Ubuntu releases (18.10) & no hardware changes. "dmesg | grep -i bluetooth" reports the following: ``` [ 14.445902] Bluetooth: Core ver 2.22 [ 14.445918] Bluetooth: HCI device and connection manager initialized [ 14.445921] Bluetooth: HCI socket layer initialized [ 14.445923] Bluetooth: L2CAP socket layer initialized [ 14.445929] Bluetooth: SCO socket layer initialized [ 14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 14.499050] Bluetooth: hci0: Device revision is 5 [ 14.499052] Bluetooth: hci0: Secure boot is enabled [ 14.499053] Bluetooth: hci0: OTP lock is enabled [ 14.499053] Bluetooth: hci0: API lock is enabled [ 14.499054] Bluetooth: hci0: Debug lock is disabled [ 14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38) [ 15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.497806] Bluetooth: BNEP filters: protocol multicast [ 15.497810] Bluetooth: BNEP socket layer initialized ``` "lsb_release -rd" reports the following: ``` Description: Ubuntu 19.04 Release: 19.04 ``` "cat /proc/version_signature" reports the following: ``` Ubuntu 5.0.0-16.17-generic 5.0.8 ``` "apt-cache policy linux-firmware" reports the following: ``` linux-firmware: Installed: 1.178.1 Candidate: 1.178.1 Version table: *** 1.178.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main i386 Packages 100 /var/lib/dpkg/status 1.178 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco/main i386 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 2314 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 12:31:07 2019 InstallationDate: Installed on 2019-06-02 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 003: ID 5986:066d Acer, Inc Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: PC Specialist Limited N15_17RD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N15_17RD dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.11:bd12/25/2015:svnPCSpecialistLimited:pnN15_17RD:pvrNotApplicable:rvnCLEVO:rnN15_17RD:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N15_17RD dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor:
[Desktop-packages] [Bug 1865845] Re: No UI indication for fingerprint enrolling progress
** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1865845/+attachment/5335240/+files/journalctl.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1865845 Title: No UI indication for fingerprint enrolling progress Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Incomplete Bug description: there is no progress information shows to user while enrolling fingerprint. It might confuse user thinking it as freeze failure. steps: 1. enroll fingerprint in gnome-control-center 2. click 'Next' on the enrolling page 3. There is no message tell user that it need at least 12 times touching fingerprint. 4. user press fingerprint for 5 times, there is no way to cancel enrolling. 5. user wait for timeout and get error message for timeout notification. 6. after 5. user page of setting will always failed and show no user found. So, the suggestion would be: 1. remind user to press 12 times on fingerprint for step 3. 2. show the progress during user pressing fingerprint for step 4. And this also introduce some critical issue of step 6 that user page in settings failed forever. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 16:44:13 2020 InstallationDate: Installed on 2020-03-02 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1865845/+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 1865845] Re: No UI indication for fingerprint enrolling progress
from the latest IHV driver, it seems the requested enroll stage (12) exceeds MAX_ENROLL_STAGES (10). I'm trying to extend MAX_ENROLL_STAGES but it seems still failed. It's puzzle to me for now that who provided the 12 times requesting and why it failed to exceed MAX_ENROLL_STAGES. ** Attachment added: "gnome-control-center.log" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1865845/+attachment/5335239/+files/gnome-control-center.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1865845 Title: No UI indication for fingerprint enrolling progress Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Incomplete Bug description: there is no progress information shows to user while enrolling fingerprint. It might confuse user thinking it as freeze failure. steps: 1. enroll fingerprint in gnome-control-center 2. click 'Next' on the enrolling page 3. There is no message tell user that it need at least 12 times touching fingerprint. 4. user press fingerprint for 5 times, there is no way to cancel enrolling. 5. user wait for timeout and get error message for timeout notification. 6. after 5. user page of setting will always failed and show no user found. So, the suggestion would be: 1. remind user to press 12 times on fingerprint for step 3. 2. show the progress during user pressing fingerprint for step 4. And this also introduce some critical issue of step 6 that user page in settings failed forever. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 16:44:13 2020 InstallationDate: Installed on 2020-03-02 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1865845/+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 1866813] [NEW] chromium moved profile without warning on deb->snap transition
Public bug reported: >From what I've read on the snap package it copied the profile. My profile was kept on encrypted drive and bind mounted to .config/chromium Freely copying user data, most often delicate (passwords, browser history) without any warning is a bad thing. At least I'd expect apt warn me that the profile will move. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- 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/1866813 Title: chromium moved profile without warning on deb->snap transition Status in chromium-browser package in Ubuntu: New Bug description: From what I've read on the snap package it copied the profile. My profile was kept on encrypted drive and bind mounted to .config/chromium Freely copying user data, most often delicate (passwords, browser history) without any warning is a bad thing. At least I'd expect apt warn me that the profile will move. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1866813/+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 1018622] Re: [SB Live! Platinum CT4760P] No sound
Alright, thanks for the update Knightnet. ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1018622 Title: [SB Live! Platinum CT4760P] No sound Status in alsa-driver package in Ubuntu: Invalid Bug description: No further information available. Seems to be a common Ubuntu/Debian problem as few distro's produce sound from this card. Had same problems with Debian 32bit installation. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: julian 4547 F pulseaudio Card0.Amixer.info: Card hw:0 'Live'/'SB Live! Platinum [CT4760P] (rev.7, serial:0x80401102) at 0xa000, irq 18' Mixer name : 'SigmaTel STAC9721,23' Components : 'AC97a:83847609' Controls : 217 Simple ctrls : 38 Card1.Amixer.info: Card hw:1 'CK804'/'NVidia CK804 with ALC850 at irq 22' Mixer name : 'Realtek ALC850 rev 0' Components : 'AC97a:414c4790' Controls : 42 Simple ctrls : 27 CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied dmesg: write failed: Broken pipe Date: Wed Jun 27 23:09:49 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS A8N-SLI DELUXE ACPI BIOS Revision 1805 dmi.board.name: A8N-SLI DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-SLIDELUXEACPIBIOSRevision1805:bd09/29/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8N-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1018622/+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 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
If possible, try to participate in the bug report that I have opened on gitlab and to share your experiences If I am the only one discussing the problem, it will hardly be considered soon https://gitlab.freedesktop.org/drm/intel/issues/1377 -- 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/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767654/+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 1856884] Re: not proper sound device
*** This bug is a duplicate of bug 1847570 *** https://bugs.launchpad.net/bugs/1847570 after updating to modern 19.10 apt update and upgrade i have 1)after sleeping my 2.1 system doesns't exist and i don't hear any sound. systemctl --user restart pulseaudio this helps. But how could we fix it. maybe it happened after this fix. I need a help and give all information. My computer is modern. -- 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/1856884 Title: not proper sound device Status in pulseaudio package in Ubuntu: Incomplete Bug description: when i insert or take out my headphones , the system doesn't send signal on my headphones, i need to switch by hand. it worked in ubuntu 18.10 correct. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob1929 F pulseaudio /dev/snd/controlC1: rob1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (326 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (43 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 dmi.board.vendor: ASRock 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884/+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 1864778] Re: Intel Drivers Artifacts after Mesa-Dev Update
I have a similar problem, the fonts are broken, just small rectangles: https://www.ap-i.net/mantis/view.php?id=2291 corrado@corrado-x5-ff-0309:~$ inxi -SCGxx System: Host: corrado-x5-ff-0309 Kernel: 5.4.0-14-generic x86_64 bits: 64 compiler: gcc v: 9.2.1 Desktop: Gnome 3.35.91 wm: gnome-shell dm: GDM3 Distro: Ubuntu 20.04 LTS (Focal Fossa) CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 801 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 802 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5912 Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.0 direct render: Yes corrado@corrado-x5-ff-0309:~$ ** Bug watch added: Skychart bug tracker #2291 http://www.ap-i.net/mantis/view.php?id=2291 -- 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/1864778 Title: Intel Drivers Artifacts after Mesa-Dev Update Status in mesa package in Ubuntu: Confirmed Bug description: After the update from the 20.04 LTS fresh live image from 19.3.3-1ubuntu1 to 20.0.0-1ubuntu1 mesa I get serious artifacts on startup when using the intel driver instead of modesetting. These artifacts go away when I enable Option AccelMethod "uxa" but persist if the default, "sna" or the other modes are used "none", "off", "blt". These pixels appear throughout the experience of using Ubuntu and generate in sporadic places. The font also looks completely broken. I've never had this issue before with the Intel drivers. I have Skylake HD 530. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1864778/+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 1864778] Re: Intel Drivers Artifacts after Mesa-Dev Update
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- 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/1864778 Title: Intel Drivers Artifacts after Mesa-Dev Update Status in mesa package in Ubuntu: Confirmed Bug description: After the update from the 20.04 LTS fresh live image from 19.3.3-1ubuntu1 to 20.0.0-1ubuntu1 mesa I get serious artifacts on startup when using the intel driver instead of modesetting. These artifacts go away when I enable Option AccelMethod "uxa" but persist if the default, "sna" or the other modes are used "none", "off", "blt". These pixels appear throughout the experience of using Ubuntu and generate in sporadic places. The font also looks completely broken. I've never had this issue before with the Intel drivers. I have Skylake HD 530. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1864778/+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 1759462] Re: Keyboard shortcuts not operational on 18.04
Kubuntu 18.04.04 doesnt have Dolphin shortcut Ctrl+E https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1866763 Kubuntu 18.04.04 terminal doenst have shortcut ctrl+t https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1866764 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1759462 Title: Keyboard shortcuts not operational on 18.04 Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: After installing 18.04, I noticed that certain keyboard shortcuts no longer function. It appears to be related to the shortcuts that gnome-settings-daemon control as my shortcuts that are provided by my desktop (Budgie) still function. Some examples are: * Media keys for volume up/down/mute * ctrl-alt-t for the terminal. I tried changing the shortcut to test. Same behaviour. I double checked, and it looks like the needed daemon is still running, ``` dustin3337 0.0 0.2 500736 22216 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-keyboard dustin3338 0.0 0.3 943372 25732 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-media-keys dustin3343 0.0 0.0 274908 5844 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-mouse dustin3345 0.0 0.3 519896 25144 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-power dustin3348 0.0 0.1 346004 10212 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-print-notifications dustin3351 0.0 0.0 374684 7952 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-smartcard dustin3355 0.0 0.1 329584 8064 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-sound dustin3361 0.0 0.1 449708 9856 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-sharing dustin3367 0.0 0.0 272416 4772 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy dustin3375 0.0 0.0 420028 5804 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-rfkill dustin3383 0.0 0.2 507120 23244 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-wacom dustin3385 0.0 0.3 498040 25040 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-xsettings dustin3387 0.0 0.0 274900 5936 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-a11y-settings dustin3392 0.0 0.2 496016 22044 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-clipboard dustin3395 0.0 0.3 810156 25976 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-color dustin3396 0.0 0.2 471656 21080 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-datetime dustin3400 0.0 0.0 361196 7116 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-housekeeping dustin3433 0.0 0.1 505404 12576 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-printer dustin9776 0.0 0.0 18188 1032 pts/1S+ 21:19 0:00 grep --color=auto gnome-settings-daemon ``` Reboot does not seem to help. However, occasionally the shortcuts do seem to work - but only very occasionally. Any other info needed? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Mar 27 21:12:18 2018 InstallationDate: Installed on 2018-03-05 (22 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1759462/+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 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series
Test result: https://docs.google.com/spreadsheets/d/1A_nTnwoxzFGpirKbqpQL4bYVBD0ZbDJVicjuZpgVbv4/edit#gid=566033014 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1854485 Title: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Bionic: In Progress Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-440 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Eoan: In Progress Status in nvidia-graphics-drivers-340 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-390 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-440 source package in Eoan: Fix Committed Status in nvidia-settings source package in Eoan: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] 440.40: * New upstream release: - Added support for the following GPU: Quadro T2000 with Max-Q Design - Added support for the __GL_SYNC_DISPLAY_DEVICE environment variable for Vulkan applications. - Fixed a bug that caused applications running directly on a display (such as VR HMDs) to tear when a G-SYNC or G-SYNC Compatible monitor is plugged in the system. - Fixed a bug in an error handling path that could cause a kernel crash while loading nvidia.ko. - Fixed driver installation failure on Oracle Linux 7.7 systems, where the NVIDIA kernel module failed to build with error "unknown type name 'vm_fault_t'". * Changes from the 440.36 series: - Added support for the following GPUs: o GeForce GTX 1650 SUPER o GeForce GTX 1660 SUPER - Fixed graphical corruption that can occur when using glslang SPIR-V Generator Version <= 2. - Fixed a bug that could cause the X server to crash when running applications using GLX indirect rendering. - Updated the Module.symvers sanity check, which is part of the NVIDIA kernel module build process, to accommodate the recent addition of a new field in the Module.symvers file format. This fixes the error "The Module.symvers file is missing [...]" seen during driver installation or DKMS rebuilds with Linux 5.4 RC kernels. - Fixed kernel module build problems with Linux kernel 5.4.0 release candidates. - Updated nvidia-bug-report.sh to collect information about X server crashes from coredumpctl, when available. - Updated the nvidia-drm kernel module for compatibility with the removal of the DRIVER_PRIME flag in recent Linux kernel versions. - Enabled parallel GLSL shader linking by default; i.e., allow GL_ARB_parallel_shader_compile to work without first calling glMaxShaderCompilerThreadsARB(). - Added support for HDMI 2.1 variable refresh rate (VRR) G-SYNC Compatible monitors on supported GPUs.For more details, see "Configuring Multiple Display Devices on One X Screen" in the README. Added support for the GLX_NV_multigpu_context and GL_NV_gpu_multicast extensions.For more details, see the "Configuring SLI and Multi-GPU FrameRendering" chapter of the README, and the extension specifications: https://www.khronos.org/registry/OpenGL/extensions/NV/GLX_NV_multigpu_context.txt
