[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
Any progress? I'm having a hard time to understand what's preventing the upgrade to TB78. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Triaged Status in thunderbird source package in Focal: Fix Committed Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+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 1903893] Re: [snap] Notifications do not show a custom icon
This was also reported upstream: https://bugs.chromium.org/p/chromium/issues/detail?id=1160601. -- 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/1903893 Title: [snap] Notifications do not show a custom icon Status in chromium-browser package in Ubuntu: Confirmed Bug description: Hi, Notification coming from Chromium web browser ( as a snap ) show generic icon instead of favicon or website icon or any website picture. For reference ⋅ https://forum.snapcraft.io/t/notifications-in-chromium-show-generic-icon/21079 ⋅ https://github.com/solus-project/budgie-desktop/pull/2000#issuecomment-653833784 ⋅ https://discourse.ubuntubudgie.org/t/notification-issues/434 It's *not* specific to ( Ubuntu ) Budgie. And to some extent might affect any chromium snap based web browser. Interesting insight in second link, quoting : « Chromium based browser notifications pop up with broken icon images. This is due to the fact these browsers prefix the icon name in the notification with "file:///". Furthermore, snap based chromium browsers save the temporary icon in the snap, and don't pass the correct path to Raven. If the icon names start with "file:///", clearing the icon name fixes both of these issues by allowing the browsers to show the correct image (same as Firefox does), and allows the snaps to default to the fallback "mail-unread-symbolic" icon, instead of showing a broken image icon. This fix also should have absolutely no effect on any other notifications. » Attachment : top right is the actual notification ( with unread mail icon ) it should show : ⋅ ideally, picture from site ( cover art in that case, it's a music streaming site, as done in Firefox in same situation ) ⋅ or (fav)icon for the site ( deezer here, which icon is shown a bit above in workspaces applet in top panel ) ⋅ or web browser icon ( chromium ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1903893/+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 1900481] Re: [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect card
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1900481 Title: [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Expired Bug description: Following upgrade to 20.04, I have no audio. My output device is "Dummy Output". I chose one audio device to report against: none are detected. All this may be obvious from the auto-detected diagnostics. It was working in 18.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Oct 19 19:43:52 2020 InstallationDate: Installed on 2018-05-05 (897 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180505) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel MID Symptom_Jack: Mic, Top Title: [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 030DMJ dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3300:pvrA10:rvnDellInc.:rn030DMJ:rvrA10:cvnDellInc.:ct8:cvrA10: dmi.product.name: Vostro 3300 dmi.product.sku: To be filled by O.E.M. dmi.product.version: A10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1900481/+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 1910480] Re: no audio on fresh install kubuntu groovy
** 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/1910480 Title: no audio on fresh install kubuntu groovy Status in alsa-driver package in Ubuntu: New Bug description: on installing Kubuntu Groovy 'no output or input devices found' sound appears to be disabled running ubuntu-debug -s audio does produce sound in both headphone channels in first part of test but no sound in second part sound is recognised and working okay if Kubuntu Focal is installed ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1071 F pulseaudio bob1074 F pipewire-media- /dev/snd/controlC1: bob1074 F pipewire-media- /dev/snd/seq:bob1070 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Jan 7 03:19:48 2021 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful Symptom_Card: Built-in Audio - HDA ATI SB Symptom_Jack: SPDIF Out, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: None of the above Title: [MBB-895908, Realtek ALC892, SPDIF Out, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A99FX PRO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: 7354844-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/07/2014:br4.6:svnNOVATECHLTD:pnMBB-895908:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx:cvnNOVATECHLTD:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MBB-895908 dmi.product.sku: SKU dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1910480/+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 1910480] [NEW] no audio on fresh install kubuntu groovy
You have been subscribed to a public bug: on installing Kubuntu Groovy 'no output or input devices found' sound appears to be disabled running ubuntu-debug -s audio does produce sound in both headphone channels in first part of test but no sound in second part sound is recognised and working okay if Kubuntu Focal is installed ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1071 F pulseaudio bob1074 F pipewire-media- /dev/snd/controlC1: bob1074 F pipewire-media- /dev/snd/seq:bob1070 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Jan 7 03:19:48 2021 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful Symptom_Card: Built-in Audio - HDA ATI SB Symptom_Jack: SPDIF Out, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: None of the above Title: [MBB-895908, Realtek ALC892, SPDIF Out, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A99FX PRO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: 7354844-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/07/2014:br4.6:svnNOVATECHLTD:pnMBB-895908:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx:cvnNOVATECHLTD:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MBB-895908 dmi.product.sku: SKU dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- no audio on fresh install kubuntu groovy https://bugs.launchpad.net/bugs/1910480 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 1910405] Re: bluetoothd hangs and cannot be killed
A process that cannot be killed usually means it's blocked in a kernel call. So this sounds like a bug in the kernel Bluetooth code... Please: 1. Run this command to gather more system info: apport-collect 1910405 2. Try a newer Ubuntu release or just a newer kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D ** Tags added: bionic ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1910405 Title: bluetoothd hangs and cannot be killed Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hi, When having a bluetooth headphone (JBL Live) connected using the A2DP pulseaudio sink, the output sound suddenly stops during a music streaming of videocall session. Sometimes just disconnecting and reconnecting the headphone works, but some times reconnection is not possible anymore due to the hanging of bluetoothd. Bluetoothd still appears in the processes list, but cannot be killed, neither with "sudo service bluetooth stop" or "kill -9": $ ps afx | grep blue 9597 tty2 Sl+0:01 | \_ gnome-control-center bluetooth 5405 ?Ss 0:00 \_ /usr/lib/bluetooth/obexd 10694 pts/0S+ 0:00 \_ grep blue 20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd All programs keep working normally, only bluetooth is affected as well as the bluetooth settings page. The only solution is a hard reboot. A soft reboot doesn't even work: the systems keeps trying to end the bluetoothd process so one needs to press the power button for a few seconds to terminate the process. $ bluetoothd --version 5.48 $ uname -a Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been working nice for over one year now just like previous versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1910405/+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 1910435] Re: display texts are gone noting will show
Thanks for the bug report. Please attach a screenshot or photo of the problem. Also, do you find the problem only occurs after suspend/hibernate? ** Tags added: nvidia ** Summary changed: - display texts are gone noting will show + [nvidia] display texts are gone noting will show ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Also affects: nvidia-graphics-drivers-450 (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1910435 Title: [nvidia] display texts are gone noting will show Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-450 package in Ubuntu: Incomplete Bug description: no text showing even restart and shutdown button's text ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 02:17:02 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-42-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-58-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia, 450.80.02, 5.4.0-59-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:8627] InstallationDate: Installed on 2020-12-24 (12 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0d8c:0014 C-Media Electronics, Inc. Audio Adapter (Unitek Y-247A) Bus 001 Device 003: ID 1038:170a SteelSeries ApS SteelSeries Rival 100 Dell China Bus 001 Device 002: ID 0c45:672e Microdia USB DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=15221e3c-7bd7-41a8-b8bc-27f5c93ca2a5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3806 dmi.board.asset.tag: Default string dmi.board.name: H110M-F dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3806:bd05/09/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-F:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau:
[Desktop-packages] [Bug 1909776] Re: Left Mouse Button Sometimes Gets Stuck in Unity same as bug #1040844
>From what I read, both the affected apps you mention use Qt/QML and Python. So I wonder are any other types of apps affected? -- 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/1909776 Title: Left Mouse Button Sometimes Gets Stuck in Unity same as bug #1040844 Status in xorg-server package in Ubuntu: Incomplete Bug description: It seems like this is an old bug and I'm noticing only in the last few months. Sometimes, after I leave my PC on or after a standby, my left mouse button seems stuck in two appimage applications (freecad 0.18.4 and cura 4.8.0). I found no way to workaround this if not just after a reboot. Thanks in advance, Massimo ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-128.131-generic 4.15.18 Uname: Linux 4.15.0-128-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Dec 31 18:59:29 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5300 [17aa:3906] InstallationDate: Installed on 2015-12-12 (1846 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 80HE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-128-generic root=UUID=691bfdf1-ec74-4a27-bfe5-b660d9b9531f ro noprompt quiet splash pcie_aspm i915.lvds_downclock=1 i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 resume=UUID=9aa74165-44e7-42e8-8792-f50b6d875421 net.ifnames=0 biosdevname=0 i8042.reset vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A6CN58WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 3 Pro-1370 dmi.modalias: dmi:bvnLENOVO:bvrA6CN58WW:bd08/06/2015:svnLENOVO:pn80HE:pvrLenovoYOGA3Pro-1370:rvnLENOVO:rnVIUU4:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYOGA3Pro-1370: dmi.product.family: IDEAPAD dmi.product.name: 80HE dmi.product.version: Lenovo YOGA 3 Pro-1370 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Dec 31 12:49:57 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.8 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1909776/+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 1846837] Re: Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64
** Changed in: gst-libav1.0 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1846837 Title: Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64 Status in GStreamer: Unknown Status in gcc-10 package in Ubuntu: New Status in gcc-9 package in Ubuntu: New Status in gst-libav1.0 package in Ubuntu: Invalid Status in totem package in Ubuntu: New Bug description: Hello! I found that totem-video-thumbnailer is broken on aarch64. It fail with following error: (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.740: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.764: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.788: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block I tried to rollback all related packages I could think of (totem, gcc-9, ffmpeg) to previous releases, but for some reason this doesn't help. I remember video thumbnail generation on aarch64 worked fine few weeks ago. To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/1846837/+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 1910471] [NEW] [bcm2835_hdmi - bcm2835 HDMI 1, playback] No sound at all
Public bug reported: Running Ubuntu Mate 20.04 on Raspberry Pi 4 with Dual Monitor Set-up Description:Ubuntu 20.04.1 LTS Release:20.04 Packages involved: Unknown Issue: I can choose either 2 HDMI monitors or sound but not both Expected: Sound works with both monitors plugged in (1) No sound from headphone jack or HDMI in two monitor configuration (2) If I unplug 2nd monitor and reboot, sound works fine in HDMI or headphone jack (3) If I plug in second monitor while Pi is running, no picture in second monitor but sound still works (4) Sound works normally in Raspbian ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-1025.28-raspi 5.4.73 Uname: Linux 5.4.0-1025-raspi aarch64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: loreleiandmike 1211 F pulseaudio /dev/snd/pcmC2D0p: loreleiandmike 1211 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Jan 6 19:45:47 2021 ImageMediaBuild: 20200812 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:b1 failed Symptom_Card: Built-in Audio - bcm2835 Headphones Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: loreleiandmike 1211 F pulseaudio Symptom_Type: No sound at all Title: [bcm2835_hdmi - bcm2835 HDMI 1, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 focal uec-images -- 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/1910471 Title: [bcm2835_hdmi - bcm2835 HDMI 1, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Running Ubuntu Mate 20.04 on Raspberry Pi 4 with Dual Monitor Set-up Description: Ubuntu 20.04.1 LTS Release: 20.04 Packages involved: Unknown Issue: I can choose either 2 HDMI monitors or sound but not both Expected: Sound works with both monitors plugged in (1) No sound from headphone jack or HDMI in two monitor configuration (2) If I unplug 2nd monitor and reboot, sound works fine in HDMI or headphone jack (3) If I plug in second monitor while Pi is running, no picture in second monitor but sound still works (4) Sound works normally in Raspbian ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-1025.28-raspi 5.4.73 Uname: Linux 5.4.0-1025-raspi aarch64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: loreleiandmike 1211 F pulseaudio /dev/snd/pcmC2D0p: loreleiandmike 1211 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Jan 6 19:45:47 2021 ImageMediaBuild: 20200812 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:b1 failed Symptom_Card: Built-in Audio - bcm2835 Headphones Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: loreleiandmike 1211 F pulseaudio Symptom_Type: No sound at all Title: [bcm2835_hdmi - bcm2835 HDMI 1, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1910471/+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 1846837] Re: Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64
Answers from GStreamer bugtracker: > This very much looks like it's something much lower level than gstreamer-libav. Googling libgomp shows it's an openmp implementation used with gcc which means I imagine this issues is either some compiler or ffmpeg issue or some combination thereof. > Yeah, this is not a problem on our side. Please report this in Ubuntu against their toolchain. By the way, I guess Totem is currently broken on Ubuntu Desktop images for Raspberry Pi 4 too? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1846837 Title: Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64 Status in GStreamer: Unknown Status in gcc-10 package in Ubuntu: New Status in gcc-9 package in Ubuntu: New Status in gst-libav1.0 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: Hello! I found that totem-video-thumbnailer is broken on aarch64. It fail with following error: (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.740: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.764: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.788: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block I tried to rollback all related packages I could think of (totem, gcc-9, ffmpeg) to previous releases, but for some reason this doesn't help. I remember video thumbnail generation on aarch64 worked fine few weeks ago. To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/1846837/+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 1910464] [NEW] Error when clicking Restart & Update for OS updates
Public bug reported: I have pending OS updates, according to Software. However, when I hit Restart & Update, I get the following error message: Unable to install updates: GDBus.Error:org.gtk.GDBus.UnmappedGError:Quark._pk_2dengine_-2derror_2dquark.Code1: Prepared update not found: /var/lib/-PackageKit/prepared-update It then attempts to restart anyway. On reboot, the pending OS updates remain shown in Software. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-software 3.38.0-2build1 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 6 18:51:38 2021 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2020-02-14 (327 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak 3.38.0-2build1 gnome-software-plugin-snap3.38.0-2build1 ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: gnome-software UpgradeStatus: Upgraded to groovy on 2020-12-24 (13 days ago) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1910464 Title: Error when clicking Restart & Update for OS updates Status in gnome-software package in Ubuntu: New Bug description: I have pending OS updates, according to Software. However, when I hit Restart & Update, I get the following error message: Unable to install updates: GDBus.Error:org.gtk.GDBus.UnmappedGError:Quark._pk_2dengine_-2derror_2dquark.Code1: Prepared update not found: /var/lib/-PackageKit/prepared-update It then attempts to restart anyway. On reboot, the pending OS updates remain shown in Software. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-software 3.38.0-2build1 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 6 18:51:38 2021 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2020-02-14 (327 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak 3.38.0-2build1 gnome-software-plugin-snap3.38.0-2build1 ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: gnome-software UpgradeStatus: Upgraded to groovy on 2020-12-24 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1910464/+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 1909621] Re: my gnome control center is not opeaning and working
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1909621 Title: my gnome control center is not opeaning and working Status in gnome-control-center package in Ubuntu: New Bug description: i cannot access the control setting of ubantu 20 when i start this i cant open settings ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Dec 30 09:23:13 2020 InstallationDate: Installed on 2020-10-29 (61 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1909621/+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 1903632]
*** Bug 139452 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1903632 Title: Touchscreen can't be used to scroll anymore. Instead it will select everything on its way. Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: Ever since I upgrade to 20.10 from 20.04, I have been experiencing this issue. There are times when a user might want to scroll their screen by touching their screen. But I can't do this anymore. I want to know what went wrong? What can I do? Any info is appreciated. Note: Currently, I can scroll without in issue in Nautilus. But I can't do the same in Firefox, Tor browser, Libre Office, etc. Except Nautilus, all apps select words on screen whenever I touch my screen to scroll. But we all know, SCROLL ≠ SELECT. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 09:25:39 2020 DistUpgraded: 2020-10-28 23:47:17,717 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.14, 5.8.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:0641] InstallationDate: Installed on 2020-02-16 (267 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 5548 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i45x0v@/vmlinuz-5.8.0-26-generic root=ZFS=rpool/ROOT/ubuntu_i45x0v ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-10-28 (12 days ago) dmi.bios.date: 05/28/2019 dmi.bios.release: 5.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0FFJC4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/28/2019:br5.4:svnDellInc.:pnInspiron5548:pvrA10:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA10: dmi.product.name: Inspiron 5548 dmi.product.sku: 0641 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-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-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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/df-libreoffice/+bug/1903632/+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 1910435] Re: display texts are gone noting will show
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1910435 Title: display texts are gone noting will show Status in xorg package in Ubuntu: New Bug description: no text showing even restart and shutdown button's text ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 02:17:02 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-42-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-58-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia, 450.80.02, 5.4.0-59-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:8627] InstallationDate: Installed on 2020-12-24 (12 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0d8c:0014 C-Media Electronics, Inc. Audio Adapter (Unitek Y-247A) Bus 001 Device 003: ID 1038:170a SteelSeries ApS SteelSeries Rival 100 Dell China Bus 001 Device 002: ID 0c45:672e Microdia USB DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=15221e3c-7bd7-41a8-b8bc-27f5c93ca2a5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3806 dmi.board.asset.tag: Default string dmi.board.name: H110M-F dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3806:bd05/09/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-F:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1910435/+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 1905519] Re: Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from
A fix is available upstream Can someone make a patch? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1905519 Title: Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Status in Dash to dock: New Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: The syslog is full of these messages, continuously written all day long Nov 25 07:46:42 pc1 gnome-shell[2980]: Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 25 07:46:42 pc1 gnome-shell[2980]: == Stack trace for context 0x56541fffb220 == Nov 25 07:46:42 pc1 gnome-shell[2980]: #0 7ffddbfa1940 b /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:2051 (1839cb6a2420 @ 208) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 07:42:45 2020 InstallationDate: Installed on 2014-06-03 (2366 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1905519/+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 1910435] [NEW] display texts are gone noting will show
You have been subscribed to a public bug: no text showing even restart and shutdown button's text ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 02:17:02 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-42-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-58-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia, 450.80.02, 5.4.0-59-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:8627] InstallationDate: Installed on 2020-12-24 (12 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0d8c:0014 C-Media Electronics, Inc. Audio Adapter (Unitek Y-247A) Bus 001 Device 003: ID 1038:170a SteelSeries ApS SteelSeries Rival 100 Dell China Bus 001 Device 002: ID 0c45:672e Microdia USB DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=15221e3c-7bd7-41a8-b8bc-27f5c93ca2a5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3806 dmi.board.asset.tag: Default string dmi.board.name: H110M-F dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3806:bd05/09/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-F:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- display texts are gone noting will show https://bugs.launchpad.net/bugs/1910435 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872268] Re: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders (when ubuntu-dock is loaded)
Now it works, thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1872268 Title: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders (when ubuntu-dock is loaded) Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock source package in Focal: Incomplete Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Bug: Gnome shell while opening app drawer, clicking on an app folder and clicking on the blank area freezes gnome shell and it makes the session completely unusable and non recoverable. How to reproduce: 1- Click 9 dots on bottom corner of dash (the app launcher button), wait for the app grid to show up. 2- Click on an app folder to open it. 3- Click on the blank area outside of the opened folder dialog. 4- Gnome shell gets freezes and never come back from this state, on both wayland session and x11 session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 12:00:13 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1872268/+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 1905623] Re: df: /run/user/1000/doc: Operation not permitted
Has gnulib upstream been notified about the fix for this bug? ... or about the original treat-devtmpfs-and-squashfs-as-dummy- filesystems.patch that the fix was applied to? https://launchpadlibrarian.net/510003931/coreutils_8.32-4ubuntu1_8.32-4ubuntu2.diff.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1905623 Title: df: /run/user/1000/doc: Operation not permitted Status in coreutils package in Ubuntu: Fix Released Status in xdg-desktop-portal package in Ubuntu: Triaged Bug description: /run/user/1000/doc is a fuse.portal mount point, but statfs() return EPERM, hence df produces an error message. Maybe statfs() is not implemented, but it would be good to quieten this down (df even does not allow me to ignore it, probably because it looks at statfs to find out fs type, so my fs type ignoring doesn't work). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1905623/+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 1905519] Re: Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from
I can confirm #4, triggered by updates. Can be stopped by restarting Gnome Shell. ALT+F2 r ENTER Thank you -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1905519 Title: Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Status in Dash to dock: New Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: The syslog is full of these messages, continuously written all day long Nov 25 07:46:42 pc1 gnome-shell[2980]: Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 25 07:46:42 pc1 gnome-shell[2980]: == Stack trace for context 0x56541fffb220 == Nov 25 07:46:42 pc1 gnome-shell[2980]: #0 7ffddbfa1940 b /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:2051 (1839cb6a2420 @ 208) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 07:42:45 2020 InstallationDate: Installed on 2014-06-03 (2366 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1905519/+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 1907904] Re: gnome-shell 20.10 crashes with Wayland
I have updated GNOME to 3.38.2 today, by enabling "proposed packages" like explained in bug 1898910. I will see if that solves the issue. Thanks. -- 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/1907904 Title: gnome-shell 20.10 crashes with Wayland Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu Gnome 20.10 (upgraded from 20.04), 64 bits,Wayland session AMD CPU Fx GPU Radeon Very frequently, Gnome-shell crashes and difficult to understand why or when. Example : open a Libreoffice Calc file ; export it twice in PDF format on the Desktop. Right-click on this files icons on the desktop to delete them : for the 2nd, the screen becomes black (I can do nothing) and after about 20 s, I get the login screen. I exported the journal file (attached file) (and the session crashes again) because the system says nothing ! Doesn't happen with X session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1907904/+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 1902219] Re: Online Accounts Credentials Not Working
Any fix??? -- 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/1902219 Title: Online Accounts Credentials Not Working Status in gnome-control-center package in Ubuntu: New Bug description: I just booted up ubuntu 20.04 (Groovy Gorilla) and I couldn't use my google drive account in files. It was telling me that the credentials are wrong but I relogined then also no result same credentials expired. The Microsoft account was also showing wrong credentials. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Oct 30 16:47:53 2020 InstallationDate: Installed on 2020-10-27 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1902219/+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 1910421] [NEW] Evince crashes on an unreadable nonempty postscript file owned by root
Public bug reported: Package: evince Version: 3.38.0-1 I run an up-to-date groovy 20.10. This is how to reproduce the segfault: root@host:/tmp# rm mwe.ps root@host:/tmp# echo "test" > mwe.ps root@host:/tmp# chmod g-rwx,o-rwx mwe.ps root@host:/tmp# exit logout user@host:/tmp$ evince mwe.ps Segmentation fault (core dumped) An expected outcome would be a meaningful error message instead of a crash. Thanks in advance for repairing this bug. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- 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/1910421 Title: Evince crashes on an unreadable nonempty postscript file owned by root Status in evince package in Ubuntu: New Bug description: Package: evince Version: 3.38.0-1 I run an up-to-date groovy 20.10. This is how to reproduce the segfault: root@host:/tmp# rm mwe.ps root@host:/tmp# echo "test" > mwe.ps root@host:/tmp# chmod g-rwx,o-rwx mwe.ps root@host:/tmp# exit logout user@host:/tmp$ evince mwe.ps Segmentation fault (core dumped) An expected outcome would be a meaningful error message instead of a crash. Thanks in advance for repairing this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1910421/+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 1909776] Re: Left Mouse Button Sometimes Gets Stuck in Unity same as bug #1040844
Happy new year and thanks for the reply, the issue occours with both, touchpad and mouse, even xhanging mouse port, the issue remains.I'll try to update, but not now, I'll have to check that all drivers working for my lenovo yoga 3 pro first. It wasn't that easy to have all devices running. Now, working from home I need the PC running. A faster workaround was perfect, but I'll see with the update. Thanks, Massimo -- 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/1909776 Title: Left Mouse Button Sometimes Gets Stuck in Unity same as bug #1040844 Status in xorg-server package in Ubuntu: Incomplete Bug description: It seems like this is an old bug and I'm noticing only in the last few months. Sometimes, after I leave my PC on or after a standby, my left mouse button seems stuck in two appimage applications (freecad 0.18.4 and cura 4.8.0). I found no way to workaround this if not just after a reboot. Thanks in advance, Massimo ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-128.131-generic 4.15.18 Uname: Linux 4.15.0-128-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Dec 31 18:59:29 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5300 [17aa:3906] InstallationDate: Installed on 2015-12-12 (1846 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 80HE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-128-generic root=UUID=691bfdf1-ec74-4a27-bfe5-b660d9b9531f ro noprompt quiet splash pcie_aspm i915.lvds_downclock=1 i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 resume=UUID=9aa74165-44e7-42e8-8792-f50b6d875421 net.ifnames=0 biosdevname=0 i8042.reset vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A6CN58WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 3 Pro-1370 dmi.modalias: dmi:bvnLENOVO:bvrA6CN58WW:bd08/06/2015:svnLENOVO:pn80HE:pvrLenovoYOGA3Pro-1370:rvnLENOVO:rnVIUU4:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYOGA3Pro-1370: dmi.product.family: IDEAPAD dmi.product.name: 80HE dmi.product.version: Lenovo YOGA 3 Pro-1370 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Dec 31 12:49:57 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.8 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1909776/+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 1891407] Re: [journalctl --follow] Wi-Fi auto disconnect randomly, unable to fix (updated: including PCIe Bus Error)
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
--
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/1891407
Title:
[journalctl --follow] Wi-Fi auto disconnect randomly, unable to fix
(updated: including PCIe Bus Error)
Status in network-manager package in Ubuntu:
Invalid
Bug description:
Ubuntu 20.04.01 LTS (newly installed)
(Moved that device from windows 10, didnt had issue in it)
HP 15T-au000 device.
[lspci]Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE
PCIe Wireless Network Adapter
[lspci | awk '/[Nn]et/ {print $1}' | xargs -i% lspci -ks %]
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI
Express Fast Ethernet controller (rev 0a)
DeviceName: Realtek PCIe FE Family Controller
Subsystem: Hewlett-Packard Company RTL810xE PCI Express Fast Ethernet
controller
Kernel driver in use: r8169
Kernel modules: r8169
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe
Wireless Network Adapter
DeviceName: Realtek Sanji2 RTL8723BE b/g/n 1x1 + BT 4 LE PCIe+USB M.2
Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network Adapter
Kernel driver in use: rtl8723be
Kernel modules: rtl8723be
Wi-Fi key is correct (i can use internet to visit sites, watch videos in
youtube etc) however randomly disconnect and appear window to re-connect
(sometimes constantly disconnect)
No network related change has made (IPv6 disabled through settings)
Only one SSID is in use: Dialog 4G
I ran `journalctl --follow` and below is the log. let me know if
required to provide further details
~Updated~
There also `PCIe Bus Error: severity=Corrected, type=Physical Layer` occur
due that wifi card - RTL8723BE
It usually appear when boot the device (before login screen) and currently i
suppressed that issue by adding `pci=noaer` to grub (alternative pci=nomsi)
I found https://github.com/rtlwifi-linux/rtlwifi_new and
https://github.com/silenoth/rtlwifi_new-extended it contain
'RTL8723BE' however most people had used them due wifi card does not
display or unable connect but i dont have such issue and users have
reported installation issues then didnt consider to put to my machine.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891407/+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 1910405] [NEW] bluetoothd hangs and cannot be killed
Public bug reported: Hi, When having a bluetooth headphone (JBL Live) connected using the A2DP pulseaudio sink, the output sound suddenly stops during a music streaming of videocall session. Sometimes just disconnecting and reconnecting the headphone works, but some times reconnection is not possible anymore due to the hanging of bluetoothd. Bluetoothd still appears in the processes list, but cannot be killed, neither with "sudo service bluetooth stop" or "kill -9": $ ps afx | grep blue 9597 tty2 Sl+0:01 | \_ gnome-control-center bluetooth 5405 ?Ss 0:00 \_ /usr/lib/bluetooth/obexd 10694 pts/0S+ 0:00 \_ grep blue 20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd All programs keep working normally, only bluetooth is affected as well as the bluetooth settings page. The only solution is a hard reboot. A soft reboot doesn't even work: the systems keeps trying to end the bluetoothd process so one needs to press the power button for a few seconds to terminate the process. $ bluetoothd --version 5.48 $ uname -a Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been working nice for over one year now just like previous versions. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1910405 Title: bluetoothd hangs and cannot be killed Status in bluez package in Ubuntu: New Bug description: Hi, When having a bluetooth headphone (JBL Live) connected using the A2DP pulseaudio sink, the output sound suddenly stops during a music streaming of videocall session. Sometimes just disconnecting and reconnecting the headphone works, but some times reconnection is not possible anymore due to the hanging of bluetoothd. Bluetoothd still appears in the processes list, but cannot be killed, neither with "sudo service bluetooth stop" or "kill -9": $ ps afx | grep blue 9597 tty2 Sl+0:01 | \_ gnome-control-center bluetooth 5405 ?Ss 0:00 \_ /usr/lib/bluetooth/obexd 10694 pts/0S+ 0:00 \_ grep blue 20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd All programs keep working normally, only bluetooth is affected as well as the bluetooth settings page. The only solution is a hard reboot. A soft reboot doesn't even work: the systems keeps trying to end the bluetoothd process so one needs to press the power button for a few seconds to terminate the process. $ bluetoothd --version 5.48 $ uname -a Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been working nice for over one year now just like previous versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1910405/+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 1632027] Re: New Document feature missing from Nautilus 3.20+
Adding templates file to ~/Templates works for Nautilus 1:3.36.3-0ubuntu1 (Ubuntu 20.04), but the right context menu is not available if one has no more empty space left in the window to right click (say when you display a directory with 50+ files in it). My comment suggest probably another bug report, but I could not find one searching the web regarding this issue. If you know of such bug report, please provide the link. I am reporting this problem here since it is related and causes a discovery problem too if it is impossible to access the right click dialog box. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1632027 Title: New Document feature missing from Nautilus 3.20+ Status in Nautilus: Invalid Status in nautilus package in Ubuntu: Confirmed Bug description: Ubuntu has a patch ( 16_unity_new_documents.patch ) to enable a 'New Document' function in the right-click context menu. This patch was not ported to Nautilus 3.20 so this Ubuntu-specific feature is missing in Ubuntu 16.10. https://bazaar.launchpad.net/~ubuntu- desktop/nautilus/ubuntu/view/head:/debian/patches/16_unity_new_documents.patch While this patch being disabled is noted in the debian/changelog, here's a formal bug to document the issue and maybe give it a bit more visibility so that it will be fixed. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 10 12:54:50 2016 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.preferences' b'open-folder-on-dnd-hover' b'false' b'org.gnome.nautilus.window-state' b'sidebar-width' b'171' b'org.gnome.nautilus.window-state' b'geometry' b"'1106x542+436+438'" b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2016-08-11 (59 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1632027/+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 1733322] Re: Unable to enable file or screen sharing with unmanaged network connection
I have been experiencing the same. Is there any workaround meanwhile? Just to mention, I am using Debian 10. -- 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/1733322 Title: Unable to enable file or screen sharing with unmanaged network connection Status in gnome-control-center: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Bug description: I have installed Ubuntu Server 17.10. At request from a colleague I then tried to install ubuntu-desktop and enable screen sharing. However, this did not work as expected. When trying to enable screen sharing (same goes for file sharing), the enable button just jumps straight back to disabled when toggling it. I assumed this had something to do with the fact that the "networks" list at the bottom of the sharing dialog was empty. This appears in the syslog when trying to toggle: Nov 20 11:31:06 bcubuntu3 gnome-control-c[1054]: Failed to enable service vino-server: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Sharing cannot be enabled on this network, status is '0' This computer has only a single wired network connection (no wifi). This connection shows in the system menu as "Wired unmanaged" which seems to be the reason that it doesn't show up in the sharing dialogs. As a workaround, I tried the following things: 1. Change "managed=false" to "managed=true" in /etc/NetworkManager/NetworkManager.conf as suggested in https://askubuntu.com/a/2905 2. Touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf as suggested in https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547 3. Change renderer to NetworkManager in /etc/netplan/01-netcfg.yaml 1 and 2 was not enough to get NetworkManager to manage the wired interface, but 3, possibly together with one or both of the previous steps did the trick. When I finally got NetworkManager to manage the wired connection, it did show up in the sharing dialogs, and I was able to enable screen sharing. However, it would seem reasonable to be able to enable sharing even on unmanaged interfaces by some mechanism, especially since unmanaged interfaces seem to be the norm these days. ~$ lsb_release -rd Description:Ubuntu 17.10 Release:17.10 gnome-control-center: Installed: 1:3.26.1-0ubuntu5 Candidate: 1:3.26.1-0ubuntu5 Version table: *** 1:3.26.1-0ubuntu5 500 500 http://se.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.26.1-0ubuntu4 500 500 http://se.archive.ubuntu.com/ubuntu artful/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1733322/+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 1910391] [NEW] Lightdm is not working on minimal DE install without recommends
Public bug reported: I tried to install Focal with minimal DE without install recommends and installing lightdm. On debian works "out of the box" on ubuntu not, lightdm fails to start. I saw that issue is because missing a greeter, on debian is correctly as dependencies, on ubuntu packages is instead as recommends, moving from recommends to dependens will solve this. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- 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/1910391 Title: Lightdm is not working on minimal DE install without recommends Status in lightdm package in Ubuntu: New Bug description: I tried to install Focal with minimal DE without install recommends and installing lightdm. On debian works "out of the box" on ubuntu not, lightdm fails to start. I saw that issue is because missing a greeter, on debian is correctly as dependencies, on ubuntu packages is instead as recommends, moving from recommends to dependens will solve this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1910391/+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 1910387] [NEW] Firefox don't respect sound settings.
Public bug reported: Firefox don't respect sound settings. Keeps using internal output device (default) instead of selected one (HDMI). Other applications respects that and works fine (chrome, vlc ...) only firefox have this problem. This problem appears after upgrade to 20.04 I tried to change graphic card and also drivers but the problem persists. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 84.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BuildID: 20201221152838 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Jan 6 12:06:52 2021 ExecutablePath: /usr/lib/firefox/firefox Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-08-06 (1614 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-5a576006-0903-42d0-95cb-b051d1180511 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=84.0.1/20201221152838 (In use) RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-5a576006-0903-42d0-95cb-b051d1180511 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2020-08-27 (132 days ago) dmi.bios.date: 10/31/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FB dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-DS3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFB:bd10/31/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-DS3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. ** Affects: firefox (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 firefox in Ubuntu. https://bugs.launchpad.net/bugs/1910387 Title: Firefox don't respect sound settings. Status in firefox package in Ubuntu: New Bug description: Firefox don't respect sound settings. Keeps using internal output device (default) instead of selected one (HDMI). Other applications respects that and works fine (chrome, vlc ...) only firefox have this problem. This problem appears after upgrade to 20.04 I tried to change graphic card and also drivers but the problem persists. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 84.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BuildID: 20201221152838 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Jan 6 12:06:52 2021 ExecutablePath: /usr/lib/firefox/firefox Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-08-06 (1614 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-5a576006-0903-42d0-95cb-b051d1180511 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=84.0.1/20201221152838 (In use) RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-5a576006-0903-42d0-95cb-b051d1180511 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2020-08-27 (132 days ago) dmi.bios.date: 10/31/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FB
[Desktop-packages] [Bug 1170353] Re: Host names intermittently resolve to 0.0.0.0
It's happened to me a few times on 20.04.1: $ host support.coinjar.com support.coinjar.com has address 0.0.0.0 support.coinjar.com has IPv6 address :: support.coinjar.com is an alias for coinjar.zendesk.com. coinjar.zendesk.com mail is handled by 10 mail-pod-25.int.zendesk.com. $ sudo resolvectl flush-caches $ host support.coinjar.com support.coinjar.com has address 0.0.0.0 support.coinjar.com has IPv6 address :: support.coinjar.com is an alias for coinjar.zendesk.com. coinjar.zendesk.com mail is handled by 10 mail-pod-25.int.zendesk.com. $ dig support.coinjar.com ; <<>> DiG 9.16.1-Ubuntu <<>> support.coinjar.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12759 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;support.coinjar.com. IN A ;; ANSWER SECTION: support.coinjar.com.34 IN A 0.0.0.0 ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Jan 06 20:23:28 AEDT 2021 ;; MSG SIZE rcvd: 64 Then 2 minutes later the problem resolves itself: $ dig support.coinjar.com ; <<>> DiG 9.16.1-Ubuntu <<>> support.coinjar.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64605 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;support.coinjar.com. IN A ;; ANSWER SECTION: support.coinjar.com.151 IN CNAME coinjar.zendesk.com. coinjar.zendesk.com.900 IN A 104.16.51.111 coinjar.zendesk.com.900 IN A 104.16.53.111 ;; Query time: 68 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Jan 06 20:25:31 AEDT 2021 ;; MSG SIZE rcvd: 110 Nothing in /var/log/syslog or systemd-resolved's systemd log. -- 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/1170353 Title: Host names intermittently resolve to 0.0.0.0 Status in network-manager package in Ubuntu: Invalid Bug description: About 5% of DNS queries resolve to 0.0.0.0. A couple of times an hour during normal browsing, Firefox resolves a domain to 0.0.0.0. Opening the same site in Chrome has a 50% chance of it working, then it normally works after a few reloads. Thunderbird has also occasionally resolved googlemail.com to 0.0.0.0. Domains include google.com, wikipedia.org, harvestapp.com and many more. I couldn't reproduce this with dig/nslookup for a while, but after 5 minutes of (re)trying random domains) did: $ dig mail.google.com ; <<>> DiG 9.8.1-P1 <<>> mail.google.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22905 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;mail.google.com. IN A ;; ANSWER SECTION: mail.google.com. 60 IN A 0.0.0.0 ;; Query time: 0 msec ;; SERVER: 127.0.1.1#53(127.0.1.1) ;; WHEN: Thu Apr 18 13:57:04 2013 ;; MSG SIZE rcvd: 49 Note the "0 msec", so I'm pretty sure this is dnsmasq's local cache. Using Xubuntu 12.10, NetworkManager 0.9.6.0, Dnsmasq 2.63rc6. NetworkManager has DNS servers set to "8.8.8.8, 8.8.4.4" (also tried setting it to my router's DNS server, with no effect). /etc/resolve.conf just has "nameserver 127.0.1.1" dnsmasq is currently running: /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind- interfaces --pid-file=/var/run/sendsigs.omit.d/network- manager.dnsmasq.pid --listen-address=127.0.1.1 --conf-file=/var/run /nm-dns-dnsmasq.conf --cache-size=0 --proxy-dnssec --enable- dbus=org.freedesktop.NetworkManager.dnsmasq --conf- dir=/etc/NetworkManager/dnsmasq.d ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Apr 18 14:27:33 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-01-11 (97 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) IpRoute: default via 10.0.0.1 dev eth0 proto static 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.10 metric 1 169.254.0.0/16 dev eth0 scope link
[Desktop-packages] [Bug 1910235] Re: The mouse stops working after taking a screenshot
Please try uninstalling/disabling these extensions: 'dash-to-pa...@jderose9.github.com', 'workspace-switch- wraparo...@theychx.org' Removing extensions is the first thing we need to try because so many bugs are caused by extensions. -- 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/1910235 Title: The mouse stops working after taking a screenshot Status in gnome-shell package in Ubuntu: Incomplete Bug description: Steps to reproduce this bug: 1. Open Chromium browser. 2. Go to the page with the form in which there is a standard browser drop-down menu (form select) 3. Open it 4. Try to take a screenshot with the keyboard shortcut: Ctrl+Shift+PrintScreen 5. Try to switch between applications using the panel and check the operation of the mouse in other applications besides browser (in my case Slack) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-26 (71 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910235/+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 1905467] Re: [USB-Audio - Logitech Wireless Headset, playback] volume slider - sound audible only from 50% to 100% of the slider position
I see the same behavior. -- 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/1905467 Title: [USB-Audio - Logitech Wireless Headset, playback] volume slider - sound audible only from 50% to 100% of the slider position Status in alsa-driver package in Ubuntu: New Bug description: After establishing connection with Logitech H800 Wireless Headset via USB Dongle, the system sound has to be set at the minimum of 50% of the slider for the sound in the headphones to be audible. Below the 50% volume slider position the sound is completely muted. Expected behaviour: Volume slider properly changing the sound level from 0% to 100% with the sound being muted at 0% and at maximum level at 100%. System: Ubuntu 20.04.1 LTS alsa-driver: k5.4.0-54-generic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: maciej 6716 F pulseaudio /dev/snd/pcmC3D0p: maciej 6716 F...m pulseaudio /dev/snd/controlC0: maciej 6716 F pulseaudio /dev/snd/controlC1: maciej 6716 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 24 21:29:56 2020 InstallationDate: Installed on 2020-06-22 (154 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: H600 [Wireless Headset] - Logitech Wireless Headset Symptom_PulseAudioLog: lis 22 12:33:32 y510p-ubuntu dbus-daemon[1500]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.31' (uid=125 pid=1940 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") lis 22 12:33:34 y510p-ubuntu pulseaudio[1940]: Failed to find a working profile. lis 22 12:33:34 y510p-ubuntu pulseaudio[1940]: Failed to load module "module-alsa-card" (argument: "device_id="2" name="pci-_01_00.1" card_name="alsa_card.pci-_01_00.1" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. lis 24 09:41:02 y510p-ubuntu pulseaudio[1940]: Failed to create sink input: sink is suspended. lis 24 10:30:54 y510p-ubuntu pulseaudio[1940]: Failed to create sink input: sink is suspended. Symptom_Type: Volume slider, or mixer problems Title: [USB-Audio - Logitech Wireless Headset, playback] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 1/30/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN47WW(V3.08) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 3193STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN47WW(V3.08):bd1/30/2015:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr3193STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1905467/+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 1910235] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1910235/+attachment/5449648/+files/ShellJournal.txt -- 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/1910235 Title: The mouse stops working after taking a screenshot Status in gnome-shell package in Ubuntu: Incomplete Bug description: Steps to reproduce this bug: 1. Open Chromium browser. 2. Go to the page with the form in which there is a standard browser drop-down menu (form select) 3. Open it 4. Try to take a screenshot with the keyboard shortcut: Ctrl+Shift+PrintScreen 5. Try to switch between applications using the panel and check the operation of the mouse in other applications besides browser (in my case Slack) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-26 (71 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910235/+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 1910235] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1910235/+attachment/5449647/+files/ProcEnviron.txt -- 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/1910235 Title: The mouse stops working after taking a screenshot Status in gnome-shell package in Ubuntu: Incomplete Bug description: Steps to reproduce this bug: 1. Open Chromium browser. 2. Go to the page with the form in which there is a standard browser drop-down menu (form select) 3. Open it 4. Try to take a screenshot with the keyboard shortcut: Ctrl+Shift+PrintScreen 5. Try to switch between applications using the panel and check the operation of the mouse in other applications besides browser (in my case Slack) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-26 (71 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910235/+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 1910235] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1910235/+attachment/5449645/+files/GsettingsChanges.txt -- 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/1910235 Title: The mouse stops working after taking a screenshot Status in gnome-shell package in Ubuntu: Incomplete Bug description: Steps to reproduce this bug: 1. Open Chromium browser. 2. Go to the page with the form in which there is a standard browser drop-down menu (form select) 3. Open it 4. Try to take a screenshot with the keyboard shortcut: Ctrl+Shift+PrintScreen 5. Try to switch between applications using the panel and check the operation of the mouse in other applications besides browser (in my case Slack) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-26 (71 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910235/+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 1910235] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1910235/+attachment/5449649/+files/monitors.xml.txt -- 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/1910235 Title: The mouse stops working after taking a screenshot Status in gnome-shell package in Ubuntu: Incomplete Bug description: Steps to reproduce this bug: 1. Open Chromium browser. 2. Go to the page with the form in which there is a standard browser drop-down menu (form select) 3. Open it 4. Try to take a screenshot with the keyboard shortcut: Ctrl+Shift+PrintScreen 5. Try to switch between applications using the panel and check the operation of the mouse in other applications besides browser (in my case Slack) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-26 (71 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910235/+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 1910235] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1910235/+attachment/5449646/+files/ProcCpuinfoMinimal.txt -- 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/1910235 Title: The mouse stops working after taking a screenshot Status in gnome-shell package in Ubuntu: Incomplete Bug description: Steps to reproduce this bug: 1. Open Chromium browser. 2. Go to the page with the form in which there is a standard browser drop-down menu (form select) 3. Open it 4. Try to take a screenshot with the keyboard shortcut: Ctrl+Shift+PrintScreen 5. Try to switch between applications using the panel and check the operation of the mouse in other applications besides browser (in my case Slack) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-26 (71 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910235/+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 1910235] Re: The mouse stops working after taking a screenshot
apport information ** Tags added: apport-collected focal ** Description changed: Steps to reproduce this bug: 1. Open Chromium browser. 2. Go to the page with the form in which there is a standard browser drop-down menu (form select) 3. Open it 4. Try to take a screenshot with the keyboard shortcut: Ctrl+Shift+PrintScreen 5. Try to switch between applications using the panel and check the operation of the mouse in other applications besides browser (in my case Slack) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.14 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-10-26 (71 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + NonfreeKernelModules: nvidia_modeset nvidia + Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 + RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 + Tags: focal + Uname: Linux 5.4.0-58-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1910235/+attachment/5449644/+files/Dependencies.txt -- 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/1910235 Title: The mouse stops working after taking a screenshot Status in gnome-shell package in Ubuntu: Incomplete Bug description: Steps to reproduce this bug: 1. Open Chromium browser. 2. Go to the page with the form in which there is a standard browser drop-down menu (form select) 3. Open it 4. Try to take a screenshot with the keyboard shortcut: Ctrl+Shift+PrintScreen 5. Try to switch between applications using the panel and check the operation of the mouse in other applications besides browser (in my case Slack) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-26 (71 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910235/+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
