[Touch-packages] [Bug 1958060] Re: bash returns wrong variable value/call more proccesses?
[Expired for bash (Ubuntu) because there has been no activity for 60
days.]
** Changed in: bash (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1958060
Title:
bash returns wrong variable value/call more proccesses?
Status in bash package in Ubuntu:
Expired
Bug description:
Simple function gives different results when interpretator set in first
string of script
CHECKPROC()
{
i=$(ps aux | grep -c $0)
ps aux | grep -c $0
echo variable is $i
sleep 10
}
CHECKPROC
Expected
In any conditions it will return same values, then will increments when other
copies of script will be found in proccesses list.
Happened.
We set interpretator with #!/bin/bash or #!/bin/sh in first string of script
and runs multiple copies of script from one terminal with & after scriptname.
It's returns "1" and "variable is 1" always.
Without interpretator setup, when string #!/bin/bash or #!/bin/sh deleted.
Run multiple copies scriptname.sh&
On every iteration it returns right first value and "variable is $value+1"
$scriptname.sh&
2
variable is 3
$scriptname.sh&
3
variable is 4
...and so on.
Without counting in first case it returns only string with grep, in
second case -- one more string with different PID and script name when
called from i=$(...) or i=`...`
Ubuntu 14.04 x32, bash 4.3.11(1)-release
Same results from other man on
GNU bash, version 5.1.16(1)-release (aarch64-apple-darwin21.1.0)
GNU bash, version 4.4.20(1)-release (x86_64-pc-linux-gnu)
lsb_release -rd
Description: Ubuntu 14.04.6 LTS
Release: 14.04
apt-cache policy bash
bash:
Установлен: 4.3-7ubuntu1.7
Кандидат: 4.3-7ubuntu1.7
Таблица версий:
4.3-7ubuntu1.8+esm1 0
-32768 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main i386
Packages
*** 4.3-7ubuntu1.7 0
500 http://ru.archive.ubuntu.com/ubuntu/ trusty-updates/main i386
Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386
Packages
100 /var/lib/dpkg/status
4.3-6ubuntu1 0
500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1958060/+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 1965603] [NEW] [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound at all
Public bug reported: computer model:notebook 9 pen 15" nvidia GPU: Nvidia geforce mx150 Sound: AKG stereo speakers High definition audio no sound whats so ever, not even in bluetooth. removed and reinstalled alsa and pulse audio, then restarted, just to have no sound still. checked settings in sound menu to see if I can select proper audio device but only one selection is given. Any ideas on how to go about in fixing issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: densetsu 1521 F pulseaudio /dev/snd/pcmC0D0c: densetsu 1521 F...m pulseaudio /dev/snd/pcmC0D0p: densetsu 1521 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Mar 18 19:19:42 2022 InstallationDate: Installed on 2022-03-17 (1 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) 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 failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1033 F pulseaudio densetsu 1521 F pulseaudio /dev/snd/pcmC0D0c: densetsu 1521 F...m pulseaudio /dev/snd/pcmC0D0p: densetsu 1521 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P07RES.076.190919.SP dmi.board.asset.tag: No Asset Tag dmi.board.name: NP950SBE-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9849A0L-C01-G001-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP07RES.076.190919.SP:bd09/19/2019:br5.13:svnSAMSUNGELECTRONICSCO.,LTD.:pn950SBE/951SBE:pvrP07RES:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP950SBE-X01US:rvrSGL9849A0L-C01-G001-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PRES: dmi.product.family: Notebook 9 Series dmi.product.name: 950SBE/951SBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PRES dmi.product.version: P07RES dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1965603 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: computer model:notebook 9 pen 15" nvidia GPU: Nvidia geforce mx150 Sound: AKG stereo speakers High definition audio no sound whats so ever, not even in bluetooth. removed and reinstalled alsa and pulse audio, then restarted, just to have no sound still. checked settings in sound menu to see if I can select proper audio device but only one selection is given. Any ideas on how to go about in fixing issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: densetsu 1521 F pulseaudio /dev/snd/pcmC0D0c: densetsu 1521 F...m pulseaudio /dev/snd/pcmC0D0p: densetsu 1521 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Mar 18 19:19:42 2022 InstallationDate: Installed on 2022-03-17 (1 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) 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 failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1033 F pulseaudio densetsu 1521 F pulseaudio /dev/snd/pcmC0D0c: densetsu 1521 F...m pulseaudio /dev/snd/pcmC0D0p:
[Touch-packages] [Bug 1953428] Re: /etc/PackageKit/Vendor.conf specifies invalid CodecUrl
** Changed in: packagekit (Ubuntu) Milestone: None => ubuntu-22.04-beta -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1953428 Title: /etc/PackageKit/Vendor.conf specifies invalid CodecUrl Status in packagekit package in Ubuntu: Confirmed Bug description: CodecUrl in /etc/PackageKit/Vendor.conf on Impish at least currently has: http://shop.canonical.com/index.php?cPath=19=f1e370ea7563ed5e654c10450364ff24 shop.canonical.com does not have a DNS record and has been dead for a long time so this should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1953428/+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 1958088] Re: Mopidy wil not connect to icecast2
Ok solved the libenc issue on ubuntu 20.04 using GitHub - raveberry/raveberry: A multi-user music server with a focus on participation Streaming doesn’t work (there is only silence) This is a known issue on Ubuntu 20.04 and Debian Bullseye. To fix it, downgrade libshout3: cd /tmp # for x86_64 wget http://mirrors.kernel.org/ubuntu/pool/main/libs/libshout/libshout3_2.4.1-2build1_amd64.deb -O libshout.deb # for armhf (Raspberry Pi) wget http://raspbian.raspberrypi.org/raspbian/pool/main/libs/libshout/libshout3_2.4.1-2_armhf.deb -O libshout.deb sudo dpkg -i libshout.deb sudo apt-mark hold libshout3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libshout in Ubuntu. https://bugs.launchpad.net/bugs/1958088 Title: Mopidy wil not connect to icecast2 Status in libshout package in Ubuntu: New Bug description: Mopidy will not connect to icecast2, similar to bug 1908639. Mixxx fixed it by linking to the static version of libshout 2.4.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libshout/+bug/1958088/+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 1965535] Re: Stop recommending snap
It's also worth pointing out how snap does not offer feature parity. VA- API and native-component extensions are broken to this day with Chromium snap, for four years now. The latter meaning that entire countries can not use chromium snap if they wish to use their national authentication and signature system on the web. Broken for millions of potential users and nobody cares. Seeing how shipping fully-working software seems not doable with snaps, recommending it as a default is an user-hostile decision at this point in time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1965535 Title: Stop recommending snap Status in ubuntu-meta package in Ubuntu: Opinion Bug description: Currently, ubuntu recommends installing snap by default, and some apps are slowly transitioning from DEB-based installation to Snap-based installation. APT is great, and facilitates having a clean, maintainable system. The snap project is not very well designed or engineered (just changing the location of where snap data is located is taking the project more than 5 years because it was hardcoded: https://bugs.launchpad.net/snapd/+bug/1575053). Snaps are large and VERY slow. The design of snap, as well as the way that decisions are made, are very questionable, and are receiving increasing amounts of criticism. I'd like to request that Ubuntu stops recommending snap, stops transitioning towards snaps, and we come back to defaulting to DEB/APT-based installation for all apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965535/+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 1965535] Re: Stop recommending snap
+1 For the record, Snap being forced upon users for critical packages is the primary reason why I recently dropped Ubuntu and stopped recommending the distro to others, after using it for over 15 years. Container-based packaging has its place. Snap has some interesting features compared to FlatPak and AppImage. However, none of them are suitable replacements for deb & apt, and this is really driven home when they're used for core packages like the web browser. Snap in particular has multiple fundamental design and implementation problems that make it intolerable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1965535 Title: Stop recommending snap Status in ubuntu-meta package in Ubuntu: Opinion Bug description: Currently, ubuntu recommends installing snap by default, and some apps are slowly transitioning from DEB-based installation to Snap-based installation. APT is great, and facilitates having a clean, maintainable system. The snap project is not very well designed or engineered (just changing the location of where snap data is located is taking the project more than 5 years because it was hardcoded: https://bugs.launchpad.net/snapd/+bug/1575053). Snaps are large and VERY slow. The design of snap, as well as the way that decisions are made, are very questionable, and are receiving increasing amounts of criticism. I'd like to request that Ubuntu stops recommending snap, stops transitioning towards snaps, and we come back to defaulting to DEB/APT-based installation for all apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965535/+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 1916931] Re: omshell returns inconsistent results or segfaults
I confirm this bug with this package on ubuntu 20.04 too, not happening when build from source -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1916931 Title: omshell returns inconsistent results or segfaults Status in isc-dhcp package in Ubuntu: Confirmed Bug description: I have just built a Ubuntu 20.04 server and installed isc-dhcp-server 4.4.1 on it and I am seeing inconsistent returns from omshell. Initially omshell returns data as expected, but when I exit and re-enter omshell connections fail. Here is the initial, working, session: # omshell > server localhost > port 7911 > key omapi_key > connect obj: > new failover-state obj: failover-state > set name = "dhcp-failover" obj: failover-state name = "dhcp-failover" > open obj: failover-state name = "dhcp-failover" partner-address = c0:9d:e9:76:e9:55:00:00 partner-port = 00:00:02:07 local-address = 10:9d:e9:76:e9:55:00:00 local-port = 00:00:02:07 max-outstanding-updates = 00:00:00:0a mclt = 00:00:01:2c load-balance-max-secs = 00:00:00:03 load-balance-hba = ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 partner-state = 00:00:00:02 local-state = 00:00:00:02 partner-stos = 60:36:d0:68 local-stos = 60:36:8b:3b hierarchy = 00:00:00:01 last-packet-sent = 00:00:00:00 last-timestamp-received = 00:00:00:00 skew = 00:00:00:00 max-response-delay = 00:00:00:3c cur-unacked-updates = 00:00:00:00 Here is what I see when the connect fails. Well, just hangs really. # omshell > server localhost > port 7911 > key omapi_key > connect And then I hit ctrl-c to break out and tried again: # omshell > server localhost > port 7911 > key omapi_key > connect Segmentation fault (core dumped) Note, the peer to this server is still running Ubuntu 18.04 with isc-dhcp-server 4.3.5. Running the exact same commands on the peer works reliably. (They are using the same python script to drive omshell.) The DHCP server on the new system appears to be working just fine as reported by omshell on the peer and systemctl. I was curious if the problem could be with the mis-matched versions of isc-dhcp-server so I shutdown isc-dhcp-server on the 18.04 system and get the same results. I also tried using a python script with the pypureomapi module to try and determine if the problem was in omshell or the server. I got very similar results when I attempted to get information about the failover state of the server. Interestingly interrogating the server about host information seems to work just fine. This is a critical bug since I don't see how to fail over a DHCP that is running the isc-dhcp-server on 20.04 without being able to issue omapi commands. I am attaching apport output to this bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1916931/+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 1964442] Re: [jammy Regression] signing a changes file in gnome-terminal sends keys to the terminal
I experienced a similar issue today. I ran `snap install app` in my terminal. It popped up a PolicyKit login window and my terminal started filling with empty input lines. Around the same time, I had this in my journal log repeatedly: gnome-shell: Object 0x5614373df110 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Therefore, I'm reassigning to gnome-shell and ibus. I don't think this issue is specific to gnome-terminal. You might eventually see it with a different terminal. I am using the default Ubuntu session on Wayland. ** Package changed: gnome-terminal (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Confirmed ** Also affects: ibus (Ubuntu) Importance: Undecided Status: New ** Changed in: ibus (Ubuntu) Status: New => Confirmed -- 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/1964442 Title: [jammy Regression] signing a changes file in gnome-terminal sends keys to the terminal Status in gnome-shell package in Ubuntu: Confirmed Status in ibus package in Ubuntu: Confirmed Bug description: This is a regression not seen until this week (not seen until March 4 at least). Calling debsign from a terminal pops up the window to enter the key, but the terminal is sent continuous keys and the terminal scrolls down with empty input lines. You can still sign the file, however you end up with an empty scroll buffer if the signing takes too long time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964442/+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 1965565] [NEW] package linux-firmware 1.187.29 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Public bug reported: error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.29 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Mar 18 18:15:50 2022 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-02-17 (29 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20SQS1TF01 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 SourcePackage: initramfs-tools Title: package linux-firmware 1.187.29 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.26 dmi.bios.vendor: LENOVO dmi.bios.version: N30ET43W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SQS1TF01 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 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.16 dmi.modalias: dmi:bvnLENOVO:bvrN30ET43W(1.26):bd11/08/2021:br1.26:efr1.16:svnLENOVO:pn20SQS1TF01:pvrThinkPadP17Gen1:rvnLENOVO:rn20SQS1TF01:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20SQ_BU_Think_FM_ThinkPadP17Gen1: dmi.product.family: ThinkPad P17 Gen 1 dmi.product.name: 20SQS1TF01 dmi.product.sku: LENOVO_MT_20SQ_BU_Think_FM_ThinkPad P17 Gen 1 dmi.product.version: ThinkPad P17 Gen 1 dmi.sys.vendor: LENOVO ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1965565 Title: package linux-firmware 1.187.29 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.29 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Mar 18 18:15:50 2022 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-02-17 (29 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20SQS1TF01 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 SourcePackage: initramfs-tools Title: package linux-firmware 1.187.29 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.26 dmi.bios.vendor: LENOVO dmi.bios.version: N30ET43W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SQS1TF01 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 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.16 dmi.modalias: dmi:bvnLENOVO:bvrN30ET43W(1.26):bd11/08/2021:br1.26:efr1.16:svnLENOVO:pn20SQS1TF01:pvrThinkPadP17Gen1:rvnLENOVO:rn20SQS1TF01:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20SQ_BU_Think_FM_ThinkPadP17Gen1: dmi.product.family: ThinkPad P17 Gen 1 dmi.product.name: 20SQS1TF01 dmi.product.sku: LENOVO_MT_20SQ_BU_Think_FM_ThinkPad P17 Gen 1 dmi.product.version: ThinkPad P17 Gen 1 dmi.sys.vendor: LENOVO To manage
[Touch-packages] [Bug 1962332] Re: xenial systemd fails to start if cgroup2 is mounted
It's the SRU team's purview to make exceptions here. The rationale that this only benefits images is and therefore needs to be in the main archive is sound. So for the SRU team, I'm +1 on going ahead with this. But someone still needs to prepare the SRU, which I think falls to Foundations. -- 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/1962332 Title: xenial systemd fails to start if cgroup2 is mounted Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Bug description: [impact] now that jammy has moved to using unified cgroup2, containers started on jammy must also use unified cgroup2 (since the cgroup subsystems can only be mounted as v1 or v2 throughout the entire system, including inside containers). However, the systemd in xenial does not include support for cgroup2, and doesn't recognize its magic (added in upstream commit 099619957a0), so it fails to start completely. [workaround] On Jammy host edit default kernel command line to include systemd.unified_cgroup_hierarchy=false update your bootloader configuration; and reboot then hybrid cgroups will be on the host, and one can launch xenial container then. [test case] create a jammy system, that has unified cgroup2 mounted. Then: $ lxc launch ubuntu:xenial test-x ... $ lxc shell test-x (inside xenial container): $ mv /sbin/init /sbin/init.old $ cat > /sbin/init <+a q Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted [!!] Failed to mount API filesystems, freezing. Freezing execution. [regression potential] any regression would likely break xenial containers from starting at all, or cause cgroup-related problems with systemd starting and/or managing services. [scope] this is needed only for xenial. However, as xenial is out of standard support, this would need to be an exception. this is fixed upstream with commit 099619957a0 (and possibly others - needs closer investigation and testing) which is first included in v230, so this is fixed already in b and later. this is not needed - by default - for trusty because upstart is used there; however, I think it's possible to change trusty over to use systemd instead of upstart. But since trusty is out of standard support, and it doesn't fail by default, it doesn't seem like it should be fixed. [other info] An alternative appears to be to change the host system back to using the 'hybrid' cgroup, however that obviously is awful and would remove the benefits of cgroup v2 from the host system, and force all containers on the host system to also use the 'hybrid' cgroup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962332/+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 1962332] Re: xenial systemd fails to start if cgroup2 is mounted
I feel like this special case should be decided and handled by the release team, not Foundations. -- 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/1962332 Title: xenial systemd fails to start if cgroup2 is mounted Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Bug description: [impact] now that jammy has moved to using unified cgroup2, containers started on jammy must also use unified cgroup2 (since the cgroup subsystems can only be mounted as v1 or v2 throughout the entire system, including inside containers). However, the systemd in xenial does not include support for cgroup2, and doesn't recognize its magic (added in upstream commit 099619957a0), so it fails to start completely. [workaround] On Jammy host edit default kernel command line to include systemd.unified_cgroup_hierarchy=false update your bootloader configuration; and reboot then hybrid cgroups will be on the host, and one can launch xenial container then. [test case] create a jammy system, that has unified cgroup2 mounted. Then: $ lxc launch ubuntu:xenial test-x ... $ lxc shell test-x (inside xenial container): $ mv /sbin/init /sbin/init.old $ cat > /sbin/init <+a q Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted [!!] Failed to mount API filesystems, freezing. Freezing execution. [regression potential] any regression would likely break xenial containers from starting at all, or cause cgroup-related problems with systemd starting and/or managing services. [scope] this is needed only for xenial. However, as xenial is out of standard support, this would need to be an exception. this is fixed upstream with commit 099619957a0 (and possibly others - needs closer investigation and testing) which is first included in v230, so this is fixed already in b and later. this is not needed - by default - for trusty because upstart is used there; however, I think it's possible to change trusty over to use systemd instead of upstart. But since trusty is out of standard support, and it doesn't fail by default, it doesn't seem like it should be fixed. [other info] An alternative appears to be to change the host system back to using the 'hybrid' cgroup, however that obviously is awful and would remove the benefits of cgroup v2 from the host system, and force all containers on the host system to also use the 'hybrid' cgroup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962332/+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 1929345] Re: Pressing calculator key generates infinitely many key-press key-release events
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu2 ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Lukas Märdian (slyon) ** Changed in: systemd (Ubuntu) Status: Triaged => In Progress -- 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/1929345 Title: Pressing calculator key generates infinitely many key-press key- release events Status in systemd package in Ubuntu: In Progress Bug description: Full description is posted in this AskUbuntu question: https://askubuntu.com/q/1336575/625814 I've got a new notebook HP Omen 15, manufactured in 2020. I has Calculator key, this key is actual normal media key. Pressing on it launches calculator only once, after the OS is booted. No reaction for other presses. If I run xev and press Calculator I see infinitely many messages about pressing and releasing XF86Calculator key: ... KeyRelease event, serial 42, synthetic NO, window 0x3e1, root 0x29e, subw 0x0, time 52918, (151,-96), root:(151,806), state 0x14, keycode 148 (keysym 0x1008ff1d, XF86Calculator), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 42, synthetic NO, window 0x3e1, root 0x29e, subw 0x0, time 52918, (151,-96), root:(151,806), state 0x14, keycode 148 (keysym 0x1008ff1d, XF86Calculator), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 42, synthetic NO, window 0x3e1, root 0x29e, subw 0x0, time 52958, (151,-96), root:(151,806), state 0x14, keycode 148 (keysym 0x1008ff1d, XF86Calculator), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 42, synthetic NO, window 0x3e1, root 0x29e, subw 0x0, time 52958, (151,-96), root:(151,806), state 0x14, keycode 148 (keysym 0x1008ff1d, XF86Calculator), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 42, synthetic NO, window 0x3e1, root 0x29e, subw 0x0, time 52999, (151,-96), root:(151,806), state 0x14, keycode 148 (keysym 0x1008ff1d, XF86Calculator), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False ... Then I press Ctrl-C to stop this stream. This happens only once after the system is booted, next runs of xev don't show any events after pressing this key. If I run showkey, it always shows scan codes and key codes for that key: $ sudo showkey -s kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... 0x9c 0xe0 0x21 0x1d ^Ccaught signal 2, cleaning up... 0xe0 0x21 $ sudo showkey -k kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... keycode 28 release keycode 140 press keycode 29 press ^Ccaught signal 2, cleaning up... Debugging with evtest shows that this key doesn't generate any events, while some other keys do: sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0: Power Button /dev/input/event1: Lid Switch /dev/input/event2: Power Button /dev/input/event3: AT Translated Set 2 keyboard /dev/input/event4: Video Bus /dev/input/event5: HP WMI hotkeys /dev/input/event6: HDA NVidia HDMI/DP,pcm=3 /dev/input/event7: SONiX USB Keyboard /dev/input/event8: SONiX USB Keyboard Consumer Control /dev/input/event9: SONiX USB Keyboard System Control /dev/input/event10: PixArt Dell MS116 USB Optical Mouse /dev/input/event11: HDA NVidia HDMI/DP,pcm=7 /dev/input/event12: HDA NVidia HDMI/DP,pcm=8 /dev/input/event13: HDA NVidia HDMI/DP,pcm=9 /dev/input/event14: HDA NVidia HDMI/DP,pcm=10 /dev/input/event15: HDA NVidia HDMI/DP,pcm=11 /dev/input/event16: SYNA32A5:00 06CB:CE17 Mouse /dev/input/event17: SYNA32A5:00 06CB:CE17 Touchpad /dev/input/event18: HD-Audio Generic Mic /dev/input/event19: HD-Audio Generic Headphone /dev/input/event20: HP Wide Vision HD Camera: HP Wi /dev/input/event21: WI-XB400 (AVRCP) Select the device event number [0-21]: 5 Input driver version is 1.0.1 Input device ID: bus 0x19 vendor 0x0 product 0x0 version 0x0 Input device name: "HP WMI hotkeys" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 138 (KEY_HELP) Event code 141 (KEY_SETUP) Event code 148 (KEY_PROG1) Event code 153 (KEY_DIRECTION) Event code 184 (KEY_F14) Event code 185 (KEY_F15) Event code 186
[Touch-packages] [Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
Hey Dan Streetman (ddstreet), I believe the above patch satisfies your valid concerns about backporting. Would you please analyse for acceptance? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: New Bug description: [Impact] openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a CertificateRequest message to the client with a non-empty status_request extension. This issue was fixed in openssl-1.1.1d and is included in Focal onward. Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767 Upstream patch review at https://github.com/openssl/openssl/pull/9780 The issue leads to various client failures with TLS 1.3 as described in, e.g. https://github.com/golang/go/issues/35722 https://github.com/golang/go/issues/34040 [Test Plan] The issue can be reproduced by building with `enable-ssl-trace` and then running `s_server` like this: ``` openssl s_server -key key.pem -cert cert.pem -status_file test/recipes/ocsp-response.der -Verify 5 ``` And running `s_client` like this: ``` openssl s_client -status -trace -cert cert.pem -key key.pem ``` The output shows a `status_request` extension in the `CertificateRequest` as follows: Received Record Header: Version = TLS 1.2 (0x303) Content Type = ApplicationData (23) Length = 1591 Inner Content Type = Handshake (22) CertificateRequest, Length=1570 request_context (len=0): extensions, length = 1567 extension_type=status_request(5), length=1521 - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2 0.. 000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01 0.+.0.. 001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86 0...0.. 002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47 0..1.0...UG ...more lines omitted... If the `status_request` extension is present in a `CertificateRequest` then it must be empty according to RFC8446, Sec. 4.4.2.1. [Where problems could occur] The patch disables the `status_request` extension inside a `CertificateRequest`. Applications expecting the incorrect, non-empty reply for the `status_request` extension will break with this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+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 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
openssl (1.1.1-1ubuntu2.1~18.04.15ubuntu1) bionic; urgency=medium * Backport pr9780 but make it optional: - d/p/pr9780_0002-Teach-TLSProxy-how-to-parse-CertificateRequest-messa.patch - d/p/pr9780_0001-Don-t-send-a-status_request-extension-in-a-Certifica.patch - d/p/lp1940141-make-pr-9780-optional.patch - d/p/lp1940141-fix-tests-accordingly.patch - d/p/lp1940141-update-manpages.patch -- Bruce Elrick Wed, 16 Mar 2022 17:05:32 + ** Patch added: "Backport pr9780 but make it optional" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+attachment/5570447/+files/bionic.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: New Bug description: [Impact] openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a CertificateRequest message to the client with a non-empty status_request extension. This issue was fixed in openssl-1.1.1d and is included in Focal onward. Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767 Upstream patch review at https://github.com/openssl/openssl/pull/9780 The issue leads to various client failures with TLS 1.3 as described in, e.g. https://github.com/golang/go/issues/35722 https://github.com/golang/go/issues/34040 [Test Plan] The issue can be reproduced by building with `enable-ssl-trace` and then running `s_server` like this: ``` openssl s_server -key key.pem -cert cert.pem -status_file test/recipes/ocsp-response.der -Verify 5 ``` And running `s_client` like this: ``` openssl s_client -status -trace -cert cert.pem -key key.pem ``` The output shows a `status_request` extension in the `CertificateRequest` as follows: Received Record Header: Version = TLS 1.2 (0x303) Content Type = ApplicationData (23) Length = 1591 Inner Content Type = Handshake (22) CertificateRequest, Length=1570 request_context (len=0): extensions, length = 1567 extension_type=status_request(5), length=1521 - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2 0.. 000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01 0.+.0.. 001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86 0...0.. 002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47 0..1.0...UG ...more lines omitted... If the `status_request` extension is present in a `CertificateRequest` then it must be empty according to RFC8446, Sec. 4.4.2.1. [Where problems could occur] The patch disables the `status_request` extension inside a `CertificateRequest`. Applications expecting the incorrect, non-empty reply for the `status_request` extension will break with this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+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 1798400] Re: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic
Bug still there. In most situations the remote cannot be used at all. Not via bluetooth (because of this issue), neither via wifi (because you typically do presentations at sites where you do not control the wifi network and traffic to the relevant ports gets blocked). Suggested upstream some possible solutions including stop advertising the functionality. Consider closing as Wontfix because I think there is really nothing that downstream can do about it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+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 1931582] Re: Add LOGO to /etc/os-release
Checking that topic again, fedora added back a patch stating they don't think the upstream solution is enough https://src.fedoraproject.org/rpms/gnome-control-center/blob/rawhide/f/distro-logo.patch The discussion continued upstream in https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/965 and then https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/1399 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1399 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1399 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1931582 Title: Add LOGO to /etc/os-release Status in base-files package in Ubuntu: Triaged Status in base-files package in Debian: New Bug description: /etc/os-release can provide a logo file, this is now used by gnome- control-center to show the logo into the info panel. If ubuntu would provide its logo name in such file we would be able to remove the downstream patch that forces the usage of /usr/share/pixmaps/ubuntu-logo-icon.png References --- https://www.freedesktop.org/software/systemd/man/os-release.html https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/985 GNOME Control Center, as of version 41, can look for variations of the named LOGO. So we should offer those variations if possible too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1931582/+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 1958019]
(In reply to Mark York from comment #580) > (In reply to vpi from comment #579) > > (In reply to Mark York from comment #578) > > > (In reply to vpi from comment #577) > > > > (In reply to Darin Miller from comment #563) > > > > > *Ubuntu version: > > > > > > > > > > 1) install kernel build tools: > > > > > (https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel): > > > > > > > > > > * sudo apt install libncurses-dev gawk flex bison openssl libssl-dev > > dkms > > > > > libelf-dev libudev-dev libpci-dev libiberty-dev autoconf git > > > > > > > > > > 2) clone the kernel from github and checkout to v5.17 branch (Rather > > > large, > > > > > multiple GB's): > > > > > > > > > > * git clone https://github.com/torvalds/linux.git > > > > > * cd linux > > > > > * git checkout v5.17-rc4 > > > > > > > > > > 3) get the patch and install it: > > > > > > > > > > get the patch form this site and save to "linux" directory: (top > right > > > > > corner "series" button) and use the following "git am ..." line to > > apply > > > > the > > > > > patch: > > > > > > > > > > > > > > > https://patchwork.kernel.org/project/linux-acpi/patch/20220121172431.6876-4- > > > > > sbind...@opensource.cirrus.com/ > > > > > > > > > > * git am Support-Spi-in-i2c-multi-instantiate-driver.patch > > > > > > > > > > 4) load current kernel config and change configuration then run the > > > > > following scripts/config commands: > > > > > > > > > > * make olddefconfig > > > > > * ./scripts/config --enable CONFIG_SERIAL_MULTI_INSTANTIATE > > > > > * ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_I2C > > > > > * ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_SPI > > > > > * ./scripts/config --disable CONFIG_DEBUG_INFO > > > > > * ./scripts/config --set-str CONFIG_SYSTEM_TRUSTED_KEYS "" > > > > > * ./scripts/config --set-str CONFIG_SYSTEM_REVOCATION_KEYS "" > > > > > > > > > > 6) build the kernel > > > > > > > > > > * make -j 16 > > > > > > > > > > 7) install the kernel > > > > > > > > > > * sudo make module_install > > > > > * sudo make install > > > > > > > > Hi guys, > > > > > > > > This is my first time compiling a kernel (Legion 7 16ACHg6/Ubuntu > 20.04). > > I > > > > followed these steps (checked out the v5.17-rc8 branch on git) but at > the > > > > end I am getting this error at the last step, just before running sudo > > make > > > > install: > > > > > > > > arch/x86/Makefile:154: CONFIG_X86_X32 enabled but no binutils support > > > > sh ./arch/x86/boot/install.sh 5.17.0-rc8+ \ > > > > arch/x86/boot/bzImage System.map "/boot" > > > > > > > > *** Missing file: arch/x86/boot/bzImage > > > > *** You need to run "make" before "make install". > > > > > > > > make: *** [arch/x86/Makefile:278: install] Error 1 > > > > > > > > Any help would be appreciated > > > > > > > > > Hello @vpi > > > > > > Before running "make install" you need to compile the kernel with "make". > > > "make install" will install the compiled kernel, so you need to compile > it > > > first. > > > > Hi Mark, > > > > I should've been clearer in my last comment. I followed the instructions > > stepwise, which means I ran "make -j 16" before running "make install". And > > yet I was getting this error. > > Hi vpi, > > I would recommend to start fresh. What I would do is: > 1. Get into the kernel config with "make menuconfig", load the .config file > from the "Load" button at the bottom. > 2. Exit the menu, this will save the and accommodate the config. > 3. Compile the kernel with "make" and whatever options you want. > 3. Compile the kernel modules (if you have chosen to build drivers as > modules) with "make modules_install". > 5. Install the kernel image in /boot with "make install". > > Try this and let me know of the results. I'm really interested in fixing > this problem myself as well. I have a Legion 7 16ACHg6 (AMD) and speakers > don't work on Arch Linux. > 4. Remember to check GRUB's config files to include the new kernel image. -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio
[Touch-packages] [Bug 1958019]
(In reply to vpi from comment #579) > (In reply to Mark York from comment #578) > > (In reply to vpi from comment #577) > > > (In reply to Darin Miller from comment #563) > > > > *Ubuntu version: > > > > > > > > 1) install kernel build tools: > > > > (https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel): > > > > > > > > * sudo apt install libncurses-dev gawk flex bison openssl libssl-dev > dkms > > > > libelf-dev libudev-dev libpci-dev libiberty-dev autoconf git > > > > > > > > 2) clone the kernel from github and checkout to v5.17 branch (Rather > > large, > > > > multiple GB's): > > > > > > > > * git clone https://github.com/torvalds/linux.git > > > > * cd linux > > > > * git checkout v5.17-rc4 > > > > > > > > 3) get the patch and install it: > > > > > > > > get the patch form this site and save to "linux" directory: (top right > > > > corner "series" button) and use the following "git am ..." line to > apply > > > the > > > > patch: > > > > > > > > > > https://patchwork.kernel.org/project/linux-acpi/patch/20220121172431.6876-4- > > > > sbind...@opensource.cirrus.com/ > > > > > > > > * git am Support-Spi-in-i2c-multi-instantiate-driver.patch > > > > > > > > 4) load current kernel config and change configuration then run the > > > > following scripts/config commands: > > > > > > > > * make olddefconfig > > > > * ./scripts/config --enable CONFIG_SERIAL_MULTI_INSTANTIATE > > > > * ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_I2C > > > > * ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_SPI > > > > * ./scripts/config --disable CONFIG_DEBUG_INFO > > > > * ./scripts/config --set-str CONFIG_SYSTEM_TRUSTED_KEYS "" > > > > * ./scripts/config --set-str CONFIG_SYSTEM_REVOCATION_KEYS "" > > > > > > > > 6) build the kernel > > > > > > > > * make -j 16 > > > > > > > > 7) install the kernel > > > > > > > > * sudo make module_install > > > > * sudo make install > > > > > > Hi guys, > > > > > > This is my first time compiling a kernel (Legion 7 16ACHg6/Ubuntu 20.04). > I > > > followed these steps (checked out the v5.17-rc8 branch on git) but at the > > > end I am getting this error at the last step, just before running sudo > make > > > install: > > > > > > arch/x86/Makefile:154: CONFIG_X86_X32 enabled but no binutils support > > > sh ./arch/x86/boot/install.sh 5.17.0-rc8+ \ > > > arch/x86/boot/bzImage System.map "/boot" > > > > > > *** Missing file: arch/x86/boot/bzImage > > > *** You need to run "make" before "make install". > > > > > > make: *** [arch/x86/Makefile:278: install] Error 1 > > > > > > Any help would be appreciated > > > > > > Hello @vpi > > > > Before running "make install" you need to compile the kernel with "make". > > "make install" will install the compiled kernel, so you need to compile it > > first. > > Hi Mark, > > I should've been clearer in my last comment. I followed the instructions > stepwise, which means I ran "make -j 16" before running "make install". And > yet I was getting this error. Hi vpi, I would recommend to start fresh. What I would do is: 1. Get into the kernel config with "make menuconfig", load the .config file from the "Load" button at the bottom. 2. Exit the menu, this will save the and accommodate the config. 3. Compile the kernel with "make" and whatever options you want. 3. Compile the kernel modules (if you have chosen to build drivers as modules) with "make modules_install". 5. Install the kernel image in /boot with "make install". Try this and let me know of the results. I'm really interested in fixing this problem myself as well. I have a Legion 7 16ACHg6 (AMD) and speakers don't work on Arch Linux. 4. -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago)
[Touch-packages] [Bug 1958019]
(In reply to Alex from comment #584) > (In reply to henry.hormaza from comment #583) > > Hi, I'm trying the new fedora 36, right now it has the 5.17.0 RC8, what > > should I do to enable the configuration without building the kernel? or is > > just that the RC8 don't have the patch yet? > > I using Fedora 35 right now, I have the Galaxy Book Pro 360, but it has the > ALC298 realtek chip. I tried this patch for the kernel within this bug > report but still didn't work for me. Also, the kernel 5.16.15 still doesn't > seem to have a fix or even 5.17. > > However, this guide works: > https://forum.manjaro.org/t/howto-set-up-the-audio-card-in-samsung-galaxy- > book/37090 > > All I needed to do was install alsa-tools then run the script with the > hda-verbs and after running the script (need to run it a few times) my audio > works from my speakers and headphone. Without this, just audio works from > headphone jack but not from speakers. > > Additionally, after some time maybe 1 hr or so, or, if I exit a page with > audio running, I need to re run the script again to apply the hda-verbs for > my speakers to work. > > Anyways, that worked for me and it might work for you. No need to mess with > any kernel patches. I already have my laptop with sound on fedora 35 (comment 560), I was talking about the kernel 5.17 that will be set in fedora 36. I don't understand how is merged every patch in a new kernel release. -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~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 1958019]
(In reply to henry.hormaza from comment #583) > Hi, I'm trying the new fedora 36, right now it has the 5.17.0 RC8, what > should I do to enable the configuration without building the kernel? or is > just that the RC8 don't have the patch yet? I using Fedora 35 right now, I have the Galaxy Book Pro 360, but it has the ALC298 realtek chip. I tried this patch for the kernel within this bug report but still didn't work for me. Also, the kernel 5.16.15 still doesn't seem to have a fix or even 5.17. However, this guide works: https://forum.manjaro.org/t/howto-set-up-the- audio-card-in-samsung-galaxy-book/37090 All I needed to do was install alsa-tools then run the script with the hda-verbs and after running the script (need to run it a few times) my audio works from my speakers and headphone. Without this, just audio works from headphone jack but not from speakers. Additionally, after some time maybe 1 hr or so, or, if I exit a page with audio running, I need to re run the script again to apply the hda- verbs for my speakers to work. Anyways, that worked for me and it might work for you. No need to mess with any kernel patches. -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~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 1958019]
Hi, I'm trying the new fedora 36, right now it has the 5.17.0 RC8, what should I do to enable the configuration without building the kernel? or is just that the RC8 don't have the patch yet? -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~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 1958019]
(In reply to Mark York from comment #580) > (In reply to vpi from comment #579) > > (In reply to Mark York from comment #578) > > > (In reply to vpi from comment #577) > > > > (In reply to Darin Miller from comment #563) > > > > > *Ubuntu version: > > > > > > > > > > 1) install kernel build tools: > > > > > (https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel): > > > > > > > > > > * sudo apt install libncurses-dev gawk flex bison openssl libssl-dev > > dkms > > > > > libelf-dev libudev-dev libpci-dev libiberty-dev autoconf git > > > > > > > > > > 2) clone the kernel from github and checkout to v5.17 branch (Rather > > > large, > > > > > multiple GB's): > > > > > > > > > > * git clone https://github.com/torvalds/linux.git > > > > > * cd linux > > > > > * git checkout v5.17-rc4 > > > > > > > > > > 3) get the patch and install it: > > > > > > > > > > get the patch form this site and save to "linux" directory: (top > right > > > > > corner "series" button) and use the following "git am ..." line to > > apply > > > > the > > > > > patch: > > > > > > > > > > > > > > > https://patchwork.kernel.org/project/linux-acpi/patch/20220121172431.6876-4- > > > > > sbind...@opensource.cirrus.com/ > > > > > > > > > > * git am Support-Spi-in-i2c-multi-instantiate-driver.patch > > > > > > > > > > 4) load current kernel config and change configuration then run the > > > > > following scripts/config commands: > > > > > > > > > > * make olddefconfig > > > > > * ./scripts/config --enable CONFIG_SERIAL_MULTI_INSTANTIATE > > > > > * ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_I2C > > > > > * ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_SPI > > > > > * ./scripts/config --disable CONFIG_DEBUG_INFO > > > > > * ./scripts/config --set-str CONFIG_SYSTEM_TRUSTED_KEYS "" > > > > > * ./scripts/config --set-str CONFIG_SYSTEM_REVOCATION_KEYS "" > > > > > > > > > > 6) build the kernel > > > > > > > > > > * make -j 16 > > > > > > > > > > 7) install the kernel > > > > > > > > > > * sudo make module_install > > > > > * sudo make install > > > > > > > > Hi guys, > > > > > > > > This is my first time compiling a kernel (Legion 7 16ACHg6/Ubuntu > 20.04). > > I > > > > followed these steps (checked out the v5.17-rc8 branch on git) but at > the > > > > end I am getting this error at the last step, just before running sudo > > make > > > > install: > > > > > > > > arch/x86/Makefile:154: CONFIG_X86_X32 enabled but no binutils support > > > > sh ./arch/x86/boot/install.sh 5.17.0-rc8+ \ > > > > arch/x86/boot/bzImage System.map "/boot" > > > > > > > > *** Missing file: arch/x86/boot/bzImage > > > > *** You need to run "make" before "make install". > > > > > > > > make: *** [arch/x86/Makefile:278: install] Error 1 > > > > > > > > Any help would be appreciated > > > > > > > > > Hello @vpi > > > > > > Before running "make install" you need to compile the kernel with "make". > > > "make install" will install the compiled kernel, so you need to compile > it > > > first. > > > > Hi Mark, > > > > I should've been clearer in my last comment. I followed the instructions > > stepwise, which means I ran "make -j 16" before running "make install". And > > yet I was getting this error. > > Hi vpi, > > I would recommend to start fresh. What I would do is: > 1. Get into the kernel config with "make menuconfig", load the .config file > from the "Load" button at the bottom. > 2. Exit the menu, this will save the and accommodate the config. > 3. Compile the kernel with "make" and whatever options you want. > 3. Compile the kernel modules (if you have chosen to build drivers as > modules) with "make modules_install". > 5. Install the kernel image in /boot with "make install". > > Try this and let me know of the results. I'm really interested in fixing > this problem myself as well. I have a Legion 7 16ACHg6 (AMD) and speakers > don't work on Arch Linux. > 4. I forgot to mention that you should add the patches after loading the conf file. -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio
[Touch-packages] [Bug 1958019]
(In reply to Mark York from comment #578) > (In reply to vpi from comment #577) > > (In reply to Darin Miller from comment #563) > > > *Ubuntu version: > > > > > > 1) install kernel build tools: > > > (https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel): > > > > > > * sudo apt install libncurses-dev gawk flex bison openssl libssl-dev dkms > > > libelf-dev libudev-dev libpci-dev libiberty-dev autoconf git > > > > > > 2) clone the kernel from github and checkout to v5.17 branch (Rather > large, > > > multiple GB's): > > > > > > * git clone https://github.com/torvalds/linux.git > > > * cd linux > > > * git checkout v5.17-rc4 > > > > > > 3) get the patch and install it: > > > > > > get the patch form this site and save to "linux" directory: (top right > > > corner "series" button) and use the following "git am ..." line to apply > > the > > > patch: > > > > > > https://patchwork.kernel.org/project/linux-acpi/patch/20220121172431.6876-4- > > > sbind...@opensource.cirrus.com/ > > > > > > * git am Support-Spi-in-i2c-multi-instantiate-driver.patch > > > > > > 4) load current kernel config and change configuration then run the > > > following scripts/config commands: > > > > > > * make olddefconfig > > > * ./scripts/config --enable CONFIG_SERIAL_MULTI_INSTANTIATE > > > * ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_I2C > > > * ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_SPI > > > * ./scripts/config --disable CONFIG_DEBUG_INFO > > > * ./scripts/config --set-str CONFIG_SYSTEM_TRUSTED_KEYS "" > > > * ./scripts/config --set-str CONFIG_SYSTEM_REVOCATION_KEYS "" > > > > > > 6) build the kernel > > > > > > * make -j 16 > > > > > > 7) install the kernel > > > > > > * sudo make module_install > > > * sudo make install > > > > Hi guys, > > > > This is my first time compiling a kernel (Legion 7 16ACHg6/Ubuntu 20.04). I > > followed these steps (checked out the v5.17-rc8 branch on git) but at the > > end I am getting this error at the last step, just before running sudo make > > install: > > > > arch/x86/Makefile:154: CONFIG_X86_X32 enabled but no binutils support > > sh ./arch/x86/boot/install.sh 5.17.0-rc8+ \ > > arch/x86/boot/bzImage System.map "/boot" > > > > *** Missing file: arch/x86/boot/bzImage > > *** You need to run "make" before "make install". > > > > make: *** [arch/x86/Makefile:278: install] Error 1 > > > > Any help would be appreciated > > > Hello @vpi > > Before running "make install" you need to compile the kernel with "make". > "make install" will install the compiled kernel, so you need to compile it > first. Hi Mark, I should've been clearer in my last comment. I followed the instructions stepwise, which means I ran "make -j 16" before running "make install". And yet I was getting this error. -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO
[Touch-packages] [Bug 1958019]
(In reply to vpi from comment #577) > (In reply to Darin Miller from comment #563) > > *Ubuntu version: > > > > 1) install kernel build tools: > > (https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel): > > > > * sudo apt install libncurses-dev gawk flex bison openssl libssl-dev dkms > > libelf-dev libudev-dev libpci-dev libiberty-dev autoconf git > > > > 2) clone the kernel from github and checkout to v5.17 branch (Rather large, > > multiple GB's): > > > > * git clone https://github.com/torvalds/linux.git > > * cd linux > > * git checkout v5.17-rc4 > > > > 3) get the patch and install it: > > > > get the patch form this site and save to "linux" directory: (top right > > corner "series" button) and use the following "git am ..." line to apply > the > > patch: > > > https://patchwork.kernel.org/project/linux-acpi/patch/20220121172431.6876-4- > > sbind...@opensource.cirrus.com/ > > > > * git am Support-Spi-in-i2c-multi-instantiate-driver.patch > > > > 4) load current kernel config and change configuration then run the > > following scripts/config commands: > > > > * make olddefconfig > > * ./scripts/config --enable CONFIG_SERIAL_MULTI_INSTANTIATE > > * ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_I2C > > * ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_SPI > > * ./scripts/config --disable CONFIG_DEBUG_INFO > > * ./scripts/config --set-str CONFIG_SYSTEM_TRUSTED_KEYS "" > > * ./scripts/config --set-str CONFIG_SYSTEM_REVOCATION_KEYS "" > > > > 6) build the kernel > > > > * make -j 16 > > > > 7) install the kernel > > > > * sudo make module_install > > * sudo make install > > Hi guys, > > This is my first time compiling a kernel (Legion 7 16ACHg6/Ubuntu 20.04). I > followed these steps (checked out the v5.17-rc8 branch on git) but at the > end I am getting this error at the last step, just before running sudo make > install: > > arch/x86/Makefile:154: CONFIG_X86_X32 enabled but no binutils support > sh ./arch/x86/boot/install.sh 5.17.0-rc8+ \ > arch/x86/boot/bzImage System.map "/boot" > > *** Missing file: arch/x86/boot/bzImage > *** You need to run "make" before "make install". > > make: *** [arch/x86/Makefile:278: install] Error 1 > > Any help would be appreciated Hello @vpi Before running "make install" you need to compile the kernel with "make". "make install" will install the compiled kernel, so you need to compile it first. -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias:
[Touch-packages] [Bug 1959047] Re: systemd ignores RootDirectory option in .service units
Is there a chance to SRU a targeted patch for LXD in Bionic to fix the issue instead? -- 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/1959047 Title: systemd ignores RootDirectory option in .service units Status in systemd package in Ubuntu: Confirmed Bug description: The version of systemd (249.5-2ubuntu4) currently packaged for the Ubuntu development version (22.04 Jammy Jellyfish) totally ignores the RootDirectory= option in systemd service files. With RootDirectory, systemd should start the service after calling chroot() on the supplied directory. To test/reproduce, create a test service file with the following contents: # /etc/systemd/system/lsb-release.service [Unit] Description=LSB Release Information [Service] Type=simple RootDirectory=/var/chroot/trusty ExecStartPre=/bin/pwd ExecStart=/usr/bin/lsb_release -a You should have a chroot environment in the specified RootDirectory, even though you can still deduce if systemd attempted to chroot or not from the resulting error message. In my example, I installed an end-of-life Ubuntu 14.04 Trusty Tahr in the chroot environment. On systems NOT affected by the problem, I get the following result when I start this test service. This is what I'd expect. Jan 25 20:40:40 dolly systemd[1]: Starting LSB Release Information... Jan 25 20:40:40 dolly pwd[361]: / Jan 25 20:40:40 dolly systemd[1]: Started LSB Release Information. Jan 25 20:40:40 dolly lsb_release[362]: No LSB modules are available. Jan 25 20:40:40 dolly lsb_release[362]: Distributor ID:Ubuntu Jan 25 20:40:40 dolly lsb_release[362]: Description:Ubuntu 14.04 LTS Jan 25 20:40:40 dolly lsb_release[362]: Release:14.04 Jan 25 20:40:40 dolly lsb_release[362]: Codename:trusty Jan 25 20:40:40 dolly systemd[1]: lsb-release.service: Succeeded. On the problematic system, however, I get the following result. Jan 25 21:21:08 savelog systemd[1]: Starting LSB Release Information... Jan 25 21:21:08 savelog systemd[1]: Started LSB Release Information. Jan 25 21:21:08 savelog pwd[81114]: / Jan 25 21:21:08 savelog lsb_release[81115]: No LSB modules are available. Jan 25 21:21:08 savelog lsb_release[81115]: Distributor ID:Ubuntu Jan 25 21:21:08 savelog lsb_release[81115]: Description:Ubuntu Jammy Jellyfish (development branch) Jan 25 21:21:08 savelog lsb_release[81115]: Release:22.04 Jan 25 21:21:08 savelog lsb_release[81115]: Codename:jammy Jan 25 21:21:08 savelog systemd[1]: lsb-release.service: Deactivated successfully. It totally run the service on the host's root filesystem, it didn't care even the slightest that a RootDirectory is specified. Tested on the following releases / systemd versions: Ubuntu 18.04.6 Bionic Beaver – ISSUE NOT PRESENT systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid Ubuntu 20.04.3 Focal Fossa – ISSUE NOT PRESENT systemd 245 (245.4-4ubuntu3.15) +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid Ubuntu 21.10 Impish Indri – ISSUE NOT PRESENT systemd 248 (248.3-1ubuntu8.2) +PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS -OPENSSL +ACL +BLKID +CURL +ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP -LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified Ubuntu 22.04 Jammy Jellyfish (development branch) – ISSUE PRESENT systemd 249 (249.5-2ubuntu4) +PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS -OPENSSL +ACL +BLKID +CURL +ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP -LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified Note that the problem is produced under an LXC container; since systemd detects virtualization, it might change how it behaves. It's either a bug or an intentional change I don't understand yet (i.e. the RootDirectory option has deprecated and is about to be replaced with something else, or there are additional conditions to be met before RootDirectory is considered), but I think in the latter case I should at least get a warning that there is a change in configuration. I imagine suddenly everyone's existing service units utilizing RootDirectory silently stop working without any information regarding why. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1959047/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1959047] Re: systemd ignores RootDirectory option in .service units
This is caused by https://git.launchpad.net/ubuntu/+source/systemd/tree/debian/patches/debian/UBUNTU- Revert-namespace-be-more-careful-when-handling- namespacin.patch?h=ubuntu/jammy From upstream's point of view, ignoring sandboxing options requested by unit owners is quite dangerous. It can result in programs running completely unconstrained. See: https://github.com/systemd/systemd/issues/22760 ** Bug watch added: github.com/systemd/systemd/issues #22760 https://github.com/systemd/systemd/issues/22760 ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1959047 Title: systemd ignores RootDirectory option in .service units Status in systemd package in Ubuntu: Confirmed Bug description: The version of systemd (249.5-2ubuntu4) currently packaged for the Ubuntu development version (22.04 Jammy Jellyfish) totally ignores the RootDirectory= option in systemd service files. With RootDirectory, systemd should start the service after calling chroot() on the supplied directory. To test/reproduce, create a test service file with the following contents: # /etc/systemd/system/lsb-release.service [Unit] Description=LSB Release Information [Service] Type=simple RootDirectory=/var/chroot/trusty ExecStartPre=/bin/pwd ExecStart=/usr/bin/lsb_release -a You should have a chroot environment in the specified RootDirectory, even though you can still deduce if systemd attempted to chroot or not from the resulting error message. In my example, I installed an end-of-life Ubuntu 14.04 Trusty Tahr in the chroot environment. On systems NOT affected by the problem, I get the following result when I start this test service. This is what I'd expect. Jan 25 20:40:40 dolly systemd[1]: Starting LSB Release Information... Jan 25 20:40:40 dolly pwd[361]: / Jan 25 20:40:40 dolly systemd[1]: Started LSB Release Information. Jan 25 20:40:40 dolly lsb_release[362]: No LSB modules are available. Jan 25 20:40:40 dolly lsb_release[362]: Distributor ID:Ubuntu Jan 25 20:40:40 dolly lsb_release[362]: Description:Ubuntu 14.04 LTS Jan 25 20:40:40 dolly lsb_release[362]: Release:14.04 Jan 25 20:40:40 dolly lsb_release[362]: Codename:trusty Jan 25 20:40:40 dolly systemd[1]: lsb-release.service: Succeeded. On the problematic system, however, I get the following result. Jan 25 21:21:08 savelog systemd[1]: Starting LSB Release Information... Jan 25 21:21:08 savelog systemd[1]: Started LSB Release Information. Jan 25 21:21:08 savelog pwd[81114]: / Jan 25 21:21:08 savelog lsb_release[81115]: No LSB modules are available. Jan 25 21:21:08 savelog lsb_release[81115]: Distributor ID:Ubuntu Jan 25 21:21:08 savelog lsb_release[81115]: Description:Ubuntu Jammy Jellyfish (development branch) Jan 25 21:21:08 savelog lsb_release[81115]: Release:22.04 Jan 25 21:21:08 savelog lsb_release[81115]: Codename:jammy Jan 25 21:21:08 savelog systemd[1]: lsb-release.service: Deactivated successfully. It totally run the service on the host's root filesystem, it didn't care even the slightest that a RootDirectory is specified. Tested on the following releases / systemd versions: Ubuntu 18.04.6 Bionic Beaver – ISSUE NOT PRESENT systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid Ubuntu 20.04.3 Focal Fossa – ISSUE NOT PRESENT systemd 245 (245.4-4ubuntu3.15) +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid Ubuntu 21.10 Impish Indri – ISSUE NOT PRESENT systemd 248 (248.3-1ubuntu8.2) +PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS -OPENSSL +ACL +BLKID +CURL +ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP -LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified Ubuntu 22.04 Jammy Jellyfish (development branch) – ISSUE PRESENT systemd 249 (249.5-2ubuntu4) +PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS -OPENSSL +ACL +BLKID +CURL +ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP -LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified Note that the problem is produced under an LXC container; since systemd detects virtualization, it might change how it behaves. It's either a bug or an intentional change I don't understand yet (i.e. the RootDirectory option has deprecated and is about to be replaced with something else,
[Touch-packages] [Bug 1965535] Re: Stop recommending snap
** Description changed: Currently, ubuntu recommends installing snap by default, and some apps are slowly transitioning from DEB-based installation to Snap-based installation. APT is great, and facilitates having a clean, maintainable system. - The snap project is not very well designed or engineered (just changing the location of where snap data is located is taking the project more than 5 years because it was hardcoded: https://bugs.launchpad.net/snapd/+bug/1575053). Snaps are large and VERY slow. The design of snap, as well as the way decisions are made, are very questionable, and are receiving - increasing amounts of criticism. + The snap project is not very well designed or engineered (just changing + the location of where snap data is located is taking the project more + than 5 years because it was hardcoded: + https://bugs.launchpad.net/snapd/+bug/1575053). Snaps are large and VERY + slow. The design of snap, as well as the way that decisions are made, + are very questionable, and are receiving increasing amounts of + criticism. I'd like to request that Ubuntu stops recommending snap, stops transitioning towards snaps, and we come back to defaulting to DEB/APT- based installation for all apps. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1965535 Title: Stop recommending snap Status in ubuntu-meta package in Ubuntu: Opinion Bug description: Currently, ubuntu recommends installing snap by default, and some apps are slowly transitioning from DEB-based installation to Snap-based installation. APT is great, and facilitates having a clean, maintainable system. The snap project is not very well designed or engineered (just changing the location of where snap data is located is taking the project more than 5 years because it was hardcoded: https://bugs.launchpad.net/snapd/+bug/1575053). Snaps are large and VERY slow. The design of snap, as well as the way that decisions are made, are very questionable, and are receiving increasing amounts of criticism. I'd like to request that Ubuntu stops recommending snap, stops transitioning towards snaps, and we come back to defaulting to DEB/APT-based installation for all apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965535/+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 1965535] Re: Stop recommending snap
** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1965535 Title: Stop recommending snap Status in ubuntu-meta package in Ubuntu: Opinion Bug description: Currently, ubuntu recommends installing snap by default, and some apps are slowly transitioning from DEB-based installation to Snap-based installation. APT is great, and facilitates having a clean, maintainable system. The snap project is not very well designed or engineered (just changing the location of where snap data is located is taking the project more than 5 years because it was hardcoded: https://bugs.launchpad.net/snapd/+bug/1575053). Snaps are large and VERY slow. The design of snap, as well as the way that decisions are made, are very questionable, and are receiving increasing amounts of criticism. I'd like to request that Ubuntu stops recommending snap, stops transitioning towards snaps, and we come back to defaulting to DEB/APT-based installation for all apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965535/+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 1965535] Re: Stop recommending snap
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1965535 Title: Stop recommending snap Status in ubuntu-meta package in Ubuntu: Opinion Bug description: Currently, ubuntu recommends installing snap by default, and some apps are slowly transitioning from DEB-based installation to Snap-based installation. APT is great, and facilitates having a clean, maintainable system. The snap project is not very well designed or engineered (just changing the location of where snap data is located is taking the project more than 5 years because it was hardcoded: https://bugs.launchpad.net/snapd/+bug/1575053). Snaps are large and VERY slow. The design of snap, as well as the way decisions are made, are very questionable, and are receiving increasing amounts of criticism. I'd like to request that Ubuntu stops recommending snap, stops transitioning towards snaps, and we come back to defaulting to DEB/APT-based installation for all apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965535/+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 1850804] Re: Tab completion warnings with ubuntu-bug
Is there any news on this? The problem still happens after upgrading to Ubuntu 22.04. There don't appear to have been updates since I last reported this for 21.10. -- 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/1850804 Title: Tab completion warnings with ubuntu-bug Status in apport package in Ubuntu: Confirmed Bug description: When running ubuntu-bug on the command line, and tab completing the package name, the following warnings are printed: /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Oct 31 10:54:43 2019 InstallationDate: Installed on 2017-08-16 (805 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1850804/+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 1965490] Re: Create multiple profiles per verb for conflicting devices
** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1965490 Title: Create multiple profiles per verb for conflicting devices Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: New Bug description: Please include the following MR to make UCM's ConflictingDevice work properly under PulseAudio. Systems like Lenovo P520c and Lenovo P620 requires the change to make audio port selection logic really work. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/596 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1965490/+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 1965535] Re: Stop recommending snap
** Description changed: Currently, ubuntu recommends installing snap by default, and some apps are slowly transitioning from DEB-based installation to Snap-based installation. APT is great, and facilitates having a clean, maintainable system. - The snap project is not very well designed or engineered (just changing - the location of where snap data is located is taking the project more - than 5 years because it was hardcoded: - https://bugs.launchpad.net/snapd/+bug/1575053). The design of snap, and - many decisions made in the project that impact users, are very - questionable, and snaps are large and VERY slow. + The snap project is not very well designed or engineered (just changing the location of where snap data is located is taking the project more than 5 years because it was hardcoded: https://bugs.launchpad.net/snapd/+bug/1575053). Snaps are large and VERY slow. The design of snap, as well as the way decisions are made, are very questionable, and are receiving + increasing amounts of criticism. I'd like to request that Ubuntu stops recommending snap, stops transitioning towards snaps, and we come back to defaulting to DEB/APT- based installation for all apps. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1965535 Title: Stop recommending snap Status in ubuntu-meta package in Ubuntu: New Bug description: Currently, ubuntu recommends installing snap by default, and some apps are slowly transitioning from DEB-based installation to Snap-based installation. APT is great, and facilitates having a clean, maintainable system. The snap project is not very well designed or engineered (just changing the location of where snap data is located is taking the project more than 5 years because it was hardcoded: https://bugs.launchpad.net/snapd/+bug/1575053). Snaps are large and VERY slow. The design of snap, as well as the way decisions are made, are very questionable, and are receiving increasing amounts of criticism. I'd like to request that Ubuntu stops recommending snap, stops transitioning towards snaps, and we come back to defaulting to DEB/APT-based installation for all apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965535/+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 1965535] [NEW] Stop recommending snap
Public bug reported: Currently, ubuntu recommends installing snap by default, and some apps are slowly transitioning from DEB-based installation to Snap-based installation. APT is great, and facilitates having a clean, maintainable system. The snap project is not very well designed or engineered (just changing the location of where snap data is located is taking the project more than 5 years because it was hardcoded: https://bugs.launchpad.net/snapd/+bug/1575053). The design of snap, and many decisions made in the project that impact users, are very questionable, and snaps are large and VERY slow. I'd like to request that Ubuntu stops recommending snap, stops transitioning towards snaps, and we come back to defaulting to DEB/APT- based installation for all apps. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1965535 Title: Stop recommending snap Status in ubuntu-meta package in Ubuntu: New Bug description: Currently, ubuntu recommends installing snap by default, and some apps are slowly transitioning from DEB-based installation to Snap-based installation. APT is great, and facilitates having a clean, maintainable system. The snap project is not very well designed or engineered (just changing the location of where snap data is located is taking the project more than 5 years because it was hardcoded: https://bugs.launchpad.net/snapd/+bug/1575053). The design of snap, and many decisions made in the project that impact users, are very questionable, and snaps are large and VERY slow. I'd like to request that Ubuntu stops recommending snap, stops transitioning towards snaps, and we come back to defaulting to DEB/APT-based installation for all apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965535/+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 1965526] [NEW] gdb 9.2 silently exits when debugging from within eclipse
Public bug reported: While I was trying to debug a program from eclipse on a 20.04 system, I noticed gdb aborting and stopping the debugged program after a few steps. Turns out this is a gdb bug: https://sourceware.org/bugzilla/show_bug.cgi?id=28711 with a simple fix. I have rebuilt the package locally with the patch, but filing this because I think it could be helpful to others to integrate that patch in the package. ** Affects: gdb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1965526 Title: gdb 9.2 silently exits when debugging from within eclipse Status in gdb package in Ubuntu: New Bug description: While I was trying to debug a program from eclipse on a 20.04 system, I noticed gdb aborting and stopping the debugged program after a few steps. Turns out this is a gdb bug: https://sourceware.org/bugzilla/show_bug.cgi?id=28711 with a simple fix. I have rebuilt the package locally with the patch, but filing this because I think it could be helpful to others to integrate that patch in the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1965526/+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 1965490] Re: Create multiple profiles per verb for conflicting devices
FFe removed as it's a fix to make ALSA UCM device work more properly. ** Summary changed: - [FFe] Create multiple profiles per verb for conflicting devices + Create multiple profiles per verb for conflicting devices -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1965490 Title: Create multiple profiles per verb for conflicting devices Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: New Bug description: Please include the following MR to make UCM's ConflictingDevice work properly under PulseAudio. Systems like Lenovo P520c and Lenovo P620 requires the change to make audio port selection logic really work. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/596 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1965490/+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 1965490] Re: [FFe] Create multiple profiles per verb for conflicting devices
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Tags added: oem-priority -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1965490 Title: [FFe] Create multiple profiles per verb for conflicting devices Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: New Bug description: Please include the following MR to make UCM's ConflictingDevice work properly under PulseAudio. Systems like Lenovo P520c and Lenovo P620 requires the change to make audio port selection logic really work. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/596 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1965490/+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 1965518] [NEW] [USB-Audio - USB Audio, recording] Recording problem
Public bug reported: Microphone when using built in mbo MSI Z690 Edge WiFi DDR4 audio Realtek ALC4080 is not recording audio. What I did found out, that the bar which indicates that something is recording is going up, when I play some sound on ubuntu, so input "thinks" it is output I think. If raport is somehow saying I was not using that mic at the moment, that is because I was using other card which I need to buy, for mic to temporarly work. I rechecked it before sending report, and yes, that original from MBO audio input is still not working. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity Date: Fri Mar 18 10:39:26 2022 InstallationDate: Installed on 2022-03-12 (5 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Audio failed Symptom_Card: USB Audio - USB Audio Symptom_Type: None of the above Title: [USB-Audio - USB Audio, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2021 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.10 dmi.board.asset.tag: Default string dmi.board.name: MPG Z690 EDGE WIFI DDR4 (MS-7D31) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.10:bd12/13/2021:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D31:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ690EDGEWIFIDDR4(MS-7D31):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D31 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Attachment added: "sound_configuration_on_gui.png" https://bugs.launchpad.net/bugs/1965518/+attachment/5570349/+files/sound_configuration_on_gui.png -- 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/1965518 Title: [USB-Audio - USB Audio, recording] Recording problem Status in alsa-driver package in Ubuntu: New Bug description: Microphone when using built in mbo MSI Z690 Edge WiFi DDR4 audio Realtek ALC4080 is not recording audio. What I did found out, that the bar which indicates that something is recording is going up, when I play some sound on ubuntu, so input "thinks" it is output I think. If raport is somehow saying I was not using that mic at the moment, that is because I was using other card which I need to buy, for mic to temporarly work. I rechecked it before sending report, and yes, that original from MBO audio input is still not working. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity Date: Fri Mar 18 10:39:26 2022 InstallationDate: Installed on 2022-03-12 (5 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Audio failed Symptom_Card: USB Audio - USB Audio Symptom_Type: None of the above Title: [USB-Audio - USB Audio, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2021 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.10 dmi.board.asset.tag: Default string dmi.board.name: MPG Z690 EDGE WIFI DDR4 (MS-7D31) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.10:bd12/13/2021:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D31:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ690EDGEWIFIDDR4(MS-7D31):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
[Touch-packages] [Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
logs from live system ** Attachment added: "logs.log" https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+attachment/5570326/+files/logs.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Triaged Bug description: WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1965328] Re: transient scope could not be started error in bionic lxd container
Let me reiterate what I mentioned in the MM channel. The snap in question apparently uses device access in which case we'll set up device filtering. The host being impish, uses cgroup v2, which percolates to the container. Since it's v2, device filtering is implemented by attaching a BPF program on the cgorup, hence we need to have a separate group otherwise we'd break your session. Snap will ask your systemd --user to create a transient scope for the app, but looking at the logs this fails with: Mar 17 16:13:22 b2 systemd[2487]: snap.snapcraft.snapcraft.237e42c2-4906-439b-a992-743647600bc6.scope: Failed to add PIDs to scope's control Mar 17 16:13:22 b2 systemd[2487]: snap.snapcraft.snapcraft.237e42c2-4906-439b-a992-743647600bc6.scope: Failed with result 'resources'. Mar 17 16:13:22 b2 systemd[2487]: Failed to start snap.snapcraft.snapcraft.237e42c2-4906-439b-a992-743647600bc6.scope. At this point running snap will fail and the sandbox cannot be completed. I think the main problem is why create transient scope fails the way it did, and whether systemd from bionic even works properly on a host with unified hierarchy. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1965328 Title: transient scope could not be started error in bionic lxd container Status in Snappy: New Status in systemd package in Ubuntu: New Bug description: On my impish development host machine I tend to use lxd containers to support snap building and other tasks targeting different releases. Today I came to use a bionic container as per usual and found that I could not invoke any snap applications. I installed hello-world as the most simple test of running a snap app: ``` ubuntu@b:~$ hello-world internal error, please report: running "hello-world" failed: transient scope could not be started, job /org/freedesktop/systemd1/job/44 finished with result failed ``` I made sure the container had up to date packages in it (apt & snaps) and rebooted it. But the problem persisted. I then created a second container and installed hello-world in it and again the problem was reproducible. At the time of producing the following attachments I had not attempted to reboot the host. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1965328/+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 1965490] [NEW] [FFe] Create multiple profiles per verb for conflicting devices
Public bug reported: Please include the following MR to make UCM's ConflictingDevice work properly under PulseAudio. Systems like Lenovo P520c and Lenovo P620 requires the change to make audio port selection logic really work. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/596 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1965490 Title: [FFe] Create multiple profiles per verb for conflicting devices Status in pulseaudio package in Ubuntu: New Bug description: Please include the following MR to make UCM's ConflictingDevice work properly under PulseAudio. Systems like Lenovo P520c and Lenovo P620 requires the change to make audio port selection logic really work. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/596 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1965490/+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
