[Desktop-packages] [Bug 2051895] Re: Lenovo XT99 BT headset can't work in HFP profile
sponsor team, this is the debdiff for noble thx. ** Patch added: "pulseaudio_16.1+dfsg1-2ubuntu7.debdiff" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2051895/+attachment/5744050/+files/pulseaudio_16.1+dfsg1-2ubuntu7.debdiff ** Changed in: pulseaudio (Ubuntu Jammy) Status: New => In Progress ** Changed in: pulseaudio (Ubuntu Mantic) Status: New => In Progress ** Changed in: pulseaudio (Ubuntu Noble) Status: New => In Progress -- 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/2051895 Title: Lenovo XT99 BT headset can't work in HFP profile Status in HWE Next: New Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Jammy: In Progress Status in pulseaudio source package in Mantic: In Progress Status in pulseaudio source package in Noble: In Progress Bug description: [Summary] When use the ThinkPluse xt99 bluetooth head set to run the test com.canonical.certification::bluetooth/audio_record_playback, it cannot record the sound and playback. It seems this device cannot switch to Hand free mode in this platform. [Steps to reproduce] Connect the ThinkPluse xt99, use the Handfree mode, then try to record some voice. [Expected result] The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound. [Actual result] The bluetooth headset xt99 cannot work in the Handfree mode. [Failure rate] 100% [Impact] With the current Ubuntu 22.04 oem image, we try to connect the LENOVO XT99 bt headset and let it work in HFP mode, we select HFP profile from gnome sound-setting, but the microphone will not auto change to bt microphone and the bt output could not work too. So this BT headset could only work in A2DP mode with the current 22.04 OEM image. And we tried ubuntu 22.04 generic image, mantic image and noble image, none of them could make the headset work in HFP mode. [Fix] Cherry-pick a pulseaudio commit from upstream. [Test] Install the patched pulseaudio and reboot, connect to the LENOVO XT99 bt headset, select it to work in HFP mode, tested playback and capture, all worked well. [Where problems could occur] This change will impact bt headset negotiation process in the pulseaudio, so the possiblity of regression is limited to bt headset, it could make the bt headset fail to connect, but this possibility is very low, we tested the patch with different bt headset and bt speaker, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051895/+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 2051895] Re: Lenovo XT99 BT headset can't work in HFP profile
sponsor team, this is the debdiff for mantic thx. ** Patch added: "pulseaudio_16.1+dfsg1-2ubuntu5.debdiff" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2051895/+attachment/5744049/+files/pulseaudio_16.1+dfsg1-2ubuntu5.debdiff -- 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/2051895 Title: Lenovo XT99 BT headset can't work in HFP profile Status in HWE Next: New Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Jammy: In Progress Status in pulseaudio source package in Mantic: In Progress Status in pulseaudio source package in Noble: In Progress Bug description: [Summary] When use the ThinkPluse xt99 bluetooth head set to run the test com.canonical.certification::bluetooth/audio_record_playback, it cannot record the sound and playback. It seems this device cannot switch to Hand free mode in this platform. [Steps to reproduce] Connect the ThinkPluse xt99, use the Handfree mode, then try to record some voice. [Expected result] The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound. [Actual result] The bluetooth headset xt99 cannot work in the Handfree mode. [Failure rate] 100% [Impact] With the current Ubuntu 22.04 oem image, we try to connect the LENOVO XT99 bt headset and let it work in HFP mode, we select HFP profile from gnome sound-setting, but the microphone will not auto change to bt microphone and the bt output could not work too. So this BT headset could only work in A2DP mode with the current 22.04 OEM image. And we tried ubuntu 22.04 generic image, mantic image and noble image, none of them could make the headset work in HFP mode. [Fix] Cherry-pick a pulseaudio commit from upstream. [Test] Install the patched pulseaudio and reboot, connect to the LENOVO XT99 bt headset, select it to work in HFP mode, tested playback and capture, all worked well. [Where problems could occur] This change will impact bt headset negotiation process in the pulseaudio, so the possiblity of regression is limited to bt headset, it could make the bt headset fail to connect, but this possibility is very low, we tested the patch with different bt headset and bt speaker, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051895/+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 2051895] Re: Lenovo XT99 BT headset can't work in HFP profile
sponsor team, this is the debdiff for jammy thx. ** Description changed: [Summary] When use the ThinkPluse xt99 bluetooth head set to run the test com.canonical.certification::bluetooth/audio_record_playback, it cannot record the sound and playback. - It seems this device cannot switch to Hand free mode in this platform. + It seems this device cannot switch to Hand free mode in this platform. [Steps to reproduce] - Connect the ThinkPluse xt99, use the Handfree mode, then try to record some voice. + Connect the ThinkPluse xt99, use the Handfree mode, then try to record some voice. [Expected result] The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound. [Actual result] The bluetooth headset xt99 cannot work in the Handfree mode. [Failure rate] 100% + + + [Impact] + With the current Ubuntu 22.04 oem image, we try to connect the LENOVO + XT99 bt headset and let it work in HFP mode, we select HFP profile + from gnome sound-setting, but the microphone will not auto change to + bt microphone and the bt output could not work too. So this BT headset + could only work in A2DP mode with the current 22.04 OEM image. + + And we tried ubuntu 22.04 generic image, mantic image and noble image, + none of them could make the headset work in HFP mode. + + [Fix] + Cherry-pick a pulseaudio commit from upstream. + + [Test] + Install the patched pulseaudio and reboot, connect to the LENOVO XT99 + bt headset, select it to work in HFP mode, tested playback and capture, + all worked well. + + [Where problems could occur] + This change will impact bt headset negotiation process in the pulseaudio, + so the possiblity of regression is limited to bt headset, it could make + the bt headset fail to connect, but this possibility is very low, we tested + the patch with different bt headset and bt speaker, all worked well. ** Patch added: "pulseaudio_15.99.1+dfsg1-1ubuntu2.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2051895/+attachment/5744048/+files/pulseaudio_15.99.1+dfsg1-1ubuntu2.2.debdiff -- 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/2051895 Title: Lenovo XT99 BT headset can't work in HFP profile Status in HWE Next: New Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Jammy: In Progress Status in pulseaudio source package in Mantic: In Progress Status in pulseaudio source package in Noble: In Progress Bug description: [Summary] When use the ThinkPluse xt99 bluetooth head set to run the test com.canonical.certification::bluetooth/audio_record_playback, it cannot record the sound and playback. It seems this device cannot switch to Hand free mode in this platform. [Steps to reproduce] Connect the ThinkPluse xt99, use the Handfree mode, then try to record some voice. [Expected result] The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound. [Actual result] The bluetooth headset xt99 cannot work in the Handfree mode. [Failure rate] 100% [Impact] With the current Ubuntu 22.04 oem image, we try to connect the LENOVO XT99 bt headset and let it work in HFP mode, we select HFP profile from gnome sound-setting, but the microphone will not auto change to bt microphone and the bt output could not work too. So this BT headset could only work in A2DP mode with the current 22.04 OEM image. And we tried ubuntu 22.04 generic image, mantic image and noble image, none of them could make the headset work in HFP mode. [Fix] Cherry-pick a pulseaudio commit from upstream. [Test] Install the patched pulseaudio and reboot, connect to the LENOVO XT99 bt headset, select it to work in HFP mode, tested playback and capture, all worked well. [Where problems could occur] This change will impact bt headset negotiation process in the pulseaudio, so the possiblity of regression is limited to bt headset, it could make the bt headset fail to connect, but this possibility is very low, we tested the patch with different bt headset and bt speaker, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051895/+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 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking
Thanks for the note. Just created merge requests on salsa instead. -- 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/2051074 Title: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking Status in HWE Next: New Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: New Status in mutter source package in Mantic: New Status in mutter source package in Noble: Fix Committed Bug description: [Impact] On systems equipped with reduced blanking panel, mirror mode can result to no image on external monitor. The reason is due to current fallback modes don't have pixelclock for reduced blanking, so inadequate refresh rate is used to mode set, and result with atomic commit failure. [Fix] https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3449 Add reduced blanking (RB) to fallback modes, so mutter can use RB mode to meet pixelclock requirement in order to pick the right refresh rate. [Test] Connect an external monitor to affected system. Use the monitor hotkey to switch to mirror mode or use GNOME control center to choose mirror mode. With the patch included, the issue is no longer observed. [Where problems could occur] The modelines of reduced blanking have reversed Hsync and Vsync flags, so if the driver doesn't handle those flags correctly, the atomic modeset/commit may fail. I haven't observe any issue on Intel/AMD/Nvidia GPU so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051074/+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 1958019]
(In reply to Lukas from comment #814) > (In reply to Jacob Garby from comment #813) > > I have a "Lenovo Legion Slim 7i 16", and several days ago, out of nowhere, > > the speaker started working. I have no idea how -- I did not change > anything > > manually. I suspect it's a new kernel version that did it. > > > > I'm on Arch Linux, and I can't remember which kernel version I have > > installed (but I can update when I get home later today). > > > > Anyway, good news! > > Amazing > > I would like to reproduce this. You can find out your current kernel version > with the command "uname -r". The installed sound packages/libs would also be > interesting. What I know of would be to look at the alsa version. > Someone else surely has more information on what to specificly look for and > how. Yep! I'll post this kind of info before the end of today, check back in a few hours. I can tell you now that the speakers first started working when using pulseaudio as my sound server, but soon after (in order to get bluetooth working nicer) I switched to pipewire. -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
(In reply to Jacob Garby from comment #813) > I have a "Lenovo Legion Slim 7i 16", and several days ago, out of nowhere, > the speaker started working. I have no idea how -- I did not change anything > manually. I suspect it's a new kernel version that did it. > > I'm on Arch Linux, and I can't remember which kernel version I have > installed (but I can update when I get home later today). > > Anyway, good news! Amazing I would like to reproduce this. You can find out your current kernel version with the command "uname -r". The installed sound packages/libs would also be interesting. What I know of would be to look at the alsa version. Someone else surely has more information on what to specificly look for and how. -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
I have a "Lenovo Legion Slim 7i 16", and several days ago, out of nowhere, the speaker started working. I have no idea how -- I did not change anything manually. I suspect it's a new kernel version that did it. I'm on Arch Linux, and I can't remember which kernel version I have installed (but I can update when I get home later today). Anyway, good news! -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 2051895] Re: Lenovo XT99 BT headset can't work in HFP profile
** Also affects: pulseaudio (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu Jammy) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu Mantic) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu Noble) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu Jammy) Assignee: (unassigned) => Hui Wang (hui.wang) ** Tags added: oem-priority originate-from-2045342 sutton -- 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/2051895 Title: Lenovo XT99 BT headset can't work in HFP profile Status in HWE Next: New Status in pulseaudio package in Ubuntu: New Status in pulseaudio source package in Jammy: New Status in pulseaudio source package in Mantic: New Status in pulseaudio source package in Noble: New Bug description: [Summary] When use the ThinkPluse xt99 bluetooth head set to run the test com.canonical.certification::bluetooth/audio_record_playback, it cannot record the sound and playback. It seems this device cannot switch to Hand free mode in this platform. [Steps to reproduce] Connect the ThinkPluse xt99, use the Handfree mode, then try to record some voice. [Expected result] The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound. [Actual result] The bluetooth headset xt99 cannot work in the Handfree mode. [Failure rate] 100% To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051895/+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 2051895] Re: Lenovo XT99 BT headset can't work in HFP profile
** Package changed: linux-oem-6.1 (Ubuntu) => pulseaudio (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/2051895 Title: Lenovo XT99 BT headset can't work in HFP profile Status in HWE Next: New Status in pulseaudio package in Ubuntu: New Status in pulseaudio source package in Jammy: New Status in pulseaudio source package in Mantic: New Status in pulseaudio source package in Noble: New Bug description: [Summary] When use the ThinkPluse xt99 bluetooth head set to run the test com.canonical.certification::bluetooth/audio_record_playback, it cannot record the sound and playback. It seems this device cannot switch to Hand free mode in this platform. [Steps to reproduce] Connect the ThinkPluse xt99, use the Handfree mode, then try to record some voice. [Expected result] The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound. [Actual result] The bluetooth headset xt99 cannot work in the Handfree mode. [Failure rate] 100% To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051895/+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 2051895] [NEW] Lenovo XT99 BT headset can't work in HFP profile
You have been subscribed to a public bug: [Summary] When use the ThinkPluse xt99 bluetooth head set to run the test com.canonical.certification::bluetooth/audio_record_playback, it cannot record the sound and playback. It seems this device cannot switch to Hand free mode in this platform. [Steps to reproduce] Connect the ThinkPluse xt99, use the Handfree mode, then try to record some voice. [Expected result] The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound. [Actual result] The bluetooth headset xt99 cannot work in the Handfree mode. [Failure rate] 100% ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- Lenovo XT99 BT headset can't work in HFP profile https://bugs.launchpad.net/bugs/2051895 You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio 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 2051894] [NEW] Cannot activate WWAN connection, repeatedly connects and disconnects very quickly
Public bug reported: I have a SIM installed and activated. If I boot into Windows I can verify connectivity works there. In Ubuntu I can see the connection. When I try to activate it, graphically it toggles on and off very quickly. mccli output is pasted below. I believe all the hardware is fully supported. This laptop can be ordered with Linux (Ubuntu 22.04 LTS) or Windows 10/11. It is a Lenovo ThinkPad z16 gen1 Additionally here's a screen cap of what I'm seeing in the UI https://photos.app.goo.gl/bsoQbF7KPC9zLufr6 # mmcli -m 0 -- General | path: /org/freedesktop/ModemManager1/Modem/0 | device id: 06d0e7ce8f0a51e2ae17d0340ef10fe5c0e7794e -- Hardware | manufacturer: Intel | model: MBIM [8086:7560] | firmware revision: 18601.5001.00.01.16.35_TM | h/w revision: V1.3 | supported: gsm-umts, lte |current: gsm-umts, lte | equipment id: 016175005936119 -- System | device: /sys/devices/pci:00/:00:01.3/:05:00.0 |drivers: iosm | plugin: Intel | primary port: wwan0mbim0 | ports: wwan0 (net), wwan0at0 (at), wwan0at1 (at), wwan0mbim0 (mbim) -- Numbers |own: 16318330089ËFsÿ -- Status | unlock retries: sim-pin (3) | state: disabled |power state: low -- Modes| supported: allowed: 3g, 4g; preferred: none |current: allowed: 3g, 4g; preferred: none -- IP | supported: ipv4, ipv6, ipv4v6 -- 3GPP | imei: 016175005936119 | enabled locks: fixed-dialing | packet service state: detached -- 3GPP EPS | ue mode of operation: csps-2 | initial bearer ip type: ipv4v6 -- SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 | sim slot paths: slot 1: /org/freedesktop/ModemManager1/SIM/0 (active) | slot 2: /org/freedesktop/ModemManager1/SIM/1 -- # journalctl -f -u NetworkManager.service Jan 31 20:32:10 nickh-ThinkPad-Z16 NetworkManager[1115]: [1706754730.2611] policy: auto-activating connection 'Google-Fi' (05250c1d-91b1-420c-99ec-f922b318a83d) Jan 31 20:32:10 nickh-ThinkPad-Z16 NetworkManager[1115]: [1706754730.2614] device (wwan0mbim0): Activation: starting connection 'Google-Fi' (05250c1d-91b1-420c-99ec-f922b318a83d) Jan 31 20:32:10 nickh-ThinkPad-Z16 NetworkManager[1115]: [1706754730.2614] device (wwan0mbim0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Jan 31 20:32:10 nickh-ThinkPad-Z16 NetworkManager[1115]: [1706754730.2781] device (wwan0mbim0): state change: prepare -> disconnected (reason 'user-requested', sys-iface-state: 'managed') Jan 31 20:32:10 nickh-ThinkPad-Z16 NetworkManager[1115]: [1706754730.2787] policy: auto-activating connection 'Google-Fi' (05250c1d-91b1-420c-99ec-f922b318a83d) Jan 31 20:32:10 nickh-ThinkPad-Z16 NetworkManager[1115]: [1706754730.2791] device (wwan0mbim0): Activation: starting connection 'Google-Fi' (05250c1d-91b1-420c-99ec-f922b318a83d) Jan 31 20:32:10 nickh-ThinkPad-Z16 NetworkManager[1115]: [1706754730.2791] device (wwan0mbim0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Jan 31 20:32:10 nickh-ThinkPad-Z16 NetworkManager[1115]: [1706754730.2795] device (wwan0mbim0): state change: prepare -> deactivating (reason 'user-requested', sys-iface-state: 'managed') Jan 31 20:32:10 nickh-ThinkPad-Z16 NetworkManager[1115]: [1706754730.2797] audit: op="device-disconnect" interface="wwan0mbim0" pid=3422 uid=1000 result="success" Jan 31 20:32:10 nickh-ThinkPad-Z16 NetworkManager[1115]: [1706754730.3267] device (wwan0mbim0): state change: deactivating -> disconnected (reason 'user-requested', sys-iface-state: 'managed') ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: modemmanager 1.20.6-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 31 20:27:22 2024 InstallationDate: Installed on 2024-01-30 (1 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user)
[Desktop-packages] [Bug 1999320] Re: Font alignment issue in search bar when using scaling factor > 1
** Tags added: noble -- 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/1999320 Title: Font alignment issue in search bar when using scaling factor > 1 Status in gnome-shell package in Ubuntu: Confirmed Bug description: When I use a desktop interface text scaling factor of 1.5, the alignment text in the applications menu search bar is not set properly I have attached a screenshot showing the issue. 1) Description: Ubuntu 22.04.1 LTS Release: 22.04 2) xorg: Installed: 1:7.7+23ubuntu2 Candidate: 1:7.7+23ubuntu2 Version table: *** 1:7.7+23ubuntu2 500 500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 3) text was centered 4) it is not centered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1999320/+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 1999320] Re: Font alignment issue in search bar when using scaling factor > 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1999320 Title: Font alignment issue in search bar when using scaling factor > 1 Status in gnome-shell package in Ubuntu: Confirmed Bug description: When I use a desktop interface text scaling factor of 1.5, the alignment text in the applications menu search bar is not set properly I have attached a screenshot showing the issue. 1) Description: Ubuntu 22.04.1 LTS Release: 22.04 2) xorg: Installed: 1:7.7+23ubuntu2 Candidate: 1:7.7+23ubuntu2 Version table: *** 1:7.7+23ubuntu2 500 500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 3) text was centered 4) it is not centered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1999320/+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 2051870] Re: With font scaling, text in the GNOME Shell search box is cut off
*** This bug is a duplicate of bug 1999320 *** https://bugs.launchpad.net/bugs/1999320 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 1999320, 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. ** Package changed: yaru-theme (Ubuntu) => gnome-shell (Ubuntu) ** This bug has been marked a duplicate of bug 1999320 Font alignment issue in search bar when using scaling factor > 1 -- 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/2051870 Title: With font scaling, text in the GNOME Shell search box is cut off Status in gnome-shell package in Ubuntu: New Bug description: If you increase font scaling – either with Gnome Tweaks > Fonts > Scaling Factor or gsettings org.gnome.desktop.interface text-scaling- factor – text in the GNOME Shell search box is cut off. Text scaling can help with hidpi screens and is an accessibility feature. I noticed this a while ago but I finally got around to testing it systematically in December with the then-current noble daily build and reported it upstream (https://github.com/ubuntu/yaru/issues/4023). I today confirmed it's still present in an updated Noble install. The issue does not occur with the default GNOME/Adwaita Shell theme installed with gnome-session or other OSes like OpenSUSE Tumbleweed so it seems like a Yaru theme issue. My upstream bug report (https://github.com/ubuntu/yaru/issues/4023) has examples with screenshots. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: yaru-theme-gnome-shell 23.10.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 31 12:03:33 2024 Dependencies: InstallationDate: Installed on 2023-03-16 (321 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: yaru-theme UpgradeStatus: Upgraded to noble on 2023-12-08 (54 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051870/+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 2051855] Re: Mutter causes desktop to extend beyond screen, looks like 2140p on 1440p screen
Thanks for the bug report. Does the problem only occur after changing display settings? Does it resolve itself after a reboot? Please also attach a copy of $HOME/.config/monitors.xml ** Tags added: multimonitor ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- 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/2051855 Title: Mutter causes desktop to extend beyond screen, looks like 2140p on 1440p screen Status in mutter package in Ubuntu: Incomplete Bug description: Mutter causes desktop to extend beyond screen, looks like 2140p on 1440p screen. This appeared only after installing the latest update of the libmutter package. I am using 2x Samsung S27AG502NUXEN displays in extended desktop mode (join). So far the only fix i have found is holding back this package. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: libmutter-13-0 45.2-0ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 31 14:33:53 2024 InstallationDate: Installed on 2021-10-04 (849 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mutter UpgradeStatus: Upgraded to mantic on 2023-10-16 (107 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2051855/+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 2051543] Re: When I use a keyboard shortcut to lower a window, the window retains its keyboard focus.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
** Information type changed from Private Security to Public Security
--
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/2051543
Title:
When I use a keyboard shortcut to lower a window, the window retains
its keyboard focus.
Status in gnome-shell package in Ubuntu:
New
Bug description:
This happens no matter which focusing strategy i choose (click to
focus or hover to focus). Until a few weeks ago, the new top window
would receive focus when using hover to focus.
This can be a security risk in that you often start typing in the
wrong window.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 29 13:53:47 2024
DistUpgraded: 2023-10-24 00:16:21,014 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA
controller])
Subsystem: Lenovo HD Graphics 620 [17aa:224b]
InstallationDate: Installed on 2021-02-23 (1070 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=4fc71965-9660-4a7c-ada5-7906da430d47 ro quiet splash intel_iommu=off
vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-10-23 (98 days ago)
dmi.bios.date: 08/15/2023
dmi.bios.release: 1.51
dmi.bios.vendor: LENOVO
dmi.bios.version: N1WET72W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HF004UMD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.22
dmi.modalias:
dmi:bvnLENOVO:bvrN1WET72W(1.51):bd08/15/2023:br1.51:efr1.22:svnLENOVO:pn20HF004UMD:pvrThinkPadT470s:rvnLENOVO:rn20HF004UMD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HF_BU_Think_FM_ThinkPadT470s:
dmi.product.family: ThinkPad T470s
dmi.product.name: 20HF004UMD
dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
dmi.product.version: ThinkPad T470s
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2021-02-23 (1072 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
Package: gnome-shell 45.2-0ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: mutter-common 45.2-0ubuntu3
Tags: mantic
Uname: Linux 6.5.0-14-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-23 (99 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lpadmin lxd plugdev
sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051543/+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 1971434] Re: Display powersave only blanks, but does not turn off
The MUTTER_DEBUG_ENABLE_ATOMIC_KMS worked for me as well, thank you! -- 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/1971434 Title: Display powersave only blanks, but does not turn off Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-07-04 (667 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: gnome-settings-daemon 42.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers video wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+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 2051886] [NEW] Unable to move windows by dragging the title bar on GTK4 Xorg with touchscreens
Public bug reported: https://gitlab.gnome.org/GNOME/gtk/-/issues/5610 cross posting this here since it affects the majority of Ubuntu's UI applications in Ubuntu Noble (eg: settings) and is perceived as a regression by users from Ubuntu Jammy where the majority of applications are GTK3 based. This is a confirmed GTK4 bug (not mutter) and affects all releases of GTK4 on all DEs/compositors (eg: Gnome with Mutter, KDE with KWin, Unity with compiz) Hoping to have a ubuntu developer look into this regression since the upstream bug report has existed for almost 1 year with no action from gnome. ** Affects: gtk4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2051886 Title: Unable to move windows by dragging the title bar on GTK4 Xorg with touchscreens Status in gtk4 package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/gtk/-/issues/5610 cross posting this here since it affects the majority of Ubuntu's UI applications in Ubuntu Noble (eg: settings) and is perceived as a regression by users from Ubuntu Jammy where the majority of applications are GTK3 based. This is a confirmed GTK4 bug (not mutter) and affects all releases of GTK4 on all DEs/compositors (eg: Gnome with Mutter, KDE with KWin, Unity with compiz) Hoping to have a ubuntu developer look into this regression since the upstream bug report has existed for almost 1 year with no action from gnome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2051886/+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 2039021] Re: NO-GUI headless convert-to function error in 7.6.1.2 60(Build:2)
** Changed in: df-libreoffice Status: Fix Released => Confirmed ** Bug watch added: Debian Bug tracker #1058653 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058653 -- 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/2039021 Title: NO-GUI headless convert-to function error in 7.6.1.2 60(Build:2) Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: New Bug description: Original bug report to LibreOffice team: https://bugs.documentfoundation.org/show_bug.cgi?id=157424 7.6.1.2 60(Build:2) no-gui version, Ubuntu Server 20.04 LTS gives error. soffice --headless --convert-to pdf path/to/file --> Error: source file could not be loaded Ubuntu 20.04 LTS Desktop version has no error with the same version, only on Server. The installation difference is libreoffice vs libreoffice-nogui. Previous version doesent produces this error: 7.5.6.2 50(Build:2) work perfect. Lots of no-gui version fails in Ubuntu Server 20.04 LTS with "Error: source file could not be loaded" message. Specific examples: - LibreOffice 6.4.7.2 40(Build:2) --> Same error with xlsx with --convert-to html - LibreOffice 7.5.3.2 50(Build:2) --> Same error with xlsx with --convert-to html !!! Only LibreOffice 7.5.6.2 50(Build:2) works perfectly in both case. !!! Example outputs: soffice --headless --convert-to pdf teszt.docx convert /home/zsolt/teszt.docx -> /home/zsolt/teszt.pdf using filter : writer_pdf_Export soffice --headless --convert-to html teszt.xlsx convert /home/zsolt/teszt.xlsx -> /home/zsolt/teszt.html using filter : HTML (StarCalc) Fortunately *ppa:libreoffice/libreoffice-still* contains the good version so i had to change the repos in all servers To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/2039021/+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 2039021]
there's still [pid 1261847] openat(AT_FDCWD, "/usr/lib/libreoffice/program/libcuilo.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) in the strace and after installing libreoffice-core the conversion succeeds. -- 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/2039021 Title: NO-GUI headless convert-to function error in 7.6.1.2 60(Build:2) Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: New Bug description: Original bug report to LibreOffice team: https://bugs.documentfoundation.org/show_bug.cgi?id=157424 7.6.1.2 60(Build:2) no-gui version, Ubuntu Server 20.04 LTS gives error. soffice --headless --convert-to pdf path/to/file --> Error: source file could not be loaded Ubuntu 20.04 LTS Desktop version has no error with the same version, only on Server. The installation difference is libreoffice vs libreoffice-nogui. Previous version doesent produces this error: 7.5.6.2 50(Build:2) work perfect. Lots of no-gui version fails in Ubuntu Server 20.04 LTS with "Error: source file could not be loaded" message. Specific examples: - LibreOffice 6.4.7.2 40(Build:2) --> Same error with xlsx with --convert-to html - LibreOffice 7.5.3.2 50(Build:2) --> Same error with xlsx with --convert-to html !!! Only LibreOffice 7.5.6.2 50(Build:2) works perfectly in both case. !!! Example outputs: soffice --headless --convert-to pdf teszt.docx convert /home/zsolt/teszt.docx -> /home/zsolt/teszt.pdf using filter : writer_pdf_Export soffice --headless --convert-to html teszt.xlsx convert /home/zsolt/teszt.xlsx -> /home/zsolt/teszt.html using filter : HTML (StarCalc) Fortunately *ppa:libreoffice/libreoffice-still* contains the good version so i had to change the repos in all servers To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/2039021/+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 2039021]
no, sorry, the convert of gpredict (see http://bugs.debian.org/1058653) still fails with the patch applied -- 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/2039021 Title: NO-GUI headless convert-to function error in 7.6.1.2 60(Build:2) Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: New Bug description: Original bug report to LibreOffice team: https://bugs.documentfoundation.org/show_bug.cgi?id=157424 7.6.1.2 60(Build:2) no-gui version, Ubuntu Server 20.04 LTS gives error. soffice --headless --convert-to pdf path/to/file --> Error: source file could not be loaded Ubuntu 20.04 LTS Desktop version has no error with the same version, only on Server. The installation difference is libreoffice vs libreoffice-nogui. Previous version doesent produces this error: 7.5.6.2 50(Build:2) work perfect. Lots of no-gui version fails in Ubuntu Server 20.04 LTS with "Error: source file could not be loaded" message. Specific examples: - LibreOffice 6.4.7.2 40(Build:2) --> Same error with xlsx with --convert-to html - LibreOffice 7.5.3.2 50(Build:2) --> Same error with xlsx with --convert-to html !!! Only LibreOffice 7.5.6.2 50(Build:2) works perfectly in both case. !!! Example outputs: soffice --headless --convert-to pdf teszt.docx convert /home/zsolt/teszt.docx -> /home/zsolt/teszt.pdf using filter : writer_pdf_Export soffice --headless --convert-to html teszt.xlsx convert /home/zsolt/teszt.xlsx -> /home/zsolt/teszt.html using filter : HTML (StarCalc) Fortunately *ppa:libreoffice/libreoffice-still* contains the good version so i had to change the repos in all servers To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/2039021/+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 2039021]
Noel Grandin committed a patch related to this issue. It has been pushed to "libreoffice-7-6": https://git.libreoffice.org/core/commit/180da9297ba1e45cbb85debd40136f0281d45b97 tdf#158695 convert-to bogusly needs libcui (--disable-gui build) It will be available in 7.6.5. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- 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/2039021 Title: NO-GUI headless convert-to function error in 7.6.1.2 60(Build:2) Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: New Bug description: Original bug report to LibreOffice team: https://bugs.documentfoundation.org/show_bug.cgi?id=157424 7.6.1.2 60(Build:2) no-gui version, Ubuntu Server 20.04 LTS gives error. soffice --headless --convert-to pdf path/to/file --> Error: source file could not be loaded Ubuntu 20.04 LTS Desktop version has no error with the same version, only on Server. The installation difference is libreoffice vs libreoffice-nogui. Previous version doesent produces this error: 7.5.6.2 50(Build:2) work perfect. Lots of no-gui version fails in Ubuntu Server 20.04 LTS with "Error: source file could not be loaded" message. Specific examples: - LibreOffice 6.4.7.2 40(Build:2) --> Same error with xlsx with --convert-to html - LibreOffice 7.5.3.2 50(Build:2) --> Same error with xlsx with --convert-to html !!! Only LibreOffice 7.5.6.2 50(Build:2) works perfectly in both case. !!! Example outputs: soffice --headless --convert-to pdf teszt.docx convert /home/zsolt/teszt.docx -> /home/zsolt/teszt.pdf using filter : writer_pdf_Export soffice --headless --convert-to html teszt.xlsx convert /home/zsolt/teszt.xlsx -> /home/zsolt/teszt.html using filter : HTML (StarCalc) Fortunately *ppa:libreoffice/libreoffice-still* contains the good version so i had to change the repos in all servers To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/2039021/+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 2051875] [NEW] monitor goes to sleep (power save) mode as soon as the system attempts to display the graphical login screen. Attempting to switch to a character console wakes t
Public bug reported: https://askubuntu.com/questions/1500676/is-there-a-solution- for-22-04-and-kernel-6-5-0-14-or-6-5-0-15-22-04-for-users?noredirect=1 I'm running 22.04 LTS with an Asus NVidia GeForce GT 730. I'm using the Ubuntu provided video driver (Nouveau). Since upgrading my kernel to 6.5, I notice that my monitor goes to sleep (power save) mode as soon as the system attempts to display the graphical login screen. Attempting to switch to a character console wakes the monitor but I still have a blank screen. Switching back to the graphical login screen puts the monitor back to sleep. My current solution is to use my previous 6.2 kernel. I've been reading in the forums about users having problems with recompiling their driver source, gcc version mismatches v11 (6.2 kernel) vs v12 (6.5 kernel) and some driver source incompatibilities with the new compiler. I'm wondering how soon users might expect a fix for the stock driver or if we should expect a fix? I've got a 2nd Linux systems also 22.04 with a GT 610 that has no issues with the latest 6.5 kernel. The command dkms status returns nothing. And apt-cache policy gcc-12 returns gcc-12: Installed: (none) Candidate: 12.3.0-1ubuntu1~22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-video-nouveau 1:1.0.17-2build1 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error creating textual authentication agent: Error opening current controlling terminal for the process (`/dev/tty'): No such device or address Date: Wed Jan 31 11:18:16 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK208B [GeForce GT 730] [1043:881a] ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd ASPEED Graphics Family [1458:2000] InstallationDate: Installed on 2023-05-05 (271 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Cirrascale VB1416 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=UUID=8138fb3d-3187-4185-9154-470cb45cf4c4 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error creating textual authentication agent: Error opening current controlling terminal for the process (`/dev/tty'): No such device or address dmi.bios.date: 06/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: GIGABYTE dmi.bios.version: R17 dmi.board.asset.tag: 01234567890123456789AN dmi.board.name: GA-7PESH2 dmi.board.vendor: GIGABYTE dmi.board.version: 0001 dmi.chassis.asset.tag: 01234567890123456789AN dmi.chassis.type: 17 dmi.chassis.vendor: Cirrascale dmi.chassis.version: 240272-101 dmi.modalias: dmi:bvnGIGABYTE:bvrR17:bd06/26/2018:br4.6:svnCirrascale:pnVB1416:pvr0002:rvnGIGABYTE:rnGA-7PESH2:rvr0001:cvnCirrascale:ct17:cvr240272-101:sku: dmi.product.family: GIGABYTE Server dmi.product.name: VB1416 dmi.product.version: 0002 dmi.sys.vendor: Cirrascale version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- 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/2051875 Title: monitor goes to sleep (power save) mode as soon as the system attempts to display the graphical login screen. Attempting to switch to a character console wakes the monitor but I still have a blank screen. Switching back to the graphical login screen puts the monitor back to sleep. Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description:
[Desktop-packages] [Bug 2051870] [NEW] With font scaling, text in the GNOME Shell search box is cut off
Public bug reported: If you increase font scaling – either with Gnome Tweaks > Fonts > Scaling Factor or gsettings org.gnome.desktop.interface text-scaling- factor – text in the GNOME Shell search box is cut off. Text scaling can help with hidpi screens and is an accessibility feature. I noticed this a while ago but I finally got around to testing it systematically in December with the then-current noble daily build and reported it upstream (https://github.com/ubuntu/yaru/issues/4023). I today confirmed it's still present in an updated Noble install. The issue does not occur with the default GNOME/Adwaita Shell theme installed with gnome-session or other OSes like OpenSUSE Tumbleweed so it seems like a Yaru theme issue. My upstream bug report (https://github.com/ubuntu/yaru/issues/4023) has examples with screenshots. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: yaru-theme-gnome-shell 23.10.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 31 12:03:33 2024 Dependencies: InstallationDate: Installed on 2023-03-16 (321 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: yaru-theme UpgradeStatus: Upgraded to noble on 2023-12-08 (54 days ago) ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2051870 Title: With font scaling, text in the GNOME Shell search box is cut off Status in yaru-theme package in Ubuntu: New Bug description: If you increase font scaling – either with Gnome Tweaks > Fonts > Scaling Factor or gsettings org.gnome.desktop.interface text-scaling- factor – text in the GNOME Shell search box is cut off. Text scaling can help with hidpi screens and is an accessibility feature. I noticed this a while ago but I finally got around to testing it systematically in December with the then-current noble daily build and reported it upstream (https://github.com/ubuntu/yaru/issues/4023). I today confirmed it's still present in an updated Noble install. The issue does not occur with the default GNOME/Adwaita Shell theme installed with gnome-session or other OSes like OpenSUSE Tumbleweed so it seems like a Yaru theme issue. My upstream bug report (https://github.com/ubuntu/yaru/issues/4023) has examples with screenshots. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: yaru-theme-gnome-shell 23.10.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 31 12:03:33 2024 Dependencies: InstallationDate: Installed on 2023-03-16 (321 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: yaru-theme UpgradeStatus: Upgraded to noble on 2023-12-08 (54 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2051870/+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 1988754]
(In reply to Timur from comment #3) > Marked regression but repro also in 4.1, not consistently, but other time it > doesn't crash it will on 2nd Insert. Also repro in 43all oldest. So I remove > regression. Also crashed on second insert, after undo, in OOo 3.3, let's mark as inherited. -- 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/1988754 Title: libreoffice writer crashes when edit the page break Status in LibreOffice: In Progress Status in libreoffice package in Ubuntu: New Bug description: LibreOffice Writes crashes when editing the page break. It happens in Xubuntu 22.04.1 and also in LinuxMint 21. I have tried also using LibreOffice from ppa and it still crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1988754/+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 2051855] [NEW] Mutter causes desktop to extend beyond screen, looks like 2140p on 1440p screen
Public bug reported: Mutter causes desktop to extend beyond screen, looks like 2140p on 1440p screen. This appeared only after installing the latest update of the libmutter package. I am using 2x Samsung S27AG502NUXEN displays in extended desktop mode (join). So far the only fix i have found is holding back this package. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: libmutter-13-0 45.2-0ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 31 14:33:53 2024 InstallationDate: Installed on 2021-10-04 (849 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mutter UpgradeStatus: Upgraded to mantic on 2023-10-16 (107 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- 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/2051855 Title: Mutter causes desktop to extend beyond screen, looks like 2140p on 1440p screen Status in mutter package in Ubuntu: New Bug description: Mutter causes desktop to extend beyond screen, looks like 2140p on 1440p screen. This appeared only after installing the latest update of the libmutter package. I am using 2x Samsung S27AG502NUXEN displays in extended desktop mode (join). So far the only fix i have found is holding back this package. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: libmutter-13-0 45.2-0ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 31 14:33:53 2024 InstallationDate: Installed on 2021-10-04 (849 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mutter UpgradeStatus: Upgraded to mantic on 2023-10-16 (107 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2051855/+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 2051838] [NEW] /usr/libexec/gdm-wayland-session: Error: WaylandMessage::Write() too many files to send
Public bug reported: GDM, or more specifically is flooding systemd journal and /var/log/syslog via rsyslogd with gigabytes of the following messages: Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: Error: WaylandMessage::Write() too many files to send Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: : Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[283270]: Error: WaylandMessage::Write() too many files to send Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[283270]: : Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: Error: WaylandMessage::Write() too many files to send Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: : Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[283270]: Error: WaylandMessage::Write() too many files to send Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[283270]: : Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: Error: WaylandMessage::Write() too many files to send I noticed the problem when I started to run out of disk because /var/log/syslog was consuming more than 400GiB. I noticed that rsyslogd starts to consume a lot of CPU trying to process such volume of messages. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Affects: gdm3 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2051838 Title: /usr/libexec/gdm-wayland-session: Error: WaylandMessage::Write() too many files to send Status in gdm3 package in Ubuntu: New Status in gdm3 source package in Jammy: New Bug description: GDM, or more specifically is flooding systemd journal and /var/log/syslog via rsyslogd with gigabytes of the following messages: Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: Error: WaylandMessage::Write() too many files to send Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: : Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[283270]: Error: WaylandMessage::Write() too many files to send Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[283270]: : Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: Error: WaylandMessage::Write() too many files to send Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: : Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[283270]: Error: WaylandMessage::Write() too many files to send Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[283270]: : Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: Error: WaylandMessage::Write() too many files to send I noticed the problem when I started to run out of disk because /var/log/syslog was consuming more than 400GiB. I noticed that rsyslogd starts to consume a lot of CPU trying to process such volume of messages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2051838/+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 1424201] Re: Web browsers lacking hardware-accelerated video decoding
** Description changed: This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux browsers. We will close this bug when most browsers will have Va-api decoding working OOTB without user interaction like in WinOS and MacOS January 2024: - Quickest answer : Install firefox Flatpak https://flathub.org/fr/apps/org.mozilla.firefox - activate VAAPI with the flag media.ffmpeg.vaapi.enabled=true + activate VAAPI with the flag media.ffmpeg.vaapi.enabled=true - - Snap : still not ready + - Snap : Test in Progress - deb from mozilla : not tested. August 2022 : * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1 ) -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need to fix this as most youtube is AV1 now. * In july 2020, things are getting better : - Chromium : A patch is used on most distro packages. , more info here https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497 - Firefox : Firefox team has done a great job and now Va-api decoding in Wayland is possible and X11 is possible in nightly ! Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 * In 2015 I opened this bug , no easy solution was available and battery drained when playing video in browser was crazy. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Fix Released Status in chromium-browser package in Ubuntu: In Progress Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux browsers. We will close this bug when most browsers will have Va-api decoding working OOTB without user interaction like in WinOS and MacOS January 2024: - Quickest answer : Install firefox Flatpak https://flathub.org/fr/apps/org.mozilla.firefox activate VAAPI with the flag media.ffmpeg.vaapi.enabled=true - Snap : Test in Progress - deb from mozilla : not tested. August 2022 : * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1 ) -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need to fix this as most youtube is AV1 now. * In july 2020, things are getting better : - Chromium : A patch is used on most distro packages. , more info here https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1816497 - Firefox : Firefox team has done a great job and now Va-api decoding in Wayland is possible and X11 is possible in nightly ! Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 * In 2015 I opened this bug , no easy solution was available and battery drained when playing video in browser was crazy. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+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 1493964] Re: Gnome terminal scrollbars background is not themable
The downstream patch added by Ubuntu to address this issue is suspected to cause a crash, see lp:2049923. -- 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/1493964 Title: Gnome terminal scrollbars background is not themable Status in GNOME Terminal: Won't Fix Status in gnome-terminal package in Ubuntu: Fix Released Bug description: This is related to bug #1451924, however upstream proposed fix is not yet ready to use. Basically gnome-terminal provides a scroll bar which is boxed horizontally with the terminal itself, and currently the scrollbar background is not inherited from terminal itself, leading to a white background. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1493964/+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 2049923] Re: gnome-terminal freezing, then crashing
Found the option, will try with "Show scrollbar" DISABLED. -- 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/2049923 Title: gnome-terminal freezing, then crashing Status in gnome-terminal package in Ubuntu: New Bug description: First: It's very hard to reproduce, but it happens to me about once per week. If often open new windows or split windows out from tabs. And then it happens. First it becomes unresponsive, and then after about 2-3 seconds it simply closes all instances. [328830.780749] gnome-terminal-[117706]: segfault at 460742 ip 7fdb2fb45611 sp 7ffdb8c5fda0 error 4 in libgtk-3.so.0.2406.32[7fdb2f883000+38f000] likely on CPU 4 (core 4, socket 0) [328830.780761] Code: fb 48 83 ec 20 64 48 8b 04 25 28 00 00 00 48 89 44 24 18 31 c0 e8 bf 6d ff ff 48 85 db 74 7a 48 89 c6 48 8b 03 48 85 c0 74 05 <48> 39 30 74 0c 48 89 df e8 a2 c2 d4 ff 85 c0 74 5e 48 89 e6 48 89 [329377.925310] gnome-terminal-[120116]: segfault at 2f0774 ip 7f86af745611 sp 7ffc9943c5c0 error 4 in libgtk-3.so.0.2406.32[7f86af483000+38f000] likely on CPU 2 (core 2, socket 0) [329377.925324] Code: fb 48 83 ec 20 64 48 8b 04 25 28 00 00 00 48 89 44 24 18 31 c0 e8 bf 6d ff ff 48 85 db 74 7a 48 89 c6 48 8b 03 48 85 c0 74 05 <48> 39 30 74 0c 48 89 df e8 a2 c2 d4 ff 85 c0 74 5e 48 89 e6 48 89 unfortunately, apport isn't automatically creating a crash report. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-terminal 3.49.92-2ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 19 16:48:43 2024 SourcePackage: gnome-terminal UpgradeStatus: Upgraded to mantic on 2023-10-17 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2049923/+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 2049923] Re: gnome-terminal freezing, then crashing
"I suspect that toggling the scrollbar's visibility might eliminate this bug for you" -I'd like to try that, but where's that option hidden? As for dropping the patch: I could try rebuilding, but for the time being I'd prefer the other option. -- 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/2049923 Title: gnome-terminal freezing, then crashing Status in gnome-terminal package in Ubuntu: New Bug description: First: It's very hard to reproduce, but it happens to me about once per week. If often open new windows or split windows out from tabs. And then it happens. First it becomes unresponsive, and then after about 2-3 seconds it simply closes all instances. [328830.780749] gnome-terminal-[117706]: segfault at 460742 ip 7fdb2fb45611 sp 7ffdb8c5fda0 error 4 in libgtk-3.so.0.2406.32[7fdb2f883000+38f000] likely on CPU 4 (core 4, socket 0) [328830.780761] Code: fb 48 83 ec 20 64 48 8b 04 25 28 00 00 00 48 89 44 24 18 31 c0 e8 bf 6d ff ff 48 85 db 74 7a 48 89 c6 48 8b 03 48 85 c0 74 05 <48> 39 30 74 0c 48 89 df e8 a2 c2 d4 ff 85 c0 74 5e 48 89 e6 48 89 [329377.925310] gnome-terminal-[120116]: segfault at 2f0774 ip 7f86af745611 sp 7ffc9943c5c0 error 4 in libgtk-3.so.0.2406.32[7f86af483000+38f000] likely on CPU 2 (core 2, socket 0) [329377.925324] Code: fb 48 83 ec 20 64 48 8b 04 25 28 00 00 00 48 89 44 24 18 31 c0 e8 bf 6d ff ff 48 85 db 74 7a 48 89 c6 48 8b 03 48 85 c0 74 05 <48> 39 30 74 0c 48 89 df e8 a2 c2 d4 ff 85 c0 74 5e 48 89 e6 48 89 unfortunately, apport isn't automatically creating a crash report. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-terminal 3.49.92-2ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 19 16:48:43 2024 SourcePackage: gnome-terminal UpgradeStatus: Upgraded to mantic on 2023-10-17 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2049923/+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 2049923] Re: gnome-terminal freezing, then crashing
H trying to make sense of it...
There's hardly any code from gnome-terminal itself in the stack trace,
most of them is from GTK.
#10 is from update_color_scheme():
if (gdk_rgba_hash (>bg_color) != gdk_rgba_hash ())
{
priv->bg_color = bg;
g_object_notify (G_OBJECT (screen), "bg-color"); < this line
}
#0 gtk_widget_queue_draw() is called by #1 g_closure_invoke(), so the
former is called as a callback registered earlier. The only place where
this method can be registered as a callback is in
terminal_screen_container_constructed():
g_signal_connect_swapped (priv->screen, "notify::bg-color",
G_CALLBACK (gtk_widget_queue_draw),
priv->vscrollbar);
and it's indeed about the same "bg-color" signal, so I'm quite sure this
is where we are.
Now, this is not part of upstream gnome-terminal. It's added by Ubuntu's
"scrollbar-background-theming.patch", as per lp:1493964, which tries to
theme the scrollbar to match the terminal screen's main background
color.
I suspect that toggling the scrollbar's visibility might eliminate this
bug for you. Also, if you're familiar with recompiling Ubuntu packages
with tiny modifications, I'm fairly confident that dropping this patch
should fix the problem. Installed packages, modules, settings, whatnot
related to GTK scrollbars (e.g. choosing whether to use an overlay or
traditional one, etc.) might easily be relevant to whether this bug
occurs.
I'm not an Ubuntu developer, and I'm not affiliated with Ubuntu or
Launchpad. I'm a GNOME Terminal developer. At this point, I suspect with
99%+ certainity that upstream GNOME Terminal is not affected by the bug,
it's introduced by Ubuntu (or maybe Debian). Therefore I'm sorry but I'm
afraid I won't be able to help any further, the investigation and fixing
should be continued by Ubuntu devs.
--
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/2049923
Title:
gnome-terminal freezing, then crashing
Status in gnome-terminal package in Ubuntu:
New
Bug description:
First: It's very hard to reproduce, but it happens to me about once per week.
If often open new windows or split windows out from tabs. And then it
happens. First it becomes unresponsive, and then after about 2-3 seconds it
simply closes all instances.
[328830.780749] gnome-terminal-[117706]: segfault at 460742 ip
7fdb2fb45611 sp 7ffdb8c5fda0 error 4 in
libgtk-3.so.0.2406.32[7fdb2f883000+38f000] likely on CPU 4 (core 4, socket 0)
[328830.780761] Code: fb 48 83 ec 20 64 48 8b 04 25 28 00 00 00 48 89
44 24 18 31 c0 e8 bf 6d ff ff 48 85 db 74 7a 48 89 c6 48 8b 03 48 85
c0 74 05 <48> 39 30 74 0c 48 89 df e8 a2 c2 d4 ff 85 c0 74 5e 48 89 e6
48 89
[329377.925310] gnome-terminal-[120116]: segfault at 2f0774 ip
7f86af745611 sp 7ffc9943c5c0 error 4 in
libgtk-3.so.0.2406.32[7f86af483000+38f000] likely on CPU 2 (core 2,
socket 0)
[329377.925324] Code: fb 48 83 ec 20 64 48 8b 04 25 28 00 00 00 48 89
44 24 18 31 c0 e8 bf 6d ff ff 48 85 db 74 7a 48 89 c6 48 8b 03 48 85
c0 74 05 <48> 39 30 74 0c 48 89 df e8 a2 c2 d4 ff 85 c0 74 5e 48 89 e6
48 89
unfortunately, apport isn't automatically creating a crash report.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-terminal 3.49.92-2ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 19 16:48:43 2024
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to mantic on 2023-10-17 (94 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2049923/+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 2049923] Re: gnome-terminal freezing, then crashing
Here goes the backtrace - couldn't send it via email, since: The message you sent included commands to modify the bug report, but you didn't sign the message with an OpenPGP key that is registered in Launchpad. -- 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/2049923 Title: gnome-terminal freezing, then crashing Status in gnome-terminal package in Ubuntu: New Bug description: First: It's very hard to reproduce, but it happens to me about once per week. If often open new windows or split windows out from tabs. And then it happens. First it becomes unresponsive, and then after about 2-3 seconds it simply closes all instances. [328830.780749] gnome-terminal-[117706]: segfault at 460742 ip 7fdb2fb45611 sp 7ffdb8c5fda0 error 4 in libgtk-3.so.0.2406.32[7fdb2f883000+38f000] likely on CPU 4 (core 4, socket 0) [328830.780761] Code: fb 48 83 ec 20 64 48 8b 04 25 28 00 00 00 48 89 44 24 18 31 c0 e8 bf 6d ff ff 48 85 db 74 7a 48 89 c6 48 8b 03 48 85 c0 74 05 <48> 39 30 74 0c 48 89 df e8 a2 c2 d4 ff 85 c0 74 5e 48 89 e6 48 89 [329377.925310] gnome-terminal-[120116]: segfault at 2f0774 ip 7f86af745611 sp 7ffc9943c5c0 error 4 in libgtk-3.so.0.2406.32[7f86af483000+38f000] likely on CPU 2 (core 2, socket 0) [329377.925324] Code: fb 48 83 ec 20 64 48 8b 04 25 28 00 00 00 48 89 44 24 18 31 c0 e8 bf 6d ff ff 48 85 db 74 7a 48 89 c6 48 8b 03 48 85 c0 74 05 <48> 39 30 74 0c 48 89 df e8 a2 c2 d4 ff 85 c0 74 5e 48 89 e6 48 89 unfortunately, apport isn't automatically creating a crash report. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-terminal 3.49.92-2ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 19 16:48:43 2024 SourcePackage: gnome-terminal UpgradeStatus: Upgraded to mantic on 2023-10-17 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2049923/+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 2049923] Re: gnome-terminal freezing, then crashing
** Attachment added: "Backtrace" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2049923/+attachment/5743881/+files/backtrace.txt -- 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/2049923 Title: gnome-terminal freezing, then crashing Status in gnome-terminal package in Ubuntu: New Bug description: First: It's very hard to reproduce, but it happens to me about once per week. If often open new windows or split windows out from tabs. And then it happens. First it becomes unresponsive, and then after about 2-3 seconds it simply closes all instances. [328830.780749] gnome-terminal-[117706]: segfault at 460742 ip 7fdb2fb45611 sp 7ffdb8c5fda0 error 4 in libgtk-3.so.0.2406.32[7fdb2f883000+38f000] likely on CPU 4 (core 4, socket 0) [328830.780761] Code: fb 48 83 ec 20 64 48 8b 04 25 28 00 00 00 48 89 44 24 18 31 c0 e8 bf 6d ff ff 48 85 db 74 7a 48 89 c6 48 8b 03 48 85 c0 74 05 <48> 39 30 74 0c 48 89 df e8 a2 c2 d4 ff 85 c0 74 5e 48 89 e6 48 89 [329377.925310] gnome-terminal-[120116]: segfault at 2f0774 ip 7f86af745611 sp 7ffc9943c5c0 error 4 in libgtk-3.so.0.2406.32[7f86af483000+38f000] likely on CPU 2 (core 2, socket 0) [329377.925324] Code: fb 48 83 ec 20 64 48 8b 04 25 28 00 00 00 48 89 44 24 18 31 c0 e8 bf 6d ff ff 48 85 db 74 7a 48 89 c6 48 8b 03 48 85 c0 74 05 <48> 39 30 74 0c 48 89 df e8 a2 c2 d4 ff 85 c0 74 5e 48 89 e6 48 89 unfortunately, apport isn't automatically creating a crash report. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-terminal 3.49.92-2ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 19 16:48:43 2024 SourcePackage: gnome-terminal UpgradeStatus: Upgraded to mantic on 2023-10-17 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2049923/+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
Re: [Desktop-packages] [ext] [Bug 2049923] Re: gnome-terminal freezing, then crashing
* Egmont Koblinger <2049...@bugs.launchpad.net>: > > change to that new tab > > This is a no-op because the new tab is automatically swithed to, > correct? Indeed. > --- > > Are you on Wayland or X11? This command should answer it: > > echo $XDG_SESSION_TYPE $ echo $XDG_SESSION_TYPE x11 I could check with wayland if you like > I cannot reproduce the crash. The steps to reproduce are very simple, so > I believe we should have received more crash reports. There must be > something weird, unique going on in your machine, at least that's what I > suspect. > > Have you customized your shell prompt, for example? It might be > relevant. Nope. It's hildeb@vsw-it-nw-10:~$ username @ hostname > Or do you have unusually large or unusually small gnome- > terminal windows, or anything nontypical in the terminal's default > config? No, definitely not (site is about a quarter of the screen) > I'd like to see a stack trace of the crash. Could you please do the > following? Will work on that. Do I have to kill re-existing gnome-terminal-server processes? -- 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/2049923 Title: gnome-terminal freezing, then crashing Status in gnome-terminal package in Ubuntu: New Bug description: First: It's very hard to reproduce, but it happens to me about once per week. If often open new windows or split windows out from tabs. And then it happens. First it becomes unresponsive, and then after about 2-3 seconds it simply closes all instances. [328830.780749] gnome-terminal-[117706]: segfault at 460742 ip 7fdb2fb45611 sp 7ffdb8c5fda0 error 4 in libgtk-3.so.0.2406.32[7fdb2f883000+38f000] likely on CPU 4 (core 4, socket 0) [328830.780761] Code: fb 48 83 ec 20 64 48 8b 04 25 28 00 00 00 48 89 44 24 18 31 c0 e8 bf 6d ff ff 48 85 db 74 7a 48 89 c6 48 8b 03 48 85 c0 74 05 <48> 39 30 74 0c 48 89 df e8 a2 c2 d4 ff 85 c0 74 5e 48 89 e6 48 89 [329377.925310] gnome-terminal-[120116]: segfault at 2f0774 ip 7f86af745611 sp 7ffc9943c5c0 error 4 in libgtk-3.so.0.2406.32[7f86af483000+38f000] likely on CPU 2 (core 2, socket 0) [329377.925324] Code: fb 48 83 ec 20 64 48 8b 04 25 28 00 00 00 48 89 44 24 18 31 c0 e8 bf 6d ff ff 48 85 db 74 7a 48 89 c6 48 8b 03 48 85 c0 74 05 <48> 39 30 74 0c 48 89 df e8 a2 c2 d4 ff 85 c0 74 5e 48 89 e6 48 89 unfortunately, apport isn't automatically creating a crash report. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-terminal 3.49.92-2ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 19 16:48:43 2024 SourcePackage: gnome-terminal UpgradeStatus: Upgraded to mantic on 2023-10-17 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2049923/+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 1625773] Re: Segfault when using -w / --window to screenshot current window.
Can't make window screenshot either. Whole screen or part of the screen is fine, but window segfaults. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1625773 Title: Segfault when using -w / --window to screenshot current window. Status in gnome-screenshot package in Ubuntu: Confirmed Bug description: The gnome-screenshot program segfaults every time, when I try to capture the current window with `gnome-screenshot -w`. Taking an area screenshot with `gnome-screenshot -a`, and taking a full desktop screenshot with `gnome-screenshot` works, but taking a current window screenshot with `gnome-screenshot -w` segfaults every time. Adding delay with `-d ` and capturing pointer or not with `-p` has no effect. This may be the same bug as https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/81817 although that one is closed long ago. The relationship is that I'm using gnome-screenshot inside the XMonad window manager, a non- standard window manager. Stack trace: $ gdb gnome-screenshot GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1 [...] Reading symbols from gnome-screenshot...(no debugging symbols found)...done. (gdb) core-file core warning: core file may not match specified executable file. [New LWP 25469] [New LWP 25472] [New LWP 25470] [New LWP 25471] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `gnome-screenshot -d 3 -w -p'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0040dbb5 in ?? () [Current thread is 1 (Thread 0x7f3b4c841a40 (LWP 25469))] (gdb) where #0 0x0040dbb5 in ?? () #1 0x0040e1ea in ?? () #2 0x00408bc1 in ?? () #3 0x00408df9 in ?? () #4 0x7f3b4a5afac3 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f3b4a5af05a in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f3b4a5af400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f3b4a5af4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f3b4ab76cdd in g_application_run () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #9 0x00408385 in ?? () #10 0x7f3b49a84830 in __libc_start_main (main=0x408320, argc=5, argv=0x7fff78989e68, init=, fini=, rtld_fini=, stack_end=0x7fff78989e58) at ../csu/libc-start.c:291 #11 0x004083c9 in ?? () System information: $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 $ apt-cache policy gnome-screenshot gnome-screenshot: Installed: 3.18.0-1ubuntu2 Candidate: 3.18.0-1ubuntu2 Version table: *** 3.18.0-1ubuntu2 500 500 http://vault.galois.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1625773/+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 2049923] Re: gnome-terminal freezing, then crashing
> change to that new tab This is a no-op because the new tab is automatically swithed to, correct? --- Are you on Wayland or X11? This command should answer it: echo $XDG_SESSION_TYPE --- I cannot reproduce the crash. The steps to reproduce are very simple, so I believe we should have received more crash reports. There must be something weird, unique going on in your machine, at least that's what I suspect. Have you customized your shell prompt, for example? It might be relevant. Or do you have unusually large or unusually small gnome- terminal windows, or anything nontypical in the terminal's default config? --- I'd like to see a stack trace of the crash. Could you please do the following? Open two terminals that are _not_ gnome-terminal. For example xterm. Make sure gnome-terminal is _not_ running. In the first xterm, execute two: ulimit -c unlimited /usr/libexec/gnome-terminal-server In the second xterm, within 10 seconds, execute: gnome-terminal You should see a gnome-terminal window appear as usual. Make it crash according to the aforementioned steps. In the first window you should see a brief message including "core dumped". In the directory /var/lib/apport/coredump you should see a freshly created file, mentioning gnome-terminal-server in its name. Verify its timestamp that it's indeed a freshly created one. Run this command gdb /usr/libexec/gnome-terminal-server /var/lib/apport/coredupmp/[the new filename of that core dump] You might then need to press Enter a few times until you get a "(gdb)" prompt. There execute the command bt full You might again need to press Enter a few times to continue its output (if it asks to "Type for more"), until you get a "(gdb)" prompt again. Then please copy-paste gdb's output here. (There might be an easier way of getting this info using apport, but I'm not familiar with that. If you are then you can do that.) Thanks in advance! -- 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/2049923 Title: gnome-terminal freezing, then crashing Status in gnome-terminal package in Ubuntu: New Bug description: First: It's very hard to reproduce, but it happens to me about once per week. If often open new windows or split windows out from tabs. And then it happens. First it becomes unresponsive, and then after about 2-3 seconds it simply closes all instances. [328830.780749] gnome-terminal-[117706]: segfault at 460742 ip 7fdb2fb45611 sp 7ffdb8c5fda0 error 4 in libgtk-3.so.0.2406.32[7fdb2f883000+38f000] likely on CPU 4 (core 4, socket 0) [328830.780761] Code: fb 48 83 ec 20 64 48 8b 04 25 28 00 00 00 48 89 44 24 18 31 c0 e8 bf 6d ff ff 48 85 db 74 7a 48 89 c6 48 8b 03 48 85 c0 74 05 <48> 39 30 74 0c 48 89 df e8 a2 c2 d4 ff 85 c0 74 5e 48 89 e6 48 89 [329377.925310] gnome-terminal-[120116]: segfault at 2f0774 ip 7f86af745611 sp 7ffc9943c5c0 error 4 in libgtk-3.so.0.2406.32[7f86af483000+38f000] likely on CPU 2 (core 2, socket 0) [329377.925324] Code: fb 48 83 ec 20 64 48 8b 04 25 28 00 00 00 48 89 44 24 18 31 c0 e8 bf 6d ff ff 48 85 db 74 7a 48 89 c6 48 8b 03 48 85 c0 74 05 <48> 39 30 74 0c 48 89 df e8 a2 c2 d4 ff 85 c0 74 5e 48 89 e6 48 89 unfortunately, apport isn't automatically creating a crash report. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-terminal 3.49.92-2ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 19 16:48:43 2024 SourcePackage: gnome-terminal UpgradeStatus: Upgraded to mantic on 2023-10-17 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2049923/+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 2051829] [NEW] Nautilus file manager failed to connect to samba share with user without password
Public bug reported: Ubuntu 23.10 nautilus: Installed: 1:45~rc-1ubuntu1 I expected successful connection to a samba share with specific user without password. I have home samba server running on ubuntu server. It provides one share with disabled anonymous access but with a user without password (blank). Windows explorer, mac finder and other clients works fine, even terminal smbclient, but then i try to connect with nautilus from ubuntu desktop as "registered user" but leave password blank -> i got "invalid argument". When i create another samba user on the server with a password - connection was successful. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 31 12:18:54 2024 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2023-12-27 (35 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2023.09.06 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session ** Attachment added: "image_2024-01-31_122839837.png" https://bugs.launchpad.net/bugs/2051829/+attachment/5743877/+files/image_2024-01-31_122839837.png -- 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/2051829 Title: Nautilus file manager failed to connect to samba share with user without password Status in nautilus package in Ubuntu: New Bug description: Ubuntu 23.10 nautilus: Installed: 1:45~rc-1ubuntu1 I expected successful connection to a samba share with specific user without password. I have home samba server running on ubuntu server. It provides one share with disabled anonymous access but with a user without password (blank). Windows explorer, mac finder and other clients works fine, even terminal smbclient, but then i try to connect with nautilus from ubuntu desktop as "registered user" but leave password blank -> i got "invalid argument". When i create another samba user on the server with a password - connection was successful. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 31 12:18:54 2024 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2023-12-27 (35 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2023.09.06 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2051829/+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 1424201] Re: Web browsers lacking hardware-accelerated video decoding
Yeah that's the same question I had in "EDIT" of comment #151. Someone just needs to test it on old and new hardware. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Fix Released Status in chromium-browser package in Ubuntu: In Progress Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux browsers. We will close this bug when most browsers will have Va-api decoding working OOTB without user interaction like in WinOS and MacOS January 2024: - Quickest answer : Install firefox Flatpak https://flathub.org/fr/apps/org.mozilla.firefox activate VAAPI with the flag media.ffmpeg.vaapi.enabled=true - Snap : still not ready - deb from mozilla : not tested. August 2022 : * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1 ) -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need to fix this as most youtube is AV1 now. * In july 2020, things are getting better : - Chromium : A patch is used on most distro packages. , more info here https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1816497 - Firefox : Firefox team has done a great job and now Va-api decoding in Wayland is possible and X11 is possible in nightly ! Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 * In 2015 I opened this bug , no easy solution was available and battery drained when playing video in browser was crazy. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+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 1970069] Re: Annoying boot messages interfering with splash screen
Hmm, no plymouthd isn't starting quite early enough in Noble: 2.799s - plymouthd starts 4.080s - first show-splash attempt (rejected because DRM hasn't started yet) 5.290s - found /dev/dri/card0 5.364s - showing splash screen What this means is that any attempt to fix the bug in plymouthd itself (I was planning with FBIOPUT_CON2FBMAP) would be unreliable because plymouthd has started too late to dodge those early console messages. ** Changed in: plymouth (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1424201] Re: Web browsers lacking hardware-accelerated video decoding
@Daniel, #146 mentions xwayland but we switched firefox to use wayland by default since so it should work at least on waylands sessions? And #2 is about newer intel generation. Said differently on a < 13th gen using wayland the videoacc should be working out of the box no? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Fix Released Status in chromium-browser package in Ubuntu: In Progress Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux browsers. We will close this bug when most browsers will have Va-api decoding working OOTB without user interaction like in WinOS and MacOS January 2024: - Quickest answer : Install firefox Flatpak https://flathub.org/fr/apps/org.mozilla.firefox activate VAAPI with the flag media.ffmpeg.vaapi.enabled=true - Snap : still not ready - deb from mozilla : not tested. August 2022 : * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1 ) -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need to fix this as most youtube is AV1 now. * In july 2020, things are getting better : - Chromium : A patch is used on most distro packages. , more info here https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1816497 - Firefox : Firefox team has done a great job and now Va-api decoding in Wayland is possible and X11 is possible in nightly ! Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 * In 2015 I opened this bug , no easy solution was available and battery drained when playing video in browser was crazy. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+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
