[Desktop-packages] [Bug 1887005] Re: Untranslatable "Ratio:" in compact view
The fix has been released with 4.0.0 . ** Changed in: transmission (Ubuntu) Status: Fix Committed => Fix Released -- 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/1887005 Title: Untranslatable "Ratio:" in compact view Status in transmission package in Ubuntu: Fix Released Bug description: It is impossible now to translate "Ratio:" string in compact torrent list. Please apply the patch to fix the issue. https://git.launchpad.net/ubuntu/+source/transmission/tree/gtk/torrent- cell-renderer.c?id=3a7bff14283a3962b181bd1a9dc870cc356eaffe#n219 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1887005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 930821] Re: file names should have a tooltip
The fix has been released with 2.42 ** Changed in: transmission (Ubuntu) Status: Fix Committed => Fix Released -- 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/930821 Title: file names should have a tooltip Status in transmission package in Ubuntu: Fix Released Bug description: Sometimes filenames are too long to be displayed and are trunked. If you are only interested in downloading some of the files, a tooltip on file names is most usefull, especialy if the files have the same prefix and you need to check the endings. The alternative is to increase the size of the name column and then to scroll to the right. Personally, I find the tooltip version more convenient. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/930821/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1059136] Re: Up arrow and down arrow not rendered properly in web interface
This has been fixed for a long time. ** Changed in: transmission (Ubuntu) Status: Confirmed => Fix Released -- 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/1059136 Title: Up arrow and down arrow not rendered properly in web interface Status in Transmission: Fix Released Status in transmission package in Ubuntu: Fix Released Bug description: The up arrow and down arrow for each torrent aren't rendered as arrows, but instead as the text '' and ''. I've attached a screenshot of this in both Firefox and Chromium (transmission- arrows.png). When I create an html document using those character references I see actual arrows, so my assumption is that Transmission's doing these in a 'wrong' way, rather than that my browsers aren't supporting them properly. I've also attached a screenshot of that, in case I've used the wrong terminology somewhere above. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: transmission-common 2.61-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 ApportVersion: 2.5.2-0ubuntu4 Architecture: amd64 Date: Sun Sep 30 16:45:59 2012 Dependencies: InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120910) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: transmission UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/transmission/+bug/1059136/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking
I'm merging the fix for bug 2054510 into the same updates so please wait... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2051074 Title: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking Status in HWE Next: New Status in OEM Priority Project: New Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: In Progress Status in mutter source package in Mantic: In Progress Status in mutter source package in Noble: Fix Committed Bug description: [Impact] On systems equipped with reduced blanking panel, mirror mode can result to no image on external monitor. The reason is due to current fallback modes don't have pixelclock for reduced blanking, so inadequate refresh rate is used to mode set, and result with atomic commit failure. [Fix] https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3449 Add reduced blanking (RB) to fallback modes, so mutter can use RB mode to meet pixelclock requirement in order to pick the right refresh rate. [Test] Connect an external monitor to affected system. Use the monitor hotkey to switch to mirror mode or use GNOME control center to choose mirror mode. With the patch included, the issue is no longer observed. [Where problems could occur] The modelines of reduced blanking have reversed Hsync and Vsync flags, so if the driver doesn't handle those flags correctly, the atomic modeset/commit may fail. I haven't observe any issue on Intel/AMD/Nvidia GPU so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054510] Re: Incomplete screen redraws in virtual machines running Xorg
** Tags added: regression-release -- 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/2054510 Title: Incomplete screen redraws in virtual machines running Xorg Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: In Progress Status in mutter source package in Mantic: Triaged Status in mutter source package in Noble: Fix Committed Bug description: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. 3. Open Settings > About and verify Graphics = llvmpipe and Windowing System = X11. 4. sudo snap install chromium 5. Open Chromium and find a web page with lots of text. Plain text without any links and staying at the top of the page will work best because you don't want to trigger any scrolling. 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. Avoid triggering any page scrolling. 7. Release the mouse button in roughly the middle of the area of text that was selected. 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 due to https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking
** Changed in: mutter (Ubuntu Jammy) Status: New => In Progress ** Changed in: mutter (Ubuntu Mantic) Status: New => In Progress ** Changed in: mutter (Ubuntu Jammy) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Changed in: mutter (Ubuntu Mantic) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Changed in: mutter (Ubuntu Noble) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2051074 Title: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking Status in HWE Next: New Status in OEM Priority Project: New Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: In Progress Status in mutter source package in Mantic: In Progress Status in mutter source package in Noble: Fix Committed Bug description: [Impact] On systems equipped with reduced blanking panel, mirror mode can result to no image on external monitor. The reason is due to current fallback modes don't have pixelclock for reduced blanking, so inadequate refresh rate is used to mode set, and result with atomic commit failure. [Fix] https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3449 Add reduced blanking (RB) to fallback modes, so mutter can use RB mode to meet pixelclock requirement in order to pick the right refresh rate. [Test] Connect an external monitor to affected system. Use the monitor hotkey to switch to mirror mode or use GNOME control center to choose mirror mode. With the patch included, the issue is no longer observed. [Where problems could occur] The modelines of reduced blanking have reversed Hsync and Vsync flags, so if the driver doesn't handle those flags correctly, the atomic modeset/commit may fail. I haven't observe any issue on Intel/AMD/Nvidia GPU so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2053289] Re: Internal microphone realtek ALC257 is not working in 24.04 Noble (Fujitsu WU4/H1)
The solution listed here works for my case above: https://github.com/thesofproject/linux/issues/2460#issuecomment-779212719 ** Bug watch added: github.com/thesofproject/linux/issues #2460 https://github.com/thesofproject/linux/issues/2460 -- 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/2053289 Title: Internal microphone realtek ALC257 is not working in 24.04 Noble (Fujitsu WU4/H1) Status in alsa-driver package in Ubuntu: New Bug description: I tried to record sound with my internal Mic. Nothing is working. I use arecord. ``` bagus:~$ arecord test.wav arecord: main:834: audio open error: Operation not supported bagus:~$ arecord -d 10 -f cd -t wav -D copy foobar.wav ALSA lib pcm.c:2675:(snd_pcm_open_noupdate) Unknown PCM copy arecord: main:834: audio open error: No such file or directory bagus:~$ arecord -l List of CAPTURE Hardware Devices card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 6: DMIC (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 7: DMIC16kHz (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 bagus:~$ lsb_release -rd No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 bagus:~$ apt-cache policy alsa-base alsa-base: Installed: (none) Candidate: 1.0.25+dfsg-0ubuntu7 Version table: 1.0.25+dfsg-0ubuntu7 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2053289/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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] Re: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all
** Bug watch added: github.com/PJungkamp/yoga9-linux/issues #11 https://github.com/PJungkamp/yoga9-linux/issues/11 -- 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 thornley.david from comment #819) > I am running an 14IRP8 (Yoga Pro/Slim 9i), specifically this model > (https://psref.lenovo.com/Detail/Yoga/Yoga_Pro_9_14IRP8?M=83BU0024AU). > > I have the laptop running Ubuntu 23.10 and I run mainline kernels from > Ubuntu. I have tried almost every recent kernel build up until 6.8-rc5 today > (I had read that 6.8 was supposed to fix this issue). Audio is still running > only the tweaters, zero bass. > > I've tried many things, notably the snd.conf (options > snd-sof-intel-hda-common hda_model=alc287-yoga9-bass-spk-pin) to no avail. > Also tried noble's firmware-sof-signed package, manually tweaking the amixer > configuration. > > My alsa info -> > https://alsa-project.org/db/?f=634d31445ad5a7c4a023cdb15a07dea2a4048437 > > Thanks!! Do you have full volume sound? I have a similar model (https://psref.lenovo.com/Detail/Lenovo/Lenovo_Slim_Pro_9_14IRP8?M=83BV0002US) and had to do a few things to make the amplifier work in the first place, but I still don't have any bass. To get sound on linux 6.7 I had to update the firmware files and use `options snd-sof-intel-hda-common hda_model=17aa:38be`, which had a different effect to alc287-yoga9-bass-spk-pin (not sure why). I described with more details at https://github.com/PJungkamp/yoga9-linux/issues/11#issuecomment-1899400594 I didn't try a lot on 6.8 but my current config doesn't fix the bass there too. -- 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]
Could you share your acpidump output? -- 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]
Based on alsa-info, its subsystem ID is: 0x17aa38be It's here in the patch_realtek.c: SND_PCI_QUIRK(0x17aa, 0x38be, "Yoga S980-14.5 proX YC Dual", ALC287_FIXUP_TAS2781_I2C), snd_hda_scodec_tas2781_i2c loaded. Could you run this as well? dmesg|grep 2781 -- 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 noticed that patch is present in the kernel I am running... "dmesg | grep 2781" yields nothing. "lsmod" indicates snd_hda_scodec_tas2781_i2c is loaded. I'm quite green with the audio subsystem in linux, so pretty overwhelmed and suprised how complicated it is :) I'm not 100% sure, but it sounds like there is firmware and associated tuning values present in the EFI system that are also required. One other thing I noticed, running "i2cdetect -r 3" doesn't report any probed addresses. -r 1 has one at 0x14, -r 2 has at 0x2c, less that I think expected based on other similar posts. -- 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 thornley.david from comment #819) > I am running an 14IRP8 (Yoga Pro/Slim 9i), specifically this model > (https://psref.lenovo.com/Detail/Yoga/Yoga_Pro_9_14IRP8?M=83BU0024AU). Not sure what the cause of this is, but there is no specific mention of "14IRP8" in any of the kernel code, so I guess there is still no specific support for your issue, unfortunately. Possibly the fix would be as simple as the commit which fixed it for the 16IRH8 (just several lines of code https://github.com/torvalds/linux/commit/99af5b11c57d33c32d761797f6308b40936c22ed), but I don't know enough about any of this to say for sure. -- 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 2054510] Re: Incomplete screen redraws in virtual machines running Xorg
** Description changed: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. 3. Open Settings > About and verify Graphics = llvmpipe and Windowing System = X11. 4. sudo snap install chromium 5. Open Chromium and find a web page with lots of text. Plain text without any links and staying at the top of the page will work best because you don't want to trigger any scrolling. 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. Avoid triggering any page scrolling. 7. Release the mouse button in roughly the middle of the area of text that was selected. 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] - This is a regression that started in 3.37.3 via 551101c65cda. + This is a regression that started in 3.37.3 due to + https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda. -- 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/2054510 Title: Incomplete screen redraws in virtual machines running Xorg Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: In Progress Status in mutter source package in Mantic: Triaged Status in mutter source package in Noble: Fix Committed Bug description: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. 3. Open Settings > About and verify Graphics = llvmpipe and Windowing System = X11. 4. sudo snap install chromium 5. Open Chromium and find a web page with lots of text. Plain text without any links and staying at the top of the page will work best because you don't want to trigger any scrolling. 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. Avoid triggering any page scrolling. 7. Release the mouse button in roughly the middle of the area of text that was selected. 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 due to https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034298] Re: [82YU, Realtek ALC257, Mic, Internal] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/2034298 Title: [82YU, Realtek ALC257, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Though playback works fine through inbuilt speakers, the inbuilt microphone in Ubuntu 22.04.3 installed in Lenovo V15 Gen4 AMN (AMD Ryzen 5 7520U with Radeon Graphics) laptop does not work. For now, the work is being managed by attaching an external headphohe set to listen to and record audio. Hence, please look into this matter and provide a solution.By the way, to confirm that there is defect the hardware, Windows Home was installed and microphone was found to be working absolutely fine there. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pradip 1503 F pulseaudio /dev/snd/controlC0: pradip 1503 F pulseaudio /dev/snd/controlC1: pradip 1503 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 00:24:21 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording 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: pradip 1503 F pulseaudio /dev/snd/controlC0: pradip 1503 F pulseaudio /dev/snd/controlC1: pradip 1503 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [82YU, Realtek ALC257, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2023 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: L1CN30WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V15 G4 AMN dmi.ec.firmware.release: 1.30 dmi.modalias: dmi:bvnLENOVO:bvrL1CN30WW:bd04/27/2023:br1.30:efr1.30:svnLENOVO:pn82YU:pvrLenovoV15G4AMN:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV15G4AMN:skuLENOVO_MT_82YU_BU_idea_FM_V15G4AMN: dmi.product.family: V15 G4 AMN dmi.product.name: 82YU dmi.product.sku: LENOVO_MT_82YU_BU_idea_FM_V15 G4 AMN dmi.product.version: Lenovo V15 G4 AMN dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2034298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043119] Re: screen color calibration : no start button
I just butted up against this same problem!!! -- 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/2043119 Title: screen color calibration : no start button Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I try to calibrate my screen using the utility of gnome-control-center, color section. I have a Spyder3 Express probe connected by USB and the Calibrate… button become active. So I click this button and the process begin with a dialog box giving several informations until it ask for the name of the further colour profile. After that, a small window appears asking to put the probe on this window and to press "Start"… but there is no Start button. I tried the same on Ubuntu 22.04 (on a VM) : the same window occupied all the screen and we can see a Start button at the bottom right and a Cancel one on the bottom left. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 9 15:58:51 2023 InstallationDate: Installed on 2020-04-10 (1308 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-10-13 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2043119/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2053289] Re: Internal microphone realtek ALC257 is not working in 24.04 Noble (Fujitsu WU4/H1)
** Summary changed: - Internal microphone is not working in 24.04 (Fujitsu WU4/H1) + Internal microphone realtek ALC257 is not working in 24.04 Noble (Fujitsu WU4/H1) ** Tags added: alc257 -- 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/2053289 Title: Internal microphone realtek ALC257 is not working in 24.04 Noble (Fujitsu WU4/H1) Status in alsa-driver package in Ubuntu: New Bug description: I tried to record sound with my internal Mic. Nothing is working. I use arecord. ``` bagus:~$ arecord test.wav arecord: main:834: audio open error: Operation not supported bagus:~$ arecord -d 10 -f cd -t wav -D copy foobar.wav ALSA lib pcm.c:2675:(snd_pcm_open_noupdate) Unknown PCM copy arecord: main:834: audio open error: No such file or directory bagus:~$ arecord -l List of CAPTURE Hardware Devices card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 6: DMIC (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 7: DMIC16kHz (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 bagus:~$ lsb_release -rd No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 bagus:~$ apt-cache policy alsa-base alsa-base: Installed: (none) Candidate: 1.0.25+dfsg-0ubuntu7 Version table: 1.0.25+dfsg-0ubuntu7 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2053289/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054560] Re: Xorg freeze: i915 flips and commits are timing out
Next time the problem happens please: 1. Reboot. 2. Run: journalctl -b-1 > prevboot.txt 3. Attach the resulting text file here. ** Summary changed: - Xorg freeze + Xorg freeze: i915 flips and commits are timing out ** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu) ** Changed in: linux-hwe-6.5 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2054560 Title: Xorg freeze: i915 flips and commits are timing out Status in linux-hwe-6.5 package in Ubuntu: Incomplete Bug description: Random freezes occur since the installation of 6.5.x kernel. Freeze occur several times a day, probably after touching the mouse or keyboard, but I'm not sure. App continue to work sound is OK, there is just no dispay updated. Booting to old 6.2 kernel solves the problem. I have tried all 6.5 updates since the first released, but each time, I had a freeze after a few hours. Example of last mesg in dmesg when freeze occur : Feb 21 11:03:59 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 21 11:04:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:04:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 21 11:04:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 21 11:05:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:05:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 21 11:05:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:05:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:274:DP-5] commit wait timed out Feb 21 11:05:22 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 21 11:05:32 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:05:32 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 21 11:05:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:05:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:274:DP-5] commit wait timed out Feb 21 11:05:53 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 21 11:06:03 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:06:03 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 21 11:06:13 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:06:13 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:274:DP-5] commit wait timed out Feb 21 11:06:23 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out or : Feb 13 10:37:18 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 13 10:39:06 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 10:39:06 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 13 11:22:09 pf46avw7 kernel: perf: interrupt took too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 79750 Feb 13 11:35:00 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 13 11:35:10 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:35:10 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 13 11:35:21 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:35:21 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:282:DP-5] commit wait timed out Feb 13 11:35:31 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 13 11:35:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:35:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 13 11:35:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:35:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:282:DP-5] commit wait timed out Feb 13 11:36:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 13 11:36:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:36:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 13 11:36:22 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:36:22 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:282:DP-5] commit wait timed out
[Desktop-packages] [Bug 2054319] Re: System installed from jammy point release iso cannot upgrade to noble
Please use 'ubuntu-bug' to report each crash file so the robots can analyse and classify them. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2054319 Title: System installed from jammy point release iso cannot upgrade to noble Status in gnome-shell package in Ubuntu: New Status in policykit-1 package in Ubuntu: New Status in tracker-miners package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: We have different crashes being encountered. In our auto-upgrade- testing, we see gnome-shell crash, however, when testing locally, I didn't experience this. @hyask did experience the gnome-shell crash though. When running an upgrade from jammy to noble in a virsh vm, about halfway through the upgrade process my gui dies. I then ran the upgrade from a console, to which it revealed that just the gui dies - the upgrade process, for me, continues and then laterally fails. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader-core 1:24.04.7 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu7 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:1000:124:1592041:2024-02-19 14:26:22.564354912 +:2024-02-19 14:51:56.318947066 +:/var/crash/_usr_libexec_tracker-extract-3.1000.crash 600:0:124:833806:2024-02-19 14:34:18.370597600 +:2024-02-19 14:34:19.370597600 +:/var/crash/polkitd.0.crash Date: Mon Feb 19 14:53:39 2024 InstallationDate: Installed on 2024-02-19 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to noble on 2024-02-19 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: pkexec must be setuid root VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.init.d.apport: 2024-02-14T15:51:44 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054627] Re: Chromium fails to launch/startup up
I just updated the system. There were a few KDE updates that were performed. After a reboot the issue went away. It seems this might of been related to KDE as I recall I occasionally had issue launching apps from the GUI. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2054627 Title: Chromium fails to launch/startup up Status in chromium-browser package in Ubuntu: New Bug description: Chromium fails to start up from the KDE interface. I click the icon and nothing happen. When I launch Chromium from the terminal it launches but I get the following output in the terminal: (chrome:55656): Gtk-WARNING **: 20:39:23.626: Theme parsing error: gtk.css:1:21: Failed to import: Error opening file /home/user/snap/chromium/2757/.config/gtk-3.0/colors.css: No such file or directory Gtk-Message: 20:39:23.666: Failed to load module "colorreload-gtk-module" Gtk-Message: 20:39:23.666: Failed to load module "window-decorations-gtk-module" [55656:55656:0221/203923.708230:ERROR:policy_logger.cc(156)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(161) Cloud management controller initialization aborted as CBCM is not enabled. Please use the `--enable-chrome-browser-cloud-management` command line flag to enable it if you are not using the official Google Chrome build. (chrome:55656): IBUS-WARNING **: 20:39:24.041: Failed to mkdir /home/user/snap/chromium/2757/.config/ibus/bus: Not a directory ProblemType: Bug DistroRelease: Ubuntu 24.04 Uname: Linux 6.7.5-060705-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu7 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 21 20:40:07 2024 InstallationDate: Installed on 2024-02-17 (5 days ago) InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240213) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Snap: chromium 121.0.6167.184 (stable) SnapChanges: ID Status Spawn Ready Summary 4Done2024-02-21T19:35:25-06:00 2024-02-21T19:35:59-06:00 Install "chromium" snap SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2054627/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054627] [NEW] Chromium fails to launch/startup up
Public bug reported: Chromium fails to start up from the KDE interface. I click the icon and nothing happen. When I launch Chromium from the terminal it launches but I get the following output in the terminal: (chrome:55656): Gtk-WARNING **: 20:39:23.626: Theme parsing error: gtk.css:1:21: Failed to import: Error opening file /home/user/snap/chromium/2757/.config/gtk-3.0/colors.css: No such file or directory Gtk-Message: 20:39:23.666: Failed to load module "colorreload-gtk-module" Gtk-Message: 20:39:23.666: Failed to load module "window-decorations-gtk-module" [55656:55656:0221/203923.708230:ERROR:policy_logger.cc(156)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(161) Cloud management controller initialization aborted as CBCM is not enabled. Please use the `--enable-chrome-browser-cloud-management` command line flag to enable it if you are not using the official Google Chrome build. (chrome:55656): IBUS-WARNING **: 20:39:24.041: Failed to mkdir /home/user/snap/chromium/2757/.config/ibus/bus: Not a directory ProblemType: Bug DistroRelease: Ubuntu 24.04 Uname: Linux 6.7.5-060705-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu7 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 21 20:40:07 2024 InstallationDate: Installed on 2024-02-17 (5 days ago) InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240213) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Snap: chromium 121.0.6167.184 (stable) SnapChanges: ID Status Spawn Ready Summary 4Done2024-02-21T19:35:25-06:00 2024-02-21T19:35:59-06:00 Install "chromium" snap SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2054627 Title: Chromium fails to launch/startup up Status in chromium-browser package in Ubuntu: New Bug description: Chromium fails to start up from the KDE interface. I click the icon and nothing happen. When I launch Chromium from the terminal it launches but I get the following output in the terminal: (chrome:55656): Gtk-WARNING **: 20:39:23.626: Theme parsing error: gtk.css:1:21: Failed to import: Error opening file /home/user/snap/chromium/2757/.config/gtk-3.0/colors.css: No such file or directory Gtk-Message: 20:39:23.666: Failed to load module "colorreload-gtk-module" Gtk-Message: 20:39:23.666: Failed to load module "window-decorations-gtk-module" [55656:55656:0221/203923.708230:ERROR:policy_logger.cc(156)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(161) Cloud management controller initialization aborted as CBCM is not enabled. Please use the `--enable-chrome-browser-cloud-management` command line flag to enable it if you are not using the official Google Chrome build. (chrome:55656): IBUS-WARNING **: 20:39:24.041: Failed to mkdir /home/user/snap/chromium/2757/.config/ibus/bus: Not a directory ProblemType: Bug DistroRelease: Ubuntu 24.04 Uname: Linux 6.7.5-060705-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu7 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 21 20:40:07 2024 InstallationDate: Installed on 2024-02-17 (5 days ago) InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240213) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Snap: chromium 121.0.6167.184 (stable) SnapChanges: ID Status Spawn Ready Summary 4Done2024-02-21T19:35:25-06:00 2024-02-21T19:35:59-06:00 Install "chromium" snap SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2054627/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054510] Re: Incomplete screen redraws in virtual machines running Xorg
** Tags added: udeng-1928 ** Tags added: fixed-in-mutter-46.0 fixed-upstream -- 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/2054510 Title: Incomplete screen redraws in virtual machines running Xorg Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: In Progress Status in mutter source package in Mantic: Triaged Status in mutter source package in Noble: Fix Committed Bug description: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. 3. Open Settings > About and verify Graphics = llvmpipe and Windowing System = X11. 4. sudo snap install chromium 5. Open Chromium and find a web page with lots of text. Plain text without any links and staying at the top of the page will work best because you don't want to trigger any scrolling. 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. Avoid triggering any page scrolling. 7. Release the mouse button in roughly the middle of the area of text that was selected. 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 via 551101c65cda. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970800] Re: Clicking a calendar date in the bottom row of the panel calendar causes a graphical glitch
still happens on 22.04 LTS… ** Attachment added: "Capture d’écran du 2024-02-22 02-56-56.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970800/+attachment/5748290/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202024-02-22%2002-56-56.png -- 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/1970800 Title: Clicking a calendar date in the bottom row of the panel calendar causes a graphical glitch Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: If you click a calendar date in the bottom row of the top panel calendar, the backdrop shrinks and the dates overflow out of the backdrop boundaries. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-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..02.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 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 28 16:25:17 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] CometLake-U GT2 [UHD Graphics] [1462:129c] Subsystem: Micro-Star International Co., Ltd. [MSI] TU117M [GeForce GTX 1650 Mobile / Max-Q] [1462:129c] InstallationDate: Installed on 2022-04-22 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2019 dmi.bios.release: 1.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16S3IMS.108 dmi.board.asset.tag: Default string dmi.board.name: MS-16S3 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku16S3.1: dmi.product.family: Prestige dmi.product.name: Prestige 15 A10SC dmi.product.sku: 16S3.1 dmi.product.version: REV:1.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.0.1-1ubuntu2 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.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/gnome-shell/+bug/1970800/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2053235] Re: Upgrade libwayland to 1.22.0
Same for Weston 13.0. But since it's Nvidia asking, maybe we can help some other way? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2053235 Title: Upgrade libwayland to 1.22.0 Status in wayland package in Ubuntu: Fix Released Status in wayland source package in Jammy: New Status in wayland source package in Mantic: Fix Released Status in wayland source package in Noble: Fix Released Bug description: We look to use / upgrade to Weston 13.0 on Ubuntu 22.04.3 LTS. We see the following Weston-13.0 dependencies are not met for the same. libwayland*: required version >= 1.22.0 So we request to upgrade these packages on Ubuntu 22.04.3 LTS. The release of Ubuntu we are using: - Ubuntu 22.04.3 LTS Current version of the libwayland* packages: - libwayland-bin/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-client0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-cursor0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-dev/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-egl1/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-server0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] What we expect to happen: - We want the upgrade of libwayland* packages to 1.22.0 on Ubuntu 22.04.3 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2053235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054517] Re: webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions
*** This bug is a duplicate of bug 2037015 *** https://bugs.launchpad.net/bugs/2037015 If it's just appeared in 22.04.4 then Mesa might be to blame, but this looks more likely: https://launchpad.net/ubuntu/+source/webkit2gtk/2.42.5-0ubuntu0.22.04.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2054517 Title: webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions Status in mesa package in Ubuntu: New Status in webkit2gtk package in Ubuntu: New Bug description: webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions. Assuming it doesn't crash first. You first see the corruption in the initial setup wizard on first boot of noble-preinstalled-desktop-arm64+raspi.img.xz but the same corruption is then visible in the Help app on Xorg. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libwebkit2gtk-4.1-0 2.43.3-1 ProcVersionSignature: Ubuntu 6.5.0-1005.7-raspi 6.5.3 Uname: Linux 6.5.0-1005-raspi aarch64 ApportVersion: 2.27.0-0ubuntu7 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Feb 21 14:38:56 2024 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: webkit2gtk UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2054517/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037015] Re: Screen corruption of slides during install on Raspberry Pi 4
Same issue in Yelp (the Help app) when in Xorg sessions. So I think this is a webkit2gtk bug that only manifests on Xorg (like our installer/live sessions). Also I have removed the series targets because they were getting cluttered and likely targeting the wrong package anyway. ** Also affects: webkit2gtk (Ubuntu) Importance: Undecided Status: New ** Tags added: noble ** No longer affects: ubiquity (Ubuntu Jammy) ** No longer affects: ubiquity (Ubuntu Mantic) ** No longer affects: ubiquity (Ubuntu Noble) ** No longer affects: webkit2gtk (Ubuntu Jammy) ** No longer affects: webkit2gtk (Ubuntu Mantic) ** No longer affects: webkit2gtk (Ubuntu Noble) ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Confirmed ** Changed in: webkit2gtk (Ubuntu) Status: New => Confirmed ** Tags added: raspi raspigfx -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2037015 Title: Screen corruption of slides during install on Raspberry Pi 4 Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2037015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054517] Re: webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions
*** This bug is a duplicate of bug 2037015 *** https://bugs.launchpad.net/bugs/2037015 ** This bug has been marked a duplicate of bug 2037015 Screen corruption of slides during install on Raspberry Pi 4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2054517 Title: webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions Status in mesa package in Ubuntu: New Status in webkit2gtk package in Ubuntu: New Bug description: webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions. Assuming it doesn't crash first. You first see the corruption in the initial setup wizard on first boot of noble-preinstalled-desktop-arm64+raspi.img.xz but the same corruption is then visible in the Help app on Xorg. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libwebkit2gtk-4.1-0 2.43.3-1 ProcVersionSignature: Ubuntu 6.5.0-1005.7-raspi 6.5.3 Uname: Linux 6.5.0-1005-raspi aarch64 ApportVersion: 2.27.0-0ubuntu7 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Feb 21 14:38:56 2024 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: webkit2gtk UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2054517/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054612] Re: soffice.bin crashed with SIGSEGV in rtl_uString_release()
*** This bug is a duplicate of bug 2052384 *** https://bugs.launchpad.net/bugs/2052384 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2052384, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2054612/+attachment/5748250/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/2054612/+attachment/5748252/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2054612/+attachment/5748255/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2054612/+attachment/5748256/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/2054612/+attachment/5748257/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2054612/+attachment/5748258/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2054612/+attachment/5748259/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 2052384 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2054612 Title: soffice.bin crashed with SIGSEGV in rtl_uString_release() Status in libreoffice package in Ubuntu: New Bug description: soffice.bin crashed with SIGSEGV in rtl_uString_release() ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: libreoffice-core 4:24.2.0~rc1-0ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu7 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: XFCE Date: Wed Feb 21 19:11:14 2024 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2024-02-03 (19 days ago) InstallationMedia: Xubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240202) JournalErrors: Feb 21 19:11:17 hostname systemd[1894]: launchpadlib-cache-clean.service: Failed with result 'exit-code'. Feb 21 19:11:17 hostname systemd[1894]: Failed to start launchpadlib-cache-clean.service - Clean up old files in the Launchpadlib cache. ProcAttrCurrent: libreoffice-soffice (complain) ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc file:///home/username/Dropbox/Dropbox%20Raiz%20Pogorelsky/Docpog/01-Docpog%20Principal/Documentos/Arquivo.xls --splash-pipe=5 SegvAnalysis: Segfault happened at: 0x763fc3988c64 :mov (%rdi),%eax PC (0x763fc3988c64) ok source "(%rdi)" (0x763face324c0) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: libreoffice StacktraceTop: rtl_uString_release () from /usr/lib/libreoffice/program/libuno_sal.so.3 ?? () from /usr/lib/libreoffice/program/libmergedlo.so ?? () from /usr/lib/libreoffice/program/libmergedlo.so __run_exit_handlers (status=0, listp=0x763fbe1fe680 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at ./stdlib/exit.c:111 __GI_exit (status=) at ./stdlib/exit.c:141 Title: soffice.bin crashed with SIGSEGV in rtl_uString_release() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip fax floppy lpadmin plugdev sambashare sudo tape users video separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2054612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
This bug was fixed in the package plasma-welcome - 5.27.10-1ubuntu1 --- plasma-welcome (5.27.10-1ubuntu1) noble; urgency=low [ Ubuntu Merge-o-Matic ] * Merge from Debian unstable. Remaining changes: - Kubuntu Vcs and maintainer fields. [ Scarlett Moore ] * Add apparmor profile to fix userns. Ref: LP: #2046844 * Release to archive. plasma-welcome (5.27.10-1) unstable; urgency=medium [ Patrick Franz ] * New upstream release (5.27.10). -- Scarlett Moore Wed, 21 Feb 2024 04:23:15 -0700 ** Changed in: plasma-welcome (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bubblewrap in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akonadiconsole package in Ubuntu: In Progress Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Committed Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kgeotag package in Ubuntu: In Progress Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Committed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2046844/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)
My personal thoughts are that the proposal is nothing if not carefully considered...! Lots of great discussion and input. There is plenty of opportunity for people to provide feedback on whether or how the change impacts them in ways we were unable to foresee. On Tue, Feb 20, 2024 at 11:31 PM Christian Ehrhardt < 1833...@bugs.launchpad.net> wrote: > While there was sadly neither enough time not enough resources to do all > the deep dive analysis that could have been done, we succeeded by > reaching out to many more parties and got their input as well. Thank you > all! > > Since Noble feature freeze is coming we need to make a call either way. > I proposed the underlying seed change [1]. > And even once accepted that has to be followed by an update to ubuntu-meta. > Furthermore we'd have more follow up, like enabling it in special cases > like the AWS images for the reasons Fabio mentioned. > > Of course this is just a proposal. There are many other options left, > from not changing anything to more subtle counters to my proposal like > only doing so in 24.10 to give things more time, to holding back until > someone found time/resource to gather more data. > > But for now, I feel "Not enabling it by default, but enabling > selectively where identified to be wanted" seems to be the better choice > - and that is what I proposed. > > [1]: https://code.launchpad.net/~paelzer/ubuntu- > seeds/+git/platform/+merge/460904 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1833322 > > Title: > Please consider no more having irqbalance enabled by default (per > image/use-case/TBD) > > Status in Ubuntu on IBM z Systems: > Confirmed > Status in irqbalance package in Ubuntu: > Confirmed > Status in ubuntu-meta package in Ubuntu: > Confirmed > > Bug description: > as per https://github.com/pop-os/default-settings/issues/60 > > Distribution (run cat /etc/os-release): > > $ cat /etc/os-release > NAME="Pop!_OS" > VERSION="19.04" > ID=ubuntu > ID_LIKE=debian > PRETTY_NAME="Pop!_OS 19.04" > VERSION_ID="19.04" > HOME_URL="https://system76.com/pop; > SUPPORT_URL="http://support.system76.com; > BUG_REPORT_URL="https://github.com/pop-os/pop/issues; > PRIVACY_POLICY_URL="https://system76.com/privacy; > VERSION_CODENAME=disco > UBUNTU_CODENAME=disco > > Related Application and/or Package Version (run apt policy $PACKAGE > NAME): > > $ apt policy irqbalance > irqbalance: > Installed: 1.5.0-3ubuntu1 > Candidate: 1.5.0-3ubuntu1 > Version table: > *** 1.5.0-3ubuntu1 500 > 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages > 100 /var/lib/dpkg/status > > $ apt rdepends irqbalance > irqbalance > Reverse Depends: > Recommends: ubuntu-standard > gce-compute-image-packages > > Issue/Bug Description: > > as per konkor/cpufreq#48 and > http://konkor.github.io/cpufreq/faq/#irqbalance-detected > > irqbalance is technically not needed on desktop systems (supposedly it > is mainly for servers), and may actually reduce performance and power > savings. It appears to provide benefits only to server environments > that have relatively-constant loading. If it is truly a server- > oriented package, then it shouldn't be installed by default on a > desktop/laptop system and shouldn't be included in desktop OS images. > > Steps to reproduce (if you know): > > This is potentially an issue with all default installs. > > Expected behavior: > > n/a > > Other Notes: > > I can safely remove it via "sudo apt purge irqbalance" without any > apparent adverse side-effects. If someone is running a situation where > they need it, then they always have the option of installing it from > the repositories. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+subscriptions > > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Please consider no more having irqbalance enabled by default (per image/use-case/TBD) Status in Ubuntu on IBM z Systems: Confirmed Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed:
[Desktop-packages] [Bug 2054600] [NEW] nautilus crash changing tabs
Public bug reported: Crash while changing tabs. Unfortunately, nautilus crashes often on my system at random. I have submitted several bugs. Here is the crash file https://errors.ubuntu.com/oops/04da7342-d0ea-11ee-9d0e-fa163ec44ecd Ubuntu 23.10, nautilus 1:45~rc-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 21 18:50:16 2024 InstallationDate: Installed on 2023-06-06 (260 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) SourcePackage: nautilus UpgradeStatus: Upgraded to mantic on 2023-10-14 (130 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 nautilus-image-converter 0.4.0-2 python3-nautilus 4.0-1build1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic third-party-packages -- 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/2054600 Title: nautilus crash changing tabs Status in nautilus package in Ubuntu: New Bug description: Crash while changing tabs. Unfortunately, nautilus crashes often on my system at random. I have submitted several bugs. Here is the crash file https://errors.ubuntu.com/oops/04da7342-d0ea-11ee-9d0e-fa163ec44ecd Ubuntu 23.10, nautilus 1:45~rc-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 21 18:50:16 2024 InstallationDate: Installed on 2023-06-06 (260 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) SourcePackage: nautilus UpgradeStatus: Upgraded to mantic on 2023-10-14 (130 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 nautilus-image-converter 0.4.0-2 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2054600/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054111] Re: [SRU] libreoffice 7.6.5 for mantic
** Changed in: libreoffice (Ubuntu Mantic) Status: New => In Progress ** Description changed: [Impact] * LibreOffice 7.6.5 is in its fifth bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.5_release * Version 7.6.2 is currently released in mantic. For a list of fixed bugs compared to 7.6.4 see the list of bugs fixed in the release candidates of 7.6.5 (that's a total of ? bugs): https://wiki.documentfoundation.org/Releases/7.6.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.5/RC2#List_of_fixed_bugs - 7.6.5 RC1 is identical to the 7.6.5 release + 7.6.5 RC2 is identical to the 7.6.5 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_76/1816/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15791929/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/amd64/libr/libreoffice/20240216_132420_3c270@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/arm64/libr/libreoffice/20240216_140709_197f6@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/armhf/libr/libreoffice/20240216_222053_83134@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/ppc64el/libr/libreoffice/20240216_130131_fd665@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/s390x/libr/libreoffice/20240216_141429_f0d16@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of ? bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. ** Description changed: [Impact] * LibreOffice 7.6.5 is in its fifth bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.5_release - * Version 7.6.2 is currently released in mantic. For a list of fixed bugs compared to 7.6.4 see the list of bugs fixed in the release candidates of 7.6.5 (that's a total of ? bugs): + * Version 7.6.2 is currently released in mantic. For a list of fixed bugs compared to 7.6.4 see the list of bugs fixed in the release candidates of 7.6.5 (that's a total of 94 bugs): https://wiki.documentfoundation.org/Releases/7.6.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.5/RC2#List_of_fixed_bugs 7.6.5 RC2 is identical to the 7.6.5 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_76/1816/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests
[Desktop-packages] [Bug 1988754]
Tested in: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ef9e1116d1100af50d7b74dcee5155c81b7b50fb CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded I can still crash it by successively undoing a re-doing after inserting a page break once. It is quite inconsistent, once it crashed after 3 undo-redo cycles, once after 30+. Do you see the same thing? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1988754 Title: libreoffice writer crashes when edit the page break Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: New Bug description: LibreOffice Writes crashes when editing the page break. It happens in Xubuntu 22.04.1 and also in LinuxMint 21. I have tried also using LibreOffice from ppa and it still crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1988754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037017] Re: Sharing tab hangs gnome-control-center
Failed to reproduce this on the jammy .4 images during ISO testing. Possibility it's either fixed or only occurs on later versions. Will attempt to reproduce on mantic later, if I've got the time. -- 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/2037017 Title: Sharing tab hangs gnome-control-center Status in gnome-control-center package in Ubuntu: Confirmed Bug description: On the Ubuntu Desktop for Raspberry Pi current Mantic beta images (with gnome-control-center version 1.45.0-1ubuntu1), on a Raspberry Pi 4B, switching to the "Sharing" tab hangs the application (presenting the Force Quit / Wait overlay prompt). Worse, re-launching the application simply re-opens the "Sharing" tab resulting in another hang. A workaround for now is to launch the application from the command-line, forcing initial selection of a different tab, e.g. "gnome-control-center info-overview". Launching the application from the command line with "gnome-control- center sharing" also causes the hang, but unfortunately there's no additional console output to shed any light on the situation. I'm not sure if this is Pi specific (haven't attempted it on any other platforms yet). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037017/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054517] Re: webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions
This may be a duplicate of LP: #2037015 -- we saw this on mantic first, then noble, in the oem-config process (the first-time setup wizard). Previously it *didn't* affect jammy, but I'm currently running through the ISO tests for the jammy .4 release and it's cropped up there now as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2054517 Title: webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions Status in mesa package in Ubuntu: New Status in webkit2gtk package in Ubuntu: New Bug description: webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions. Assuming it doesn't crash first. You first see the corruption in the initial setup wizard on first boot of noble-preinstalled-desktop-arm64+raspi.img.xz but the same corruption is then visible in the Help app on Xorg. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libwebkit2gtk-4.1-0 2.43.3-1 ProcVersionSignature: Ubuntu 6.5.0-1005.7-raspi 6.5.3 Uname: Linux 6.5.0-1005-raspi aarch64 ApportVersion: 2.27.0-0ubuntu7 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Feb 21 14:38:56 2024 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: webkit2gtk UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2054517/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968907] Re: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Dear and beloved community, Just as recent as February 8th the issue still present on my machine: > hostnamectl Chassis: desktop Machine ID: d7cd3b4105a5434aa091038c06c945c8 Boot ID: f420ddad3eb744729c321f220a435897 Operating System: Ubuntu 22.04.3 LTS Kernel: Linux 6.5.0-17-generic Architecture: x86-64 Hardware Vendor: Dell Inc. Hardware Model: OptiPlex 3000 > journalctl | grep GLib-GIO-CRITICAL feb 08 11:20:04 04cpu-1138 gnome-session[1774]: gnome-session-binary[1774]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed feb 08 11:20:04 04cpu-1138 gnome-session[1774]: gnome-session-binary[1774]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed feb 08 11:20:04 04cpu-1138 gnome-session-binary[1774]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed feb 08 11:20:04 04cpu-1138 gnome-session-binary[1774]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed feb 08 11:40:42 04cpu-1138 gnome-session[1796]: gnome-session-binary[1796]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed feb 08 11:40:42 04cpu-1138 gnome-session[1796]: gnome-session-binary[1796]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed feb 08 11:40:42 04cpu-1138 gnome-session-binary[1796]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed feb 08 11:40:42 04cpu-1138 gnome-session-binary[1796]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed After reinstall Ubuntu in november 2023, I have avoid to install software via snap and the difference was that no more frequenlty blackouts were present, but that is only my experience though. I will attach my machine to the Ubuntu Pro subscription to check if, with the security updates it provides, something changes. ** Attachment added: "Logs for the GLib-GIO-CRITICAL gnome-session issue" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1968907/+attachment/5748203/+files/glib_gio_critical.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1968907 Title: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Status in gnome-session: Fix Released Status in gnome-session package in Ubuntu: Fix Released Bug description: Hi, I see the following errors in the system logs: # journalctl | grep gnome-session-binary Apr 13 18:22:54 vougeot gnome-session[3453]: gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 13 18:22:54 vougeot gnome-session[3453]: gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 13 18:22:54 vougeot gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 13 18:22:54 vougeot gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-session-bin 42.0-1ubuntu2 Uname: Linux 5.17.2-051702-generic x86_64 ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Apr 13 19:48:49 2022 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1968907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2053235] Re: Upgrade libwayland to 1.22.0
I have doubts this will happen, as that's a new major upstream version and doesn't really fit the stable release update rules. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2053235 Title: Upgrade libwayland to 1.22.0 Status in wayland package in Ubuntu: Fix Released Status in wayland source package in Jammy: New Status in wayland source package in Mantic: Fix Released Status in wayland source package in Noble: Fix Released Bug description: We look to use / upgrade to Weston 13.0 on Ubuntu 22.04.3 LTS. We see the following Weston-13.0 dependencies are not met for the same. libwayland*: required version >= 1.22.0 So we request to upgrade these packages on Ubuntu 22.04.3 LTS. The release of Ubuntu we are using: - Ubuntu 22.04.3 LTS Current version of the libwayland* packages: - libwayland-bin/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-client0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-cursor0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-dev/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-egl1/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-server0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] What we expect to happen: - We want the upgrade of libwayland* packages to 1.22.0 on Ubuntu 22.04.3 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2053235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054183] Re: nautilus not generating thumbnails anymore
THANKS, I hadn't emptied the folder ~/.cache/thumbnails/fail/gnome- thumbnail-factory -- 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/2054183 Title: nautilus not generating thumbnails anymore Status in nautilus package in Ubuntu: Confirmed Bug description: After the upgrade to 24.04, nautilus is not generating thumbnails for new files. Old thumbnails are displayed ok. I cleaned out $HOME/.cache/thumbnails/ and found that only a subdirectory "fail" is being generated. It contains a subdirectory "gnome-thumbnail-factory" which in turn contains lots of PNG files: ece577c54f5ca98e1f7aaa5b4e932aa4.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced ee638c64b1c285684412717bf120e295.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced ef811735cfb8e69447b5d3a53f361c63.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced f0b3ab2f77c342daa3579bfcf9c72481.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced f0ddb101b8342e4b298b4c7121881422.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:45.2.1-4ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 17 08:49:55 2024 EcryptfsInUse: Yes InstallationDate: Installed on 2019-04-16 (1767 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nautilus UpgradeStatus: Upgraded to noble on 2024-02-14 (3 days ago) usr_lib_nautilus: file-roller 43.1-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2054183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 571229]
Created attachment 9381353 cioparseiproc19862186.txt Thanks from condamithin1983. -- 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/571229 Title: Menus are not shown when accessed by keys in full screen mode, but they work Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Status in firefox-3.5 package in Ubuntu: Triaged Bug description: Binary package hint: firefox-3.0 marcingo@idevele:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 9.10 Release: 9.10 Codename: karmic marcingo@idevele:~$ apt-cache policy firefox firefox: Installed: 3.5.9+nobinonly-0ubuntu0.9.10.1 Candidate: 3.5.9+nobinonly-0ubuntu0.9.10.1 Version table: *** 3.5.9+nobinonly-0ubuntu0.9.10.1 0 500 http://hu.archive.ubuntu.com karmic-updates/main Packages 500 http://security.ubuntu.com karmic-security/main Packages 100 /var/lib/dpkg/status 3.5.3+build1+nobinonly-0ubuntu6 0 500 http://hu.archive.ubuntu.com karmic/main Packages Ubuntu Netbook Remix Normal mode: I press Alt-F. The File menu appears. I can see that the key for print preview is V as it is underlined. I press V. The print preview appears. Fullscreen mode: I press Alt-F. The File menu does NOT appear. I press V just in case. The print preview appears. Always reproducible. Expected Results: The menu should be displayed upon the corresponding keypress in fullscreen mode as well. It is worst with the Bookmarks, because they change and by the time one memorizes a keystroke combination, a new bookmark or submenu will likely make it invalid. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/571229/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054319] Re: System installed from jammy point release iso cannot upgrade to noble
** Also affects: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Also affects: tracker-miners (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2054319 Title: System installed from jammy point release iso cannot upgrade to noble Status in gnome-shell package in Ubuntu: New Status in policykit-1 package in Ubuntu: New Status in tracker-miners package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: We have different crashes being encountered. In our auto-upgrade- testing, we see gnome-shell crash, however, when testing locally, I didn't experience this. @hyask did experience the gnome-shell crash though. When running an upgrade from jammy to noble in a virsh vm, about halfway through the upgrade process my gui dies. I then ran the upgrade from a console, to which it revealed that just the gui dies - the upgrade process, for me, continues and then laterally fails. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader-core 1:24.04.7 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu7 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:1000:124:1592041:2024-02-19 14:26:22.564354912 +:2024-02-19 14:51:56.318947066 +:/var/crash/_usr_libexec_tracker-extract-3.1000.crash 600:0:124:833806:2024-02-19 14:34:18.370597600 +:2024-02-19 14:34:19.370597600 +:/var/crash/polkitd.0.crash Date: Mon Feb 19 14:53:39 2024 InstallationDate: Installed on 2024-02-19 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to noble on 2024-02-19 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: pkexec must be setuid root VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.init.d.apport: 2024-02-14T15:51:44 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
** Description changed: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. + [ Workaround ] + + On most machines you can hide the problem by using these kernel parameters together: + quiet splash loglevel=2 fastboot + [ Test Plan ] - 1. Boot Ubuntu on a number of laptops that have the problem and verify - no console text messages appear during boot. - - 2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them - still. - - 3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages - should appear. + 1. Boot Ubuntu on a number of laptops that have the problem and verify no console text messages appear during boot. + 2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still. + 3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages should appear. [ Where problems could occur ] Since the fix works by deferring fbcon's takeover of the console, the main problem encountered during its development was the inability to VT switch. [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. ** Changed in: systemd (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: Won't Fix Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=2 fastboot [ Test Plan ] 1. Boot Ubuntu on a number of laptops that have the problem and verify no console text messages appear during boot. 2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still. 3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages should appear. [ Where problems could occur ] Since the fix works by deferring fbcon's takeover of the console, the main problem encountered during its development was the inability to VT switch. [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054560] [NEW] Xorg freeze
Public bug reported: Random freezes occur since the installation of 6.5.x kernel. Freeze occur several times a day, probably after touching the mouse or keyboard, but I'm not sure. App continue to work sound is OK, there is just no dispay updated. Booting to old 6.2 kernel solves the problem. I have tried all 6.5 updates since the first released, but each time, I had a freeze after a few hours. Example of last mesg in dmesg when freeze occur : Feb 21 11:03:59 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 21 11:04:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:04:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 21 11:04:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 21 11:05:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:05:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 21 11:05:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:05:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:274:DP-5] commit wait timed out Feb 21 11:05:22 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 21 11:05:32 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:05:32 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 21 11:05:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:05:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:274:DP-5] commit wait timed out Feb 21 11:05:53 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 21 11:06:03 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:06:03 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 21 11:06:13 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:06:13 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:274:DP-5] commit wait timed out Feb 21 11:06:23 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out or : Feb 13 10:37:18 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 13 10:39:06 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 10:39:06 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 13 11:22:09 pf46avw7 kernel: perf: interrupt took too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 79750 Feb 13 11:35:00 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 13 11:35:10 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:35:10 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 13 11:35:21 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:35:21 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:282:DP-5] commit wait timed out Feb 13 11:35:31 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 13 11:35:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:35:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 13 11:35:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:35:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:282:DP-5] commit wait timed out Feb 13 11:36:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 13 11:36:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:36:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 13 11:36:22 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:36:22 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:282:DP-5] commit wait timed out Feb 13 11:36:32 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 13 11:37:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:37:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out or Feb 01 09:37:11 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 01 09:37:23 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 01 09:37:23 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 01 09:37:45 pf46avw7 kernel: rfkill: input handler enabled Feb 01 09:37:55 pf46avw7 kernel: i915 :00:02.0: [drm]
[Desktop-packages] [Bug 2036388] Re: Login screen grey background flickers
** 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/2036388 Title: Login screen grey background flickers Status in gnome-shell package in Ubuntu: Triaged Bug description: Login screen grey background flickers on startup and again on login. It looks like it's trying to fade between two very similar shades of grey and there just aren't enough colours between them to fade smoothly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2036388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054510] Re: Incomplete screen redraws in virtual machines running Xorg
Noble will get the fix automatically with mutter 46.0 Jammy is the next most important release (especially to the customer) and is under review here: https://salsa.debian.org/gnome-team/mutter/-/merge_requests/120 ** Tags added: jammy mantic noble -- 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/2054510 Title: Incomplete screen redraws in virtual machines running Xorg Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: In Progress Status in mutter source package in Mantic: Triaged Status in mutter source package in Noble: Fix Committed Bug description: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. 3. Open Settings > About and verify Graphics = llvmpipe and Windowing System = X11. 4. sudo snap install chromium 5. Open Chromium and find a web page with lots of text. Plain text without any links and staying at the top of the page will work best because you don't want to trigger any scrolling. 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. Avoid triggering any page scrolling. 7. Release the mouse button in roughly the middle of the area of text that was selected. 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 via 551101c65cda. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054510] Re: Incomplete screen redraws in virtual machines running Xorg
** Changed in: mutter (Ubuntu Jammy) Status: Triaged => In Progress -- 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/2054510 Title: Incomplete screen redraws in virtual machines running Xorg Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: In Progress Status in mutter source package in Mantic: Triaged Status in mutter source package in Noble: Fix Committed Bug description: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. 3. Open Settings > About and verify Graphics = llvmpipe and Windowing System = X11. 4. sudo snap install chromium 5. Open Chromium and find a web page with lots of text. Plain text without any links and staying at the top of the page will work best because you don't want to trigger any scrolling. 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. Avoid triggering any page scrolling. 7. Release the mouse button in roughly the middle of the area of text that was selected. 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 via 551101c65cda. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047912] Re: There is a heap buffer overflow in texlive-bin
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-25262
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to texlive-bin in Ubuntu.
https://bugs.launchpad.net/bugs/2047912
Title:
There is a heap buffer overflow in texlive-bin
Status in texlive-bin package in Ubuntu:
New
Bug description:
Hello,
I found a heap-buffer overflow in function ttfLoadHDMX; ttfdump can install
by apt-get texlive-binaries. I compile lastest texlive-source by clone
https://github.com/TeX-Live/texlive-source/ on unbuntu for debugging.
The overflow content and size are controlled by input. Exploiting this
issue can achive any code excuted
The steps for reproducing the vul on unbuntu:
(1) sudo apt-get iunstall texlive-binaries
(2) ttfdump -i poc.ttf
The poc.ttf can view the attachment .ttfdump aborted and prompt "malloc():
corrupted top size" due memory corrupt.
The issue exist in function ttfLoadHDMX :
/***function ttfLoadHDMX begin ***/
static void ttfLoadHDMX (FILE *fp,HDMXPtr hdmx,ULONG offset)
{
int i;
xfseek(fp, offset, SEEK_SET, "ttfLoadHDMX");
hdmx->version = ttfGetUSHORT(fp);
hdmx->numDevices = ttfGetUSHORT(fp);
hdmx->size = ttfGetLONG(fp);
hdmx->Records = XCALLOC (hdmx->numDevices, DeviceRecord);
for (i=0;inumDevices;i++)
{
hdmx->Records[i].PixelSize = ttfGetBYTE(fp);
hdmx->Records[i].MaxWidth = ttfGetBYTE(fp);
hdmx->Records[i].Width = XCALLOC (hdmx->size, BYTE); (1)
fread ((hdmx->Records+i)->Width, sizeof(BYTE),
hdmx->numGlyphs+1,fp); (2)
}
}
/***function ttfLoadHDMX end ***/
At above code (1) ,allocte heap buffer for Width according to the parsed
hdmx width. And at above code (2) , copy Width content from file and copy size
decided by controlled hdmx->numGlyphs. In the poc , hdmx->size eaqual to 1216
and hdmx->numGlyphs+1 is 4155,which get heap buffer overflow.
/*** debug info ***/
(gdb) p hdmx->numGlyphs+1
$23 = 4155
(gdb) p hdmx->size
$24 = 1216
/*** debug info end ***/
From :
Dongzhuo zhao working with ADLab of Venustech
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-bin/+bug/2047912/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054510] Re: Incomplete screen redraws in virtual machines running Xorg
** Description changed: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. 3. Open Settings > About and verify Graphics = llvmpipe and Windowing System = X11. - 4. TODO + 4. sudo snap install chromium + 5. Open Chromium and find a web page with lots of text. + 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. + 7. Release the mouse button in roughly the middle of the area of text that was selected. + 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). + 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 via 551101c65cda. ** Description changed: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. 3. Open Settings > About and verify Graphics = llvmpipe and Windowing System = X11. 4. sudo snap install chromium - 5. Open Chromium and find a web page with lots of text. + 5. Open Chromium and find a web page with lots of text. Plain text without any links will work best. 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. 7. Release the mouse button in roughly the middle of the area of text that was selected. 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 via 551101c65cda. ** Description changed: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. 3. Open Settings > About and verify Graphics = llvmpipe and Windowing System = X11. 4. sudo snap install chromium - 5. Open Chromium and find a web page with lots of text. Plain text without any links will work best. + 5. Open Chromium and find a web page with lots of text. Plain text without any links and staying at the top of the page will work best. 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. 7. Release the mouse button in roughly the middle of the area of text that was selected. 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 via 551101c65cda. ** Description changed: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. 3. Open Settings > About and verify Graphics = llvmpipe and Windowing System = X11. 4. sudo snap install chromium - 5. Open Chromium and find a web page with lots of text. Plain text without any links and staying at the top of the page will work best. + 5. Open Chromium and find a web page with lots of text. Plain text without any links and staying at the top of the page will work best because you don't want to trigger any scrolling. 6. Start selecting text with the mouse and
Re: [Desktop-packages] [Bug 2047912] Re: There is a heap buffer overflow in texlive-bin
Hello!
I got the CVE ID (CVE-2024-25262) for this issue.
Thanks
dongzhuo zhao 于2024年2月19日周一 11:03写道：
> Hello，I have reported this issue to TexLive and the maintenance team have
> confirmed this issue and fixed it. they want me reuest CVE ID by myself.
> And Iasrequest a CVE ID, but do not get answer for this moment. If you
> could accelerate this requesting process, that would be great!
>
> George-Andrei Iosif <2047...@bugs.launchpad.net> 于2024年2月7日周三 16:29写道：
>
>> I have marked this bug as public because the public domain already
>> contains information about this TeX Live issue (as seen in the GitHub
>> issue and upstream changelog).
>>
>> @dongzhuo, could you please contact the upstream (either in the existing
>> PR or via their mailing list) to confirm that they (1) recognize this
>> issue as a vulnerability impacting the security of their software (and
>> not just a functional bug), and (2) do not have any other CVE ID
>> assignment process already established? The latter is important because
>> some projects prefer contacting MITRE for the assignment.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/2047912
>>
>> Title:
>> There is a heap buffer overflow in texlive-bin
>>
>> Status in texlive-bin package in Ubuntu:
>> New
>>
>> Bug description:
>> Hello,
>> I found a heap-buffer overflow in function ttfLoadHDMX; ttfdump can
>> install by apt-get texlive-binaries. I compile lastest texlive-source by
>> clone https://github.com/TeX-Live/texlive-source/ on unbuntu for
>> debugging.
>> The overflow content and size are controlled by input. Exploiting
>> this issue can achive any code excuted
>>
>> The steps for reproducing the vul on unbuntu:
>> (1) sudo apt-get iunstall texlive-binaries
>> (2) ttfdump -i poc.ttf
>>
>>
>> The poc.ttf can view the attachment .ttfdump aborted and prompt
>> "malloc(): corrupted top size" due memory corrupt.
>>
>> The issue exist in function ttfLoadHDMX :
>>
>> /***function ttfLoadHDMX begin ***/
>>
>> static void ttfLoadHDMX (FILE *fp,HDMXPtr hdmx,ULONG offset)
>> {
>> int i;
>>
>> xfseek(fp, offset, SEEK_SET, "ttfLoadHDMX");
>>
>> hdmx->version = ttfGetUSHORT(fp);
>> hdmx->numDevices = ttfGetUSHORT(fp);
>> hdmx->size = ttfGetLONG(fp);
>>
>> hdmx->Records = XCALLOC (hdmx->numDevices, DeviceRecord);
>>
>> for (i=0;inumDevices;i++)
>> {
>> hdmx->Records[i].PixelSize = ttfGetBYTE(fp);
>> hdmx->Records[i].MaxWidth = ttfGetBYTE(fp);
>> hdmx->Records[i].Width = XCALLOC (hdmx->size, BYTE); (1)
>> fread ((hdmx->Records+i)->Width, sizeof(BYTE),
>> hdmx->numGlyphs+1,fp); (2)
>> }
>> }
>>
>>
>> /***function ttfLoadHDMX end ***/
>>
>>
>> At above code (1) ,allocte heap buffer for Width according to the
>> parsed hdmx width. And at above code (2) , copy Width content from file and
>> copy size decided by controlled hdmx->numGlyphs. In the poc , hdmx->size
>> eaqual to 1216 and hdmx->numGlyphs+1 is 4155,which get heap buffer overflow.
>>
>> /*** debug info ***/
>> (gdb) p hdmx->numGlyphs+1
>> $23 = 4155
>> (gdb) p hdmx->size
>> $24 = 1216
>> /*** debug info end ***/
>>
>>
>> From :
>>
>> Dongzhuo zhao working with ADLab of Venustech
>>
>> To manage notifications about this bug go to:
>>
>> https://bugs.launchpad.net/ubuntu/+source/texlive-bin/+bug/2047912/+subscriptions
>>
>>
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to texlive-bin in Ubuntu.
https://bugs.launchpad.net/bugs/2047912
Title:
There is a heap buffer overflow in texlive-bin
Status in texlive-bin package in Ubuntu:
New
Bug description:
Hello,
I found a heap-buffer overflow in function ttfLoadHDMX; ttfdump can install
by apt-get texlive-binaries. I compile lastest texlive-source by clone
https://github.com/TeX-Live/texlive-source/ on unbuntu for debugging.
The overflow content and size are controlled by input. Exploiting this
issue can achive any code excuted
The steps for reproducing the vul on unbuntu:
(1) sudo apt-get iunstall texlive-binaries
(2) ttfdump -i poc.ttf
The poc.ttf can view the attachment .ttfdump aborted and prompt "malloc():
corrupted top size" due memory corrupt.
The issue exist in function ttfLoadHDMX :
/***function ttfLoadHDMX begin ***/
static void ttfLoadHDMX (FILE *fp,HDMXPtr hdmx,ULONG offset)
{
int i;
xfseek(fp, offset, SEEK_SET, "ttfLoadHDMX");
hdmx->version = ttfGetUSHORT(fp);
hdmx->numDevices = ttfGetUSHORT(fp);
hdmx->size = ttfGetLONG(fp);
hdmx->Records = XCALLOC (hdmx->numDevices, DeviceRecord);
for (i=0;inumDevices;i++)
{
hdmx->Records[i].PixelSize = ttfGetBYTE(fp);
hdmx->Records[i].MaxWidth = ttfGetBYTE(fp);
[Desktop-packages] [Bug 2054510] Re: Incomplete screen redraws in virtual machines running Xorg
** Description changed: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] - TODO: Figure out a minimal test plan that doesn't require modifying - code. + 1. Set up a virtual machine without graphics acceleration. + 2. Log into 'Ubuntu on Xorg'. + 3. Open Settings > About and verify Graphics = llvmpipe and Windowing System = X11. + 4. TODO [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 via 551101c65cda. -- 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/2054510 Title: Incomplete screen redraws in virtual machines running Xorg Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Triaged Status in mutter source package in Mantic: Triaged Status in mutter source package in Noble: Fix Committed Bug description: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. 3. Open Settings > About and verify Graphics = llvmpipe and Windowing System = X11. 4. sudo snap install chromium 5. Open Chromium and find a web page with lots of text. 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. 7. Release the mouse button in roughly the middle of the area of text that was selected. 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 via 551101c65cda. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2051855] Re: Mutter causes desktop to extend beyond screen, looks like 2160p on 1440p screen
No the option adjust for TV is not there, also the problem is that the screen is out of bounds in right and downward direction, left and upwards fits the screen just fine. I have attached a image of the problem. ** Attachment added: "Screenshot_screen_issue.png" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2051855/+attachment/5748070/+files/Screenshot_screen_issue.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2051855 Title: Mutter causes desktop to extend beyond screen, looks like 2160p on 1440p screen Status in mutter package in Ubuntu: Incomplete Bug description: Mutter causes desktop to extend beyond screen, looks like 2160p on 1440p screen. This appeared only after installing the latest update of the libmutter package. I am using 2x Samsung S27AG502NUXEN displays in extended desktop mode (join). So far the only fix i have found is holding back this package. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: libmutter-13-0 45.2-0ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 31 14:33:53 2024 InstallationDate: Installed on 2021-10-04 (849 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mutter UpgradeStatus: Upgraded to mantic on 2023-10-16 (107 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2051855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
