[Desktop-packages] [Bug 1946096] Re: Apply upstream patches to fix problems for Foxconn and Quectel modems.
Hi SRU team, Please help to check the status of this case which looks stuck at some steps. Thanks -- 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/1946096 Title: Apply upstream patches to fix problems for Foxconn and Quectel modems. Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: Fix Committed Bug description: [Impact] The following 2 modems need the ModemManager v1.16.6 suite to be patched from v1.18.2 to fix some problems(LP#1943774, LP#1943780): * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 4. Using the firmware upgrading application to upgrade the modem’s firmware 5. Verify if the modem’s firmware upgrading is successful 6. Reboot 7. Verify if the upgraded modem firmware is still working [Where problems could occur] The requested upstream patches are for these 2 specific modems and the status information. This should not affect existing generic functions and other modems. [Other Info] The firmware and the upgrading application can be downloaded from the following link: * LP#1943774 for Quectel modems * LP#1943780 for Foxconn modems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+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 1947746] Re: [Snap] Ubuntu Firefox installed from snap cannot use Trezor U2F
Thanks Olivier Tilloy for your quick response. The Trezor works well. Even for the web wallet on https://wallet.trezor.io Maybe because they use Trezor Bridge It's just the U2F/FIDO2 functionality that doesn't works Here is the `lsusb` $ lsusb Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 002: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 009: ID 30de:6544 KIOXIA TransMemory Bus 003 Device 008: ID 0bda:8152 Realtek Semiconductor Corp. RTL8152 Fast Ethernet Adapter Bus 003 Device 010: ID 1209:53c1 Generic SatoshiLabs TREZOR Bus 003 Device 007: ID 214b:7250 Huasheng Electronics USB2.0 HUB Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 048d:5702 Integrated Technology Express, Inc. ITE Device Bus 001 Device 002: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter Bus 001 Device 007: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 006: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 005: ID 046d:0825 Logitech, Inc. Webcam C270 Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1947746 Title: [Snap] Ubuntu Firefox installed from snap cannot use Trezor U2F Status in firefox package in Ubuntu: Incomplete Bug description: Trezor U2F security key doesn't work with firefox snap after updating to Ubuntu 21.10, but works with apt debian firefox package. Steps to reproduce: 1) Insert Trezor U2F security key in USB port. 2) Launch `run snap firefox` (it is the default on Ubuntu 21.10) 3) Test https://demo.yubico.com/webauthn-technical/registration It works well on Ubuntu 21.04 and on traditional apt debian installation. $ snap list firefox Name Version Rev Tracking Publisher Notes firefox 93.0-1 631 latest/stable mozilla✓ - $ snap connections firefox Interface PlugSlot Notes audio-playbackfirefox:audio-playback :audio-playback - audio-record firefox:audio-record:audio-record - avahi-observe firefox:avahi-observe :avahi-observe - browser-support firefox:browser-sandbox :browser-support - camerafirefox:camera :camera - content[gnome-3-38-2004] firefox:gnome-3-38-2004 gnome-3-38-2004:gnome-3-38-2004 - content[gtk-3-themes] firefox:gtk-3-themes gtk-common-themes:gtk-3-themes - content[icon-themes] firefox:icon-themes gtk-common-themes:icon-themes- content[sound-themes] firefox:sound-themes gtk-common-themes:sound-themes - cups-control firefox:cups-control:cups-control - dbus - firefox:dbus-daemon - desktop firefox:desktop :desktop - desktop-legacyfirefox:desktop-legacy :desktop-legacy - gsettings firefox:gsettings :gsettings - hardware-observe firefox:hardware-observe:hardware-observe - home firefox:home:home - joystick firefox:joystick- - mpris - firefox:mpris - network firefox:network :network - network-observe firefox:network-observe - - openglfirefox:opengl :opengl - personal-filesfirefox:dot-mozilla-firefox :personal-files - removable-media firefox:removable-media :removable-media - screen-inhibit-controlfirefox:screen-inhibit-control :screen-inhibit-control - system-files firefox:etc-firefox-policies:system-files - system-packages-doc firefox:system-packages-doc :system-packages-doc - u2f-devices firefox:u2f-devices :u2f-devices
[Desktop-packages] [Bug 1946143] Re: Apply upstream patches to display 5G NSA status
Hi,
The libqmi packages from the {impish, hirsute, focal}-proposed channels
wrere verified.
The 5G status information can be displayed using the package from the
-proposed channel.
The detail testing report is attached as "Test Report for
LP#1946143.pdf".
Thanks
** Attachment added: "Test Report for LP#1946143.pdf"
https://bugs.launchpad.net/oem-priority/+bug/1946143/+attachment/5534488/+files/Test%20Report%20for%20LP%231946143.pdf
** Tags removed: verification-needed verification-needed-focal
verification-needed-hirsute verification-needed-impish
** Tags added: verification-done verification-done-focal
verification-done-hirsute verification-done-impish
** Tags removed: verification-done verification-done-focal
verification-done-hirsute verification-done-impish
** Tags added: verification-needed verification-needed-focal
verification-needed-hirsute verification-needed-impish
** Tags removed: verification-needed-focal verification-needed-hirsute
verification-needed-impish
** Tags added: verification-done-focal verification-done-hirsute
verification-done-impish
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libqmi in Ubuntu.
https://bugs.launchpad.net/bugs/1946143
Title:
Apply upstream patches to display 5G NSA status
Status in OEM Priority Project:
In Progress
Status in libqmi package in Ubuntu:
Fix Committed
Status in libqmi source package in Focal:
Fix Committed
Status in libqmi source package in Hirsute:
Fix Committed
Status in libqmi source package in Impish:
Fix Committed
Bug description:
[Impact]
The 5G NSA status can not be displayed in the libqmi version 1.28.6-1.
(LP#1937012)
The 5G NSA status is supported in the libqmi version 1.30.2.
The requested upstream patches are listed as below:
* 5G NSA status patches
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/29905223c5ae6e5e4ef9246dd9dd4d01b2819d9a
* qmicli,nas: flag as 'n/a' the 5G NSA signal quality if not connected
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/b05df7b658f9cfb4c5e74a3e07913de689914a8f
[Test Plan]
1. Install the Ubuntu image.
2. Boot and login the system.
3. Verify if the field “5G NSA Available: ” can be displayed via executing:
$ sudo qmicli --device=/dev/wwan0p2MBIM --device-open-proxy
--nas-get-system-info
...
5G NSA Available: 'no'
...
[Where problems could occur]
The requested upstream patches are for displaying the status information of
5G NSA network.
This should not affect existing generic functions.
[Other Info]
The latest version of libqmi suit can display the 5G NSA status.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1946143/+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 1930188] Re: Acer Aspire 5 sound driver issues
All 7 packages were not yet available from software updater in focal but I managed to upgrade them using apt-get upgrade and seems to work fine. Thanks all again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Committed Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1. Headphones appears always plugged in even if they are physically not 2. When actually plugging in headset/earphones it does not auto switch from speakers/internal mic to headphones/headset microphone automatically and vice versa, have to manually switch everytime. 3.
[Desktop-packages] [Bug 27867]
Data Visualization is the key to unlocking the true stories that your data has always wanted to tell. Building effective visualization on agile and extensible modern data platforms can become the key to unlocking silos of information and driving transformation forward for your career and enterprise. https://saxonglobal.com/services/data-visualization/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/27867 Title: Background color is always white, top banner is never displayed in Firefox Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Released Bug description: Problem shows whatever the version of Epiphany (before and after today's upodate ie). Whatever the website I visit, the background colour is always white, and the logo/banner at the top of the page, is not displayed. I attached an example, showing Ubuntu bugzilla. No Ubuntu logo at the top, and no yellow background. http://bugzilla.gnome.org/show_bug.cgi?id=121118: http://bugzilla.gnome.org/show_bug.cgi?id=121118 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/27867/+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 1947194] Re: When using Wayland in 21.04, the display often never wakes up after lock
Thanks. Those crashes are from gnome-shell crashing in libglib-2.0.so.0.6800.1+43647 but we don't have any useful debug symbols in them :( Please open the Extensions app and ensure you don't have any extensions enabled other than the Ubuntu ones. Please also upgrade to 21.10 when you can as we are more keen to find out if such bugs exist there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1947194 Title: When using Wayland in 21.04, the display often never wakes up after lock Status in mutter package in Ubuntu: Incomplete Bug description: When using Wayland in 21.04, the display often never wakes up after lock up. Also, on boot up, desktop icons and most favorites on dash are not displayed, even though desktop icons are enabled. I can get them to show up only by re-enabling desktop icons. The workaround now is to disable Wayland, and the original xorg server works fine. The display driver is: 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) The monitor is an HP 22cwa running of of a displayport interface. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 14 14:32:26 2021 DistUpgraded: 2021-07-28 16:05:54,589 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:047e] InstallationDate: Installed on 2018-12-04 (1044 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. OptiPlex 990 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-07-28 (77 days ago) dmi.bios.date: 11/24/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd11/24/2011:br4.6:svnDellInc.:pnOptiPlex990:pvr01:sku:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1947194/+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 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
** Tags added: impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height Status in GNOME Terminal: New Status in gnome-terminal package in Ubuntu: Triaged Bug description: 1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt + T) 2. "stty -a | grep rows" reports "rows 24; columns 80;" 3. Maximize the window (by clicking on the maximize button, or double clicking the title bar, or dragging the window up to the panel) 4. Do the same again to un-maximize the window 5. Now "stty -a | grep rows" reports "rows 23; columns 79;" Each time I do this, the window keeps getting one character shorter and one character narrower! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Mar 6 10:22:46 2014 InstallationDate: Installed on 2010-04-15 (1421 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+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)
** Tags added: hirsute impish -- 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 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition
Launchpad has imported 4 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1734791. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2021-10-08T07:21:39+00:00 Marian+mozilla wrote: User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/93.0.4577.99 Safari/537.36 Steps to reproduce: This issue concerns the Firefox snap package. I have configured Firefox to use SPNEGO authentication against my authentication server using the policy `Authentication/SPNEGO` (as documented at https://github.com/mozilla/policy- templates/blob/master/README.md#authentication). Firefox shows the policy in `about:policies` and the corresponding setting `network.negotiate-auth.trusted-uris` in `about:config`, so the policy is found and applied correctly. Actual results: Even though the policy is active, Firefox does not attempt Kerberos authentication against my authentication server. The exact same policy DOES work with the regular deb-based version of Firefox, so the issue has to be in the snap package. I guess that the snap version does not have access to the required files and/or environment variables. I logged which files and directories the deb-based Firefox accesses that seem to have to do with Kerberos/SPNEGO using `strace -f -t -e trace=file firefox` on my system running Ubuntu 21.10 beta: ``` /lib/x86_64-linux-gnu/libgssapi_krb5.so.2 /lib/x86_64-linux-gnu/libkrb5.so.3 /lib/x86_64-linux-gnu/libk5crypto.so.3 /lib/x86_64-linux-gnu/libkrb5support.so.0 /etc/gss/mech /etc/gss/mech.d /etc/krb5.conf /etc/krb5/user/10017/client.keytab /usr/share/locale/*/LC_MESSAGES/mit-krb5.mo /usr/share/locale-langpack/*/LC_MESSAGES/mit-krb5.mo /tmp/krb5cc_10017_QfHqc3 ``` `10017` is the user ID of the user running firefox. The last file `/tmp/krb5cc_10017_QfHqc3` is the user's Kerberos ticket cache, which is given by the environment variable `KRB5CCNAME`. So the first step would be to allow the snap to access the listed files and directories, as well as to the environment variable `KRB5CCNAME`. Of course, the list is just generated by looking at the deb-based Firefox on my system and might not be complete. In any case, I'd be happy to test an updated snap. Expected results: Kerberos/SPNEGO authentication should work the same as in the deb-based Firefox. Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1849346/comments/14 On 2021-10-12T12:27:10+00:00 Andrei-purice wrote: Setting a component for this issue in order to get the dev team involved. If you feel it's an incorrect one please feel free to change it to a more appropriate one. Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1849346/comments/17 On 2021-10-15T14:11:37+00:00 Olivier Tilloy wrote: Triagers, please update the component to "Release Automation: Snap" and add a blocks reference to bug 1665641. Thanks! Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1849346/comments/19 On 2021-10-18T07:57:39+00:00 Daniel Calcoen wrote: There are several references across the internet about similar problems. https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849346 Firefox with Kerberos/SPENGO works fine in the non snap version and Firefox snap version don't. Seems some door is closed in the snap. Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1849346/comments/21 ** Changed in: firefox Status: Unknown => New -- 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/1849346 Title: [snap] kerberos GSSAPI no longer works after deb->snap transition Status in Mozilla Firefox: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: I configure AuthServerWhitelist as documented: https://www.chromium.org/developers/design-documents/http- authentication and can see my whitelisted domains in chrome://policy/ but websites that used to work with SPNEGO/GSSAPI/kerberos no longer work. I'm guessing the snap needs some sort of permission to use the kerberos ticket cache (or the plumbing to do so doesn't exist...). I can confirm that Chrome has the desired behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1849346/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
Has anyone tried PCManFM or Inkscape on focal? It seems that this update doesn't fix GNOME Shell on focal, but *maybe* that's because Shell is hitting a different bug? If this can be verified to fix PCManFM, Inkscape, or something on focal we can release it and open a new bug for GNOME Shell on Focal. If this *doesn't* fix something on focal, we need to work out why - maybe it needs more changes backported, like bionic did? If FCManFM & Inkscape don't hang on focal *without* this update then I think we can release the bionic update and close the focal task. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Fix Committed Status in libx11 source package in Focal: Fix Committed Status in libx11 source package in Groovy: Won't Fix Bug description: [Impact] There is a race in libx11 causing applications to randomly abort. It's not trivial to reproduce, but there are enough duplicates that this deserves an SRU to bionic & focal. [Fix] Backport a commit from upstream: From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001 From: Frediano Ziglio Date: Wed, 29 Jan 2020 09:06:54 + Subject: [PATCH] Fix poll_for_response race condition In poll_for_response is it possible that event replies are skipped and a more up to date message reply is returned. This will cause next poll_for_event call to fail aborting the program. This was proved using some slow ssh tunnel or using some program to slow down server replies (I used a combination of xtrace and strace). How the race happens: - program enters into poll_for_response; - poll_for_event is called but the server didn't still send the reply; - pending_requests is not NULL because we send a request (see call to append_pending_request in _XSend); - xcb_poll_for_reply64 is called from poll_for_response; - xcb_poll_for_reply64 will read from server, at this point server reply with an event (say sequence N) and the reply to our last request (say sequence N+1); - xcb_poll_for_reply64 returns the reply for the request we asked; - last_request_read is set to N+1 sequence in poll_for_response; - poll_for_response returns the response to the request; - poll_for_event is called (for instance from another poll_for_response); - event with sequence N is retrieved; - the N sequence is widen, however, as the "new" number computed from last_request_read is less than N the number is widened to N + 2^32 (assuming last_request_read is still contained in 32 bit); - poll_for_event enters the nested if statement as req is NULL; - we compare the widen N (which now does not fit into 32 bit) with request (which fits into 32 bit) hitting the throw_thread_fail_assert. To avoid the race condition and to avoid the sequence to go back I check again for new events after getting the response and return this last event if present saving the reply to return it later. To test the race and the fix it's helpful to add a delay (I used a "usleep(5000)") before calling xcb_poll_for_reply64. Original patch written by Frediano Ziglio, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34 Reworked primarily for readability by Peter Hutterer, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53 Signed-off-by: Peter Hutterer bionic needs another commit so that the real fix applies. [Test case] It's a race condition, the SRU sponsor (tjaalton) does not have a test case for this, but the bug subscribers seem to. [Where things could go wrong] In theory there might be a case where a race still happens, but since this has been upstream for a year now with no follow-up commits, it's safe to assume that there are no regressions. -- STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not
[Desktop-packages] [Bug 1933828] Re: NTP servers from DHCP are not propagated to timesyncd
Here is a networkd-dispatcher fix: https://launchpad.net/~hellsworth/+archive/ubuntu/networkd-dispatcher/+build/22316215 And here is a network-manager fix: https://launchpad.net/~hellsworth/+archive/ubuntu/network-manager/+build/22316944 Both should work, so please test the networkd-dispatcher fix first and network-manager if needbe. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1933828 Title: NTP servers from DHCP are not propagated to timesyncd Status in OEM Priority Project: New Status in network-manager package in Ubuntu: New Status in network-manager source package in Focal: New Bug description: Network manager gets NTP servers from DHCP but do not update timesyncd to use it which keeps using ntp.ubuntu.com. This is a problem on private networks which do not have access to public internet. On this type of network the configuration of timesyncd must be updated manually instead of inheriting the conf from the dhcp servers. This can be integrated with a NM dispatcher script such as below: etc/NetworkManager/dispatcher.d/10-update-timesyncd for example: ==8<=8<=8<=8<=8<== #! /usr/bin/bash [ -n "$CONNECTION_UUID" ] || exit INTERFACE=$1 ACTION=$2 case $ACTION in up | dhcp4-change | dhcp6-change) [ -n "$DHCP4_NTP_SERVERS" ] || exit mkdir -p /etc/systemd/timesyncd.conf.d/ cat< /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf [Time] NTP=$DHCP4_NTP_SERVERS RootDistanceMaxSec=15 EOF systemctl restart systemd-timesyncd ;; down) rm -f /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf systemctl restart systemd-timesyncd ;; esac ==8<=8<=8<=8<=8<== ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 14:08:52 2021 InstallationDate: Installed on 2020-05-31 (393 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) RebootRequiredPkgs: linux-image-5.11.0-20-generic linux-base SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933828/+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 1866134] Re: Yaru icons are not shown in Gnome-Software
** Changed in: gnome-software Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1866134 Title: Yaru icons are not shown in Gnome-Software Status in GNOME Software: Fix Released Status in snap-store-desktop: Fix Released Status in gnome-software package in Ubuntu: Triaged Bug description: When an icon theme different from Adwaita is selected, the icons from that theme are not shown in Gnome-Software. This is confusing for user because they now see two different icons for the same application (see the screenshot upstream). It would be great if Gnome-Software would look for the icon in the selected icon theme. Reported upstream here: https://gitlab.gnome.org/GNOME/gnome- software/issues/929 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1866134/+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 1925467] Re: stack-buffer-overflow of text.c in function _import_ansi
** Changed in: libcaca
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcaca in Ubuntu.
https://bugs.launchpad.net/bugs/1925467
Title:
stack-buffer-overflow of text.c in function _import_ansi
Status in libcaca:
Fix Released
Status in libcaca package in Ubuntu:
Triaged
Bug description:
Hello ubuntu security team
issues: https://github.com/cacalabs/libcaca/issues/55
System info：
Ubuntu 20.04 : clang 10.0.0 , gcc 9.3.0
Fedora 33: clang 11.0.0 , gcc 10.2.1
libcaca version e4968ba
Verification steps：
1.Get the source code of libcaca
2.Compile the libcaca.so library
$ cd libcaca
$ ./bootstrap
$ ./configure
$ make
or
$ cd libcaca
$ ./bootstrap
$ ../configure CC="clang -O2 -fno-omit-frame-pointer -g
-fsanitize=address,fuzzer-no-link -fsanitize-coverage=bb" CXX="clang++ -O2
-fno-omit-frame-pointer -g -fsanitize=address,fuzzer-no-link
-fsanitize-coverage=bb"
$ make
3.Create the poc_ansi.cc && build
#include "config.h"
#include "caca.h"
//#include "common-image.h"
#include
#include
#include
#include
#include
#include
using namespace std;
void crash(const uint8_t *Data, size_t Size) {
if(Size<8) return ;
size_t len=0;
caca_canvas_t *cv;
cv = caca_create_canvas(0,0);
caca_create_frame(cv,0);
caca_set_frame(cv,0);
caca_import_canvas_from_memory(cv,Data,Size,"ansi");
caca_free_canvas(cv);
cv=NULL;
}
int main(int args,char* argv[]){
size_t len = 0;
unsigned char buffer[] =
{0x20,0x4a,0x0c,0x0a,0x20,0x0a,0x20,0x0c,0xc,0xc};
len = sizeof(buffer)/sizeof(unsigned char);
printf("%d\n",sizeof(buffer)/sizeof(unsigned char));
crash((const uint8_t*)buffer,len);
return 0;
}
4.compile poc_ansi.cc
clang++ -g poc_ansi.cc -O2 -fno-omit-frame-pointer -fsanitize=address
-I./caca/ -lcaca -L./caca/.libs/ -Wl,-rpath,./caca/.libs/ -o poc_ansi
5.Run poc_ansi
asan info:
=
==3763372==ERROR: AddressSanitizer: stack-buffer-overflow on address
0x7ffda0164bea at pc 0x7f098d82c310 bp 0x7ffda01647b0 sp 0x7ffda01647a8
READ of size 1 at 0x7ffda0164bea thread T0
#0 0x7f098d82c30f in _import_ansi
/home/hh/Downloads/libcaca/caca/codec/text.c:391:38
#1 0x4c6c72 in crash(unsigned char const*, unsigned long)
/home/hh/Downloads/libcaca/poc_bin.cc:21:3
#2 0x4c6c72 in main /home/hh/Downloads/libcaca/poc_bin.cc:34:9
#3 0x7f098d2780b2 in __libc_start_main
/build/glibc-eX1tMB/glibc-2.31/csu/../csu/libc-start.c:308:16
#4 0x41c38d in _start (/home/hh/Downloads/libcaca/poc_mbay+0x41c38d)
Address 0x7ffda0164bea is located in stack of thread T0 at offset 42 in frame
#0 0x4c6b9f in main /home/hh/Downloads/libcaca/poc_bin.cc:28
This frame has 1 object(s):
[32, 42) 'buffer' (line 31) <== Memory access at offset 42 overflows this
variable
HINT: this may be a false positive if your program uses some custom stack
unwind mechanism, swapcontext or vfork
(longjmp and C++ exceptions *are* supported)
SUMMARY: AddressSanitizer: stack-buffer-overflow
/home/hh/Downloads/libcaca/caca/codec/text.c:391:38 in _import_ansi
Shadow bytes around the buggy address:
0x100034024920: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
0x100034024930: f8 f8 f8 f8 f8 f8 f8 f8 f8 f2 f2 f2 f2 f2 f2 f2
0x100034024940: f2 f2 f8 f2 f2 f2 f8 f3 f3 f3 f3 f3 00 00 00 00
0x100034024950: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x100034024960: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x100034024970: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00[02]f3 f3
0x100034024980: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x100034024990: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1000340249a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1000340249b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1000340249c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user:f7
Container overflow: fc
Array cookie:ac
Intra object redzone:bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone:cb
Shadow gap: cc
==3763372==ABORTING
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/libcaca/+bug/1925467/+subscriptions
--
Mailing list:
[Desktop-packages] [Bug 1925468] Re: stack-buffer-overflow of import.c in function _import_bin
** Changed in: libcaca
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcaca in Ubuntu.
https://bugs.launchpad.net/bugs/1925468
Title:
stack-buffer-overflow of import.c in function _import_bin
Status in libcaca:
Fix Released
Status in libcaca package in Ubuntu:
Triaged
Bug description:
Hello ubuntu security team
issues：https://github.com/cacalabs/libcaca/issues/56
System info：
Ubuntu 20.04 : clang 10.0.0 , gcc 9.3.0
Fedora 33: clang 11.0.0 , gcc 10.2.1
libcaca version e4968ba
Verification steps：
1.Get the source code of libcaca
2.Compile the libcaca.so library
$ cd libcaca
$ ./bootstrap
$ ./configure
$ make
or
$ cd libcaca
$ ./bootstrap
$ ../configure CC="clang -O2 -fno-omit-frame-pointer -g
-fsanitize=address,fuzzer-no-link -fsanitize-coverage=bb" CXX="clang++ -O2
-fno-omit-frame-pointer -g -fsanitize=address,fuzzer-no-link
-fsanitize-coverage=bb"
$ make
3.Create the poc_bin.cc && build
#include "config.h"
#include "caca.h"
//#include "common-image.h"
#include
#include
#include
#include
#include
#include
using namespace std;
void crash(const uint8_t *Data, size_t Size) {
if(Size<8) return ;
size_t len=0;
caca_canvas_t *cv;
cv = caca_create_canvas(0,0);
caca_create_frame(cv,0);
caca_set_frame(cv,0);
caca_import_canvas_from_memory(cv,Data,Size,"bin");
caca_free_canvas(cv);
cv=NULL;
}
int main(int args,char* argv[]){
size_t len = 0;
unsigned char buffer[] =
{0x0a,0x20,0x0a,0x0a,0x20,0x20,0x20,0x20,0x20,0x20,0x47,0x47,0x47};
len = sizeof(buffer)/sizeof(unsigned char);
printf("%d\n",sizeof(buffer)/sizeof(unsigned char));
crash((const uint8_t*)buffer,len);
return 0;
}
4.compile poc_bin.cc
clang++ -g poc_bin.cc -O2 -fno-omit-frame-pointer -fsanitize=address
-I./caca/ -lcaca -L./caca/.libs/ -Wl,-rpath,./caca/.libs/ -o poc_bin
5.Run poc_bin
asan info:
=
==3817476==ERROR: AddressSanitizer: stack-buffer-overflow on address
0x7ffe7cd3774d at pc 0x7f8c6314acfd bp 0x7ffe7cd376c0 sp 0x7ffe7cd376b8
READ of size 1 at 0x7ffe7cd3774d thread T0
#0 0x7f8c6314acfc in _import_bin
/home/hh/Downloads/libcaca/caca/codec/import.c:425:33
#1 0x4c6c72 in crash(unsigned char const*, unsigned long)
/home/hh/Downloads/libcaca/poc_bin.cc:21:3
#2 0x4c6c72 in main /home/hh/Downloads/libcaca/poc_bin.cc:34:9
#3 0x7f8c62ba00b2 in __libc_start_main
/build/glibc-eX1tMB/glibc-2.31/csu/../csu/libc-start.c:308:16
#4 0x41c38d in _start (/home/hh/Downloads/libcaca/poc_bin+0x41c38d)
Address 0x7ffe7cd3774d is located in stack of thread T0 at offset 45 in frame
#0 0x4c6b9f in main /home/hh/Downloads/libcaca/poc_bin.cc:28
This frame has 1 object(s):
[32, 45) 'buffer' (line 31) <== Memory access at offset 45 overflows this
variable
HINT: this may be a false positive if your program uses some custom stack
unwind mechanism, swapcontext or vfork
(longjmp and C++ exceptions *are* supported)
SUMMARY: AddressSanitizer: stack-buffer-overflow
/home/hh/Downloads/libcaca/caca/codec/import.c:425:33 in _import_bin
Shadow bytes around the buggy address:
0x10004f99ee90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99eea0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99eeb0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99eec0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99eed0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x10004f99eee0: 00 00 00 00 f1 f1 f1 f1 00[05]f3 f3 00 00 00 00
0x10004f99eef0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99ef00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99ef10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99ef20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99ef30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user:f7
Container overflow: fc
Array cookie:ac
Intra object redzone:bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone:cb
Shadow gap: cc
==3817476==ABORTING
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/libcaca/+bug/1925468/+subscriptions
--
Mailing
[Desktop-packages] [Bug 1947790] [NEW] marisa FTBFS on ppc64el
Public bug reported:
marisa fails to build on ppc64el:
# extconf.rb needs to exist library when configure
cd bindings/ruby; ruby extconf.rb --with-opt-include=../../include \
--with-opt-lib=../../lib/marisa/.libs
checking for -lmarisa... *** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers. Check the mkmf.log file for more details. You may
need configuration options.
Provided configuration options:
--with-opt-dir
--without-opt-dir
--with-opt-include=${opt-dir}/include
--with-opt-lib=${opt-dir}/lib
--with-make-prog
--without-make-prog
--srcdir=.
--curdir
--ruby=/usr/bin/$(RUBY_BASE_NAME)2.7
--with-marisa-dir
--without-marisa-dir
--with-marisa-include
--without-marisa-include=${marisa-dir}/include
--with-marisa-lib
--without-marisa-lib=${marisa-dir}/lib
--with-marisalib
--without-marisalib
/usr/lib/ruby/2.7.0/mkmf.rb:471:in `try_do': The compiler failed to generate an
executable file. (RuntimeError)
You have to install development tools first.
from /usr/lib/ruby/2.7.0/mkmf.rb:564:in `try_link0'
from /usr/lib/ruby/2.7.0/mkmf.rb:582:in `try_link'
from /usr/lib/ruby/2.7.0/mkmf.rb:801:in `try_func'
from /usr/lib/ruby/2.7.0/mkmf.rb:1029:in `block in have_library'
from /usr/lib/ruby/2.7.0/mkmf.rb:971:in `block in checking_for'
from /usr/lib/ruby/2.7.0/mkmf.rb:361:in `block (2 levels) in postpone'
from /usr/lib/ruby/2.7.0/mkmf.rb:331:in `open'
from /usr/lib/ruby/2.7.0/mkmf.rb:361:in `block in postpone'
from /usr/lib/ruby/2.7.0/mkmf.rb:331:in `open'
from /usr/lib/ruby/2.7.0/mkmf.rb:357:in `postpone'
from /usr/lib/ruby/2.7.0/mkmf.rb:970:in `checking_for'
from /usr/lib/ruby/2.7.0/mkmf.rb:1024:in `have_library'
from extconf.rb:3:in `'
The same source builds successfully in impish. A known environment
change is python3.10, but I'm not able to see in the buildlog that the
failure is related to that.
https://launchpadlibrarian.net/564533377/buildlog_ubuntu-jammy-
ppc64el.marisa_0.2.6-3ubuntu2_BUILDING.txt.gz
** Affects: marisa (Ubuntu)
Importance: Undecided
Status: New
** Tags: ftbfs jammy ppc64el update-excuse
** Tags added: ppc64el
--
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/1947790
Title:
marisa FTBFS on ppc64el
Status in marisa package in Ubuntu:
New
Bug description:
marisa fails to build on ppc64el:
# extconf.rb needs to exist library when configure
cd bindings/ruby; ruby extconf.rb --with-opt-include=../../include \
--with-opt-lib=../../lib/marisa/.libs
checking for -lmarisa... *** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers. Check the mkmf.log file for more details. You may
need configuration options.
Provided configuration options:
--with-opt-dir
--without-opt-dir
--with-opt-include=${opt-dir}/include
--with-opt-lib=${opt-dir}/lib
--with-make-prog
--without-make-prog
--srcdir=.
--curdir
--ruby=/usr/bin/$(RUBY_BASE_NAME)2.7
--with-marisa-dir
--without-marisa-dir
--with-marisa-include
--without-marisa-include=${marisa-dir}/include
--with-marisa-lib
--without-marisa-lib=${marisa-dir}/lib
--with-marisalib
--without-marisalib
/usr/lib/ruby/2.7.0/mkmf.rb:471:in `try_do': The compiler failed to generate
an executable file. (RuntimeError)
You have to install development tools first.
from /usr/lib/ruby/2.7.0/mkmf.rb:564:in `try_link0'
from /usr/lib/ruby/2.7.0/mkmf.rb:582:in `try_link'
from /usr/lib/ruby/2.7.0/mkmf.rb:801:in `try_func'
from /usr/lib/ruby/2.7.0/mkmf.rb:1029:in `block in have_library'
from /usr/lib/ruby/2.7.0/mkmf.rb:971:in `block in checking_for'
from /usr/lib/ruby/2.7.0/mkmf.rb:361:in `block (2 levels) in postpone'
from /usr/lib/ruby/2.7.0/mkmf.rb:331:in `open'
from /usr/lib/ruby/2.7.0/mkmf.rb:361:in `block in postpone'
from /usr/lib/ruby/2.7.0/mkmf.rb:331:in `open'
from /usr/lib/ruby/2.7.0/mkmf.rb:357:in `postpone'
from /usr/lib/ruby/2.7.0/mkmf.rb:970:in `checking_for'
from /usr/lib/ruby/2.7.0/mkmf.rb:1024:in `have_library'
from extconf.rb:3:in `'
The same source builds successfully in impish. A known environment
change is python3.10, but I'm not able to see in the buildlog that the
failure is related to that.
https://launchpadlibrarian.net/564533377/buildlog_ubuntu-jammy-
ppc64el.marisa_0.2.6-3ubuntu2_BUILDING.txt.gz
To manage notifications about this bug go to:
Re: [Desktop-packages] [Bug 1947194] Re: When using Wayland in 21.04, the display often never wakes up after lock
I got a case of failing to wake up with GDK_SYNCHRONIZE turned on, and I've attached the output from journalctl. However, there's no new crash file. Am turning off wayland for now. On 2021-10-19 2:13 a.m., Daniel van Vugt wrote: > Per the instructions in comment #5: > > "If step 1 failed then look at https://errors.ubuntu.com/user/ID where > ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. > Do you find any links to recent problems on that page? If so then please > send the links to us." > ** Attachment added: "prevboot-sync.txt" https://bugs.launchpad.net/bugs/1947194/+attachment/5534419/+files/prevboot-sync.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1947194 Title: When using Wayland in 21.04, the display often never wakes up after lock Status in mutter package in Ubuntu: Incomplete Bug description: When using Wayland in 21.04, the display often never wakes up after lock up. Also, on boot up, desktop icons and most favorites on dash are not displayed, even though desktop icons are enabled. I can get them to show up only by re-enabling desktop icons. The workaround now is to disable Wayland, and the original xorg server works fine. The display driver is: 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) The monitor is an HP 22cwa running of of a displayport interface. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 14 14:32:26 2021 DistUpgraded: 2021-07-28 16:05:54,589 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:047e] InstallationDate: Installed on 2018-12-04 (1044 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. OptiPlex 990 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-07-28 (77 days ago) dmi.bios.date: 11/24/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd11/24/2011:br4.6:svnDellInc.:pnOptiPlex990:pvr01:sku:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1947194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1947194] Re: When using Wayland in 21.04, the display often never wakes up after lock
On second thought, I re-enabled wayland and turned on GDK_SYNCHRONIZE and I'll give it a day or so to see if the bug crops up again. There's definitely something wrong about gdm3 calling wayland because after boot, icons that should appear on the dash only do so AFTER you run a program, like a terminal via ctrl-alt-T. On 2021-10-19 2:13 a.m., Daniel van Vugt wrote: > Per the instructions in comment #5: > > "If step 1 failed then look at https://errors.ubuntu.com/user/ID where > ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. > Do you find any links to recent problems on that page? If so then please > send the links to us." > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1947194 Title: When using Wayland in 21.04, the display often never wakes up after lock Status in mutter package in Ubuntu: Incomplete Bug description: When using Wayland in 21.04, the display often never wakes up after lock up. Also, on boot up, desktop icons and most favorites on dash are not displayed, even though desktop icons are enabled. I can get them to show up only by re-enabling desktop icons. The workaround now is to disable Wayland, and the original xorg server works fine. The display driver is: 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) The monitor is an HP 22cwa running of of a displayport interface. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 14 14:32:26 2021 DistUpgraded: 2021-07-28 16:05:54,589 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:047e] InstallationDate: Installed on 2018-12-04 (1044 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. OptiPlex 990 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-07-28 (77 days ago) dmi.bios.date: 11/24/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd11/24/2011:br4.6:svnDellInc.:pnOptiPlex990:pvr01:sku:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1947194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1947194] Re: When using Wayland in 21.04, the display often never wakes up after lock
After disabling the GDK_SYNCHRONIZE statement, I finally was able to get the bug to reappear. I've attached a new prevboot file (after a power button shot down and reboot). I also used apport-cli to upload the crash report. It's url is https://errors.ubuntu.com/oops/0005b74e-3103-11ec-b60f-fa163e6cac46 I'm going to disable wayland again as the system is a little too flaky with it enabled. On 2021-10-19 2:13 a.m., Daniel van Vugt wrote: > Per the instructions in comment #5: > > "If step 1 failed then look at https://errors.ubuntu.com/user/ID where > ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. > Do you find any links to recent problems on that page? If so then please > send the links to us." > ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/bugs/1947194/+attachment/5534358/+files/prevboot.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1947194 Title: When using Wayland in 21.04, the display often never wakes up after lock Status in mutter package in Ubuntu: Incomplete Bug description: When using Wayland in 21.04, the display often never wakes up after lock up. Also, on boot up, desktop icons and most favorites on dash are not displayed, even though desktop icons are enabled. I can get them to show up only by re-enabling desktop icons. The workaround now is to disable Wayland, and the original xorg server works fine. The display driver is: 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) The monitor is an HP 22cwa running of of a displayport interface. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 14 14:32:26 2021 DistUpgraded: 2021-07-28 16:05:54,589 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:047e] InstallationDate: Installed on 2018-12-04 (1044 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. OptiPlex 990 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-07-28 (77 days ago) dmi.bios.date: 11/24/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd11/24/2011:br4.6:svnDellInc.:pnOptiPlex990:pvr01:sku:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1947194/+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 1927689] Re: Paper height HP OfficeJet 150
** Changed in: ubuntu Status: Invalid => New ** Package changed: ubuntu => hplip (Ubuntu) ** Tags added: hirsute -- 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/1927689 Title: Paper height HP OfficeJet 150 Status in HPLIP: New Status in sane-backends: Unknown Status in hplip package in Ubuntu: New Bug description: The height of the paper size is limited to letter size: > scanimage -- help -d hpaio:/usb/Officejet_150_Mobile_L511?serial=MY2A9720DR ... -y 0..277.707mm [277.707] Height of scan-area. ... When I try to scan a A4 document, the bottom of the page is "cut off". But as there is the limit, it is also not possible to set A4 as size: > scanimage -x 210 -y 296 -d hpaio:/usb/Officejet_150_Mobile_L511?serial=MY2A9720DR scanimage: setting of option --br-y failed (Invalid argument) I would like to look for some more details, where the limitation comes from. Especially, as the OfficeJet 150 has and ADF, which should not have any trouble scanning pages longer than letter size. Where is the paper size limitation set? Where are the properties for the device (hpaio:/usb/Officejet_150_Mobile_L511?serial=MY2A9720DR) stored? Thanks Ben To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1927689/+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 1947670] Re: /etc/profile.d/im-config_wayland.sh prevents sourcing /etc/profile
Correction: Uninstalling im-config may not be so easy on an Ubuntu system. So maybe you want to simply edit the script. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1947670 Title: /etc/profile.d/im-config_wayland.sh prevents sourcing /etc/profile Status in im-config package in Ubuntu: In Progress Bug description: We upgraded a build server from Ubuntu 18.04 to 20.04. The build server had some scripts in /etc/profile.d/ that set up the required build environment. The builds would source `. /etc/profile` in the beginning. After the upgrade, the script /etc/profile.d/im-config_wayland.sh line ``` test "$XDG_SESSION_TYPE" = 'wayland' || return ``` evaluates with `test tty = wayland` returning the build script early. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1947670/+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 1927689] [NEW] Paper height HP OfficeJet 150
You have been subscribed to a public bug: The height of the paper size is limited to letter size: > scanimage -- help -d hpaio:/usb/Officejet_150_Mobile_L511?serial=MY2A9720DR ... -y 0..277.707mm [277.707] Height of scan-area. ... When I try to scan a A4 document, the bottom of the page is "cut off". But as there is the limit, it is also not possible to set A4 as size: > scanimage -x 210 -y 296 -d > hpaio:/usb/Officejet_150_Mobile_L511?serial=MY2A9720DR scanimage: setting of option --br-y failed (Invalid argument) I would like to look for some more details, where the limitation comes from. Especially, as the OfficeJet 150 has and ADF, which should not have any trouble scanning pages longer than letter size. Where is the paper size limitation set? Where are the properties for the device (hpaio:/usb/Officejet_150_Mobile_L511?serial=MY2A9720DR) stored? Thanks Ben ** Affects: hplip Importance: Undecided Status: New ** Affects: sane-backends Importance: Unknown Status: Unknown ** Affects: hplip (Ubuntu) Importance: Undecided Status: New -- Paper height HP OfficeJet 150 https://bugs.launchpad.net/bugs/1927689 You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip 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 1947670] Re: /etc/profile.d/im-config_wayland.sh prevents sourcing /etc/profile
Thanks for explaining. This was news to me, but I can confirm that those test() commands are problematic if you source with the -e option set. Usually /etc/profile is sourced by some display manager without the -e option, which may explain that nobody has reported this previously. It should be fixed, and I have pushed this commit: https://salsa.debian.org/input-method-team/im-config/-/commit/776845bd Note that the change will be effective only in Ubuntu 22.04. In the meantime, and if you want to use the -e option, the easiest way is probably to uninstall im-config: sudo apt purge im-config (I assume you don't need it for the described purpose.) ** Changed in: im-config (Ubuntu) Importance: Undecided => Low ** Changed in: im-config (Ubuntu) Status: Incomplete => In Progress ** Changed in: im-config (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1947670 Title: /etc/profile.d/im-config_wayland.sh prevents sourcing /etc/profile Status in im-config package in Ubuntu: In Progress Bug description: We upgraded a build server from Ubuntu 18.04 to 20.04. The build server had some scripts in /etc/profile.d/ that set up the required build environment. The builds would source `. /etc/profile` in the beginning. After the upgrade, the script /etc/profile.d/im-config_wayland.sh line ``` test "$XDG_SESSION_TYPE" = 'wayland' || return ``` evaluates with `test tty = wayland` returning the build script early. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1947670/+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 1930188] Re: Acer Aspire 5 sound driver issues
This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu0.11 --- alsa-ucm-conf (1.2.2-1ubuntu0.11) focal; urgency=medium * d/p/0033-HDA-Intel-add-Boost-volume-control-for-Headset-Mic.patch Add Mic Boost in the HDA Intel ucm, after this change, when users adjust input volume, the Mic Boost could be adjusted as well as Capture Volume. (LP: #1930188) -- Hui Wang Tue, 14 Sep 2021 15:11:12 +0800 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Committed Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1.
[Desktop-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu3.12 --- pulseaudio (1:13.99.1-1ubuntu3.12) focal; urgency=medium * d/p/0001-alsa-sink-source-set-volume-to-hw-immediately-if-ucm.patch Fix the output volume issue for machines with sof audio driver, if a machine uses sof audio driver, the headphone and speaker will share the output volume from UI, this patch will fix this issue, after applying this patch, the speaker and headphone will have independent volume. (LP: #1930188) -- Hui Wang Mon, 13 Sep 2021 12:11:14 +0800 ** Changed in: pulseaudio (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Committed Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if
Re: [Desktop-packages] [Bug 1934194] Re: package chromium-browser 91.0.4472.101-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned err
Here is more .. cjm@Jetson-AI-001:~$ journalctl -xe Oct 19 12:51:39 Jetson-AI-001 kernel: pcieport :00:01.0:[ 0] Receiver Error (First) Oct 19 12:51:42 Jetson-AI-001 rtkit-daemon[6509]: Supervising 0 threads of 0 processes of 0 users. Oct 19 12:51:42 Jetson-AI-001 rtkit-daemon[6509]: Supervising 0 threads of 0 processes of 0 users. Oct 19 12:51:42 Jetson-AI-001 rtkit-daemon[6509]: Supervising 0 threads of 0 processes of 0 users. Oct 19 12:51:42 Jetson-AI-001 rtkit-daemon[6509]: Supervising 0 threads of 0 processes of 0 users. Oct 19 12:51:42 Jetson-AI-001 rtkit-daemon[6509]: Failed to make ourselves RT: Operation not permitted Oct 19 12:52:41 Jetson-AI-001 systemd[1]: Starting Daily apt download activities... -- Subject: A start job for unit apt-daily.service has begun execution -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit apt-daily.service has begun execution. -- -- The job identifier is 2259. Oct 19 12:52:43 Jetson-AI-001 systemd[1]: apt-daily.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The unit apt-daily.service has successfully entered the 'dead' state. Oct 19 12:52:43 Jetson-AI-001 systemd[1]: Finished Daily apt download activities. -- Subject: A start job for unit apt-daily.service has finished successfully -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit apt-daily.service has finished successfully. -- -- The job identifier is 2259. Oct 19 12:59:32 Jetson-AI-001 kernel: pcieport :00:01.0: AER: Corrected error received: id=0010 Oct 19 12:59:32 Jetson-AI-001 kernel: pcieport :00:01.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0008(Recei> Oct 19 12:59:32 Jetson-AI-001 kernel: pcieport :00:01.0: device [10de:0fae] error status/mask=0001/2000 Oct 19 12:59:32 Jetson-AI-001 kernel: pcieport :00:01.0:[ 0] Receiver Error (First) Oct 19 12:59:54 Jetson-AI-001 rtkit-daemon[6509]: Supervising 0 threads of 0 processes of 0 users. Oct 19 12:59:54 Jetson-AI-001 rtkit-daemon[6509]: Supervising 0 threads of 0 processes of 0 users. lines 2383-2416/2416 (END) Thanks for your help, Carter (615) 337-2472 On Tue, Oct 19, 2021 at 11:01 AM Olivier Tilloy <1934...@bugs.launchpad.net> wrote: > Can you try running the following command in a terminal, and let us know > how this goes? > > sudo snap install chromium > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1934194 > > Title: > package chromium-browser 91.0.4472.101-0ubuntu0.18.04.1 failed to > install/upgrade: new chromium-browser package pre-installation script > subprocess returned error exit status 1 > > Status in chromium-browser package in Ubuntu: > Incomplete > > Bug description: > Just installed and received system unstable messages. > > ProblemType: Package > DistroRelease: Ubuntu 20.04 > Package: chromium-browser 91.0.4472.101-0ubuntu0.18.04.1 > ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 > Uname: Linux 5.4.0-77-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > CasperMD5CheckResult: skip > DRM.card0-DVI-I-1: >enabled: disabled >dpms: On >status: disconnected >edid-base64: >modes: > DRM.card0-HDMI-A-1: >enabled: enabled >dpms: On >status: connected >edid-base64: > AP///wBBDAhXAQEBAQAXAQOAZjl4CvntplJQnyQKR0qhCACBwIGAswCpwAEBAQEBAQEBAjqAGHE4LUBYLEUA+jwyAAAeqRoAoFAAFjAwIDcA+jwyAAAa/AAzMlBGTDU3MDgvRjcK/QAXTA9RDwAKICAgICAgAV0CAx9xSQECAwQFByCQBiYJBwcVB1BmAwwAIACA4gAPAjqAGHE4LUBYLEUA+jwyAAAeAR2AGHEcFiBYLCUA+jwyAACeAR0AclHQHiBuKFUA+jwyAAAejArQiiDgLRAQPpYA+jwyAAAYjAqgFFHwFgAmfEMA+jwyAACYzw== >modes: 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080i > 1920x1080 1920x1080 1680x1050 1600x900 1280x1024 1280x768 1280x720 1280x720 > 1280x720 1024x768 1440x480i 800x600 720x480 720x480 720x480 720x480 720x480 > 720x480i 720x480i 720x480i 720x480i 640x480 640x480 640x480 720x400 > Date: Wed Jun 30 16:37:28 2021 > Desktop-Session: >'None' >'None' >'None' > Env: >'None' >'None' > ErrorMessage: new chromium-browser package pre-installation script > subprocess returned error exit status 1 > InstallationDate: Installed on 2020-09-01 (302 days ago) > InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release amd64 > (20190304.5) > InstalledPlugins: > > Load-Avg-1min: 6.32 > Load-Processes-Running-Percent: 0.2% > MachineType: Hewlett-Packard s5-1070t > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-77-generic > root=UUID=a8b4761a-7e53-4c94-9a12-3ace3096a126 ro quiet splash vt.handoff=7 > Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, > 3.8.2-0ubuntu2 > PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, > 2.7.17-4 > SourcePackage:
Re: [Desktop-packages] [Bug 1934194] Re: package chromium-browser 91.0.4472.101-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned err
Yes Sir, I gave it a try. Below is a screenshot. cjm@Jetson-AI-001:~$ sudo snap install chromium error: cannot perform the following tasks: - Mount snap "chromium" (1791) (systemctl command [start snap-chromium-1791.mount] failed with exit status 1: Job failed. See "journalctl -xe" for details. ) Thanks, Carter (615) 337-2472 On Tue, Oct 19, 2021 at 11:01 AM Olivier Tilloy <1934...@bugs.launchpad.net> wrote: > Can you try running the following command in a terminal, and let us know > how this goes? > > sudo snap install chromium > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1934194 > > Title: > package chromium-browser 91.0.4472.101-0ubuntu0.18.04.1 failed to > install/upgrade: new chromium-browser package pre-installation script > subprocess returned error exit status 1 > > Status in chromium-browser package in Ubuntu: > Incomplete > > Bug description: > Just installed and received system unstable messages. > > ProblemType: Package > DistroRelease: Ubuntu 20.04 > Package: chromium-browser 91.0.4472.101-0ubuntu0.18.04.1 > ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 > Uname: Linux 5.4.0-77-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > CasperMD5CheckResult: skip > DRM.card0-DVI-I-1: >enabled: disabled >dpms: On >status: disconnected >edid-base64: >modes: > DRM.card0-HDMI-A-1: >enabled: enabled >dpms: On >status: connected >edid-base64: > AP///wBBDAhXAQEBAQAXAQOAZjl4CvntplJQnyQKR0qhCACBwIGAswCpwAEBAQEBAQEBAjqAGHE4LUBYLEUA+jwyAAAeqRoAoFAAFjAwIDcA+jwyAAAa/AAzMlBGTDU3MDgvRjcK/QAXTA9RDwAKICAgICAgAV0CAx9xSQECAwQFByCQBiYJBwcVB1BmAwwAIACA4gAPAjqAGHE4LUBYLEUA+jwyAAAeAR2AGHEcFiBYLCUA+jwyAACeAR0AclHQHiBuKFUA+jwyAAAejArQiiDgLRAQPpYA+jwyAAAYjAqgFFHwFgAmfEMA+jwyAACYzw== >modes: 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080i > 1920x1080 1920x1080 1680x1050 1600x900 1280x1024 1280x768 1280x720 1280x720 > 1280x720 1024x768 1440x480i 800x600 720x480 720x480 720x480 720x480 720x480 > 720x480i 720x480i 720x480i 720x480i 640x480 640x480 640x480 720x400 > Date: Wed Jun 30 16:37:28 2021 > Desktop-Session: >'None' >'None' >'None' > Env: >'None' >'None' > ErrorMessage: new chromium-browser package pre-installation script > subprocess returned error exit status 1 > InstallationDate: Installed on 2020-09-01 (302 days ago) > InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release amd64 > (20190304.5) > InstalledPlugins: > > Load-Avg-1min: 6.32 > Load-Processes-Running-Percent: 0.2% > MachineType: Hewlett-Packard s5-1070t > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-77-generic > root=UUID=a8b4761a-7e53-4c94-9a12-3ace3096a126 ro quiet splash vt.handoff=7 > Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, > 3.8.2-0ubuntu2 > PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, > 2.7.17-4 > SourcePackage: chromium-browser > Title: package chromium-browser 91.0.4472.101-0ubuntu0.18.04.1 failed to > install/upgrade: new chromium-browser package pre-installation script > subprocess returned error exit status 1 > UpgradeStatus: Upgraded to focal on 2021-06-30 (0 days ago) > dmi.bios.date: 10/05/2011 > dmi.bios.vendor: AMI > dmi.bios.version: 7.16 > dmi.board.name: 2AC2 > dmi.board.vendor: PEGATRON CORPORATION > dmi.board.version: 1.02A > dmi.chassis.asset.tag: 2MD1450H90 > dmi.chassis.type: 3 > dmi.chassis.vendor: Hewlett-Packard > dmi.modalias: > dmi:bvnAMI:bvr7.16:bd10/05/2011:svnHewlett-Packard:pns5-1070t:pvr1.02A:rvnPEGATRONCORPORATION:rn2AC2:rvr1.02A:cvnHewlett-Packard:ct3:cvr: > dmi.product.family: 103C_53316J G=D > dmi.product.name: s5-1070t > dmi.product.sku: LP019AV#ABA > dmi.product.version: 1.02A > dmi.sys.vendor: Hewlett-Packard > modified.conffile..etc.default.chromium-browser: [deleted] > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1934194/+subscriptions > > -- 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/1934194 Title: package chromium-browser 91.0.4472.101-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: Incomplete Bug description: Just installed and received system unstable messages. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 91.0.4472.101-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DRM.card0-DVI-I-1: enabled: disabled dpms:
[Desktop-packages] [Bug 1947769] [NEW] package libgdk-pixbuf-2.0-0:amd64 2.42.6+dfsg-1build2 failed to install/upgrade: triggers looping, abandoned
Public bug reported: After updating to 20.10 this error started to show every 5 min ProblemType: Package DistroRelease: Ubuntu 21.10 Package: libgdk-pixbuf-2.0-0:amd64 2.42.6+dfsg-1build2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Oct 19 17:04:11 2021 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2021-07-21 (90 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: /usr/bin/python3.9, Python 3.9.7, python-is-python3, 3.9.2-1 RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf-2.0-0:amd64 2.42.6+dfsg-1build2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to impish on 2021-10-19 (0 days ago) ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package impish need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1947769 Title: package libgdk-pixbuf-2.0-0:amd64 2.42.6+dfsg-1build2 failed to install/upgrade: triggers looping, abandoned Status in gdk-pixbuf package in Ubuntu: New Bug description: After updating to 20.10 this error started to show every 5 min ProblemType: Package DistroRelease: Ubuntu 21.10 Package: libgdk-pixbuf-2.0-0:amd64 2.42.6+dfsg-1build2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Oct 19 17:04:11 2021 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2021-07-21 (90 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: /usr/bin/python3.9, Python 3.9.7, python-is-python3, 3.9.2-1 RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf-2.0-0:amd64 2.42.6+dfsg-1build2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to impish on 2021-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1947769/+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 1922839] Re: Opening new tab in gnome-terminal launched from nautilus loses most environment variables
This bug was fixed in the package gnome-terminal - 3.38.1-1ubuntu1.1 --- gnome-terminal (3.38.1-1ubuntu1.1) hirsute; urgency=medium * Fix environment variables on opening new tab via the "Open in Terminal" right click menu in Nautilus. (LP: #1922839) - d/p/screen-Use-clean-env-when-creating-new-tab.patch -- Matthew Ruffell Tue, 13 Apr 2021 13:44:53 +1200 ** Changed in: gnome-terminal (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1922839 Title: Opening new tab in gnome-terminal launched from nautilus loses most environment variables Status in GNOME Terminal: Unknown Status in gnome-terminal package in Ubuntu: Fix Released Status in gnome-terminal source package in Hirsute: Fix Released Bug description: [Impact] If you launch gnome-terminal by right clicking a directory in Nautilus, selecting "Open in Terminal", you get a fully functional terminal window. If you then press the new tab button, or ctrl-shift-t to open a new terminal tab, you will find that most environment variables have become unset, and you see the text: To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. Comparing printenv between: Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/ Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/ Most commands won't run in the new terminal tab, due to $HOME and $USER not being set. Note, if you launch gnome-terminal from gnome-shell or the dock, and create a new tab, everything works perfectly. Is something wrong with the Nautilus option for "Open in Terminal"? [Testcase] 1. Launch Nautilus to home directory 2. Right click > "Open in Terminal" 3. Run "printenv" to see full list of env variables 4. Click new tab button, or ctrl-shift-t 5. Run "printenv" see the lack of env variables I have a test package available in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1922839-test The build in the ppa has 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac reverted. If you install this package, environment variables will be set correctly. [Where problems could occur] I think there is some risk with re-instating a commit which has been reverted, and users could run into similar issues as found in the upstream bug. We do have some supporting evidence that the commit isn't too harmful, since it is applied to Groovy currently, things work as intended there, and users haven't complained about the issues in the upstream bug applying to Groovy. If a regression were to occur, then launching a new gnome-terminal or opening a new tab could land the user with a terminal with little to no environment variables set. A workaround will be to launch gnome- terminal from gnome-shell overview. [Other info] Focal and Groovy have the following commit applied: commit fd5ac772154426e2da5afd633b336414bca33be9 Author: Christian Persch Date: Mon Mar 23 09:57:56 2020 +0100 Subject: screen: Use clean env when creating new tab Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/fd5ac772154426e2da5afd633b336414bca33be9 This was then reverted in 3.38.1 due to the upstream bug: https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253 The reverted commit is: commit 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac Author: Christian Persch Date: Thu Sep 17 17:10:47 2020 +0200 Subject: Revert "screen: Use clean env when creating new tab" Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac This revert seems to have broken Hirsute. If we revert the revert, that is, apply the commit again, things work as intended. To fix this, we need to re-apply fd5ac772154426e2da5afd633b336414bca33be9. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1922839/+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 1922839] Update Released
The verification of the Stable Release Update for gnome-terminal 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 gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1922839 Title: Opening new tab in gnome-terminal launched from nautilus loses most environment variables Status in GNOME Terminal: Unknown Status in gnome-terminal package in Ubuntu: Fix Released Status in gnome-terminal source package in Hirsute: Fix Released Bug description: [Impact] If you launch gnome-terminal by right clicking a directory in Nautilus, selecting "Open in Terminal", you get a fully functional terminal window. If you then press the new tab button, or ctrl-shift-t to open a new terminal tab, you will find that most environment variables have become unset, and you see the text: To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. Comparing printenv between: Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/ Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/ Most commands won't run in the new terminal tab, due to $HOME and $USER not being set. Note, if you launch gnome-terminal from gnome-shell or the dock, and create a new tab, everything works perfectly. Is something wrong with the Nautilus option for "Open in Terminal"? [Testcase] 1. Launch Nautilus to home directory 2. Right click > "Open in Terminal" 3. Run "printenv" to see full list of env variables 4. Click new tab button, or ctrl-shift-t 5. Run "printenv" see the lack of env variables I have a test package available in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1922839-test The build in the ppa has 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac reverted. If you install this package, environment variables will be set correctly. [Where problems could occur] I think there is some risk with re-instating a commit which has been reverted, and users could run into similar issues as found in the upstream bug. We do have some supporting evidence that the commit isn't too harmful, since it is applied to Groovy currently, things work as intended there, and users haven't complained about the issues in the upstream bug applying to Groovy. If a regression were to occur, then launching a new gnome-terminal or opening a new tab could land the user with a terminal with little to no environment variables set. A workaround will be to launch gnome- terminal from gnome-shell overview. [Other info] Focal and Groovy have the following commit applied: commit fd5ac772154426e2da5afd633b336414bca33be9 Author: Christian Persch Date: Mon Mar 23 09:57:56 2020 +0100 Subject: screen: Use clean env when creating new tab Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/fd5ac772154426e2da5afd633b336414bca33be9 This was then reverted in 3.38.1 due to the upstream bug: https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253 The reverted commit is: commit 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac Author: Christian Persch Date: Thu Sep 17 17:10:47 2020 +0200 Subject: Revert "screen: Use clean env when creating new tab" Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac This revert seems to have broken Hirsute. If we revert the revert, that is, apply the commit again, things work as intended. To fix this, we need to re-apply fd5ac772154426e2da5afd633b336414bca33be9. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1922839/+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 1930188] Re: Acer Aspire 5 sound driver issues
This bug was fixed in the package alsa-ucm-conf - 1.2.4-2ubuntu1.4 --- alsa-ucm-conf (1.2.4-2ubuntu1.4) hirsute; urgency=medium * d/p/0007-HDA-Intel-add-Boost-volume-control-for-Headset-Mic.patch Add Mic Boost in the HDA Intel ucm, after this change, when users adjust input volume, the Mic Boost could be adjusted as well as Capture Volume. (LP: #1930188) -- Hui Wang Tue, 14 Sep 2021 11:08:28 +0800 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Committed Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1.
[Desktop-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
This bug was fixed in the package pulseaudio - 1:14.2-1ubuntu1.2 --- pulseaudio (1:14.2-1ubuntu1.2) hirsute; urgency=medium * d/p/0001-alsa-sink-source-set-volume-to-hw-immediately-if-ucm.patch Fix the output volume issue for machines with sof audio driver, if a machine uses sof audio driver, the headphone and speaker will share the output volume from UI, this patch will fix this issue, after applying this patch, the speaker and headphone will have independent volume. (LP: #1930188) -- Hui Wang Mon, 13 Sep 2021 11:28:16 +0800 ** Changed in: pulseaudio (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Committed Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if
[Desktop-packages] [Bug 1930188] Update Released
The verification of the Stable Release Update for pulseaudio 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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Committed Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what
[Desktop-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
Hello Bijay, or anyone else affected, Accepted alsa-ucm-conf into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm- conf/1.2.4-2ubuntu5 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- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Committed Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Impish: Fix Committed Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU
[Desktop-packages] [Bug 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file des
@Nikola: If that issue happened also in 21.04, it's not the same issue as the one dealt with in this bug report. The latter is about a regression due to an upgrade of vte2.91. So you may want to submit a new bug report (with more details, exact error messages, etc.). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1946499 Title: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not installed Status in Ubuntu MATE: Invalid Status in gdebi package in Ubuntu: Fix Released Status in vte2.91 package in Ubuntu: Confirmed Status in gdebi source package in Impish: Triaged Bug description: Steps to reproduce: 1. Install Ubuntu MATE 21.10 2. Open Firefox, navigate to discord.com 3. Download deb-file. At time of writing from the https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link 4. Open Caja in ~/Downloads folder and use GDebi to install the discord-0.0.16.deb file 5. In the GDebi window click Install button Expected results: * Gdebi quietly install discord package, there are no error messages in its terminal Actual results: * Gdebi terminal shows the error in the last line ``` Selecting previously unselected package gconf2-common. (Reading database ... 457178 files and directories currently installed.) Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ... Unpacking gconf2-common (3.2.6-7ubuntu2) ... Selecting previously unselected package libgconf-2-4:amd64. Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ... Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service-backend. Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service-backend (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service. Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service (3.2.6-7ubuntu2) ... Selecting previously unselected package libappindicator1. Preparing to unpack .../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ... Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Selecting previously unselected package libunwind-13:amd64. Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ... Unpacking libunwind-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++abi1-13:amd64. Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1-13:amd64. Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1:amd64. Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ... Unpacking libc++1:amd64 (1:13.0-53~exp1) ... Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Setting up gconf2-common (3.2.6-7ubuntu2) ... Creating config file /etc/gconf/2/path with new version Setting up libunwind-13:amd64 (1:13.0.0-2) ... Setting up libc++abi1-13:amd64 (1:13.0.0-2) ... Setting up libc++1-13:amd64 (1:13.0.0-2) ... Setting up libc++1:amd64 (1:13.0-53~exp1) ... Setting up gconf-service (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... Processing triggers for sgml-base (1.30) ... Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Setting up gconf-service-backend (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... dpkg: error: unable to read filedescriptor flags for : Bad file descriptor ``` and as the result Discord package is not installed . ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdebi 0.9.5.7+nmu5ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Oct 8 18:17:36 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1946499/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net
[Desktop-packages] [Bug 1946143] Please test proposed package
Hello Jerry, or anyone else affected, Accepted libqmi into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libqmi/1.28.6-1~21.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- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. 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: libqmi (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/1946143 Title: Apply upstream patches to display 5G NSA status Status in OEM Priority Project: In Progress Status in libqmi package in Ubuntu: Fix Committed Status in libqmi source package in Focal: Fix Committed Status in libqmi source package in Hirsute: Fix Committed Status in libqmi source package in Impish: Fix Committed Bug description: [Impact] The 5G NSA status can not be displayed in the libqmi version 1.28.6-1. (LP#1937012) The 5G NSA status is supported in the libqmi version 1.30.2. The requested upstream patches are listed as below: * 5G NSA status patches https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/29905223c5ae6e5e4ef9246dd9dd4d01b2819d9a * qmicli,nas: flag as 'n/a' the 5G NSA signal quality if not connected https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/b05df7b658f9cfb4c5e74a3e07913de689914a8f [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Verify if the field “5G NSA Available: ” can be displayed via executing: $ sudo qmicli --device=/dev/wwan0p2MBIM --device-open-proxy --nas-get-system-info ... 5G NSA Available: 'no' ... [Where problems could occur] The requested upstream patches are for displaying the status information of 5G NSA network. This should not affect existing generic functions. [Other Info] The latest version of libqmi suit can display the 5G NSA status. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946143/+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 1946143] Please test proposed package
Hello Jerry, or anyone else affected, Accepted libqmi into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libqmi/1.28.6-1~20.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- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/1946143 Title: Apply upstream patches to display 5G NSA status Status in OEM Priority Project: In Progress Status in libqmi package in Ubuntu: Fix Committed Status in libqmi source package in Focal: Fix Committed Status in libqmi source package in Hirsute: Fix Committed Status in libqmi source package in Impish: Fix Committed Bug description: [Impact] The 5G NSA status can not be displayed in the libqmi version 1.28.6-1. (LP#1937012) The 5G NSA status is supported in the libqmi version 1.30.2. The requested upstream patches are listed as below: * 5G NSA status patches https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/29905223c5ae6e5e4ef9246dd9dd4d01b2819d9a * qmicli,nas: flag as 'n/a' the 5G NSA signal quality if not connected https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/b05df7b658f9cfb4c5e74a3e07913de689914a8f [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Verify if the field “5G NSA Available: ” can be displayed via executing: $ sudo qmicli --device=/dev/wwan0p2MBIM --device-open-proxy --nas-get-system-info ... 5G NSA Available: 'no' ... [Where problems could occur] The requested upstream patches are for displaying the status information of 5G NSA network. This should not affect existing generic functions. [Other Info] The latest version of libqmi suit can display the 5G NSA status. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946143/+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 1946143] Re: Apply upstream patches to display 5G NSA status
Hello Jerry, or anyone else affected, Accepted libqmi into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libqmi/1.28.6-2ubuntu1 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- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. 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: libqmi (Ubuntu Impish) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-impish ** Changed in: libqmi (Ubuntu Hirsute) Status: New => Fix Committed ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/1946143 Title: Apply upstream patches to display 5G NSA status Status in OEM Priority Project: In Progress Status in libqmi package in Ubuntu: Fix Committed Status in libqmi source package in Focal: Fix Committed Status in libqmi source package in Hirsute: Fix Committed Status in libqmi source package in Impish: Fix Committed Bug description: [Impact] The 5G NSA status can not be displayed in the libqmi version 1.28.6-1. (LP#1937012) The 5G NSA status is supported in the libqmi version 1.30.2. The requested upstream patches are listed as below: * 5G NSA status patches https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/29905223c5ae6e5e4ef9246dd9dd4d01b2819d9a * qmicli,nas: flag as 'n/a' the 5G NSA signal quality if not connected https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/b05df7b658f9cfb4c5e74a3e07913de689914a8f [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Verify if the field “5G NSA Available: ” can be displayed via executing: $ sudo qmicli --device=/dev/wwan0p2MBIM --device-open-proxy --nas-get-system-info ... 5G NSA Available: 'no' ... [Where problems could occur] The requested upstream patches are for displaying the status information of 5G NSA network. This should not affect existing generic functions. [Other Info] The latest version of libqmi suit can display the 5G NSA status. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946143/+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 1946599] Re: Firefox break when returning from console with wayland (nvidia) on ubuntu 21.10 beta
here the ugly raw about ** Attachment added: "about.txt" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1946599/+attachment/5534339/+files/about.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1946599 Title: Firefox break when returning from console with wayland (nvidia) on ubuntu 21.10 beta Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: (again snap firefox) Returning from console break all firefox tabs which have to be refreshed mv@i56400:~$ firefox [GFX1-]: glxtest: libEGL missing [GFX1-]: glxtest: EGL test failed xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel error: cannot send/recv xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390144,name=PContent::Msg_AsyncMessage) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv [Parent 6310, IPC I/O Parent] WARNING: FileDescriptorSet destroyed with unconsumed descriptors: file /build/firefox/parts/firefox/build/ipc/chromium/src/chrome/common/file_descriptor_set_posix.cc:19 After that, I logged under x11 (for test) but wasn't able to launch firefox: Error: cannot open display: :0 I had to reboot and the problem occurs only with wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1946599/+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 1946606] Re: thunderbird 91 does not support movemail
I agree that breaking an existing profile when upgrading with no way of recovering it after downgrading is very user-unfriendly. That said it's an upstream decision, and it was documented in the upstream release notes: https://www.thunderbird.net/en-US/thunderbird/91.0/releasenotes/. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1946606 Title: thunderbird 91 does not support movemail Status in thunderbird package in Ubuntu: Won't Fix Bug description: Thunderbird 91 does not support local Unix Mailspool (Movemail) accounts. This is apparently a well-known upstream decision, but is not documented in the Ubuntu changelog for the package, and the sudden absence of a local mail account is rather jarring to experience. > remove movemail support https://bugzilla.mozilla.org/show_bug.cgi?id=1625741 https://hg.mozilla.org/comm- central/rev/931a1fb770eb9bf6d2b99c7afcf07521376a5da4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1946606/+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 1947670] Re: /etc/profile.d/im-config_wayland.sh prevents sourcing /etc/profile
Hi Gunnar,
The software from $SILICON_VENDOR is installed using the Graphical
installer. Not long ago, the GUI install was the only option.
We run the actual build jobs via a Jenkins agent over SSH.
Here's a small stunt double of the build job
{code}
#!/bin/bash
set -ex
echo "XDG_SESSION_TYPE=$XDG_SESSION_TYPE"
# source environment from /etc/profile
. /etc/profile
echo "Continuing build with the environment set up"
{code}
The -e option is set according to our shell scripting recommendations, which
then aborts when sourcing
/etc/profile.d/im-config_wayland.sh
I suggest the below as a replacement
{code}
# /etc/profile.d/im-config_wayland.sh
#
# This sets the IM variables on Wayland.
if [ ! "$XDG_SESSION_TYPE" = 'wayland' ]; then
return
fi
# don't do anything if im-config was removed but not purged
if [ ! -r /usr/share/im-config/xinputrc.common ]; then
return
fi
if [ -r /etc/X11/Xsession.d/70im-config_launch ]; then
. /etc/X11/Xsession.d/70im-config_launch
fi
{code}
Assuming I didn't mess anything up, it should do the same thing - but
doesn't explode with the -e option set.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to im-config in Ubuntu.
https://bugs.launchpad.net/bugs/1947670
Title:
/etc/profile.d/im-config_wayland.sh prevents sourcing /etc/profile
Status in im-config package in Ubuntu:
Incomplete
Bug description:
We upgraded a build server from Ubuntu 18.04 to 20.04.
The build server had some scripts in /etc/profile.d/ that set up the
required build environment.
The builds would source `. /etc/profile` in the beginning.
After the upgrade, the script /etc/profile.d/im-config_wayland.sh
line
```
test "$XDG_SESSION_TYPE" = 'wayland' || return
```
evaluates with `test tty = wayland` returning the build script early.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1947670/+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 1940707] Re: [upstream] Maximized window becomes a mess at next startup after manually choosing to restore previous session
Launchpad has imported 3 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1677259. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2020-11-14T02:28:59+00:00 Lrebrown wrote: User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:82.0) Gecko/20100101 Firefox/82.0 Steps to reproduce: For the past few major firefox versions (at least) I've been experiencing an issue on Linux whereby when opening firefox (which I always use maximised and with session-restore enabled) the window frame ends up maximised, but with the window content (including titlebar elements) incorrectly drawn and positioned using the un-maximised window dimensions. To be clear, this is not just a content drawing issue, it's a positioning issue also - the actual window min/max/close buttons, for instance, are positioned according to the un-maximised window width from the left side of the screen. This typically if not exclusively seems to happen when I `alt+tab` away to a different app during loading of firefox, or at least it is more likely to re-occur if I do that. I'm using Debian Sid, with Gnome & Wayland. I have a HiDPI screen. This seems related to #1388670, possibly a duplicate, though that seems to focus on a situation with a specific setting that does not apply to me if you go by its title. This also describes the situation with webrenderer enabled (which is worse), for what that's worth. This is also possibly related to #1454156, which itself plays a part in poor startup behaviour and the fix for which may surely play some part in fixing the problem(s). Actual results: The startup experience follows this pattern: Initially the window starts out maximised with a single new empty tab. It takes several seconds to process the session data (I have a lot of open tabs, in the region of 2000+). As soon as it is done with that processing, the behaviour of #1454156 is seen, i.e. the window is suddenly replaced/resized giving an un-maximised window with the restored tabs; a split second later it is then restored to maximised again. After this silly max->unmax->max cycle the window content then sometimes is left stuck incorrectly at the un-maximised window dimensions. The details of this differ somewhat with webrenderer enabled, which I'll describe shortly in case it is of interest in fixing webrenderer bugs, especially since things are significantly worse under webrenderer. Without webrenderer the window content is simply drawn and elements positioned, using unmaximised-window dimensions, from the top left of the maximised window frame, with the remainder of the window area shown black. A quick workaround when this happens is to either double-click the titlebar or otherwise click the maximise button, such that the window becomes un-maximised; You can then re-maximise it, following which it will then be resized correctly. The problem typically or exclusively seems to occur when I `alt+tab` away to a different application during the firefox startup, though does not seem to reliably do so every single time. So for instance, if I turn on my computer, login, open my email application, open firefox, and just sit and wait for firefox to fully load with my restored session, it usually (or always?) does things correctly. However, if while firefox is sat processing the session data during its startup (remember, I have lots of tabs and so this takes multiple seconds for me), I `alt+tab` away to my email program to start reading email in the mean time, some seconds later once firefox has processed the session data, it then tries to steal focus, forcing itself on top of the mail application window (a bug in itself - is there an existing report?), requiring three `alt+tab`s (iirc) to switch back to the email I was reading. Or rather perhaps it's not stealing focus, but just incorrectly has its window drawn in the foreground instead of the background, not having bothered to recheck that it had focus? In this case it will sometimes encounter the window content dimension issue. Note, pressing `alt` to toggle the old window menu just updates the wrongly-drawn window content accordingly, it does *not* correct the dimensions used. With `gfx.webrenderer.all` enabled, behaviour is similar but worse. The key difference is, after taking several seconds to process the session data, what results from it then re-maximising the window: - again the un-maximised dimensions are incorrectly used to draw and position the window content within the maximised window frame. - this displayed content appears in the bottom left rather than top left. - the area to the right, with firefox having forced itself to the foreground over my maximised email client, shows a portion of said email client.
[Desktop-packages] [Bug 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition
** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1734791 Importance: Unknown Status: Unknown ** Changed in: firefox (Ubuntu) Status: New => Confirmed ** No longer affects: thunderbird (Ubuntu) -- 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/1849346 Title: [snap] kerberos GSSAPI no longer works after deb->snap transition Status in Mozilla Firefox: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: I configure AuthServerWhitelist as documented: https://www.chromium.org/developers/design-documents/http- authentication and can see my whitelisted domains in chrome://policy/ but websites that used to work with SPNEGO/GSSAPI/kerberos no longer work. I'm guessing the snap needs some sort of permission to use the kerberos ticket cache (or the plumbing to do so doesn't exist...). I can confirm that Chrome has the desired behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1849346/+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 1946599] Re: Firefox break when returning from console with wayland (nvidia) on ubuntu 21.10 beta
Can you please browse to about:support, copy the raw contents of the page and attach them here as a text file? Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1946599 Title: Firefox break when returning from console with wayland (nvidia) on ubuntu 21.10 beta Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: (again snap firefox) Returning from console break all firefox tabs which have to be refreshed mv@i56400:~$ firefox [GFX1-]: glxtest: libEGL missing [GFX1-]: glxtest: EGL test failed xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel error: cannot send/recv xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390144,name=PContent::Msg_AsyncMessage) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv [Parent 6310, IPC I/O Parent] WARNING: FileDescriptorSet destroyed with unconsumed descriptors: file /build/firefox/parts/firefox/build/ipc/chromium/src/chrome/common/file_descriptor_set_posix.cc:19 After that, I logged under x11 (for test) but wasn't able to launch firefox: Error: cannot open display: :0 I had to reboot and the problem occurs only with wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1946599/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding
Indeed, before closing the firefox task for this bug, we need to look into the situation with the deb package. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux browsers. In 2015 I opened this bug , no easy solution was available and battery drained when playing video in browser was crazy. In july 2020, things are getting better : - Chromium : A patch is used on most distro packages. Ubuntu now will integrate this patch on Snap chromium stable soon , more info here https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1816497 - Firefox : Firefox team has done a great job and now Va-api decoding in Wayland is possible and X11 is possible in nightly ! Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 We shall close this bug when both browsers will have Va-api decoding available in Stable. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file des
When I do right-click on .deb package and open it with Gdebi-gtk, and try to install a package on 21.10 (also used to happen od 21.04) program closes. I have downloaded 0.9.5.7+nmu6 and I think I have built it with dpkg- buildpackage - us -uc and still happens the same. 0.9.5.7+nmu6 works of gdebi-gtk is called from Terminal and .deb opened via File>Open , but it does not when on right-click and install in Thunar. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1946499 Title: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not installed Status in Ubuntu MATE: Invalid Status in gdebi package in Ubuntu: Fix Released Status in vte2.91 package in Ubuntu: Confirmed Status in gdebi source package in Impish: Triaged Bug description: Steps to reproduce: 1. Install Ubuntu MATE 21.10 2. Open Firefox, navigate to discord.com 3. Download deb-file. At time of writing from the https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link 4. Open Caja in ~/Downloads folder and use GDebi to install the discord-0.0.16.deb file 5. In the GDebi window click Install button Expected results: * Gdebi quietly install discord package, there are no error messages in its terminal Actual results: * Gdebi terminal shows the error in the last line ``` Selecting previously unselected package gconf2-common. (Reading database ... 457178 files and directories currently installed.) Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ... Unpacking gconf2-common (3.2.6-7ubuntu2) ... Selecting previously unselected package libgconf-2-4:amd64. Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ... Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service-backend. Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service-backend (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service. Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service (3.2.6-7ubuntu2) ... Selecting previously unselected package libappindicator1. Preparing to unpack .../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ... Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Selecting previously unselected package libunwind-13:amd64. Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ... Unpacking libunwind-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++abi1-13:amd64. Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1-13:amd64. Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1:amd64. Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ... Unpacking libc++1:amd64 (1:13.0-53~exp1) ... Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Setting up gconf2-common (3.2.6-7ubuntu2) ... Creating config file /etc/gconf/2/path with new version Setting up libunwind-13:amd64 (1:13.0.0-2) ... Setting up libc++abi1-13:amd64 (1:13.0.0-2) ... Setting up libc++1-13:amd64 (1:13.0.0-2) ... Setting up libc++1:amd64 (1:13.0-53~exp1) ... Setting up gconf-service (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... Processing triggers for sgml-base (1.30) ... Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Setting up gconf-service-backend (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... dpkg: error: unable to read filedescriptor flags for : Bad file descriptor ``` and as the result Discord package is not installed . ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdebi 0.9.5.7+nmu5ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Oct 8 18:17:36 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1940707] Re: Maximized window becomes a mess at next startup after manually choosing to restore previous session
That sounds like an upstream bug, possibly https://bugzilla.mozilla.org/show_bug.cgi?id=1677259. ** Bug watch added: Mozilla Bugzilla #1677259 https://bugzilla.mozilla.org/show_bug.cgi?id=1677259 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1677259 Importance: Unknown Status: Unknown ** Summary changed: - Maximized window becomes a mess at next startup after manually choosing to restore previous session + [upstream] Maximized window becomes a mess at next startup after manually choosing to restore previous session ** Tags added: upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1940707 Title: [upstream] Maximized window becomes a mess at next startup after manually choosing to restore previous session Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: Confirmed Bug description: Checked on both current and new user. This behavior is observed only if "Restore previous session" is not enabled to occur automatically at startup. 1) Ubuntu 20.04.2 LTS 2) 91.0+build2-0ubuntu0.20.04.1 3) "Restore previous session" should not change window settings and appearance 4) "Restore previous session" drastically changes window settings and appearance in a very unpleasant way Steps to reproduce: 1) Don't have "Restore previous session" enabled in Settings > General > Startup 2) Browse some sites 3) Close the window and confirm your desire to close it 4) Reopen Firefox 5) Go to History and select "Restore previous session" 6) The window will break apart as a result Screenshot below. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 91.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kbar 1005 F pulseaudio /dev/snd/controlC1: kbar 1005 F pulseaudio BuildID: 20210804193234 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: XFCE Date: Fri Aug 20 23:27:25 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2021-05-17 (95 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IpRoute: default via 192.168.1.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.102 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=91.0/20210804193234 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2014 dmi.bios.release: 15.54 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 220D dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.49 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.49 dmi.modalias: dmi:bvnInsyde:bvrF.36:bd12/18/2014:br15.54:efr86.49:svnHewlett-Packard:pnHP14NotebookPC:pvr097512405F0610180:rvnHewlett-Packard:rn220D:rvr86.49:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 14 Notebook PC dmi.product.sku: L8N69PA#UUF dmi.product.version: 097512405F0610180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1940707/+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 1934194] Re: package chromium-browser 91.0.4472.101-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error e
Can you try running the following command in a terminal, and let us know how this goes? sudo snap install chromium -- 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/1934194 Title: package chromium-browser 91.0.4472.101-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: Incomplete Bug description: Just installed and received system unstable messages. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 91.0.4472.101-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DRM.card0-DVI-I-1: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wBBDAhXAQEBAQAXAQOAZjl4CvntplJQnyQKR0qhCACBwIGAswCpwAEBAQEBAQEBAjqAGHE4LUBYLEUA+jwyAAAeqRoAoFAAFjAwIDcA+jwyAAAa/AAzMlBGTDU3MDgvRjcK/QAXTA9RDwAKICAgICAgAV0CAx9xSQECAwQFByCQBiYJBwcVB1BmAwwAIACA4gAPAjqAGHE4LUBYLEUA+jwyAAAeAR2AGHEcFiBYLCUA+jwyAACeAR0AclHQHiBuKFUA+jwyAAAejArQiiDgLRAQPpYA+jwyAAAYjAqgFFHwFgAmfEMA+jwyAACYzw== modes: 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080i 1920x1080 1920x1080 1680x1050 1600x900 1280x1024 1280x768 1280x720 1280x720 1280x720 1024x768 1440x480i 800x600 720x480 720x480 720x480 720x480 720x480 720x480i 720x480i 720x480i 720x480i 640x480 640x480 640x480 720x400 Date: Wed Jun 30 16:37:28 2021 Desktop-Session: 'None' 'None' 'None' Env: 'None' 'None' ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-09-01 (302 days ago) InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release amd64 (20190304.5) InstalledPlugins: Load-Avg-1min: 6.32 Load-Processes-Running-Percent: 0.2% MachineType: Hewlett-Packard s5-1070t ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-77-generic root=UUID=a8b4761a-7e53-4c94-9a12-3ace3096a126 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 91.0.4472.101-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-06-30 (0 days ago) dmi.bios.date: 10/05/2011 dmi.bios.vendor: AMI dmi.bios.version: 7.16 dmi.board.name: 2AC2 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.02A dmi.chassis.asset.tag: 2MD1450H90 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr7.16:bd10/05/2011:svnHewlett-Packard:pns5-1070t:pvr1.02A:rvnPEGATRONCORPORATION:rn2AC2:rvr1.02A:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: s5-1070t dmi.product.sku: LP019AV#ABA dmi.product.version: 1.02A dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1934194/+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 1947524] Re: Restore and maximize window laggy
Can you please run the following command in a terminal? apport-collect 1947524 ** Changed in: thunderbird (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1947524 Title: Restore and maximize window laggy Status in thunderbird package in Ubuntu: Incomplete Bug description: Fresh installation of Ubuntustudio 21.10 (Plasma desktop) with thunderbird 91.1.2 (deb version, not a snap). When I use the restore or maximize button of the thunderbird window, the screen is not updated correctly, it takes a few seconds and maybe never finishes. However, when I open the application menu, the screen will be instantly refreshed and the thunderbird window is drawn correctly then. I was able to take some screenshots: https://i.imgur.com/uNGDG05.jpg shows the screen about one and a half second after hitting the restore button https://i.imgur.com/pvpv4Ir.png shows the screen about one and a half second after hitting the maximize button. Since I'm having this problem with thunderbird only, I don't think it's related to Plasma but the application itself, but who knows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1947524/+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 1942364] Re: sonixb camera is unusable on Chromium
Can you please share the output of the following commands (when your camera is plugged)? cat /run/udev/data/b43:128 cat /run/udev/data/b43:0 ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/1942364 Title: sonixb camera is unusable on Chromium Status in chromium-browser package in Ubuntu: Incomplete Bug description: I'm trying to use an USB camera on Chromium, however it is not being detected. lsusb shows it as: Bus 001 Device 076: ID 0c45:6001 Microdia Genius VideoCAM NB While this camera isn't the best I've ever seen, it works properly when using ffplay and guvcview. The following is the output of some utilities related to the camera: $ v4l2-ctl --info Driver Info: Driver name : sonixb Card type: USB camera Bus info : usb-:00:14.0-1 Driver version : 5.11.22 Capabilities : 0x8521 Video Capture Read/Write Streaming Extended Pix Format Device Capabilities Device Caps : 0x0521 Video Capture Read/Write Streaming Extended Pix Format $ v4l2-ctl --list-formats-ext ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'S910' (GSPCA SN9C10X, compressed) Size: Discrete 160x120 Size: Discrete 176x144 Size: Discrete 320x240 Size: Discrete 352x288 [1]: 'BA81' (8-bit Bayer BGBG/GRGR) Size: Discrete 160x120 Size: Discrete 176x144 ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Sep 1 15:12:28 2021 InstallationDate: Installed on 2017-06-13 (1540 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Snap: chromium 92.0.4515.159 (latest/candidate) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to focal on 2019-12-22 (618 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1942364/+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 1947748] Re: Firefox application menu problem with wayland
*** This bug is a duplicate of bug 1940417 *** https://bugs.launchpad.net/bugs/1940417 ** This bug has been marked a duplicate of bug 1940417 On Wayland toolbar menus are sometimes invisible/flickering -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1947748 Title: Firefox application menu problem with wayland Status in firefox package in Ubuntu: Confirmed Bug description: Hi a few weeks ago, firefox stopped to display its menus. Dropdowns of add-ons stopped working, also. The system usually runs Gnome I tried to - use default GTK theme - use standard theme in Firefox - restart in safe-mode - disable hardware acceleration - use Ubuntu desktop instead of Gnome with no success. Then i've changed my desktop to "Ubuntu with Xorg" at login and the problem vanished. What's the matter? Kind regards, dsto Additional information Version:93.0+build1-0ubuntu3 Description: Ubuntu 21.10 Release: 21.10 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: firefox 93.0+build1-0ubuntu3 Uname: Linux 5.13.12-051312-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dani 33215 F pulseaudio /dev/snd/controlC1: dani 33215 F pulseaudio /dev/snd/controlC0: dani 33215 F pulseaudio BuildID: 20210927210923 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Oct 19 15:15:28 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-02-05 (1351 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-2342be4a-ba6e-477e-8b18-eeb621171002 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:360 PrefSources: prefs.js user.js Profiles: Profile0 (Default) - LastVersion=93.0/20210927210923 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to impish on 2021-07-28 (82 days ago) dmi.bios.date: 05/10/2018 dmi.bios.release: 2.32 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.32 dmi.board.asset.tag: CZC1365RZ5 dmi.board.name: 1495 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC1365RZ5 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.32:bd05/10/2018:br2.32:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:skuXL510AV:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq 8200 Elite SFF PC dmi.product.sku: XL510AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1947748/+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 1942364] Re: sonixb camera is unusable on Chromium
The denials on "/run/udev/data/b43:128" and "/run/udev/data/b43:0" may be relevant. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => New -- 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/1942364 Title: sonixb camera is unusable on Chromium Status in chromium-browser package in Ubuntu: New Bug description: I'm trying to use an USB camera on Chromium, however it is not being detected. lsusb shows it as: Bus 001 Device 076: ID 0c45:6001 Microdia Genius VideoCAM NB While this camera isn't the best I've ever seen, it works properly when using ffplay and guvcview. The following is the output of some utilities related to the camera: $ v4l2-ctl --info Driver Info: Driver name : sonixb Card type: USB camera Bus info : usb-:00:14.0-1 Driver version : 5.11.22 Capabilities : 0x8521 Video Capture Read/Write Streaming Extended Pix Format Device Capabilities Device Caps : 0x0521 Video Capture Read/Write Streaming Extended Pix Format $ v4l2-ctl --list-formats-ext ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'S910' (GSPCA SN9C10X, compressed) Size: Discrete 160x120 Size: Discrete 176x144 Size: Discrete 320x240 Size: Discrete 352x288 [1]: 'BA81' (8-bit Bayer BGBG/GRGR) Size: Discrete 160x120 Size: Discrete 176x144 ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Sep 1 15:12:28 2021 InstallationDate: Installed on 2017-06-13 (1540 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Snap: chromium 92.0.4515.159 (latest/candidate) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to focal on 2019-12-22 (618 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1942364/+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 1947746] Re: [Snap] Ubuntu Firefox installed from snap cannot use U2F
Similar to bug #1945182. Can you share the output of running `lsusb` in a terminal when your Trezor key is plugged in? ** Summary changed: - [Snap] Ubuntu Firefox installed from snap cannot use U2F + [Snap] Ubuntu Firefox installed from snap cannot use Trezor U2F ** Changed in: firefox (Ubuntu) Status: New => Incomplete ** Tags added: snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1947746 Title: [Snap] Ubuntu Firefox installed from snap cannot use Trezor U2F Status in firefox package in Ubuntu: Incomplete Bug description: Trezor U2F security key doesn't work with firefox snap after updating to Ubuntu 21.10, but works with apt debian firefox package. Steps to reproduce: 1) Insert Trezor U2F security key in USB port. 2) Launch `run snap firefox` (it is the default on Ubuntu 21.10) 3) Test https://demo.yubico.com/webauthn-technical/registration It works well on Ubuntu 21.04 and on traditional apt debian installation. $ snap list firefox Name Version Rev Tracking Publisher Notes firefox 93.0-1 631 latest/stable mozilla✓ - $ snap connections firefox Interface PlugSlot Notes audio-playbackfirefox:audio-playback :audio-playback - audio-record firefox:audio-record:audio-record - avahi-observe firefox:avahi-observe :avahi-observe - browser-support firefox:browser-sandbox :browser-support - camerafirefox:camera :camera - content[gnome-3-38-2004] firefox:gnome-3-38-2004 gnome-3-38-2004:gnome-3-38-2004 - content[gtk-3-themes] firefox:gtk-3-themes gtk-common-themes:gtk-3-themes - content[icon-themes] firefox:icon-themes gtk-common-themes:icon-themes- content[sound-themes] firefox:sound-themes gtk-common-themes:sound-themes - cups-control firefox:cups-control:cups-control - dbus - firefox:dbus-daemon - desktop firefox:desktop :desktop - desktop-legacyfirefox:desktop-legacy :desktop-legacy - gsettings firefox:gsettings :gsettings - hardware-observe firefox:hardware-observe:hardware-observe - home firefox:home:home - joystick firefox:joystick- - mpris - firefox:mpris - network firefox:network :network - network-observe firefox:network-observe - - openglfirefox:opengl :opengl - personal-filesfirefox:dot-mozilla-firefox :personal-files - removable-media firefox:removable-media :removable-media - screen-inhibit-controlfirefox:screen-inhibit-control :screen-inhibit-control - system-files firefox:etc-firefox-policies:system-files - system-packages-doc firefox:system-packages-doc :system-packages-doc - u2f-devices firefox:u2f-devices :u2f-devices - unity7firefox:unity7 :unity7 - upower-observefirefox:upower-observe :upower-observe - wayland firefox:wayland :wayland - x11 firefox:x11 :x11 - $ cat /etc/os-release PRETTY_NAME="Ubuntu 21.10" NAME="Ubuntu" VERSION_ID="21.10" VERSION="21.10 (Impish Indri)" VERSION_CODENAME=impish ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=impish $ echo $XDG_SESSION_TYPE wayland $ uname -r 5.13.0-19-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1947746/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1947748] Re: Firefox application menu problem with wayland
Can confirm as a Wayland issue. Example: The dropdown "Other bookmarks" menu on the Bookmarks toolbar won't display any bookmarks if the Firefox window is too near the right hand edge of the screen. Moving the window to the left (perhaps by making it smaller first) allows all bookmarks to be displayed both to the left and right of the dropdown menu. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1947748 Title: Firefox application menu problem with wayland Status in firefox package in Ubuntu: Confirmed Bug description: Hi a few weeks ago, firefox stopped to display its menus. Dropdowns of add-ons stopped working, also. The system usually runs Gnome I tried to - use default GTK theme - use standard theme in Firefox - restart in safe-mode - disable hardware acceleration - use Ubuntu desktop instead of Gnome with no success. Then i've changed my desktop to "Ubuntu with Xorg" at login and the problem vanished. What's the matter? Kind regards, dsto Additional information Version:93.0+build1-0ubuntu3 Description: Ubuntu 21.10 Release: 21.10 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: firefox 93.0+build1-0ubuntu3 Uname: Linux 5.13.12-051312-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dani 33215 F pulseaudio /dev/snd/controlC1: dani 33215 F pulseaudio /dev/snd/controlC0: dani 33215 F pulseaudio BuildID: 20210927210923 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Oct 19 15:15:28 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-02-05 (1351 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-2342be4a-ba6e-477e-8b18-eeb621171002 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:360 PrefSources: prefs.js user.js Profiles: Profile0 (Default) - LastVersion=93.0/20210927210923 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to impish on 2021-07-28 (82 days ago) dmi.bios.date: 05/10/2018 dmi.bios.release: 2.32 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.32 dmi.board.asset.tag: CZC1365RZ5 dmi.board.name: 1495 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC1365RZ5 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.32:bd05/10/2018:br2.32:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:skuXL510AV:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq 8200 Elite SFF PC dmi.product.sku: XL510AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1947748/+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 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
The bug is still present in 21.10 . This bug in 21.04 went away this August 2021 approx. But upgrading from 21.04 to 21.10 brought back the bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height Status in GNOME Terminal: New Status in gnome-terminal package in Ubuntu: Triaged Bug description: 1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt + T) 2. "stty -a | grep rows" reports "rows 24; columns 80;" 3. Maximize the window (by clicking on the maximize button, or double clicking the title bar, or dragging the window up to the panel) 4. Do the same again to un-maximize the window 5. Now "stty -a | grep rows" reports "rows 23; columns 79;" Each time I do this, the window keeps getting one character shorter and one character narrower! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Mar 6 10:22:46 2014 InstallationDate: Installed on 2010-04-15 (1421 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+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 1947748] [NEW] Firefox application menu problem with wayland
Public bug reported: Hi a few weeks ago, firefox stopped to display its menus. Dropdowns of add-ons stopped working, also. The system usually runs Gnome I tried to - use default GTK theme - use standard theme in Firefox - restart in safe-mode - disable hardware acceleration - use Ubuntu desktop instead of Gnome with no success. Then i've changed my desktop to "Ubuntu with Xorg" at login and the problem vanished. What's the matter? Kind regards, dsto Additional information Version:93.0+build1-0ubuntu3 Description:Ubuntu 21.10 Release:21.10 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: firefox 93.0+build1-0ubuntu3 Uname: Linux 5.13.12-051312-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dani 33215 F pulseaudio /dev/snd/controlC1: dani 33215 F pulseaudio /dev/snd/controlC0: dani 33215 F pulseaudio BuildID: 20210927210923 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Oct 19 15:15:28 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-02-05 (1351 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-2342be4a-ba6e-477e-8b18-eeb621171002 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:360 PrefSources: prefs.js user.js Profiles: Profile0 (Default) - LastVersion=93.0/20210927210923 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to impish on 2021-07-28 (82 days ago) dmi.bios.date: 05/10/2018 dmi.bios.release: 2.32 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.32 dmi.board.asset.tag: CZC1365RZ5 dmi.board.name: 1495 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC1365RZ5 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.32:bd05/10/2018:br2.32:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:skuXL510AV:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq 8200 Elite SFF PC dmi.product.sku: XL510AV dmi.sys.vendor: Hewlett-Packard ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1947748 Title: Firefox application menu problem with wayland Status in firefox package in Ubuntu: New Bug description: Hi a few weeks ago, firefox stopped to display its menus. Dropdowns of add-ons stopped working, also. The system usually runs Gnome I tried to - use default GTK theme - use standard theme in Firefox - restart in safe-mode - disable hardware acceleration - use Ubuntu desktop instead of Gnome with no success. Then i've changed my desktop to "Ubuntu with Xorg" at login and the problem vanished. What's the matter? Kind regards, dsto Additional information Version:93.0+build1-0ubuntu3 Description: Ubuntu 21.10 Release: 21.10 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: firefox 93.0+build1-0ubuntu3 Uname: Linux 5.13.12-051312-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dani 33215 F pulseaudio /dev/snd/controlC1: dani 33215 F pulseaudio /dev/snd/controlC0: dani 33215 F pulseaudio BuildID: 20210927210923 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Oct 19 15:15:28 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-02-05 (1351 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-2342be4a-ba6e-477e-8b18-eeb621171002 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:360 PrefSources: prefs.js user.js Profiles: Profile0 (Default) - LastVersion=93.0/20210927210923 (In use)
[Desktop-packages] [Bug 1947746] [NEW] [Snap] Ubuntu Firefox installed from snap cannot use U2F
Public bug reported: Trezor U2F security key doesn't work with firefox snap after updating to Ubuntu 21.10, but works with apt debian firefox package. Steps to reproduce: 1) Insert Trezor U2F security key in USB port. 2) Launch `run snap firefox` (it is the default on Ubuntu 21.10) 3) Test https://demo.yubico.com/webauthn-technical/registration It works well on Ubuntu 21.04 and on traditional apt debian installation. $ snap list firefox Name Version Rev Tracking Publisher Notes firefox 93.0-1 631 latest/stable mozilla✓ - $ snap connections firefox Interface PlugSlot Notes audio-playbackfirefox:audio-playback :audio-playback - audio-record firefox:audio-record:audio-record - avahi-observe firefox:avahi-observe :avahi-observe - browser-support firefox:browser-sandbox :browser-support - camerafirefox:camera :camera - content[gnome-3-38-2004] firefox:gnome-3-38-2004 gnome-3-38-2004:gnome-3-38-2004 - content[gtk-3-themes] firefox:gtk-3-themes gtk-common-themes:gtk-3-themes - content[icon-themes] firefox:icon-themes gtk-common-themes:icon-themes- content[sound-themes] firefox:sound-themes gtk-common-themes:sound-themes - cups-control firefox:cups-control:cups-control - dbus - firefox:dbus-daemon - desktop firefox:desktop :desktop - desktop-legacyfirefox:desktop-legacy :desktop-legacy - gsettings firefox:gsettings :gsettings - hardware-observe firefox:hardware-observe:hardware-observe - home firefox:home:home - joystick firefox:joystick- - mpris - firefox:mpris - network firefox:network :network - network-observe firefox:network-observe - - openglfirefox:opengl :opengl - personal-filesfirefox:dot-mozilla-firefox :personal-files - removable-media firefox:removable-media :removable-media - screen-inhibit-controlfirefox:screen-inhibit-control :screen-inhibit-control - system-files firefox:etc-firefox-policies:system-files - system-packages-doc firefox:system-packages-doc :system-packages-doc - u2f-devices firefox:u2f-devices :u2f-devices - unity7firefox:unity7 :unity7 - upower-observefirefox:upower-observe :upower-observe - wayland firefox:wayland :wayland - x11 firefox:x11 :x11 - $ cat /etc/os-release PRETTY_NAME="Ubuntu 21.10" NAME="Ubuntu" VERSION_ID="21.10" VERSION="21.10 (Impish Indri)" VERSION_CODENAME=impish ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=impish $ echo $XDG_SESSION_TYPE wayland $ uname -r 5.13.0-19-generic ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Package changed: chromium-browser (Ubuntu) => firefox (Ubuntu) -- 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/1947746 Title: [Snap] Ubuntu Firefox installed from snap cannot use U2F Status in firefox package in Ubuntu: New Bug description: Trezor U2F security key doesn't work with firefox snap after updating to Ubuntu 21.10, but works with apt debian firefox package. Steps to reproduce: 1) Insert Trezor U2F security key in USB port. 2) Launch `run snap firefox` (it is the default on Ubuntu 21.10) 3) Test https://demo.yubico.com/webauthn-technical/registration It works well on Ubuntu 21.04 and on traditional apt debian installation. $ snap list firefox Name Version Rev Tracking
Re: [Desktop-packages] [Bug 1947466] Re: [CREATIVE MUVO 1c, playback] volume slider does not change sound volume
i just noticed, this slider also doesn't work on my ps5 headset https://www.playstation.com/en-us/accessories/pulse-3d-wireless-headset/ niedz., 17 paź 2021 o 17:50 Hui Wang <1947...@bugs.launchpad.net> napisał(a): > bluetooth adapter is CSR8510 A10 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1947466 > > Title: > [CREATIVE MUVO 1c, playback] volume slider does not change sound > volume > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1947466/+subscriptions > > -- Paweł Bogaczewicz http://bogaczew.blip.pl/ if (statusIsNotValid.compareTo( Boolean.FALSE ) != 0) skipValidation = false; -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1947466 Title: [CREATIVE MUVO 1c, playback] volume slider does not change sound volume Status in alsa-driver package in Ubuntu: New Bug description: changing the volume of system volume does not affect the sound volume at all. i have to change volume of each program separetly. i.e to change volume of spotify i have to adjust the 'spotify' slider in settings, etc. i'm on fresh install of ubuntu 21.10 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pawel 1425 F pulseaudio /dev/snd/controlC1: pawel 1425 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 20:58:59 2021 InstallationDate: Installed on 2021-10-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: CREATIVE MUVO 1c Symptom_Type: Volume slider, or mixer problems Title: [CREATIVE MUVO 1c, playback] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: Default string dmi.board.name: H110M PRO-VD (MS-7996) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd07/27/2016:br5.11:svnMSI:pnMS-7996:pvr1.0:skuDefaultstring:rvnMSI:rnH110MPRO-VD(MS-7996):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7996 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1947466/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1947194] Re: When using Wayland in 21.04, the display often never wakes up after lock
The last error reported was on Oct 18 and the url is https://errors.ubuntu.com/oops/33300c46-3036-11ec-ad49-fa163e102db1 I've rebooted into wayland, but so far the bug has not occurred. It's possible that the synchronization is preventing it from happening. I will wait a while longer and if it still does not happen, I will disable synchronization and try again. On 2021-10-19 2:13 a.m., Daniel van Vugt wrote: > Per the instructions in comment #5: > > "If step 1 failed then look at https://errors.ubuntu.com/user/ID where > ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. > Do you find any links to recent problems on that page? If so then please > send the links to us." > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1947194 Title: When using Wayland in 21.04, the display often never wakes up after lock Status in mutter package in Ubuntu: Incomplete Bug description: When using Wayland in 21.04, the display often never wakes up after lock up. Also, on boot up, desktop icons and most favorites on dash are not displayed, even though desktop icons are enabled. I can get them to show up only by re-enabling desktop icons. The workaround now is to disable Wayland, and the original xorg server works fine. The display driver is: 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) The monitor is an HP 22cwa running of of a displayport interface. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 14 14:32:26 2021 DistUpgraded: 2021-07-28 16:05:54,589 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:047e] InstallationDate: Installed on 2018-12-04 (1044 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. OptiPlex 990 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-07-28 (77 days ago) dmi.bios.date: 11/24/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd11/24/2011:br4.6:svnDellInc.:pnOptiPlex990:pvr01:sku:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1947194/+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 1947706] Re: gnome crash after power save and display turn on
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1947706 Title: gnome crash after power save and display turn on Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hi My desktop crashed and sent me back to login page. After input my password display switched black again and then showed login screen. Just reboot fixed my problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 19 11:46:44 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-11-27 (325 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1947706/+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 1947706] [NEW] gnome crash after power save and display turn on
Public bug reported: Hi My desktop crashed and sent me back to login page. After input my password display switched black again and then showed login screen. Just reboot fixed my problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 19 11:46:44 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-11-27 (325 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1947706 Title: gnome crash after power save and display turn on Status in gnome-shell package in Ubuntu: New Bug description: Hi My desktop crashed and sent me back to login page. After input my password display switched black again and then showed login screen. Just reboot fixed my problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 19 11:46:44 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-11-27 (325 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1947706/+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 1947698] [NEW] window buttons alignment is wrong in RTL locales
Public bug reported: In RTL locales (e.g. fa_IR.UTF-8), the alignment of window buttons (close, min, max) is reverted. For example, in the `gnome-chess` or `extensions`, window buttons are in the right corner, when all other windows has buttons on the left. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libgtk-4-1 4.4.0+ds1-5 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 19 12:57:21 2021 InstallationDate: Installed on 2021-07-13 (98 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fa_IR SHELL=/bin/bash SourcePackage: gtk4 UpgradeStatus: Upgraded to impish on 2021-10-16 (2 days ago) ** Affects: gtk4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/1947698 Title: window buttons alignment is wrong in RTL locales Status in gtk4 package in Ubuntu: New Bug description: In RTL locales (e.g. fa_IR.UTF-8), the alignment of window buttons (close, min, max) is reverted. For example, in the `gnome-chess` or `extensions`, window buttons are in the right corner, when all other windows has buttons on the left. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libgtk-4-1 4.4.0+ds1-5 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 19 12:57:21 2021 InstallationDate: Installed on 2021-07-13 (98 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fa_IR SHELL=/bin/bash SourcePackage: gtk4 UpgradeStatus: Upgraded to impish on 2021-10-16 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/1947698/+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 1947690] Re: Default Text Editor dark theme has unreadable colour contrasts
*** This bug is a duplicate of bug 1857191 *** https://bugs.launchpad.net/bugs/1857191 ** This bug has been marked a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1947690 Title: Default Text Editor dark theme has unreadable colour contrasts Status in gedit package in Ubuntu: New Bug description: On a clean install of Ubuntu 20.04, the installation prompts allowed me to choose dark theme, which has apparently carried over to the Text Editor that is also installed by default. The problem is that this dark theme makes the currently-typed line basically illegible due to it being an extremely similar colour to the text being written. There are a few other colours that seem to also make the text difficult to read, including the "search" functionality's highlighted text colour. Both of these problems are visible in the attached screenshot :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 19 18:32:31 2021 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2021-10-09 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_AU:en LANG=en_AU.UTF-8 SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1947690/+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 1946098] Re: Update to 91.2.0 in impish
Mozilla products (including thunderbird) have a standing micro-release exception (see https://wiki.ubuntu.com/SecurityTeam/PublicationNotes#Mozilla), and as this update contains security fixes (https://www.mozilla.org/en- US/security/advisories/mfsa2021-47/) we'll go that route instead. Feel free to reject from the queue. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1946098 Title: Update to 91.2.0 in impish Status in thunderbird package in Ubuntu: Incomplete Bug description: impish currently has thunderbird 1:91.1.2+build1-0ubuntu1, which at the time of filing this bug is the latest stable release (so all is good). There is a new release candidate, 91.2.0+build1 (https://ftp.mozilla.org/pub/thunderbird/candidates/91.2.0-candidates/build1/) which, if everything goes fine, will become a release before impish is released. I intend to upload that RC to impish-proposed, so I'm filing this bug for the release team to decide whether it's worth accepting in the release, or leaving it out as a 0-day SRU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1946098/+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 1947690] [NEW] Default Text Editor dark theme has unreadable colour contrasts
Public bug reported: On a clean install of Ubuntu 20.04, the installation prompts allowed me to choose dark theme, which has apparently carried over to the Text Editor that is also installed by default. The problem is that this dark theme makes the currently-typed line basically illegible due to it being an extremely similar colour to the text being written. There are a few other colours that seem to also make the text difficult to read, including the "search" functionality's highlighted text colour. Both of these problems are visible in the attached screenshot :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 19 18:32:31 2021 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2021-10-09 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_AU:en LANG=en_AU.UTF-8 SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot of Text Editor with line selection visible" https://bugs.launchpad.net/bugs/1947690/+attachment/5534129/+files/Screenshot%20from%202021-10-19%2018-31-01.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1947690 Title: Default Text Editor dark theme has unreadable colour contrasts Status in gedit package in Ubuntu: New Bug description: On a clean install of Ubuntu 20.04, the installation prompts allowed me to choose dark theme, which has apparently carried over to the Text Editor that is also installed by default. The problem is that this dark theme makes the currently-typed line basically illegible due to it being an extremely similar colour to the text being written. There are a few other colours that seem to also make the text difficult to read, including the "search" functionality's highlighted text colour. Both of these problems are visible in the attached screenshot :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 19 18:32:31 2021 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2021-10-09 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_AU:en LANG=en_AU.UTF-8 SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1947690/+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 1947685] Re: gnome-shell crashed with SIGSEGV in cogl_texture_get_width(texture = NULL) from get_buffer_width() from get_buffer_width() from meta_wayland_surface_get_width() fr
** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1947685 Title: gnome-shell crashed with SIGSEGV in cogl_texture_get_width(texture = NULL) from get_buffer_width() from get_buffer_width() from meta_wayland_surface_get_width() from meta_wayland_surface_get_width() Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.5-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/7fa09adf57bf9e8d35fbe3a152ee4110a1e2e174 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1947685/+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 1947685] Re: gnome-shell crashed with SIGSEGV in cogl_texture_get_width() from get_buffer_width() from get_buffer_width() from meta_wayland_surface_get_width() from meta_waylan
** Summary changed: - /usr/bin/gnome-shell:11:cogl_texture_get_width:get_buffer_width:get_buffer_width:meta_wayland_surface_get_width:meta_wayland_surface_get_width + gnome-shell crashed with SIGSEGV in cogl_texture_get_width() from get_buffer_width() from get_buffer_width() from meta_wayland_surface_get_width() from meta_wayland_surface_get_width() ** Summary changed: - gnome-shell crashed with SIGSEGV in cogl_texture_get_width() from get_buffer_width() from get_buffer_width() from meta_wayland_surface_get_width() from meta_wayland_surface_get_width() + gnome-shell crashed with SIGSEGV in cogl_texture_get_width(texture = NULL) from get_buffer_width() from get_buffer_width() from meta_wayland_surface_get_width() from meta_wayland_surface_get_width() ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1750 https://gitlab.gnome.org/GNOME/mutter/-/issues/1750 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1750 Importance: Unknown Status: Unknown -- 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/1947685 Title: gnome-shell crashed with SIGSEGV in cogl_texture_get_width(texture = NULL) from get_buffer_width() from get_buffer_width() from meta_wayland_surface_get_width() from meta_wayland_surface_get_width() Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.5-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/7fa09adf57bf9e8d35fbe3a152ee4110a1e2e174 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1947685/+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 1947315] Re: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_pa
Also tracking in https://errors.ubuntu.com/problem/1195578f641b673463009c8b7431553fce7b3586 -- 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/1947315 Title: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_paint_box() from st_theme_node_transition_get_paint_box() Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.5-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/9e0eb2f488ad83e41a8977709955a661857ba95e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1947315/+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 1947683] Re: /usr/bin/gnome-shell:11:__strcmp_avx2:st_theme_node_lookup_shadow:st_theme_node_get_box_shadow:st_theme_node_get_box_shadow:st_theme_node_get_paint_box
*** This bug is a duplicate of bug 1947315 *** https://bugs.launchpad.net/bugs/1947315 ** This bug has been marked a duplicate of bug 1947315 gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_paint_box() from st_theme_node_transition_get_paint_box() -- 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/1947683 Title: /usr/bin/gnome- shell:11:__strcmp_avx2:st_theme_node_lookup_shadow:st_theme_node_get_box_shadow:st_theme_node_get_box_shadow:st_theme_node_get_paint_box Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.5-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/1195578f641b673463009c8b7431553fce7b3586 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1947683/+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 1947683] [NEW] /usr/bin/gnome-shell:11:__strcmp_avx2:st_theme_node_lookup_shadow:st_theme_node_get_box_shadow:st_theme_node_get_box_shadow:st_theme_node_get_paint_box
*** This bug is a duplicate of bug 1947315 *** https://bugs.launchpad.net/bugs/1947315 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.5-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/1195578f641b673463009c8b7431553fce7b3586 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: hirsute impish -- 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/1947683 Title: /usr/bin/gnome- shell:11:__strcmp_avx2:st_theme_node_lookup_shadow:st_theme_node_get_box_shadow:st_theme_node_get_box_shadow:st_theme_node_get_paint_box Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.5-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/1195578f641b673463009c8b7431553fce7b3586 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1947683/+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 1947685] [NEW] gnome-shell crashed with SIGSEGV in cogl_texture_get_width(texture = NULL) from get_buffer_width() from get_buffer_width() from meta_wayland_surface_get_width()
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.5-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/7fa09adf57bf9e8d35fbe3a152ee4110a1e2e174 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: mutter Importance: Unknown Status: Unknown ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: focal hirsute impish -- 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/1947685 Title: gnome-shell crashed with SIGSEGV in cogl_texture_get_width(texture = NULL) from get_buffer_width() from get_buffer_width() from meta_wayland_surface_get_width() from meta_wayland_surface_get_width() Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.5-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/7fa09adf57bf9e8d35fbe3a152ee4110a1e2e174 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1947685/+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 1947519] Re: Unless gedit is installed, "Appearance" causes control center to crash
I assumed that the patch was changed in version 1:40.0-1ubuntu4 for a reason, which made it natural to me to add the dependency. I understand that an alternative solution is to change it so it falls back to the previous behavior if the schema is missing. Please feel free to do that instead and drop the dependency. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1947519 Title: Unless gedit is installed, "Appearance" causes control center to crash Status in gnome-control-center package in Ubuntu: In Progress Bug description: Ubuntu 21.10. Gedit not installed from deb (I use a Flatpak version). Steps to reproduce: - sudo apt remove gedit - sudo apt autoremove - gnome-control-center ubuntu Expected: control center opens with Appearance tab shown Experienced: nothing happens, log in terminal: (gnome-control-center:27462): GLib-GIO-ERROR **: 22:03:20.416: Settings schema 'org.gnome.gedit.preferences.editor' is not installed ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 21:57:23 2021 InstallationDate: Installed on 2021-06-30 (109 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to impish on 2021-10-15 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1947519/+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 1922884] Re: transmission-gtk segfault (core dumped)
I found nothing in /var/crash but in step 2 here the link : https://errors.ubuntu.com/oops/4d63d2e6-9775-11eb-96c2-fa163ee63de6 Now the machine has been upgraded to Impish but transmission always crash. So I got a crash file but when I try : ubuntu-bug /var/crash/_usr_bin_transmission-gtk.1000.crash I click on "Send" in the popup nd... nothing. :-/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1922884 Title: transmission-gtk segfault (core dumped) Status in transmission package in Ubuntu: Confirmed Bug description: Unable to launch transmission-gtk application, segfault. Ubuntu 21.04 up-to-date. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: transmission-gtk 3.00-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 7 09:47:02 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: transmission UpgradeStatus: Upgraded to hirsute on 2020-06-09 (301 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1922884/+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 1947677] [NEW] Colemak keyboard layout's left-hand backspace is also acting as Caps Lock
Public bug reported: I have installed Ubuntu with the default English (US) Qwerty keyboard layout and I added the English (Australia) Colemak keyboard layout through the Settings app (as per the screenshot attached). This is for the in-built laptop keyboard on the Lenovo ThinkPad X1 Yoga Touch. The bug is that the CapsLock key, which is meant to be remapped to a Backspace key on the Colemak keyboard layout, acts as both the CapsLock AND the Backspace, when the Colemak keyboard layout is active. This means that backspacing a single time deletes a single character AND also toggles Caps Lock. The expected behaviour is that the key acts only as Backspace when the Colemak keyboard layout is active. The output of 횡횙횛횘횙 -횛횘횘횝 | 횐횛횎횙 횇홺홱 is _횇홺홱_횁횄홻홴횂_홽홰홼홴횂(횂횃횁홸홽홶) = "횎횟획횎횟", "횙회ퟷퟶퟻ", "횞횜,횞횜,횞횜", ",회횘횕횎횖횊횔,", "" I hope a fix can be found soon :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 19 17:34:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:224e] InstallationDate: Installed on 2021-10-09 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20JDA00CAU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-38-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2021 dmi.bios.release: 1.41 dmi.bios.vendor: LENOVO dmi.bios.version: N1NET54W (1.41 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JDA00CAU dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrN1NET54W(1.41):bd08/17/2021:br1.41:efr1.19:svnLENOVO:pn20JDA00CAU:pvrThinkPadX1Yoga2nd:skuLENOVO_MT_20JD_BU_Think_FM_ThinkPad:rvnLENOVO:rn20JDA00CAU:rvrSDK0K17763WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad dmi.product.name: 20JDA00CAU dmi.product.sku: LENOVO_MT_20JD_BU_Think_FM_ThinkPad dmi.product.version: ThinkPad X1 Yoga 2nd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 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+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "Screenshot of keyboard layouts installed on this laptop" https://bugs.launchpad.net/bugs/1947677/+attachment/5534082/+files/Screenshot%20from%202021-10-19%2017-39-51.png -- 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/1947677 Title: Colemak keyboard layout's left-hand backspace is also acting as Caps Lock Status in xorg package in Ubuntu: New Bug description: I have installed Ubuntu with the default English (US) Qwerty keyboard layout and I added the English (Australia) Colemak keyboard layout through the Settings app (as per the screenshot attached). This is for the in-built laptop keyboard on the Lenovo ThinkPad X1 Yoga Touch. The bug is that the CapsLock key, which is meant to be remapped to a Backspace key on the Colemak keyboard layout, acts as both the CapsLock AND the Backspace, when the Colemak keyboard layout is active. This means that backspacing a single time deletes a single character AND also toggles Caps Lock. The expected behaviour is that the key acts only as Backspace when the Colemak keyboard layout is active. The output of 횡횙횛횘횙 -횛횘횘횝 | 횐횛횎횙 횇홺홱 is _횇홺홱_횁횄홻홴횂_홽홰홼홴횂(횂횃횁홸홽홶) = "횎횟획횎횟", "횙회ퟷퟶퟻ", "횞횜,횞횜,횞횜", ",회횘횕횎횖횊횔,", "" I hope a fix can be found soon :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux
[Desktop-packages] [Bug 1947670] Re: /etc/profile.d/im-config_wayland.sh prevents sourcing /etc/profile
Thanks for your report. The script is there to set some input method related env. variables in case of a wayland session. (If an X session, /etc/X11/Xsession.d/70im- config_launch is started via Xsession instead.) Can you please explain how it is a problem if no input method configuration is accomplished on a build server? ** Changed in: im-config (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1947670 Title: /etc/profile.d/im-config_wayland.sh prevents sourcing /etc/profile Status in im-config package in Ubuntu: Incomplete Bug description: We upgraded a build server from Ubuntu 18.04 to 20.04. The build server had some scripts in /etc/profile.d/ that set up the required build environment. The builds would source `. /etc/profile` in the beginning. After the upgrade, the script /etc/profile.d/im-config_wayland.sh line ``` test "$XDG_SESSION_TYPE" = 'wayland' || return ``` evaluates with `test tty = wayland` returning the build script early. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1947670/+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 1947519] Re: Unless gedit is installed, "Appearance" causes control center to crash
You're creating a dependency that doesn't need to exist. All we need to do is handle the case when the schema is missing with a little code change. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1947519 Title: Unless gedit is installed, "Appearance" causes control center to crash Status in gnome-control-center package in Ubuntu: In Progress Bug description: Ubuntu 21.10. Gedit not installed from deb (I use a Flatpak version). Steps to reproduce: - sudo apt remove gedit - sudo apt autoremove - gnome-control-center ubuntu Expected: control center opens with Appearance tab shown Experienced: nothing happens, log in terminal: (gnome-control-center:27462): GLib-GIO-ERROR **: 22:03:20.416: Settings schema 'org.gnome.gedit.preferences.editor' is not installed ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 21:57:23 2021 InstallationDate: Installed on 2021-06-30 (109 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to impish on 2021-10-15 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1947519/+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 1870597] Re: libinput says: scheduled expiry is in the past... your system is too slow
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4709 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4709 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4709 Importance: Unknown Status: Unknown ** Summary changed: - libinput says: scheduled expiry is in the past... your system is too slow + libinput says "your system is too slow" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1870597 Title: libinput says "your system is too slow" Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Confirmed Bug description: During the freeze, the output of the install had a message from "gdm- x-session" saying "your system is too slow". To reproduce: 1. Launch the Ubuntu installer 2. Begin the installation process 3. When the installation process begins, move the cursor around 4. Notice how the PC freezes and drops mouse events Description: Ubuntu Focal Fossa (development branch) Release: 20.04 gnome-shell: Installed: 3.36.0-2ubuntu2 Candidate: 3.36.0-2ubuntu2 Version table: *** 3.36.0-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CasperVersion: 1.442 Date: Fri Apr 3 14:24:21 2020 DisplayManager: gdm3 GsettingsChanges: LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Inspiron 5570 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed quiet splash --- ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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-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/gnome-shell/+bug/1870597/+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 1947519] Re: Unless gedit is installed, "Appearance" causes control center to crash
Not sure what you mean by that, Daniel. By letting g-c-c depend on gedit-common, we make sure that the schema is never missing. If a user uninstalls gedit, gedit-common won't be uninstalled via "apt autoremove". Hence there is no need to figure out how to handle a missing schema graciously, is it? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1947519 Title: Unless gedit is installed, "Appearance" causes control center to crash Status in gnome-control-center package in Ubuntu: In Progress Bug description: Ubuntu 21.10. Gedit not installed from deb (I use a Flatpak version). Steps to reproduce: - sudo apt remove gedit - sudo apt autoremove - gnome-control-center ubuntu Expected: control center opens with Appearance tab shown Experienced: nothing happens, log in terminal: (gnome-control-center:27462): GLib-GIO-ERROR **: 22:03:20.416: Settings schema 'org.gnome.gedit.preferences.editor' is not installed ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 21:57:23 2021 InstallationDate: Installed on 2021-06-30 (109 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to impish on 2021-10-15 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1947519/+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 1947670] [NEW] /etc/profile.d/im-config_wayland.sh prevents sourcing /etc/profile
Public bug reported: We upgraded a build server from Ubuntu 18.04 to 20.04. The build server had some scripts in /etc/profile.d/ that set up the required build environment. The builds would source `. /etc/profile` in the beginning. After the upgrade, the script /etc/profile.d/im-config_wayland.sh line ``` test "$XDG_SESSION_TYPE" = 'wayland' || return ``` evaluates with `test tty = wayland` returning the build script early. ** Affects: im-config (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1947670 Title: /etc/profile.d/im-config_wayland.sh prevents sourcing /etc/profile Status in im-config package in Ubuntu: New Bug description: We upgraded a build server from Ubuntu 18.04 to 20.04. The build server had some scripts in /etc/profile.d/ that set up the required build environment. The builds would source `. /etc/profile` in the beginning. After the upgrade, the script /etc/profile.d/im-config_wayland.sh line ``` test "$XDG_SESSION_TYPE" = 'wayland' || return ``` evaluates with `test tty = wayland` returning the build script early. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1947670/+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 1946434] Re: SRU: Set on-demand as default, enable RTD3 only on laptops and decouple on-demand with RTD3
Upload debdiff for hirsute ** Patch added: "nvidia-prime_0.8.16.2~0.21.04.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1946434/+attachment/5534071/+files/nvidia-prime_0.8.16.2~0.21.04.1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1946434 Title: SRU: Set on-demand as default, enable RTD3 only on laptops and decouple on-demand with RTD3 Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: New Bug description: [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install 20.04.3 with "Third-party packages". After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * on-demand mode supported after nvidia driver 450. And focal does not have nvidia driver lower than 450. * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946434/+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 1947194] Re: When using Wayland in 21.04, the display often never wakes up after lock
Per the instructions in comment #5: "If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us." -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1947194 Title: When using Wayland in 21.04, the display often never wakes up after lock Status in mutter package in Ubuntu: Incomplete Bug description: When using Wayland in 21.04, the display often never wakes up after lock up. Also, on boot up, desktop icons and most favorites on dash are not displayed, even though desktop icons are enabled. I can get them to show up only by re-enabling desktop icons. The workaround now is to disable Wayland, and the original xorg server works fine. The display driver is: 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) The monitor is an HP 22cwa running of of a displayport interface. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 14 14:32:26 2021 DistUpgraded: 2021-07-28 16:05:54,589 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:047e] InstallationDate: Installed on 2018-12-04 (1044 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. OptiPlex 990 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-07-28 (77 days ago) dmi.bios.date: 11/24/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd11/24/2011:br4.6:svnDellInc.:pnOptiPlex990:pvr01:sku:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1947194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1947194] Re: When using Wayland in 21.04, the display often never wakes up after lock
I was able to upload the first crash, but no web browser opened so I don't know where it went. The second crash would not upload because it said that the crash was about a package that was not installed. I edited the environment file and will try to reproduce teh bug tomorrow. Chris On 2021-10-18 9:46 p.m., Daniel van Vugt wrote: > If ubuntu-bug fails then try apport-cli instead. > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1947194 Title: When using Wayland in 21.04, the display often never wakes up after lock Status in mutter package in Ubuntu: Incomplete Bug description: When using Wayland in 21.04, the display often never wakes up after lock up. Also, on boot up, desktop icons and most favorites on dash are not displayed, even though desktop icons are enabled. I can get them to show up only by re-enabling desktop icons. The workaround now is to disable Wayland, and the original xorg server works fine. The display driver is: 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) The monitor is an HP 22cwa running of of a displayport interface. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 14 14:32:26 2021 DistUpgraded: 2021-07-28 16:05:54,589 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:047e] InstallationDate: Installed on 2018-12-04 (1044 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. OptiPlex 990 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-07-28 (77 days ago) dmi.bios.date: 11/24/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd11/24/2011:br4.6:svnDellInc.:pnOptiPlex990:pvr01:sku:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1947194/+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
