[Desktop-packages] [Bug 1939625] Re: DNS setting in network-manager is ignored
** Changed in: network-manager (Ubuntu) Status: New => Fix Released -- 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/1939625 Title: DNS setting in network-manager is ignored Status in network-manager package in Ubuntu: Fix Released Bug description: DNS setting is network-manager is ignored. Instead, /etc/resolv.conf nameserver is used by programs. see screenshot ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 12 02:36:06 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2021-08-10 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterestingModules: b44 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.22.10 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1939625/+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 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy)
This bug was fixed in the package libsignon-glib - 2.1-3ubuntu1 --- libsignon-glib (2.1-3ubuntu1) jammy; urgency=medium * add replaces relationship to gir1.2-signon-2.0 package. LP: #1916250 -- Rolf Leggewie Fri, 19 Feb 2021 16:52:20 +0100 ** Changed in: libsignon-glib (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy) Status in libsignon-glib package in Ubuntu: Fix Released Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+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 1948513] [NEW] window response slow
Public bug reported: 1) lsb_release -rd Description:Ubuntu 21.10 Release:21.10 2)apt-cache policy rhythmbox rhythmbox: インストールされているバージョン: 3.4.4-1ubuntu5 3) UI responds to scrolls and clicks within 1 second at the latest. 4) UI response is slow. It takes 2-5 seconds to respond to scrolls and clicks. There is no problem immediately after startup, but after a while the response slows down. It takes about 30 seconds after startup to operate at normal response speed. When I restart the application, the response is just as slow. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: rhythmbox 3.4.4-1ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 23 12:59:25 2021 InstallationDate: Installed on 2020-11-05 (351 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: Upgraded to impish on 2021-10-23 (0 days ago) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Attachment added: "system-monitor cpu usage" https://bugs.launchpad.net/bugs/1948513/+attachment/5535366/+files/Screenshot%20from%202021-10-23%2013-06-12.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1948513 Title: window response slow Status in rhythmbox package in Ubuntu: New Bug description: 1) lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 2)apt-cache policy rhythmbox rhythmbox: インストールされているバージョン: 3.4.4-1ubuntu5 3) UI responds to scrolls and clicks within 1 second at the latest. 4) UI response is slow. It takes 2-5 seconds to respond to scrolls and clicks. There is no problem immediately after startup, but after a while the response slows down. It takes about 30 seconds after startup to operate at normal response speed. When I restart the application, the response is just as slow. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: rhythmbox 3.4.4-1ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 23 12:59:25 2021 InstallationDate: Installed on 2020-11-05 (351 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: Upgraded to impish on 2021-10-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1948513/+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 1738251]
Dear bugcatcher1,
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of
LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
https://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat:
https://web.libera.chat/?settings=#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Warm Regards,
QA Team
MassPing-UntouchedBug
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1738251
Title:
[upstream] Missing Data when Copying from Clipboard to Writer
Status in LibreOffice:
Confirmed
Status in libreoffice package in Ubuntu:
Confirmed
Bug description:
I have copied and pasted the webpage
'https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/1607535' into
LibreOffice, so as to be able to print and read it. The resulting page is
incomplete. Thus, for example, at [Workaround 1], where the the following
command line is specified:
$ wget http://downloads.sourceforge.net/corefonts/
{andale32.exe,arial32.exe,arialb32.exe,comic32.exe,courie32.exe,
georgi32.exe,impact32.exe,times32.exe,trebuc32.exe,verdan32.exe,
webdin32.exe}
only the following text appears:
$ wget http://
{
georgi32.
webdin32.exe}
The HTML code for that text is:
$ wget http://downloads.sourceforge.net/corefonts/;>http://downloads.sourceforge.net/corefonts/
{andale32.exe,arial32.exe,arialb32.exe,comic32.exe,courie32.exe,
georgi32.exe,impact32.exe,times32.exe,trebuc32.exe,verdan32.exe,
webdin32.exe}
The problem is triggered by the tag. Where one of these occurs in the
HTML, all subsequent text is omitted until either a or a tag is
reached (and of course there may be others).
As there are 956 tags in this document, much of the text is missing
after pasting. If the all the tags are removed from the page, copying
and pasting works fine.
I shall be grateful for help with the problem, as it means that that with
LibreOffice copying and pasting is unreliable.
Ubuntu Mate 16.04.3
lsb-release: 9.20160110ubuntu0.2
LibreOffice Writer: libreoffice-writer 1:5.1.6-rc20ubuntu1-xenial2
To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1738251/+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 1948511] [NEW] Very low volume output: Realtek ALC1222 in Omen 30L desktop
Public bug reported: Volume at 100% + Speaker knob at 100% and I get barely audio than can be barely heard. Alsa Info link: http://alsa- project.org/db/?f=5bf0f297f3700c75db822f78d563962f563f355c ``` lspci 00:00.0 Host bridge: Intel Corporation Device 9b33 (rev 05) 00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 05) 00:12.0 Signal processing controller: Intel Corporation Comet Lake PCH Thermal Controller 00:14.0 USB controller: Intel Corporation Comet Lake USB 3.1 xHCI Host Controller 00:14.2 RAM memory: Intel Corporation Comet Lake PCH Shared SRAM 00:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi 00:16.0 Communication controller: Intel Corporation Comet Lake HECI Controller 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller 00:1c.0 PCI bridge: Intel Corporation Device 06bc (rev f0) 00:1d.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #9 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0685 00:1f.3 Audio device: Intel Corporation Comet Lake PCH cAVS 00:1f.4 SMBus: Intel Corporation Comet Lake PCH SMBus Controller 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake PCH SPI Controller 01:00.0 VGA compatible controller: NVIDIA Corporation GA102 [GeForce RTX 3090] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GA102 High Definition Audio Controller (rev a1) 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 16) 03:00.0 Non-Volatile memory controller: Sandisk Corp WD Black SN750 / PC SN730 NVMe SSD ``` ``` sudo dmesg | grep snd [6.624036] snd_hda_intel :00:1f.3: enabling device (0100 -> 0102) [6.624372] snd_hda_intel :01:00.1: enabling device (0100 -> 0102) [6.624423] snd_hda_intel :01:00.1: Disabling MSI [6.624426] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [6.776175] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC1220: line_outs=1 (0x1b/0x0/0x0/0x0/0x0) type:line [6.776179] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [6.776181] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x14/0x0/0x0/0x0/0x0) [6.776182] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [6.776183] snd_hda_codec_realtek hdaudioC0D0:inputs: [6.776184] snd_hda_codec_realtek hdaudioC0D0: Rear Mic=0x18 [6.776186] snd_hda_codec_realtek hdaudioC0D0: Front Mic=0x19 [6.776187] snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a [6.776188] snd_hda_codec_realtek hdaudioC0D0: Line=0x15 ``` ``` cat /proc/asound/car*/co* | grep Codec Codec: Realtek ALC1220 Codec: Nvidia GPU 9a HDMI/DP ``` ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: 30l alc1222 omen realtek -- 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/1948511 Title: Very low volume output: Realtek ALC1222 in Omen 30L desktop Status in alsa-driver package in Ubuntu: New Bug description: Volume at 100% + Speaker knob at 100% and I get barely audio than can be barely heard. Alsa Info link: http://alsa- project.org/db/?f=5bf0f297f3700c75db822f78d563962f563f355c ``` lspci 00:00.0 Host bridge: Intel Corporation Device 9b33 (rev 05) 00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 05) 00:12.0 Signal processing controller: Intel Corporation Comet Lake PCH Thermal Controller 00:14.0 USB controller: Intel Corporation Comet Lake USB 3.1 xHCI Host Controller 00:14.2 RAM memory: Intel Corporation Comet Lake PCH Shared SRAM 00:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi 00:16.0 Communication controller: Intel Corporation Comet Lake HECI Controller 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller 00:1c.0 PCI bridge: Intel Corporation Device 06bc (rev f0) 00:1d.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #9 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0685 00:1f.3 Audio device: Intel Corporation Comet Lake PCH cAVS 00:1f.4 SMBus: Intel Corporation Comet Lake PCH SMBus Controller 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake PCH SPI Controller 01:00.0 VGA compatible controller: NVIDIA Corporation GA102 [GeForce RTX 3090] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GA102 High Definition Audio Controller (rev a1) 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 16) 03:00.0 Non-Volatile memory controller: Sandisk Corp WD Black SN750 / PC SN730 NVMe SSD ``` ``` sudo dmesg | grep snd [6.624036] snd_hda_intel :00:1f.3: enabling device (0100 -> 0102) [6.624372] snd_hda_intel
[Desktop-packages] [Bug 1922414] Re: ssh-agent fails to start (has_option: command not found)
This is still broken on impish when running i3 under X11. Oct 22 15:23:39 operations /usr/libexec/gdm-x-session[5615]: /etc/X11/Xsession.d/30x11-common_xresources: line 16: has_option: command not found Oct 22 15:23:39 operations /usr/libexec/gdm-x-session[5646]: /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command not found Oct 22 15:23:39 operations /usr/libexec/gdm-x-session[5658]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in gdm3 package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Invalid Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A 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/gdm3/+bug/1922414/+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 1843588] Re: Nautilus doesn't copy filenames for paste to other programs anymore
Hello Michael, or anyone else affected, Accepted nautilus into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nautilus/1:3.36.3-0ubuntu1.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. ** Changed in: nautilus (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1843588 Title: Nautilus doesn't copy filenames for paste to other programs anymore Status in Nautilus: New Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Status in nautilus package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: New Status in gnome-shell-extension-desktop-icons source package in Focal: New Status in nautilus source package in Focal: Fix Committed Bug description: [Impact] * One of the upstream changes changed behavior of clipboard copying files/directories from nautilus to applications accepting text only (e.g. gnome-terminal). In such case the pasted input is prefixed with: x-special/nautilus-clipboard copy file:// This was not the case in earlier releases and this change has been reverted in later upstream releases. Reverting the problematic commit will fix the usecase reported in this bug (and all applications where copying from Nautilus and pasting the data into a text-based input makes sense), but will break copying to/from Desktop Icons extension. I recommend reporting the Desktop Icons extension issue (present already in every later Ubuntu release) in a separate bug and track the fix there. [Test Plan] 1. Open nautilus. 2. Right-click on any file or directory and select 'Copy' from the context menu. 3. Open gnome-terminal and right-click paste the contents of the clipboard. Expected result: path of the file/directory is pasted in the terminal. Actual result: pasted input is prefixed with "x-special/nautilus-clipboard copy file://" [Where problems could occur] * There are some workarounds listed in the upstream bug so fixing the root cause may break environments with those workarounds in place. * Reverting this change also limits functionality of the desktop icons extension shipped with Ubuntu. Namely: before the new clipboard API is used in desktop-icons (merge requests [1] and [2]) copying and pasting to/from the desktop extension to a nautilus will not be possible via keyboard shortcuts or context menu (dragging and dropping will remain to work). [1] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186 [2] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/195 [Other Info] Original bug description: Until Ubuntu 18.10 Nautilus does copy all selected filenames in simple Text format and this way you cold paste the selected files as a list to other programs: for example into the texteditor gedit. This was a very useful function if you have, for example, to upload a file to webmail or other web-service. You cold copy the file within nautilus and paste it directliy to the selection dialog or webfield to upload the file. Or if you wanted a simple List of all your files in a folder you where able to select all files with nautilus, copy and paste into gedit. This is not possible anymore. The output of natilus looks now like this: x-special/nautilus-clipboard copy file:///home//Schreibtisch/new%20document.txt Until Ubuntu 18.10 this looks like this: /home//Schreibtisch/new document.txt Steps to reproduce: 1. Select files with nautilus 2. Press Ctrl+C 3. open gedit 4. press Ctrl+V ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus
[Desktop-packages] [Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
Is there a risk that applying these changes will regress the behavior of these modems on systems which have NOT applied the firmware updates? Can the testcase include a check for this? ** Changed in: modemmanager (Ubuntu) Status: Fix Committed => Incomplete -- 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: Support manual firmware upgrading for Foxconn and Quectel modems. Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: Incomplete Bug description: [Impact] The modem certification requires that different modem firmware is used for different network carrier. This needs the firmware upgrading capability during the modem certification process. The modem manufacture vendors (Foxconn and Quectel) provided utilities to do modem's firmware upgrading manually.(LP#1943774, LP#1943780) These utilities are verified to be working when the recent versions(> v 1.18.2) of ModemManager are used with. To support manual firmware upgrading on the current Focal release which is using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2. 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 The firmware upgrading was verified using the patched ModemManager v 1.16.6 with the following 2 modems: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem [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. This should not affect existing generic functions and other modems. [Other Info] The firmware and the upgrading utilities 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 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action
For Ubuntu users at least : in the Exec line of the .desktop just replace the beginning /snap/chromium//usr/lib/chromium-browser/chrome by chromium-browser Maybe also look at Web App Manager offered by Mint team. …and now Firefox will be packaged as a snap, what a sad joke. -- 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/1732482 Title: [snap] doesn't properly save desktop files for "create shortcuts" action Status in chromium-browser package in Ubuntu: Triaged Bug description: For chrome apps, the create shortcuts action should create desktop files but it doesn't. I suspect it has something to do with paths.  tracking:candidate installed: 62.0.3202.94 (123) 246MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+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 1827958] Re: [Acer Swift 5 SF514-53T] No sound at all from the inbuilt microphone - since installation of system
I am using Acer Swift SF514-52T. This issue disappeared after I upgraded to Ubuntu 21.10. -- 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/1827958 Title: [Acer Swift 5 SF514-53T] No sound at all from the inbuilt microphone - since installation of system Status in alsa-driver package in Ubuntu: Confirmed Bug description: The inbuilt microphone has never worked on the version of ubuntu on this computer. The hardware works completely fine on other operating systems (Windows). Distribution: Ubuntu 18.04.2 LTS alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.19.21-041921-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lune 1908 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 6 23:54:58 2019 InstallationDate: Installed on 2019-01-06 (120 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 1 0 3 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1273 F pulseaudio lune 1908 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.name: Carlsberg_WL dmi.board.vendor: WL dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.03 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd12/17/2018:svnAcer:pnSwiftSF514-53T:pvrV1.03:rvnWL:rnCarlsberg_WL:rvrV1.03:cvnAcer:ct10:cvrV1.03: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-53T dmi.product.sku: dmi.product.version: V1.03 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1827958/+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 1948486] Re: Keyboard Brightness controll not operable using keyboard or mouse scrollwheel
Thank you for your bug report, the issue is an upstream one could you perhaps also report it on https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/ ? ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- 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/1948486 Title: Keyboard Brightness controll not operable using keyboard or mouse scrollwheel Status in gnome-control-center package in Ubuntu: New Bug description: At the power settings there is a slider for setting the "Keyboard Brightness". My ThinkPad T460s supports three levels: off, dim, bright With clicking and/or dragging I could move the slider to either the left-most, center, or right-most position. However when place the mouse cursor on top of it and use the scroll wheel, I could not move the slider. Same happens when I try to use the cursor keys on the keyboard. My assumption: When using the scroll wheel or the keyboard, the slider is moved by only a small fraction. So if the left-most position is 0% and the right-most is 100%, it will try to increment it by 10%. It does so, but as the only valid values are 0%, 50%, and 100%, it tries to round it to the nearest value, which is 0%, so it jumps back to where it was. You can see the slider briefly jump a short distance but only very briefly, not much more than a flicker. While I could just click/drag with the mouse to change the slider, for some people it might be an accessibility issue and thus I believe this should be fixed somehow. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu5 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: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 22 19:16:07 2021 InstallationDate: Installed on 2019-11-25 (697 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to impish on 2021-10-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1948486/+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 1948498] [NEW] Bluetooth Headset not working when Lenovo P14s AMD Gen1 is connected to Lenovo USB Dock 40AY0090EU
Public bug reported: When the Laptop is not connected to it's dock, the bluethooth headset works. As soon as it is connected to a Lenovo 40AY0090EU Dock, sound stops on the headsets and plays via the display connected via DisplayPort. The headset is still available in sound settings, but even if selected, no sound plays on the headset. If I change the configuration (HSP/A2DP), a short "click" sound can be heard on the headset, so apparently there's still something going on between the laptop and the headsets. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 22 22:04:27 2021 InstallationDate: Installed on 2021-09-29 (23 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1000MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1000MGE:pvrThinkPadP14sGen1:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1:rvnLENOVO:rn20Y1000MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1000MGE dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1948498 Title: Bluetooth Headset not working when Lenovo P14s AMD Gen1 is connected to Lenovo USB Dock 40AY0090EU Status in pulseaudio package in Ubuntu: New Bug description: When the Laptop is not connected to it's dock, the bluethooth headset works. As soon as it is connected to a Lenovo 40AY0090EU Dock, sound stops on the headsets and plays via the display connected via DisplayPort. The headset is still available in sound settings, but even if selected, no sound plays on the headset. If I change the configuration (HSP/A2DP), a short "click" sound can be heard on the headset, so apparently there's still something going on between the laptop and the headsets. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 22 22:04:27 2021 InstallationDate: Installed on 2021-09-29 (23 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1000MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1000MGE:pvrThinkPadP14sGen1:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1:rvnLENOVO:rn20Y1000MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1000MGE dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1948498/+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 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy)
Given that hirsute and impish are both stable releases and focal2impish will be a supported upgrade path when hirsute becomes end of life there is need for an SRU. So could you please add the SRU template information to the bug report? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy) Status in libsignon-glib package in Ubuntu: In Progress Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+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
I'm unsubscribing the ubuntu-sponsors team as this has already been sponsored albeit rejected by Robie. However, the package can still be accepted from the rejected queue once the bug description has been squared away. I've subscribed to the bug and will accept the package once the SRU information has been added. -- 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] [Bug 1941962] Re: pulseaudio crashed with SIGSEGV in XFreeGC() from XCloseDisplay() from pa_x11_wrapper_unref()
Just a heads-up, fix for libx11 issue 139 is now merged upstream https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/84 -- 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/1941962 Title: pulseaudio crashed with SIGSEGV in XFreeGC() from XCloseDisplay() from pa_x11_wrapper_unref() Status in X.Org X server: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/52094416ad4b4132ebf639ec8530fed1fdbac584 crash ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2 Uname: Linux 5.13.13-xanmod1-cacule x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anasc 1719 F pulseaudio /dev/snd/pcmC0D0p: anasc 1719 F...m pulseaudio CasperMD5CheckResult: pass Date: Sat Aug 28 21:00:59 2021 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2021-08-26 (2 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210824) ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal SegvAnalysis: Segfault happened at: 0x7fbcc9d6a8a4 : mov%edx,0x4(%rax) PC (0x7fbcc9d6a8a4) ok source "%edx" ok destination "0x4(%rax)" (0x0004) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: pulseaudio StacktraceTop: XFreeGC () from /lib/x86_64-linux-gnu/libX11.so.6 XCloseDisplay () from /lib/x86_64-linux-gnu/libX11.so.6 pa_x11_wrapper_unref () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-15.0.so module_x11_publish_LTX_pa__done () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-publish.so ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-15.0.so Title: pulseaudio crashed with SIGSEGV in XFreeGC() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 02/05/2021 dmi.bios.release: 15.14 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 86E2 dmi.board.vendor: HP dmi.board.version: 95.36 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.36 dmi.modalias: dmi:bvnInsyde:bvrF.14:bd02/05/2021:br15.14:efr95.36:svnHP:pnHPPavilionLaptop15-cs3xxx:pvrType1ProductConfigId:sku5SU52EA#BH4:rvnHP:rn86E2:rvr95.36:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs3xxx dmi.product.sku: 5SU52EA#BH4 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP separator: To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1941962/+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 1948482] Re: Firefox is wrongly being transitioned from deb to snap
I can confirm the problem, tested in a newly installed budgie VM installed from the 21.10 ISO. ** Package changed: firefox (Ubuntu) => update-manager (Ubuntu) ** Changed in: update-manager (Ubuntu) Importance: Undecided => High ** Changed in: update-manager (Ubuntu) Status: New => Confirmed ** Changed in: update-manager (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- 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/1948482 Title: Firefox is wrongly being transitioned from deb to snap Status in update-manager package in Ubuntu: Confirmed Status in update-manager source package in Impish: New Bug description: Reported here - 6 minutes in https://www.youtube.com/watch?v=NBTws4KoPtg In update manager the transition to snap is being made as an update i.e. this is a fresh 21.10 ubuntu budgie install where firefox is seeded as a deb not a snap ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: firefox 93.0+build1-0ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dad 828 F pulseaudio BuildID: 20210927210923 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: Budgie:GNOME Date: Fri Oct 22 17:46:11 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:360 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2021-10-22 (0 days ago) InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Release amd64 (20211011) IpRoute: default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 169.254.0.0/16 dev enp0s3 scope link metric 1000 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:360 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=93.0/20210927210923 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1948482/+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 1945100]
Comment on attachment 9237836
Bug 1725828 - Preload dependencies for the Widevine CDM when sandboxing it on
Linux.
### ESR Uplift Approval Request
* **If this is not a sec:{high,crit} bug, please state case for ESR
consideration**: Widevine EME and H.264 WebRTC may be broken depending on how
Firefox is built.
* **User impact if declined**: This doesn't affect Mozilla's builds and
probably won't affect them for some time, but downstream builds (already on
some Linux distributions, and probably more and more in the future) won't be
able to use the Widevine plugin for EME or OpenH264 for WebRTC.
* **Fix Landed on Version**: 94
* **Risk to taking this patch**: Low
* **Why is the change risky/not risky? (and alternatives if risky)**: We just
preload some libraries which are normally already loaded; the patch is small
and should have no effect on builds that weren't affected by this bug (like
Mozilla's).
One alternative is to require downstream distributions to apply the patch
themselves if they intend to build ESR91 with a recent glibc, but as far as I
know there's no good way to communicate that to everyone who needs to hear it,
and failures are likely to result in more bug reports for us.
* **String or UUID changes made by this patch**: none
--
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/1945100
Title:
Widevine violates the sandbox and crashes
Status in Mozilla Firefox:
Fix Released
Status in firefox package in Ubuntu:
Fix Released
Bug description:
I just updated for Impish Indri beta release but Firefox's Widevine
is always crashing. When I disable the GMP sandbox (setting the
environment variable MOZ_DISABLE_GMP_SANDBOX to 1) it works fine. I'm
using Firefox 92.0.1 installed via .deb package.
Here is some console logs showing the violations:
➜ firefox --ProfileManager
Gtk-Message: 09:58:02.539: Failed to load module "appmenu-gtk-module"
###!!! [Child][RunMessage] Error: Channel closing: too late to
send/recv, messages will be lost
Gtk-Message: 09:58:10.435: Failed to load module "appmenu-gtk-module"
Sandbox: attempt to open unexpected file /usr/lib/firefox/librt.so.1
Sandbox: attempt to open unexpected file /lib/x86_64-linux-gnu/librt.so.1
Sandbox: attempt to open unexpected file
/lib/x86_64-linux-gnu/glibc-hwcaps/x86-64-v3/librt.so.1
Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
Sandbox: attempt to open unexpected file
/lib/x86_64-linux-gnu/glibc-hwcaps/x86-64-v2/librt.so.1
Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
Sandbox: attempt to open unexpected file
/lib/x86_64-linux-gnu/tls/haswell/x86_64/librt.so.1
Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
Sandbox: attempt to open unexpected file
/lib/x86_64-linux-gnu/tls/haswell/librt.so.1
Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
Sandbox: attempt to open unexpected file
/lib/x86_64-linux-gnu/tls/x86_64/librt.so.1
Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
Sandbox: attempt to open unexpected file /lib/x86_64-linux-gnu/tls/librt.so.1
Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
Sandbox: attempt to open unexpected file
/lib/x86_64-linux-gnu/haswell/x86_64/librt.so.1
Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
Sandbox: attempt to open unexpected file
/lib/x86_64-linux-gnu/haswell/librt.so.1
Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
Sandbox: attempt to open unexpected file
/lib/x86_64-linux-gnu/x86_64/librt.so.1
Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
Sandbox: attempt to open unexpected file /lib/x86_64-linux-gnu/librt.so.1
Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
Sandbox: attempt to open unexpected file
/usr/lib/x86_64-linux-gnu/glibc-hwcaps/x86-64-v3/librt.so.1
Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args
4294967196 140721817045120 140721817045312 0 4294967295
[Desktop-packages] [Bug 1948486] Re: Keyboard Brightness controll not operable using keyboard or mouse scrollwheel
I just figured out that I can move the slider between the left-most and right-most position using the home and end keys on my keyboard, I haven't been able to put it to the middle just using the keyboard. I also consider this not very intuitive. There is a Fn-key combination on the built in keyboard though which controls this brightness level, so it might not be that much of an issue. But there might be other areas where there are similar issues with scrollbars. So it might be a general issue with GTK+ scrollbars or a scrollbar might not be suitable for this setting. Directly above is the control for controlling the built in screen's brightness, but as this has much more granularity, I don't experience this issue there. -- 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/1948486 Title: Keyboard Brightness controll not operable using keyboard or mouse scrollwheel Status in gnome-control-center package in Ubuntu: New Bug description: At the power settings there is a slider for setting the "Keyboard Brightness". My ThinkPad T460s supports three levels: off, dim, bright With clicking and/or dragging I could move the slider to either the left-most, center, or right-most position. However when place the mouse cursor on top of it and use the scroll wheel, I could not move the slider. Same happens when I try to use the cursor keys on the keyboard. My assumption: When using the scroll wheel or the keyboard, the slider is moved by only a small fraction. So if the left-most position is 0% and the right-most is 100%, it will try to increment it by 10%. It does so, but as the only valid values are 0%, 50%, and 100%, it tries to round it to the nearest value, which is 0%, so it jumps back to where it was. You can see the slider briefly jump a short distance but only very briefly, not much more than a flicker. While I could just click/drag with the mouse to change the slider, for some people it might be an accessibility issue and thus I believe this should be fixed somehow. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu5 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: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 22 19:16:07 2021 InstallationDate: Installed on 2019-11-25 (697 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to impish on 2021-10-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1948486/+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 1948486] [NEW] Keyboard Brightness controll not operable using keyboard or mouse scrollwheel
Public bug reported: At the power settings there is a slider for setting the "Keyboard Brightness". My ThinkPad T460s supports three levels: off, dim, bright With clicking and/or dragging I could move the slider to either the left-most, center, or right-most position. However when place the mouse cursor on top of it and use the scroll wheel, I could not move the slider. Same happens when I try to use the cursor keys on the keyboard. My assumption: When using the scroll wheel or the keyboard, the slider is moved by only a small fraction. So if the left-most position is 0% and the right-most is 100%, it will try to increment it by 10%. It does so, but as the only valid values are 0%, 50%, and 100%, it tries to round it to the nearest value, which is 0%, so it jumps back to where it was. You can see the slider briefly jump a short distance but only very briefly, not much more than a flicker. While I could just click/drag with the mouse to change the slider, for some people it might be an accessibility issue and thus I believe this should be fixed somehow. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu5 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: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 22 19:16:07 2021 InstallationDate: Installed on 2019-11-25 (697 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to impish on 2021-10-22 (0 days ago) ** Affects: gnome-control-center (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 gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1948486 Title: Keyboard Brightness controll not operable using keyboard or mouse scrollwheel Status in gnome-control-center package in Ubuntu: New Bug description: At the power settings there is a slider for setting the "Keyboard Brightness". My ThinkPad T460s supports three levels: off, dim, bright With clicking and/or dragging I could move the slider to either the left-most, center, or right-most position. However when place the mouse cursor on top of it and use the scroll wheel, I could not move the slider. Same happens when I try to use the cursor keys on the keyboard. My assumption: When using the scroll wheel or the keyboard, the slider is moved by only a small fraction. So if the left-most position is 0% and the right-most is 100%, it will try to increment it by 10%. It does so, but as the only valid values are 0%, 50%, and 100%, it tries to round it to the nearest value, which is 0%, so it jumps back to where it was. You can see the slider briefly jump a short distance but only very briefly, not much more than a flicker. While I could just click/drag with the mouse to change the slider, for some people it might be an accessibility issue and thus I believe this should be fixed somehow. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu5 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: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 22 19:16:07 2021 InstallationDate: Installed on 2019-11-25 (697 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to impish on 2021-10-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1948486/+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
Here is the output of the commands: $ cat /run/udev/data/b43:0 W:122 I:5238867 E:ID_FS_TYPE= E:SYSTEMD_READY=0 G:systemd Q:systemd V:1 $ cat /run/udev/data/b43:128 W:123 I:5238868 E:ID_FS_TYPE= E:SYSTEMD_READY=0 G:systemd Q:systemd V:1 ** 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 1948482] [NEW] Firefox is wrongly being transitioned from deb to snap
Public bug reported: Reported here - 6 minutes in https://www.youtube.com/watch?v=NBTws4KoPtg In update manager the transition to snap is being made as an update i.e. this is a fresh 21.10 ubuntu budgie install where firefox is seeded as a deb not a snap ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: firefox 93.0+build1-0ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dad 828 F pulseaudio BuildID: 20210927210923 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: Budgie:GNOME Date: Fri Oct 22 17:46:11 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:360 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2021-10-22 (0 days ago) InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Release amd64 (20211011) IpRoute: default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 169.254.0.0/16 dev enp0s3 scope link metric 1000 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:360 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=93.0/20210927210923 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Affects: firefox (Ubuntu Impish) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Description changed: - Reported here - 6 minutes in + Reported here - 6 minutes in https://www.youtube.com/watch?v=NBTws4KoPtg In update manager the transition to snap is being made as an update ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: firefox 93.0+build1-0ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: dad 828 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: dad 828 F pulseaudio BuildID: 20210927210923 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: Budgie:GNOME Date: Fri Oct 22 17:46:11 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:360 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2021-10-22 (0 days ago) InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Release amd64 (20211011) IpRoute: - default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 - 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 - 169.254.0.0/16 dev enp0s3 scope link metric 1000 + default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 + 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 + 169.254.0.0/16 dev enp0s3 scope link metric 1000 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
[Desktop-packages] [Bug 1948356] Re: Firefox 93.0 tabs are not remembered across sessions
Thanks for the report Janne. I just tested this in a clean 21.10 VM with the firefox snap and the Tree Style Tab extension, and in my tests all the tabs are properly restored across browsing sessions. Can you please browse to about:support, copy the raw data and attach it here? Thanks. ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- 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/1948356 Title: Firefox 93.0 tabs are not remembered across sessions Status in firefox package in Ubuntu: Incomplete Bug description: If I close Firefox with a bunch of tabs, then open again, the tabs are gone. I get a list of empty tabs without any actual link to them. Only the last visited site is actually filled with the URL. Up until now Firefox always remembers and restores the list of tabs. I am using Tree Style Tab, but I believe it uses the regular tab list for itself. Ubuntu 21.10 firefox 93.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948356/+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 1947257] Re: Partial profile loss on upgrade from 21.04 to 21.10
> I guess the snap firefox looks for profiles in a different location, > and the profiles aren't transferred from the old deb-firefox location > to the snap-firefox-expected location. They should be, there is code in the snap's launcher to import existing profiles. If you are willing to test again to help us understand the problem, could you please re-install the snap, and run it under one of those non-sudo users from a terminal (snap run firefox), and share the output here? That would be very helpful, 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/1947257 Title: Partial profile loss on upgrade from 21.04 to 21.10 Status in firefox package in Ubuntu: Incomplete Bug description: In the upgrade from 21.04 to 21.10 I noticed it had updated firefox. When restarting some of my profile was kept (themes, addons, etc) but I've noticed my primary window of 50+ tabs was lost. It opened 3 other windows correctly. I tried to find it via "recently closed tabs/windows" but it's not showing up. I have also confirmed there are no duplicate profiles. Silly me assumed it was done correctly and when the upgrade process offered to remove old packages I did so I can't seem to retrieve the old profile. Additional information: lsb_release -rd: Description: Ubuntu 21.10 Release: 21.10 snap package information: snap-id: 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk tracking: latest/stable/ubuntu-21.10 refresh-date: today at 09:00 AEST channels: latest/stable:93.0-1 2021-10-08 (631) 157MB - latest/candidate: 93.0-1 2021-09-28 (631) 157MB - latest/beta: 94.0b5-1 2021-10-13 (650) 157MB - latest/edge: ↑ esr/stable: 78.15.0esr-1 2021-10-04 (637) 148MB - esr/candidate:91.2.0esr-1 2021-09-29 (634) 160MB - esr/beta: ↑ esr/edge: ↑ installed: 93.0-1 (631) 157MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1947257/+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 1905054] Re: Firefox 83 Breaks WebGL
Craig, that is a different problem, tracked by https://bugzilla.mozilla.org/show_bug.cgi?id=1732580, and fixed in the upcoming Firefox 94 (currently in the beta channel). ** Bug watch added: Mozilla Bugzilla #1732580 https://bugzilla.mozilla.org/show_bug.cgi?id=1732580 ** Changed in: firefox (Ubuntu) Status: Fix Committed => Fix Released -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+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 1948355] Re: Firefox settings font size dropdown flashes, hard to select
I am not seeing this here. Could you please run the following command in a terminal to attach additional debug information to this report? Thanks! apport-collect 1948355 ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- 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/1948355 Title: Firefox settings font size dropdown flashes, hard to select Status in firefox package in Ubuntu: Incomplete Bug description: Go to settings, then font, and try to change the font size. The dropdown flashes and disappears, and is very difficult to select. Happens both on the main screen and the "advanced.." screen for all size selectors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948355/+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 1948428] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
** Package changed: ubuntu => nvidia-graphics-drivers-340 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1948428 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: i do not know ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-38-generic Date: Thu Oct 21 17:51:52 2021 InstallationDate: Installed on 2020-07-21 (457 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1948428/+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 1948428] [NEW] nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
You have been subscribed to a public bug: i do not know ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-38-generic Date: Thu Oct 21 17:51:52 2021 InstallationDate: Installed on 2020-07-21 (457 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build https://bugs.launchpad.net/bugs/1948428 You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 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 1948339] Re: Logon screen can be bypassed using various shortcuts
Thanks :) I haven't registered a CVE yet and I'm waiting for final confirmation which components are causing the described issue. Happy to contribute to the ArcticaProject issue tracker directly. As you also mentioned I can confirm that the affected arctica-greeter version is present in the following versions of Ubuntu Mate: Ubuntu Mate 20.10 - Groovy Gorilla Ubuntu Mate 21.04 - Hirsute Hippo Ubuntu Mate 21.10 - Impish Indri It doesn't seem to work for 20.04 - Focal Fossa. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1948339 Title: Logon screen can be bypassed using various shortcuts Status in Ubuntu MATE: New Status in arctica-greeter package in Ubuntu: New Status in lightdm package in Ubuntu: New Status in mate-settings-daemon package in Ubuntu: New Bug description: Hi, my little daughter discovered a logon screen bypass in Ubuntu Mate 21.10 after hitting the keyboard for a while. It turns out that several keyboard shortcuts are allowed while Ubuntu Mate is locked (arctica-greeter): - Mod4 + S (mate-search-tool) - Mod4 + E (Open Caja / File Explorer) - CTRL + Shift + Esc (mate-system-monitor) - PRNT (Screenshot) All of the mentioned shortcuts could be used to spawn a file explorer (Caja) or various other binaries as user "lightdm", who owns the logon screen. Although an interactive terminal like mate-terminal, xterm, lxterm etc. could not be opened directly, there are various options to run commands as the lightdm user, for example by creating a shell script using "caja", and execute it directly using the GUI. I've attached Proof-of-Concept GIFs for all shortcuts mentioned above. There might be additional shortcuts that could be used to achieve the same, however I'm not aware about every shortcut that is configured, but I suppose that the root cause is located somewhere in arctica- greeter, rather than within every single binary launched by shortcuts. The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I haven't tested other versions of Ubuntu Mate yet. Please find additional version details below: $ apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu4 Candidate: 1.30.0-0ubuntu4 Version table: *** 1.30.0-0ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy arctica-greeter arctica-greeter: Installed: 0.99.1.5-2nmu1 Candidate: 0.99.1.5-2nmu1 Version table: *** 0.99.1.5-2nmu1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status Thanks, Basti To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1948339/+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 1843588] Re: Nautilus doesn't copy filenames for paste to other programs anymore
Thanks Dariusz. Are you intending to fix gnome-shell-extension-desktop-icons in Focal also then, to restore the behaviour? If so, then shouldn't these be uploaded together with a Breaks clause to make sure users get both at the same time? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1843588 Title: Nautilus doesn't copy filenames for paste to other programs anymore Status in Nautilus: New Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Status in nautilus package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: New Status in gnome-shell-extension-desktop-icons source package in Focal: New Status in nautilus source package in Focal: New Bug description: [Impact] * One of the upstream changes changed behavior of clipboard copying files/directories from nautilus to applications accepting text only (e.g. gnome-terminal). In such case the pasted input is prefixed with: x-special/nautilus-clipboard copy file:// This was not the case in earlier releases and this change has been reverted in later upstream releases. Reverting the problematic commit will fix the usecase reported in this bug (and all applications where copying from Nautilus and pasting the data into a text-based input makes sense), but will break copying to/from Desktop Icons extension. I recommend reporting the Desktop Icons extension issue (present already in every later Ubuntu release) in a separate bug and track the fix there. [Test Plan] 1. Open nautilus. 2. Right-click on any file or directory and select 'Copy' from the context menu. 3. Open gnome-terminal and right-click paste the contents of the clipboard. Expected result: path of the file/directory is pasted in the terminal. Actual result: pasted input is prefixed with "x-special/nautilus-clipboard copy file://" [Where problems could occur] * There are some workarounds listed in the upstream bug so fixing the root cause may break environments with those workarounds in place. * Reverting this change also limits functionality of the desktop icons extension shipped with Ubuntu. Namely: before the new clipboard API is used in desktop-icons (merge requests [1] and [2]) copying and pasting to/from the desktop extension to a nautilus will not be possible via keyboard shortcuts or context menu (dragging and dropping will remain to work). [1] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186 [2] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/195 [Other Info] Original bug description: Until Ubuntu 18.10 Nautilus does copy all selected filenames in simple Text format and this way you cold paste the selected files as a list to other programs: for example into the texteditor gedit. This was a very useful function if you have, for example, to upload a file to webmail or other web-service. You cold copy the file within nautilus and paste it directliy to the selection dialog or webfield to upload the file. Or if you wanted a simple List of all your files in a folder you where able to select all files with nautilus, copy and paste into gedit. This is not possible anymore. The output of natilus looks now like this: x-special/nautilus-clipboard copy file:///home//Schreibtisch/new%20document.txt Until Ubuntu 18.10 this looks like this: /home//Schreibtisch/new document.txt Steps to reproduce: 1. Select files with nautilus 2. Press Ctrl+C 3. open gedit 4. press Ctrl+V ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.1-0ubuntu0.19.04.0 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 15:06:14 2019 ExecutablePath: /usr/bin/nautilus SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1843588/+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 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()
Could someone having the issue set log-level=debug in /etc/pulse/daemon.conf , restart and add the journalctl log after getting the bug? ** Changed in: pulseaudio (Ubuntu) Status: Triaged => Fix Committed -- 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/1942685 Title: pulseaudio crashed with SIGSEGV in _IceTransClose() Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Committed Bug description: https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e --- Installing Xubuntu Impish daily ISO 04092021 After install I rebooted - applied updates and then rebooted again- the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() ) occurred after logging in. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kx 847 F pulseaudio CasperMD5CheckResult: pass Date: Sat Sep 4 16:43:45 2021 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2021-09-04 (0 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904) ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal Signal: 11 SourcePackage: pulseaudio StacktraceTop: _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6 _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6 IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6 SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6 ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so Title: pulseaudio crashed with SIGSEGV in _IceTransClose() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 12/23/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN51WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V14-IIL dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL: dmi.product.family: V14-IIL dmi.product.name: 82C4 dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL dmi.product.version: Lenovo V14-IIL dmi.sys.vendor: LENOVO separator: To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1942685/+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 1948438] [NEW] Printer kan niet worden gestart. Controleer de configuratie van uw printer
Public bug reported: My Canon MP499 printer is recognized, but if i try to use it in LibreOffice Writer, a message appears (see above). Using translate, it shows this message: Printer cannot be started. Check your printer's configuration fred@fred-Latitude-E6430:~$ lpstat fred@fred-Latitude-E6430:~$ lpstat -t scheduler is running no system default destination device for DCP-L3550CDW: dnssd://Brother%20DCP-L3550CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4dc9c43 device for MP495-series: usb://Canon/MP495%20series?serial=24F65A=1 DCP-L3550CDW accepting requests since vr 23 jul 2021 12:55:49 CEST MP495-series accepting requests since vr 22 okt 2021 10:58:01 CEST printer DCP-L3550CDW is idle. enabled since vr 23 jul 2021 12:55:49 CEST printer MP495-series is idle. enabled since vr 22 okt 2021 10:58:01 CEST fred@fred-Latitude-E6430:~$ sudo service cups status [sudo] wachtwoord voor fred: ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: > Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago TriggeredBy: ● cups.path ● cups.socket Docs: man:cupsd(8) Main PID: 977 (cupsd) Tasks: 3 (limit: 9421) Memory: 24.9M CGroup: /system.slice/cups.service ├─ 977 /usr/sbin/cupsd -l ├─2129 /usr/lib/cups/notifier/dbus dbus:// └─4449 /usr/lib/cups/notifier/dbus dbus:// okt 22 10:56:11 fred-Latitude-E6430 systemd[1]: Started CUPS Scheduler. okt 22 10:57:39 fred-Latitude-E6430 /hpfax[2022]: [2022]: error: Failed to crea> lines 1-16/16 (END)...skipping... ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: > Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago TriggeredBy: ● cups.path ● cups.socket Docs: man:cupsd(8) Main PID: 977 (cupsd) Tasks: 3 (limit: 9421) Memory: 24.9M CGroup: /system.slice/cups.service ├─ 977 /usr/sbin/cupsd -l ├─2129 /usr/lib/cups/notifier/dbus dbus:// └─4449 /usr/lib/cups/notifier/dbus dbus:// okt 22 10:56:11 fred-Latitude-E6430 systemd[1]: Started CUPS Scheduler. okt 22 10:57:39 fred-Latitude-E6430 /hpfax[2022]: [2022]: error: Failed to crea> ~ ~ ~ ~ ~ ~ ~ ~ lines 1-16/16 (END)...skipping... ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: > Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago TriggeredBy: ● cups.path ● cups.socket Docs: man:cupsd(8) Main PID: 977 (cupsd) Tasks: 3 (limit: 9421) Memory: 24.9M CGroup: /system.slice/cups.service ├─ 977 /usr/sbin/cupsd -l ├─2129 /usr/lib/cups/notifier/dbus dbus:// └─4449 /usr/lib/cups/notifier/dbus dbus:// okt 22 10:56:11 fred-Latitude-E6430 systemd[1]: Started CUPS Scheduler. okt 22 10:57:39 fred-Latitude-E6430 /hpfax[2022]: [2022]: error: Failed to crea> ~ ~ ~ ~ ~ ~ ~ ~ ~ lines 1-16/16 (END)...skipping... ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: > Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago TriggeredBy: ● cups.path ● cups.socket Docs: man:cupsd(8) Main PID: 977 (cupsd) Tasks: 3 (limit: 9421) Memory: 24.9M CGroup: /system.slice/cups.service ├─ 977 /usr/sbin/cupsd -l ├─2129 /usr/lib/cups/notifier/dbus dbus:// └─4449 /usr/lib/cups/notifier/dbus dbus:// okt 22 10:56:11 fred-Latitude-E6430 systemd[1]: Started CUPS Scheduler. okt 22 10:57:39 fred-Latitude-E6430 /hpfax[2022]: [2022]: error: Failed to crea> ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ lines 1-16/16 (END)...skipping... ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: > Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago TriggeredBy: ● cups.path ● cups.socket Docs: man:cupsd(8) Main PID: 977 (cupsd) Tasks: 3 (limit: 9421) Memory: 24.9M CGroup: /system.slice/cups.service ├─ 977 /usr/sbin/cupsd -l ├─2129 /usr/lib/cups/notifier/dbus dbus:// └─4449 /usr/lib/cups/notifier/dbus dbus:// okt 22 10:56:11 fred-Latitude-E6430 systemd[1]: Started CUPS Scheduler. okt 22 10:57:39 fred-Latitude-E6430 /hpfax[2022]: [2022]: error: Failed to crea> ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ lines 1-16/16 (END)...skipping... ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: > Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago TriggeredBy: ● cups.path ● cups.socket Docs: man:cupsd(8) Main PID: 977 (cupsd) Tasks: 3 (limit: 9421) Memory: 24.9M CGroup: /system.slice/cups.service ├─ 977
[Desktop-packages] [Bug 1936826]
*** Bug 2016353 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1936826
Title:
gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
[st-focus-manager.c:199]
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
Fix Released
Status in gnome-shell package in Fedora:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/a7fed12980ff951be9a10c4f2e04d99a23b010ae
---
Testing daily Ubuntu Impish ISO 2021-07-19
Test machine : Dell [Latitude] 7280 (i5-7300U,
Received the error message - Ubuntu has experienced an internal error
...do you want to send ...etc, etc.
This bug occurred when I was scrolling up and down on the "Settings"
app and selected "Appearance".
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: gnome-shell 40.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 19 12:15:54 2021
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'40.2'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'is')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2021-07-19 (0 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210719)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
st_focus_manager_remove_group () from /usr/lib/gnome-shell/libst-1.0.so
g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1936826/+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 1936826]
*** Bug 2016444 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1936826
Title:
gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
[st-focus-manager.c:199]
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
Fix Released
Status in gnome-shell package in Fedora:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/a7fed12980ff951be9a10c4f2e04d99a23b010ae
---
Testing daily Ubuntu Impish ISO 2021-07-19
Test machine : Dell [Latitude] 7280 (i5-7300U,
Received the error message - Ubuntu has experienced an internal error
...do you want to send ...etc, etc.
This bug occurred when I was scrolling up and down on the "Settings"
app and selected "Appearance".
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: gnome-shell 40.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 19 12:15:54 2021
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'40.2'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'is')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2021-07-19 (0 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210719)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
st_focus_manager_remove_group () from /usr/lib/gnome-shell/libst-1.0.so
g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1936826/+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 1936826]
*** Bug 2016329 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1936826
Title:
gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
[st-focus-manager.c:199]
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
Fix Released
Status in gnome-shell package in Fedora:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/a7fed12980ff951be9a10c4f2e04d99a23b010ae
---
Testing daily Ubuntu Impish ISO 2021-07-19
Test machine : Dell [Latitude] 7280 (i5-7300U,
Received the error message - Ubuntu has experienced an internal error
...do you want to send ...etc, etc.
This bug occurred when I was scrolling up and down on the "Settings"
app and selected "Appearance".
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: gnome-shell 40.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 19 12:15:54 2021
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'40.2'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'is')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2021-07-19 (0 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210719)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
st_focus_manager_remove_group () from /usr/lib/gnome-shell/libst-1.0.so
g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1936826/+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 1948355] Re: Firefox settings font size dropdown flashes, hard to select
Firefox 93.0-1 Ubuntu 21.10 -- 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/1948355 Title: Firefox settings font size dropdown flashes, hard to select Status in firefox package in Ubuntu: New Bug description: Go to settings, then font, and try to change the font size. The dropdown flashes and disappears, and is very difficult to select. Happens both on the main screen and the "advanced.." screen for all size selectors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948355/+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 1948355] Re: Firefox settings font size dropdown flashes, hard to select
Firefox 91.0-1 Ubuntu 21.10 -- 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/1948355 Title: Firefox settings font size dropdown flashes, hard to select Status in firefox package in Ubuntu: New Bug description: Go to settings, then font, and try to change the font size. The dropdown flashes and disappears, and is very difficult to select. Happens both on the main screen and the "advanced.." screen for all size selectors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948355/+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 1948339] Re: Logon screen can be bypassed using various shortcuts
Upstream is now informed via https://github.com/ArcticaProject/arctica-greeter/issues/28 . I cited this bug there. Bastian Kanbach (bkanbach), you are welcome to add more comments there. ** Bug watch added: github.com/ArcticaProject/arctica-greeter/issues #28 https://github.com/ArcticaProject/arctica-greeter/issues/28 ** Bug watch added: github.com/canonical/lightdm/issues #214 https://github.com/canonical/lightdm/issues/214 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1948339 Title: Logon screen can be bypassed using various shortcuts Status in Ubuntu MATE: New Status in arctica-greeter package in Ubuntu: New Status in lightdm package in Ubuntu: New Status in mate-settings-daemon package in Ubuntu: New Bug description: Hi, my little daughter discovered a logon screen bypass in Ubuntu Mate 21.10 after hitting the keyboard for a while. It turns out that several keyboard shortcuts are allowed while Ubuntu Mate is locked (arctica-greeter): - Mod4 + S (mate-search-tool) - Mod4 + E (Open Caja / File Explorer) - CTRL + Shift + Esc (mate-system-monitor) - PRNT (Screenshot) All of the mentioned shortcuts could be used to spawn a file explorer (Caja) or various other binaries as user "lightdm", who owns the logon screen. Although an interactive terminal like mate-terminal, xterm, lxterm etc. could not be opened directly, there are various options to run commands as the lightdm user, for example by creating a shell script using "caja", and execute it directly using the GUI. I've attached Proof-of-Concept GIFs for all shortcuts mentioned above. There might be additional shortcuts that could be used to achieve the same, however I'm not aware about every shortcut that is configured, but I suppose that the root cause is located somewhere in arctica- greeter, rather than within every single binary launched by shortcuts. The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I haven't tested other versions of Ubuntu Mate yet. Please find additional version details below: $ apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu4 Candidate: 1.30.0-0ubuntu4 Version table: *** 1.30.0-0ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy arctica-greeter arctica-greeter: Installed: 0.99.1.5-2nmu1 Candidate: 0.99.1.5-2nmu1 Version table: *** 0.99.1.5-2nmu1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status Thanks, Basti To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1948339/+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 1948339] Re: Logon screen can be bypassed using various shortcuts
Lightdm - https://github.com/canonical/lightdm/issues/214 . -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1948339 Title: Logon screen can be bypassed using various shortcuts Status in Ubuntu MATE: New Status in arctica-greeter package in Ubuntu: New Status in lightdm package in Ubuntu: New Status in mate-settings-daemon package in Ubuntu: New Bug description: Hi, my little daughter discovered a logon screen bypass in Ubuntu Mate 21.10 after hitting the keyboard for a while. It turns out that several keyboard shortcuts are allowed while Ubuntu Mate is locked (arctica-greeter): - Mod4 + S (mate-search-tool) - Mod4 + E (Open Caja / File Explorer) - CTRL + Shift + Esc (mate-system-monitor) - PRNT (Screenshot) All of the mentioned shortcuts could be used to spawn a file explorer (Caja) or various other binaries as user "lightdm", who owns the logon screen. Although an interactive terminal like mate-terminal, xterm, lxterm etc. could not be opened directly, there are various options to run commands as the lightdm user, for example by creating a shell script using "caja", and execute it directly using the GUI. I've attached Proof-of-Concept GIFs for all shortcuts mentioned above. There might be additional shortcuts that could be used to achieve the same, however I'm not aware about every shortcut that is configured, but I suppose that the root cause is located somewhere in arctica- greeter, rather than within every single binary launched by shortcuts. The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I haven't tested other versions of Ubuntu Mate yet. Please find additional version details below: $ apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu4 Candidate: 1.30.0-0ubuntu4 Version table: *** 1.30.0-0ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy arctica-greeter arctica-greeter: Installed: 0.99.1.5-2nmu1 Candidate: 0.99.1.5-2nmu1 Version table: *** 0.99.1.5-2nmu1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status Thanks, Basti To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1948339/+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 1948410] [NEW] [nvidia] Software cursor in Wayland sessions (EGLStreams)
Public bug reported: Software cursor used in Wayland sessions (EGLStreams). To see it just add this to /etc/environment: CLUTTER_PAINT=damage-region and reboot. ** Affects: mutter Importance: Unknown Status: Unknown ** Affects: mutter (Ubuntu) Importance: Low Status: Triaged ** Tags: impish nvidia nvidia-drm.modeset performance ** Changed in: mutter (Ubuntu) Importance: Undecided => Low ** Changed in: mutter (Ubuntu) Status: New => Triaged ** Tags added: impish ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1980 https://gitlab.gnome.org/GNOME/mutter/-/issues/1980 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1980 Importance: Unknown Status: Unknown -- 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/1948410 Title: [nvidia] Software cursor in Wayland sessions (EGLStreams) Status in Mutter: Unknown Status in mutter package in Ubuntu: Triaged Bug description: Software cursor used in Wayland sessions (EGLStreams). To see it just add this to /etc/environment: CLUTTER_PAINT=damage-region and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948410/+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 1905054] Re: Firefox 83 Breaks WebGL
I upgraded my PC from 21.04 to 21.10. I found that WebGL doesn't work in the snap firefox that 21.10 installed. I uninstalled the snap firefox and installed the deb firefox via apt. That fixed the WebGL issue. -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+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
