[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@61, yes. I had tried it and it works. It also has mSBC support - https://github.com/Arkq/bluez-alsa/issues/29, but the author himself admits that mSBC support is buggy and is not being developed. I could get it to work, but the audio was very choppy. -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@63 - your headset likely doesn't support mSBC (16 KHz), only CVSD (8KHz) in HFP/HSP mode. If that is the case, any fix - using a USB soundcard as you did, or a software fix (which this page is tracking) isn't gonna help. If it does support mSBC, 1Mii B10, and Avantree Leaf, Creative BT-W3 should be able to give decent quality audio. The definition of 'decent' varies of course. Most people in this age and time wouldn't be happy with 8 KHz (else, this page wouldn't exist), but mSBC is decent enough for most people, at least for typical voice calls. You can check the sampling frequency used very easily using Audacity > Record a few seconds using the mic in question > Analyze > Plot Spectrum. Note that Audacity plots in log scale for freq by default. If the highest freq component is just below 4 KHz, it is using CVSD @ 8 KHz sampling, and your headset is the likely culprit. If the highest component is 8 KHz, it is using mSBC @ 16 KHz. If you think that is not good enough, your options are limited. You can use FastStream (FS) which is supported only by a limited number of headsets, as well as by dongles such as Leaf, 1Mii B10, Creative BT-W2. No OS afaik supports it, so you can't use the dongle. Many devices have buggy implementations of FS. AptX LL also supposedly has bidirectional audio support, but the voiceback part is not supported by any device that I know of. ** Bug watch added: github.com/Arkq/bluez-alsa/issues #29 https://github.com/Arkq/bluez-alsa/issues/29 -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
Ryan, bugs should ideally be reported by someone who actually experiences them. So after 33.1-0ubuntu0.20.04.1 reaches the Fix Released state, please then open a new bug by running: ubuntu-bug gnome-shell-extension-appindicator -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" Status in Ubuntu AppIndicators: Unknown Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Committed Bug description: [ Impact ] Using discord application, causes the shell to slowdown and trigger lots of "unable to lookup icon ..." errors [ Test case ] Install discord app: - snap install discord Run it, starting a call seems to trigger it more [ Regression potential ] Icons may not be loaded properly, there may be delays between a good icon and an invalid one (and vice-versa). --- Updated bug #1817073 about this, but it's not really the same since this does not crash the shell fully. When speaking in discord there is supposed to be an icon change on the appindicator and logs spam me with [AppIndicatorSupport-FATAL] unable to lookup icon for discord1_40. The whole desktop freezes for a moment when talking in discord if the appindicator package is installed. Easily reproduced by joining a voice channel in discord and just doing stuff in the gnome ui, watching a video or whatever while talking. This is pretty bad since it leaves no choice but to uninstall gnome- shell-extension-appindicator and loosing that functionality if people wants to use discord on ubuntu. This is also reported on the extensions github page: https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/171 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/157 Someone also made a video on youtube showing the problem: https://www.youtube.com/watch?v=ABavT7yXlso To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/1849142/+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 1895301] Re: XrandR does not propose 3440x1440 21:9 resolution
** Changed in: xorg-server (Ubuntu) Status: Expired => Incomplete -- 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/1895301 Title: XrandR does not propose 3440x1440 21:9 resolution Status in xorg-server package in Ubuntu: Incomplete Bug description: XrandR does not propose 3440x1440 21:9 resolution on Ubuntu 20.04 : How to reproduce : - Connect on HDMI 1.4 Intel HD 630 mobile a UWUHD 3440x1440 monitor - Only 16:9 are proposed by xrandR - XrandR should propose all supported resolutions WorkAround : manually add the mode xrandr --newmode "3440x1440_30.00" 196.90 3440 3600 3960 4480 1440 1441 1444 1465 -HSync +Vsync xrandr --addmode HDMI-2 3440x1440_30.00 xrandr --output HDMI-2 --mode 3440x1440_30.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1895301/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@ gyhor, I am pretty sure you got a faulty 1Mii B10. It doesnt get past enumeration, so it is not a compatibility issue. You also mention that it was tried on different systems and didn't work. Time to get it replaced. -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1662244] Re: lightdm causes all greeters to fail to start
Thanks Adding * soft memlock 262144 * hard memlock 262144 in /etc/security/limits.conf solved the same problem with lightdm and X not starting on Ubuntu 18.04 running on a motherboard with VIA KM400 integrated graphics. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1662244 Title: lightdm causes all greeters to fail to start Status in Light Display Manager: Invalid Status in LightDM GTK+ Greeter: Invalid Status in lightdm package in Ubuntu: Invalid Status in unity-greeter package in Ubuntu: Invalid Bug description: lightdm is failing to start. Best guess is because of unity-session- manager. This is from .xsession-errors. dbus-update-activation-environment: setting _=/usr/bin/dbus-update-activation-environment upstart: click-user-hooks main process (4028) terminated with status 1 upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon respawning too fast, stopped upstart: indicator-application main process ended, respawning upstart: indicator-application main process ended, respawning upstart: indicator-application respawning too fast, stopped xbrlapi: window 0x03a00084 changed to NULL name xbrlapi: window 0x03a00084 changed to NULL name xbrlapi: window 0x03c00084 changed to NULL name xbrlapi: window 0x03c00084 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name upstart: dbus main process (4023) killed by TERM signal I've tried to move aside $HOME/.config/dconf/user and that didn't work. I've reverted kernel versions and that didn't work. I've moved aside $HOME/.cache and that didn't work. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.5-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Mon Feb 6 10:21:29 2017 InstallationDate: Installed on 2015-07-20 (566 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: lightdm UpgradeStatus: Upgraded to yakkety on 2016-12-14 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1662244/+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 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
** No longer affects: gnome-shell-extension-appindicator ** Also affects: gnome-shell-extension-appindicator via https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/236 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" Status in Ubuntu AppIndicators: Unknown Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Committed Bug description: [ Impact ] Using discord application, causes the shell to slowdown and trigger lots of "unable to lookup icon ..." errors [ Test case ] Install discord app: - snap install discord Run it, starting a call seems to trigger it more [ Regression potential ] Icons may not be loaded properly, there may be delays between a good icon and an invalid one (and vice-versa). --- Updated bug #1817073 about this, but it's not really the same since this does not crash the shell fully. When speaking in discord there is supposed to be an icon change on the appindicator and logs spam me with [AppIndicatorSupport-FATAL] unable to lookup icon for discord1_40. The whole desktop freezes for a moment when talking in discord if the appindicator package is installed. Easily reproduced by joining a voice channel in discord and just doing stuff in the gnome ui, watching a video or whatever while talking. This is pretty bad since it leaves no choice but to uninstall gnome- shell-extension-appindicator and loosing that functionality if people wants to use discord on ubuntu. This is also reported on the extensions github page: https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/171 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/157 Someone also made a video on youtube showing the problem: https://www.youtube.com/watch?v=ABavT7yXlso To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/1849142/+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 1884396] Re: Ubuntu freezing intermittently when the mega.nz appindicator is loaded
** No longer affects: gnome-shell-extension-appindicator ** Also affects: gnome-shell-extension-appindicator via https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/226 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1884396 Title: Ubuntu freezing intermittently when the mega.nz appindicator is loaded Status in Ubuntu AppIndicators: Unknown Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Committed Bug description: [ Impact ] Indicators using (big) pixmap icons cause the shell to use a lot of CPU computation, which interfere with user experience [ Test case ] - Install mega client from https://mega.nz/sync - Run it in ubuntu and ensure it doesn't block the UI while syncing (but even opening/closing the app should be enough to trigger Alternatively use this test tool: https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js Launch it with `gjs` and select the 'Crazy icons updates' menu item: - The shell should not hang [ Regression potential ] Icon updates may be late or not apply immediately (or at all). In general there has been a refactor of the iconCache, so internally it may happen that we load an icon more times, or that there could be an increase in RAM usage as per missing garbage collecting of it. I had similar issues when 20.04 was released, then it disappeared with an upgrade - but sadly it's back. I have short intermittent freezings of the OS. About every 15-30 seconds Ubunut freezes for a second or two. Eg when writing this description, the OS freezes every second word. When the freeze goes away the OS is snappy. I have tried switching between Wayland and Xorg - but the problem persists. If I write something when it freezes up the last character will be replicated many times - like what happened jut now. This problem did not show up in ubuntu 18.04 through 19.10. Hope U can fix this soon - using my laptop in unbearable. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 23:54:52 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: evdi, 1.7.0, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 [19e5:3e04] InstallationDate: Installed on 2020-05-12 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd (Foxlink) HD Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HUAWEI MACH-WX9 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=a2cbbb7f-c619-418a-a98f-9a9cc31b42fa ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2019 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.28 dmi.board.name: MACH-WX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M13 dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M13 dmi.modalias: dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:svnHUAWEI:pnMACH-WX9:pvrM13:rvnHUAWEI:rnMACH-WX9-PCB:rvrM13:cvnHUAWEI:ct10:cvrM13: dmi.product.family: MateBook X dmi.product.name: MACH-WX9 dmi.product.sku: C189 dmi.product.version: M13 dmi.sys.vendor: HUAWEI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.9
[Desktop-packages] [Bug 1904258] Re: Nautilus (Files) app shows drive that was pulled out without unmount
it's supposed to be a 'o' the lettre and not '0' the number, and it should displays events as they happen on the command line where your started gio -- 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/1904258 Title: Nautilus (Files) app shows drive that was pulled out without unmount Status in nautilus package in Ubuntu: Incomplete Bug description: I mount a flash drive onto my Ubuntu 18.04.5 instance. Started writing data to it. While data is still being written to the flash drive I pulled out the flash drive. Looking at the Nautilus (Files) window, I still see the drive. Running findmnt -S , produces some output. None is produced when offically unmounted. When I plug the flash drive back in, a second instance of the drive appears. When drive is pulled, but Nautilus displays the drive, clicking on it displays "Folder Empty" (or something close). When drive is put back in and the second instance appears, clicking either drive displays contents of drive. This might be caused by a reference being held by the program writing data to the drive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1904258/+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 1884396] Re: Ubuntu freezing intermittently when the mega.nz appindicator is loaded
** Also affects: gnome-shell-extension-appindicator via https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/226 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1884396 Title: Ubuntu freezing intermittently when the mega.nz appindicator is loaded Status in gnome-shell-extension-appindicator: Unknown Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Committed Bug description: [ Impact ] Indicators using (big) pixmap icons cause the shell to use a lot of CPU computation, which interfere with user experience [ Test case ] - Install mega client from https://mega.nz/sync - Run it in ubuntu and ensure it doesn't block the UI while syncing (but even opening/closing the app should be enough to trigger Alternatively use this test tool: https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js Launch it with `gjs` and select the 'Crazy icons updates' menu item: - The shell should not hang [ Regression potential ] Icon updates may be late or not apply immediately (or at all). In general there has been a refactor of the iconCache, so internally it may happen that we load an icon more times, or that there could be an increase in RAM usage as per missing garbage collecting of it. I had similar issues when 20.04 was released, then it disappeared with an upgrade - but sadly it's back. I have short intermittent freezings of the OS. About every 15-30 seconds Ubunut freezes for a second or two. Eg when writing this description, the OS freezes every second word. When the freeze goes away the OS is snappy. I have tried switching between Wayland and Xorg - but the problem persists. If I write something when it freezes up the last character will be replicated many times - like what happened jut now. This problem did not show up in ubuntu 18.04 through 19.10. Hope U can fix this soon - using my laptop in unbearable. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 23:54:52 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: evdi, 1.7.0, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 [19e5:3e04] InstallationDate: Installed on 2020-05-12 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd (Foxlink) HD Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HUAWEI MACH-WX9 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=a2cbbb7f-c619-418a-a98f-9a9cc31b42fa ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2019 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.28 dmi.board.name: MACH-WX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M13 dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M13 dmi.modalias: dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:svnHUAWEI:pnMACH-WX9:pvrM13:rvnHUAWEI:rnMACH-WX9-PCB:rvrM13:cvnHUAWEI:ct10:cvrM13: dmi.product.family: MateBook X dmi.product.name: MACH-WX9 dmi.product.sku: C189 dmi.product.version: M13 dmi.sys.vendor: HUAWEI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-v
[Desktop-packages] [Bug 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
** Also affects: gnome-shell-extension-appindicator via https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/236 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" Status in gnome-shell-extension-appindicator: Unknown Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Committed Bug description: [ Impact ] Using discord application, causes the shell to slowdown and trigger lots of "unable to lookup icon ..." errors [ Test case ] Install discord app: - snap install discord Run it, starting a call seems to trigger it more [ Regression potential ] Icons may not be loaded properly, there may be delays between a good icon and an invalid one (and vice-versa). --- Updated bug #1817073 about this, but it's not really the same since this does not crash the shell fully. When speaking in discord there is supposed to be an icon change on the appindicator and logs spam me with [AppIndicatorSupport-FATAL] unable to lookup icon for discord1_40. The whole desktop freezes for a moment when talking in discord if the appindicator package is installed. Easily reproduced by joining a voice channel in discord and just doing stuff in the gnome ui, watching a video or whatever while talking. This is pretty bad since it leaves no choice but to uninstall gnome- shell-extension-appindicator and loosing that functionality if people wants to use discord on ubuntu. This is also reported on the extensions github page: https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/171 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/157 Someone also made a video on youtube showing the problem: https://www.youtube.com/watch?v=ABavT7yXlso To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/1849142/+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 1893693] Re: Unable to scroll gnome app list
[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Expired -- 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/1893693 Title: Unable to scroll gnome app list Status in gnome-shell package in Ubuntu: Expired Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Expired Bug description: I'm unable to scroll from page 1 to 2 in all apps under the gnome app list. Changing the dock from left side to bottom or right side solves the issue. Ubuntu 20.04 fresh install. See here for same issue: https://askubuntu.com/questions/1241165/should-i-report-show- applications-not-scrolling-as-a-bug ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 31 22:37:56 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-22 (39 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893693/+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 1893693] Re: Unable to scroll gnome app list
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1893693 Title: Unable to scroll gnome app list Status in gnome-shell package in Ubuntu: Expired Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Expired Bug description: I'm unable to scroll from page 1 to 2 in all apps under the gnome app list. Changing the dock from left side to bottom or right side solves the issue. Ubuntu 20.04 fresh install. See here for same issue: https://askubuntu.com/questions/1241165/should-i-report-show- applications-not-scrolling-as-a-bug ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 31 22:37:56 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-22 (39 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893693/+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 1895301] Re: XrandR does not propose 3440x1440 21:9 resolution
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- 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/1895301 Title: XrandR does not propose 3440x1440 21:9 resolution Status in xorg-server package in Ubuntu: Expired Bug description: XrandR does not propose 3440x1440 21:9 resolution on Ubuntu 20.04 : How to reproduce : - Connect on HDMI 1.4 Intel HD 630 mobile a UWUHD 3440x1440 monitor - Only 16:9 are proposed by xrandR - XrandR should propose all supported resolutions WorkAround : manually add the mode xrandr --newmode "3440x1440_30.00" 196.90 3440 3600 3960 4480 1440 1441 1444 1465 -HSync +Vsync xrandr --addmode HDMI-2 3440x1440_30.00 xrandr --output HDMI-2 --mode 3440x1440_30.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1895301/+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 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
Please open the new bug and provide a link so I can follow the progress and test the solution -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Committed Bug description: [ Impact ] Using discord application, causes the shell to slowdown and trigger lots of "unable to lookup icon ..." errors [ Test case ] Install discord app: - snap install discord Run it, starting a call seems to trigger it more [ Regression potential ] Icons may not be loaded properly, there may be delays between a good icon and an invalid one (and vice-versa). --- Updated bug #1817073 about this, but it's not really the same since this does not crash the shell fully. When speaking in discord there is supposed to be an icon change on the appindicator and logs spam me with [AppIndicatorSupport-FATAL] unable to lookup icon for discord1_40. The whole desktop freezes for a moment when talking in discord if the appindicator package is installed. Easily reproduced by joining a voice channel in discord and just doing stuff in the gnome ui, watching a video or whatever while talking. This is pretty bad since it leaves no choice but to uninstall gnome- shell-extension-appindicator and loosing that functionality if people wants to use discord on ubuntu. This is also reported on the extensions github page: https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/171 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/157 Someone also made a video on youtube showing the problem: https://www.youtube.com/watch?v=ABavT7yXlso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+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 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
Since this was declared fixed in Ubuntu 21.04 and 20.10 already it would mess up the bug tracking to say the same fix isn't good enough in 20.04. And nobody's saying it's not an improvement. So I suggest we accept it as is, declare this bug fixed, and then open a new bug about the remaining performance problem. Because aside from anything else the upstream bug is also closed so a new one of them would also need to be opened. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Committed Bug description: [ Impact ] Using discord application, causes the shell to slowdown and trigger lots of "unable to lookup icon ..." errors [ Test case ] Install discord app: - snap install discord Run it, starting a call seems to trigger it more [ Regression potential ] Icons may not be loaded properly, there may be delays between a good icon and an invalid one (and vice-versa). --- Updated bug #1817073 about this, but it's not really the same since this does not crash the shell fully. When speaking in discord there is supposed to be an icon change on the appindicator and logs spam me with [AppIndicatorSupport-FATAL] unable to lookup icon for discord1_40. The whole desktop freezes for a moment when talking in discord if the appindicator package is installed. Easily reproduced by joining a voice channel in discord and just doing stuff in the gnome ui, watching a video or whatever while talking. This is pretty bad since it leaves no choice but to uninstall gnome- shell-extension-appindicator and loosing that functionality if people wants to use discord on ubuntu. This is also reported on the extensions github page: https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/171 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/157 Someone also made a video on youtube showing the problem: https://www.youtube.com/watch?v=ABavT7yXlso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+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 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
It looks like this was intended to be the fix: https://github.com/ubuntu/gnome-shell-extension- appindicator/commit/745c66a73e0 If that's true then perhaps an idler is still too frequent. That could potentially still use high CPU because it's not throttled in any way. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Committed Bug description: [ Impact ] Using discord application, causes the shell to slowdown and trigger lots of "unable to lookup icon ..." errors [ Test case ] Install discord app: - snap install discord Run it, starting a call seems to trigger it more [ Regression potential ] Icons may not be loaded properly, there may be delays between a good icon and an invalid one (and vice-versa). --- Updated bug #1817073 about this, but it's not really the same since this does not crash the shell fully. When speaking in discord there is supposed to be an icon change on the appindicator and logs spam me with [AppIndicatorSupport-FATAL] unable to lookup icon for discord1_40. The whole desktop freezes for a moment when talking in discord if the appindicator package is installed. Easily reproduced by joining a voice channel in discord and just doing stuff in the gnome ui, watching a video or whatever while talking. This is pretty bad since it leaves no choice but to uninstall gnome- shell-extension-appindicator and loosing that functionality if people wants to use discord on ubuntu. This is also reported on the extensions github page: https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/171 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/157 Someone also made a video on youtube showing the problem: https://www.youtube.com/watch?v=ABavT7yXlso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+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 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
Thanks. I've tentatively marked that as a failure, but it still might not be if those messages no longer happen repeatedly. ** Tags removed: verification-done verification-done-focal ** Tags added: verification-failed verification-failed-focal ** Tags removed: verification-failed verification-failed-focal ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Committed Bug description: [ Impact ] Using discord application, causes the shell to slowdown and trigger lots of "unable to lookup icon ..." errors [ Test case ] Install discord app: - snap install discord Run it, starting a call seems to trigger it more [ Regression potential ] Icons may not be loaded properly, there may be delays between a good icon and an invalid one (and vice-versa). --- Updated bug #1817073 about this, but it's not really the same since this does not crash the shell fully. When speaking in discord there is supposed to be an icon change on the appindicator and logs spam me with [AppIndicatorSupport-FATAL] unable to lookup icon for discord1_40. The whole desktop freezes for a moment when talking in discord if the appindicator package is installed. Easily reproduced by joining a voice channel in discord and just doing stuff in the gnome ui, watching a video or whatever while talking. This is pretty bad since it leaves no choice but to uninstall gnome- shell-extension-appindicator and loosing that functionality if people wants to use discord on ubuntu. This is also reported on the extensions github page: https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/171 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/157 Someone also made a video on youtube showing the problem: https://www.youtube.com/watch?v=ABavT7yXlso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+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 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
Status file too ** Attachment added: "status.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+attachment/5435346/+files/status.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Committed Bug description: [ Impact ] Using discord application, causes the shell to slowdown and trigger lots of "unable to lookup icon ..." errors [ Test case ] Install discord app: - snap install discord Run it, starting a call seems to trigger it more [ Regression potential ] Icons may not be loaded properly, there may be delays between a good icon and an invalid one (and vice-versa). --- Updated bug #1817073 about this, but it's not really the same since this does not crash the shell fully. When speaking in discord there is supposed to be an icon change on the appindicator and logs spam me with [AppIndicatorSupport-FATAL] unable to lookup icon for discord1_40. The whole desktop freezes for a moment when talking in discord if the appindicator package is installed. Easily reproduced by joining a voice channel in discord and just doing stuff in the gnome ui, watching a video or whatever while talking. This is pretty bad since it leaves no choice but to uninstall gnome- shell-extension-appindicator and loosing that functionality if people wants to use discord on ubuntu. This is also reported on the extensions github page: https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/171 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/157 Someone also made a video on youtube showing the problem: https://www.youtube.com/watch?v=ABavT7yXlso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+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 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
Done! I see Nov 18 14:24:37 pop-offs ubuntu-appindicat...@ubuntu.com[32755]: discord1, Impossible to lookup icon for 'discord1_33-panel' in path /tmp/.org.chromium.Chromium.PSxy7s Nov 18 14:24:37 pop-offs ubuntu-appindicat...@ubuntu.com[32755]: unable to update icon for discord1 Nov 18 14:24:51 pop-offs ubuntu-appindicat...@ubuntu.com[32755]: discord1, Impossible to lookup icon for 'discord1_39-panel' in path /tmp/.org.chromium.Chromium.cZ6PNp Nov 18 14:24:51 pop-offs ubuntu-appindicat...@ubuntu.com[32755]: unable to update icon for discord1 Please see attached. ** Attachment added: "newmessages.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+attachment/5435342/+files/newmessages.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Committed Bug description: [ Impact ] Using discord application, causes the shell to slowdown and trigger lots of "unable to lookup icon ..." errors [ Test case ] Install discord app: - snap install discord Run it, starting a call seems to trigger it more [ Regression potential ] Icons may not be loaded properly, there may be delays between a good icon and an invalid one (and vice-versa). --- Updated bug #1817073 about this, but it's not really the same since this does not crash the shell fully. When speaking in discord there is supposed to be an icon change on the appindicator and logs spam me with [AppIndicatorSupport-FATAL] unable to lookup icon for discord1_40. The whole desktop freezes for a moment when talking in discord if the appindicator package is installed. Easily reproduced by joining a voice channel in discord and just doing stuff in the gnome ui, watching a video or whatever while talking. This is pretty bad since it leaves no choice but to uninstall gnome- shell-extension-appindicator and loosing that functionality if people wants to use discord on ubuntu. This is also reported on the extensions github page: https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/171 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/157 Someone also made a video on youtube showing the problem: https://www.youtube.com/watch?v=ABavT7yXlso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+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 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
It depends if you see any messages in your system log like this bug describes. If you see the same messages while the problem is happening then this bug is not fixed. If you see no messages, or different messages to what this bug describes then the remaining performance issue probably needs a new bug. To check, please: 1. Run these commands in a Terminal window: dpkg -s gnome-shell-extension-appindicator > status.txt journalctl -f > newmessages.txt 2. Reproduce the remaining issues. 3. Press Ctrl+C in the Terminal window. 4. Attach the resulting text files here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Committed Bug description: [ Impact ] Using discord application, causes the shell to slowdown and trigger lots of "unable to lookup icon ..." errors [ Test case ] Install discord app: - snap install discord Run it, starting a call seems to trigger it more [ Regression potential ] Icons may not be loaded properly, there may be delays between a good icon and an invalid one (and vice-versa). --- Updated bug #1817073 about this, but it's not really the same since this does not crash the shell fully. When speaking in discord there is supposed to be an icon change on the appindicator and logs spam me with [AppIndicatorSupport-FATAL] unable to lookup icon for discord1_40. The whole desktop freezes for a moment when talking in discord if the appindicator package is installed. Easily reproduced by joining a voice channel in discord and just doing stuff in the gnome ui, watching a video or whatever while talking. This is pretty bad since it leaves no choice but to uninstall gnome- shell-extension-appindicator and loosing that functionality if people wants to use discord on ubuntu. This is also reported on the extensions github page: https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/171 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/157 Someone also made a video on youtube showing the problem: https://www.youtube.com/watch?v=ABavT7yXlso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+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 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
Why does the issue still occur with the fix? The severity is lessened but it is still there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Committed Bug description: [ Impact ] Using discord application, causes the shell to slowdown and trigger lots of "unable to lookup icon ..." errors [ Test case ] Install discord app: - snap install discord Run it, starting a call seems to trigger it more [ Regression potential ] Icons may not be loaded properly, there may be delays between a good icon and an invalid one (and vice-versa). --- Updated bug #1817073 about this, but it's not really the same since this does not crash the shell fully. When speaking in discord there is supposed to be an icon change on the appindicator and logs spam me with [AppIndicatorSupport-FATAL] unable to lookup icon for discord1_40. The whole desktop freezes for a moment when talking in discord if the appindicator package is installed. Easily reproduced by joining a voice channel in discord and just doing stuff in the gnome ui, watching a video or whatever while talking. This is pretty bad since it leaves no choice but to uninstall gnome- shell-extension-appindicator and loosing that functionality if people wants to use discord on ubuntu. This is also reported on the extensions github page: https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/171 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/157 Someone also made a video on youtube showing the problem: https://www.youtube.com/watch?v=ABavT7yXlso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+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 1904597] Re: Minimizing a fullscreen window causes Graphical issues
Please run: apport-collect 1904597 to automatically gather system info, and then run: lspci -kv > lspci.txt journalctl -b0 > journal.txt and then attach the resulting text files here. ** Tags added: focal ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1904597 Title: Minimizing a fullscreen window causes Graphical issues Status in gnome-shell package in Ubuntu: Incomplete Bug description: Upon minimizing or tabbing out of a fullscreen window, the cursor will lag behind, and other applications will slow drastically. I have an AMD 5700XT and I believe the included driver is causing the issue but I am not certain. I am using ubuntu 20.04 lts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904597/+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 1904616] Re: after upgrade analog audio output vanished
*** This bug is a duplicate of bug 1897965 *** https://bugs.launchpad.net/bugs/1897965 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1897965, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1897965 PulseAudio doesn't work when pipewire is installed (ie. KDE) -- 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/1904616 Title: after upgrade analog audio output vanished Status in pulseaudio package in Ubuntu: New Bug description: after an upgrade from 20.04 to 20.10 the analog audio output vanished. in pavucontrol there is no corresponding profile available for the built-in audio in the configuration tab. additional info: > aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 > pacmd list-cards 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xb123 irq 140" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1f.3" sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "02c8" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: input:analog-stereo: Analog Stereo Input (priority 65, available: no) output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: unknown) output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI) Output + Analog Stereo Input (priority 5965, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-stereo-extra1+input:analog-stereo: Digital Stereo (HDMI 2) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround-extra1+input:analog-stereo: Digital Surround 5.1 (HDMI 2) Output + Analog Stereo Input (priority 665, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1+input:analog-stereo: Digital Surround 7.1 (HDMI 2) Output + Analog Stereo Input (priority 665, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-stereo-extra2+input:analog-stereo: Digital Stereo (HDMI 3) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-stereo-extra3: Digital Stereo (HDMI 4) Output (priority 5700, available: no) output:hdmi-stereo-extra3+input:analog-stereo: Digital Stereo (HDMI 4) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra3: Digital Surround 5.1 (HDMI 4) Output (priority 600, available: no) output:hdmi-surround71-extra3: Digital Surround 7.1 (HDMI 4) Output (priority 600, available: no) output:hdmi-stereo-extra4: Digital Stereo (HDMI 5) O
[Desktop-packages] [Bug 1904638] Re: Xbox Series X|S controller doesn't pair
** Tags added: groovy ** Summary changed: - Xbox Series X|S controller doesn't pair + Xbox Series X|S controller Xbox icon still blinks after pairing ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Xbox Series X|S controller Xbox icon still blinks after pairing + Xbox Series X|S controller doesn't work and Xbox icon still blinks after pairing -- 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/1904638 Title: Xbox Series X|S controller doesn't work and Xbox icon still blinks after pairing Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: I have Xbox Series X|S controller and the Xbox icon still blinks after the successful pairing. I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm following this bug closely and I can provide any information you need and do any tests you want. mhalano@glados:~$ lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 mhalano@glados:~$ apt policy bluez bluez: Installed: 5.55-0ubuntu1.1 Candidate: 5.55-0ubuntu1.1 Version table: *** 5.55-0ubuntu1.1 500 500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.55-0ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904474] Re: Black/purple screen after booting Ubuntu
Thanks but the new attached logs also don't appear to be useful. They show both a successful boot and recovery mode boot. This makes me think they maybe don't relate to this bug... To be sure, please try again: Reboot, reproduce a failed boot again, wait for a minute or so, then reboot into recovery mode and run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. Only one text file. -- 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/1904474 Title: Black/purple screen after booting Ubuntu Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hi, I am failing to boot into a freshly installed Ubuntu 18.04.5 LTS on my ThinkPad-T460. When choosing the right bootloader in BIOS I get a dark screen, Ubuntu is not booting (also after 15mins of waiting ...). I first thought my issue would be a *Black/purple screen after you boot Ubuntu for the first time* like over here: https://askubuntu.com/questions/162075/my-computer-boots-to-a-black- screen-what-options-do-i-have-to-fix-it So I added ```ǹomodeset``` in the script executed before booting Ubuntu. Interestingly I was able to boot and then made this change persistent by updating the bootloader. I tried some more times to boot and suddenly it stopped working properly (with same blackscreen as before). I also took a look to the bootscript, ```ǹomodeset``` was present there. Then I played around with some other obscure suggestions like adding ```nouveau.noaccel=1``` instead of ```nomodeset``` and replace ```qiuiet splash``` by ```noapic noacpi nosplash inqpoll```, but nothing gave me a soultion which did not get stuck with black screen of death after some reboots. I am a little bit clueless at the moment, so I have appended the uncompressed logs in ```/var/log```, captured like in https://wiki.ubuntu.com/DebuggingKernelBoot . The files appended are from a boot that got stuck, I have killed my laptop after 10mins of nothing happening. Btw. I have a dual boot with Windows 10, but I do not know if this is relevant for this issue. Best Alexander --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-16 (1 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Package: gnome-shell 3.28.4-0ubuntu18.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-53.59~18.04.1-generic 5.4.65 Tags: bionic Uname: Linux 5.4.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904474/+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 1904470] Re: 100Hz monitor fails to wake after lock
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1904470 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: focal groovy ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (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/1904470 Title: 100Hz monitor fails to wake after lock Status in gnome-shell package in Ubuntu: Incomplete Bug description: When set to 100Hz the monitor will work without issues until the machine is locked. When i want to unlock it the scrren does not wake up. The only way to wake up the screen is to unplug the HDMI cable from the GPU and plug it in again. This issue does not happen on 60Hz. This issue is present on both 20.04.1 LTS and 20.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904470/+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 1904568] Re: Noise on screen while using
*** This bug is a duplicate of bug 1896091 *** https://bugs.launchpad.net/bugs/1896091 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1896091, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1896091 [i915] Noise-like lines of graphics corruption when moving windows in Xorg sessions -- 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/1904568 Title: Noise on screen while using Status in xorg package in Ubuntu: New Bug description: When I'm using my laptop, I sometimes see some noises on screen. they're mostly horizontal noise lines in panels (but sometimes on other parts). I attached a picture of the problem. I use Kubuntu 20.10. The problem is present when I connect my laptop to external screen (so it's not monitor's problem). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Tue Nov 17 16:30:07 2020 DistUpgraded: 2020-11-08 22:54:50,746 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1131] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce MX130] [1043:1131] InstallationDate: Installed on 2020-10-02 (45 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. VivoBook S15 X510UF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-28-generic root=UUID=2dccc476-4ac0-4ab2-9742-bde2ad020de3 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to groovy on 2020-11-08 (8 days ago) dmi.bios.date: 09/06/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X510UF.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X510UF dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX510UF.304:bd09/06/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnVivoBookS15X510UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX510UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook S dmi.product.name: VivoBook S15 X510UF dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER 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 N/A 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/ubuntu/+source/xorg/+bug/1904568/+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 1904462] Re: Dejadup fails after upgrading from 18.04 to 20.04
Were you using the snap package? There was a bug briefly in duplicity that would have caused this error, but it is fixed now. Do you still see this? I don’t believe the bug was ever present in Ubuntu 20.04 itself. ** Changed in: deja-dup (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1904462 Title: Dejadup fails after upgrading from 18.04 to 20.04 Status in Ubuntu MATE: New Status in deja-dup package in Ubuntu: Incomplete Bug description: Upgraded from 18.04 to 20.04 using do-release-upgrade. Dejadup now fails to make backups. Log attached, i think the last line is the error. "PermissionError: [Errno 13] Permission denied: b'/home/morpheus/.config/gnome-mpv/.deja-dup-ignore' I have checked inside that folder, and there is no hidden file '.deja- dup-ignore' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1904462/+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 1903986] Re: Ubuntu 20.04 freezes with remmina in full-screen
If your mouse pointer still works then that means only the gnome-shell process has frozen or crashed. The mouse pointer keeps moving because it's managed by the Xorg process. So next we need more information about the graphics hardware and to check for historical crashes. Please run this command to collect more system info: apport-collect 1903986 Then to help us find the cause of any crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1903986 Title: Ubuntu 20.04 freezes with remmina in full-screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: On Ubuntu 20.04 using Remmina accessing remote Windows session to my work and everything was working fine for 5 hours and then suddenly Reminna freezes. Mouse pointer still working fine, but Remmina not responding and also keyboard not responding (maybe because all of the keys are controller by Remmina). This problem is now third time the problem appeared: - bug 1902051 - bug 1903710 with no response. :( Work-around: hard press power button to power off laptop and power on it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 12:38:25 2020 InstallationDate: Installed on 2019-10-23 (386 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (89 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+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 1904237] Re: [regression] On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1904237 Title: [regression] On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal Status in gnome-shell package in Ubuntu: New Bug description: mutter 3.36.6-1ubuntu0.20.04.2 shows again the incorrect behavior that was fixed in https://bugs.launchpad.net/mutter/+bug/1880596 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-13 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: mutter 3.36.6-1ubuntu0.20.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-13 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904237/+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 1303316] Re: Digital S/PDIF output is not present in 5.1 mode
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017. Ubuntu 14.04 (trusty) reached end of standard support in April 2019. Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Won't Fix -- 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/1303316 Title: Digital S/PDIF output is not present in 5.1 mode Status in pulseaudio package in Ubuntu: Won't Fix Bug description: I have the sound connected through digital S / PDIF Sound works properly selecting stereo, but can not get it to work using 5.1 When I select stereo sound, appears on the tab below to phonon spdif output option. When I select Output 5.1, that option does not appear. I imagine the error will also occur selecting 7.1 Deputy screenshots. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: phonon 4:4.7.0really4.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55 Uname: Linux 3.2.0-60-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Sun Apr 6 13:12:42 2014 InstallationMedia: Kubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MarkForUpload: True ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: phonon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1303316/+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 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward
Or is that a typo and you meant to say you are using Ubuntu 20.10 already? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 onward Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Groovy: Fix Committed Bug description: SRU request: [Impact] * Installing the 340 driver will fail when running Linux 5.7 or newer. [Test Case] * Install nvidia-340 from -proposed. * Check that the modules was built and installed, using the following command: dkms status [Regression Potential] * The driver once built and installed could be not working and lead to have the desktop not starting for example. Check that you get a desktop loaded and decent performances Hi developers, thanks for your great work on porting legacy drivers to Ubuntu. Anyway I have to complain in not seeing Nvidia 340.108 driver for kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4, because Nvidia 340.108 fails to install with kernels 5.5 and 5.6. Archlinux already has a driver for Kernel 5.6 via AUR (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has one for kernel 5.5. So, the question is: when will we see a new version in repositories? Bye and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+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 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward
Good to hear. Unfortunately that version is intended for Ubuntu 20.10 so needs to be tested there before it is approved. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 onward Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Groovy: Fix Committed Bug description: SRU request: [Impact] * Installing the 340 driver will fail when running Linux 5.7 or newer. [Test Case] * Install nvidia-340 from -proposed. * Check that the modules was built and installed, using the following command: dkms status [Regression Potential] * The driver once built and installed could be not working and lead to have the desktop not starting for example. Check that you get a desktop loaded and decent performances Hi developers, thanks for your great work on porting legacy drivers to Ubuntu. Anyway I have to complain in not seeing Nvidia 340.108 driver for kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4, because Nvidia 340.108 fails to install with kernels 5.5 and 5.6. Archlinux already has a driver for Kernel 5.6 via AUR (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has one for kernel 5.5. So, the question is: when will we see a new version in repositories? Bye and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+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 1904258] Re: Nautilus (Files) app shows drive that was pulled out without unmount
Could you tell me where to find the generated logs? I see terminal output running gio mount -0 but don't know where the generated log is being saved. -- 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/1904258 Title: Nautilus (Files) app shows drive that was pulled out without unmount Status in nautilus package in Ubuntu: Incomplete Bug description: I mount a flash drive onto my Ubuntu 18.04.5 instance. Started writing data to it. While data is still being written to the flash drive I pulled out the flash drive. Looking at the Nautilus (Files) window, I still see the drive. Running findmnt -S , produces some output. None is produced when offically unmounted. When I plug the flash drive back in, a second instance of the drive appears. When drive is pulled, but Nautilus displays the drive, clicking on it displays "Folder Empty" (or something close). When drive is put back in and the second instance appears, clicking either drive displays contents of drive. This might be caused by a reference being held by the program writing data to the drive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1904258/+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 1904547] Re: gnome-control-center crashed with SIGSEGV in cc_display_config_get_panel_orientation_managed() from reset_current_config() from on_screen_changed() from on_screen_
Ironically for me it happens inside GNOME when I am developing GNOME. -- 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/1904547 Title: gnome-control-center crashed with SIGSEGV in cc_display_config_get_panel_orientation_managed() from reset_current_config() from on_screen_changed() from on_screen_changed() from g_closure_invoke() Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-control-center package in Debian: Unknown Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.38.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/22eb073fed09f6a2f9f5ff9bd4b2677ea9b8336f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1904547/+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 1904640] [NEW] Placeholder for 1.8.3 update
Public bug reported: https://github.com/flatpak/flatpak/releases/tag/1.8.3 ** Affects: flatpak (Ubuntu) Importance: Undecided Assignee: Andrew Hayzen (ahayzen) Status: In Progress ** Changed in: flatpak (Ubuntu) Status: New => In Progress ** Changed in: flatpak (Ubuntu) Assignee: (unassigned) => Andrew Hayzen (ahayzen) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1904640 Title: Placeholder for 1.8.3 update Status in flatpak package in Ubuntu: In Progress Bug description: https://github.com/flatpak/flatpak/releases/tag/1.8.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1904640/+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 1904638] [NEW] Xbox Series X|S controller doesn't pair
Public bug reported: I have Xbox Series X|S controller and the Xbox icon still blinks after the successful pairing. I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm following this bug closely and I can provide any information you need and do any tests you want. mhalano@glados:~$ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 mhalano@glados:~$ apt policy bluez bluez: Installed: 5.55-0ubuntu1.1 Candidate: 5.55-0ubuntu1.1 Version table: *** 5.55-0ubuntu1.1 500 500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.55-0ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages ** 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/1904638 Title: Xbox Series X|S controller doesn't pair Status in bluez package in Ubuntu: New Bug description: I have Xbox Series X|S controller and the Xbox icon still blinks after the successful pairing. I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm following this bug closely and I can provide any information you need and do any tests you want. mhalano@glados:~$ lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 mhalano@glados:~$ apt policy bluez bluez: Installed: 5.55-0ubuntu1.1 Candidate: 5.55-0ubuntu1.1 Version table: *** 5.55-0ubuntu1.1 500 500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.55-0ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1899262] Autopkgtest regression report (wpa/2:2.6-15ubuntu2.6)
All autopkgtests for the newly accepted wpa (2:2.6-15ubuntu2.6) for bionic have finished running. The following regressions have been reported in tests triggered by the package: netplan.io/0.99-0ubuntu3~18.04.3 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#wpa [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1899262 Title: Broken dbus GetAll message to wpa supplicant interface properties Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Bionic: Fix Committed Bug description: * Impact One of the distro patch is incorrect and create issues when trying to query dbus properties * Test Case $ sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1 /fi/w1/wpa_supplicant1/Interfaces/1 org.freedesktop.DBus.Properties.GetAll string:fi.w1.wpa_supplicant1.Interface shouldn't error out (the /1 reflect the interface number and could be a different value, check with d-feet if needed) * Regression potential The fixes is in the dbus interface, check that communication with desktop clients (indicator, applet, settings) still works correctly, returning expected informations on the signal, etc - dbus-send is able to read the properties of interface using GetAll. Those information include interface name, status, encryption method, etc. The regression was introduced when someone try to have the Station attribute supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1899262/+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 1903936] Autopkgtest regression report (snapd-glib/1.58-0ubuntu0.20.10.0)
All autopkgtests for the newly accepted snapd-glib (1.58-0ubuntu0.20.10.0) for groovy have finished running. The following regressions have been reported in tests triggered by the package: software-properties/0.99.3 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/groovy/update_excuses.html#snapd-glib [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1903936 Title: Update to 1.58 Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Bionic: Fix Committed Status in snapd-glib source package in Focal: Fix Committed Status in snapd-glib source package in Groovy: Fix Committed Status in snapd-glib source package in Hirsute: Fix Released Bug description: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Changes to error message carry low risk of introducing an issue if such an error occurred. GIR annotation changes fix a call that was previously broken, and is unlikely to make that any worse. Risks are mitigated by automatic regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1903936/+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 1901290] Re: [SRU] Enchant-2 does not work properly with backends that want a NUL-terminated string
This bug was fixed in the package enchant-2 - 2.2.8-1ubuntu0.20.04.1
---
enchant-2 (2.2.8-1ubuntu0.20.04.1) focal; urgency=medium
* debian/patches/Fix_back-ends_that_want_a_NUL-terminated_string.patch:
- Fix Zemberek and Voikko backends under eg gspell (LP: #1901290)
-- Timo Jyrinki Thu, 05 Nov 2020 16:13:12 +0200
** Changed in: enchant-2 (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to enchant-2 in Ubuntu.
https://bugs.launchpad.net/bugs/1901290
Title:
[SRU] Enchant-2 does not work properly with backends that want a NUL-
terminated string
Status in enchant-2 package in Ubuntu:
Fix Released
Status in enchant-2 source package in Focal:
Fix Released
Status in enchant-2 source package in Groovy:
Fix Released
Status in enchant-2 package in Debian:
Unknown
Bug description:
[Impact]
Spell checking / spelling error highlighting does not work properly in
eg gedit, gnote or gtranslator when using a language which uses Voikko
(often Finnish, but also North Sámi (giella-sme package) or user
installed HFST spellers like other Sámi languages or Greenlandic) or
Zemberek (Turkish) backend via Enchant-2.
[Test Case]
(from https://gitlab.gnome.org/GNOME/gspell/-/issues/10)
1. apt install libenchant-2-voikko voikko-fi
2. Run gedit, gnote, gtranslator or other gspell using program
3. (in gedit) Enable underlining of incorrectly typed words, and set Finnish
(suomi) as language
4. Copy-paste for example "tämä on testitekstiä" ("this is test text"), maybe
for a comparison "tämmä on vihre" (1st and 3rd word incorrect)
5. Note how everything is underlined - in suggestions, you can choose the
same word and the underlining disappears, but as soon as you eg "leave" the
word (press space after it) it gets underlined again. However, if doing manual
spell checking the words are correctly understood as being correct.
[Where problems could occur]
The patch changes code in voikko and zemberek plugins, which are built
and shipped separately. Zemberek is not built at all in Debian or
Ubuntu. Thus, no changes (or problems) should be possible to happen
outside the Voikko plugin (libenchant-2-voikko binary package), unless
a toolchain change since the last build in March 2020 would cause a
change with unchanged source.
Voikko plugin would be good to test via multiple libraries like
gspell, gtkspell, sonnet that there are no regressions.
--- original report ---
This shows up particularly with the inline checking feature of gspell
in eg gedit which is part of the default Ubuntu installation.
The issue is fixed in Enchant 2.2.12, and after that release reaches
Debian and Ubuntu hirsute, I hope a backport of this patch to https
://patch-diff.githubusercontent.com/raw/AbiWord/enchant/pull/260.patch
can be done to groovy and focal.
SRU paperwork to be added later, but in general all backends would be
good to test after the backport in various ways like gspell, sonnet.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/enchant-2/+bug/1901290/+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 1901290] Re: [SRU] Enchant-2 does not work properly with backends that want a NUL-terminated string
This bug was fixed in the package enchant-2 - 2.2.8-1ubuntu0.20.10.1
---
enchant-2 (2.2.8-1ubuntu0.20.10.1) groovy; urgency=medium
* debian/patches/Fix_back-ends_that_want_a_NUL-terminated_string.patch:
- Fix Zemberek and Voikko backends under eg gspell (LP: #1901290)
-- Timo Jyrinki Thu, 05 Nov 2020 16:13:12 +0200
** Changed in: enchant-2 (Ubuntu Groovy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to enchant-2 in Ubuntu.
https://bugs.launchpad.net/bugs/1901290
Title:
[SRU] Enchant-2 does not work properly with backends that want a NUL-
terminated string
Status in enchant-2 package in Ubuntu:
Fix Released
Status in enchant-2 source package in Focal:
Fix Released
Status in enchant-2 source package in Groovy:
Fix Released
Status in enchant-2 package in Debian:
Unknown
Bug description:
[Impact]
Spell checking / spelling error highlighting does not work properly in
eg gedit, gnote or gtranslator when using a language which uses Voikko
(often Finnish, but also North Sámi (giella-sme package) or user
installed HFST spellers like other Sámi languages or Greenlandic) or
Zemberek (Turkish) backend via Enchant-2.
[Test Case]
(from https://gitlab.gnome.org/GNOME/gspell/-/issues/10)
1. apt install libenchant-2-voikko voikko-fi
2. Run gedit, gnote, gtranslator or other gspell using program
3. (in gedit) Enable underlining of incorrectly typed words, and set Finnish
(suomi) as language
4. Copy-paste for example "tämä on testitekstiä" ("this is test text"), maybe
for a comparison "tämmä on vihre" (1st and 3rd word incorrect)
5. Note how everything is underlined - in suggestions, you can choose the
same word and the underlining disappears, but as soon as you eg "leave" the
word (press space after it) it gets underlined again. However, if doing manual
spell checking the words are correctly understood as being correct.
[Where problems could occur]
The patch changes code in voikko and zemberek plugins, which are built
and shipped separately. Zemberek is not built at all in Debian or
Ubuntu. Thus, no changes (or problems) should be possible to happen
outside the Voikko plugin (libenchant-2-voikko binary package), unless
a toolchain change since the last build in March 2020 would cause a
change with unchanged source.
Voikko plugin would be good to test via multiple libraries like
gspell, gtkspell, sonnet that there are no regressions.
--- original report ---
This shows up particularly with the inline checking feature of gspell
in eg gedit which is part of the default Ubuntu installation.
The issue is fixed in Enchant 2.2.12, and after that release reaches
Debian and Ubuntu hirsute, I hope a backport of this patch to https
://patch-diff.githubusercontent.com/raw/AbiWord/enchant/pull/260.patch
can be done to groovy and focal.
SRU paperwork to be added later, but in general all backends would be
good to test after the backport in various ways like gspell, sonnet.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/enchant-2/+bug/1901290/+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 1904474] Re: Black/purple screen after booting Ubuntu
Sorry, the BTW above was nonsense. When trying to boot using `Advanced Options` in BIOS and choose Ubuntu there, the screen shows ` Loading Linux5.4.0-53-generic ... Loading initial ramdisk ` and gets stuck there. The strange comes now: if I open the bootscript for Ubuntu in BIOS removing one of the two spaces in the line `ro nomodeset quiet splash` or `ro nouveau.noaccel=1 quiet splash` (between ro and the other stuff) works fine, boots like a charm. I am really curious what is going on here :-) -- 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/1904474 Title: Black/purple screen after booting Ubuntu Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hi, I am failing to boot into a freshly installed Ubuntu 18.04.5 LTS on my ThinkPad-T460. When choosing the right bootloader in BIOS I get a dark screen, Ubuntu is not booting (also after 15mins of waiting ...). I first thought my issue would be a *Black/purple screen after you boot Ubuntu for the first time* like over here: https://askubuntu.com/questions/162075/my-computer-boots-to-a-black- screen-what-options-do-i-have-to-fix-it So I added ```ǹomodeset``` in the script executed before booting Ubuntu. Interestingly I was able to boot and then made this change persistent by updating the bootloader. I tried some more times to boot and suddenly it stopped working properly (with same blackscreen as before). I also took a look to the bootscript, ```ǹomodeset``` was present there. Then I played around with some other obscure suggestions like adding ```nouveau.noaccel=1``` instead of ```nomodeset``` and replace ```qiuiet splash``` by ```noapic noacpi nosplash inqpoll```, but nothing gave me a soultion which did not get stuck with black screen of death after some reboots. I am a little bit clueless at the moment, so I have appended the uncompressed logs in ```/var/log```, captured like in https://wiki.ubuntu.com/DebuggingKernelBoot . The files appended are from a boot that got stuck, I have killed my laptop after 10mins of nothing happening. Btw. I have a dual boot with Windows 10, but I do not know if this is relevant for this issue. Best Alexander --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-16 (1 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Package: gnome-shell 3.28.4-0ubuntu18.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-53.59~18.04.1-generic 5.4.65 Tags: bionic Uname: Linux 5.4.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904474/+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 1904474] Re: Black/purple screen after booting Ubuntu
** Attachment added: "prevboot2.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904474/+attachment/5435258/+files/prevboot2.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/1904474 Title: Black/purple screen after booting Ubuntu Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hi, I am failing to boot into a freshly installed Ubuntu 18.04.5 LTS on my ThinkPad-T460. When choosing the right bootloader in BIOS I get a dark screen, Ubuntu is not booting (also after 15mins of waiting ...). I first thought my issue would be a *Black/purple screen after you boot Ubuntu for the first time* like over here: https://askubuntu.com/questions/162075/my-computer-boots-to-a-black- screen-what-options-do-i-have-to-fix-it So I added ```ǹomodeset``` in the script executed before booting Ubuntu. Interestingly I was able to boot and then made this change persistent by updating the bootloader. I tried some more times to boot and suddenly it stopped working properly (with same blackscreen as before). I also took a look to the bootscript, ```ǹomodeset``` was present there. Then I played around with some other obscure suggestions like adding ```nouveau.noaccel=1``` instead of ```nomodeset``` and replace ```qiuiet splash``` by ```noapic noacpi nosplash inqpoll```, but nothing gave me a soultion which did not get stuck with black screen of death after some reboots. I am a little bit clueless at the moment, so I have appended the uncompressed logs in ```/var/log```, captured like in https://wiki.ubuntu.com/DebuggingKernelBoot . The files appended are from a boot that got stuck, I have killed my laptop after 10mins of nothing happening. Btw. I have a dual boot with Windows 10, but I do not know if this is relevant for this issue. Best Alexander --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-16 (1 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Package: gnome-shell 3.28.4-0ubuntu18.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-53.59~18.04.1-generic 5.4.65 Tags: bionic Uname: Linux 5.4.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904474/+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 1904474] Re: Black/purple screen after booting Ubuntu
sorry appended file abve seems not to work. ** Attachment added: "prevboot1.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904474/+attachment/5435257/+files/prevboot1.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/1904474 Title: Black/purple screen after booting Ubuntu Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hi, I am failing to boot into a freshly installed Ubuntu 18.04.5 LTS on my ThinkPad-T460. When choosing the right bootloader in BIOS I get a dark screen, Ubuntu is not booting (also after 15mins of waiting ...). I first thought my issue would be a *Black/purple screen after you boot Ubuntu for the first time* like over here: https://askubuntu.com/questions/162075/my-computer-boots-to-a-black- screen-what-options-do-i-have-to-fix-it So I added ```ǹomodeset``` in the script executed before booting Ubuntu. Interestingly I was able to boot and then made this change persistent by updating the bootloader. I tried some more times to boot and suddenly it stopped working properly (with same blackscreen as before). I also took a look to the bootscript, ```ǹomodeset``` was present there. Then I played around with some other obscure suggestions like adding ```nouveau.noaccel=1``` instead of ```nomodeset``` and replace ```qiuiet splash``` by ```noapic noacpi nosplash inqpoll```, but nothing gave me a soultion which did not get stuck with black screen of death after some reboots. I am a little bit clueless at the moment, so I have appended the uncompressed logs in ```/var/log```, captured like in https://wiki.ubuntu.com/DebuggingKernelBoot . The files appended are from a boot that got stuck, I have killed my laptop after 10mins of nothing happening. Btw. I have a dual boot with Windows 10, but I do not know if this is relevant for this issue. Best Alexander --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-16 (1 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Package: gnome-shell 3.28.4-0ubuntu18.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-53.59~18.04.1-generic 5.4.65 Tags: bionic Uname: Linux 5.4.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904474/+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 1904474] Re: Black/purple screen after booting Ubuntu
Hi, I have followed your suggestion and recorded the output of `journalctl -b-1` to the files appended. `prevboot1.text` is with `GRUB_CMDLINE_LINUX_DEFAULT="nouveau.noaccel=1 quiet splash"` and `prevboot2.txt` is with `GRUB_CMDLINE_LINUX_DEFAULT="nomodeset quiet splash"` in `/etc/default/grub`, which both fail to boot (or is X not loaded properly?). BTW I have found that my Ubuntu starts properly if I boot it with the entry in `Advanced Options` in BIOS and choose it there; only using the Ubuntu entry first displayed when BIOS pops up gets stucked in black/purple screen. Best Alexander ** Attachment added: "prevboot" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904474/+attachment/5435256/+files/prevboot -- 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/1904474 Title: Black/purple screen after booting Ubuntu Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hi, I am failing to boot into a freshly installed Ubuntu 18.04.5 LTS on my ThinkPad-T460. When choosing the right bootloader in BIOS I get a dark screen, Ubuntu is not booting (also after 15mins of waiting ...). I first thought my issue would be a *Black/purple screen after you boot Ubuntu for the first time* like over here: https://askubuntu.com/questions/162075/my-computer-boots-to-a-black- screen-what-options-do-i-have-to-fix-it So I added ```ǹomodeset``` in the script executed before booting Ubuntu. Interestingly I was able to boot and then made this change persistent by updating the bootloader. I tried some more times to boot and suddenly it stopped working properly (with same blackscreen as before). I also took a look to the bootscript, ```ǹomodeset``` was present there. Then I played around with some other obscure suggestions like adding ```nouveau.noaccel=1``` instead of ```nomodeset``` and replace ```qiuiet splash``` by ```noapic noacpi nosplash inqpoll```, but nothing gave me a soultion which did not get stuck with black screen of death after some reboots. I am a little bit clueless at the moment, so I have appended the uncompressed logs in ```/var/log```, captured like in https://wiki.ubuntu.com/DebuggingKernelBoot . The files appended are from a boot that got stuck, I have killed my laptop after 10mins of nothing happening. Btw. I have a dual boot with Windows 10, but I do not know if this is relevant for this issue. Best Alexander --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-16 (1 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Package: gnome-shell 3.28.4-0ubuntu18.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-53.59~18.04.1-generic 5.4.65 Tags: bionic Uname: Linux 5.4.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904474/+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 1904474] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1904474/+attachment/5435253/+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/1904474 Title: Black/purple screen after booting Ubuntu Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hi, I am failing to boot into a freshly installed Ubuntu 18.04.5 LTS on my ThinkPad-T460. When choosing the right bootloader in BIOS I get a dark screen, Ubuntu is not booting (also after 15mins of waiting ...). I first thought my issue would be a *Black/purple screen after you boot Ubuntu for the first time* like over here: https://askubuntu.com/questions/162075/my-computer-boots-to-a-black- screen-what-options-do-i-have-to-fix-it So I added ```ǹomodeset``` in the script executed before booting Ubuntu. Interestingly I was able to boot and then made this change persistent by updating the bootloader. I tried some more times to boot and suddenly it stopped working properly (with same blackscreen as before). I also took a look to the bootscript, ```ǹomodeset``` was present there. Then I played around with some other obscure suggestions like adding ```nouveau.noaccel=1``` instead of ```nomodeset``` and replace ```qiuiet splash``` by ```noapic noacpi nosplash inqpoll```, but nothing gave me a soultion which did not get stuck with black screen of death after some reboots. I am a little bit clueless at the moment, so I have appended the uncompressed logs in ```/var/log```, captured like in https://wiki.ubuntu.com/DebuggingKernelBoot . The files appended are from a boot that got stuck, I have killed my laptop after 10mins of nothing happening. Btw. I have a dual boot with Windows 10, but I do not know if this is relevant for this issue. Best Alexander --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-16 (1 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Package: gnome-shell 3.28.4-0ubuntu18.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-53.59~18.04.1-generic 5.4.65 Tags: bionic Uname: Linux 5.4.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904474/+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 1899262] Re: Broken dbus GetAll message to wpa supplicant interface properties
Hello Michael, or anyone else affected, Accepted wpa into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wpa/2:2.6-15ubuntu2.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: wpa (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1899262 Title: Broken dbus GetAll message to wpa supplicant interface properties Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Bionic: Fix Committed Bug description: * Impact One of the distro patch is incorrect and create issues when trying to query dbus properties * Test Case $ sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1 /fi/w1/wpa_supplicant1/Interfaces/1 org.freedesktop.DBus.Properties.GetAll string:fi.w1.wpa_supplicant1.Interface shouldn't error out (the /1 reflect the interface number and could be a different value, check with d-feet if needed) * Regression potential The fixes is in the dbus interface, check that communication with desktop clients (indicator, applet, settings) still works correctly, returning expected informations on the signal, etc - dbus-send is able to read the properties of interface using GetAll. Those information include interface name, status, encryption method, etc. The regression was introduced when someone try to have the Station attribute supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1899262/+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 1904474] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1904474/+attachment/5435255/+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/1904474 Title: Black/purple screen after booting Ubuntu Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hi, I am failing to boot into a freshly installed Ubuntu 18.04.5 LTS on my ThinkPad-T460. When choosing the right bootloader in BIOS I get a dark screen, Ubuntu is not booting (also after 15mins of waiting ...). I first thought my issue would be a *Black/purple screen after you boot Ubuntu for the first time* like over here: https://askubuntu.com/questions/162075/my-computer-boots-to-a-black- screen-what-options-do-i-have-to-fix-it So I added ```ǹomodeset``` in the script executed before booting Ubuntu. Interestingly I was able to boot and then made this change persistent by updating the bootloader. I tried some more times to boot and suddenly it stopped working properly (with same blackscreen as before). I also took a look to the bootscript, ```ǹomodeset``` was present there. Then I played around with some other obscure suggestions like adding ```nouveau.noaccel=1``` instead of ```nomodeset``` and replace ```qiuiet splash``` by ```noapic noacpi nosplash inqpoll```, but nothing gave me a soultion which did not get stuck with black screen of death after some reboots. I am a little bit clueless at the moment, so I have appended the uncompressed logs in ```/var/log```, captured like in https://wiki.ubuntu.com/DebuggingKernelBoot . The files appended are from a boot that got stuck, I have killed my laptop after 10mins of nothing happening. Btw. I have a dual boot with Windows 10, but I do not know if this is relevant for this issue. Best Alexander --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-16 (1 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Package: gnome-shell 3.28.4-0ubuntu18.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-53.59~18.04.1-generic 5.4.65 Tags: bionic Uname: Linux 5.4.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904474/+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 1904474] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1904474/+attachment/5435254/+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/1904474 Title: Black/purple screen after booting Ubuntu Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hi, I am failing to boot into a freshly installed Ubuntu 18.04.5 LTS on my ThinkPad-T460. When choosing the right bootloader in BIOS I get a dark screen, Ubuntu is not booting (also after 15mins of waiting ...). I first thought my issue would be a *Black/purple screen after you boot Ubuntu for the first time* like over here: https://askubuntu.com/questions/162075/my-computer-boots-to-a-black- screen-what-options-do-i-have-to-fix-it So I added ```ǹomodeset``` in the script executed before booting Ubuntu. Interestingly I was able to boot and then made this change persistent by updating the bootloader. I tried some more times to boot and suddenly it stopped working properly (with same blackscreen as before). I also took a look to the bootscript, ```ǹomodeset``` was present there. Then I played around with some other obscure suggestions like adding ```nouveau.noaccel=1``` instead of ```nomodeset``` and replace ```qiuiet splash``` by ```noapic noacpi nosplash inqpoll```, but nothing gave me a soultion which did not get stuck with black screen of death after some reboots. I am a little bit clueless at the moment, so I have appended the uncompressed logs in ```/var/log```, captured like in https://wiki.ubuntu.com/DebuggingKernelBoot . The files appended are from a boot that got stuck, I have killed my laptop after 10mins of nothing happening. Btw. I have a dual boot with Windows 10, but I do not know if this is relevant for this issue. Best Alexander --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-16 (1 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Package: gnome-shell 3.28.4-0ubuntu18.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-53.59~18.04.1-generic 5.4.65 Tags: bionic Uname: Linux 5.4.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904474/+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 1904474] Re: Black/purple screen after booting Ubuntu
apport information ** Tags added: apport-collected ** Description changed: Hi, I am failing to boot into a freshly installed Ubuntu 18.04.5 LTS on my ThinkPad-T460. When choosing the right bootloader in BIOS I get a dark screen, Ubuntu is not booting (also after 15mins of waiting ...). I first thought my issue would be a *Black/purple screen after you boot Ubuntu for the first time* like over here: https://askubuntu.com/questions/162075/my-computer-boots-to-a-black- screen-what-options-do-i-have-to-fix-it So I added ```ǹomodeset``` in the script executed before booting Ubuntu. Interestingly I was able to boot and then made this change persistent by updating the bootloader. I tried some more times to boot and suddenly it stopped working properly (with same blackscreen as before). I also took a look to the bootscript, ```ǹomodeset``` was present there. Then I played around with some other obscure suggestions like adding ```nouveau.noaccel=1``` instead of ```nomodeset``` and replace ```qiuiet splash``` by ```noapic noacpi nosplash inqpoll```, but nothing gave me a soultion which did not get stuck with black screen of death after some reboots. I am a little bit clueless at the moment, so I have appended the uncompressed logs in ```/var/log```, captured like in https://wiki.ubuntu.com/DebuggingKernelBoot . The files appended are from a boot that got stuck, I have killed my laptop after 10mins of nothing happening. Btw. I have a dual boot with Windows 10, but I do not know if this is relevant for this issue. Best Alexander + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.20 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2020-11-16 (1 days ago) + InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) + Package: gnome-shell 3.28.4-0ubuntu18.04.3 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-53.59~18.04.1-generic 5.4.65 + Tags: bionic + Uname: Linux 5.4.0-53-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1904474/+attachment/5435252/+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/1904474 Title: Black/purple screen after booting Ubuntu Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hi, I am failing to boot into a freshly installed Ubuntu 18.04.5 LTS on my ThinkPad-T460. When choosing the right bootloader in BIOS I get a dark screen, Ubuntu is not booting (also after 15mins of waiting ...). I first thought my issue would be a *Black/purple screen after you boot Ubuntu for the first time* like over here: https://askubuntu.com/questions/162075/my-computer-boots-to-a-black- screen-what-options-do-i-have-to-fix-it So I added ```ǹomodeset``` in the script executed before booting Ubuntu. Interestingly I was able to boot and then made this change persistent by updating the bootloader. I tried some more times to boot and suddenly it stopped working properly (with same blackscreen as before). I also took a look to the bootscript, ```ǹomodeset``` was present there. Then I played around with some other obscure suggestions like adding ```nouveau.noaccel=1``` instead of ```nomodeset``` and replace ```qiuiet splash``` by ```noapic noacpi nosplash inqpoll```, but nothing gave me a soultion which did not get stuck with black screen of death after some reboots. I am a little bit clueless at the moment, so I have appended the uncompressed logs in ```/var/log```, captured like in https://wiki.ubuntu.com/DebuggingKernelBoot . The files appended are from a boot that got stuck, I have killed my laptop after 10mins of nothing happening. Btw. I have a dual boot with Windows 10, but I do not know if this is relevant for this issue. Best Alexander --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-16 (1 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Package: gnome-shell 3.28.4-0ubuntu18.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-53.59~18.04.1-generic 5.4.65 Tags: bionic Uname: Linux 5.4.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/
[Desktop-packages] [Bug 1897530] Re: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"
Hello Kent, or anyone else affected, Accepted xorg-server into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:1.20.8-2ubuntu2.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: xorg-server (Ubuntu Focal) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-focal -- 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/1897530 Title: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server source package in Bionic: Invalid Status in xorg-server-hwe-18.04 source package in Bionic: Confirmed Status in xorg-server source package in Focal: Fix Committed Status in xorg-server-hwe-18.04 source package in Focal: Invalid Bug description: [Impact] On a hybrid machine where NVIDIA is rendering the screen, if a display attached to a dock is removed while on suspend mode, on resume X crashes. [Test case] Test hot-unplug during suspend and resume, X shouldn't crash. [Regression potential] This replaces a patch we had with two commits that got merged upstream after a fairly extensive review process: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/443/ And we ship it in groovy. If there were issues caused by it, they would be around hot-unplugging a dock while on suspend and such. -- Expectation: on removal of external display during S3, after resume eDP rendering should still continue by Nvidia. Symptom description: Plug out DP cable when suspension, when resume, X will crash. 1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but NV was rendering for eDP. 2. After S3 entry dock was removed. 3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails resume of TB3 devices and logs confirm that. 4. X fails to enter VT due to Null meta mode. To address the explanation, X is not failing to enter the VT due to NVIDIA’s NULL MetaMode. It’s the Intel (modesetting) driver that is failing to enter the VT. It’s expected that NVIDIA would have a NULL MetaMode, since there are no displays connected to it. Our driver is pretty robust to head state changes – even if we have to fall back to a NULL MetaMode, we will still enter the VT successfully. The logs clearly show that the failure is originating from the Intel (modesetting) driver, not the NVIDIA driver. The relevant path in X is driver.c:EnterVT() => drmmode_display.c:drmmode_set_desired_modes(). In this function, the Intel driver tries to set a mode on each of the previously connected/enabled displays, and it tries to find the closest possible mode using xf86OutputFindClosestMode(). This is similar to our driver’s functionality, but unlike us, they don’t support a NULL fallback. If there are no modes supported on one of the displays, it simply fails, which causes X to terminate: DisplayModePtr mode = xf86OutputFindClosestMode(output, pScrn->currentMode); if (!mode) return FALSE; Since we removed one of the displays via the dock, it fails. It doesn’t matter if the internal panel is still available, Intel will fail if it can’t re-enable ANY of the previously connected displays. Technically the modesetting driver isn’t specifically an Intel driver, it’s a generic driver that can be used by any DRM device – it’s just that Intel has chosen to use the modesetting driver as their standard Linux X driver going forward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1897530/+subscriptions -- Mailing list: https://launch
[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
@Hui Wang Thank you so much for your help. Unfortunately now I got another problem. I upgraded to Ubuntu 20.10 with kernel 5.8.0-28 and now the driver doesn't compile, there is a fatal error, on 20.04 with kernel 5.4.0.53 there was no errors. I opened an issue here https://github.com/rtlwifi-linux/rtlwifi-next/issues/18 , but honestly I don't know if someone reads that forum. ** Bug watch added: github.com/rtlwifi-linux/rtlwifi-next/issues #18 https://github.com/rtlwifi-linux/rtlwifi-next/issues/18 -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1903211] Re: Computer freezes randomly after unsuspending
Thank you Brian...thats the one. Hoping someone can advise what the issue might be, and how i might be able to resolve. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1903211 Title: Computer freezes randomly after unsuspending Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: After unsuspending Ubuntu 20.04 the PC feezes for long periods of time. A look at HTOP shows a CPU core locking (i have 8 cores), and the command /var/log/syslog indicates that there is excessive logging happening...like hundreds of logs per second. I have tried blacklisting the nouveau driver and installing NVIDIA but that caused other problems in that my PC could not boot up, presumably due to incorrect NVIDIA settings. So now i just make sure the PC does not suspend, and when it does i have to restart to use the PC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1903211/+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 1903936] Re: Update to 1.58
Updated to snapd-glib 1.58-0ubuntu0.20.04.0 on focal and all dependencies are working. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1903936 Title: Update to 1.58 Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Bionic: Fix Committed Status in snapd-glib source package in Focal: Fix Committed Status in snapd-glib source package in Groovy: Fix Committed Status in snapd-glib source package in Hirsute: Fix Released Bug description: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Changes to error message carry low risk of introducing an issue if such an error occurred. GIR annotation changes fix a call that was previously broken, and is unlikely to make that any worse. Risks are mitigated by automatic regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1903936/+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 1888505] Re: Two-finger touchpad zoom extremely sensitive
I'm sorry about that: I misunderstood you. It's good that you commented, because I installed LO 7 from snap and it's still broken. I open Calc, a new spreadsheet, scroll up or down, sometimes it works, sometimes it stalls and then starts working again. I open Draw, hold and scroll on the touchpad (two-finger scroll) and Zoom in/out is extremely sensitive. -- 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/1888505 Title: Two-finger touchpad zoom extremely sensitive Status in libreoffice package in Ubuntu: New Bug description: Open Calc -> + Expected behaviour: document viewpan zooms/unzooms at a reasonable speed Observed behaviour: document viewpan zooms/unzooms from maximum zoom in to maximum zoom out in maybe 10-15% of the height of the touchpad, i.e. it is unusably oversensitive. Also affects Draw and Writer, 100% reproducible. Other apps (Firefox, Eye of Gnome/Image viewer) behave as expected (very usable zoom/unzoom sensitivity). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-core 1:6.0.7-0ubuntu0.18.04.10 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 14:43:20 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-05-10 (804 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2020-03-04 (140 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1888505/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Recently i bought both: 1Mii B10 and Avantree Leaf Quick review of them on my Ubuntu 16.04 64bit - plug and play -> both OK, no issues - audio quality with mic enabled -> bad bad bad, no significantly different than using pc bluetooth Therefore... there is no solution, apart from wired headset -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button
Still happens, Focal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-themes-extra in Ubuntu. https://bugs.launchpad.net/bugs/1861558 Title: Snap 'ed applicaitons have garbage on top of the window Close [x] button Status in adwaita-icon-theme package in Ubuntu: Confirmed Status in gnome-themes-extra package in Ubuntu: Confirmed Status in humanity-icon-theme package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in ubuntu-mono package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 19.10 installed 2. Install GNOME application as a Snap - for example with sudo snap install gedit gnome-calculator 3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the one of the following: * Adwaita * DMZ-Black * DMZ-White * hicolor * HighContrast * Humanity * Humanity-Dark * LoginIcons For example - Adwaita theme with Adwaita icon set. 4. Open GNOME Calculator as a Snap application: /snap/bin/gnome-calculator Expected result: * GNOME Calculator looks as any other GTK application Actual result: * GNOME Calculator has garbage on top of the window Close [x] button --- Notes: 1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868 2. one can use the script below to check all possible Theme<->Icon combinations: ``` #!/bin/bash DISPLAY=:0 for t in $(ls -1 /usr/share/themes/) do for i in $(ls -1 /usr/share/icons/) do echo -e "\nTheme: $t, Icons: $i\n" gsettings set org.gnome.desktop.interface gtk-theme "$t" gsettings set org.gnome.desktop.interface icon-theme "$i" /snap/bin/gnome-calculator #read -r -s -p "Press for next theme" done done ``` ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: snapd 2.41+19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 1 17:55:09 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+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 1587154] Re: --working-directory does not work anymore
Anyone in the "works for me" choir: you're missing the point; it DOES NOT work if and when the user has set the "Run custom command" option for gnome-terminal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1587154 Title: --working-directory does not work anymore Status in gnome-terminal package in Ubuntu: Fix Released Bug description: After upgrading from ubuntu 14.04 to 16.04 one of my script the uses --working-directory option stopped working. Simply running: gnome-terminal --working-directory=/tmp Starts the terminal in my home directory. Changing the command to gnome-terminal.real does not solve my problem either. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1587154/+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 1587154] Re: --working-directory does not work anymore
Anyone in the "works for me" choir: you're missing the point; it DOES BOT work if and when the user has set the "Run custom command" option for gnome-terminal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1587154 Title: --working-directory does not work anymore Status in gnome-terminal package in Ubuntu: Fix Released Bug description: After upgrading from ubuntu 14.04 to 16.04 one of my script the uses --working-directory option stopped working. Simply running: gnome-terminal --working-directory=/tmp Starts the terminal in my home directory. Changing the command to gnome-terminal.real does not solve my problem either. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1587154/+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 1903936] Re: Update to 1.58
Updated to snapd-glib 1.58-0ubuntu0.20.10.0 on groovy and all dependencies are working. ** Tags removed: verification-needed-groovy ** Tags added: verification-dine-groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1903936 Title: Update to 1.58 Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Bionic: Fix Committed Status in snapd-glib source package in Focal: Fix Committed Status in snapd-glib source package in Groovy: Fix Committed Status in snapd-glib source package in Hirsute: Fix Released Bug description: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Changes to error message carry low risk of introducing an issue if such an error occurred. GIR annotation changes fix a call that was previously broken, and is unlikely to make that any worse. Risks are mitigated by automatic regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1903936/+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 1904622] [NEW] boto3+s3 bucket fails
Public bug reported: I have a duplicity job that runs on multiple hosts, and am now having failures on my 20.04 hosts. The syntax for the job (as I am currently testing to debug) is: duplicity --dry-run list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Using the duplicity packages from focal/main duplicity=0.8.11.1612-1 And I installed the boto packages from focal/universe python3-boto3=1.9.253-1 python3-botocore=1.14.14+repack-1 This runs into the error: Using temporary directory $tmpDir/duplicity-iyhq3se4-tempdir Traceback (innermost last): File "/usr/bin/duplicity", line 106, in with_tempdir(main) File "/usr/bin/duplicity", line 92, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1525, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1175, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 85, in __init__ self.reset_connection() File "/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 96, in reset_connection self.s3.meta.client.head_bucket(Bucket=self.bucket_name) File "/home/ubuntu/.local/lib/python3.8/site-packages/botocore/client.py", line 357, in _api_call return self._make_api_call(operation_name, kwargs) File "/home/ubuntu/.local/lib/python3.8/site-packages/botocore/client.py", line 676, in _make_api_call raise error_class(parsed_response, operation_name) botocore.exceptions.ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden I then tried the duplicity snap from the snap store, both the stable and edge builds, with the same issue: Main action: list-current duplicity 0.8.17 Args: /snap/duplicity/138/bin/duplicity --dry-run --ignore-errors list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Linux duplicity 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 x86_64 x86_64 /snap/duplicity/141/usr/bin/python3 3.6.9 (default, Oct 8 2020, 12:12:24) [GCC 8.4.0] Attempt 1 failed. ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden Main action: list-current duplicity 0.8.18.dev11 Args: /snap/duplicity/141/bin/duplicity --dry-run --ignore-errors list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Linux duplicity 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 x86_64 x86_64 /snap/duplicity/141/usr/bin/python3 3.6.9 (default, Oct 8 2020, 12:12:24) [GCC 8.4.0] Attempt 1 failed. ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden I also tried to update the boto3/botocore packages by way of pip3: pip3 freeze | grep boto boto3==1.16.19 botocore==1.19.19 And lastly as a last ditch, I tried to pull the packages from the groovy/universe repo, bringing them to: python3-boto3 1.13.14-1 python3-botocore 1.17.22+repack-1_all I have also tried in a 20.10 system as well to see if any changes there, but same results. Hoping for something I can look at to get this back working as it was in 18.04 since 14.04. For good measure, I verified in a bionic build that using the same arguments as above with duplicity=0.7.17 python-boto=2.44.0-1ubuntu2.18.04.1 I then verified by uninstalling the deb and installing the snap (0.8.17) on bionic that the behavior stays the same. And just to satisfy the 1-4 guidelines: 1. The main system I am having issues with: $ lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 Also tested against $ lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 $ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 2. $ apt-cache policy duplicity duplicity: Installed: 0.8.11.1612-1 Candidate: 0.8.11.1612-1 Version table:
[Desktop-packages] [Bug 1634264] Re: package nvidia-opencl-icd-340 340.96-0ubuntu3.16.04.1 failed to install/upgrade: Es gibt kein Skript in der neuen Version des Paketes - Abbruch
** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1634264 Title: package nvidia-opencl-icd-340 340.96-0ubuntu3.16.04.1 failed to install/upgrade: Es gibt kein Skript in der neuen Version des Paketes - Abbruch Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Bug description: During upgrade from 16.04 to 16.10 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: nvidia-opencl-icd-340 340.98-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.96 Sun Nov 8 22:33:28 PST 2015 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Oct 17 20:59:24 2016 Dependencies: gcc-6-base 6.2.0-5ubuntu12 libc6 2.24-3ubuntu1 libgcc1 1:6.2.0-5ubuntu12 ocl-icd-libopencl1 2.2.9-1 DistUpgraded: 2016-10-17 19:22:46,511 DEBUG running apport_crash() DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-43-generic, x86_64: installed bbswitch, 0.8, 4.8.0-25-generic, x86_64: installed nvidia-340, 340.98, 4.4.0-43-generic, x86_64: installed nvidia-340, 340.98, 4.8.0-25-generic, x86_64: installed vboxhost, 5.0.26, 4.4.0-43-generic, x86_64: installed ErrorMessage: Es gibt kein Skript in der neuen Version des Paketes - Abbruch GraphicsCard: NVIDIA Corporation GT218M [GeForce G 105M] [10de:0a68] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd GT218M [GeForce G 105M] [144d:c059] InstallationDate: Installed on 2015-08-02 (442 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: SAMSUNG ELECTRONICS CO., LTD. R519/R719 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=4663cb1b-fbfc-4ac9-9216-5514fef2ff43 ro quiet splash acpi_osi=Linux acpi_backlight=vendor ht=on RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-opencl-icd-340 340.96-0ubuntu3.16.04.1 failed to install/upgrade: Es gibt kein Skript in der neuen Version des Paketes - Abbruch UpgradeStatus: Upgraded to yakkety on 2016-10-17 (0 days ago) dmi.bios.date: 11/24/2009 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 07CI.M052.20091124.JIP dmi.board.name: R519/R719 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr07CI.M052.20091124.JIP:bd11/24/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnR519/R719:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR519/R719:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R519/R719 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Mon Oct 17 12:44:50 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xs
[Desktop-packages] [Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward
Hello, thank you for releasing the Bugfix 340.108-0ubuntu5.20.10.2. I have tested it on my system and it works fine! I have installed this package via the proposed way: * "Enabling Pre-released updates" in the developers tab * Activate the Nvidia-Driver in the "Additional Drivers" section My System: * GT218M (GeForce G 105M) * Ubuntu 20.04 * uname -a: Linux eifx-laptop 5.8.0-29-generic #31-Ubuntu SMP Fri Nov 6 12:37:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 onward Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Groovy: Fix Committed Bug description: SRU request: [Impact] * Installing the 340 driver will fail when running Linux 5.7 or newer. [Test Case] * Install nvidia-340 from -proposed. * Check that the modules was built and installed, using the following command: dkms status [Regression Potential] * The driver once built and installed could be not working and lead to have the desktop not starting for example. Check that you get a desktop loaded and decent performances Hi developers, thanks for your great work on porting legacy drivers to Ubuntu. Anyway I have to complain in not seeing Nvidia 340.108 driver for kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4, because Nvidia 340.108 fails to install with kernels 5.5 and 5.6. Archlinux already has a driver for Kernel 5.6 via AUR (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has one for kernel 5.5. So, the question is: when will we see a new version in repositories? Bye and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+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 1903936] Autopkgtest regression report (snapd-glib/1.58-0ubuntu0.20.04.0)
All autopkgtests for the newly accepted snapd-glib (1.58-0ubuntu0.20.04.0) for focal have finished running. The following regressions have been reported in tests triggered by the package: software-properties/0.98.9.3 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#snapd-glib [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1903936 Title: Update to 1.58 Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Bionic: Fix Committed Status in snapd-glib source package in Focal: Fix Committed Status in snapd-glib source package in Groovy: Fix Committed Status in snapd-glib source package in Hirsute: Fix Released Bug description: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Changes to error message carry low risk of introducing an issue if such an error occurred. GIR annotation changes fix a call that was previously broken, and is unlikely to make that any worse. Risks are mitigated by automatic regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1903936/+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 1888505] Re: Two-finger touchpad zoom extremely sensitive
I was not suggesting to switch to the snap, just try to install it to confirm if the updated version really resolve the issue for you (one advantage of snaps is that they don't change anything on your system so if you install/try/uninstall you will basically be to the original state) -- 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/1888505 Title: Two-finger touchpad zoom extremely sensitive Status in libreoffice package in Ubuntu: New Bug description: Open Calc -> + Expected behaviour: document viewpan zooms/unzooms at a reasonable speed Observed behaviour: document viewpan zooms/unzooms from maximum zoom in to maximum zoom out in maybe 10-15% of the height of the touchpad, i.e. it is unusably oversensitive. Also affects Draw and Writer, 100% reproducible. Other apps (Firefox, Eye of Gnome/Image viewer) behave as expected (very usable zoom/unzoom sensitivity). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-core 1:6.0.7-0ubuntu0.18.04.10 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 14:43:20 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-05-10 (804 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2020-03-04 (140 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1888505/+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 1904616] Re: after upgrade analog audio output vanished
alsa-info can be found at http://alsa- project.org/db/?f=74fbad0c2c33a8e98de238a5cb713a3acdab9eb6 -- 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/1904616 Title: after upgrade analog audio output vanished Status in pulseaudio package in Ubuntu: New Bug description: after an upgrade from 20.04 to 20.10 the analog audio output vanished. in pavucontrol there is no corresponding profile available for the built-in audio in the configuration tab. additional info: > aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 > pacmd list-cards 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xb123 irq 140" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1f.3" sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "02c8" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: input:analog-stereo: Analog Stereo Input (priority 65, available: no) output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: unknown) output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI) Output + Analog Stereo Input (priority 5965, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-stereo-extra1+input:analog-stereo: Digital Stereo (HDMI 2) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround-extra1+input:analog-stereo: Digital Surround 5.1 (HDMI 2) Output + Analog Stereo Input (priority 665, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1+input:analog-stereo: Digital Surround 7.1 (HDMI 2) Output + Analog Stereo Input (priority 665, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-stereo-extra2+input:analog-stereo: Digital Stereo (HDMI 3) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-stereo-extra3: Digital Stereo (HDMI 4) Output (priority 5700, available: no) output:hdmi-stereo-extra3+input:analog-stereo: Digital Stereo (HDMI 4) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra3: Digital Surround 5.1 (HDMI 4) Output (priority 600, available: no) output:hdmi-surround71-extra3: Digital Surround 7.1 (HDMI 4) Output (priority 600, available: no) output:hdmi-stereo-extra4: Digital Stereo (HDMI 5) Output (priority 5700, available: no) output:hdmi-stereo-extra4+input:analog-stereo: Digital Stereo (HDMI 5) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra4: Digital Surround 5.1 (HDMI 5) Output (priority 600, available: no) output:hdmi-surround71-extra4: Digital Surround 7.1 (HDMI 5) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: sinks: alsa_output.pci-_00_1f.3.hdmi-stereo/#0: Built-in Audio Digital Stereo (HDMI)
[Desktop-packages] [Bug 1904616] [NEW] after upgrade analog audio output vanished
Public bug reported: after an upgrade from 20.04 to 20.10 the analog audio output vanished. in pavucontrol there is no corresponding profile available for the built-in audio in the configuration tab. additional info: > aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 > pacmd list-cards 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xb123 irq 140" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1f.3" sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "02c8" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: input:analog-stereo: Analog Stereo Input (priority 65, available: no) output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: unknown) output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI) Output + Analog Stereo Input (priority 5965, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-stereo-extra1+input:analog-stereo: Digital Stereo (HDMI 2) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround-extra1+input:analog-stereo: Digital Surround 5.1 (HDMI 2) Output + Analog Stereo Input (priority 665, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1+input:analog-stereo: Digital Surround 7.1 (HDMI 2) Output + Analog Stereo Input (priority 665, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-stereo-extra2+input:analog-stereo: Digital Stereo (HDMI 3) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-stereo-extra3: Digital Stereo (HDMI 4) Output (priority 5700, available: no) output:hdmi-stereo-extra3+input:analog-stereo: Digital Stereo (HDMI 4) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra3: Digital Surround 5.1 (HDMI 4) Output (priority 600, available: no) output:hdmi-surround71-extra3: Digital Surround 7.1 (HDMI 4) Output (priority 600, available: no) output:hdmi-stereo-extra4: Digital Stereo (HDMI 5) Output (priority 5700, available: no) output:hdmi-stereo-extra4+input:analog-stereo: Digital Stereo (HDMI 5) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra4: Digital Surround 5.1 (HDMI 5) Output (priority 600, available: no) output:hdmi-surround71-extra4: Digital Surround 7.1 (HDMI 5) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: sinks: alsa_output.pci-_00_1f.3.hdmi-stereo/#0: Built-in Audio Digital Stereo (HDMI) sources: alsa_output.pci-_00_1f.3.hdmi-stereo.monitor/#0: Monitor of Built-in Audio Digital Stereo (HDMI) ports: analog-input-mic: Microphone (priority 8700, latency offset 0 usec, available: no) properties: device.icon_name = "audio-input-microphone" hdmi-output-0: HDMI / DisplayPort (priority
[Desktop-packages] [Bug 1900167] Re: gnome-software Unable to install updates
screenshot ** Attachment added: "Screenshot from 2020-11-17 19-34-54.png" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1900167/+attachment/5435209/+files/Screenshot%20from%202020-11-17%2019-34-54.png -- 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/1900167 Title: gnome-software Unable to install updates Status in gnome-software package in Ubuntu: Incomplete Bug description: Click on 'Updates' and then on 'Restart & Update' I have a message: Unable to install updates: GDBus.error... Prepared update not found:/var/lib/PackageKit/prepared-update corrado@corrado-x2-gg-1009:~$ apt policy gnome-software gnome-software: Installed: 3.38.0-2build1 Candidate: 3.38.0-2build1 Version table: *** 3.38.0-2build1 500 500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-x2-gg-1009:~$ inxi -Fx System: Host: corrado-x2-gg-1009 Kernel: 5.8.0-23-generic x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: N/A Distro: Ubuntu 20.10 (Groovy Gorilla) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Info: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.2.0 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-8:4 Sound Server: ALSA v: k5.8.0-23-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives: Local Storage: total: 2.05 TiB used: 9.42 GiB (0.4%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 9.41 GiB (30.1%) fs: ext4 dev: /dev/nvme0n1p2 Swap: ID-1: swap-1 type: partition size: 8.00 GiB used: 0 KiB (0.0%) dev: /dev/sda2 Sensors: System Temperatures: cpu: 43.5 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 224 Uptime: 3h 13m Memory: 7.48 GiB used: 1.66 GiB (22.2%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1874 Shell: Bash v: 5.0.17 inxi: 3.1.07 corrado@corrado-x2-gg-1009:~$ ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-software 3.38.0-2build1 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 16 18:20:00 2020 InstallationDate: Installed on 2020-10-10 (6 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201009.1) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.38.0-2build1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1900167/+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 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
The KeePassXC and Stretchly snaps were not running under Wayland on Groovy. The mutter 3.38.1-2ubuntu1 package from groovy-proposed fixed the issue so that both of these snaps work again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) Status in Mutter: Unknown Status in snapd: In Progress Status in mutter package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Won't Fix Status in mutter source package in Groovy: Fix Committed Status in snapd source package in Groovy: Won't Fix Status in mutter source package in Hirsute: Fix Released Status in snapd source package in Hirsute: Won't Fix Bug description: [Impact] * Users who select the Wayland session on Ubuntu 20.10 cannot run snap confined X11 applications, due to gnome-shell no longer listening on an abstract socket for connections. * The fix, which has been accepted into upstream's gnome-3-38 branch reverts the change removing the abstract socket, and fixes the bug that prompted it's removal: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508 [Test Case] * Start with a stock Ubuntu 20.10 desktop install. * At the GDM login screen, after selecting your user account use the gear icon to select the "Ubuntu on Wayland" session, and log in. * Ensure Chromium is installed by running "sudo snap install chromium". * Try to run "chromium" from the terminal. Without the fix, it will fail with the error "Unable to open X display". With the fix applied, it will launch as normal. [Regression Potential] * The patch modifies the logic gnome-shell uses to launch Xwayland. So there is a potential that the change could break X11 application support on the Wayland session. * The default configuration for gnome-shell is to launch Xwayland on session start, so it should be immediately obvious if there are problems. * In addition to checking snapped X11 apps like Chromium, verify that a few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc). [Other Info] * Running "ss -xlp | grep Xwayland" should show that it is listening on both "/tmp/.X11-unix/X0" (the regular unix domain socket) and "@/tmp/.X11-unix/X0" (the abstract socket). --- I'm trying to run chromium installed via snap in Ubuntu 20.10 when running Ubuntu Wayland session. Unfortunately, chromium wouldn't start: > chromium [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to open X display. I am able to run Firefox just fine (assuming that Firefox still runs on xwayland) and also Intellij snap works fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu47 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 09:45:16 2020 InstallationDate: Installed on 2016-09-05 (1480 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Snap: chromium 85.0.4183.121 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+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 1888505] Re: Two-finger touchpad zoom extremely sensitive
@Sebastien I don't have an easy way to boot 20.04 for the moment and I'm unlikely to upgrade to 20.04 any time soon. As for a snap, that might work, although it feels a bit like a zero-sum game: you can have a working touchpad or normal root filesystem access, but not both...I'll see what I can do, thanks for the suggestions! -- 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/1888505 Title: Two-finger touchpad zoom extremely sensitive Status in libreoffice package in Ubuntu: New Bug description: Open Calc -> + Expected behaviour: document viewpan zooms/unzooms at a reasonable speed Observed behaviour: document viewpan zooms/unzooms from maximum zoom in to maximum zoom out in maybe 10-15% of the height of the touchpad, i.e. it is unusably oversensitive. Also affects Draw and Writer, 100% reproducible. Other apps (Firefox, Eye of Gnome/Image viewer) behave as expected (very usable zoom/unzoom sensitivity). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-core 1:6.0.7-0ubuntu0.18.04.10 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 14:43:20 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-05-10 (804 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2020-03-04 (140 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1888505/+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 1900167] Re: gnome-software Unable to install updates
This is the log you requested but the system crached when i selected 'Restart & update' so probably the log needed is the preceding one. ** Attachment added: "journalctl -b 0 > b1900167.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1900167/+attachment/5435207/+files/b1900167.txt -- 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/1900167 Title: gnome-software Unable to install updates Status in gnome-software package in Ubuntu: Incomplete Bug description: Click on 'Updates' and then on 'Restart & Update' I have a message: Unable to install updates: GDBus.error... Prepared update not found:/var/lib/PackageKit/prepared-update corrado@corrado-x2-gg-1009:~$ apt policy gnome-software gnome-software: Installed: 3.38.0-2build1 Candidate: 3.38.0-2build1 Version table: *** 3.38.0-2build1 500 500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-x2-gg-1009:~$ inxi -Fx System: Host: corrado-x2-gg-1009 Kernel: 5.8.0-23-generic x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: N/A Distro: Ubuntu 20.10 (Groovy Gorilla) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Info: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.2.0 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-8:4 Sound Server: ALSA v: k5.8.0-23-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives: Local Storage: total: 2.05 TiB used: 9.42 GiB (0.4%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 9.41 GiB (30.1%) fs: ext4 dev: /dev/nvme0n1p2 Swap: ID-1: swap-1 type: partition size: 8.00 GiB used: 0 KiB (0.0%) dev: /dev/sda2 Sensors: System Temperatures: cpu: 43.5 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 224 Uptime: 3h 13m Memory: 7.48 GiB used: 1.66 GiB (22.2%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1874 Shell: Bash v: 5.0.17 inxi: 3.1.07 corrado@corrado-x2-gg-1009:~$ ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-software 3.38.0-2build1 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 16 18:20:00 2020 InstallationDate: Installed on 2020-10-10 (6 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201009.1) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.38.0-2build1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1900167/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
or could some one point me where to find some information how to use the patches? -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
https://wiki.gentoo.org/wiki/Bluetooth_headset "If you do not want to use PulseAudio, you can use bluez-alsa to provide integration between Bluez and ALSA. " Did someone tried that on ubuntu? -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1903936] Please test proposed package
Hello Robert, or anyone else affected, Accepted snapd-glib into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/snapd- glib/1.58-0ubuntu0.20.04.0 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1903936 Title: Update to 1.58 Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Bionic: Fix Committed Status in snapd-glib source package in Focal: Fix Committed Status in snapd-glib source package in Groovy: Fix Committed Status in snapd-glib source package in Hirsute: Fix Released Bug description: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Changes to error message carry low risk of introducing an issue if such an error occurred. GIR annotation changes fix a call that was previously broken, and is unlikely to make that any worse. Risks are mitigated by automatic regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1903936/+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 1903936] Re: Update to 1.58
Hello Robert, or anyone else affected, Accepted snapd-glib into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/snapd- glib/1.58-0ubuntu0.20.10.0 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-groovy ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1903936 Title: Update to 1.58 Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Bionic: Fix Committed Status in snapd-glib source package in Focal: Fix Committed Status in snapd-glib source package in Groovy: Fix Committed Status in snapd-glib source package in Hirsute: Fix Released Bug description: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Changes to error message carry low risk of introducing an issue if such an error occurred. GIR annotation changes fix a call that was previously broken, and is unlikely to make that any worse. Risks are mitigated by automatic regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1903936/+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 1904602] [NEW] Strange crash of Software Properties
Public bug reported: After adding some repositories and the sources got reloaded, I wanted to add more repo's, so I had launched the Software Properties again, but instead of the app, I saw only this with is in the attached file. Ubuntu version: 20.04 and above (it does apply also to the same version of lUbuntu) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Attachment added: "unusual application behaviour" https://bugs.launchpad.net/bugs/1904602/+attachment/5435192/+files/Screenshot%20from%202020-11-17%2017-28-17.png ** Description changed: After adding some repositories and the sources got reloaded, I wanted to add more repo's, so I had launched the Software Properties again, but instead of the app, I saw only this with is in the attached file. + + Ubuntu version: 20.04 and above (it does apply also to the same version + of lUbuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1904602 Title: Strange crash of Software Properties Status in software-properties package in Ubuntu: New Bug description: After adding some repositories and the sources got reloaded, I wanted to add more repo's, so I had launched the Software Properties again, but instead of the app, I saw only this with is in the attached file. Ubuntu version: 20.04 and above (it does apply also to the same version of lUbuntu) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1904602/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@gdi2k What we have in the Linux now is HFP with 8kHz encoding. All other platforms such as Windows, Android, Chromium, etc, supports HFP with 16kHZ encoding which is much much better quality. Sure, it's not like A2DP, but quality is very much acceptable to speak with someone. -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Different colleagues (with stationary computer, thinkpads and me with an msi ) tried it, but everyone did get the same error message. -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Sorry that screenshot, failed and I cant edit my post, here is the screenshot: https://imgur.com/flypHpz -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@gyhor For the 1Mii B10 it specifically lists Linux support, see here: https://1mii.com/product-item/b10/ For me when I plug it in is shows up as a sound output device, screenshot (Ubuntu 20.04): https://imgur.com/a/gmToEL3 -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1904597] [NEW] Minimizing a fullscreen window causes Graphical issues
Public bug reported: Upon minimizing or tabbing out of a fullscreen window, the cursor will lag behind, and other applications will slow drastically. I have an AMD 5700XT and I believe the included driver is causing the issue but I am not certain. I am using ubuntu 20.04 lts ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1904597 Title: Minimizing a fullscreen window causes Graphical issues Status in gnome-shell package in Ubuntu: New Bug description: Upon minimizing or tabbing out of a fullscreen window, the cursor will lag behind, and other applications will slow drastically. I have an AMD 5700XT and I believe the included driver is causing the issue but I am not certain. I am using ubuntu 20.04 lts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904597/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I bought the 1Mii and tried to connect it. Unfortunately without success. Ubuntu don't recognize it: [ 6308.630984] usb 3-1.1.3: new full-speed USB device number 10 using xhci_hcd [ 6308.631134] usb 3-1.1.3: Device not responding to setup address. [ 6308.839133] usb 3-1.1.3: Device not responding to setup address. [ 6309.051064] usb 3-1.1.3: device not accepting address 10, error -71 [ 6309.251079] usb 3-1.1.3: new full-speed USB device number 11 using xhci_hcd [ 6309.251188] usb 3-1.1.3: Device not responding to setup address. [ 6309.459244] usb 3-1.1.3: Device not responding to setup address. [ 6309.667097] usb 3-1.1.3: device not accepting address 11, error -71 [ 6309.667245] usb 3-1.1-port3: unable to enumerate USB device -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1902710] Re: [SRU] Enable support for Wallaby Cloud Archive
This bug was fixed in the package software-properties - 0.98.9.3 --- software-properties (0.98.9.3) focal; urgency=medium * cloudarchive: Enable support for the Wallaby Ubuntu Cloud Archive on 20.04 (LP: #1902710). -- Corey Bryant Tue, 03 Nov 2020 09:08:24 -0500 ** Changed in: software-properties (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1902710 Title: [SRU] Enable support for Wallaby Cloud Archive Status in software-properties package in Ubuntu: Fix Committed Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Hirsute: Fix Committed Bug description: Please add support for: cloud-archive:wallaby cloud-archive:wallaby-proposed This will also need to be SRU'd back to focal. [Impact] End users have to manually enable the wallaby cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:wallaby sudo add-apt-repository cloud-archive:wallaby-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1902710/+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 1597708] Re: [HP EliteDesk 800 G1 DM, Realtek ALC221, Black Mic, Front] Duplex mac/headphone port does not produce sound.
I had try too in ubuntu 20.10 and doesn`t work ** Attachment added: "alsa-info-2010.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1597708/+attachment/5435181/+files/alsa-info-2010.txt -- 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/1597708 Title: [HP EliteDesk 800 G1 DM, Realtek ALC221, Black Mic, Front] Duplex mac/headphone port does not produce sound. Status in alsa-driver package in Ubuntu: Confirmed Bug description: The duplex mic/headphone port does not produce any sound. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-59.66~14.04.1-generic 3.19.8-ckt19 Uname: Linux 3.19.0-59-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tuomov 6588 F pulseaudio /dev/snd/pcmC1D0p: tuomov 6588 F...m pulseaudio /dev/snd/controlC1: tuomov 6588 F pulseaudio CurrentDesktop: Unity Date: Thu Jun 30 11:50:45 2016 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tuomov 6588 F pulseaudio /dev/snd/pcmC1D0p: tuomov 6588 F...m pulseaudio /dev/snd/controlC1: tuomov 6588 F pulseaudio Symptom_Jack: Black Mic, Front Symptom_Type: No sound at all Title: [HP EliteDesk 800 G1 DM, Realtek ALC221, Black Mic, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L04 v02.22 dmi.board.asset.tag: 1019155 dmi.board.name: 1825 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 1019155 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL04v02.22:bd07/16/2015:svnHewlett-Packard:pnHPEliteDesk800G1DM:pvr:rvnHewlett-Packard:rn1825:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.name: HP EliteDesk 800 G1 DM dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.modprobe.d.alsa.base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-06-28T14:28:35.250807 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1597708/+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 1904470] Re: 100Hz monitor fails to wake after lock
** 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/1904470 Title: 100Hz monitor fails to wake after lock Status in xorg package in Ubuntu: New Bug description: When set to 100Hz the monitor will work without issues until the machine is locked. When i want to unlock it the scrren does not wake up. The only way to wake up the screen is to unplug the HDMI cable from the GPU and plug it in again. This issue does not happen on 60Hz. This issue is present on both 20.04.1 LTS and 20.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1904470/+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 1904469] Re: History of Ubuntu missing from grub
** Package changed: ubuntu => zsys (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1904469 Title: History of Ubuntu missing from grub Status in zsys package in Ubuntu: New Bug description: When using Ubuntu (both 20.04.1 LTS and 20.10) with ZFS the "History of Ubuntu" entry is missing from GRUB. This may be caused by having multiple OS's on the machine. GRUB shows: Ubuntu 20.04.1 LTS - boots ubuntu Advanced options for Ubuntu 20.04.1 - Kernel selection Windows boot manager - boots windows UEFI firmware configuration - BIOS Windows and Ubuntu are on two different SSD's. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1904469/+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 1904545] Re: ZFS rollback does not do anything
** Package changed: ubuntu => zsys (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1904545 Title: ZFS rollback does not do anything Status in zsys package in Ubuntu: New Bug description: On Ubuntu 20.04.1 LTS as well as Ubuntu 20.10 rolling back a zfs snapshot does nothing. Tested rolling back autozsys as well as a manual snapshot. The rollback command does not return any error but does not rollback a snapshot. May be related to Bug #1904469 as a secondary symptom of the same issue but then again maybe not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1904545/+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 1904469] [NEW] History of Ubuntu missing from grub
You have been subscribed to a public bug: When using Ubuntu (both 20.04.1 LTS and 20.10) with ZFS the "History of Ubuntu" entry is missing from GRUB. This may be caused by having multiple OS's on the machine. GRUB shows: Ubuntu 20.04.1 LTS - boots ubuntu Advanced options for Ubuntu 20.04.1 - Kernel selection Windows boot manager - boots windows UEFI firmware configuration - BIOS Windows and Ubuntu are on two different SSD's. ** Affects: zsys (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- History of Ubuntu missing from grub https://bugs.launchpad.net/bugs/1904469 You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys 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 1904470] [NEW] 100Hz monitor fails to wake after lock
You have been subscribed to a public bug: When set to 100Hz the monitor will work without issues until the machine is locked. When i want to unlock it the scrren does not wake up. The only way to wake up the screen is to unplug the HDMI cable from the GPU and plug it in again. This issue does not happen on 60Hz. This issue is present on both 20.04.1 LTS and 20.10. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- 100Hz monitor fails to wake after lock https://bugs.launchpad.net/bugs/1904470 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 1904545] [NEW] ZFS rollback does not do anything
You have been subscribed to a public bug: On Ubuntu 20.04.1 LTS as well as Ubuntu 20.10 rolling back a zfs snapshot does nothing. Tested rolling back autozsys as well as a manual snapshot. The rollback command does not return any error but does not rollback a snapshot. May be related to Bug #1904469 as a secondary symptom of the same issue but then again maybe not. ** Affects: zsys (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- ZFS rollback does not do anything https://bugs.launchpad.net/bugs/1904545 You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys 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 1855009] Re: autopkgtests all fail on s390x
** Changed in: network-manager (Ubuntu Xenial) Assignee: Dan Streetman (ddstreet) => (unassigned) -- 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/1855009 Title: autopkgtests all fail on s390x Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in network-manager source package in Bionic: Fix Released Status in network-manager source package in Disco: Won't Fix Status in network-manager source package in Eoan: Fix Released Status in network-manager source package in Focal: Fix Released Bug description: [impact] all autopkgtests fail on s390x [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/n/network- manager/20191130_001946_a5512@/log.gz autopkgtest [00:19:32]: summary wpa-dhclient FAIL non-zero exit status 1 nm.pyFAIL non-zero exit status 1 killswitches-no-urfkill FAIL non-zero exit status 1 urfkill-integration FAIL non-zero exit status 1 [regression potential] this essentially skips all the autopkgtests for network-manager on s390x, so regressions could occur now or in the future due to lack of testing on s390x. However, all the tests already fail on s390x and have since xenial (or earlier), so there hasn't been any useful test coverage on s390x before; this doesn't change that. [other info] as mentioned in comment 2, wireless networking is specifically excluded on s390 systems: menuconfig WIRELESS bool "Wireless" depends on !S390 default y The 'wpa-dhclient' test is specific to wireless, and both 'killswitches-no-urfkill' and 'urfkill-integration' require rfkill which requires wireless, so none of those tests are valid on s390x, since it doesn't have any wireless support. However the 'nm.py' test does have some test cases that don't rely on wireless capability, but it would be much more intrusive to update the test to split out wired vs. wireless testing, and that might introduce test regressions on other archs. The use case for network-manager on s390x in general is questionable, since s390x has no wireless support and obviously is never 'mobile', which are 2 main reasons to use network-manager instead of systemd-networkd. Additionally, all tests are currently skipped on armhf due to the requirement for machine isolation (and armhf tests run in containers), so s390x is not the first arch to simply skip all network-manager autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855009/+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 1903524] Re: System state with 'space' in name prevent update-grub to create menu entries in grub.cfg
This bug was fixed in the package zsys - 0.5.3
---
zsys (0.5.3) hirsute; urgency=medium
[ Jean-Baptiste Lallement ]
[ Didier Roche ]
* Prevent usage of forbidden characters (starting with -, spaces…) for state
names (LP: #1903524)
-- Didier Roche Tue, 17 Nov 2020 10:27:47 +0100
** Changed in: zsys (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zsys in Ubuntu.
https://bugs.launchpad.net/bugs/1903524
Title:
System state with 'space' in name prevent update-grub to create menu
entries in grub.cfg
Status in grub2 package in Ubuntu:
In Progress
Status in zsys package in Ubuntu:
Fix Released
Status in grub2 source package in Focal:
Triaged
Status in zsys source package in Focal:
Triaged
Status in grub2 source package in Groovy:
Triaged
Status in zsys source package in Groovy:
Triaged
Bug description:
From https://github.com/ubuntu/zsys/issues/169
Describe the bug
I did create few days ago a System state with a 'space' in the name :
"pool/ROOT/ubuntu_u7dn3s@Stable Plex"
server:~$ zsysctl show
Name: rpool/ROOT/ubuntu_u7dn3s
ZSys: true
Last Used: current
History:
- Name: rpool/ROOT/ubuntu_u7dn3s@autozsys_ceqh6a
Created on: 2020-10-16 06:49:59
- Name: rpool/ROOT/ubuntu_u7dn3s@autozsys_ahzb7l
Created on: 2020-10-15 06:40:13
- Name: rpool/ROOT/ubuntu_u7dn3s@autozsys_a00j2k
Created on: 2020-10-08 06:46:34
- Name: rpool/ROOT/ubuntu_u7dn3s@autozsys_b7t6lj
Created on: 2020-10-07 06:20:00
- Name: rpool/ROOT/ubuntu_u7dn3s@Stable Plex
Created on: 2020-10-03 19:18:18
- Name: rpool/ROOT/ubuntu_u7dn3s@autozsys_a81mbp
Created on: 2020-10-03 17:58:19
(truncated)...
I found myself in the impossibility to boot the server few days after as the
Grub menu had only the UEFI entry in it. No more entries for current kernel or
zsys history.
server:~$ cat /boot/grub/grub.cfg
...(truncated)
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/30_uefi-firmware ###
menuentry 'UEFI Firmware Settings' $menuentry_id_option 'uefi-firmware' {
fwsetup
}
### END /etc/grub.d/30_uefi-firmware ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
(truncated)...
After chrooting into the server, I tried to rebuild the menu with update-grub
and got a weird error message on ignoring datasets:
server:~$ update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: vmlinuz-5.4.0-48-generic in rpool/ROOT/ubuntu_25bi0j
Found initrd image: initrd.img-5.4.0-48-generic in rpool/ROOT/ubuntu_25bi0j
Found linux image: vmlinuz-5.4.0-42-generic in rpool/ROOT/ubuntu_25bi0j
Found initrd image: initrd.img-5.4.0-42-generic in rpool/ROOT/ubuntu_25bi0j
...(truncated)...
Found initrd image: initrd.img-5.4.0-42-generic in
rpool/ROOT/ubuntu_u7dn3s@autozsys_a81mbp
Warning: Failed to find a valid directory 'etc' for dataset
'rpool/ROOT/ubuntu_u7dn3s@Stable'. Ignoring
Warning: Ignoring rpool/ROOT/ubuntu_u7dn3s@Stable
filesystem 'Plex' cannot be mounted, unable to open the dataset
Adding boot menu entry for UEFI Firmware Settings
done
As a result the grub.cfg file was letf with only the UEFI entry.
To solve this issue, I had to delete the problematic state and reran
update-grub. I then was back to normal.
server:~$ zsysctl state remove 'Stable Plex' --system
ZSys is adding automatic system snapshot to GRUB menu
server:~$ update-grub
...(truncated)...
server:~$ cat /boot/grub/grub.cfg
...(truncated)
menuentry '* Ubuntu 20.04.1 LTS, with Linux 5.4.0-48-generic (recovery
mode)' --class ubuntu --class gnu-linux --class gnu --class os
${menuentry_id_option} 'gnulinux-rpool/ROOT/ubuntu_u7dn3s-5.4.0-48-generic' {
recordfail
load_video
insmod gzio
if [ "${grub_platform}" = xen ]; then insmod xzio; insmod
lzopio; fi
insmod part_gpt
insmod zfs
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root 9976c549b4d44f87
else
search --no-floppy --fs-uuid --set=root 9976c549b4d44f87
fi
echo Loading Linux 5.4.0-48-generic ...
linux /BOOT/ubuntu_u7dn3s@/vmlinuz-5.4.0-48-generic
root=ZFS=rpool/ROOT/ubuntu_u7dn3s ro recovery nomodeset dis_ucode_ldr
[Desktop-packages] [Bug 1902148] Re: [snap] launchers in app's dock menu do launch general LO
After some discussion weighing the pros/cons of removing the icons from the snap, we decided that it's best to keep the icons to keep the snap as close to the upstream package as possible. ** Tags removed: rls-ff-incoming -- 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/1902148 Title: [snap] launchers in app's dock menu do launch general LO Status in libreoffice package in Ubuntu: In Progress Status in libreoffice source package in Focal: New Bug description: LO 7.0.2 Ubuntu Focal 1) right-click on LO icon in dock (white LO icon which does launch the home page with apps and recent docs) 2) select e.g. Calc It does launch general LO (home page with apps and recent docs), not Calc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1902148/+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 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
** Changed in: gnome-settings-daemon (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-settings-daemon (Ubuntu Groovy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed Status in gdm: New Status in GNOME Settings Daemon: Unknown Status in gdm3 package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: In Progress Status in pam package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Won't Fix Status in pam source package in Bionic: Invalid Status in gdm3 source package in Focal: Confirmed Status in gnome-settings-daemon source package in Focal: New Status in pam source package in Focal: Invalid Status in gdm3 source package in Groovy: Confirmed Status in gnome-settings-daemon source package in Groovy: New Status in pam source package in Groovy: Invalid Bug description: the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons()
** Changed in: gnome-shell (Ubuntu Groovy) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Status in gnome-shell source package in Groovy: Confirmed Status in gnome-shell-extension-desktop-icons source package in Groovy: Confirmed Bug description: See also bug 1898910 --- Sorry, I missed what was happening when this crashed. I'll try to catch it next time. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 08:38:45 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/gnome-shell/libst-1.0.so g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+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 1902148] Re: [snap] launchers in app's dock menu do launch general LO
** Changed in: libreoffice (Ubuntu Focal) Assignee: (unassigned) => Heather Ellsworth (hellsworth) -- 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/1902148 Title: [snap] launchers in app's dock menu do launch general LO Status in libreoffice package in Ubuntu: In Progress Status in libreoffice source package in Focal: New Bug description: LO 7.0.2 Ubuntu Focal 1) right-click on LO icon in dock (white LO icon which does launch the home page with apps and recent docs) 2) select e.g. Calc It does launch general LO (home page with apps and recent docs), not Calc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1902148/+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 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
The solution is going to require sssd which started being used in focal, we are not going to do official updates to bionic ** Changed in: gdm3 (Ubuntu Bionic) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed Status in gdm: New Status in GNOME Settings Daemon: Unknown Status in gdm3 package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: In Progress Status in pam package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Won't Fix Status in pam source package in Bionic: Invalid Status in gdm3 source package in Focal: Confirmed Status in gnome-settings-daemon source package in Focal: New Status in pam source package in Focal: Invalid Status in gdm3 source package in Groovy: Confirmed Status in gnome-settings-daemon source package in Groovy: New Status in pam source package in Groovy: Invalid Bug description: the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899179] Re: autopkgtest (almost always) fails in bionic on ppc64el starting with 1.0.3
Marked "Won't Fix" for Bionic as per discussion in the Desktop Team meeting 2020-11-17. ** Changed in: xdg-desktop-portal (Ubuntu Bionic) Status: New => Won't Fix -- 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/1899179 Title: autopkgtest (almost always) fails in bionic on ppc64el starting with 1.0.3 Status in xdg-desktop-portal package in Ubuntu: Fix Released Status in xdg-desktop-portal source package in Bionic: Won't Fix Status in xdg-desktop-portal source package in Focal: Fix Released Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-bionic/bionic/ppc64el/x/xdg-desktop- portal/20200921_121654_3c330@/log.gz autopkgtest [12:16:41]: test gnome-desktop-testing: [--- Running test: xdg-desktop-portal/testdb.test # random seed: R02Sa8a2f882d5b075ef4489c354fb44d94b 1..3 # Start of db tests ok 1 /db/open ok 2 /db/serialize ok 3 /db/modify # End of db tests PASS: xdg-desktop-portal/testdb.test Running test: xdg-desktop-portal/test-doc-portal.test # random seed: R02S8cb58d429c0a974cbecf54d1746d684e outdir: /tmp/xdp-test-Q3WHR0 dbus-daemon[1202]: [session uid=1000 pid=1202] Activating service name='org.freedesktop.portal.Documents' requested by ':1.0' (uid=1000 pid=1200 comm="/usr/libexec/installed-tests/xdg-desktop-portal/te" label="unconfined") dbus-daemon[1202]: [session uid=1000 pid=1202] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.1' (uid=1000 pid=1207 comm="/usr/libexec/xdg-document-portal " label="unconfined") dbus-daemon[1202]: [session uid=1000 pid=1202] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore' dbus-daemon[1202]: [session uid=1000 pid=1202] Successfully activated service 'org.freedesktop.portal.Documents' 1..4 # Start of db tests ok 1 /db/create_doc path: /tmp/xdp-test-Q3WHR0/doc/387dfbb5/recursive-file ok 2 /db/recursive_doc ok 3 /db/create_docs ** xdg-desktop-portal:ERROR:tests/test-doc-portal.c:607:test_add_named: assertion failed (error == NULL): Can't open /tmp/xdp-test-Q3WHR0/doc/f7828134/add-named-1 (g-file-error-quark, 23) Bail out! xdg-desktop-portal:ERROR:tests/test-doc-portal.c:607:test_add_named: assertion failed (error == NULL): Can't open /tmp/xdp-test-Q3WHR0/doc/f7828134/add-named-1 (g-file-error-quark, 23) cleaning up pid 1202 FAIL: xdg-desktop-portal/test-doc-portal.test (Child process killed by signal 6) SUMMARY: total=2; passed=1; skipped=0; failed=1; user=0.0s; system=0.0s; maxrss=9600 autopkgtest [12:16:42]: test gnome-desktop-testing: ---] autopkgtest [12:16:42]: test gnome-desktop-testing: - - - - - - - - - - results - - - - - - - - - - gnome-desktop-testing FAIL non-zero exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1899179/+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 1899179] Re: autopkgtest (almost always) fails in bionic on ppc64el starting with 1.0.3
(rational is that it's an autopkgtest issue on LTS-1 and an arch which isn't really used for desktop, we are not going to invest in a fix but the test can be made to be skipped on the infra if it's problematic for other packages) -- 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/1899179 Title: autopkgtest (almost always) fails in bionic on ppc64el starting with 1.0.3 Status in xdg-desktop-portal package in Ubuntu: Fix Released Status in xdg-desktop-portal source package in Bionic: Won't Fix Status in xdg-desktop-portal source package in Focal: Fix Released Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-bionic/bionic/ppc64el/x/xdg-desktop- portal/20200921_121654_3c330@/log.gz autopkgtest [12:16:41]: test gnome-desktop-testing: [--- Running test: xdg-desktop-portal/testdb.test # random seed: R02Sa8a2f882d5b075ef4489c354fb44d94b 1..3 # Start of db tests ok 1 /db/open ok 2 /db/serialize ok 3 /db/modify # End of db tests PASS: xdg-desktop-portal/testdb.test Running test: xdg-desktop-portal/test-doc-portal.test # random seed: R02S8cb58d429c0a974cbecf54d1746d684e outdir: /tmp/xdp-test-Q3WHR0 dbus-daemon[1202]: [session uid=1000 pid=1202] Activating service name='org.freedesktop.portal.Documents' requested by ':1.0' (uid=1000 pid=1200 comm="/usr/libexec/installed-tests/xdg-desktop-portal/te" label="unconfined") dbus-daemon[1202]: [session uid=1000 pid=1202] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.1' (uid=1000 pid=1207 comm="/usr/libexec/xdg-document-portal " label="unconfined") dbus-daemon[1202]: [session uid=1000 pid=1202] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore' dbus-daemon[1202]: [session uid=1000 pid=1202] Successfully activated service 'org.freedesktop.portal.Documents' 1..4 # Start of db tests ok 1 /db/create_doc path: /tmp/xdp-test-Q3WHR0/doc/387dfbb5/recursive-file ok 2 /db/recursive_doc ok 3 /db/create_docs ** xdg-desktop-portal:ERROR:tests/test-doc-portal.c:607:test_add_named: assertion failed (error == NULL): Can't open /tmp/xdp-test-Q3WHR0/doc/f7828134/add-named-1 (g-file-error-quark, 23) Bail out! xdg-desktop-portal:ERROR:tests/test-doc-portal.c:607:test_add_named: assertion failed (error == NULL): Can't open /tmp/xdp-test-Q3WHR0/doc/f7828134/add-named-1 (g-file-error-quark, 23) cleaning up pid 1202 FAIL: xdg-desktop-portal/test-doc-portal.test (Child process killed by signal 6) SUMMARY: total=2; passed=1; skipped=0; failed=1; user=0.0s; system=0.0s; maxrss=9600 autopkgtest [12:16:42]: test gnome-desktop-testing: ---] autopkgtest [12:16:42]: test gnome-desktop-testing: - - - - - - - - - - results - - - - - - - - - - gnome-desktop-testing FAIL non-zero exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1899179/+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
