[Desktop-packages] [Bug 1993928] Re: Switching to new input method does nothing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ibus-m17n (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-m17n in Ubuntu. https://bugs.launchpad.net/bugs/1993928 Title: Switching to new input method does nothing Status in ibus-m17n package in Ubuntu: Confirmed Bug description: I have ibus-m17n installed, but switching to a different input method does nothing. STR: 1. Make sure my 2nd input method (in my case, "Sanskrit (sa-IAST (m17n))" appears under "Settings-->Keyboard-->Input sources." 2. Use alt-space to switch to my second input method. 3. Notice on the top panel that the indicator shows that the input method has changed. 4. Attempt to key in some special characters (using Gedit, LibreOffice, etc.). Expected result: The special characters will appear. Actual result: The keyboard behaves as if the input method were my usual "English (US)." No such problem with 22.04. Removing and re-adding "Sanskrit (sa-IAST (m17n))" in Settings doesn't solve the issue. Hardware: IBM ThinkPad Carbon X-1, 5th generation. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: ibus 1.5.27-2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 23 08:44:46 2022 InstallationDate: Installed on 2017-12-08 (1779 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ibus UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-m17n/+bug/1993928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc
I can reproduce this issue and if I disable hardware acceleration in settings::system, tab will crash when webcam starting. -- 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/1999487 Title: Webcam does not work with v107.0.5304.121-hwacc Status in chromium-browser package in Ubuntu: New Bug description: With the latest version of Chromium in the stable channel (108.0.5359.94), I can access the webcam and the microphone in Google Meet and Jitsi (using a framatalk.org instance). However, with version 107.0.5304.121-hwacc (from latest/candidate/hwacc branch), the same test does not work. The only difference between the two in `snap connections chromium` is content chromium:va-driver-non-free - - Test: 1. Install Chromium from the given channel 2. Go to https://framatalk.org/ and click on "Create a room" 3. Accept the permissions to access Microphone and Camera Expected result: Image from camera is displayed on screen Actual result: The webcam is turned on (the LED turns on), but no image is captured, and after a few seconds, an error message is displayed ("We are unable to access your camera"). In the settings, I can see the camera name ("UVC Camera (046d:0802)"). Attached are two logs: - One retrieved by launching Chromium with `chromium --enable-logging=stderr`, accessing framatalk.org and clicking on "Create a room". - One retrieved by launching Chromium with `chromium --enable-logging=stderr` and accessing a Google Meet event. Configuration information = - Desktop with AMD GPU RX580 - Ubuntu 20.04 (kernel 5.15.0-56-generic) - Webcam: 046d:0802 Logitech, Inc. Webcam C200 - Headset: 046d:0a38 Logitech, Inc. Headset H340 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991761] Re: Backport packages for 22.04.2 HWE stack
spirv-headers is build-depended on by several packages; could we do test-rebuilds of those as a part of verification, please. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1991761 Title: Backport packages for 22.04.2 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-15 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in spirv-headers package in Ubuntu: Invalid Status in spirv-llvm-translator-14 package in Ubuntu: Invalid Status in spirv-llvm-translator-15 package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in libdrm source package in Jammy: In Progress Status in llvm-toolchain-15 source package in Jammy: In Progress Status in mesa source package in Jammy: In Progress Status in spirv-headers source package in Jammy: Fix Committed Status in spirv-llvm-translator-14 source package in Jammy: In Progress Status in spirv-llvm-translator-15 source package in Jammy: In Progress Bug description: [Impact The graphics HWE stack from kinetic needs to be backported for 22.04.2 directx-headers - build-dep of the new Mesa libdrm - build-dep of the new Mesa llvm-15 - new package in jammy - build-dep of the new Mesa mesa - new major release (22.2.x) - new HW support, like AMD RDNA3, Intel DG2 spirv-headers - needed by s-l-t-15 spirv-llvm-translator-14 - needed to bootstrap libclc from llvm spirv-llvm-translator-15 - needed for the actual libclc-15 after initial bootstrap Bootstrapping plan: - s-l-t-14 built from NEW - llvm-15 built with s-l-t-14 - s-l-t-15 built against llvm-15 - llvm-15 built again with s-l-t-15 -> mesa ready for building [Test case] Install the new mesa on various hw, see that everything still works like before or better. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 22.2.x in order to minimize the chance for those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1991761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991761] Re: Backport packages for 22.04.2 HWE stack
Hello Timo, or anyone else affected, Accepted spirv-headers into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/spirv- headers/1.6.1+1.3.216.0-1~ubuntu0.22.04.1 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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: spirv-headers (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1991761 Title: Backport packages for 22.04.2 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-15 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in spirv-headers package in Ubuntu: Invalid Status in spirv-llvm-translator-14 package in Ubuntu: Invalid Status in spirv-llvm-translator-15 package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in libdrm source package in Jammy: In Progress Status in llvm-toolchain-15 source package in Jammy: In Progress Status in mesa source package in Jammy: In Progress Status in spirv-headers source package in Jammy: Fix Committed Status in spirv-llvm-translator-14 source package in Jammy: In Progress Status in spirv-llvm-translator-15 source package in Jammy: In Progress Bug description: [Impact The graphics HWE stack from kinetic needs to be backported for 22.04.2 directx-headers - build-dep of the new Mesa libdrm - build-dep of the new Mesa llvm-15 - new package in jammy - build-dep of the new Mesa mesa - new major release (22.2.x) - new HW support, like AMD RDNA3, Intel DG2 spirv-headers - needed by s-l-t-15 spirv-llvm-translator-14 - needed to bootstrap libclc from llvm spirv-llvm-translator-15 - needed for the actual libclc-15 after initial bootstrap Bootstrapping plan: - s-l-t-14 built from NEW - llvm-15 built with s-l-t-14 - s-l-t-15 built against llvm-15 - llvm-15 built again with s-l-t-15 -> mesa ready for building [Test case] Install the new mesa on various hw, see that everything still works like before or better. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 22.2.x in order to minimize the chance for those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1991761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991761] Re: Backport packages for 22.04.2 HWE stack
I know it doesn't have any rdepends in the archive, but this includes a libdrm-tegra0 ABI break without bumping SONAME; what sort of consumers of libdrm-tegra0 are likely to exist? What risk mitigations could we implement? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1991761 Title: Backport packages for 22.04.2 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-15 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in spirv-headers package in Ubuntu: Invalid Status in spirv-llvm-translator-14 package in Ubuntu: Invalid Status in spirv-llvm-translator-15 package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in libdrm source package in Jammy: In Progress Status in llvm-toolchain-15 source package in Jammy: In Progress Status in mesa source package in Jammy: In Progress Status in spirv-headers source package in Jammy: New Status in spirv-llvm-translator-14 source package in Jammy: In Progress Status in spirv-llvm-translator-15 source package in Jammy: In Progress Bug description: [Impact The graphics HWE stack from kinetic needs to be backported for 22.04.2 directx-headers - build-dep of the new Mesa libdrm - build-dep of the new Mesa llvm-15 - new package in jammy - build-dep of the new Mesa mesa - new major release (22.2.x) - new HW support, like AMD RDNA3, Intel DG2 spirv-headers - needed by s-l-t-15 spirv-llvm-translator-14 - needed to bootstrap libclc from llvm spirv-llvm-translator-15 - needed for the actual libclc-15 after initial bootstrap Bootstrapping plan: - s-l-t-14 built from NEW - llvm-15 built with s-l-t-14 - s-l-t-15 built against llvm-15 - llvm-15 built again with s-l-t-15 -> mesa ready for building [Test case] Install the new mesa on various hw, see that everything still works like before or better. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 22.2.x in order to minimize the chance for those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1991761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999595] [NEW] Cannot connect via IPv6: "invalid cbClientAddress value: 82"
Public bug reported: I am trying to access a remote computer that does not have a publicly- routable IPv4 address. Let's say that MyHostName.MyDomain.com has an IP address of 2001:db8::1. If you look it up in DNS, you get no A records and one record. Using both Remmina and gnome-connections, I am unable to connect to the RDP servers MyHostName.MyDomain.com, 2001:db8::1, nor [2001:db8::1]:3389. Tonight, I'm on the same LAN as this server; I tried connecting to its LAN IPv4 address, and that worked perfectly. I used `nmap` and confirmed that TCP 3389 is open over IPv4 and IPv6 (the latter available over the WAN, too), and `ss` confirms that `gnome- remote-desktop` is listening for IPv4 and IPv6 connections. ## Server logs ``` Dec 13 21:37:18 MyHostName gnome-remote-desktop-daemon[10519]: [21:37:18:358] [10519:12845] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312] Dec 13 21:37:18 MyHostName gnome-remote-desktop-daemon[10519]: [21:37:18:459] [10519:12845] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_COMPLETE_NEEDED [0x00090313] Dec 13 21:37:19 MyHostName gnome-remote-desktop-daemon[10519]: [21:37:19:063] [10519:12845] [ERROR][com.freerdp.core.info] - protocol error: invalid cbClientAddress value: 82 Dec 13 21:37:19 MyHostName gnome-remote-desktop-daemon[10519]: [21:37:19:063] [10519:12845] [ERROR][com.freerdp.core.peer] - peer_recv_callback: CONNECTION_STATE_SECURE_SETTINGS_EXCHANGE - rdp_recv_client_info() fail Dec 13 21:37:19 MyHostName gnome-remote-desktop-daemon[10519]: [21:37:19:063] [10519:12845] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1 Dec 13 21:37:19 MyHostName gnome-remote-desktop-daemon[10519]: [21:37:19:294] [10519:12863] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312] Dec 13 21:37:19 MyHostName gnome-remote-desktop-daemon[10519]: [21:37:19:395] [10519:12863] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_COMPLETE_NEEDED [0x00090313] Dec 13 21:37:20 MyHostName gnome-remote-desktop-daemon[10519]: [21:37:20:998] [10519:12863] [ERROR][com.freerdp.core.info] - protocol error: invalid cbClientAddress value: 82 Dec 13 21:37:20 MyHostName gnome-remote-desktop-daemon[10519]: [21:37:20:998] [10519:12863] [ERROR][com.freerdp.core.peer] - peer_recv_callback: CONNECTION_STATE_SECURE_SETTINGS_EXCHANGE - rdp_recv_client_info() fail Dec 13 21:37:20 MyHostName gnome-remote-desktop-daemon[10519]: [21:37:20:998] [10519:12863] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1 Dec 13 21:38:21 MyHostName gnome-remote-desktop-daemon[10519]: [21:38:21:835] [10519:12908] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312] Dec 13 21:38:21 MyHostName gnome-remote-desktop-daemon[10519]: [21:38:21:936] [10519:12908] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_COMPLETE_NEEDED [0x00090313] Dec 13 21:38:22 MyHostName gnome-remote-desktop-daemon[10519]: [21:38:22:939] [10519:12908] [ERROR][com.freerdp.core.info] - protocol error: invalid cbClientAddress value: 82 Dec 13 21:38:22 MyHostName gnome-remote-desktop-daemon[10519]: [21:38:22:939] [10519:12908] [ERROR][com.freerdp.core.peer] - peer_recv_callback: CONNECTION_STATE_SECURE_SETTINGS_EXCHANGE - rdp_recv_client_info() fail Dec 13 21:38:22 MyHostName gnome-remote-desktop-daemon[10519]: [21:38:22:939] [10519:12908] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1 Dec 13 21:38:22 MyHostName gnome-remote-desktop-daemon[10519]: [21:38:22:181] [10519:12943] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312] Dec 13 21:38:22 MyHostName gnome-remote-desktop-daemon[10519]: [21:38:22:282] [10519:12943] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_COMPLETE_NEEDED [0x00090313] Dec 13 21:38:22 MyHostName gnome-remote-desktop-daemon[10519]: [21:36:45:122] [10519:12793] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0 Dec 13 21:38:22 MyHostName gnome-remote-desktop-daemon[10519]: [21:36:45:122] [10519:12793] [INFO][com.freerdp.core.connection] - Server Security: NLA:1 TLS:0 RDP:0 Dec 13 21:38:22 MyHostName gnome-remote-desktop-daemon[10519]: [21:36:45:122] [10519:12793] [INFO][com.freerdp.core.connection] - Negotiated Security: NLA:1 TLS:0 RDP:0 Dec 13 21:38:22 MyHostName gnome-remote-desktop-daemon[10519]: [21:36:45:363] [10519:12793] [INFO][com.freerdp.core.connection] - Accepted client: thinkpad Dec 13 21:38:22 MyHostName gnome-remote-desktop-daemon[10519]: [21:36:45:363] [10519:12793] [INFO][com.freerdp.core.connection] - Accepted channels: Dec 13 21:38:22 MyHostName gnome-remote-desktop-daemon[10519]: [21:36:45:363] [10519:12793] [INFO][com.freerdp.core.gcc] - Active rdp encryption level: NONE Dec 13 21:38:22 MyHostName g
[Desktop-packages] [Bug 1855220] Re: xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry)
@Aaron/arraybolt3 I filed against the package I did, as I don't experience it on other boxes that include much slower CPUs than those listed here, but instead use i915 or AMD gpu. Examples where I've not experienced this include (some slower boxes) - lenovo thinkpad sl510 (c2d-t6570, 2gb ram, i915) - motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series) (I believe too) - dell [optiplex] 745 (c2d-6600, 6gb, amd/ati radeon rv516/x1300/x1550) - dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550) - dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt) I mention looking for this on another d780 and not experiencing it (comment 2) and don't recall it occurring on the d960 which was my primary box (though as flurry isn't my personal choice; it was only likely used when box was used for live testing), and those boxes would have to be seen as slower than - hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600) where this is experienced. I suspect it's very video card related; and as I also note in comment #2; seems to only occur when two displays are connected & used. Also, IF only a single display is active; even the HP 8200 (comment 2) didn't have an issue with 'flurry' I report (my vertical alignment can trigger a condition an issue when openbox is used where xscreensaver only covers a single screen which is I suspect maybe the 'choppy' behavior wasn't noticed on a card usually impacted; ie. the GPU is slowed enough when it handles two screens & issue is visible my theory). This issue is minor, and I pretty much ignore it. Users can always just switch to a different screensaver (I do!); it's not great for users who have boxes/setups where they experience this on a 'new' or 'live' system in my opinion. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1855220 Title: xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry) Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: Lubuntu 20.04 daily QA-test on hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) Displays have been adjusted to my setup (one above the other) but I doubt this is an issue I suspended system, waited, pressed ESC to wake & it resumed to xscreensaver, but 'flurry' was chopped and showing white/black patches on display as if glitching... I touched mouse & my session removed. opened xscreensaver & preview - yep glitch there too... changed to 'fliptext' & no issues, but flurry is very jerky with image switching to almost-blocky-bad-signal (I think it's alternating between showing something else, text; it seems to vary on what I've had on screen before screensaver is loaded & continuing to show xscreensaver..) attempts to screengrab with delay have failed (just capturing black screen).. `lshw -C video` reports I'm using nouveau. This issue may not relate to 'xserver-xorg-video-nouveau', but I suspect it's there. I've performed this test a number of times on various boxes without issue (will do so again once I shutdown this). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.432 CompositorRunning: None CurrentDesktop: LXQt Date: Thu Dec 5 04:04:51 2019 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation G86 [Quadro NVS 290] [10de:0492] LiveMediaBuild: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191204) MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2006 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.05 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc7700 Small Form Factor dmi.product.sku: ET090AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xs
[Desktop-packages] [Bug 1975557] Re: blank screen does not turn off display backlight
I have the same problem. Screen Blank activates after a period of inactivity and then the monitor briefly turns off then on with backlight. Fresh install OS does not fix the problem. Can someone help? -- 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/1975557 Title: blank screen does not turn off display backlight Status in gnome-shell package in Ubuntu: Expired Bug description: I updated a system from 21.10 to 22.04 and noticed that when the screen is blanked by no keyboard or mouse activity that the backlight in the VGA monitor is still on. The "settings->Displays" has "Unknown Display" which I assume means the system does not know what commands to send to the monitor to shut it off. I booted a live DVD of 21.10 and the settings has the VGA display as 'AOC 22" ' which is correct and the screen blanking works correctly. So it seems that the definition for the AOC displays have been removed from 22.04. This behavior is different on Ubuntu 21.10, the VGA display is blank and the backlight is off. A minor nit is on 21.10 the "settings->Displays" shows the VGA display manufacture name, on 22.04 the VGA display manufacture name is "Unknown Display". I have discovered that the settings have the following options "settings->Power->Screen Blank" with a time value to be selected and the following text on the next line "Turns the screen off after a period of inactivity" "settings->Privacy->Screen->Blank Screen Display" with a time value to be selected and the following text on the next line "Period of inactivity after which the screen will go blank" The two options have different actions but seem to be connected because changing the time on one changes the time on the other. My guess is that the update changed the action for Ubuntu 22.04. I would like the 21.10 behavior, that is to turn off the VGA display not just blank the display when selecting the "settings->Power->Screen Blank" for 22.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975557/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991761] Re: Backport packages for 22.04.2 HWE stack
Hello Timo, or anyone else affected, Accepted directx-headers into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/directx- headers/1.606.4-1~ubuntu0.22.04.1 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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: directx-headers (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1991761 Title: Backport packages for 22.04.2 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-15 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in spirv-headers package in Ubuntu: Invalid Status in spirv-llvm-translator-14 package in Ubuntu: Invalid Status in spirv-llvm-translator-15 package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in libdrm source package in Jammy: In Progress Status in llvm-toolchain-15 source package in Jammy: In Progress Status in mesa source package in Jammy: In Progress Status in spirv-headers source package in Jammy: New Status in spirv-llvm-translator-14 source package in Jammy: In Progress Status in spirv-llvm-translator-15 source package in Jammy: In Progress Bug description: [Impact The graphics HWE stack from kinetic needs to be backported for 22.04.2 directx-headers - build-dep of the new Mesa libdrm - build-dep of the new Mesa llvm-15 - new package in jammy - build-dep of the new Mesa mesa - new major release (22.2.x) - new HW support, like AMD RDNA3, Intel DG2 spirv-headers - needed by s-l-t-15 spirv-llvm-translator-14 - needed to bootstrap libclc from llvm spirv-llvm-translator-15 - needed for the actual libclc-15 after initial bootstrap Bootstrapping plan: - s-l-t-14 built from NEW - llvm-15 built with s-l-t-14 - s-l-t-15 built against llvm-15 - llvm-15 built again with s-l-t-15 -> mesa ready for building [Test case] Install the new mesa on various hw, see that everything still works like before or better. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 22.2.x in order to minimize the chance for those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1991761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855220] Re: xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry)
I've noticed this problem also on slower systems of mine (an Acer Chromebook C720 for instance). This leads me to believe that system speed (or perhaps graphics subsystem speed?) is the culprit here, as other systems work with flurry just fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1855220 Title: xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry) Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: Lubuntu 20.04 daily QA-test on hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) Displays have been adjusted to my setup (one above the other) but I doubt this is an issue I suspended system, waited, pressed ESC to wake & it resumed to xscreensaver, but 'flurry' was chopped and showing white/black patches on display as if glitching... I touched mouse & my session removed. opened xscreensaver & preview - yep glitch there too... changed to 'fliptext' & no issues, but flurry is very jerky with image switching to almost-blocky-bad-signal (I think it's alternating between showing something else, text; it seems to vary on what I've had on screen before screensaver is loaded & continuing to show xscreensaver..) attempts to screengrab with delay have failed (just capturing black screen).. `lshw -C video` reports I'm using nouveau. This issue may not relate to 'xserver-xorg-video-nouveau', but I suspect it's there. I've performed this test a number of times on various boxes without issue (will do so again once I shutdown this). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.432 CompositorRunning: None CurrentDesktop: LXQt Date: Thu Dec 5 04:04:51 2019 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation G86 [Quadro NVS 290] [10de:0492] LiveMediaBuild: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191204) MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2006 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.05 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc7700 Small Form Factor dmi.product.sku: ET090AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1855220/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc
And this is the logs from Chromium when running the steps in the previous comment. ** Attachment added: "chromium_hwacc_no_webcam.log" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+attachment/5635526/+files/chromium_hwacc_no_webcam.log -- 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/1999487 Title: Webcam does not work with v107.0.5304.121-hwacc Status in chromium-browser package in Ubuntu: New Bug description: With the latest version of Chromium in the stable channel (108.0.5359.94), I can access the webcam and the microphone in Google Meet and Jitsi (using a framatalk.org instance). However, with version 107.0.5304.121-hwacc (from latest/candidate/hwacc branch), the same test does not work. The only difference between the two in `snap connections chromium` is content chromium:va-driver-non-free - - Test: 1. Install Chromium from the given channel 2. Go to https://framatalk.org/ and click on "Create a room" 3. Accept the permissions to access Microphone and Camera Expected result: Image from camera is displayed on screen Actual result: The webcam is turned on (the LED turns on), but no image is captured, and after a few seconds, an error message is displayed ("We are unable to access your camera"). In the settings, I can see the camera name ("UVC Camera (046d:0802)"). Attached are two logs: - One retrieved by launching Chromium with `chromium --enable-logging=stderr`, accessing framatalk.org and clicking on "Create a room". - One retrieved by launching Chromium with `chromium --enable-logging=stderr` and accessing a Google Meet event. Configuration information = - Desktop with AMD GPU RX580 - Ubuntu 20.04 (kernel 5.15.0-56-generic) - Webcam: 046d:0802 Logitech, Inc. Webcam C200 - Headset: 046d:0a38 Logitech, Inc. Headset H340 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc
1. The Pipewire flag was set to "Default", but even when set to "Enabled", the webcam does not work. 2. journalctl.log attached when accessing framatalk.org and creating a room. ** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+attachment/5635525/+files/journalctl.log -- 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/1999487 Title: Webcam does not work with v107.0.5304.121-hwacc Status in chromium-browser package in Ubuntu: New Bug description: With the latest version of Chromium in the stable channel (108.0.5359.94), I can access the webcam and the microphone in Google Meet and Jitsi (using a framatalk.org instance). However, with version 107.0.5304.121-hwacc (from latest/candidate/hwacc branch), the same test does not work. The only difference between the two in `snap connections chromium` is content chromium:va-driver-non-free - - Test: 1. Install Chromium from the given channel 2. Go to https://framatalk.org/ and click on "Create a room" 3. Accept the permissions to access Microphone and Camera Expected result: Image from camera is displayed on screen Actual result: The webcam is turned on (the LED turns on), but no image is captured, and after a few seconds, an error message is displayed ("We are unable to access your camera"). In the settings, I can see the camera name ("UVC Camera (046d:0802)"). Attached are two logs: - One retrieved by launching Chromium with `chromium --enable-logging=stderr`, accessing framatalk.org and clicking on "Create a room". - One retrieved by launching Chromium with `chromium --enable-logging=stderr` and accessing a Google Meet event. Configuration information = - Desktop with AMD GPU RX580 - Ubuntu 20.04 (kernel 5.15.0-56-generic) - Webcam: 046d:0802 Logitech, Inc. Webcam C200 - Headset: 046d:0a38 Logitech, Inc. Headset H340 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc
** Tags added: 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/1999487 Title: Webcam does not work with v107.0.5304.121-hwacc Status in chromium-browser package in Ubuntu: New Bug description: With the latest version of Chromium in the stable channel (108.0.5359.94), I can access the webcam and the microphone in Google Meet and Jitsi (using a framatalk.org instance). However, with version 107.0.5304.121-hwacc (from latest/candidate/hwacc branch), the same test does not work. The only difference between the two in `snap connections chromium` is content chromium:va-driver-non-free - - Test: 1. Install Chromium from the given channel 2. Go to https://framatalk.org/ and click on "Create a room" 3. Accept the permissions to access Microphone and Camera Expected result: Image from camera is displayed on screen Actual result: The webcam is turned on (the LED turns on), but no image is captured, and after a few seconds, an error message is displayed ("We are unable to access your camera"). In the settings, I can see the camera name ("UVC Camera (046d:0802)"). Attached are two logs: - One retrieved by launching Chromium with `chromium --enable-logging=stderr`, accessing framatalk.org and clicking on "Create a room". - One retrieved by launching Chromium with `chromium --enable-logging=stderr` and accessing a Google Meet event. Configuration information = - Desktop with AMD GPU RX580 - Ubuntu 20.04 (kernel 5.15.0-56-generic) - Webcam: 046d:0802 Logitech, Inc. Webcam C200 - Headset: 046d:0a38 Logitech, Inc. Headset H340 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999335] Re: Please remove vte from Ubuntu
It can't be removed from Debian until someone ports debian-installer away from GTK2. :( ** Tags removed: lucid ** Tags added: lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1999335 Title: Please remove vte from Ubuntu Status in vte package in Ubuntu: New Bug description: The vte source package is an old version of vte that hasn't been maintained in many years. The current version is packaged with source package name vte2.91 vte is still around in Debian because debian-installer has not yet switched to GTK3. However, Ubuntu no longer supports debian-installer and nothing in Ubuntu uses the old vte. Therefore, please remove vte from Ubuntu. $ reverse-depends src:vte $ reverse-depends -b src:vte No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1999335/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999581] [NEW] Missing build dependencies: ruby (>= 1:3.1~)
Public bug reported: marisa 0.2.6-12 in -proposed does not build due to a missing dependency. The explanation is that the ruby3.1 transition has not started yet in Ubuntu, see bug #1999550. No need to take separate measures for this reason; it will probably build as soon as the ruby3.1 transition has started. ** Affects: marisa (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to marisa in Ubuntu. https://bugs.launchpad.net/bugs/1999581 Title: Missing build dependencies: ruby (>= 1:3.1~) Status in marisa package in Ubuntu: New Bug description: marisa 0.2.6-12 in -proposed does not build due to a missing dependency. The explanation is that the ruby3.1 transition has not started yet in Ubuntu, see bug #1999550. No need to take separate measures for this reason; it will probably build as soon as the ruby3.1 transition has started. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marisa/+bug/1999581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915910] Re: evince does not print (apparmor, pxgsettings)
Hello Togo28, or anyone else affected, Accepted evince into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/evince/43.0-1ubuntu1 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- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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: evince (Ubuntu Kinetic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Fix Released Status in libproxy package in Ubuntu: Invalid Status in evince source package in Kinetic: Fix Committed Status in evince package in Debian: New Bug description: * Impact Evince hangs when opening the printing dialog for some users with a remote printer configured and connected * Test case - configure a remote printer and turn it on - open a pdf - try to print the document the print dialog shouldn't freeze the viewer * What could go wrong The change is only allowing access to one extra system binary from the apparmor profile so shouldn't really have an impact on the software behaviour. If the syntax or content of the change was incorrect it could make the apparmor profile not been loaded anymore or block access to thing that should be allowed, so ensure that opening documents, printing and thumbnailing are still working -- audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998966] Re: Update gnome-remote-desktop to 42.7
Hello Jeremy, or anyone else affected, Accepted gnome-remote-desktop into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-remote-desktop/42.7-0ubuntu1 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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-remote-desktop (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1998966 Title: Update gnome-remote-desktop to 42.7 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: Fix Committed Bug description: Impact -- This is a new stable release in the GNOME 42 series It fixes some crashes reported to errors.ubuntu.com Changes since the current Ubuntu 22.04 LTS release, 42.4: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/42.4...42.7 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1998966/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995245] Re: Update gnome-remote-desktop to 43.2
Hello Jeremy, or anyone else affected, Accepted gnome-remote-desktop into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-remote-desktop/43.2-0ubuntu1 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- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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-remote-desktop (Ubuntu Kinetic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1995245 Title: Update gnome-remote-desktop to 43.2 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Kinetic: Fix Committed Bug description: Impact -- This is a new stable release in the GNOME 43 series It fixes some crashes reported to errors.ubuntu.com https://gitlab.gnome.org/GNOME/gnome-remote- desktop/-/compare/43.0...43.2 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case and the "Basic VNC Test Case (for Ubuntu 22.04 LTS only) What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1995245/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999207] Re: Error in dead key management of latin keyboards
On 2022-12-13 19:40, Sharcoux wrote: > layout: fr,fr > variant:latin9,oss Then it's the "French (legacy, alt.)" layout you use. And yes, with that layout you get dead_circumflex by simply pressing the key to the right of the P key. (But I think the layout used to make use of some dead key doesn't really matter.) The good news is that I have figured out a way to reproduce the behavior you state as "current result" in your upstream Firefox bug. I simply removed all my IBus sources from the list of input sources and relogged in. Then I get: compositionstart: compositionupdate: ^ compositionupdate: compositionend: So it would be interesting to know if you can do the opposite. Assuming you are on a standard Ubuntu 22.04 with GNOME, can you please * install some ibus input method — suggestion: the ibus-libpinyin package * relogin * go to Settings -> Keyboard and add "Intelligent Pinyin" to your input sources * relogin again I did those steps myself, and now I'm back with this result: compositionstart: compositionupdate: ^ compositionupdate: û compositionend: û -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1999207 Title: Error in dead key management of latin keyboards Status in ibus package in Ubuntu: Incomplete Bug description: Composition events are incorrect in Ubuntu 22.04 for latin keyboard I opened an issue at Firefox [here](https://bugzilla.mozilla.org/show_bug.cgi?id=1802989) that gives all the details, but they diagnosed a bug in ubuntu-ibus To reproduce the issue, you can go [here](https://developer.mozilla.org/en- US/docs/Web/API/Element/compositionstart_event#result) and type ^+u with a fr+latin9 keayboard configuration. Here is the conclusion on the bug report: Ubuntu-ibus commits dead key sequence with empty string first, then, sends only commit string without "composing" state. The latter behavior is a usual case for inputting non-ASCII characters like Emojis. In this case, browsers need to handle it without composition for compatibility between browsers. Therefore, we cannot represent the composed character insertion as a set of composition events. Anyway, dispatching 2 set of composition events for one dead key sequence may cause trouble in web apps. Therefore, as expected, the first composition should update the "preedit string" to the composed string and commit it simply. The bug was reproduced with installing Ubuntu 22.04 with English locale and adding "French (alt., Latin-9 only)" keyboard layout. And also reproduced with the other Western keyboard layouts which have dead keys. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1999207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999578] [NEW] Bursts of high CPU usage after triggering overview
Public bug reported: As requested in the upstream bug report https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6137, I hereby file the downstream issue: I am experiencing high cpu usage of gnome-shell in situations where I would not expect it, leading to my fans running more often and wasting my battery on my Dell XPS 13 9310 2-in1. The problem can be seen in action here: https://www.youtube.com/watch?v=Y9o7a7BGPE4 See also the upstream report for syscap recordings of such situations. I think there might be a correlation with firefox being opened on another workspace (but no video or any other playback happening). At least everytime I notice that my an comes on for no reason and I fire up top to see gnome shell consuming too much cpu, when I kill all my firefox windows gnome shell cpu usage goes down as well, but that could be pure coincidence. At least I can safely rule out the triple buffering downstream ubuntu mutter patch, since I recompiled mutter without the patch and it does not really change the problem much. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: kinetic ** Attachment added: "apport.gnome-shell.4sllnc5r.apport" https://bugs.launchpad.net/bugs/1999578/+attachment/5635523/+files/apport.gnome-shell.4sllnc5r.apport -- 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/1999578 Title: Bursts of high CPU usage after triggering overview Status in gnome-shell package in Ubuntu: New Bug description: As requested in the upstream bug report https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6137, I hereby file the downstream issue: I am experiencing high cpu usage of gnome-shell in situations where I would not expect it, leading to my fans running more often and wasting my battery on my Dell XPS 13 9310 2-in1. The problem can be seen in action here: https://www.youtube.com/watch?v=Y9o7a7BGPE4 See also the upstream report for syscap recordings of such situations. I think there might be a correlation with firefox being opened on another workspace (but no video or any other playback happening). At least everytime I notice that my an comes on for no reason and I fire up top to see gnome shell consuming too much cpu, when I kill all my firefox windows gnome shell cpu usage goes down as well, but that could be pure coincidence. At least I can safely rule out the triple buffering downstream ubuntu mutter patch, since I recompiled mutter without the patch and it does not really change the problem much. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1999578/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981109] Update Released
The verification of the Stable Release Update for livecd-rootfs 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 ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1981109 Title: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container Status in fwupd package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: New Status in fwupd source package in Jammy: Invalid Status in livecd-rootfs source package in Jammy: Fix Released Status in modemmanager source package in Jammy: New Status in ubuntu-meta source package in Jammy: New Bug description: [Impact] Cloud images should not have fwupd, modemmanager, and udisks2 installed as those are not needed and only taking up memory. [Test Case] Build cloud images with livecd-rootfs and confirm that fwupd, modemmanager, and udisks2 are not present and not running. [Regression Potential] Only thing that might happen is for any of the 3 listed packages getting removed from images where they might be used. So possibly double-checking if this will affect preinstalled server images and if they care about this or not. [Original Description] Looking at memory utilization in a pristine Ubuntu lxd container (top -o RES), I see that ModemManager is running, which I was surprised to see is present at all in the stock image. Tracking this I find that fwupd depends on libmm-glib0, which in turn Recommends: modemmanager. Libraries in general should not recommend daemons, so it's possible this should be fixed by libmm-glib0 dropping this Recommends. It certainly doesn't seem to be a deliberate decision by the Server Team to have modemmanager installed and running by default on all systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container
This bug was fixed in the package livecd-rootfs - 2.765.13 --- livecd-rootfs (2.765.13) jammy; urgency=medium [ Heinrich Schuchardt ] * Backporting patches to support new RISC-V platforms (LP: #1997233) * Add support for the LicheeRV board (SUBARCH=licheerv) * Add support for the PolarFire Icicle Kit board (SUBARCH=icicle) * Reduce initrd size for Nezha and LicheeRV boards * Use efi=debug earlycon on kernel command line livecd-rootfs (2.765.12) jammy; urgency=medium * Remove fwupd, modemmanager, and udisks2 from the cloud images. LP: #1981109. -- Łukasz 'sil2100' Zemczak Mon, 21 Nov 2022 11:18:14 +0100 ** Changed in: livecd-rootfs (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1981109 Title: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container Status in fwupd package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: New Status in fwupd source package in Jammy: Invalid Status in livecd-rootfs source package in Jammy: Fix Released Status in modemmanager source package in Jammy: New Status in ubuntu-meta source package in Jammy: New Bug description: [Impact] Cloud images should not have fwupd, modemmanager, and udisks2 installed as those are not needed and only taking up memory. [Test Case] Build cloud images with livecd-rootfs and confirm that fwupd, modemmanager, and udisks2 are not present and not running. [Regression Potential] Only thing that might happen is for any of the 3 listed packages getting removed from images where they might be used. So possibly double-checking if this will affect preinstalled server images and if they care about this or not. [Original Description] Looking at memory utilization in a pristine Ubuntu lxd container (top -o RES), I see that ModemManager is running, which I was surprised to see is present at all in the stock image. Tracking this I find that fwupd depends on libmm-glib0, which in turn Recommends: modemmanager. Libraries in general should not recommend daemons, so it's possible this should be fixed by libmm-glib0 dropping this Recommends. It certainly doesn't seem to be a deliberate decision by the Server Team to have modemmanager installed and running by default on all systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3
Marc, 102.6 was officially released today, so I've gone ahead and updated my jammy mozjs branch for it. I added the CVEs you mentioned and found one more I found from 102.4. I don't see any new ones for 102.6 I've also created a ubuntu/102/kinetic branch for mozjs102 for kinetic. Since it doesn't have the gjs major update issue, I believe it could be pushed sooner than jammy. For Jammy, I think the general plan is for this update to be built in security-proposed and then published/copied to jammy-proposed for wider testing before being pushed to jammy-security. My understanding is that the Ubuntu Desktop and Ubuntu SRU teams have come to an agreement that we will test all the gnome-shell extensions that are available in the official Ubuntu repositories (for 22.04 LTS and later). Extensions installed outside of the official Ubuntu repositories are unsupported, just like anything that is user-installed outside of Ubuntu. However, we aren't aware of any likely breakage for any GNOME Shell extensions caused by this proposed update. There is no formal API for GNOME Shell extensions which allows extensions to have tremendous power but it's easily possible for an extension to break GNOME Shell so that it's not possible for GNOME Shell to run correctly or even start. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1993214 Title: [jammy] Update gjs to 1.74 using mozjs102 102.3 Status in gjs package in Ubuntu: Confirmed Status in mozjs102 package in Ubuntu: Confirmed Bug description: Impact -- GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 ESR series for security updates for the next year. This requires updating gjs from 1.72 to 1.74 from GNOME 43, as packaged in Ubuntu 22.10. This will be done as a Security Update. Updating mozjs in stable Ubuntu releases was recommended when Ubuntu first switched back to GNOME, but this is the first time it's been done. Security Impact --- I looked through https://github.com/mozilla/gecko-dev/commits/esr102/js and searched for referenced bug numbers in https://www.mozilla.org/en-US/security/advisories/ for Firefox ESR releases since Ubuntu's 91.10 and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE issued) mentioned at https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/ Uploaded Packages - We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being careful to publish it in main, not universe. And we'll update gjs. No other packages need to be updated for this change. mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are generally not possible), but nothing else in Ubuntu uses it. Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs Security Sponsoring --- sudo apt install git-buildpackage gbp clone https://salsa.debian.org/gnome-team/gjs cd gjs git checkout ubuntu/jammy gbp buildpackage --git-builder="debuild -S -nc" mkdir ../tarballs; cd ../tarballs pull-lp-source mozjs102 kinetic cd .. gbp clone https://salsa.debian.org/gnome-team/mozjs cd mozjs git checkout ubuntu/102/jammy gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs # That avoids needing to recreate the original tarball from pristine-tar which takes a while. Also, running lintian takes a while. Initial Testing Done I built the packages in my PPA. I installed the packages on Ubuntu 22.04 LTS and successfully completed the Test Case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999207] Re: Error in dead key management of latin keyboards
I'm a bit confused about your questions related with xkb-data but I hope that this will help: here is the result of `setxkbmap -print`: xkb_keymap { xkb_keycodes { include "evdev+aliases(azerty)" }; xkb_types { include "complete" }; xkb_compat{ include "complete" }; xkb_symbols { include "pc+fr(latin9)+fr(oss):2+inet(evdev)" }; xkb_geometry { include "pc(pc105)" }; }; And `setxkbmap -query`: rules: evdev model: pc105 layout: fr,fr variant:latin9,oss About the consequences for users, well, the source of all this is the breaking of compositionupdate and compositionend events for those users on Firefox. My app relies on compositionend events, but, as those events were not created by myself, I guess that my app is not the only program relying on those events. If those events are not accurate, it will break any program relying on it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1999207 Title: Error in dead key management of latin keyboards Status in ibus package in Ubuntu: Incomplete Bug description: Composition events are incorrect in Ubuntu 22.04 for latin keyboard I opened an issue at Firefox [here](https://bugzilla.mozilla.org/show_bug.cgi?id=1802989) that gives all the details, but they diagnosed a bug in ubuntu-ibus To reproduce the issue, you can go [here](https://developer.mozilla.org/en- US/docs/Web/API/Element/compositionstart_event#result) and type ^+u with a fr+latin9 keayboard configuration. Here is the conclusion on the bug report: Ubuntu-ibus commits dead key sequence with empty string first, then, sends only commit string without "composing" state. The latter behavior is a usual case for inputting non-ASCII characters like Emojis. In this case, browsers need to handle it without composition for compatibility between browsers. Therefore, we cannot represent the composed character insertion as a set of composition events. Anyway, dispatching 2 set of composition events for one dead key sequence may cause trouble in web apps. Therefore, as expected, the first composition should update the "preedit string" to the composed string and commit it simply. The bug was reproduced with installing Ubuntu 22.04 with English locale and adding "French (alt., Latin-9 only)" keyboard layout. And also reproduced with the other Western keyboard layouts which have dead keys. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1999207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997578] Re: [MIR] liblc3
liblc3 1.0.1-1ubuntu3 in lunar: universe/misc -> main Override [y|N]? y 1 publication overridden. ** Changed in: liblc3 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to liblc3 in Ubuntu. https://bugs.launchpad.net/bugs/1997578 Title: [MIR] liblc3 Status in liblc3 package in Ubuntu: Fix Released Bug description: [Availability] The package liblc3 is already in Ubuntu universe. The package liblc3 build for the architectures it is designed to work on. It currently builds and works for architetcures: amd64 arm64 armhf ppc64el riscv64 s390x Link to package https://launchpad.net/ubuntu/+source/liblc3 [Rationale] - The package liblc3 is required in Ubuntu main for low energy bluetooth devices handling in pipewire. - The package liblc3 is going to benefit users with compatible hardware which is important since we want users to be able to have high quality audio calls on Ubuntu. - The package liblc3 is required in Ubuntu main no later than Feb 23 due to feature freeze [Security] - No CVEs/security issues in this software in the past - no `suid` or `sgid` binaries - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Packages does not open privileged ports (ports < 1024) - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is maintained well in Debian/Ubuntu and has currently no open reports - Ubuntu https://bugs.launchpad.net/ubuntu/+source/liblc3/+bug - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=liblc3 - The package does not deal with exotic hardware we cannot support [Quality assurance - testing] - The package runs a test suite on build time, if it fails it makes the build fail, link to build log https://launchpadlibrarian.net/635552525/buildlog_ubuntu-lunar-amd64.liblc3_1.0.1-1ubuntu2_BUILDING.txt.gz - The package runs an autopkgtest, and is currently passing on amd64 arm64 armhf ppc64el riscv64 link to test logs https://autopkgtest.ubuntu.com/packages/libl/liblc3 (we ignore i386 doesn't provide the needed python build-depends and is only used for multiarch, the codecs aren't going to be used on it and s390x isn't a target architecture for bluetooth audio) Testing of bluetooth codecs in cloud CI isn't really possible so in addition to the library tests the package will manually tested by connecting an bluetooth low energy compatible headset and verifying that the audio quality expected is experienced in a video call and audio recording. That also got added to the https://wiki.ubuntu.com/DesktopTeam/TestPlans/Pipewire. [Quality assurance - packaging] - debian/watch is present and works - The package has only minor lintian warnings - Please link to a recent build log of the package https://launchpadlibrarian.net/635552525/buildlog_ubuntu-lunar-amd64.liblc3_1.0.1-1ubuntu2_BUILDING.txt.gz - # lintian --pedantic W: liblc3-tools: no-manual-page [usr/bin/dlc3] W: liblc3-tools: no-manual-page [usr/bin/elc3] While having a manpage for the tools would be nice we consider it as a minor issue, especially that we will not install that binary by default - Lintian overrides are not present - This package does not rely on obsolete or about to be demoted packages. - This package has no python2 or GTK2 dependencies - The package will be installed by default, but does not ask debconf questions - Packaging and build is easy, link to d/rules https://salsa.debian.org/multimedia- team/liblc3/-/blob/master/debian/rules [UI standards] - Application is not end-user facing (does not need translation) [Dependencies] - No further depends or recommends dependencies that are not yet in main [Standards compliance] - This package correctly follows FHS and Debian Policy [Maintenance/Owner] - Owning Team will be desktop-packages - Team is already subscribed to the package - This does not use static builds - This does not use vendored code - This package is not rust based - The package has been built in the archive more recently than the last test rebuild [Background information] The Package description explains the package well Upstream Name is liblc3 Link to upstream project https://github.com/google/liblc3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liblc3/+bug/1997578/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999207] Re: Error in dead key management of latin keyboards
Are you using some layout which is not provided by xkb-data? The one I used is named "French (alt., Latin-9 only)" and is represented by the dconf value fr+oss_latin9. The dconf value fr+latin9 is also available, but the name of that layout is "French (legacy, alt.)". I'm not sure about the significance of which particular layout is used, though. But I'm wondering in what way your observation results in unexpected behavior for the user. Yes, there are differences under the hood. But how is that important in practice? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1999207 Title: Error in dead key management of latin keyboards Status in ibus package in Ubuntu: Incomplete Bug description: Composition events are incorrect in Ubuntu 22.04 for latin keyboard I opened an issue at Firefox [here](https://bugzilla.mozilla.org/show_bug.cgi?id=1802989) that gives all the details, but they diagnosed a bug in ubuntu-ibus To reproduce the issue, you can go [here](https://developer.mozilla.org/en- US/docs/Web/API/Element/compositionstart_event#result) and type ^+u with a fr+latin9 keayboard configuration. Here is the conclusion on the bug report: Ubuntu-ibus commits dead key sequence with empty string first, then, sends only commit string without "composing" state. The latter behavior is a usual case for inputting non-ASCII characters like Emojis. In this case, browsers need to handle it without composition for compatibility between browsers. Therefore, we cannot represent the composed character insertion as a set of composition events. Anyway, dispatching 2 set of composition events for one dead key sequence may cause trouble in web apps. Therefore, as expected, the first composition should update the "preedit string" to the composed string and commit it simply. The bug was reproduced with installing Ubuntu 22.04 with English locale and adding "French (alt., Latin-9 only)" keyboard layout. And also reproduced with the other Western keyboard layouts which have dead keys. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1999207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999207] Re: Error in dead key management of latin keyboards
Here is a layout looking almost like mine: https://en.wikipedia.org/wiki/AZERTY#/media/File:KB_France.svg I press the key which is to the right to `p` and to the left of `$ ` and do not need to hold AltGr nor Shift. If you run `gkbd-keyboard-display -l latin-9`, you should see my layout. It doesn't look like what you describe. Don't hesitate if I can help more. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1999207 Title: Error in dead key management of latin keyboards Status in ibus package in Ubuntu: Incomplete Bug description: Composition events are incorrect in Ubuntu 22.04 for latin keyboard I opened an issue at Firefox [here](https://bugzilla.mozilla.org/show_bug.cgi?id=1802989) that gives all the details, but they diagnosed a bug in ubuntu-ibus To reproduce the issue, you can go [here](https://developer.mozilla.org/en- US/docs/Web/API/Element/compositionstart_event#result) and type ^+u with a fr+latin9 keayboard configuration. Here is the conclusion on the bug report: Ubuntu-ibus commits dead key sequence with empty string first, then, sends only commit string without "composing" state. The latter behavior is a usual case for inputting non-ASCII characters like Emojis. In this case, browsers need to handle it without composition for compatibility between browsers. Therefore, we cannot represent the composed character insertion as a set of composition events. Anyway, dispatching 2 set of composition events for one dead key sequence may cause trouble in web apps. Therefore, as expected, the first composition should update the "preedit string" to the composed string and commit it simply. The bug was reproduced with installing Ubuntu 22.04 with English locale and adding "French (alt., Latin-9 only)" keyboard layout. And also reproduced with the other Western keyboard layouts which have dead keys. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1999207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc
Thanks for the report. Can you please 1. confirm that the issue is reproducible with the Pipewire flag in about:flags turned on? 2. attach the output of journalctl around the time that happens? -- 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/1999487 Title: Webcam does not work with v107.0.5304.121-hwacc Status in chromium-browser package in Ubuntu: New Bug description: With the latest version of Chromium in the stable channel (108.0.5359.94), I can access the webcam and the microphone in Google Meet and Jitsi (using a framatalk.org instance). However, with version 107.0.5304.121-hwacc (from latest/candidate/hwacc branch), the same test does not work. The only difference between the two in `snap connections chromium` is content chromium:va-driver-non-free - - Test: 1. Install Chromium from the given channel 2. Go to https://framatalk.org/ and click on "Create a room" 3. Accept the permissions to access Microphone and Camera Expected result: Image from camera is displayed on screen Actual result: The webcam is turned on (the LED turns on), but no image is captured, and after a few seconds, an error message is displayed ("We are unable to access your camera"). In the settings, I can see the camera name ("UVC Camera (046d:0802)"). Attached are two logs: - One retrieved by launching Chromium with `chromium --enable-logging=stderr`, accessing framatalk.org and clicking on "Create a room". - One retrieved by launching Chromium with `chromium --enable-logging=stderr` and accessing a Google Meet event. Configuration information = - Desktop with AMD GPU RX580 - Ubuntu 20.04 (kernel 5.15.0-56-generic) - Webcam: 046d:0802 Logitech, Inc. Webcam C200 - Headset: 046d:0a38 Logitech, Inc. Headset H340 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999546] [NEW] HP DesignJet T120 walks flawlessly with Bionic, but not Focal or Jammy
Public bug reported: On a freshly installed Bionic system our DesignJet T120 is auto-detected as a driverless IPP printer as soon as it is switched on, and I can directly select it as the printer to use in print dialogs. On Focal and later it is not auto detected anymore (also tried with fresh installations), it is found when using "Add printer" in the printer settings, but no matter which of the provided driver options I use I can't make the printer print anything. See also this earlier forums post, without which I'd probably never have figured what was wrong in the first place, so that I for now at least can use the printer via a Bionic VM: https://ubuntuforums.org/showthread.php?t=2450952 ** Affects: hplip (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1999546 Title: HP DesignJet T120 walks flawlessly with Bionic, but not Focal or Jammy Status in hplip package in Ubuntu: New Bug description: On a freshly installed Bionic system our DesignJet T120 is auto- detected as a driverless IPP printer as soon as it is switched on, and I can directly select it as the printer to use in print dialogs. On Focal and later it is not auto detected anymore (also tried with fresh installations), it is found when using "Add printer" in the printer settings, but no matter which of the provided driver options I use I can't make the printer print anything. See also this earlier forums post, without which I'd probably never have figured what was wrong in the first place, so that I for now at least can use the printer via a Bionic VM: https://ubuntuforums.org/showthread.php?t=2450952 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1999546/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999472] Re: Dark mode not working correctly
Added package. ** Description changed: Version of Ubuntu: 22.10 - Package: ? + Package: X.org Expected to happen: Toolbox on the top right corner should stay in dark mode all the time. What happened instead: When accessing appearance options at config menu, the toolbox on the top right corner goes white, not corresponding with the dark mode selected on the config menu. ** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1999472 Title: Dark mode not working correctly Status in xorg package in Ubuntu: New Bug description: Version of Ubuntu: 22.10 Package: X.org Expected to happen: Toolbox on the top right corner should stay in dark mode all the time. What happened instead: When accessing appearance options at config menu, the toolbox on the top right corner goes white, not corresponding with the dark mode selected on the config menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1999472/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999472] [NEW] Dark mode not working correctly
You have been subscribed to a public bug: Version of Ubuntu: 22.10 Package: X.org Expected to happen: Toolbox on the top right corner should stay in dark mode all the time. What happened instead: When accessing appearance options at config menu, the toolbox on the top right corner goes white, not corresponding with the dark mode selected on the config menu. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Dark mode not working correctly https://bugs.launchpad.net/bugs/1999472 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1979096] Re: gnome-shell search can't launch apps if dock auto-hide is enabled
I have the same issue with the latest gnome-shell-extension-ubuntu-dock - 74ubuntu2 It's related to display scaling, using 200% has this issue. In my case I need to use display scaling otherwise the texts are extremely small on my screen. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1979096 Title: gnome-shell search can't launch apps if dock auto-hide is enabled Status in Dash to dock: Fix Released Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Confirmed Bug description: The problem happens, when I enable the dock to hide automatically. With this enabled, it is not possible to run the programs through the search. But when disabled, it is possible to search and run the programs. Here's the video of the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 17 18:21:45 2022 DistUpgraded: 2022-04-21 13:52:59,951 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-37-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-39-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. RS780L [Radeon 3000] [1043:8388] InstallationDate: Installed on 2021-04-15 (428 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=7e3c483e-6d02-4fc2-be0e-48207eb147eb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-21 (57 days ago) dmi.bios.date: 03/04/2017 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX/BR dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd03/04/2017:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1 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/dash-to-dock/+bug/1979096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971126] Re: unable to click on application search results
*** This bug is a duplicate of bug 1979096 *** https://bugs.launchpad.net/bugs/1979096 I have the same issue, disabling all extensions does not help. The bug appears when auto-hide is on, so basically makes auto-hide unusable. -- 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/1971126 Title: unable to click on application search results Status in gnome-shell package in Ubuntu: Incomplete Bug description: When searching for applications under the Activities section, application results appear but cannot be clicked on to start them. Attempting to use the arrow keys to navigate between the results also doesn't work. However, if the enter key is pressed, the first result will load. Other types of results can be clicked on to open them, such as folder results in Files. This appears to be a regression from previous versions. Description: Ubuntu 22.04 LTS Release: 22.04 gnome-shell: Installed: 42.0-2ubuntu1 Candidate: 42.0-2ubuntu1 Version table: *** 42.0-2ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon May 2 07:57:00 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-02-28 (62 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-22 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1971126/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
The 1.20 components have been uploaded to the 22.04 SRU queue now. @oem it would be nice if you could improve the bug description to have a more detailed testcase and regression potential section ** Description changed: * Impact Fibocom FM350 modems aren't working with the current version of modemmanager in 22.04. * Test case - Try connecting to 5G using a FM350 modem + - install modemmanager, libmbim, and libqmi from -proposed + - reboot and try WWAN function to see if any regression there. + - perform dogfooding of its reverse dependencies (network- + manager, gnome-control-center etc.) + + The verification should be done on FM350 to ensure it's correctly + handled but also on other hardware to verify that there are no + regressions * Regression potential The SRU does an update to new modemmanager serie so we should do a complete round of testing on different hardware and confirm there are no regression. - --- - :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux- wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ Modemmanager requires >= 1.19.1, the detail info is in lp:1962525 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation ** Changed in: modemmanager (Ubuntu) Importance: Undecided => High ** Changed in: modemmanager (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in modemmanager package in Ubuntu: Fix Released Bug description: * Impact Fibocom FM350 modems aren't working with the current version of modemmanager in 22.04. * Test case - install modemmanager, libmbim, and libqmi from -proposed - reboot and try WWAN function to see if any regression there. - perform dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) The verification should be done on FM350 to ensure it's correctly handled but also on other hardware to verify that there are no regressions * Regression potential The SRU does an update to new modemmanager serie so we should do a complete round of testing on different hardware and confirm there are no
[Desktop-packages] [Bug 1998765] Re: libnl3 3.4.0 doesn't work with WCN3980
** Also affects: oem-priority/focal Importance: Undecided Assignee: Robert Liu (robertliu) Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1998765 Title: libnl3 3.4.0 doesn't work with WCN3980 Status in OEM Priority Project: New Status in OEM Priority Project focal series: New Status in libnl3 package in Ubuntu: New Bug description: [ Impact ] When testing Qualcomm qcs410 with WCN3980 with 20.04 and UC20, WCN3980 is not able connect to an AP. However, with the libnl3 (3.5.0) from BSP, WCN3980 can work correctly. After bisecting the commits from 3.4.0 to 3.5.0, this commit[1] is identified as the root cause. According to the commit, the "NLA_F_NESTED" flag should be set for kernel later than 5.2. [ Test Plan ] Verify with the updated version, the WIFI module can: 1. scan WIFI networks 2. connect to an available network 3. access to the connected network [ Where problems could occur ] 1. kernel versions without NLA_F_NESTED flag defined This flag is introduced before Linux kernel v5 (checked v3.x and v4.x have it). It would not be a problem for an older kernel to understand/work with this change. Since the GA kernel is 5.4, so a generic image would still work. 2. Drivers don't use the NESTED flag. According to hui.wang's input, this change should not affect drivers which don't use the NESTED flag. But, it'd be better to cover more Wifi modules. [ Other Info ] 22.04 is using libnl3 3.0.5-0.1, so only 20.04 needs this patch. [1] https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754477] Re: totem crashed with SIGSEGV in memcpy() from gen8_render_init() from i965_Init() from __vaDriverInit_1_0()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: totem (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1754477 Title: totem crashed with SIGSEGV in memcpy() from gen8_render_init() from i965_Init() from __vaDriverInit_1_0() Status in intel-vaapi-driver package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: Just after starting up the ubuntu session. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Sun Mar 4 11:24:46 2018 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-02-23 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) ProcCmdline: totem ProcEnviron: LANGUAGE=de_AT:de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe15ef8e696 <__memmove_sse2_unaligned_erms+374>: movaps %xmm0,(%rdi) PC (0x7fe15ef8e696) ok source "%xmm0" ok destination "(%rdi)" (0x0010) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so __vaDriverInit_1_0 () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so ?? () from /usr/lib/x86_64-linux-gnu/libva.so.2 vaInitialize () from /usr/lib/x86_64-linux-gnu/libva.so.2 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so Title: totem crashed with SIGSEGV in __vaDriverInit_1_0() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1754477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754477] Re: totem crashed with SIGSEGV in memcpy() from gen8_render_init() from i965_Init() from __vaDriverInit_1_0()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: intel-vaapi-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1754477 Title: totem crashed with SIGSEGV in memcpy() from gen8_render_init() from i965_Init() from __vaDriverInit_1_0() Status in intel-vaapi-driver package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: Just after starting up the ubuntu session. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Sun Mar 4 11:24:46 2018 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-02-23 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) ProcCmdline: totem ProcEnviron: LANGUAGE=de_AT:de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe15ef8e696 <__memmove_sse2_unaligned_erms+374>: movaps %xmm0,(%rdi) PC (0x7fe15ef8e696) ok source "%xmm0" ok destination "(%rdi)" (0x0010) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so __vaDriverInit_1_0 () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so ?? () from /usr/lib/x86_64-linux-gnu/libva.so.2 vaInitialize () from /usr/lib/x86_64-linux-gnu/libva.so.2 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so Title: totem crashed with SIGSEGV in __vaDriverInit_1_0() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1754477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
** Description changed: + * Impact + + Fibocom FM350 modems aren't working with the current version of + modemmanager in 22.04. + + * Test case + + Try connecting to 5G using a FM350 modem + + * Regression potential + + The SRU does an update to new modemmanager serie so we should do a + complete round of testing on different hardware and confirm there are no + regression. + + + --- + + :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux- wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ Modemmanager requires >= 1.19.1, the detail info is in - lp:1962525 + lp:1962525 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in modemmanager package in Ubuntu: Confirmed Bug description: * Impact Fibocom FM350 modems aren't working with the current version of modemmanager in 22.04. * Test case Try connecting to 5G using a FM350 modem * Regression potential The SRU does an update to new modemmanager serie so we should do a complete round of testing on different hardware and confirm there are no regression. --- :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux- wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ Modemmanager requires >= 1.19.1, the detail info is in lp:1962525 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-0
[Desktop-packages] [Bug 1916640] Re: Nvidia 340.108 driver provided by Butterfly (kelebek333) works very well till kernel 5.17.x but not beyond
Just for info, I mean if anyone wants to port them :-), Debian SID already has drivers patched for kernel 6.1 called nvidia-legacy-340xx- driver. Please check it out here: https://metadata.ftp-master.debian.org/changelogs//non-free/n/nvidia-graphics-drivers-legacy-340xx/nvidia-graphics-drivers-legacy-340xx_340.108-17_changelog Drivers may be found here: https://packages.debian.org/sid/nvidia-legacy-340xx-driver I tried to add Debian repo to Ubuntu as a joke in the past but obviously it was unsuccessful. Anyway I will try again to look for errors that prevent it from installing coming soon. If someone has already succeeded, please notify others and post the method used. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1916640 Title: Nvidia 340.108 driver provided by Butterfly (kelebek333) works very well till kernel 5.17.x but not beyond Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: As usual I have opened this (no more) new bug report... As ALWAYS happened in the past, EVERY TWO MONTHS new patches are needed for old Nvidia 340.108 drivers, that is, with each release of a new kernel... Nvidia 340.108 fails to install with kernels 5.11.x - new patches needeed Just to inform develepers that a new patch for Nvidia 340.108 and kernel 5.11 is not yet available here: https://github.com/warpme/minimyth2/blob/master/script/nvidia/nvidia-340.108/files/ Anyway thanks for your great contribution to community and hope you publish new patched drivers without having to always report the same bug... Good day to all the developers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1916640/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918044] Re: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore
This release was made specifically to help out older LTS distributions which cannot migrate to newer libgweather. What needs to be done to get it into 20.04? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1918044 Title: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore Status in libgweather: Fix Released Status in gnome-weather package in Ubuntu: Fix Released Status in libgweather package in Ubuntu: Fix Released Status in gnome-weather source package in Focal: Confirmed Status in libgweather source package in Focal: Confirmed Status in gnome-weather package in Fedora: New Bug description: [Impact] The weather forecast is not available since one week now. Also, the weather info is gone from gnome-shell. The weather service provider retired their old API. https://developer.yr.no/news/important-changes-to-locationforecast-and-nowcast/ https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS == Version 3.36.2 == This version switches the yr.no backend to use met.no instead. Please note that this backport is only meant as a compatibility layer. Where at all possible, the newer libgweather 40 should be used as applications cannot fully comply with the met.no ToS otherwise. [Test case] - gnome-weather shows the weather forecast - gnome-shell shows the weather forecast in the calendar menu [Regression potential] - Weather forecast is totally broken now and can't be more broken. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.1-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 7 09:54:52 2021 InstallationDate: Installed on 2020-04-26 (314 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1918044/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999335] Re: Please remove vte from Ubuntu
It should be removed, but this package is synced from Debian. File a removal request there? (BTW, 'lucid' is the wrong tag by 13 years ;) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1999335 Title: Please remove vte from Ubuntu Status in vte package in Ubuntu: New Bug description: The vte source package is an old version of vte that hasn't been maintained in many years. The current version is packaged with source package name vte2.91 vte is still around in Debian because debian-installer has not yet switched to GTK3. However, Ubuntu no longer supports debian-installer and nothing in Ubuntu uses the old vte. Therefore, please remove vte from Ubuntu. $ reverse-depends src:vte $ reverse-depends -b src:vte No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1999335/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp