[Desktop-packages] [Bug 49348] Re: List view in Nautilus does not allow dragging a selection by mouse
This is resolved in 43. Rubberbanding in list view required gtk4 and the use of GtkColumnView -- 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/49348 Title: List view in Nautilus does not allow dragging a selection by mouse Status in GTK+: New Status in Nautilus: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: When viewing files in Nautilus one can drag a rectangle around them to mark certain files. This is not possible in the list view of Nautilus even though there is usually a large white space in folders with few files that can make a user believe that dragging with the mouse there would produce the same rectangle as in icon view. I do it all the time by habit, and it is very annoying. Proposal: * Make it possible to drag a rectangle in list view. The problem is that starting to drag on a list item moves that item. Konqueror has solved this that you have to drag on the item name itself to move, else a rectangle marquee is started. Personally I find this quite efficient but may be annoying for less experienced users... To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/49348/+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 271216] Re: Firefox prints one page only of long doc in a frame
** Changed in: firefox Importance: Critical => Unknown ** Bug watch added: Mozilla Bugzilla #1789259 https://bugzilla.mozilla.org/show_bug.cgi?id=1789259 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/271216 Title: Firefox prints one page only of long doc in a frame Status in Mozilla Firefox: In Progress Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: mozilla-firefox Firefox 3.01 printing: I have two frames, one containing a document that should take many pages to print. Firefox only prints one page, losing the rest. Typical site: http://www.cict.bhtafe.edu.au/subjects/ict321/bug.html It also prints one page for multi-frame documents from web access to M/S Exchange such as http://www.cict.bhtafe.edu.au/subjects/bug/MicrosoftOutlookWebAccess.html Another problem site is http://septemberfestival.com.au/index.php?option=com_content=view=4=4 which prints three pages but still loses a lot of content Package is Ubuntu 8.10 alpha5, but problem has occurred in many other distros and earlier versions of firefox. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/271216/+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 271216]
In the process of [migrating remaining bugs to the new severity system](https://bugzilla.mozilla.org/show_bug.cgi?id=1789259), the severity for this bug cannot be automatically determined. Please retriage this bug using the [new severity system](https://wiki.mozilla.org/BMO/UserGuide/BugFields#bug_severity). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/271216 Title: Firefox prints one page only of long doc in a frame Status in Mozilla Firefox: In Progress Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: mozilla-firefox Firefox 3.01 printing: I have two frames, one containing a document that should take many pages to print. Firefox only prints one page, losing the rest. Typical site: http://www.cict.bhtafe.edu.au/subjects/ict321/bug.html It also prints one page for multi-frame documents from web access to M/S Exchange such as http://www.cict.bhtafe.edu.au/subjects/bug/MicrosoftOutlookWebAccess.html Another problem site is http://septemberfestival.com.au/index.php?option=com_content=view=4=4 which prints three pages but still loses a lot of content Package is Ubuntu 8.10 alpha5, but problem has occurred in many other distros and earlier versions of firefox. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/271216/+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]
It does not, which is unfortunate, as the 6th gen model recently finally got support. The gen 7 uses the CSC3551 and the gen 7 is missing the properties in the _DSD tables. Do you already have the Gen 7? Try submitting a Lenovo support ticket asking them to add the properties. I have a ticket they haven't follow up on yet so I added a comment to the ticket I think less than an hour ago. On 10/24/22 09:55, bugzilla-dae...@kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > --- Comment #710 from Howard Chu (h...@highlandsun.com) --- > Hi, I might've missed this but - do we know for certain that the 7th gen > Legion > 7 (2022 model) uses the same amplifier chip as the 6th gen (2021 model)? > -- 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]
Hi, I might've missed this but - do we know for certain that the 7th gen Legion 7 (2022 model) uses the same amplifier chip as the 6th gen (2021 model)? -- 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 toyeisfree from comment #708) > i'm a normal user and i can be super wrong but... why we say that the bios > is missing something and in Windows work perfectly without that ? Because the windows drivers from Lenovo have those values hardcoded into them. Seems that Cirrus Logic generally expects these properties to be in the ACPI tables even for Windows. Sounds like missing properties is an issue in "older" laptop models. I don't think my model is very old, but could be that the work on it started earlier. The properties are specific to a given laptop model and having the wrong values could physically damage your speakers. Before I knew this, I hard coded the values into a kernel patch and managed to get my own sound working. Fortunately, my speakers are fine. I certainly don't know how, but perhaps the drivers could be reverse engineered to discover the values of the properties for a given model, and then you could override the DSDT like this to get your sound working: https://wiki.debian.org/OverridingDSDT IIRC, you could then use the Intel HDA early patching to set your laptop to use the quirk of another laptop that uses the cs35l41 quirk so you could get sound working without any changes at all to the kernel to get your sound working. -- 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]
Apologies, wrong laptop model#. It is: Legion S7 16ARHA7 as in the linked alsa-project url. -- 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'm a normal user and i can be super wrong but... why we say that the bios is missing something and in Windows work perfectly without that ? -- 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 antidense from comment #705) > Here are the dmesg errors: > [ 35.177946] cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: error -EINVAL: > Platform not supported > [ 35.179512] cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: error -EINVAL: > Platform not supported > > [2.331045] ACPI: \_SB_.PCI0.LPC0.EC0_: Boot DSDT EC initialization > complete > [ 35.177183] cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Error: ACPI _DSD > Properties are missing for HID CSC3551. > [ 35.178812] cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Error: ACPI _DSD > Properties are missing for HID CSC3551. As referenced here: https://bugzilla.kernel.org/show_bug.cgi?id=208555#c702 (Newer kernels had a patch that fortunately clarifies that it's a matter of missing _DSD properties) Your laptop is missing the _DSD entries to setup this device. I suggest opening a support ticket. Hopefully with enough pressure, they'll add the entries. Especially since it doesn't require Lenovo to touch Linux or anything else other than to update their own BIOS images for the affected models. -- 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 bought the Legion 7 AMD Advantage (16IAX7) and I am unable to get the audio to work in archlinux. I also tried PopOS! and PCLinuxOS which was on 5.18. It only works in Windows Enabling the CONFIG_SERIAL_MULTI_INSTANTIATE does not help in 6.0.3. I also tried adding this quirk and compiling: SND_PCI_QUIRK(0x17aa, 0x387, "Legion 7 16IAX7", ALC287_FIXUP_LEGION_15IMHG05_SPEAKERS), I have not had the chance to go back and check in 5.18. I also tried the 0.0.5 patch and that did not work either. Here are the dmesg errors: [ 35.177946] cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: error -EINVAL: Platform not supported [ 35.179512] cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: error -EINVAL: Platform not supported [2.331045] ACPI: \_SB_.PCI0.LPC0.EC0_: Boot DSDT EC initialization complete [ 35.177183] cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Error: ACPI _DSD Properties are missing for HID CSC3551. [ 35.178812] cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Error: ACPI _DSD Properties are missing for HID CSC3551. Subsystem: 3877 http://alsa-project.org/db/?f=b122164954536a489dd3f9bc659f96b1ca2aa5a4 I am assuming it's the Lenovo BIOS is missing the DSD entries? I tried to put in a lenovo ticket, and they just sent me to a page on how to fix it in Windows. -- 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 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(
** Tags removed: verification-needed ** Tags added: verification-done -- 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/1969422 Title: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object() Status in Mutter: Unknown Status in OEM Priority Project: Fix Committed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Fix Released Bug description: [ Impact ] On dual-GPU systems, gnome-shell may crash in gbm_surface_release_buffer() during display config changes, like when rearranging monitor positions. [ Test Plan ] 1. Find a dual GPU system where both use open source drivers (like Intel + AMD). 2. Ideally also attach one monitor to each GPU. 3. Open Settings and repeatedly change the monitor layout pressing Apply each time. Expect: System does not crash. [ Where problems could occur ] Anywhere to do with screen updates since the entire triple buffering patch has been updated. [ Other Info ] The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1969422/+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 1993874] Re: Settings and Quick Menu apply Dark style differently
Hi! For me the way to reproduce this its simple, 1. With dark mode/theme selected. 2. Open the settings app and select "Appearance". 3. The shell change to light/white theme. 4. Select any ascent color. 5. The shell change to dark theme again. As @Batwam say's the Appearance tab ob the Settings app is involved. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1993874 Title: Settings and Quick Menu apply Dark style differently Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I just upgraded to Ubuntu 22.10 and noticed that some of my apps were no longer in Dark mode including gedit/chrome. When setting the style through the quick menu however, these apps go to Dark mode (presumably due to gtk theme being applied). Likewise for the quick menu itself, setting the style to Dark in gnome-control-settings doesn't change it to dark, it remains light. see screenshot attached, you will see that when setting the style to Dark in Settings, gedit and the quick menu remain light. I tried to logout in case it was an issue with how the settings are applied but it didn't help. it's also clear that the toggle in the quick menu works as intended so there seems to be an issue with the way gnome- control-center applies the Dark style. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 10:21:40 2022 InstallationDate: Installed on 2022-04-06 (198 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993874/+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 1991494] Re: dark mode sometimes works
Hi! For me the way to reproduce this its simple, 1. With dark mode/theme selected. 2. Open the settings app and select "Appearance". 3. The shell change to light/white theme. 4. Select any ascent color. 5. The shell change to dark theme again. See this others bugs I think are related: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993878 https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1993874 -- 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/1991494 Title: dark mode sometimes works Status in gnome-shell package in Ubuntu: Confirmed Bug description: the dark mode sometimes works and sometimes doesn't work. If i open Ubuntu Software store dark mode doesn't work and i have to go back to turn it back on again then it work's, its like it doesn't went to be in dark mode when i open Ubuntu Software store. it doesn't matter that must to me i just want you guys to know about it. this problem in on Ubuntu 22.10 Kinetic Kudu ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 2 20:18:36 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] [1043:135e] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 920MX] [1043:135e] InstallationDate: Installed on 2022-10-02 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) MachineType: ASUSTeK COMPUTER INC. X541UVK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=70e3626f-9c69-4f70-9d86-7021fd38f8a6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/30/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541UVK.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541UVK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX541UVK.308:bd01/30/2018:br5.12:svnASUSTeKCOMPUTERINC.:pnX541UVK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UVK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: X dmi.product.name: X541UVK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.112-3ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1991494/+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 1993878] Re: Dark mode from the drop down menu turning off on it's own
Hi! For me the way to reproduce this its simple, 1. With dark mode/theme selected. 2. Open the settings app and select "Appearance". 3. The shell change to light/white theme. 4. Select any ascent color. 5. The shell change to dark theme again. -- 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/1993878 Title: Dark mode from the drop down menu turning off on it's own Status in gnome-shell package in Ubuntu: Confirmed Bug description: tldr; Dark mode from the drop down menu turning off on it's own, resulting in mismatched theme across the shell. Description: Ubuntu 22.10 Release: 22.10 Gnome 43. Expected : Dark mode from the drop down menu matching the one from system settings. What happens : Dark mode from the drop down menu turning off on it's own. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993878/+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 1993867] Re: Telegram sometimes start endless use 100% CPU
** Tags added: foundations-triage-discuss
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libvpx in Ubuntu.
https://bugs.launchpad.net/bugs/1993867
Title:
Telegram sometimes start endless use 100% CPU
Status in libvpx package in Ubuntu:
New
Status in telegram-desktop package in Ubuntu:
New
Bug description:
On Ubuntu 22.04 all was fine.
After upgrade to Ubuntu 22.10 Telegram was also updated. And
sometimes, randomly, TG starts to use 100% CPU.
Nothing on logs. But in starce i see a lot of these messages:
[pid 33581] poll([{fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=9,
events=POLLIN}, {fd=14, events=POLLIN}, {fd=19, events=POLLIN}, {fd=51,
events=POLLIN}], 6, 8) = 0 (Timeout)
PSA. Thousand messages.
In normal state, when TG use 0-2% CPU, i see same messages. So, not
related with bug.
Please, ask me additional information, i can provide any logs.
Today this bug occurs two times.
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: telegram-desktop 4.1.1+ds-1ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 22 01:53:36 2022
InstallationDate: Installed on 2018-05-02 (1633 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: telegram-desktop
UpgradeStatus: Upgraded to kinetic on 2022-10-20 (1 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1993867/+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 1994077] [NEW] GPU fan goes at 100% during mild-moderate activity, disregarding built fan curve or custom fan curve
Public bug reported: Issue with graphics card fan running at max RPM if either cpu or gpu are put under slight stress. Usually when graphics card temp goes above 50 degrees celsius, but also if the CPU is performing some intensive work. This has started ever since upgrading to Ubuntu 22.04. The actual GPU fan speed reported is sometimes misreported during these errors, and does not respond to manual control through CoreCTRL or via command-line, but it is definitely the GPU fan which is making the noise. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.1.0-060100rc1-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Oct 24 22:52:32 2022 DistUpgraded: 2022-09-11 18:48:47,235 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [174b:e353] InstallationDate: Installed on 2018-03-19 (1680 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Micro-Star International Co., Ltd. MS-7A33 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.1.0-060100rc1-generic root=UUID=49a0c4fb-2e67-4829-992f-626d1d40dc33 ro rootflags=subvol=@ resume=UUID=0841c49c-0031-4984-a508-c94b1cd49dd3 amdgpu.vm_fragment_size=9 amdgpu.ppfeaturemask=0x SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-09-11 (43 days ago) dmi.bios.date: 05/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.L3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PLUS (MS-7A33) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.L3:bd05/25/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A33:pvr3.0:rvnMSI:rnX370GAMINGPLUS(MS-7A33):rvr3.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr3.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A33 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.2~kisak1~j version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.2~kisak1~j version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 xserver.bootTime: Thu Apr 15 23:58:44 2021 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.9-2ubuntu1.2~20.04.2 xserver.video_driver: amdgpu ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy performance third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1994077 Title: GPU fan goes at 100% during mild-moderate activity, disregarding built fan curve or custom fan curve Status in xorg package in Ubuntu: New Bug description: Issue with graphics card fan running at max RPM if either cpu or gpu are put under slight stress. Usually when graphics card temp goes above 50 degrees celsius, but also if the CPU is performing some intensive work. This has started ever since upgrading to Ubuntu 22.04. The actual GPU fan speed reported is sometimes misreported during these errors, and does not respond to manual control through CoreCTRL or via command-line, but it is definitely the GPU fan which is making the noise. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.1.0-060100rc1-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Oct 24 22:52:32 2022
[Desktop-packages] [Bug 1969140] Re: Window minimize animation flickers and appears in the wrong place in Xorg sessions
After using GNOME 43 Xorg with Debian Bookworm 5.19, I rebooted into Ubuntu 22.04 Xorg 5.15, did some checks and found out that on my Ryzen laptop this was caused by the amd_pstate scaling driver which lowers the minimum CPU frequency down to 400 Mhz instead of the 1400 Mhz default on the acpi_cpufreq which Debian uses. Debian (acpi_cpufreq) behaved perfectly on both Xorg and Wayland, so I enabled the amd_pstate scaling driver and this issue came up the exact same way as in Ubuntu: it seems that scaling down a much lower cpu frequency and then back up all the times can cause some performance penalties and glitches. To me it's fine because in the Xorg session I disabled the animations and the battery life is noticeably better with the amd_pstate scaling driver, but as usual ymmv! -- 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/1969140 Title: Window minimize animation flickers and appears in the wrong place in Xorg sessions Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Bug description: Graphical glitches appears while minimizing or maximizing apps in x11 session randomly, screencast below ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 14 17:07:49 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-04-12 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1969140/+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 1994058] [NEW] segfault when selecting a folder in Ubuntu 22.10 using sudo nautilus causing nautilus to close
Public bug reported: The error appears using sudo nautilus and selecting any folder or location what causes it to kill sudo nautilus making it close (org.gnome.Nautilus:47066): GLib-GIO-CRITICAL **: 15:06:54.827: g_dbus_connection_emit_signal: assertion 'object_path != NULL && g_variant_is_object_path (object_path)' failed Violación de segmento (segfault in English) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: nautilus ** Tags added: nautilus ** Description changed: The error appears using sudo nautilus and selecting any folder or - location - + location what causes it to kill sudo nautilus what causes it to close (org.gnome.Nautilus:47066): GLib-GIO-CRITICAL **: 15:06:54.827: g_dbus_connection_emit_signal: assertion 'object_path != NULL && g_variant_is_object_path (object_path)' failed Violación de segmento (segfault in English) ** Description changed: - The error appears using sudo nautilus and selecting any folder or - location what causes it to kill sudo nautilus what causes it to close + The error appears using sudo nautilus and selecting any folder or location what causes it to kill sudo nautilus + making it close (org.gnome.Nautilus:47066): GLib-GIO-CRITICAL **: 15:06:54.827: g_dbus_connection_emit_signal: assertion 'object_path != NULL && g_variant_is_object_path (object_path)' failed Violación de segmento (segfault in English) ** Summary changed: - segfault when selecting a folder in Ubuntu 22.10 using sudo nautilus + segfault when selecting a folder in Ubuntu 22.10 using sudo nautilus causing nautilus to close -- 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/1994058 Title: segfault when selecting a folder in Ubuntu 22.10 using sudo nautilus causing nautilus to close Status in nautilus package in Ubuntu: New Bug description: The error appears using sudo nautilus and selecting any folder or location what causes it to kill sudo nautilus making it close (org.gnome.Nautilus:47066): GLib-GIO-CRITICAL **: 15:06:54.827: g_dbus_connection_emit_signal: assertion 'object_path != NULL && g_variant_is_object_path (object_path)' failed Violación de segmento (segfault in English) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1994058/+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 195798] Re: Nautilus: Impossible to change case of filename/extension in Windows Share
I am running into something similar. I changing case in a filename doesn't accept changes. ie: renaming "text.txt" to "Test.txt" doesn't work. The only thing I can do is rename "text.txt" to "test2.txt" then rename "test2.txt" to "Test.txt" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/195798 Title: Nautilus: Impossible to change case of filename/extension in Windows Share Status in gvfs: Unknown Status in Nautilus: Invalid Status in samba: Fix Released Status in gvfs package in Ubuntu: Triaged Status in samba package in Debian: Fix Released Bug description: Altough Linux is a case-sensitive operating system, I cannot change the case in filename or extension in nautilus when working on a Windows Share. If I try to rename from 123.abc to 123.ABC for example, nautilus will tell me there already is a file with that name. Obviously, it doesn't matter to Windows the case of the filename/extension. The problem is that sometimes we use Windows shares to store files that will be accessed on Linux or shared between the two operating systems. Then it becomes a problem. Example situation: You are trying to watch a AVI movie with subtitles using MPlayer. Both files (.avi, .srt) are stored at a Windows share. In order for this to work with MPlayer, both files have to have the exact same name and case. The subtitles file (.srt) has one letter in a wrong case. You try to change it with Nautilus and it won't work. Now the only two solutions are renaming through a terminal or physichal access to the Windows machine. I have some other problems, regarding external scripts linking PPT and XLS to a database... If someone at the Windows side changes the case of one letter of any of the files, we at the Linux side can't fix it simply using Nautilus. Terminal or physical access is required. And, anyway, not being able to rename a file at a share cannot be an expected behavior. It makes no sense. Regards, Effenberg To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/195798/+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 1969315] Re: text in torrent info tabs change after opening it to gibberish
OK forget about post #39 just encountered the bug again delayed startup of transmission doesn't help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1969315 Title: text in torrent info tabs change after opening it to gibberish Status in transmission package in Ubuntu: Confirmed Bug description: on transmission-gtk after opening the torrent's properties panel, the text at first it's showing ok, buy on mouse hover it changes to random text worked fine on 21.10 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: transmission-gtk 3.00-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 17 19:28:03 2022 SourcePackage: transmission UpgradeStatus: Upgraded to jammy on 2022-03-26 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1969315/+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 1994045] [NEW] ubuntu 22.04, Gnome dark theme, gnome 42.4, wayland, , gedit: if I call gedit in admin mofe I cant change the setting for current line dont emphazise
Public bug reported: ubuntu 22.04, dark theme, gnome 42.4, wayland, gedit: if I call gedit in admin mode I can't change the setting to dont emphazise current line ... so the current line is highlighted to white and unreadable. ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: admin dark gedit mode theme -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1994045 Title: ubuntu 22.04, Gnome dark theme, gnome 42.4, wayland,, gedit: if I call gedit in admin mofe I cant change the setting for current line dont emphazise Status in gedit package in Ubuntu: New Bug description: ubuntu 22.04, dark theme, gnome 42.4, wayland, gedit: if I call gedit in admin mode I can't change the setting to dont emphazise current line ... so the current line is highlighted to white and unreadable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1994045/+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 1970663]
*** Bug 1794026 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1970663 Title: Tiny mouse cursor in firefox snap Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Since a few day I've updated to Ubuntu Mate 22.04 with the firefox snap. Since then I've been having this strange bug. I have a 4k screen which I'm running at a 2180p resolution with scaling on HiDPI. This runs just fine except for in firefox. In the new firefox snap I get a really tiny mouse cursor. I also checked other snap, it is not the case there. Regards, Chris --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-02 (83 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: ubuntu-mate-artwork ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Snap: firefox 99.0.1-1 (stable) Snap.Changes: no changes found Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-02 (83 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: ubuntu-mate-artwork ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Snap: firefox 99.0.1-1 (stable) Snap.Changes: no changes found Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1970663/+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 1992667] Re: Application windows invisible (on DG2 graphics)
yes, mesa 22.2.x is a part of the hwe stack -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1992667 Title: Application windows invisible (on DG2 graphics) Status in linux-oem-6.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Fix Released Status in linux-oem-6.0 source package in Jammy: New Status in mesa source package in Jammy: New Bug description: When using GNOME Shell with Wayland, all application windows become invisible from time to time. This usually happens right after starting GNOME Shell for the first time or after having a VRAM intensive application open, such as a game. I have installed the latest linux-oem-6.0 kernel and manually enabled support for DG2 graphics by passing the i915.force_probe parameter with the PCIe ID of the graphics card. I have attached a screenshot of the described behavior below. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0 Uname: Linux 6.0.0-1005-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Oct 12 17:23:40 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-10-11 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1992667/+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 1993936] Re: Laptop battery stays 100% while discharging
** Package changed: linux (Ubuntu) => upower (Ubuntu) ** Summary changed: - Laptop battery stays 100% while discharging + Laptop battery stays 100%(or whatever percentage of battery it started with) while discharging -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1993936 Title: Laptop battery stays 100%(or whatever percentage of battery it started with) while discharging Status in upower package in Ubuntu: Confirmed Bug description: I have recently upgraded from 22.04 to 22.10. The battery remains at 100% or whatever percentage of battery it started with . The system do not identify the plugging in of the ac adapter and neither removing of it. My system is Asus TUF A15 FA506II-FA566II. The battery is correctly detected in Windows 11 and worked like a charm in the 22.04 version. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: soumyajyoti 2539 F wireplumber /dev/snd/controlC0: soumyajyoti 2539 F wireplumber /dev/snd/controlC1: soumyajyoti 2539 F wireplumber /dev/snd/seq:soumyajyoti 2536 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-11-22 (699 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming A15 FA506II_FA566II Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=80cc1579-96aa-4743-aef2-d67dbff067cb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-19 (3 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/12/2021 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506II.316 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506II dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.12 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506II.316:bd03/12/2021:br5.16:efr3.12:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingA15FA506II_FA566II:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506II:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ASUS TUF Gaming A15 dmi.product.name: ASUS TUF Gaming A15 FA506II_FA566II dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1993936/+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 1971712] Re: Add support for Intel DG2
** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Released Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip firmare: updates to i915 DMC, GuC [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971712/+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 1993936] [NEW] Laptop battery stays 100% while discharging
You have been subscribed to a public bug: I have recently upgraded from 22.04 to 22.10. The battery remains at 100% or whatever percentage of battery it started with . The system do not identify the plugging in of the ac adapter and neither removing of it. My system is Asus TUF A15 FA506II-FA566II. The battery is correctly detected in Windows 11 and worked like a charm in the 22.04 version. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: soumyajyoti 2539 F wireplumber /dev/snd/controlC0: soumyajyoti 2539 F wireplumber /dev/snd/controlC1: soumyajyoti 2539 F wireplumber /dev/snd/seq:soumyajyoti 2536 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-11-22 (699 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming A15 FA506II_FA566II Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=80cc1579-96aa-4743-aef2-d67dbff067cb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-19 (3 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/12/2021 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506II.316 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506II dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.12 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506II.316:bd03/12/2021:br5.16:efr3.12:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingA15FA506II_FA566II:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506II:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ASUS TUF Gaming A15 dmi.product.name: ASUS TUF Gaming A15 FA506II_FA566II dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: upower (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-collected kinetic -- Laptop battery stays 100% while discharging https://bugs.launchpad.net/bugs/1993936 You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower 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 1993907] Re: nautilus freezes randomly
Search appears to be unrelated in my case. -- 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/1993907 Title: nautilus freezes randomly Status in nautilus package in Ubuntu: Confirmed Bug description: nautilus becomes unresponsive and "files" is not responding sign appears at random ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-1007.7-lowlatency 5.19.7 Uname: Linux 5.19.0-1007-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 15:39:58 2022 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1272, 787)' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-05-13 (161 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-19 (3 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993907/+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 1916640] Re: Nvidia 340.108 fails to install with kernels 5.11.x - new patches needed
So, four months passed since my last post and no one answered. I confirm that patched Nvidia 340.108 drivers supplied by Butterfly (kelebek333) at https://launchpad.net/~kelebek333/+archive/ubuntu/nvidia-legacy work very well till kernel 5.17.x but not beyond. The site https://nvidia.if-not-true-then-false.com/patcher/NVIDIA-340xx/ has got new patches kernel 6.x now hoping that some willing programmers want to compile the drivers with the new patches as the kelebek- butterfly repository seems to be dead ... ** Summary changed: - Nvidia 340.108 fails to install with kernels 5.11.x - new patches needed + Nvidia 340.108 driver provided by Butterfly (kelebek333) works very well till kernel 5.17.x but not beyond -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1916640 Title: Nvidia 340.108 driver provided by Butterfly (kelebek333) works very well till kernel 5.17.x but not beyond Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: As usual I have opened this (no more) new bug report... As ALWAYS happened in the past, EVERY TWO MONTHS new patches are needed for old Nvidia 340.108 drivers, that is, with each release of a new kernel... Nvidia 340.108 fails to install with kernels 5.11.x - new patches needeed Just to inform develepers that a new patch for Nvidia 340.108 and kernel 5.11 is not yet available here: https://github.com/warpme/minimyth2/blob/master/script/nvidia/nvidia-340.108/files/ Anyway thanks for your great contribution to community and hope you publish new patched drivers without having to always report the same bug... Good day to all the developers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1916640/+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 1993907] Re: nautilus freezes randomly
The problem seems to be related to the search provider, can anyone confirm? As soon as I search anything in Gnome Activities overview, Nautilus hangs. If I disable Settings > Search > Files, I experience no hangs (of course, I lose file results in the overview when searching, too). -- 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/1993907 Title: nautilus freezes randomly Status in nautilus package in Ubuntu: Confirmed Bug description: nautilus becomes unresponsive and "files" is not responding sign appears at random ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-1007.7-lowlatency 5.19.7 Uname: Linux 5.19.0-1007-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 15:39:58 2022 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1272, 787)' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-05-13 (161 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-19 (3 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993907/+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 1916640] Re: Nvidia 340.108 fails to install with kernels 5.11.x - new patches needed
** Summary changed: - Nvidia 340.108 fails to install with kernels 5.1x - new patches needeed + Nvidia 340.108 fails to install with kernels 5.11.x - new patches needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1916640 Title: Nvidia 340.108 fails to install with kernels 5.11.x - new patches needed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: As usual I have opened this (no more) new bug report... As ALWAYS happened in the past, EVERY TWO MONTHS new patches are needed for old Nvidia 340.108 drivers, that is, with each release of a new kernel... Nvidia 340.108 fails to install with kernels 5.11.x - new patches needeed Just to inform develepers that a new patch for Nvidia 340.108 and kernel 5.11 is not yet available here: https://github.com/warpme/minimyth2/blob/master/script/nvidia/nvidia-340.108/files/ Anyway thanks for your great contribution to community and hope you publish new patched drivers without having to always report the same bug... Good day to all the developers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1916640/+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 1993800]
(In reply to Fabian Vogt from comment #9) > So the missing "instcombine" pass causes the "Cannot select" error and the > pass is missing > because Mesa passes an invalid list of passes to LLVMRunPasses and ignores > the error. Would it be possible to improve error handling here? At least some tracing would be nice. From your analysis it looks like this might affect more platforms and not just armv7, and we wouldn't have noticed anything were it not for the backend bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1993800 Title: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2> Status in LLVM: New Status in llvm-toolchain-15 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in llvm-toolchain-15 package in openSUSE: Unknown Bug description: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2> 0x2f696b8: v4i32,ch = ARMISD::VLD1DUP<(load (s32) from %ir.212)> 0x2aad434, 0x2f84090:1, Constant:i32<4> 0x2f84090: i32,i32,ch = load<(load (s32) from %ir.209, align 8), > 0x2aad434, 0x2f63a30, Constant:i32<64> 0x2f63a30: i32,ch = CopyFromReg 0x2aad434, Register:i32 %23 0x2f51c10: i32 = Register %23 0x2f82500: i32 = Constant<64> 0x2f81b28: i32 = Constant<4> 0x2f81e40: i32 = Constant<2> In function: fs_variant_partial [https://launchpadlibrarian.net/629171689/buildlog_ubuntu-kinetic- armhf.mutter_43.0-1ubuntu3_BUILDING.txt.gz] Although "LLVM ERROR: Cannot select" seems to be from LLVM, I can't determine what project "fs_variant_partial" is in. Sounds like it might be in some old version of Mesa? The start of the log suggests it's running on focal. To manage notifications about this bug go to: https://bugs.launchpad.net/llvm/+bug/1993800/+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 1994031] [NEW] Calendar in the top gets bugged after clicking a date from next month
Public bug reported: Can be easily repeatable. As i said in the summary, calendar at the top gets bugged when you click a date from the next month. Restart solves it but when i open any app it happens again. If you click a day from the present month and then click on a day from the next month, it won't happen. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 24 13:27:41 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-10-21 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1994031 Title: Calendar in the top gets bugged after clicking a date from next month Status in gnome-shell package in Ubuntu: New Bug description: Can be easily repeatable. As i said in the summary, calendar at the top gets bugged when you click a date from the next month. Restart solves it but when i open any app it happens again. If you click a day from the present month and then click on a day from the next month, it won't happen. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 24 13:27:41 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-10-21 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994031/+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 1994031] Re: Calendar in the top gets bugged after clicking a date from next month
I am not quite certain if this belongs to gnome-shell package, time or system-tray. But I can provide additional info/data if needed. -- 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/1994031 Title: Calendar in the top gets bugged after clicking a date from next month Status in gnome-shell package in Ubuntu: New Bug description: Can be easily repeatable. As i said in the summary, calendar at the top gets bugged when you click a date from the next month. Restart solves it but when i open any app it happens again. If you click a day from the present month and then click on a day from the next month, it won't happen. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 24 13:27:41 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-10-21 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994031/+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 1994027] Re: Can't move window by drag and drop by using touch screen
Switch to wayland, this issue is gone. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1994027 Title: Can't move window by drag and drop by using touch screen Status in OEM Priority Project: New Status in xorg package in Ubuntu: New Bug description: [Summary] For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed. [Steps to reproduce] 1. Install the 22.04 2. Boot and login 3. Open a folder 4. Drag-n-drop the folder with finger touch 5. Drag-n-drop the folder with the Wacom Pen [Expected result] Both finger touch and wacom pen work normally. [Actual result] Wacom Pen works normally, finger touch can not move the folder. [Failure rate] 100% [Checkbox job `com.canonical.certification::touchscreen/drag-n-drop` output] [Other Information] xorg 1:7.7+23ubuntu2 mutter-common 42.2-0ubuntu1 gnome-shell 42.4-0ubuntu0.22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994027/+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 1994027] Re: Can't move window by drag and drop by using touch screen
The touch screen works fine on 20.04 image. ** Description changed: [Summary] For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed. [Steps to reproduce] 1. Install the 22.04 2. Boot and login 3. Open a folder 4. Drag-n-drop the folder with finger touch 5. Drag-n-drop the folder with the Wacom Pen [Expected result] Both finger touch and wacom pen work normally. [Actual result] Wacom Pen works normally, finger touch can not move the folder. [Failure rate] 100% [Checkbox job `com.canonical.certification::touchscreen/drag-n-drop` output] + + [Other Information] + xorg 1:7.7+23ubuntu2 + mutter-common 42.2-0ubuntu1 + gnome-shell 42.4-0ubuntu0.22.04.1 ** Tags added: oem-priority originate-from-1991363 sutton -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1994027 Title: Can't move window by drag and drop by using touch screen Status in OEM Priority Project: New Status in xorg package in Ubuntu: New Bug description: [Summary] For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed. [Steps to reproduce] 1. Install the 22.04 2. Boot and login 3. Open a folder 4. Drag-n-drop the folder with finger touch 5. Drag-n-drop the folder with the Wacom Pen [Expected result] Both finger touch and wacom pen work normally. [Actual result] Wacom Pen works normally, finger touch can not move the folder. [Failure rate] 100% [Checkbox job `com.canonical.certification::touchscreen/drag-n-drop` output] [Other Information] xorg 1:7.7+23ubuntu2 mutter-common 42.2-0ubuntu1 gnome-shell 42.4-0ubuntu0.22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994027/+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 1994027] [NEW] Can't move window by drag and drop by using touch screen
Public bug reported: [Summary] For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed. [Steps to reproduce] 1. Install the 22.04 2. Boot and login 3. Open a folder 4. Drag-n-drop the folder with finger touch 5. Drag-n-drop the folder with the Wacom Pen [Expected result] Both finger touch and wacom pen work normally. [Actual result] Wacom Pen works normally, finger touch can not move the folder. [Failure rate] 100% [Checkbox job `com.canonical.certification::touchscreen/drag-n-drop` output] [Other Information] xorg 1:7.7+23ubuntu2 mutter-common 42.2-0ubuntu1 gnome-shell 42.4-0ubuntu0.22.04.1 ** Affects: oem-priority Importance: Undecided Status: New ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1991363 sutton -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1994027 Title: Can't move window by drag and drop by using touch screen Status in OEM Priority Project: New Status in xorg package in Ubuntu: New Bug description: [Summary] For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed. [Steps to reproduce] 1. Install the 22.04 2. Boot and login 3. Open a folder 4. Drag-n-drop the folder with finger touch 5. Drag-n-drop the folder with the Wacom Pen [Expected result] Both finger touch and wacom pen work normally. [Actual result] Wacom Pen works normally, finger touch can not move the folder. [Failure rate] 100% [Checkbox job `com.canonical.certification::touchscreen/drag-n-drop` output] [Other Information] xorg 1:7.7+23ubuntu2 mutter-common 42.2-0ubuntu1 gnome-shell 42.4-0ubuntu0.22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994027/+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 1994007] Re: totem show black screen when playing video repeatedly [resource creation failed]
Daniel,
Thanks for the information.
The totem didn't crash in my side, just black screen, and there is not crash
file in /var/crash. And there is not gstreamer1.0-vaapi package currently.
And I made a script to play this file in gstreamer, it works fine. So I
doubt this issue is related totem. smplayer and vlc looks fine in my
side.
#!/bin/bash
for a in {1..100}
do
echo $a
gst-launch-1.0 filesrc location=Robotica_1080_convert.ogv ! oggdemux !
theoradec ! autovideosink
done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1994007
Title:
totem show black screen when playing video repeatedly [resource
creation failed]
Status in OEM Priority Project:
New
Status in totem package in Ubuntu:
New
Bug description:
[steps reproduce]
1. Install Ubuntu 22.04.1LTS.
2. Play Robotica_1080_convert.ogv with Videos(totem) with cycles.
3. some times after 10 mins, some times within 2 hours,find unit's videos
show a black screen.
Details please refer to the attachments.
[failure rate]
100
[expected result]
It should can play normally.
[actual result]
find unit's videos show blackscreen,
[addtional infromation]
totem: 42.0-1ubuntu1
gstreamer1.0-plugins-base 1.20.1-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1994007/+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 1983010]
The tab doesn't completely lock up in this case - media continues to play audibly, and keyboard input is possible within the browser -- although invisible -- until the window and tab are visually obscured and then re-opened. In other words: after the issue appears, switching to a separate application and back again permits a single frame of the browser contents to render, but after that point they remain visually static (until the next manual refresh occurs). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1983010 Title: Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: I use Firefox Beta and launch it from the terminal. While watching Netflix on Firefox, I get the following messages on my terminal: Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index3/size Sandbox: attempt to open unexpected file /sys/devices/system/cpu/present Sandbox: attempt to open unexpected file /sys/devices/system/cpu Sandbox: Unexpected EOF, op 0 flags 00 path /proc/cpuinfo ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox (not installed) ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Jul 28 15:01:35 2022 InstallationDate: Installed on 2022-06-21 (36 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1983010/+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 1983010]
Ok, this happened to me again a few moments ago while browsing GitHub, and this time Spotify web player was not open (so my apologies for mistaking that as the possible cause). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1983010 Title: Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: I use Firefox Beta and launch it from the terminal. While watching Netflix on Firefox, I get the following messages on my terminal: Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index3/size Sandbox: attempt to open unexpected file /sys/devices/system/cpu/present Sandbox: attempt to open unexpected file /sys/devices/system/cpu Sandbox: Unexpected EOF, op 0 flags 00 path /proc/cpuinfo ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox (not installed) ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Jul 28 15:01:35 2022 InstallationDate: Installed on 2022-06-21 (36 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1983010/+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 1983010]
I've failed to reproduce this with Nightly and Debian unstable; I get the warnings about `/sys/devices/system/cpu` but nothing about `/proc/cpuinfo`. It's possible that that line is related to the error (i.e., whatever is trying to open `/proc/cpuinfo` for the second time causes media decoding to fail when it returns an error), but it could also be coincidence. The browser tab locking up is unexpected, though — even if the media plugin process crashes or hangs, the media subsystem is pretty good about doing everything asynchronously. If try playing something and then kill the `gmplugin` process, it stops playing and I get an in- content error that “something went wrong with playback”, and then it won't play anything until I reload the tab; that's all more or less what I'd expect. If I `SIGSTOP` the process, a few seconds later the audio stops but the time in the UI keeps advancing (and if I `SIGCONT` it, it will resume playing where it left off, which is no longer where the UI says it's playing from; that's an interesting bug but it might be Spotify's and not ours). But, no sign of the content process locking up or crashing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1983010 Title: Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: I use Firefox Beta and launch it from the terminal. While watching Netflix on Firefox, I get the following messages on my terminal: Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index3/size Sandbox: attempt to open unexpected file /sys/devices/system/cpu/present Sandbox: attempt to open unexpected file /sys/devices/system/cpu Sandbox: Unexpected EOF, op 0 flags 00 path /proc/cpuinfo ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox (not installed) ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Jul 28 15:01:35 2022 InstallationDate: Installed on 2022-06-21 (36 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1983010/+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 1983010]
Hi Gian-Carlo - this is on Debian 11 (bullseye), using the Intel i965 VA-API driver (and media.ffmpeg.vaapi.enabled=false in Firefox, if that's relevant). I'm not super keen to attempt repro without the sandboxing in place at the moment but I'll add details if & when I do. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1983010 Title: Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: I use Firefox Beta and launch it from the terminal. While watching Netflix on Firefox, I get the following messages on my terminal: Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index3/size Sandbox: attempt to open unexpected file /sys/devices/system/cpu/present Sandbox: attempt to open unexpected file /sys/devices/system/cpu Sandbox: Unexpected EOF, op 0 flags 00 path /proc/cpuinfo ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox (not installed) ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Jul 28 15:01:35 2022 InstallationDate: Installed on 2022-06-21 (36 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1983010/+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 1983010]
>Also encountered on Firefox 102.3.0 while listening to music using Spotify's web portal Hi James, as explained above the messages are just warnings, so something else must be going wrong. We'll need more details about your configuration, e.g. which distribution are you running? What graphics hardware and drivers do you have? Could you try to run Firefox with ```MOZ_DISABLE_GMP_SANDBOX=1``` set in the environment and see if the issue reproduces? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1983010 Title: Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: I use Firefox Beta and launch it from the terminal. While watching Netflix on Firefox, I get the following messages on my terminal: Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index3/size Sandbox: attempt to open unexpected file /sys/devices/system/cpu/present Sandbox: attempt to open unexpected file /sys/devices/system/cpu Sandbox: Unexpected EOF, op 0 flags 00 path /proc/cpuinfo ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox (not installed) ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Jul 28 15:01:35 2022 InstallationDate: Installed on 2022-06-21 (36 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1983010/+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 1983010]
Also encountered on Firefox 102.3.0 while listening to music using Spotify's web portal ( https://open.spotify.com/ ). ``` Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index3/size Sandbox: attempt to open unexpected file /sys/devices/system/cpu/present Sandbox: attempt to open unexpected file /sys/devices/system/cpu Sandbox: unexpected multiple open of file /proc/cpuinfo ``` Around the same time, the browser tab became graphically unresponsive (blank contents). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1983010 Title: Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: I use Firefox Beta and launch it from the terminal. While watching Netflix on Firefox, I get the following messages on my terminal: Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index3/size Sandbox: attempt to open unexpected file /sys/devices/system/cpu/present Sandbox: attempt to open unexpected file /sys/devices/system/cpu Sandbox: Unexpected EOF, op 0 flags 00 path /proc/cpuinfo ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox (not installed) ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Jul 28 15:01:35 2022 InstallationDate: Installed on 2022-06-21 (36 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1983010/+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 1984147] Re: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland
Verified that this issue is fixed in gnome-shell 42.5-0ubuntu1 Thanks! ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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/1984147 Title: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland Status in OEM Priority Project: Fix Committed Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Committed Status in gnome-shell source package in Kinetic: Fix Released Bug description: [Impact] Users using desktop PC is not able to switch monitor mode between mirrored and joined mode using Super-P or keyboard shortcut. This SRU fixes the issue. [Test Plan] 1. Use a desktop PC and start GNOME 3 2. Connect the PC with 2 monitors 3. Use Super-P to switch to joined display (note that using Displays from Settings does not trigger the issue) 4. Use Super-P to switch display mode again Expected: Display Switcher popup should appear Actual: Display Switcher does not popup [Where problems could occur] Although this change is minimal, the impact should be only on switching display mode using the shortcut. [Version] gnome-shell42.2-0ubuntu0.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-10 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984147/+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 1994019] Re: Black screen after login with MUTTER_DEBUG_FORCE_KMS_MODE=simple
I see I still have the llvm Oibaf package, but that doesn't seem related (and I ppa-purged the PPA, so IDK why that's still there...) -- 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/1994019 Title: Black screen after login with MUTTER_DEBUG_FORCE_KMS_MODE=simple Status in gnome-shell package in Ubuntu: New Bug description: The same as in bug 1994000. I removed the oibaf PPAs altogether and now should be running the standard distro packages. The situation has not been solved. I also attach the prevboot file. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 24 11:27:47 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-26 (27 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-20 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994019/+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 1994019] [NEW] Black screen after login with MUTTER_DEBUG_FORCE_KMS_MODE=simple
Public bug reported: The same as in bug 1994000. I removed the oibaf PPAs altogether and now should be running the standard distro packages. The situation has not been solved. I also attach the prevboot file. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 24 11:27:47 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-26 (27 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-20 (3 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages wayland-session ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/bugs/1994019/+attachment/5626387/+files/prevboot.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1994019 Title: Black screen after login with MUTTER_DEBUG_FORCE_KMS_MODE=simple Status in gnome-shell package in Ubuntu: New Bug description: The same as in bug 1994000. I removed the oibaf PPAs altogether and now should be running the standard distro packages. The situation has not been solved. I also attach the prevboot file. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 24 11:27:47 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-26 (27 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-20 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994019/+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 1990089] Re: Screen freeze when performing memory stress in Wayland mode
** Tags added: originate-from-1981168 somerville
--
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/1990089
Title:
Screen freeze when performing memory stress in Wayland mode
Status in Linux:
New
Status in Mutter:
Fix Released
Status in OEM Priority Project:
Incomplete
Status in linux package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Opinion
Bug description:
[Steps to reproduce]
(disable systemd-oomd or executing over ssh)
(below command allocates a lot of memory to stress kernel page fault)
1. stress-ng --stack 0 --timeout 300
2. check the screen
[Expected result]
Screen will update slowly when performing the stress-test.
but screen needs back to work after stress.
[Actual result]
Screen freeze after stress test.
[Additional information]
kernel version: vmlinuz-5.17.0-1017-oem
kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
Mesa version: 22.0.5-0ubuntu0.1
Mutter version: 42.2-0ubuntu1
Gnome-shell version: 42.2-0ubuntu0.2
* Issue happens in Wayland only
* gnome-shell keeps issuing ioctl()
```
(gdb) bt
#0 __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at
../sysdeps/unix/sysv/linux/ioctl.c:36
#1 0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80,
request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75
#2 iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=,
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
#3 iris_wait_syncobj (bufmgr=, syncobj=,
timeout_nsec=timeout_nsec@entry=9223372036854775807) at
../src/gallium/drivers/iris/iris_fence.c:215
#4 0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50,
wait=, query=0x55774159b800, ctx=) at
../src/gallium/drivers/iris/iris_query.c:635
#5 iris_get_query_result (ctx=, query=0x55774159b800,
wait=, result=0x7fffc5404e50) at
../src/gallium/drivers/iris/iris_query.c:601
#6 0x7fcaca405e89 in tc_get_query_result (_pipe=,
query=0x55774159b800, wait=, result=0x7fffc5404e50) at
../src/gallium/auxiliary/util/u_threaded_context.c:881
#7 0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0,
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at
../src/mesa/main/queryobj.c:266
#8 0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790,
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
#9 get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283
"glGetQueryObjecti64v", id=, pname=34918,
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
at ../src/mesa/main/queryobj.c:1174
#10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=,
pname=, params=) at
../src/mesa/main/queryobj.c:1257
#11 0x7fcadfa39b90 in ?? () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#20 0x7fcae0743c24 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fcae0743293 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fcadf8d0849 in meta_context_run_main_loop () from
/lib/x86_64-linux-gnu/libmutter-10.so.0
#24 0x55773f1a4f12 in ?? ()
#25 0x7fcadf429d90 in __libc_start_call_main
(main=main@entry=0x55773f1a4a70, argc=argc@entry=1,
argv=argv@entry=0x7fffc54053e8) at ../sysdeps/nptl/libc_start_call_main.h:58
#26 0x7fcadf429e40 in __libc_start_main_impl (main=0x55773f1a4a70,
argc=1, argv=0x7fffc54053e8, init=, fini=,
rtld_fini=, stack_end=0x7fffc54053d8)
at ../csu/libc-start.c:392
#27 0x55773f1a51b5 in ?? ()
```
Other discussion thread:
https://gitlab.freedesktop.org/drm/intel/-/issues/6851
https://gitlab.gnome.org/GNOME/mutter/-/issues/2431
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter (not installed)
Uname: Linux 5.18.0-rc2+ x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
Date: Mon Sep 19 10:39:59 2022
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
[Desktop-packages] [Bug 1994000] Re: Can't log in anymore after setting MUTTER_DEBUG_FORCE_KMS_MODE=simple
Ubuntu 22.10 on an Intel/Nvidia hybrid with driver 515 and MUTTER_DEBUG_FORCE_KMS_MODE=simple set is working for me. So it sounds like your oibaf PPA is the problem. Please remove all PPAs from the machine, reboot, and then open new bugs for any issues you encounter. ** Package changed: mutter (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Incomplete => Invalid -- 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/1994000 Title: Can't log in anymore after setting MUTTER_DEBUG_FORCE_KMS_MODE=simple Status in Ubuntu: Invalid Bug description: My laptop is running a Hybrid Nvidia RTX3060 + Intel i5 11400h graphics. After installing the Nvidia drivers and with Wayland (this doesn't happen with Xorg), once the screen is turned off (for example, by locking the screen or suspending the computer, it cannot be turned on. This is a behavior similarish to the one in bug 1968040 (IDK if that one was also triggered by a screen lock, this one gets triggered inmediately after turning off the screen for whatever reason). In 22.04, I solved it quite easily by setting MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0. As suggested in that ticket, I set this time MUTTER_DEBUG_FORCE_KMS_MODE=simple. I unfortunately cannot tell whether this would solve my issues because, when I reboot my computer with that variable, I simply cannot log in into my account. I type my password as usual (the login screen works perfectly, though) and then, once submited, the output is a black screen (LCD is on, though) and nothing shows up after. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 24 08:40:12 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-26 (27 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-20 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1994000/+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 1993878] Re: Dark mode from the drop down menu turning off on it's own
** Summary changed: - Theming issue on Gnome 43 + Dark mode from the drop down menu turning off on it's own ** Tags added: kinetic -- 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/1993878 Title: Dark mode from the drop down menu turning off on it's own Status in gnome-shell package in Ubuntu: Confirmed Bug description: tldr; Dark mode from the drop down menu turning off on it's own, resulting in mismatched theme across the shell. Description: Ubuntu 22.10 Release: 22.10 Gnome 43. Expected : Dark mode from the drop down menu matching the one from system settings. What happens : Dark mode from the drop down menu turning off on it's own. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993878/+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 1994015] [NEW] Crash when changing the screen layout with a switchable graphic
Public bug reported: On ubuntu 22.04, with switchable graphic enabled : - AMD Radeon Pro WX 4150 - Intel® UHD Graphics 630 if you try to change the screen layout. Gnome session crash and go back to GDM. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- 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/1994015 Title: Crash when changing the screen layout with a switchable graphic Status in gnome-settings-daemon package in Ubuntu: New Bug description: On ubuntu 22.04, with switchable graphic enabled : - AMD Radeon Pro WX 4150 - Intel® UHD Graphics 630 if you try to change the screen layout. Gnome session crash and go back to GDM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1994015/+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 1993878] Re: Theming issue on Gnome 43
** Package changed: ubuntu => gnome-shell (Ubuntu) -- 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/1993878 Title: Dark mode from the drop down menu turning off on it's own Status in gnome-shell package in Ubuntu: Confirmed Bug description: tldr; Dark mode from the drop down menu turning off on it's own, resulting in mismatched theme across the shell. Description: Ubuntu 22.10 Release: 22.10 Gnome 43. Expected : Dark mode from the drop down menu matching the one from system settings. What happens : Dark mode from the drop down menu turning off on it's own. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993878/+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 1994007] Re: totem show blackscreen when playing video repeatedly
OK it looks like the main problem is: Unsupported modifier, resource creation failed. XXX: resource creation failed which was previously reported incorrectly as a crash in bug 1972991. Please try uninstalling gstreamer1.0-vaapi and also look at https://github.com/intel/media-driver/issues/1498 ** Bug watch added: github.com/intel/media-driver/issues #1498 https://github.com/intel/media-driver/issues/1498 ** Changed in: totem (Ubuntu) Status: Incomplete => New ** Summary changed: - totem show blackscreen when playing video repeatedly + totem show black screen when playing video repeatedly [resource creation failed] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1994007 Title: totem show black screen when playing video repeatedly [resource creation failed] Status in OEM Priority Project: New Status in totem package in Ubuntu: New Bug description: [steps reproduce] 1. Install Ubuntu 22.04.1LTS. 2. Play Robotica_1080_convert.ogv with Videos(totem) with cycles. 3. some times after 10 mins, some times within 2 hours,find unit's videos show a black screen. Details please refer to the attachments. [failure rate] 100 [expected result] It should can play normally. [actual result] find unit's videos show blackscreen, [addtional infromation] totem: 42.0-1ubuntu1 gstreamer1.0-plugins-base 1.20.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994007/+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 1994000] Re: Can't log in anymore after setting MUTTER_DEBUG_FORCE_KMS_MODE=simple
Thanks. It looks like the problem is: oct 24 10:23:57 jorge-G5-KD gnome-shell[3546]: Failed to post KMS update: Failed to set mode 1920x1080_60.00 on CRTC 98: Invalid argument Although I also notice you have unsupported graphics packages installed: libdrm-amdgpu1 2.4.113+git2210180500.a81b9a~oibaf~j [origin: unknown] libdrm-common 2.4.113+git2210180500.a81b9a~oibaf~j [origin: unknown] libdrm-intel1 2.4.113+git2210180500.a81b9a~oibaf~j [origin: unknown] libdrm-nouveau2 2.4.113+git2210180500.a81b9a~oibaf~j [origin: unknown] libdrm-radeon1 2.4.113+git2210180500.a81b9a~oibaf~j [origin: unknown] libdrm2 2.4.113+git2210180500.a81b9a~oibaf~j [origin: unknown] Those packages happen to be responsible for the function that's failing above. I'm going to see if I can reproduce the bug with the supported packages before blaming the oibaf PPA. Although it does often cause bugs (which we can't fix or support here). -- 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/1994000 Title: Can't log in anymore after setting MUTTER_DEBUG_FORCE_KMS_MODE=simple Status in mutter package in Ubuntu: Incomplete Bug description: My laptop is running a Hybrid Nvidia RTX3060 + Intel i5 11400h graphics. After installing the Nvidia drivers and with Wayland (this doesn't happen with Xorg), once the screen is turned off (for example, by locking the screen or suspending the computer, it cannot be turned on. This is a behavior similarish to the one in bug 1968040 (IDK if that one was also triggered by a screen lock, this one gets triggered inmediately after turning off the screen for whatever reason). In 22.04, I solved it quite easily by setting MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0. As suggested in that ticket, I set this time MUTTER_DEBUG_FORCE_KMS_MODE=simple. I unfortunately cannot tell whether this would solve my issues because, when I reboot my computer with that variable, I simply cannot log in into my account. I type my password as usual (the login screen works perfectly, though) and then, once submited, the output is a black screen (LCD is on, though) and nothing shows up after. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 24 08:40:12 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-26 (27 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-20 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1994000/+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 1993878] [NEW] Theming issue on Gnome 43
You have been subscribed to a public bug: tldr; Dark mode from the drop down menu turning off on it's own, resulting in mismatched theme across the shell. Description:Ubuntu 22.10 Release:22.10 Gnome 43. Expected : Dark mode from the drop down menu matching the one from system settings. What happens : Dark mode from the drop down menu turning off on it's own. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bot-comment -- Theming issue on Gnome 43 https://bugs.launchpad.net/bugs/1993878 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell 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 1994000] Re: Can't log in anymore after setting MUTTER_DEBUG_FORCE_KMS_MODE=simple
I just switched to the non-atomic KMS (MUTTER_DEBUG_FORCE_KMS_MODE=simple). My computer turned to black and turned unusable. I wasn't able to Crtl+Alt+F3 and switch to the terminal at all. Hopefully, I was able to change the /etc/environment to the default with a live CD and was able to boot again to my computer normally. I can't see any crashes related to this (the last crash was yesterday, and this was a few minutes ago) in /var/crash. I can upload, though, the system log from the previous boot. ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1994000/+attachment/5626377/+files/prevboot.txt -- 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/1994000 Title: Can't log in anymore after setting MUTTER_DEBUG_FORCE_KMS_MODE=simple Status in mutter package in Ubuntu: Incomplete Bug description: My laptop is running a Hybrid Nvidia RTX3060 + Intel i5 11400h graphics. After installing the Nvidia drivers and with Wayland (this doesn't happen with Xorg), once the screen is turned off (for example, by locking the screen or suspending the computer, it cannot be turned on. This is a behavior similarish to the one in bug 1968040 (IDK if that one was also triggered by a screen lock, this one gets triggered inmediately after turning off the screen for whatever reason). In 22.04, I solved it quite easily by setting MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0. As suggested in that ticket, I set this time MUTTER_DEBUG_FORCE_KMS_MODE=simple. I unfortunately cannot tell whether this would solve my issues because, when I reboot my computer with that variable, I simply cannot log in into my account. I type my password as usual (the login screen works perfectly, though) and then, once submited, the output is a black screen (LCD is on, though) and nothing shows up after. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 24 08:40:12 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-26 (27 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-20 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1994000/+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 1994000] Re: Can't log in anymore after setting MUTTER_DEBUG_FORCE_KMS_MODE=simple
>From the file, it would seem it actually booted into the session but didn't show anything... -- 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/1994000 Title: Can't log in anymore after setting MUTTER_DEBUG_FORCE_KMS_MODE=simple Status in mutter package in Ubuntu: Incomplete Bug description: My laptop is running a Hybrid Nvidia RTX3060 + Intel i5 11400h graphics. After installing the Nvidia drivers and with Wayland (this doesn't happen with Xorg), once the screen is turned off (for example, by locking the screen or suspending the computer, it cannot be turned on. This is a behavior similarish to the one in bug 1968040 (IDK if that one was also triggered by a screen lock, this one gets triggered inmediately after turning off the screen for whatever reason). In 22.04, I solved it quite easily by setting MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0. As suggested in that ticket, I set this time MUTTER_DEBUG_FORCE_KMS_MODE=simple. I unfortunately cannot tell whether this would solve my issues because, when I reboot my computer with that variable, I simply cannot log in into my account. I type my password as usual (the login screen works perfectly, though) and then, once submited, the output is a black screen (LCD is on, though) and nothing shows up after. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 24 08:40:12 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-26 (27 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-20 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1994000/+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 1994007] Re: totem show blackscreen when playing video repeatedly
@Daniel, It should be Wayland, no nvidia card, and I could not find Xorg in 'ps -ef | grep X'. Please give it an hour or more when do testing. I could reproduce this issue on ThinkPad too. ** Attachment added: "lspci.log" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1994007/+attachment/5626378/+files/lspci.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1994007 Title: totem show blackscreen when playing video repeatedly Status in OEM Priority Project: New Status in totem package in Ubuntu: Incomplete Bug description: [steps reproduce] 1. Install Ubuntu 22.04.1LTS. 2. Play Robotica_1080_convert.ogv with Videos(totem) with cycles. 3. some times after 10 mins, some times within 2 hours,find unit's videos show a black screen. Details please refer to the attachments. [failure rate] 100 [expected result] It should can play normally. [actual result] find unit's videos show blackscreen, [addtional infromation] totem: 42.0-1ubuntu1 gstreamer1.0-plugins-base 1.20.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994007/+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 1994007] Re: totem show blackscreen when playing video repeatedly
Screenshot of this issue. ** Attachment added: "blackscreen.png" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1994007/+attachment/5626376/+files/blackscreen.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1994007 Title: totem show blackscreen when playing video repeatedly Status in OEM Priority Project: New Status in totem package in Ubuntu: Incomplete Bug description: [steps reproduce] 1. Install Ubuntu 22.04.1LTS. 2. Play Robotica_1080_convert.ogv with Videos(totem) with cycles. 3. some times after 10 mins, some times within 2 hours,find unit's videos show a black screen. Details please refer to the attachments. [failure rate] 100 [expected result] It should can play normally. [actual result] find unit's videos show blackscreen, [addtional infromation] totem: 42.0-1ubuntu1 gstreamer1.0-plugins-base 1.20.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994007/+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 1994011] Re: gnome-shell crashed with SIGSEGV in __strlen_avx2() from g_strjoinv() from init_secondary_gpu_data_gpu() from init_secondary_gpu_data() from create_renderer_gpu_da
Fix proposed: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2674 ** Changed in: gnome-shell (Ubuntu) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1994011 Title: gnome-shell crashed with SIGSEGV in __strlen_avx2() from g_strjoinv() from init_secondary_gpu_data_gpu() from init_secondary_gpu_data() from create_renderer_gpu_data_gbm() Status in gnome-shell package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 43.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/572031ecb97102a47da85c728ab7b98e918bb1bd contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994011/+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 1994000] Re: Can't log in anymore after setting MUTTER_DEBUG_FORCE_KMS_MODE=simple
Well, I wasn't using that one right now because, as I said, made me unable to use my computer. Will try to do as you suggest. -- 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/1994000 Title: Can't log in anymore after setting MUTTER_DEBUG_FORCE_KMS_MODE=simple Status in mutter package in Ubuntu: Incomplete Bug description: My laptop is running a Hybrid Nvidia RTX3060 + Intel i5 11400h graphics. After installing the Nvidia drivers and with Wayland (this doesn't happen with Xorg), once the screen is turned off (for example, by locking the screen or suspending the computer, it cannot be turned on. This is a behavior similarish to the one in bug 1968040 (IDK if that one was also triggered by a screen lock, this one gets triggered inmediately after turning off the screen for whatever reason). In 22.04, I solved it quite easily by setting MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0. As suggested in that ticket, I set this time MUTTER_DEBUG_FORCE_KMS_MODE=simple. I unfortunately cannot tell whether this would solve my issues because, when I reboot my computer with that variable, I simply cannot log in into my account. I type my password as usual (the login screen works perfectly, though) and then, once submited, the output is a black screen (LCD is on, though) and nothing shows up after. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 24 08:40:12 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-26 (27 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-20 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1994000/+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 1994011] Re: gnome-shell crashed with SIGSEGV in __strlen_avx2() from g_strjoinv() from init_secondary_gpu_data_gpu() from init_secondary_gpu_data() from create_renderer_gpu_da
** Tags added: multigpu -- 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/1994011 Title: gnome-shell crashed with SIGSEGV in __strlen_avx2() from g_strjoinv() from init_secondary_gpu_data_gpu() from init_secondary_gpu_data() from create_renderer_gpu_data_gbm() Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 43.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/572031ecb97102a47da85c728ab7b98e918bb1bd contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994011/+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 1952107] Re: Google Contacts API Deprecated
When will this fix be released also for Ubuntu 22.04 (Jammy Jellyfish)? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Fix Released Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Bionic: Triaged Status in evolution-data-server source package in Bionic: Triaged Status in evolution source package in Focal: Triaged Status in evolution-data-server source package in Focal: Triaged Status in evolution source package in Impish: Fix Released Status in evolution-data-server source package in Impish: Fix Released Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+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 1994011] Re: gnome-shell crashed with SIGSEGV in __strlen_avx2() from g_strjoinv() from init_secondary_gpu_data_gpu() from init_secondary_gpu_data() from create_renderer_gpu_da
** Summary changed: - /usr/bin/gnome-shell:11:__strlen_avx2:g_strjoinv:init_secondary_gpu_data_gpu:init_secondary_gpu_data:create_renderer_gpu_data_gbm + gnome-shell crashed with SIGSEGV in __strlen_avx2() from g_strjoinv() from init_secondary_gpu_data_gpu() from init_secondary_gpu_data() from create_renderer_gpu_data_gbm() -- 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/1994011 Title: gnome-shell crashed with SIGSEGV in __strlen_avx2() from g_strjoinv() from init_secondary_gpu_data_gpu() from init_secondary_gpu_data() from create_renderer_gpu_data_gbm() Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 43.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/572031ecb97102a47da85c728ab7b98e918bb1bd contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994011/+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 1994011] [NEW] gnome-shell crashed with SIGSEGV in __strlen_avx2() from g_strjoinv() from init_secondary_gpu_data_gpu() from init_secondary_gpu_data() from create_renderer_gpu_
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 43.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/572031ecb97102a47da85c728ab7b98e918bb1bd contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bionic focal jammy kinetic -- 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/1994011 Title: gnome-shell crashed with SIGSEGV in __strlen_avx2() from g_strjoinv() from init_secondary_gpu_data_gpu() from init_secondary_gpu_data() from create_renderer_gpu_data_gbm() Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 43.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/572031ecb97102a47da85c728ab7b98e918bb1bd contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994011/+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 1949183] Re: Cheese screenshot white screen and video freezes
On Ubuntu 22.04 starting cheese from terminal i see nothing for many seconds and then a message: corrado@corrado-n2-jammy:~$ cheese (cheese:3226): cheese-WARNING **: 09:40:13.862: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) and cheese window opens with a message: These was an error playing video... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1949183 Title: Cheese screenshot white screen and video freezes Status in OEM Priority Project: New Status in cheese package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 development branch with kernel 5.13.0-19-generic on wayland and Xorg When taking webcam pictures with cheese on wayland and xorg, it takes the picture but gives me a few seconds of white screen after the shot When taking a webcam video it takes a freezed picture instead of a video and has problems to push the stop recording button --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: Notebook N7x0WU Package: cheese 3.38.0-4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 RelatedPackageVersions: cheese3.38.0-4 cheese-common 3.38.0-4 Tags: wayland-session jammy gstreamer-error Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: Notebook N7x0WU Package: cheese 3.38.0-4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 RelatedPackageVersions: cheese3.38.0-4 cheese-common 3.38.0-4 Tags: wayland-session jammy gstreamer-error Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1949183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1994010] Re: gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from mozilla::detail::IntrinsicMemoryOps
This is the top gnome-shell crasher in kinetic. Although not totally
new, it is almost non-existent in jammy.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1994010
Title:
gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from
mozilla::detail::IntrinsicMemoryOps::load()
Status in gjs package in Ubuntu:
New
Status in gnome-shell package in Ubuntu:
New
Status in mozjs102 package in Ubuntu:
New
Bug description:
gnome-shell crashed with SIGSEGV:
#0 std::__atomic_base::load (__m=std::memory_order_relaxed,
this=0x0) at /usr/include/c++/12/bits/atomic_base.h:486
__b = std::memory_order_relaxed
#1 mozilla::detail::IntrinsicMemoryOps::load (aPtr=...) at
.././debian/build/dist/include/mozilla/Atomics.h:195
No locals.
#2 mozilla::detail::AtomicBaseIncDec::operator unsigned long (this=0x0) at
.././debian/build/dist/include/mozilla/Atomics.h:340
No locals.
#3 js::gc::CellWithTenuredGCPointer::headerPtr
(this=0x0) at .././js/src/gc/Cell.h:802
No locals.
#4 JSObject::shape (this=, this=) at
.././js/src/vm/JSObject.h:99
No locals.
#5 JSObject::nonCCWRealm (this=0x0) at .././js/src/vm/JSObject.h:413
No locals.
#6 JSContext::enterRealmOf (target=0x0, this=0x561efe351c00) at
.././js/src/vm/JSContext-inl.h:318
No locals.
#7 JSAutoRealm::JSAutoRealm (this=, cx=,
target=, this=, cx=,
target=) at .././js/src/jsapi.cpp:519
No locals.
#8 0x7f9b4910db2a in gjs_object_set_gproperty (object=,
property_id=, value=0x7ffc738467d0, pspec=0x561efe19be10) at
../gi/gobject.cpp:209
priv =
cx = 0x561efe351c00
js_obj = {> = { = {stack = 0x561efe351c18, prev = 0x0},
}, >> =
{ >> =
{, void>> = {}, }, }, ptr = 0x0}
ar = {cx_ = 0x561efe351c00, oldRealm_ = 0x0}
...
https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1994010/+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 1994010] [NEW] gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from mozilla::detail::IntrinsicMemoryOps
Public bug reported:
gnome-shell crashed with SIGSEGV:
#0 std::__atomic_base::load (__m=std::memory_order_relaxed,
this=0x0) at /usr/include/c++/12/bits/atomic_base.h:486
__b = std::memory_order_relaxed
#1 mozilla::detail::IntrinsicMemoryOps::load (aPtr=...) at
.././debian/build/dist/include/mozilla/Atomics.h:195
No locals.
#2 mozilla::detail::AtomicBaseIncDec::operator unsigned long (this=0x0) at
.././debian/build/dist/include/mozilla/Atomics.h:340
No locals.
#3 js::gc::CellWithTenuredGCPointer::headerPtr
(this=0x0) at .././js/src/gc/Cell.h:802
No locals.
#4 JSObject::shape (this=, this=) at
.././js/src/vm/JSObject.h:99
No locals.
#5 JSObject::nonCCWRealm (this=0x0) at .././js/src/vm/JSObject.h:413
No locals.
#6 JSContext::enterRealmOf (target=0x0, this=0x561efe351c00) at
.././js/src/vm/JSContext-inl.h:318
No locals.
#7 JSAutoRealm::JSAutoRealm (this=, cx=,
target=, this=, cx=,
target=) at .././js/src/jsapi.cpp:519
No locals.
#8 0x7f9b4910db2a in gjs_object_set_gproperty (object=,
property_id=, value=0x7ffc738467d0, pspec=0x561efe19be10) at
../gi/gobject.cpp:209
priv =
cx = 0x561efe351c00
js_obj = {>
= { = {stack = 0x561efe351c18, prev = 0x0}, }, >> =
{ >> =
{, void>> = {}, }, }, ptr = 0x0}
ar = {cx_ = 0x561efe351c00, oldRealm_ = 0x0}
...
https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71
** Affects: gjs (Ubuntu)
Importance: Undecided
Status: New
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Affects: mozjs102 (Ubuntu)
Importance: Undecided
Status: New
** Tags: jammy kinetic
** Also affects: mozjs102 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gjs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1994010
Title:
gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from
mozilla::detail::IntrinsicMemoryOps::load()
Status in gjs package in Ubuntu:
New
Status in gnome-shell package in Ubuntu:
New
Status in mozjs102 package in Ubuntu:
New
Bug description:
gnome-shell crashed with SIGSEGV:
#0 std::__atomic_base::load (__m=std::memory_order_relaxed,
this=0x0) at /usr/include/c++/12/bits/atomic_base.h:486
__b = std::memory_order_relaxed
#1 mozilla::detail::IntrinsicMemoryOps::load (aPtr=...) at
.././debian/build/dist/include/mozilla/Atomics.h:195
No locals.
#2 mozilla::detail::AtomicBaseIncDec::operator unsigned long (this=0x0) at
.././debian/build/dist/include/mozilla/Atomics.h:340
No locals.
#3 js::gc::CellWithTenuredGCPointer::headerPtr
(this=0x0) at .././js/src/gc/Cell.h:802
No locals.
#4 JSObject::shape (this=, this=) at
.././js/src/vm/JSObject.h:99
No locals.
#5 JSObject::nonCCWRealm (this=0x0) at .././js/src/vm/JSObject.h:413
No locals.
#6 JSContext::enterRealmOf (target=0x0, this=0x561efe351c00) at
.././js/src/vm/JSContext-inl.h:318
No locals.
#7 JSAutoRealm::JSAutoRealm (this=, cx=,
target=, this=, cx=,
target=) at .././js/src/jsapi.cpp:519
No locals.
#8 0x7f9b4910db2a in gjs_object_set_gproperty (object=,
property_id=, value=0x7ffc738467d0, pspec=0x561efe19be10) at
../gi/gobject.cpp:209
priv =
cx = 0x561efe351c00
js_obj = {> = { = {stack = 0x561efe351c18, prev = 0x0},
}, >> =
{ >> =
{, void>> = {}, }, }, ptr = 0x0}
ar = {cx_ = 0x561efe351c00, oldRealm_ = 0x0}
...
https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1994010/+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 1994007] Re: totem show blackscreen when playing video repeatedly
I can't reproduce this yet. Can you attach output from 'lspci -k' and tell if it's just Wayland or just Xorg? ** Tags added: jammy ** Changed in: totem (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1994007 Title: totem show blackscreen when playing video repeatedly Status in OEM Priority Project: New Status in totem package in Ubuntu: Incomplete Bug description: [steps reproduce] 1. Install Ubuntu 22.04.1LTS. 2. Play Robotica_1080_convert.ogv with Videos(totem) with cycles. 3. some times after 10 mins, some times within 2 hours,find unit's videos show a black screen. Details please refer to the attachments. [failure rate] 100 [expected result] It should can play normally. [actual result] find unit's videos show blackscreen, [addtional infromation] totem: 42.0-1ubuntu1 gstreamer1.0-plugins-base 1.20.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994007/+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 1994007] Re: totem show blackscreen when playing video repeatedly
I didn't find any errors with below debugging method. G_MESSAGES_DEBUG=all totem XXX.ogv GST_DEBUG_NO_COLOR=1 GST_DEBUG=*:2 totem XXX.ogv -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1994007 Title: totem show blackscreen when playing video repeatedly Status in OEM Priority Project: New Status in totem package in Ubuntu: New Bug description: [steps reproduce] 1. Install Ubuntu 22.04.1LTS. 2. Play Robotica_1080_convert.ogv with Videos(totem) with cycles. 3. some times after 10 mins, some times within 2 hours,find unit's videos show a black screen. Details please refer to the attachments. [failure rate] 100 [expected result] It should can play normally. [actual result] find unit's videos show blackscreen, [addtional infromation] totem: 42.0-1ubuntu1 gstreamer1.0-plugins-base 1.20.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994007/+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 1994000] Re: Can't log in anymore after setting MUTTER_DEBUG_FORCE_KMS_MODE=simple
Thanks for the bug report. I can see bug 1968040 in the log, but that also shows that atomic KMS is in use whereas this bug should be about non-atomic KMS failing (MUTTER_DEBUG_FORCE_KMS_MODE=simple). Please check for any crashes using https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment Please also collect a system log from when MUTTER_DEBUG_FORCE_KMS_MODE=simple was in use. If it was the previous boot then run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Summary changed: - Laptop screen can't be turned on after suspension or locking + Can't log in anymore after setting MUTTER_DEBUG_FORCE_KMS_MODE=simple ** Tags added: hybrid i915 multigpu nvidia ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1994000 Title: Can't log in anymore after setting MUTTER_DEBUG_FORCE_KMS_MODE=simple Status in mutter package in Ubuntu: Incomplete Bug description: My laptop is running a Hybrid Nvidia RTX3060 + Intel i5 11400h graphics. After installing the Nvidia drivers and with Wayland (this doesn't happen with Xorg), once the screen is turned off (for example, by locking the screen or suspending the computer, it cannot be turned on. This is a behavior similarish to the one in bug 1968040 (IDK if that one was also triggered by a screen lock, this one gets triggered inmediately after turning off the screen for whatever reason). In 22.04, I solved it quite easily by setting MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0. As suggested in that ticket, I set this time MUTTER_DEBUG_FORCE_KMS_MODE=simple. I unfortunately cannot tell whether this would solve my issues because, when I reboot my computer with that variable, I simply cannot log in into my account. I type my password as usual (the login screen works perfectly, though) and then, once submited, the output is a black screen (LCD is on, though) and nothing shows up after. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 24 08:40:12 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-26 (27 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-20 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1994000/+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 1994007] Re: totem show blackscreen when playing video repeatedly
Testing video ** Attachment added: "Robotica_1080_convert.ogv" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1994007/+attachment/5626369/+files/Robotica_1080_convert.ogv ** Tags added: oem-priority originate-from-1992321 sutton -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1994007 Title: totem show blackscreen when playing video repeatedly Status in OEM Priority Project: New Status in totem package in Ubuntu: New Bug description: [steps reproduce] 1. Install Ubuntu 22.04.1LTS. 2. Play Robotica_1080_convert.ogv with Videos(totem) with cycles. 3. some times after 10 mins, some times within 2 hours,find unit's videos show a black screen. Details please refer to the attachments. [failure rate] 100 [expected result] It should can play normally. [actual result] find unit's videos show blackscreen, [addtional infromation] totem: 42.0-1ubuntu1 gstreamer1.0-plugins-base 1.20.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994007/+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 1994007] [NEW] totem show blackscreen when playing video repeatedly
Public bug reported: [steps reproduce] 1. Install Ubuntu 22.04.1LTS. 2. Play Robotica_1080_convert.ogv with Videos(totem) with cycles. 3. some times after 10 mins, some times within 2 hours,find unit's videos show a black screen. Details please refer to the attachments. [failure rate] 100 [expected result] It should can play normally. [actual result] find unit's videos show blackscreen, [addtional infromation] totem: 42.0-1ubuntu1 gstreamer1.0-plugins-base 1.20.1-1 ** Affects: oem-priority Importance: Undecided Status: New ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1992321 sutton -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1994007 Title: totem show blackscreen when playing video repeatedly Status in OEM Priority Project: New Status in totem package in Ubuntu: New Bug description: [steps reproduce] 1. Install Ubuntu 22.04.1LTS. 2. Play Robotica_1080_convert.ogv with Videos(totem) with cycles. 3. some times after 10 mins, some times within 2 hours,find unit's videos show a black screen. Details please refer to the attachments. [failure rate] 100 [expected result] It should can play normally. [actual result] find unit's videos show blackscreen, [addtional infromation] totem: 42.0-1ubuntu1 gstreamer1.0-plugins-base 1.20.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994007/+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 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Hello Daniel. Thanks for your help, see bug 1994000. -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 1994000] [NEW] Laptop screen can't be turned on after suspension or locking
Public bug reported: My laptop is running a Hybrid Nvidia RTX3060 + Intel i5 11400h graphics. After installing the Nvidia drivers and with Wayland (this doesn't happen with Xorg), once the screen is turned off (for example, by locking the screen or suspending the computer, it cannot be turned on. This is a behavior similarish to the one in bug 1968040 (IDK if that one was also triggered by a screen lock, this one gets triggered inmediately after turning off the screen for whatever reason). In 22.04, I solved it quite easily by setting MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0. As suggested in that ticket, I set this time MUTTER_DEBUG_FORCE_KMS_MODE=simple. I unfortunately cannot tell whether this would solve my issues because, when I reboot my computer with that variable, I simply cannot log in into my account. I type my password as usual (the login screen works perfectly, though) and then, once submited, the output is a black screen (LCD is on, though) and nothing shows up after. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 24 08:40:12 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-26 (27 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-20 (3 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1994000 Title: Laptop screen can't be turned on after suspension or locking Status in gnome-shell package in Ubuntu: New Bug description: My laptop is running a Hybrid Nvidia RTX3060 + Intel i5 11400h graphics. After installing the Nvidia drivers and with Wayland (this doesn't happen with Xorg), once the screen is turned off (for example, by locking the screen or suspending the computer, it cannot be turned on. This is a behavior similarish to the one in bug 1968040 (IDK if that one was also triggered by a screen lock, this one gets triggered inmediately after turning off the screen for whatever reason). In 22.04, I solved it quite easily by setting MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0. As suggested in that ticket, I set this time MUTTER_DEBUG_FORCE_KMS_MODE=simple. I unfortunately cannot tell whether this would solve my issues because, when I reboot my computer with that variable, I simply cannot log in into my account. I type my password as usual (the login screen works perfectly, though) and then, once submited, the output is a black screen (LCD is on, though) and nothing shows up after. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 24 08:40:12 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-26 (27 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-20 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994000/+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 1993912] Re: GNOME screen recorder drops vast majority of frames
*** This bug is a duplicate of bug 1987631 *** https://bugs.launchpad.net/bugs/1987631 That's the fix for bug 1987631 so we can merge with that. ** This bug has been marked a duplicate of bug 1987631 Screencast only records one second -- 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/1993912 Title: GNOME screen recorder drops vast majority of frames Status in gnome-shell package in Ubuntu: New Bug description: When I try to record a region on my screen, after about 4 seconds the frames stop updating. In the attached video, I am toggling between the two visible windows every half second, roughly. The only frame updates after 0:04 occur at 0:33, 1:07, and 1:40. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 12:13:30 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-01 (174 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993912/+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 1993920] Re: Some windows overflow to other monitors whenever they're near to border and wider than main screen
*** This bug is a duplicate of bug 1990563 *** https://bugs.launchpad.net/bugs/1990563 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 1990563, 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: xorg (Ubuntu) => mutter (Ubuntu) ** This bug has been marked a duplicate of bug 1990563 Some maximized windows appear on both monitors -- 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/1993920 Title: Some windows overflow to other monitors whenever they're near to border and wider than main screen Status in mutter package in Ubuntu: New Bug description: After upgrading to Ubuntu 22.10, some applications (for example, VSCode and MySQL Workbench) are presenting weird behavior: if I move it to the secondary monitor and maximize the window, it gets mirrored in the main monitor. I've made some tests and realized that this issue occurs if I place the application window near to the divisor between the two monitors and this window's width is greater than the main monitor's one. Here is a link to a video that shows this issue: https://youtu.be/FmYSgpwS6Bk ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 18:19:27 2022 DistUpgraded: 2022-10-20 20:40:37,319 DEBUG icon theme changed, re-reading DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Comet Lake UHD Graphics [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Comet Lake UHD Graphics [144d:c834] InstallationDate: Installed on 2022-10-15 (7 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: SAMSUNG ELECTRONICS CO., LTD. 550XCJ/550XCR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-21-generic root=UUID=46adeab8-b7f5-472d-b479-38b045a695ff ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-20 (1 days ago) dmi.bios.date: 02/23/2022 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P12RFH.054.220223.HC dmi.board.asset.tag: No Asset Tag dmi.board.name: NP550XCJ-KF1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLA664A0C-C01-G002-S0001+10.0.19041 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP12RFH.054.220223.HC:bd02/23/2022:br5.16:svnSAMSUNGELECTRONICSCO.,LTD.:pn550XCJ/550XCR:pvrP12RFH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP550XCJ-KF1BR:rvrSGLA664A0C-C01-G002-S0001+10.0.19041:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PRFH: dmi.product.family: Notebook 5 Series dmi.product.name: 550XCJ/550XCR dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PRFH dmi.product.version: P12RFH dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1993920/+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 1993935] Re: Bluetooth is not connecting to any of my phone or headsets [Intel 3165 8086:3166]
** Summary changed: - Bluetooth issue + Bluetooth is not connecting to any of my phone or headsets [Intel 3165 8086:3166] ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1993935 Title: Bluetooth is not connecting to any of my phone or headsets [Intel 3165 8086:3166] Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Bluetooth is not connecting to any of my phone or headsets ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: bluez 5.65-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 23 15:04:45 2022 InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b628 Chicony Electronics Co., Ltd EasyCamera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81H7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=a1ad31f9-4430-4654-856d-9a144597827d ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/29/2020 dmi.bios.release: 1.26 dmi.bios.vendor: LENOVO dmi.bios.version: 8QCN26WW(V1.14) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 130-15IKB dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnLENOVO:bvr8QCN26WW(V1.14):bd12/29/2020:br1.26:efr1.26:svnLENOVO:pn81H7:pvrLenovoideapad130-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad130-15IKB:skuLENOVO_MT_81H7_BU_idea_FM_ideapad130-15IKB: dmi.product.family: ideapad 130-15IKB dmi.product.name: 81H7 dmi.product.sku: LENOVO_MT_81H7_BU_idea_FM_ideapad 130-15IKB dmi.product.version: Lenovo ideapad 130-15IKB dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A8:6D:AA:B9:23:31 ACL MTU: 1021:5 SCO MTU: 96:6 DOWN RX bytes:1914 acl:9 sco:0 events:106 errors:0 TX bytes:1359 acl:10 sco:0 commands:83 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1993935/+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 1987631] Re: Screencast only records one second
>From the upstream bug: > I think we can close this given that the workaround that has now been > released in 43 and 42.5 is all we can do from the shell side and the > required pipewire 0.3.57 has been out for a while now as well. ** Tags added: fixed-in-gnome-shell-42.5 fixed-in-gnome-shell-43.rc fixed-upstream ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Fix Released ** Also affects: gnome-shell (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Jammy) Status: New => Fix Released ** Changed in: gnome-shell (Ubuntu Jammy) Status: Fix Released => Fix Committed -- 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/1987631 Title: Screencast only records one second Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Committed Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1993892] Re: Window area is unusable
Thanks for the bug report. Please try deleting any local extensions: cd ~/.local/share/gnome-shell/ rm -rf extensions and then log in again. If the problem still occurs then next time it does please: 1. Wait 10 seconds. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1993892 Title: Window area is unusable Status in gnome-shell package in Ubuntu: Incomplete Bug description: The window area becomes unusable without warning and the same visual artefacts are seen (see attached). The system taskbar is still responsive, so I can logout/login, which resolves the issues temporarily. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 16:10:38 2022 DistUpgraded: 2022-10-21 06:47:07,363 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:2081] InstallationDate: Installed on 2022-10-14 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Intel(R) Client Systems NUC10i5FNH ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_6w0xyh@/vmlinuz-5.19.0-21-generic root=ZFS=rpool/ROOT/ubuntu_6w0xyh ro quiet splash vt.handoff=1 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago) dmi.bios.date: 04/09/2021 dmi.bios.release: 5.16 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0052.2021.0409.1144 dmi.board.asset.tag: Default string dmi.board.name: NUC10i5FNB dmi.board.vendor: Intel Corporation dmi.board.version: M38063-307 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0052.2021.0409.1144:bd04/09/2021:br5.16:efr3.9:svnIntel(R)ClientSystems:pnNUC10i5FNH:pvrM38014-308:rvnIntelCorporation:rnNUC10i5FNB:rvrM38063-307:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC10i5FNHN: dmi.product.family: FN dmi.product.name: NUC10i5FNH dmi.product.sku: BXNUC10i5FNHN dmi.product.version: M38014-308 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993892/+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 1993912] Re: GNOME screen recorder drops vast majority of frames
** Tags added: amdgpu -- 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/1993912 Title: GNOME screen recorder drops vast majority of frames Status in gnome-shell package in Ubuntu: New Bug description: When I try to record a region on my screen, after about 4 seconds the frames stop updating. In the attached video, I am toggling between the two visible windows every half second, roughly. The only frame updates after 0:04 occur at 0:33, 1:07, and 1:40. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 12:13:30 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-01 (174 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993912/+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 1993926] Re: No icon in tray and integration in menu when someone is connected
This orange screencast icon is only shown in Wayland sessions. In x11, any application can listen to input for any application (including passwords) and peek at their rendered content, so it is pointless to show that icon in x11 sessions too, since with no icon shown, applications can still spy on others there. In any case, it is not g-r-d, that shows that icon, but gnome-shell, when either a remote desktop session or screencast session was created. ** Changed in: gnome-remote-desktop (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1993926 Title: No icon in tray and integration in menu when someone is connected Status in gnome-remote-desktop package in Ubuntu: Invalid Bug description: I'm running an up to date Ubuntu 22.04.1 LTS using X. A friend of mine is having the same hardware and it's fully functional. Just few extensions but even I I disable everything still no orange icon and no integration, got no info. It's working perfectly, just a tiny bug. Anything I can provide to help? ... if you can provide commands I can do it. OS: Ubuntu 22.04.1 LTS Kernel: 5.15.0-52-generic Package: 42.4-0ubuntu1 *** 42.4-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-4ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1993926/+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 1993864] Re: Nautilus extension for gnome-console bad localization
** Tags added: jammy ** Package changed: mutter (Ubuntu) => gnome-console (Ubuntu) -- 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/1993864 Title: Nautilus extension for gnome-console bad localization Status in gnome-console package in Ubuntu: New Bug description: I've installed the nautilus-extension-gnome-console to have a right click item in Nautilus to open the current folder in Console, but it doesn't match my system language (French) and keeps displaying "Open in Console"). Tested on Ubuntu 22.04 with : - nautilus-extension-gnome-console 42~beta-1 - libnautilus-extension1a:amd64 1:42.2-0ubuntu1 - nautilus 1:42.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-console/+bug/1993864/+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 1993806] Re: Bluetooth not turning on and not connecting to my device [8087:0aaa Intel Corp. Bluetooth 9460/9560]
This is probably a kernel or firmware bug. Please try using the officially supported Ubuntu kernel (5.15.0-52.58) and/or try a newer upstream kernel like https://kernel.ubuntu.com/~kernel- ppa/mainline/v6.0.3/amd64/ ** Summary changed: - bluetooth not turning on and not connectting to my device + Bluetooth not turning on and not connecting to my device [8087:0aaa Intel Corp. Bluetooth 9460/9560] ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1993806 Title: Bluetooth not turning on and not connecting to my device [8087:0aaa Intel Corp. Bluetooth 9460/9560] Status in linux package in Ubuntu: Incomplete Bug description: Yesterday I connect my bluettoh phone in my new computer with Ubuntu 22.04, then today I wasnt able to reconect my phone, I tryes to disconect it in ubuntu interface, but this doesnt disconect, but no sound come from my earphone, then I tryed to turn bluetooth off, and it doesnt turn in again now. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluetooth (not installed) Uname: Linux 5.19.2-051902-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 21 08:37:09 2022 InstallationDate: Installed on 2022-08-18 (63 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Positivo Bahia - VAIO VJFE44F11X-B2111H ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.2-051902-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2022 dmi.bios.release: 5.24 dmi.bios.version: V1.19.X dmi.board.asset.tag: Default string dmi.board.name: VJFE-ADLBAT55 dmi.board.vendor: Positivo Tecnologia SA dmi.board.version: 11179464 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Positivo Tecnologia SA dmi.chassis.version: Default string dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvn:bvrV1.19.X:bd06/17/2022:br5.24:efr1.14:svnPositivoBahia-VAIO:pnVJFE44F11X-B2111H:pvrV1.19.X:rvnPositivoTecnologiaSA:rnVJFE-ADLBAT55:rvr11179464:cvnPositivoTecnologiaSA:ct10:cvrDefaultstring:sku3343073: dmi.product.family: VJFE44 dmi.product.name: VJFE44F11X-B2111H dmi.product.sku: 3343073 dmi.product.version: V1.19.X dmi.sys.vendor: Positivo Bahia - VAIO hciconfig: hci0:Type: Primary Bus: USB BD Address: 70:32:17:8B:A0:FF ACL MTU: 1021:4 SCO MTU: 96:6 DOWN RX bytes:2874357 acl:298 sco:0 events:409778 errors:0 TX bytes:251252400 acl:406246 sco:0 commands:3297 errors:0 syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993806/+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 1993831] Re: gnome-shell does not contain gjs dependence
** Tags added: kinetic -- 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/1993831 Title: gnome-shell does not contain gjs dependence Status in gnome-shell package in Ubuntu: Triaged Bug description: Hi, I updated from Ubuntu 22.04 to Ubuntu 22.10 and I had an issue with GNOME shell "Extensions" app. I replaced "Extensions" (gnome-shell-extension-prefs) with Flatpak version of it from Flathub using GNOME "Software" center. After this, I'm not sure, I might have used the "sudo apt auto-remove" command. After these changes, Flatpak version of the "Extensions" app gave an error: (https://github.com/flathub/org.gnome.Extensions/issues/13) After a bit of digging, I realized removing "Extensions" packages also removes gjs dependence. So I installed gjs package and "Extensions" works again. 1) OS OS: Ubuntu 22.10 Desktop: GNOME 2) Package gnome-shell: 43.0-1ubuntu2 gnome-shell-extension-prefs: 43.0-1ubuntu2 3) What you expected to happen Removing the package and installing Flatpak version without any error. 4) What happened instead I replaced the app with Flatpak version and it removed gjs and gnome- shell extension support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993831/+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
