[Touch-packages] [Bug 1967648] Re: lubuntu jammy - `ubuntu-bug lxqt-config` isn't opening firefox
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1967648 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1967648 Title: lubuntu jammy - `ubuntu-bug lxqt-config` isn't opening firefox Status in apport package in Ubuntu: New Bug description: /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?' Lubuntu jammy install test on dell optiplex 780 I adjusted displays as mouse-movements were annoying me, noticed an issue thus filed a bug report using `ubuntu-bug lxqt-config` ** expected output on executing `ubuntu-but lxqt-config` I expected firefox to start ** actual output --- lubuntu@lubuntu:~$ ubuntu-bug lxqt-config *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ... *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (19.6 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 98% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/lxqt- config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?' --- ie. `firefox` doesn't start as it's now a snap package first attempt to file `ubuntu-bug apport` ended up with --- *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/lxqt- config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?' lubuntu@lubuntu:~$ --- ** other notes - I don't know if this only impacts lubuntu, or others too - I've not (yet) looked for other/existing bugs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu80 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: LXQt Date: Sun Apr 3 12:09:05 2022 LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220402) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1967648/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1967648] Re: lubuntu jammy - `ubuntu-bug lxqt-config` isn't opening firefox
** Description changed: + /usr/bin/xdg-open: 882: firefox: not found + /usr/bin/xdg-open: 882: firefox: not found + xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?' + + Lubuntu jammy install test on dell optiplex 780 I adjusted displays as mouse-movements were annoying me, noticed an issue thus filed a bug report using `ubuntu-bug lxqt-config` ** expected output on executing `ubuntu-but lxqt-config` I expected firefox to start ** actual output --- lubuntu@lubuntu:~$ ubuntu-bug lxqt-config *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ... *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: - S: Send report (19.6 KB) - V: View report - K: Keep report file for sending later or copying to somewhere else - I: Cancel and ignore future crashes of this program version - C: Cancel + S: Send report (19.6 KB) + V: View report + K: Keep report file for sending later or copying to somewhere else + I: Cancel and ignore future crashes of this program version + C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 98% *** To continue, you must visit the following URL: - https://bugs.launchpad.net/ubuntu/+source/lxqt- + https://bugs.launchpad.net/ubuntu/+source/lxqt- config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4? You can launch a browser now, or copy this URL into a browser on another computer. - Choices: - 1: Launch a browser now - C: Cancel + 1: Launch a browser now + C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found - /usr/bin/xdg-open: 882: firefox: not found - xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?' + /usr/bin/xdg-open: 882: firefox: not found + xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?' --- ie. `firefox` doesn't start as it's now a snap package first attempt to file `ubuntu-bug apport` ended up with --- *** To continue, you must visit the following URL: - https://bugs.launchpad.net/ubuntu/+source/lxqt- + https://bugs.launchpad.net/ubuntu/+source/lxqt- config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4? You can launch a browser now, or copy this URL into a browser on another computer. - Choices: - 1: Launch a browser now - C: Cancel + 1: Launch a browser now + C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found - /usr/bin/xdg-open: 882: firefox: not found - xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?' + /usr/bin/xdg-open: 882: firefox: not found + xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?' lubuntu@lubuntu:~$ --- - ** other notes - I don't know if this only impacts lubuntu, or others too - I've not (yet) looked for other/existing bugs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu80 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: LXQt Date: Sun Apr 3 12:09:05 2022 LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220402) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1967648 Title: lubuntu jammy - `ubuntu-bug lxqt-config` isn't opening firefox Status in apport package in Ubuntu: New Bug description: /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebu
[Touch-packages] [Bug 1967651] Re: jammy beta xorg no kb / mouse
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1967651 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1967651 Title: jammy beta xorg no kb / mouse Status in xorg-server package in Ubuntu: New Bug description: after updating to jammy beta, xorg does not work for any desktop, in every case the desktop comes up, but there is no response to keyboard or mouse (not even numlock). I tried unplugging and replugging the devices with no luck. All desktops do 'work' in the wayland version, but the display flashes frequently, showing parts of other windows ubuntu=bug gathers information, but does not open the browser window after reporting that it's uploaded the data. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1967651/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1967651] [NEW] jammy beta xorg no kb / mouse
Public bug reported: after updating to jammy beta, xorg does not work for any desktop, in every case the desktop comes up, but there is no response to keyboard or mouse (not even numlock). I tried unplugging and replugging the devices with no luck. All desktops do 'work' in the wayland version, but the display flashes frequently, showing parts of other windows ubuntu=bug gathers information, but does not open the browser window after reporting that it's uploaded the data. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1967651 Title: jammy beta xorg no kb / mouse Status in xorg package in Ubuntu: New Bug description: after updating to jammy beta, xorg does not work for any desktop, in every case the desktop comes up, but there is no response to keyboard or mouse (not even numlock). I tried unplugging and replugging the devices with no luck. All desktops do 'work' in the wayland version, but the display flashes frequently, showing parts of other windows ubuntu=bug gathers information, but does not open the browser window after reporting that it's uploaded the data. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1967651/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1967648] [NEW] lubuntu jammy - `ubuntu-bug lxqt-config` isn't opening firefox
Public bug reported: Lubuntu jammy install test on dell optiplex 780 I adjusted displays as mouse-movements were annoying me, noticed an issue thus filed a bug report using `ubuntu-bug lxqt-config` ** expected output on executing `ubuntu-but lxqt-config` I expected firefox to start ** actual output --- lubuntu@lubuntu:~$ ubuntu-bug lxqt-config *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ... *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (19.6 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 98% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/lxqt- config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?' --- ie. `firefox` doesn't start as it's now a snap package first attempt to file `ubuntu-bug apport` ended up with --- *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/lxqt- config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?' lubuntu@lubuntu:~$ --- ** other notes - I don't know if this only impacts lubuntu, or others too - I've not (yet) looked for other/existing bugs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu80 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: LXQt Date: Sun Apr 3 12:09:05 2022 LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220402) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1967648 Title: lubuntu jammy - `ubuntu-bug lxqt-config` isn't opening firefox Status in apport package in Ubuntu: New Bug description: Lubuntu jammy install test on dell optiplex 780 I adjusted displays as mouse-movements were annoying me, noticed an issue thus filed a bug report using `ubuntu-bug lxqt-config` ** expected output on executing `ubuntu-but lxqt-config` I expected firefox to start ** actual output --- lubuntu@lubuntu:~$ ubuntu-bug lxqt-config *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ... *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (19.6 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 98% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/lxqt- config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4? You can launch
[Touch-packages] [Bug 1452115] Re: Python interpreter binary is not compiled as PIE
This bug was fixed in the package python3.10 - 3.10.4-3 --- python3.10 (3.10.4-3) unstable; urgency=medium * Build a python3.10-nopie package, diverting the python3.10 executable. * Build the python3.10 interpreter with PIE enabled. Closes: ##919134. LP: #1452115. * Fix build on ia64 (Adrian Glaubitz). Closes: #1008576. -- Matthias Klose Sat, 02 Apr 2022 11:04:19 +0200 ** Changed in: python3.10 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1452115 Title: Python interpreter binary is not compiled as PIE Status in Python: New Status in python2.7 package in Ubuntu: Fix Released Status in python3.10 package in Ubuntu: Fix Released Status in python3.4 package in Ubuntu: Fix Released Status in python3.6 package in Ubuntu: Confirmed Status in python3.7 package in Ubuntu: Confirmed Status in python3.8 package in Ubuntu: Confirmed Status in python3.9 package in Ubuntu: New Status in python3.7 package in Debian: New Status in python3.8 package in Debian: New Bug description: The python2.7 binary (installed at /usr/bin/python2.7; package version 2.7.6-8) is not compiled as a position independent executable (PIE). It appears that the python compilation process is somewhat arcane and the hardening wrapper probably doesn't do the trick for it. This is incredibly dangerous as it means that any vulnerability within a native module (e.g. ctypes-based), or within python itself will expose an incredibly large amount of known memory contents at known addresses (including a large number of dangerous instruction groupings). This enables ROP-based (https://en.wikipedia.org/wiki/Return-oriented_programming) to abuse the interpreter itself to bypass non-executable page protections. I have put together an example vulnerable C shared object (with a buffer overflow) accessed via python through the ctypes interface as an example. This uses a single ROP "gadget" on top of using the known PLT location for system(3) (https://en.wikipedia.org/wiki/Return-to-libc_attack) to call "id". The example code is accessible at: - https://gist.github.com/ChaosData/ae6076cb1c3cc7b0a367 I'm not exactly familiar enough with the python build process to say where exactly an -fPIE needs to be injected into a script/makefile, but I feel that given the perceived general preference for ctypes- based modules over python written ones, as the native code implementations tend to be more performant, this feels like a large security hole within the system. Given the nature of this "issue," I'm not 100% sure of where it is best reported, but from what I can tell, this conflicts with the Ubuntu hardening features and is definitely exploitable should a native module contain a sufficiently exploitable vulnerability that allows for control of the instruction register. To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/1452115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903516] Re: aborted (core dumped) when using ConnectTimeout > 2147483
** Merge proposal linked: https://code.launchpad.net/~sergiodj/ubuntu/+source/openssh/+git/openssh/+merge/418102 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1903516 Title: aborted (core dumped) when using ConnectTimeout > 2147483 Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Bionic: Triaged Status in openssh source package in Focal: Triaged Status in openssh source package in Impish: Triaged Status in openssh source package in Jammy: Fix Released Bug description: [Impact] Setting ConnectTimeout to a value higher than INT_MAX/1000 causes the ssh client to crash. This happens due to an integer overflow which was fixed upstream with the patch being proposed for this SRU, which caps the effective value for that option at INT_MAX/1000. While use cases triggering the bug may be uncommon, the patch is straightforward and the fix could be staged for the next time an upload is needed. [Test Plan] Running ssh -o "ConnectTimeout=$(perl -e 'use POSIX; my $max = int(POSIX::INT_MAX/1000)+1; print "$max\n";')" localhost triggers the error. In this case, the ssh client will crash and Aborted will be printed to stderr. By applying the proposed fix, running the same command should allow the ssh connection to proceed to the authentication steps. [Where problems could occur] Most problems would manifest due to rebuilding the package (e.g., dependency changes). Since this proposal is to stage these SRUs, such risk is being deferred to be shared with the next, more critical, upload. [Other Info] All the SRUs proposed here should be staged due to the low priority nature of the bug. [Original bug report] The ssh client fails with the message "Aborted (core dumped)" when setting the ConnectTimeout to 2147484 or higher. lsb_release: Linux Mint 20 (but also tested this on latest ubuntu:20.04 docker container) openssh-client version: 1:8.2p1-4ubuntu0.1 I expected that either the connect timeout would be used correctly, or that it would fail with a proper error message saying the connect timeout can't be higher than 2147483. What happened: $ ssh -o "ConnectTimeout=2147484" localhost Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1903516/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903516] Re: aborted (core dumped) when using ConnectTimeout > 2147483
** Merge proposal linked: https://code.launchpad.net/~sergiodj/ubuntu/+source/openssh/+git/openssh/+merge/418101 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1903516 Title: aborted (core dumped) when using ConnectTimeout > 2147483 Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Bionic: Triaged Status in openssh source package in Focal: Triaged Status in openssh source package in Impish: Triaged Status in openssh source package in Jammy: Fix Released Bug description: [Impact] Setting ConnectTimeout to a value higher than INT_MAX/1000 causes the ssh client to crash. This happens due to an integer overflow which was fixed upstream with the patch being proposed for this SRU, which caps the effective value for that option at INT_MAX/1000. While use cases triggering the bug may be uncommon, the patch is straightforward and the fix could be staged for the next time an upload is needed. [Test Plan] Running ssh -o "ConnectTimeout=$(perl -e 'use POSIX; my $max = int(POSIX::INT_MAX/1000)+1; print "$max\n";')" localhost triggers the error. In this case, the ssh client will crash and Aborted will be printed to stderr. By applying the proposed fix, running the same command should allow the ssh connection to proceed to the authentication steps. [Where problems could occur] Most problems would manifest due to rebuilding the package (e.g., dependency changes). Since this proposal is to stage these SRUs, such risk is being deferred to be shared with the next, more critical, upload. [Other Info] All the SRUs proposed here should be staged due to the low priority nature of the bug. [Original bug report] The ssh client fails with the message "Aborted (core dumped)" when setting the ConnectTimeout to 2147484 or higher. lsb_release: Linux Mint 20 (but also tested this on latest ubuntu:20.04 docker container) openssh-client version: 1:8.2p1-4ubuntu0.1 I expected that either the connect timeout would be used correctly, or that it would fail with a proper error message saying the connect timeout can't be higher than 2147483. What happened: $ ssh -o "ConnectTimeout=2147484" localhost Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1903516/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966418] Re: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc)
** Summary changed: - [jammy regression] Evolution does not display message content anymore + [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc) Status in Gnome DevHelp: Invalid Status in Mesa: Unknown Status in Webkit: Unknown Status in epiphany-browser package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in liferea package in Ubuntu: Invalid Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/devhelp/+bug/1966418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1967640] [NEW] package udev 249.11-0ubuntu2 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1
Public bug reported: I don't know anything Ubuntu just told me there was a bug and I just sent a report ProblemType: Package DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CustomUdevRuleFiles: 70-snap.firefox.rules 70-snap.snapd.rules Date: Sun Mar 27 21:35:10 2022 Df: Sys. de fichiers blocs de 1K Utilisé Disponible Uti% Monté sur tmpfs 340860 1108 339752 1% /run /dev/sda6 402122632 115920796 265959416 31% / tmpfs1704296 01704296 0% /dev/shm tmpfs 5120 0 5120 0% /run/lock ErrorMessage: installed udev package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-03-27 (6 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=4082b1cb-5861-4f76-b7d1-278936a44624 ro quiet splash vt.handoff=7 Python3Details: /usr/local/bin/python3.10, Python 3.10.4, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu1 apt 2.4.3 SourcePackage: systemd Title: package udev 249.11-0ubuntu2 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/03/2017 dmi.bios.release: 4.6 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.name: 81B3 dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.30:bd11/03/2017:br4.6:svnHP:pn:pvr:rvnHP:rn81B3:rvr00:cvnHP:ct3:cvr:sku: dmi.product.family: 103C_53316J dmi.sys.vendor: HP ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1967640 Title: package udev 249.11-0ubuntu2 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: I don't know anything Ubuntu just told me there was a bug and I just sent a report ProblemType: Package DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CustomUdevRuleFiles: 70-snap.firefox.rules 70-snap.snapd.rules Date: Sun Mar 27 21:35:10 2022 Df: Sys. de fichiers blocs de 1K Utilisé Disponible Uti% Monté sur tmpfs 340860 1108 339752 1% /run /dev/sda6 402122632 115920796 265959416 31% / tmpfs1704296 01704296 0% /dev/shm tmpfs 5120 0 5120 0% /run/lock ErrorMessage: installed udev package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-03-27 (6 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=4082b1cb-5861-4f76-b7d1-278936a44624 ro quiet splash vt.handoff=7 Python3Details: /usr/local/bin/python3.10, Python 3.10.4, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu1 apt 2.4.3 SourcePackage: systemd Title: package udev 249.11-0ubuntu2 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/03/2017 dmi.bios.release: 4.6 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.name: 81B3 dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.30:bd11/03/2017:br4.6:svnHP:pn:pvr:rvnHP:rn81B3:rvr00:cvnHP:ct3:cvr:sku: dmi.product.family: 103C_53316J dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1967640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1913977] Re: Bad sound quality (no bass) on Thinkpad T490s
I am having the same issue on my Thinkpad T490. Very tinny/high treble audio with no bass. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1913977 Title: Bad sound quality (no bass) on Thinkpad T490s Status in alsa-driver package in Ubuntu: New Bug description: Sound works on with 20.04 on the Thinkpad T490s, but sound quality is noticeably worse than on Windows. It looks like the same bug here: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hmahmood 1360 F pulseaudio /dev/snd/pcmC0D0p: hmahmood 1360 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 31 19:14:57 2021 InstallationDate: Installed on 2021-01-30 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [20NYS83800, Realtek ALC257, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2020 dmi.bios.release: 1.70 dmi.bios.vendor: LENOVO dmi.bios.version: N2JET92W (1.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NYS83800 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.20 dmi.modalias: dmi:bvnLENOVO:bvrN2JET92W(1.70):bd08/31/2020:br1.70:efr1.20:svnLENOVO:pn20NYS83800:pvrThinkPadT490s:rvnLENOVO:rn20NYS83800:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490s dmi.product.name: 20NYS83800 dmi.product.sku: LENOVO_MT_20NY_BU_Think_FM_ThinkPad T490s dmi.product.version: ThinkPad T490s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1913977/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876335] Re: package lvm2 2.03.02-2ubuntu6 failed to install/upgrade: podproces zainstalowany pakiet lvm2 skrypt post-installation zwrócił kod błędu 1
I am checked apt --simulate purge lvm2 because there was no dependencies i went with purge apt purge lvm2; apt install lvm2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1876335 Title: package lvm2 2.03.02-2ubuntu6 failed to install/upgrade: podproces zainstalowany pakiet lvm2 skrypt post-installation zwrócił kod błędu 1 Status in lvm2 package in Ubuntu: New Bug description: Nie mam pojęcia o co chodzi. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: lvm2 2.03.02-2ubuntu6 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 AptOrdering: ovmf:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri May 1 15:20:02 2020 DpkgHistoryLog: Start-Date: 2020-05-01 15:19:54 Commandline: /usr/bin/unattended-upgrade Upgrade: ovmf:amd64 (0~20190606.20d2e5a1-2ubuntu1, 0~20190606.20d2e5a1-2ubuntu1.1) ErrorMessage: podproces zainstalowany pakiet lvm2 skrypt post-installation zwrócił kod błędu 1 InstallationDate: Installed on 2020-04-16 (15 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: lvm2 Title: package lvm2 2.03.02-2ubuntu6 failed to install/upgrade: podproces zainstalowany pakiet lvm2 skrypt post-installation zwrócił kod błędu 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1876335/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876335] Re: package lvm2 2.03.02-2ubuntu6 failed to install/upgrade: podproces zainstalowany pakiet lvm2 skrypt post-installation zwrócił kod błędu 1
`Konfigurowanie pakietu lvm2 (2.03.07-1ubuntu1) ... update-initramfs: deferring update (trigger activated) Failed to restart lvm2-lvmpolld.service: Unit lvm2-lvmpolld.socket is masked. invoke-rc.d: initscript lvm2-lvmpolld, action "restart" failed. ● lvm2-lvmpolld.service - LVM2 poll daemon Loaded: loaded (/lib/systemd/system/lvm2-lvmpolld.service; static; vendor preset: enabled) Active: inactive (dead) Docs: man:lvmpolld(8) dpkg: błąd przetwarzania pakietu lvm2 (--configure): podproces zainstalowany pakiet lvm2 skrypt post-installation zwrócił kod błędu 1` *uname -r :* 5.4.0-107-generic *lsb_release -crid :* Distributor ID:Ubuntu Description: Ubuntu 20.04.4 LTS Release: 20.04 Codename: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1876335 Title: package lvm2 2.03.02-2ubuntu6 failed to install/upgrade: podproces zainstalowany pakiet lvm2 skrypt post-installation zwrócił kod błędu 1 Status in lvm2 package in Ubuntu: New Bug description: Nie mam pojęcia o co chodzi. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: lvm2 2.03.02-2ubuntu6 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 AptOrdering: ovmf:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri May 1 15:20:02 2020 DpkgHistoryLog: Start-Date: 2020-05-01 15:19:54 Commandline: /usr/bin/unattended-upgrade Upgrade: ovmf:amd64 (0~20190606.20d2e5a1-2ubuntu1, 0~20190606.20d2e5a1-2ubuntu1.1) ErrorMessage: podproces zainstalowany pakiet lvm2 skrypt post-installation zwrócił kod błędu 1 InstallationDate: Installed on 2020-04-16 (15 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: lvm2 Title: package lvm2 2.03.02-2ubuntu6 failed to install/upgrade: podproces zainstalowany pakiet lvm2 skrypt post-installation zwrócił kod błędu 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1876335/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966221] Re: gnome-extensions-app crashes with "Segmentation fault (core dumped)"
This bug was fixed in the package mesa - 22.0.1-1ubuntu1 --- mesa (22.0.1-1ubuntu1) jammy; urgency=medium * Merge from Debian. * Drop patch for GFX1036, upstream. * control: Actually recommend libgl1-amber-dri. * enable-dg2.diff: Fixed to detect DG2 platform. -- Timo Aaltonen Wed, 30 Mar 2022 11:59:33 +0300 ** Changed in: mesa (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966221 Title: gnome-extensions-app crashes with "Segmentation fault (core dumped)" Status in Mesa: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Bug description: when I use the command "gnome-extensions-app" in command line ,it will crash and report "Segmentation fault (core dumped)" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-prefs 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 22:32:21 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-09 (42 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1966221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1967595] Re: Display Issue in 5:4
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1967595 Title: Display Issue in 5:4 Status in xorg package in Ubuntu: New Bug description: I have a 5:4 screen and when I launch Ubuntu (i'm using Xubuntu with ubuntu-desktop installed) the display is not properly aligned with the screen and I tried to invert the screen and my session closed everytime I try. Oh i forgot to tell i'm on Ubuntu 22.04 Beta. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1967595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1967595] [NEW] Display Issue in 5:4
You have been subscribed to a public bug: I have a 5:4 screen and when I launch Ubuntu (i'm using Xubuntu with ubuntu-desktop installed) the display is not properly aligned with the screen and I tried to invert the screen and my session closed everytime I try. Oh i forgot to tell i'm on Ubuntu 22.04 Beta. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Display Issue in 5:4 https://bugs.launchpad.net/bugs/1967595 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960307] Re: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices
Thanks, it was indeed a separate issue. Needed to remove bluez-alsa-utils... All is good now, would be great if one could change the codec through gnome-control-center. Pavucontrol method works. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1960307 Title: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices Status in PulseAudio: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Confirmed Status in gstreamer1.0 package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After the announcements of PulseAudio 15 and Gstreamer 1.20, which both advertised LDAC and AptX (HD) support, I expected that jammy (22.04) would support those codecs. Though in reality it seems that something is missing, gstreamer reports that those codecs are supported but "pactl [...] list-codec" only lists sbc (and variants). Checking here https://packages.ubuntu.com/jammy/pulseaudio-module- bluetooth it seems that PulseAudio is not built with gstreamer support, is that the current blocker? To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1960307/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1892134] Re: software-properties-gtk crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'com.ubuntu.So
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1892134 Title: software-properties-gtk crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'com.ubuntu.SoftwareProperties': timed out (service_start_timeout=25000ms) Status in software-properties package in Ubuntu: Confirmed Bug description: help meto fix this ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: software-properties-gtk 0.99.3 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 19 06:58:30 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2019-05-17 (459 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonArgs: ['/usr/bin/software-properties-gtk'] PythonDetails: N/A SourcePackage: software-properties Title: software-properties-gtk crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'com.ubuntu.SoftwareProperties': timed out (service_start_timeout=25000ms) UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1892134/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1967625] [NEW] package linux-image-5.14.0-1031-oem 5.14.0-1031.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: I didn't notice an issue, just a popup window was appearing everytime asking me to report this ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1031-oem 5.14.0-1031.34 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Apr 2 11:51:35 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2022-03-18 (15 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) 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: initramfs-tools Title: package linux-image-5.14.0-1031-oem 5.14.0-1031.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1967625 Title: package linux-image-5.14.0-1031-oem 5.14.0-1031.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: I didn't notice an issue, just a popup window was appearing everytime asking me to report this ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1031-oem 5.14.0-1031.34 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Apr 2 11:51:35 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2022-03-18 (15 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) 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: initramfs-tools Title: package linux-image-5.14.0-1031-oem 5.14.0-1031.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1967625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1967620] [NEW] [FFe] LXC 5.0 LTS
Public bug reported: LXC 5.0 LTS will very soon be released. The upstream release has been held up due to an incomplete port to meson (and deprecation of autotools), it's otherwise been ready to go for a few months. As far as LXC releases go, it's a very light one. Comparing it to current 4.0.12, we have: - No liblxc API changes at all (no new symbols or changes to headers) - Addition of a few configuration keys: - lxc.cgroup.dir.monitor.pivot - lxc.cgroup.dir.monitor - lxc.cgroup.dir.container.inner - lxc.cgroup.dir.container - lxc.time.offset.boot - lxc.time.offset.monotonic - veth.n_rxqueues - veth.n_txqueues - veth.vlan.id - veth.vlan.tagged.id - Port to meson (replacing autotools) Diffstat: ``` stgraber@dakara:~/data/code/lxc/lxc (lxc/master)$ git diff lxc-4.0.12.. . | diffstat .gitignore |1 config/init/systemd/Makefile.am| 10 + config/init/systemd/lxc-net.service.in |1 configure.ac |5 doc/api-extensions.md |9 + doc/ja/lxc.container.conf.sgml.in | 129 - doc/lxc.container.conf.sgml.in | 98 lxc.spec.in|1 meson.build|4 src/lxc/api_extensions.h |3 src/lxc/cgroups/cgfsng.c | 93 +++ src/lxc/cmd/lxc-checkconfig.in |6 - src/lxc/cmd/lxc_monitord.c | 59 + src/lxc/cmd/lxc_user_nic.c |2 src/lxc/conf.c | 11 + src/lxc/confile.c | 664 +--- src/lxc/network.c | 18 ++- src/lxc/network.h |4 src/lxc/terminal.c |1 src/lxc/terminal.h |3 src/lxc/tools/lxc_autostart.c |8 + src/lxc/utils.c|3 src/tests/aa.c |2 src/tests/config_jump_table.c |2 src/tests/containertests.c |2 src/tests/get_item.c | 90 ++- src/tests/getkeys.c|2 src/tests/locktests.c |2 src/tests/lxc-test-utils.c | 16 +- src/tests/meson.build | 534 ++ src/tests/mount_injection.c|2 src/tests/parse_config_file.c | 17 ++ src/tests/reboot.c |2 src/tests/share_ns.c |4 src/tests/snapshot.c |2 35 files changed, 1676 insertions(+), 134 deletions(-) ``` LXC 4.0.12 which we released on Feb 1st has all the bugfixes and other non-feature changes from LXC 5.0, making this quite a small and generally safe delta. The new features can be roughly categorized as: - Improve flexibility in cgroup configuration (make naming of /sys/fs/cgroup directories configurable) - Add support for the time namespace (clock offset) - Add support for configuring (basic sysctl) the number of veth queues - Add support for bridge VLAN filtering on veth devices LXC 5.0 will be an upstream LTS with a support duration matching that of Ubuntu 22.04 or until June 2027. Jammy currently ships LXC 4.0.12 which is only supported until June 2025 and will not see new bugfix releases after LXC 5.0 comes out (only security). LXC is unseeded and in universe these days. The main goal of putting the new LTS in the release is to reduce the maintenance cost for the Ubuntu LTS and to satisfy some of Canonical's customers that are directly using those packages and would expect a consistent set of LTS releases. LXCFS 5.0 is already in jammy and LXD 5.0 has similarly been released, though that one ships exclusively as a snap. If we can get general agreement that getting this LXC release in Ubuntu 22.04 is fine, what I can do to fast track things a bit is upload a 5.0~git-hash version which still relies on autotools, get that do clear autopkgtest and CI and then follow that up with the final 5.0 with the meson port as soon as it's complete on our side (expecting about a week, just got two directories to port). As a reminder, this is all unseeded and in universe, so overall impact should be quite low. Full upstream diff (4.0.12 to 5.0): https://gist.github.com/5c76aefcc8643e37a3e1b81a7a37a6f9 ** Affects: lxc (Ubuntu) Importance: High Status: New ** Changed in: lxc (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1967620 Title: [FFe] LXC 5.0 LTS Status in lxc package in Ubuntu: New Bug description:
[Touch-packages] [Bug 1967165] Re: package linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
In my case the error message was "could not write compressed host" /boot partition as per installed default may be a bit small-ish. Tried running update-upgrade command again, same result. ran "sudo apt autoremove --purge" to remove old kernels; update-upgrade worked fine after that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1967165 Title: package linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: automated update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-104.118-generic 5.4.166 Uname: Linux 5.4.0-104-generic x86_64 NonfreeKernelModules: falcon_lsm_serviceable falcon_nf_netcontain falcon_kal falcon_lsm_pinned_13207 falcon_lsm_pinned_13109 nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Mar 30 06:47:50 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2022-02-10 (48 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1967165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1967165] Re: package linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
In my case the error message was "could not write compressed host" /boot partition as per installed default may be a bit small-ish. Tried running update-upgrade command again, same result. ran "sudo apt autoremove --purge" to remove old kernels; update-upgrade worked fine after that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1967165 Title: package linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: automated update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-104.118-generic 5.4.166 Uname: Linux 5.4.0-104-generic x86_64 NonfreeKernelModules: falcon_lsm_serviceable falcon_nf_netcontain falcon_kal falcon_lsm_pinned_13207 falcon_lsm_pinned_13109 nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Mar 30 06:47:50 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2022-02-10 (48 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1967165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966849] Re: gzip exec format error under WSL
** Changed in: gzip Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1966849 Title: gzip exec format error under WSL Status in gzip: New Status in gzip package in Ubuntu: Confirmed Bug description: gzip version 1.10-4ubuntu3 fails to run under WSL1 on Windows 19044.1620, making WSL pretty much unusable. bash: /usr/bin/gzip: cannot execute binary file: Exec format error ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gzip 1.10-4ubuntu3 ProcVersionSignature: Microsoft 4.4.0-19041.1237-Microsoft 4.4.35 Uname: Linux 4.4.0-19041-Microsoft x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Mar 29 06:40:33 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/usr/bin/fish SourcePackage: gzip UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gzip/+bug/1966849/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1967609] [NEW] Nvidia 510 driver causes screen corruption in X for Ubuntu 22.04
Public bug reported: I was having strange un smooth scrolling in videos and video games, and sections of the GUI like the taskbar would disappear for a second or two. I moved to the 470 driver, and all the problems went away. I simple wanted to give you the pertinent information. Hopefully I have done that. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 07:06:47 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/470.103.01, 5.15.0-23-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia/470.103.01, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-23-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU116M [GeForce GTX 1660 Ti Mobile] [17aa:3a46] InstallationDate: Installed on 2022-03-31 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: LENOVO 82B1 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=3909483b-c0cc-449e-ac4b-024d9e0b353f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2020 dmi.bios.release: 1.14 dmi.bios.vendor: LENOVO dmi.bios.version: FSCN14WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05H dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrFSCN14WW:bd08/26/2020:br1.14:efr1.14:svnLENOVO:pn82B1:pvrLenovoLegion515ARH05H:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05H:skuLENOVO_MT_82B1_BU_idea_FM_Legion515ARH05H: dmi.product.family: Legion 5 15ARH05H dmi.product.name: 82B1 dmi.product.sku: LENOVO_MT_82B1_BU_idea_FM_Legion 5 15ARH05H dmi.product.version: Lenovo Legion 5 15ARH05H dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption jammy package-from-proposed ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1967609 Title: Nvidia 510 driver causes screen corruption in X for Ubuntu 22.04 Status in xorg package in Ubuntu: New Bug description: I was having strange un smooth scrolling in videos and video games, and sections of the GUI like the taskbar would disappear for a second or two. I moved to the 470 driver, and all the problems went away. I simple wanted to give you the pertinent information. Hopefully I have done that. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path
[Touch-packages] [Bug 1966849] Re: gzip exec format error under WSL
Note that only 1.10-4ubuntu3 is affected, so users can install gzip 1.10-4ubuntu1 and set the package on hold for the time being, until the issue is resolved. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1966849 Title: gzip exec format error under WSL Status in gzip: Unknown Status in gzip package in Ubuntu: Confirmed Bug description: gzip version 1.10-4ubuntu3 fails to run under WSL1 on Windows 19044.1620, making WSL pretty much unusable. bash: /usr/bin/gzip: cannot execute binary file: Exec format error ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gzip 1.10-4ubuntu3 ProcVersionSignature: Microsoft 4.4.0-19041.1237-Microsoft 4.4.35 Uname: Linux 4.4.0-19041-Microsoft x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Mar 29 06:40:33 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/usr/bin/fish SourcePackage: gzip UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gzip/+bug/1966849/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966849] Re: gzip exec format error under WSL
Reported to WSL: https://github.com/microsoft/WSL/issues/8219 ** Bug watch added: github.com/microsoft/WSL/issues #8219 https://github.com/microsoft/WSL/issues/8219 ** Also affects: gzip via https://github.com/microsoft/WSL/issues/8219 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1966849 Title: gzip exec format error under WSL Status in gzip: Unknown Status in gzip package in Ubuntu: Confirmed Bug description: gzip version 1.10-4ubuntu3 fails to run under WSL1 on Windows 19044.1620, making WSL pretty much unusable. bash: /usr/bin/gzip: cannot execute binary file: Exec format error ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gzip 1.10-4ubuntu3 ProcVersionSignature: Microsoft 4.4.0-19041.1237-Microsoft 4.4.35 Uname: Linux 4.4.0-19041-Microsoft x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Mar 29 06:40:33 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/usr/bin/fish SourcePackage: gzip UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gzip/+bug/1966849/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960307] Re: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices
Whether your headset cannot be switched from HFP to A2DP is a separate issue anyway. You can try pairing and trusting the device again, also please check if you have pipewire audio enabled which could seldom take over bluetooth a2dp, and see if bluetoothd log has anything related. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1960307 Title: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices Status in PulseAudio: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Confirmed Status in gstreamer1.0 package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After the announcements of PulseAudio 15 and Gstreamer 1.20, which both advertised LDAC and AptX (HD) support, I expected that jammy (22.04) would support those codecs. Though in reality it seems that something is missing, gstreamer reports that those codecs are supported but "pactl [...] list-codec" only lists sbc (and variants). Checking here https://packages.ubuntu.com/jammy/pulseaudio-module- bluetooth it seems that PulseAudio is not built with gstreamer support, is that the current blocker? To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1960307/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1948339] Re: Logon screen can be bypassed using various shortcuts
Sorry for the late reply on this issue. I only saw it a few days ago. I've spoken with the Arctica greeter developer and we've been working on a fix. The issue is this, Arctica Greeter requires a window manager and it invokes Marco, the window manager from MATE Desktop. Marco handles keybindings and by default has a number predefined. Ubuntu MATE adds a few more. This is why you are able to invoke applications bound to keybindings in Marco from Arctica Greeter. The proposed solution is to add a patch to Marco so that it can be invoked with keybindings disabled and then patch Arctica Greeter to invoke Marco with the argument to disable its keybindings. I will start preparing patched versions of Marco and Artica Greeter in a PPA for testing/validation. ** Changed in: arctica-greeter (Ubuntu) Status: New => Triaged ** Changed in: lightdm (Ubuntu) Status: New => Invalid ** Changed in: mate-settings-daemon (Ubuntu) Status: New => Invalid ** Also affects: marco (Ubuntu) Importance: Undecided Status: New ** Changed in: marco (Ubuntu) Status: New => Triaged ** Changed in: arctica-greeter (Ubuntu) Importance: Undecided => Critical ** Changed in: arctica-greeter (Ubuntu) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) ** Changed in: marco (Ubuntu) Importance: Undecided => Critical ** Changed in: marco (Ubuntu) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) ** No longer affects: ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Touch seeded 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 arctica-greeter package in Ubuntu: Triaged Status in lightdm package in Ubuntu: Invalid Status in marco package in Ubuntu: Triaged Status in mate-settings-daemon package in Ubuntu: Invalid 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/+source/arctica-greeter/+bug/1948339/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966849] Re: gzip exec format error under WSL
I am seeing the same error when I update Ubuntu 22.04 under WSL1: Processing triggers for install-info (6.8-4build1) ... sh: 1: gzip: Exec format error install-info: warning: no info dir entry in `/usr/share/info/coreutils.info.gz' sh: 1: gzip: Exec format error install-info: warning: no info dir entry in `/usr/share/info/diffutils.info.gz' ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1966849 Title: gzip exec format error under WSL Status in gzip package in Ubuntu: Confirmed Bug description: gzip version 1.10-4ubuntu3 fails to run under WSL1 on Windows 19044.1620, making WSL pretty much unusable. bash: /usr/bin/gzip: cannot execute binary file: Exec format error ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gzip 1.10-4ubuntu3 ProcVersionSignature: Microsoft 4.4.0-19041.1237-Microsoft 4.4.35 Uname: Linux 4.4.0-19041-Microsoft x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Mar 29 06:40:33 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/usr/bin/fish SourcePackage: gzip UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1966849/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966849] Re: gzip exec format error under WSL
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gzip (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1966849 Title: gzip exec format error under WSL Status in gzip package in Ubuntu: Confirmed Bug description: gzip version 1.10-4ubuntu3 fails to run under WSL1 on Windows 19044.1620, making WSL pretty much unusable. bash: /usr/bin/gzip: cannot execute binary file: Exec format error ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gzip 1.10-4ubuntu3 ProcVersionSignature: Microsoft 4.4.0-19041.1237-Microsoft 4.4.35 Uname: Linux 4.4.0-19041-Microsoft x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Mar 29 06:40:33 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/usr/bin/fish SourcePackage: gzip UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1966849/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960307] Re: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices
My current output for this command is:
pactl send-message /card/bluez_card.XX_XX_XX_XX_XX_XX/bluez list-codecs
[{"name":"CVSD","description":"CVSD"},{"name":"mSBC","description":"mSBC"}]
Usually, my headset only visible at pactl list cards at the second
connection attemtp and when it doeas connect I cannot change from AFP to
A2DB from the settings menu.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1960307
Title:
No gstreamer dependency causes high-fidelity codecs to be missing for
Bluetooth devices
Status in PulseAudio:
Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
Confirmed
Status in gstreamer1.0 package in Ubuntu:
Confirmed
Status in pulseaudio package in Ubuntu:
Confirmed
Bug description:
After the announcements of PulseAudio 15 and Gstreamer 1.20, which
both advertised LDAC and AptX (HD) support, I expected that jammy
(22.04) would support those codecs.
Though in reality it seems that something is missing, gstreamer
reports that those codecs are supported but "pactl [...] list-codec"
only lists sbc (and variants).
Checking here https://packages.ubuntu.com/jammy/pulseaudio-module-
bluetooth it seems that PulseAudio is not built with gstreamer
support, is that the current blocker?
To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1960307/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966552] Re: IBus input method candidate box cannot follow the cursor
** Changed in: ibus Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1966552 Title: IBus input method candidate box cannot follow the cursor Status in ibus: Fix Released Status in ibus package in Ubuntu: New Status in ibus-libpinyin package in Ubuntu: New Bug description: I have tested it in some software, such as Microsoft Edge, Onlyoffice, and it does not follow the cursor position correctly, but always at the bottom left of the application window. However, in some applications such as Gedit, it works fine. Pictures are here：https://i.bmp.ovh/imgs/2022/03/34ebb5158ceeedfc.png OS: Ubuntu Jammy Jellyfish Kernel: 5.15.0-23-generic on Wayland ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ibus-libpinyin 1.12.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 26 23:59:28 2022 InstallationDate: Installed on 2022-02-09 (45 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: ibus-libpinyin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1966552/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1967602] [NEW] intell error
Public bug reported: to debug the driver of intell and nvidia ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..03.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.54 Tue Feb 8 04:42:21 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 11:02:54 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: nvidia, 510.54, 5.13.0-39-generic, x86_64: installed GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:14ad] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 840M] [1043:14ad] InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: ASUSTeK COMPUTER INC. N56JN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic root=UUID=e5109f6b-927a-4288-ae57-107f31ecd576 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2019 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56JN.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56JN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56JN.205:bd06/11/2019:br4.6:svnASUSTeKCOMPUTERINC.:pnN56JN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56JN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: N dmi.product.name: N56JN dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1967602 Title: intell error Status in xorg package in Ubuntu: New Bug description: to debug the driver of intell and nvidia ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..03.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.54 Tue Feb 8 04:42:21 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 11:02:54 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: nvidia, 510.54, 5.13.0-39-generic, x86_64: installed GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller])
