[Desktop-packages] [Bug 1973084] Re: transmission-daemon high RAM usage
I've installed a clean Lunar and am testing out the proposed package. Will report back in ~3 days. -- 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/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Fix Released Status in transmission source package in Jammy: Fix Committed Status in transmission source package in Lunar: Fix Committed Status in transmission package in Debian: New Bug description: [ Impact ] There is a memory leak in transmission-daemon that was introduced by a faulty openssl3 patch. It has been reported that it's noticeable after a few hours of seeding/downloading torrent files, less than a day. [ Test Plan ] Being a memory leak, there is no immediate/quick test that can be performed, other than letting it run for a few hours and measure memory consumption "before" and "after". comment #5 mentions about 1Gb of RAM after 18h of runtime. #comment 14 mentions 12Gb of RAM, but not for how long it was running. comment #20 says that after 24h using the patched version from a PPA build, the memory consumption was steady at 300Mb. I'd suggest a 24h test and that it should stay under 1Gb of RAM. [ Where problems could occur ] The patch loads the default and legacy openssl3 providers. This will potentially change the set of algorithms available to the application, compared to what was there before. That being said, the legacy provider is a conservative approach, and the likely result is that *more* algorithms will become available, and not less. This is also the approach I have seen in other applications that were rebuilt using openssl3 instead of openssl1.1. It does seem safer than the original patch, which was manually handling ciphers, in particular RC4, and, well, introduced the memory leak. [ Other Info ] Patch came from gentoo. [ Original Description ] Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938605] Re: Gnome Terminal "Copy As HTML" produces deprecated HTML5 font elements
** No longer affects: gnome-terminal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1938605 Title: Gnome Terminal "Copy As HTML" produces deprecated HTML5 font elements Status in gnome-terminal package in Ubuntu: Confirmed Status in gnome-terminal package in Debian: New Bug description: If you highlight text in gnome-terminal and right-click it, you get a "Copy as HTML" option. The HTML that gnome-terminal generates when using that feature contains tags. font tags were depreciated in HTML 4.01, and made obsolete entirely in HTML 5. (See: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/font). Attached is a sample of the HTML generated by gnome-terminal. The correct behavior would be to include style info such as font colors inside the "style" attribute of a tag, rather than using tags. That is to say, should be replaced by , and should be replaced by This bug exists in gnome terminal through version 3.38.1-1ubuntu1, and it exists in Ubuntu 21.04 as well as in prior versions of Ubuntu. I've attached both a copy of the output of Copy As HTML, containing the deprecated tag. Below is a fixed version of this output that doesn't rely on the tag: alecto@styx:~$ ls apps Bitwarden-1.27.1-x86_64_a6df18330216c2546e435c5a9c5df432.AppImage gitkraken session-desktop-linux-x86_64-1.6.7_18e4489c1ba2c40986ad03ca6522e187.AppImage sources alecto@styx:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1938605/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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 m from comment #792) > I'm on 6.6.4 on a Lenovo Yoga S940-14IIL > > cat /sys/class/sound/hwC1D0/subsystem_id 0x17aa3819 > > Same subsystem_id as for Lenovo 13s Gen2 ITL > (https://github.com/torvalds/linux/blob/master/sound/pci/hda/patch_realtek. > c#L10193) > > Sound works, but it is high-pitched since the base is missing. The C940 also has alc298 and tas2770. Please try this: sudo nano /etc/modprobe.d/alsa-base.conf add this line: options snd-hda-intel model=17aa:3818 save: ctrl+o ctrl+x sudo reboot -- 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 1704002] Re: Missing icon for mono speakers
The symlinks need to point to Yaru icons or be included in Gnome. The issue still exists in Noble. ~$ cd /usr/share/gnome-control-center && find -xtype l && readlink -f $(find -xtype l) /usr/share/icons/hicolor/48x48/devices/audio-speaker-mono-testing.svg /usr/share/icons/hicolor/48x48/devices/audio-speaker-mono.svg /usr/share/gnome-control-center/icons/hicolor/48x48/devices/audio-speaker-center-testing.svg /usr/share/gnome-control-center/icons/hicolor/48x48/devices/audio-speaker-center.svg ~$ find -P /usr/share/icons -name audio-speaker-center.svg /usr/share/icons/Yaru/scalable/devices/audio-speaker-center.svg ~$ find -P /usr/share/icons -name audio-speaker-center-testing.svg /usr/share/icons/Yaru-magenta/scalable/devices/audio-speaker-center-testing.svg /usr/share/icons/Yaru-bark/scalable/devices/audio-speaker-center-testing.svg /usr/share/icons/Yaru-blue/scalable/devices/audio-speaker-center-testing.svg /usr/share/icons/Yaru-viridian/scalable/devices/audio-speaker-center-testing.svg /usr/share/icons/Yaru-purple/scalable/devices/audio-speaker-center-testing.svg /usr/share/icons/Yaru-olive/scalable/devices/audio-speaker-center-testing.svg /usr/share/icons/Yaru-prussiangreen/scalable/devices/audio-speaker-center-testing.svg /usr/share/icons/Yaru-sage/scalable/devices/audio-speaker-center-testing.svg /usr/share/icons/Yaru-red/scalable/devices/audio-speaker-center-testing.svg /usr/share/icons/Yaru/scalable/devices/audio-speaker-center-testing.svg ** Tags added: noble -- 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/1704002 Title: Missing icon for mono speakers Status in gnome-control-center: Confirmed Status in gnome-control-center package in Ubuntu: Fix Released Bug description: For mono speakers (e.g. Bluetooth HFP/HSP profiles) there is no icon, and so the default missing icon is shown. We don't have assets for a mono speaker. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1704002/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915929] Re: gnome-shell-calendar-server assert failure on arm64: double free or corruption (fasttop)
Hello shine, or anyone else affected, Accepted gnome-shell into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- shell/3.36.9-0ubuntu0.20.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed-focal -- 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/1915929 Title: gnome-shell-calendar-server assert failure on arm64: double free or corruption (fasttop) Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Committed Status in gnome-shell source package in Hirsute: Fix Released Bug description: [ Impact ] gnome-shell-calendar-server crashes (and it seems to happen more in aarch64). https://errors.ubuntu.com/problem/028fd7df90d750d70c7fea9719974347af67fa5a https://errors.ubuntu.com/problem/33eeeda9b48baf59fe82b6b1f0aaa9465193b7f1 [ Test case ] There's not a clear test case, but this is relevant: - Configure a supported calendar in your online accounts - GNOME shell should show your events in the calendar (under notifications panel) [ Regression potential ] gnome-shell-calendar-server may leak memory. --- M1 Mac mini Parallels Ubuntu VM ProblemType: CrashDistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-2ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic aarch64 ApportVersion: 2.20.11-0ubuntu58 Architecture: arm64 AssertionMessage: double free or corruption (fasttop) CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 17 04:34:36 2021 DisplayManager: gdm3 ExecutablePath: /usr/libexec/gnome-shell-calendar-server GsettingsChanges: b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.notifications' b'application-children' b"['apport-gtk']" b'org.gnome.desktop.peripherals.keyboard' b'numlock-state' b'true' InstallationDate: Installed on 2021-02-17 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha arm64 (20210217) ProcCmdline: /usr/libexec/gnome-shell-calendar-server ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1 Signal: 6SourcePackage: gnome-shell StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x81245180 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x81240c08 "double free or corruption (fasttop)") at malloc.c:5389 _int_free (av=, p=0xe9eee300, have_lock=0) at malloc.c:4298 g_variant_builder_clear () from /lib/aarch64-linux-gnu/libglib-2.0.so.0 ?? () Title: gnome-shell-calendar-server assert failure: double free or corruption (fasttop) UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1915929/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042796] Re: Ubuntu 20.04: Buttons/icons at the edge of the touchscreen don't respond to taps if they are very small
Hello Kai-Chuan, or anyone else affected, Accepted gnome-shell into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- shell/3.36.9-0ubuntu0.20.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-shell (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2042796 Title: Ubuntu 20.04: Buttons/icons at the edge of the touchscreen don't respond to taps if they are very small Status in Mutter: Fix Released Status in OEM Priority Project: Triaged Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Committed Bug description: [ Impact ] Touchscreen touches at the left or bottom edges (within 20px) of the screen are not treated as mouse clicks. Icons only get highlighted, not launched. [ Test Plan ] 0. Find a touchscreen. 1. Set Ubuntu Dock in Panel mode (the default mode) if not already. 2. Touch as close to the edge of the screen as possible. Aim for the gap between the icon and the edge of the screen. Expect: The app launch animation occurs for each tap. Icons aren't just highlighted. [ Where problems could occur ] Anywhere in touchscreen gesture tracking or even regular touchscreen usage. As this bug demonstrates, the former is able to interfere with even simple touchscreen actions. [ Workaround ] Size the Ubuntu Dock adequately large so it is unlikely the user will touch less than 20 pixels from the edge of the screen. [ Original description ] On Dell OptiPlex 7400 AIO, go to gnome-control-center > appearance, adjust the dock icon-size to 24. It is hard to launch corner app like firefox, or trigger the launcher. The app icon gets focus but not clicked. 1. Ubuntu version 20.04.6 2. gnome-shell 3.36.9-0ubuntu0.20.04.2 3. The app or launcher is launched after a click 4. Only see focus but no app launched To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2042796/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013973] Re: libcogl-common's only file is a dev jpg
Bug was fixed upstream since Mantic. Cogl is no longer in the default installation since Mantic. It still exists from Focal to Lunar. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cogl in Ubuntu. https://bugs.launchpad.net/bugs/2013973 Title: libcogl-common's only file is a dev jpg Status in cogl package in Ubuntu: Won't Fix Bug description: libcogl-common requires development file /usr/share/cogl/examples- data/crate.jpg The project is retired- https://gitlab.gnome.org/Archive/cogl https://blogs.gnome.org/clutter/2022/02/16/retiring-clutter/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cogl/+bug/2013973/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013973] Re: libcogl-common's only file is a dev jpg, negating the need for the package to be recommended. Will be empty in the future.
** No longer affects: cogl (Debian) ** Summary changed: - libcogl-common's only file is a dev jpg, negating the need for the package to be recommended. Will be empty in the future. + libcogl-common's only file is a dev jpg ** Description changed: - Gnome-control-center supposedly requires cheese libraries that require - clutter which requires cogl. The cogl libraries recommend libcogl- - common, which is how it ends up in both the default and minimal - installation. + libcogl-common requires development file /usr/share/cogl/examples- + data/crate.jpg - Here are the contents of libcogl-common in Ubuntu. - /usr/share/cogl/examples-data/crate.jpg - /usr/share/doc/libcogl-common/changelog.Debian.gz - /usr/share/doc/libcogl-common/copyright - - The file /usr/share/cogl/examples-data/crate.jpg accidentally ended up - alone in the libcogl-common package. The package doesn't need to be - recommended and exists for an unknown reason in Ubuntu. Debian's - unneeded translation files are not included. - - The project is archived after being retired- + The project is retired- https://gitlab.gnome.org/Archive/cogl https://blogs.gnome.org/clutter/2022/02/16/retiring-clutter/ ** Tags removed: kinetic lunar mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cogl in Ubuntu. https://bugs.launchpad.net/bugs/2013973 Title: libcogl-common's only file is a dev jpg Status in cogl package in Ubuntu: Won't Fix Bug description: libcogl-common requires development file /usr/share/cogl/examples- data/crate.jpg The project is retired- https://gitlab.gnome.org/Archive/cogl https://blogs.gnome.org/clutter/2022/02/16/retiring-clutter/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cogl/+bug/2013973/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046491] [NEW] Finger Print Sensor is not working on goodixmoc device
Public bug reported: AMD testing of some Goodix MOC devices shows that this device fails to work properly: [ 208.586084] usb 1-2: New USB device found, idVendor=27c6, idProduct=6496, bcdDevice= 1.00 The issue is specifically that there is a problem with the 'enroll create' state. It has been fixed by the following commit that is part of fprintd 1.94.6: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/86566e8d0b7b36ebaa5588af75b46e2c93a12918 Please consider bringing either that commit or the whole 1.94.6 version into Ubuntu (1.94.6 also adds compatibilities with a bunch of other devices). ** Affects: fprintd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/2046491 Title: Finger Print Sensor is not working on goodixmoc device Status in fprintd package in Ubuntu: New Bug description: AMD testing of some Goodix MOC devices shows that this device fails to work properly: [ 208.586084] usb 1-2: New USB device found, idVendor=27c6, idProduct=6496, bcdDevice= 1.00 The issue is specifically that there is a problem with the 'enroll create' state. It has been fixed by the following commit that is part of fprintd 1.94.6: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/86566e8d0b7b36ebaa5588af75b46e2c93a12918 Please consider bringing either that commit or the whole 1.94.6 version into Ubuntu (1.94.6 also adds compatibilities with a bunch of other devices). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/2046491/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046485] [NEW] intel 3000 hd graphics not working
Public bug reported: when i try this command sudo apt-get install xserver-xorg-video-intel i get this xserver-xorg-video-intel is already the newest version (2:2.99.917+git20210115-1). i have intel 3000 hd graphics built-in in my laptop. but my screen is too bright and i am getting 3rd class video quality in youtube in browser, i checked videos in 720p, 1080p, but same issue. when i check some videos in my laptop, that are in good quality downloaded from internet. issue is same. i have no issue in windows 7, 10. but only i have issue is in Linux mint, and Lubuntu Lubuntu 22.04 LTS Lubuntu 22.04.3 LTS JAMMY JELLYFISH RELEASE AMD 20230807 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5json: { "result": "skip" } CasperVersion: 1.470.2 CompositorRunning: None CurrentDesktop: LXQt Date: Thu Dec 14 23:55:58 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:1658] LiveMediaBuild: Lubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcKernelCmdLine: fsck.mode=skip noprompt boot=casper floppy.allowed_drive_mask=0 ignore_uuid -- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2011 dmi.bios.release: 15.27 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1B dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1658 dmi.board.vendor: Hewlett-Packard dmi.board.version: 10.31 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 16.49 dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1B:bd10/05/2011:br15.27:efr16.49:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058C11244720001620100:rvnHewlett-Packard:rn1658:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion:skuA3X35UA#ABA: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.sku: A3X35UA#ABA dmi.product.version: 058C11244720001620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2046485 Title: intel 3000 hd graphics not working Status in xorg package in Ubuntu: New Bug description: when i try this command sudo apt-get install xserver-xorg-video-intel i get this xserver-xorg-video-intel is already the newest version (2:2.99.917+git20210115-1). i have intel 3000 hd graphics built-in in my laptop. but my screen is too bright and i am getting 3rd class video quality in youtube in browser, i checked videos in 720p, 1080p, but same issue. when i check some videos in my laptop, that are in good quality downloaded from internet. issue is same. i have no issue in windows 7, 10. but only i have issue is in Linux mint, and Lubuntu Lubuntu 22.04 LTS Lubuntu 22.04.3 LTS JAMMY JELLYFISH RELEASE AMD 20230807 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5json: { "result": "skip" } CasperVersion: 1.470.2 CompositorRunning: None CurrentDesktop: LXQt Date: Thu Dec 14 23:55:58 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:1658] LiveMediaBuild: Lubuntu
[Desktop-packages] [Bug 2046037] Re: CVE-2023-6185 and CVE-2023-6186
These have been published now, thanks! https://ubuntu.com/security/notices/USN-6546-1 https://ubuntu.com/security/notices/USN-6546-2 ** Changed in: libreoffice (Ubuntu Focal) Status: In Progress => Fix Released ** Changed in: libreoffice (Ubuntu Jammy) Status: In Progress => Fix Released -- 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/2046037 Title: CVE-2023-6185 and CVE-2023-6186 Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: Fix Released Status in libreoffice source package in Jammy: Fix Released Status in libreoffice source package in Lunar: Fix Released Status in libreoffice source package in Mantic: Fix Released Status in libreoffice source package in Noble: Fix Released Bug description: CVE-2023-6185: "Improper input validation enabling arbitrary Gstreamer pipeline injection" https://www.libreoffice.org/about-us/security/advisories/cve-2023-6185/ CVE-2023-6186: "Link targets allow arbitrary script execution" https://www.libreoffice.org/about-us/security/advisories/cve-2023-6186/ https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/log/?h=wip/focal-6.4 https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/log/?h=wip/jammy-7.3 More information will follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2046037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035076] Re: Can't enter capital accented letters with Caps Lock on Wayland
This bug was fixed in the package mutter - 45.2-0ubuntu1 --- mutter (45.2-0ubuntu1) mantic; urgency=medium [ Jeremy Bícha ] * New upstream release (LP: #2043000) - Fix entering capital accent letters with Caps Lock (LP: #2035076) - Fix Wacom on X11 issues (LP: #2043027) * debian/libmutter-13-0.symbols: Add new symbols * Drop patches applied in new release * Rebase X11 fractional scaling patch [ Daniel van Vugt ] * Rebase triple buffering patch -- Jeremy Bícha Mon, 04 Dec 2023 13:45:25 -0500 ** Changed in: mutter (Ubuntu Mantic) Status: Fix Committed => Fix Released -- 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/2035076 Title: Can't enter capital accented letters with Caps Lock on Wayland Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: Fix Released Status in mutter package in Fedora: Unknown Bug description: Impact -- Capital accented letters can't be entered using CAPS LOCK in the Wayland session Test Case - Open a terminal and install basic French support: sudo apt install language-pack-gnome-fr Open the Settings app. In the sidebar, click Keyboard Click +, choose French (France), then choose the French (AZERTY) keyboard Close the Settings app In the top right of the screen, click en and switch the keyboard layout to French (AZERTY) In the text editor, type é (this is the number 2 key on a US English keyboard). Now, press the Caps Lock key to enable Caps Lock. Press the same key. You should get É What Could Go Wrong --- This fix is included in mutter 45.2 so see the master bug for this upstream update: LP: #2043000 Original bug report --- Most programs don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. I've noticed that everything works fine using the Live session which still uses X11 session. It looks there's no problem with programs that use xwayland like Gimp and MarkText. WORKAROUND === In "Settings -> Keyboard" it's possible to set a "compose key". For example I've selected the [Super left] key. If I want to compose È I press and immediately release each key: [Super left] + [E] + [Alt Gr] + ['] If you want É: [Super left] + [E] + ['] Do the same for the other vowels. === ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2035076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043000] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2043000 Title: Update mutter to 45.2 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 45 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/45.2/NEWS Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- Ubuntu 24.04 "Noble" has mutter 45.1 with all the non translation commits cherry-picked. It will get updated to 45.2 (and eventually to 46) after a mesa regression is handled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2043000/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035076] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2035076 Title: Can't enter capital accented letters with Caps Lock on Wayland Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: Fix Released Status in mutter package in Fedora: Unknown Bug description: Impact -- Capital accented letters can't be entered using CAPS LOCK in the Wayland session Test Case - Open a terminal and install basic French support: sudo apt install language-pack-gnome-fr Open the Settings app. In the sidebar, click Keyboard Click +, choose French (France), then choose the French (AZERTY) keyboard Close the Settings app In the top right of the screen, click en and switch the keyboard layout to French (AZERTY) In the text editor, type é (this is the number 2 key on a US English keyboard). Now, press the Caps Lock key to enable Caps Lock. Press the same key. You should get É What Could Go Wrong --- This fix is included in mutter 45.2 so see the master bug for this upstream update: LP: #2043000 Original bug report --- Most programs don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. I've noticed that everything works fine using the Live session which still uses X11 session. It looks there's no problem with programs that use xwayland like Gimp and MarkText. WORKAROUND === In "Settings -> Keyboard" it's possible to set a "compose key". For example I've selected the [Super left] key. If I want to compose È I press and immediately release each key: [Super left] + [E] + [Alt Gr] + ['] If you want É: [Super left] + [E] + ['] Do the same for the other vowels. === ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2035076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043027] Re: Wacom Intuos S stop working after upgrading to Ubuntu 23.10
This bug was fixed in the package mutter - 45.2-0ubuntu1 --- mutter (45.2-0ubuntu1) mantic; urgency=medium [ Jeremy Bícha ] * New upstream release (LP: #2043000) - Fix entering capital accent letters with Caps Lock (LP: #2035076) - Fix Wacom on X11 issues (LP: #2043027) * debian/libmutter-13-0.symbols: Add new symbols * Drop patches applied in new release * Rebase X11 fractional scaling patch [ Daniel van Vugt ] * Rebase triple buffering patch -- Jeremy Bícha Mon, 04 Dec 2023 13:45:25 -0500 ** Changed in: mutter (Ubuntu Mantic) Status: Fix Committed => Fix Released -- 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/2043027 Title: Wacom Intuos S stop working after upgrading to Ubuntu 23.10 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: Fix Released Bug description: Impact -- Clicking does not work correctly with Wacom tablets in the Ubuntu/GNOME X11 sessions Test Case - One of the people affected by this issue will verify whether their Wacom tablet is working noticably better with the upgraded Mutter packages What Could Go Wrong --- The fix for this issue is included in upstream's mutter 45.2 release so please see bug 2043000 as the master bug for this upgrade Original Bug Report --- Tablet seems to work until I open Krita (as I could read on Internet, it may be related with Qt Apps). When Krita is open, mouse movement works ok with the tablet, but when it comes to click action it doesn't work and any further action with mouse is not captured (even outside Krita!). To regain control of the mouse I have to Alt+Tab and then I can click again. Some details that may be handy: - I've got two monitors - Maybe Qt apps related - My graphic card is nVidia GTX 1060 6Gb, driver used nvidia-driver-535 Thanks for your effort. I love Ubuntu! ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-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..06.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 535.129.03 Thu Oct 19 18:56:32 UTC 2023 GCC version: ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 8 17:20:34 2023 DistUpgraded: 2023-11-08 00:54:28,961 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: mantic DistroVariant: ubuntu DkmsStatus: nvidia/535.129.03, 6.2.0-36-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia/535.129.03, 6.5.0-10-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) virtualbox/7.0.10, 6.2.0-36-generic, x86_64: installed virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB] [19da:1438] InstallationDate: Installed on 2022-04-09 (578 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcEnviron: LANG=es_ES.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic root=UUID=9dd904a0-11bb-40fa-9fe8-2f10449a416c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to mantic on 2023-11-07 (1 days ago) dmi.bios.date: 06/15/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0608 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING
[Desktop-packages] [Bug 2043027] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2043027 Title: Wacom Intuos S stop working after upgrading to Ubuntu 23.10 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: Fix Released Bug description: Impact -- Clicking does not work correctly with Wacom tablets in the Ubuntu/GNOME X11 sessions Test Case - One of the people affected by this issue will verify whether their Wacom tablet is working noticably better with the upgraded Mutter packages What Could Go Wrong --- The fix for this issue is included in upstream's mutter 45.2 release so please see bug 2043000 as the master bug for this upgrade Original Bug Report --- Tablet seems to work until I open Krita (as I could read on Internet, it may be related with Qt Apps). When Krita is open, mouse movement works ok with the tablet, but when it comes to click action it doesn't work and any further action with mouse is not captured (even outside Krita!). To regain control of the mouse I have to Alt+Tab and then I can click again. Some details that may be handy: - I've got two monitors - Maybe Qt apps related - My graphic card is nVidia GTX 1060 6Gb, driver used nvidia-driver-535 Thanks for your effort. I love Ubuntu! ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-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..06.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 535.129.03 Thu Oct 19 18:56:32 UTC 2023 GCC version: ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 8 17:20:34 2023 DistUpgraded: 2023-11-08 00:54:28,961 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: mantic DistroVariant: ubuntu DkmsStatus: nvidia/535.129.03, 6.2.0-36-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia/535.129.03, 6.5.0-10-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) virtualbox/7.0.10, 6.2.0-36-generic, x86_64: installed virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB] [19da:1438] InstallationDate: Installed on 2022-04-09 (578 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcEnviron: LANG=es_ES.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic root=UUID=9dd904a0-11bb-40fa-9fe8-2f10449a416c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to mantic on 2023-11-07 (1 days ago) dmi.bios.date: 06/15/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0608 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING B550-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor:
[Desktop-packages] [Bug 2043000] Re: Update mutter to 45.2
This bug was fixed in the package mutter - 45.2-0ubuntu1 --- mutter (45.2-0ubuntu1) mantic; urgency=medium [ Jeremy Bícha ] * New upstream release (LP: #2043000) - Fix entering capital accent letters with Caps Lock (LP: #2035076) - Fix Wacom on X11 issues (LP: #2043027) * debian/libmutter-13-0.symbols: Add new symbols * Drop patches applied in new release * Rebase X11 fractional scaling patch [ Daniel van Vugt ] * Rebase triple buffering patch -- Jeremy Bícha Mon, 04 Dec 2023 13:45:25 -0500 ** Changed in: mutter (Ubuntu Mantic) Status: Fix Committed => Fix Released -- 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/2043000 Title: Update mutter to 45.2 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 45 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/45.2/NEWS Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- Ubuntu 24.04 "Noble" has mutter 45.1 with all the non translation commits cherry-picked. It will get updated to 45.2 (and eventually to 46) after a mesa regression is handled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2043000/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045043] Re: Update fonts-noto-color-emoji for Unicode 15.1
This bug was fixed in the package fonts-noto-color-emoji - 2.042-0ubuntu0.22.04.1 --- fonts-noto-color-emoji (2.042-0ubuntu0.22.04.1) jammy; urgency=medium * New upstream release (LP: #2045043) - This major update introduces support for the Unicode 15.1 standard https://blog.emojipedia.org/googles-emoji-15-1-support-in-noto-color-emoji/ -- Jeremy Bícha Thu, 30 Nov 2023 11:37:35 -0500 ** Changed in: fonts-noto-color-emoji (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/2045043 Title: Update fonts-noto-color-emoji for Unicode 15.1 Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Status in fonts-noto-color-emoji source package in Jammy: Fix Released Status in fonts-noto-color-emoji source package in Mantic: Fix Released Bug description: [Impact] Ubuntu has included Google's color emoji font by default for years. Annually, the Unicode Consortium releases a new Unicode standard with new emoji. Internet communication platforms quickly adopt the new emoji and it's important that those emoji also work on the latest Ubuntu release. Emojipedia provides a list of the emoji provided by this font. Click the Show new link to see the new emoji. Click the changed link to see other changes that were made in this release. https://emojipedia.org/google/15.1/ Or see https://blog.emojipedia.org/googles-emoji-15-1-support-in-noto- color-emoji/ More background at https://jenniferdaniel.substack.com/p/breaking-the- cycle [Test Plan] The test plan is outlined on this wiki: https://wiki.ubuntu.com/DesktopTeam/TestPlans/EmojiFont [Where problems could occur] Sometimes there is an issue with the display of a particular font after the font has been updated. See LP: #2034986 for instance. Perhaps this is a bug with font caching. In this case, it is not believed that the color emoji font is used by GNOME Shell itself so a simple restart of any apps that use emoji should be enough to fix that issue. This could technically be a User Interface Freeze change, but the new and changed emoji don't show in the Ubuntu docs or official screenshots. So there doesn't seem to be a need to notify the Docs team. There are no translations here so no need to notify the Translations team. [Other] I do not intend to prepare this update for Ubuntu 23.04. People are encouraged to upgrade to 23.10 for UI improvements and 23.04 will reach end of life around January. This update does not require nototools to be updated. This update is a prerequisite for a GNOME Characters update for Ubuntu 23.10. See LP: #2045056 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/2045043/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043524] Re: audio disappeared after upgrade to Ubuntu 23.10
Same thing happening with Lenovo Legion Pro 7 Gen 6 The sound with the integrated sound card has disappeared, however it's working over HDMI and Bluetooth. Here's alsa-info output: http://alsa-project.org/db/?f=b90325c4bf477327de3bceb39c0af9be569ebbaf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2043524 Title: audio disappeared after upgrade to Ubuntu 23.10 Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except there is no audio output on streaming functions. The external bluetooth speaker is connected and detected. It is charged and responds to testing. Just no sound when playing videos or podcasts. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: owner 975 F wireplumber /dev/snd/seq:owner 971 F pipewire CasperMD5CheckResult: fail CurrentDesktop: KDE Date: Tue Nov 14 17:50:17 2023 InstallationDate: Installed on 2023-04-15 (213 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago) dmi.bios.date: 07/04/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P31/W8 (MS-7788) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7788 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2043524/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045043] Re: Update fonts-noto-color-emoji for Unicode 15.1
This bug was fixed in the package fonts-noto-color-emoji - 2.042-0ubuntu0.23.10.1 --- fonts-noto-color-emoji (2.042-0ubuntu0.23.10.1) mantic; urgency=medium * New upstream release (LP: #2045043) - This major update introduces support for the Unicode 15.1 standard https://blog.emojipedia.org/googles-emoji-15-1-support-in-noto-color-emoji/ -- Jeremy Bícha Thu, 30 Nov 2023 11:39:05 -0500 ** Changed in: fonts-noto-color-emoji (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/2045043 Title: Update fonts-noto-color-emoji for Unicode 15.1 Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Status in fonts-noto-color-emoji source package in Jammy: Fix Released Status in fonts-noto-color-emoji source package in Mantic: Fix Released Bug description: [Impact] Ubuntu has included Google's color emoji font by default for years. Annually, the Unicode Consortium releases a new Unicode standard with new emoji. Internet communication platforms quickly adopt the new emoji and it's important that those emoji also work on the latest Ubuntu release. Emojipedia provides a list of the emoji provided by this font. Click the Show new link to see the new emoji. Click the changed link to see other changes that were made in this release. https://emojipedia.org/google/15.1/ Or see https://blog.emojipedia.org/googles-emoji-15-1-support-in-noto- color-emoji/ More background at https://jenniferdaniel.substack.com/p/breaking-the- cycle [Test Plan] The test plan is outlined on this wiki: https://wiki.ubuntu.com/DesktopTeam/TestPlans/EmojiFont [Where problems could occur] Sometimes there is an issue with the display of a particular font after the font has been updated. See LP: #2034986 for instance. Perhaps this is a bug with font caching. In this case, it is not believed that the color emoji font is used by GNOME Shell itself so a simple restart of any apps that use emoji should be enough to fix that issue. This could technically be a User Interface Freeze change, but the new and changed emoji don't show in the Ubuntu docs or official screenshots. So there doesn't seem to be a need to notify the Docs team. There are no translations here so no need to notify the Translations team. [Other] I do not intend to prepare this update for Ubuntu 23.04. People are encouraged to upgrade to 23.10 for UI improvements and 23.04 will reach end of life around January. This update does not require nototools to be updated. This update is a prerequisite for a GNOME Characters update for Ubuntu 23.10. See LP: #2045056 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/2045043/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045043] Update Released
The verification of the Stable Release Update for fonts-noto-color-emoji has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/2045043 Title: Update fonts-noto-color-emoji for Unicode 15.1 Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Status in fonts-noto-color-emoji source package in Jammy: Fix Released Status in fonts-noto-color-emoji source package in Mantic: Fix Released Bug description: [Impact] Ubuntu has included Google's color emoji font by default for years. Annually, the Unicode Consortium releases a new Unicode standard with new emoji. Internet communication platforms quickly adopt the new emoji and it's important that those emoji also work on the latest Ubuntu release. Emojipedia provides a list of the emoji provided by this font. Click the Show new link to see the new emoji. Click the changed link to see other changes that were made in this release. https://emojipedia.org/google/15.1/ Or see https://blog.emojipedia.org/googles-emoji-15-1-support-in-noto- color-emoji/ More background at https://jenniferdaniel.substack.com/p/breaking-the- cycle [Test Plan] The test plan is outlined on this wiki: https://wiki.ubuntu.com/DesktopTeam/TestPlans/EmojiFont [Where problems could occur] Sometimes there is an issue with the display of a particular font after the font has been updated. See LP: #2034986 for instance. Perhaps this is a bug with font caching. In this case, it is not believed that the color emoji font is used by GNOME Shell itself so a simple restart of any apps that use emoji should be enough to fix that issue. This could technically be a User Interface Freeze change, but the new and changed emoji don't show in the Ubuntu docs or official screenshots. So there doesn't seem to be a need to notify the Docs team. There are no translations here so no need to notify the Translations team. [Other] I do not intend to prepare this update for Ubuntu 23.04. People are encouraged to upgrade to 23.10 for UI improvements and 23.04 will reach end of life around January. This update does not require nototools to be updated. This update is a prerequisite for a GNOME Characters update for Ubuntu 23.10. See LP: #2045056 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/2045043/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046436] Re: Ubuntu won't boot after enabling jumbo packets on network device
Hi, If you press ESC when the splash screen shows up, do you see the console? We need to know where it's getting stuck to better understand the problem. If you manage to see the console during boot, can you describe what you see? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2046436 Title: Ubuntu won't boot after enabling jumbo packets on network device Status in network-manager package in Ubuntu: New Bug description: Ubuntu Desktop 23.10 Asrock IMB-X1714 main board, with Intel I226V and I226LM ethernet controllers network-manager 1.44.2-1ubuntu1.2 When enabling jumbo packets on a wired network device by setting MTU to 9000, Ubuntu will not boot anymore. The Ubuntu splash screen, with rotating wheel, appears, at a lower resolution than ordinary, but freezes after a few seconds. I can only revert this by disabling the ethernet devices in BIOS. After that Ubuntu will boot normally. I can then manually edit the .yaml configuration files in /etc/netplan to disable jumbo packets again. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Dec 14 11:04:19 2023 IfupdownConfig: InstallationDate: Installed on 2023-12-13 (1 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) IpRoute: default via 192.168.0.1 dev enp4s0 proto dhcp src 192.168.0.208 metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.0.0/24 dev enp4s0 proto kernel scope link src 192.168.0.208 metric 100 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled missing enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2046436/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046436] [NEW] Ubuntu won't boot after enabling jumbo packets on network device
Public bug reported: Ubuntu Desktop 23.10 Asrock IMB-X1714 main board, with Intel I226V and I226LM ethernet controllers network-manager 1.44.2-1ubuntu1.2 When enabling jumbo packets on a wired network device by setting MTU to 9000, Ubuntu will not boot anymore. The Ubuntu splash screen, with rotating wheel, appears, at a lower resolution than ordinary, but freezes after a few seconds. I can only revert this by disabling the ethernet devices in BIOS. After that Ubuntu will boot normally. I can then manually edit the .yaml configuration files in /etc/netplan to disable jumbo packets again. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Dec 14 11:04:19 2023 IfupdownConfig: InstallationDate: Installed on 2023-12-13 (1 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) IpRoute: default via 192.168.0.1 dev enp4s0 proto dhcp src 192.168.0.208 metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.0.0/24 dev enp4s0 proto kernel scope link src 192.168.0.208 metric 100 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled missing enabled missing enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2046436 Title: Ubuntu won't boot after enabling jumbo packets on network device Status in network-manager package in Ubuntu: New Bug description: Ubuntu Desktop 23.10 Asrock IMB-X1714 main board, with Intel I226V and I226LM ethernet controllers network-manager 1.44.2-1ubuntu1.2 When enabling jumbo packets on a wired network device by setting MTU to 9000, Ubuntu will not boot anymore. The Ubuntu splash screen, with rotating wheel, appears, at a lower resolution than ordinary, but freezes after a few seconds. I can only revert this by disabling the ethernet devices in BIOS. After that Ubuntu will boot normally. I can then manually edit the .yaml configuration files in /etc/netplan to disable jumbo packets again. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Dec 14 11:04:19 2023 IfupdownConfig: InstallationDate: Installed on 2023-12-13 (1 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) IpRoute: default via 192.168.0.1 dev enp4s0 proto dhcp src 192.168.0.208 metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.0.0/24 dev enp4s0 proto kernel scope link src 192.168.0.208 metric 100 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled missing enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2046436/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp