[Touch-packages] [Bug 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller
#9 doesn't seem to be a regression caused by pulseaudio. -- 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/2007331 Title: Fix HFP mSBC support on Realtek Bluetooth USB controller Status in HWE Next: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in pulseaudio source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in pulseaudio source package in Kinetic: Fix Committed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in pulseaudio source package in Lunar: Fix Released Bug description: [Impact] When a BT headset is connected Realtek BT USB controller, HFP profile can't play or record sound when mSBC codec is used. [Fix] At Linux kernel side, add a Realtek specific quirk to support mSBC. At PulseAudio side, send more data frames until the connected device sends response. [Test] Connect different headsets to the said controller, HFP can play and record sounds now. Also verified A2DP profile is unaffected. [Where problems could occur] The kernel part is Realtek specific, so the regression risk is very limited. The pulseaudio side only affects HFP profile, since the codeflow only changes when a mic is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007331/+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 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller
Verified on the following steps: 1) Enabled proposed pocket, upgrade pulseaudio and install oem kernel 6.1.0-1008.8. 2) Reboot. 3) Pair and connect AirPods, play some audio to ensure that A2DP still works. 4) Switch to HFP and I can hear sound. Microphone also works too. 5) Keep switching between A2DP and HFP profile, both of them work all the time. ** Tags removed: verification-needed verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done verification-done-jammy verification-done-kinetic -- 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/2007331 Title: Fix HFP mSBC support on Realtek Bluetooth USB controller Status in HWE Next: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in pulseaudio source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in pulseaudio source package in Kinetic: Fix Committed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in pulseaudio source package in Lunar: Fix Released Bug description: [Impact] When a BT headset is connected Realtek BT USB controller, HFP profile can't play or record sound when mSBC codec is used. [Fix] At Linux kernel side, add a Realtek specific quirk to support mSBC. At PulseAudio side, send more data frames until the connected device sends response. [Test] Connect different headsets to the said controller, HFP can play and record sounds now. Also verified A2DP profile is unaffected. [Where problems could occur] The kernel part is Realtek specific, so the regression risk is very limited. The pulseaudio side only affects HFP profile, since the codeflow only changes when a mic is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007331/+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 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist
** Also affects: software-properties (Ubuntu Lunar)
Importance: Undecided
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1795278
Title:
software-properties-{qt,kde} attempts to use KUrl but it doesn't exist
Status in software-properties package in Ubuntu:
Triaged
Status in software-properties source package in Focal:
Triaged
Status in software-properties source package in Jammy:
Triaged
Status in software-properties source package in Kinetic:
Triaged
Status in software-properties source package in Lunar:
Triaged
Bug description:
Release: Kubuntu 18.04
Version: 0.96.24.32.1
When clicking the "Import Key" button in the "Authentication" section
of the panel it throws this error:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py",
line 667, in add_key_clicked
url = KUrl.fromPath(home)
NameError: name 'KUrl' is not defined
While this doesn't crash the program it causes nothing to happen when
clicking the button. Running the program in a terminal reveals the
error being printed to stderr.
After debugging it appears KUrl doesn't exist anywhere and I'm not
sure if's a python module that has changed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+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 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on
I've created https://github.com/snapcore/snapd/pull/12627 as a proposed fix for the issue. -- 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/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on Status in glib2.0 package in Ubuntu: New Status in ibus package in Ubuntu: New Bug description: Test Case - From Ubuntu 23.04, install glib >= 2.75.3-3 Test 1: Log out Click your name on the login screen. Click the gear button to choose Ubuntu on Xorg Enter your password to finish logging in. Open Firefox (or Chromium) Try to enter text in the address bar. Test 2: Install the ibus-libpinyin package. Log out and log in again. Go to Settings -> Keyboard and add "Chinese (Intelligent Pinyin)" to your input sources. Log out Click your name on the login screen. Click the gear button to choose Ubuntu (on Wayland). Enter your password to finish logging in. Open Firefox (or Chromium) Try to enter text in the address bar. What Happens No text is inputted Other Info -- You see the issue as soon as IBus has been 'turned on'. With the current g-s-d version you need to somehow trigger a need to turn IBus on. In an X11 session IBus is always turned on due to im-config 0.55-1. In a Wayland session you need to tell it to turn IBus on by either adding an IBus input method to your input sources or make use of the Screen Keyboard feature. And I've only seen the issue with the Firefox and Chromium snaps. Warning message if you start firefox from terminal: [Parent 3792, Main Thread] WARNING: Unable to connect to ibus: Could not connect: Permission denied: 'glib warning', file /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:167 (firefox:3792): IBUS-WARNING **: 15:23:11.814: Unable to connect to ibus: Could not connect: Permission denied gnome-settings-daemon - gnome-settings-daemon 44 Beta makes the situation worse since it always turns IBus on in both Wayland and X11, but I reverted https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/27bc0889c so that we could continue with the update. See https://salsa.debian.org/gnome-team/gnome-settings-daemon/-/commit/baeeed93 Before I did that, I tested disabling our patches but it didn't make a difference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+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 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on
Okay. In a clean Lunar VM with glib 2.75.3 installed and ibus enabled as
described in the bug description, I could reproduce the input problems
in Firefox. I saw the following AppArmor denial in the dmesg logs:
[ +0.343553] audit: type=1400 audit(1678248386.012:62):
apparmor="DENIED" operation="connect" profile="snap.firefox.firefox"
name="/home/james/.cache/ibus/dbus-THbBfRNt" pid=2398 comm="pool-
firefox" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
I edited /var/lib/snapd/apparmor/profiles/snap.firefox.firefox and added
the following rule:
@{HOME}/.cache/ibus/dbus-* rw,
After reloading the policy with "apparmor_parser -r
.../snap.firefox.firefox", keyboard input worked again. So that confirms
my guess about the cause of the problem. This is something we can fix
via a snapd update.
Longer term, we should get these snaps using ibus's portal interface,
which is both more secure (i.e. suitable to allow in the desktop
interface) and should be immune to future changes of this type.
--
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/2008279
Title:
glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if
IBus is turned on
Status in glib2.0 package in Ubuntu:
New
Status in ibus package in Ubuntu:
New
Bug description:
Test Case
-
From Ubuntu 23.04, install glib >= 2.75.3-3
Test 1:
Log out
Click your name on the login screen.
Click the gear button to choose Ubuntu on Xorg
Enter your password to finish logging in.
Open Firefox (or Chromium)
Try to enter text in the address bar.
Test 2:
Install the ibus-libpinyin package.
Log out and log in again.
Go to Settings -> Keyboard and add "Chinese (Intelligent Pinyin)"
to your input sources.
Log out
Click your name on the login screen.
Click the gear button to choose Ubuntu (on Wayland).
Enter your password to finish logging in.
Open Firefox (or Chromium)
Try to enter text in the address bar.
What Happens
No text is inputted
Other Info
--
You see the issue as soon as IBus has been 'turned on'. With the current
g-s-d version you need to somehow trigger a need to turn IBus on. In an X11
session IBus is always turned on due to im-config 0.55-1. In a Wayland session
you need to tell it to turn IBus on by either adding an IBus input method to
your input sources or make use of the Screen Keyboard feature.
And I've only seen the issue with the Firefox and Chromium snaps.
Warning message if you start firefox from terminal:
[Parent 3792, Main Thread] WARNING: Unable to connect to ibus: Could
not connect: Permission denied: 'glib warning', file
/build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:167
(firefox:3792): IBUS-WARNING **: 15:23:11.814: Unable to connect to
ibus: Could not connect: Permission denied
gnome-settings-daemon
-
gnome-settings-daemon 44 Beta makes the situation worse since it always turns
IBus on in both Wayland and X11, but I reverted
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/27bc0889c so that
we could continue with the update. See
https://salsa.debian.org/gnome-team/gnome-settings-daemon/-/commit/baeeed93
Before I did that, I tested disabling our patches but it didn't make a
difference.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+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 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist
There is now an MP in software-properties that will fix this bug.
https://code.launchpad.net/~arraybolt3/software-
properties/+git/software-properties/+merge/438504
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1795278
Title:
software-properties-{qt,kde} attempts to use KUrl but it doesn't exist
Status in software-properties package in Ubuntu:
Triaged
Status in software-properties source package in Focal:
Triaged
Status in software-properties source package in Jammy:
Triaged
Status in software-properties source package in Kinetic:
Triaged
Bug description:
Release: Kubuntu 18.04
Version: 0.96.24.32.1
When clicking the "Import Key" button in the "Authentication" section
of the panel it throws this error:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py",
line 667, in add_key_clicked
url = KUrl.fromPath(home)
NameError: name 'KUrl' is not defined
While this doesn't crash the program it causes nothing to happen when
clicking the button. Running the program in a terminal reveals the
error being printed to stderr.
After debugging it appears KUrl doesn't exist anywhere and I'm not
sure if's a python module that has changed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+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 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist
** Merge proposal linked:
https://code.launchpad.net/~arraybolt3/software-properties/+git/software-properties/+merge/438504
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1795278
Title:
software-properties-{qt,kde} attempts to use KUrl but it doesn't exist
Status in software-properties package in Ubuntu:
Triaged
Status in software-properties source package in Focal:
Triaged
Status in software-properties source package in Jammy:
Triaged
Status in software-properties source package in Kinetic:
Triaged
Bug description:
Release: Kubuntu 18.04
Version: 0.96.24.32.1
When clicking the "Import Key" button in the "Authentication" section
of the panel it throws this error:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py",
line 667, in add_key_clicked
url = KUrl.fromPath(home)
NameError: name 'KUrl' is not defined
While this doesn't crash the program it causes nothing to happen when
clicking the button. Running the program in a terminal reveals the
error being printed to stderr.
After debugging it appears KUrl doesn't exist anywhere and I'm not
sure if's a python module that has changed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+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 2009637] Re: package libgl1-mesa-dri 22.3.6-1ubuntu1 failed to install/upgrade: intentando sobreescribir `/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', que está también en el paque
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2009637 Title: package libgl1-mesa-dri 22.3.6-1ubuntu1 failed to install/upgrade: intentando sobreescribir `/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', que está también en el paquete libgl1-amber-dri:amd64 21.3.7-0ubuntu1 Status in mesa package in Ubuntu: Confirmed Bug description: Solved with a simple “apt --fix-broken install” but still… ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgl1-mesa-dri 22.3.6-1ubuntu1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None Date: Tue Mar 7 15:25:16 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ErrorMessage: intentando sobreescribir `/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', que está también en el paquete libgl1-amber-dri:amd64 21.3.7-0ubuntu1 ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [103c:84e7] InstallationDate: Installed on 2023-02-13 (22 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209) MachineType: HP HP Pavilion Laptop 15-cw0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic root=UUID=782cbb37-7870-44d8-aa55-53fdff89ddf8 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.20ubuntu2 apt 2.5.6 SourcePackage: mesa Title: package libgl1-mesa-dri 22.3.6-1ubuntu1 failed to install/upgrade: intentando sobreescribir `/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', que está también en el paquete libgl1-amber-dri:amd64 21.3.7-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2021 dmi.bios.release: 15.46 dmi.bios.vendor: AMI dmi.bios.version: F.46 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 84E7 dmi.board.vendor: HP dmi.board.version: 99.30 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 99.30 dmi.modalias: dmi:bvnAMI:bvrF.46:bd01/04/2021:br15.46:efr99.30:svnHP:pnHPPavilionLaptop15-cw0xxx:pvr:rvnHP:rn84E7:rvr99.30:cvnHP:ct10:cvrChassisVersion:sku3PY37LA#ABM: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cw0xxx dmi.product.sku: 3PY37LA#ABM dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2009637/+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 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on
This seems like the most likely culprit: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3005 This basically means that code that would have created an abstract namespace socket in glib 2.74.x now creates a regular unix domain socket in 2.75.x. We have AppArmor rules in snapd's desktop-legacy interface granting access to the abstract namespace socket in $XDG_CACHE_HOME, but nothing for the equivalent regular socket: https://github.com/snapcore/snapd/blob/d5f47ca71fcd8a884072e75391a7e55d9ec9d145/interfaces/builtin/desktop_legacy.go#L142-L149 I still need to verify this is the actual cause, but if so it should be relatively simple to update snapd's AppArmor rules to allow access to this socket. -- 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/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on Status in glib2.0 package in Ubuntu: New Status in ibus package in Ubuntu: New Bug description: Test Case - From Ubuntu 23.04, install glib >= 2.75.3-3 Test 1: Log out Click your name on the login screen. Click the gear button to choose Ubuntu on Xorg Enter your password to finish logging in. Open Firefox (or Chromium) Try to enter text in the address bar. Test 2: Install the ibus-libpinyin package. Log out and log in again. Go to Settings -> Keyboard and add "Chinese (Intelligent Pinyin)" to your input sources. Log out Click your name on the login screen. Click the gear button to choose Ubuntu (on Wayland). Enter your password to finish logging in. Open Firefox (or Chromium) Try to enter text in the address bar. What Happens No text is inputted Other Info -- You see the issue as soon as IBus has been 'turned on'. With the current g-s-d version you need to somehow trigger a need to turn IBus on. In an X11 session IBus is always turned on due to im-config 0.55-1. In a Wayland session you need to tell it to turn IBus on by either adding an IBus input method to your input sources or make use of the Screen Keyboard feature. And I've only seen the issue with the Firefox and Chromium snaps. Warning message if you start firefox from terminal: [Parent 3792, Main Thread] WARNING: Unable to connect to ibus: Could not connect: Permission denied: 'glib warning', file /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:167 (firefox:3792): IBUS-WARNING **: 15:23:11.814: Unable to connect to ibus: Could not connect: Permission denied gnome-settings-daemon - gnome-settings-daemon 44 Beta makes the situation worse since it always turns IBus on in both Wayland and X11, but I reverted https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/27bc0889c so that we could continue with the update. See https://salsa.debian.org/gnome-team/gnome-settings-daemon/-/commit/baeeed93 Before I did that, I tested disabling our patches but it didn't make a difference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+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 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on
I think last time we had problems like this it was due to changes in the location of the socket for ibus's private D-Bus bus. Looking into the glib diffs for clues. -- 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/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on Status in glib2.0 package in Ubuntu: New Status in ibus package in Ubuntu: New Bug description: Test Case - From Ubuntu 23.04, install glib >= 2.75.3-3 Test 1: Log out Click your name on the login screen. Click the gear button to choose Ubuntu on Xorg Enter your password to finish logging in. Open Firefox (or Chromium) Try to enter text in the address bar. Test 2: Install the ibus-libpinyin package. Log out and log in again. Go to Settings -> Keyboard and add "Chinese (Intelligent Pinyin)" to your input sources. Log out Click your name on the login screen. Click the gear button to choose Ubuntu (on Wayland). Enter your password to finish logging in. Open Firefox (or Chromium) Try to enter text in the address bar. What Happens No text is inputted Other Info -- You see the issue as soon as IBus has been 'turned on'. With the current g-s-d version you need to somehow trigger a need to turn IBus on. In an X11 session IBus is always turned on due to im-config 0.55-1. In a Wayland session you need to tell it to turn IBus on by either adding an IBus input method to your input sources or make use of the Screen Keyboard feature. And I've only seen the issue with the Firefox and Chromium snaps. Warning message if you start firefox from terminal: [Parent 3792, Main Thread] WARNING: Unable to connect to ibus: Could not connect: Permission denied: 'glib warning', file /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:167 (firefox:3792): IBUS-WARNING **: 15:23:11.814: Unable to connect to ibus: Could not connect: Permission denied gnome-settings-daemon - gnome-settings-daemon 44 Beta makes the situation worse since it always turns IBus on in both Wayland and X11, but I reverted https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/27bc0889c so that we could continue with the update. See https://salsa.debian.org/gnome-team/gnome-settings-daemon/-/commit/baeeed93 Before I did that, I tested disabling our patches but it didn't make a difference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+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 806880] Re: make_bak_dir mkdir failed: File exists (17)
The rsync versions mentioned in the bug are very old and the distro version they came with, long out of support. As such, I'll mark the issue as incomplete until this can be reproduced/confirmed with a recent/supported version. Thanks! ** Changed in: rsync (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/806880 Title: make_bak_dir mkdir failed: File exists (17) Status in rsync package in Ubuntu: Incomplete Bug description: I have an rsync-based backup routine. Today I had the following error: $ rsync -F -h -av --backup --delete --delete-excluded --force --backup-dir=/media/2TBBackup/backup/.versions/media/hp320/Skannat#2011-07-07#11:21:33 --exclude=*.o --exclude=*~ --exclude=#* /media/hp320/Skannat /media/2TBBackup/backup/media/hp320 sending incremental file list Skannat/neg004c/im4114-2.tif.xmp Skannat/neg004c/im4115-2.tif.xmp Skannat/neg004c/im4116-2.tif.xmp Skannat/neg004c/im4123-2.tif.xmp Skannat/neg005c/im4044-2.tif.xmp [...] Skannat/neg023/2003bfl-0169-imh235.tif.xmp rsync: make_bak_dir mkdir "/media/2TBBackup/backup/.versions/media/hp320/Skannat#2011-07-07#11:21:33" failed: File exists (17) rsync: keep_backup failed: "/media/2TBBackup/backup/media/hp320/Skannat/neg004c/im4114-2.tif.xmp" -> "/media/2TBBackup/backup/.versions/media/hp320/Skannat#2011-07-07#11:21:33/Skannat/neg004c/im4114-2.tif.xmp": No such file or directory (2) rsync: stat "/media/2TBBackup/backup/.versions/media/hp320/Skannat#2011-07-07#11:21:33/Skannat/neg004c/im4114-2.tif.xmp" failed: No such file or directory (2) ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: rsync 3.0.7-2ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11 Uname: Linux 2.6.35-28-generic x86_64 Architecture: amd64 Date: Thu Jul 7 11:26:57 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate amd64 (20100928.1) SourcePackage: rsync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/806880/+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 1404635] Re: rsync: recv_generator: mkdir error with folder ending with space
I'll mark this old bug as fix released because I can't reproduce it on 20.04 (3.1.3) nor 22.04 (rsync 3.2.7). Here's how I tested it on 20.04: # rsync --version rsync version 3.1.3 protocol version 31 ... # mkdir -p "src/a " dst # rsync -aiv src/ dst/ sending incremental file list .d..t.. ./ cd+ a / sent 73 bytes received 23 bytes 192.00 bytes/sec total size is 0 speedup is 0.00 # ls -l dst/ total 1 drwxr-xr-x 2 root root 2 Mar 8 00:30 'a ' ** Changed in: rsync (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1404635 Title: rsync: recv_generator: mkdir error with folder ending with space Status in rsync package in Ubuntu: Fix Released Bug description: Hi, I notice what rsync is not able to copy folder which ending with space : Example which not working : rsync: recv_generator: mkdir "/var/Janji feat. T.R. " failed: Invalid argument (22) *** Skipping any contents from this failed directory *** If I remove space at the end, it works. mkdir can create folder with space at the end. rsync version 3.1.0 protocol version 31 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1404635/+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 2005124] Re: package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubunt
This bug was fixed in the package fontconfig - 2.14.1-3ubuntu3 --- fontconfig (2.14.1-3ubuntu3) lunar; urgency=medium * Implement the transition of available config files from /etc to /usr after a decade of delay (LP: #2007124). fontconfig (2.14.1-3ubuntu2) lunar; urgency=medium * debian/control: - Make fontconfig-config break/replace kubuntu-settings-desktop << 1:23.04.3 to handle symlink conflict (LP: #2005124). -- Gunnar Hjalmarsson Thu, 23 Feb 2023 15:54:28 +0100 ** Changed in: fontconfig (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2005124 Title: package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubuntu-settings-desktop 1:23.04.2 Status in fontconfig package in Ubuntu: Fix Released Status in kubuntu-settings package in Ubuntu: Fix Released Status in fontconfig package in Debian: Unknown Bug description: I don't know ProblemType: Package DistroRelease: Ubuntu 23.04 Package: fontconfig-config 2.13.1-4.4ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Feb 4 05:59:53 2023 DuplicateSignature: package:fontconfig-config:2.13.1-4.4ubuntu1 Unpacking fontconfig-config (2.14.1-3ubuntu1) over (2.13.1-4.4ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-xn7IM4/015-fontconfig-config_2.14.1-3ubuntu1_amd64.deb (--unpack): trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubuntu-settings-desktop 1:23.04.2 ErrorMessage: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubuntu-settings-desktop 1:23.04.2 InstallationDate: Installed on 2023-01-31 (3 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230130) PackageArchitecture: all Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.19ubuntu3 apt 2.5.5 SourcePackage: fontconfig Title: package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubuntu-settings-desktop 1:23.04.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124/+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 2007124] Re: Move available config files from /etc to /usr
This bug was fixed in the package fontconfig - 2.14.1-3ubuntu3 --- fontconfig (2.14.1-3ubuntu3) lunar; urgency=medium * Implement the transition of available config files from /etc to /usr after a decade of delay (LP: #2007124). fontconfig (2.14.1-3ubuntu2) lunar; urgency=medium * debian/control: - Make fontconfig-config break/replace kubuntu-settings-desktop << 1:23.04.3 to handle symlink conflict (LP: #2005124). -- Gunnar Hjalmarsson Thu, 23 Feb 2023 15:54:28 +0100 ** Changed in: fontconfig (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2007124 Title: Move available config files from /etc to /usr Status in fontconfig package in Ubuntu: Fix Released Bug description: At the upgrade to fontconfig 2.10 a decade ago, the directory for storing available config files was changed from /etc/fonts/conf.avail to /usr/share/fontconfig/conf.avail. It was done upstream as well as in Debian, but Ubuntu delayed the transition for some reason. I think we should do that transition in Ubuntu too. That will get Ubuntu in sync with the upstream documentation and the delta to Debian gets reduced a little. The changes needed are straightforward. I put a proposed upload in this PPA: https://launchpad.net/~gunnarhj/+archive/ubuntu/fontconfig and I would appreciate someone's eyes on it. So, what's the caveat? The only thing I can think of is that distros, system admins and individual users may have tweaked the font configuration by including symlinks which point to the moved files. While I don't have the impression that such symlinks are very frequent — custom conf files put directly in /etc/fonts/conf.d or equivalent places in $HOME seem to be more common — to the extent they exist, they will be silently disabled. Bug #2005124 revealed an example of a symlink which pointed to a file which will be moved if we do this. OTOH, in that case upstream added a symlink with the very same name, so we had to deal with that conflict. If the name of Kubuntu's link had been something else, we might not be aware of it yet. The changelog for this upload: https://launchpad.net/ubuntu/+source/fontconfig/2.10.1-0ubuntu1 states that the transition will be done "later with another upload once the details are sorted". Are there other details which I have missed? If not, I suppose that the potential inconvenience is approximately as big today as it was 2012. And since next LTS release is more than one year ahead, this ought to be an appropriate time to make the change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2007124/+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 2009637] [NEW] package libgl1-mesa-dri 22.3.6-1ubuntu1 failed to install/upgrade: intentando sobreescribir `/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', que está también en el paq
Public bug reported: Solved with a simple “apt --fix-broken install” but still… ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgl1-mesa-dri 22.3.6-1ubuntu1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None Date: Tue Mar 7 15:25:16 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ErrorMessage: intentando sobreescribir `/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', que está también en el paquete libgl1-amber-dri:amd64 21.3.7-0ubuntu1 ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [103c:84e7] InstallationDate: Installed on 2023-02-13 (22 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209) MachineType: HP HP Pavilion Laptop 15-cw0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic root=UUID=782cbb37-7870-44d8-aa55-53fdff89ddf8 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.20ubuntu2 apt 2.5.6 SourcePackage: mesa Title: package libgl1-mesa-dri 22.3.6-1ubuntu1 failed to install/upgrade: intentando sobreescribir `/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', que está también en el paquete libgl1-amber-dri:amd64 21.3.7-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2021 dmi.bios.release: 15.46 dmi.bios.vendor: AMI dmi.bios.version: F.46 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 84E7 dmi.board.vendor: HP dmi.board.version: 99.30 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 99.30 dmi.modalias: dmi:bvnAMI:bvrF.46:bd01/04/2021:br15.46:efr99.30:svnHP:pnHPPavilionLaptop15-cw0xxx:pvr:rvnHP:rn84E7:rvr99.30:cvnHP:ct10:cvrChassisVersion:sku3PY37LA#ABM: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cw0xxx dmi.product.sku: 3PY37LA#ABM dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar single-occurrence ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2009637 Title: package libgl1-mesa-dri 22.3.6-1ubuntu1 failed to install/upgrade: intentando sobreescribir `/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', que está también en el paquete libgl1-amber-dri:amd64 21.3.7-0ubuntu1 Status in mesa package in Ubuntu: New Bug description: Solved with a simple “apt --fix-broken install” but still… ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgl1-mesa-dri 22.3.6-1ubuntu1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None Date: Tue Mar 7 15:25:16 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ErrorMessage: intentando sobreescribir `/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', que está también en el paquete libgl1-amber-dri:amd64 21.3.7-0ubuntu1 ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [103c:84e7] InstallationDate: Installed on 2023-02-13 (22 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209) MachineType: HP HP Pavilion Laptop 15-cw0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic root=UUID=782cbb37-7870-44d8-aa55-53fdff89ddf8 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.20ubuntu2 apt 2.5.6 SourcePackage: mesa Title: package libgl1-mesa-dri 22.3.6-1ubuntu1 failed to install/upgrade:
[Touch-packages] [Bug 2007913] Re: HDMI Output sound has disappeared after Ubuntu update
You select your kernel in the grub boot menu. There is an option for alternative boot configurations. I have a dual boot environment set up so grub comes up every time for me. I think you hit esc to bring it up if it normally boots straight into windows. If you have any trouble it should come up in a search pretty quick. -- 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/2007913 Title: HDMI Output sound has disappeared after Ubuntu update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After months using the HDMI output without problems, it has stopped working after a system update two days ago. HDMI output is not listed in the list of available output devices. Same computer works with this sound output perfectly when booting with Windows or an older installation of Ubuntu (18.04). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 21 08:12:58 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-30 (296 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M01EWR120 dmi.board.asset.tag: OEM Default string000 dmi.board.name: OEM Default string000 dmi.board.vendor: OEM Default string000 dmi.board.version: OEM Default string000 dmi.chassis.asset.tag: OEM Default string000 dmi.chassis.type: 10 dmi.chassis.vendor: OEM Default string000 dmi.chassis.version: OEM Default string000 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000: dmi.product.family: OEM Default string000 dmi.product.name: CoreBox dmi.product.sku: OEM Default string000 dmi.product.version: OEM Default string000 dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+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 2009630] Re: package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-a
*** This bug is a duplicate of bug 2006744 *** https://bugs.launchpad.net/bugs/2006744 ** This bug has been marked a duplicate of bug 2006744 libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file conflict -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2009630 Title: package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 Status in mesa package in Ubuntu: New Bug description: Happens while using firefox, terminal (apt upgrade) and sudoku. Not sure what exactly trigerred that. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Tue Mar 7 21:38:45 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu DpkgTerminalLog: Preparing to unpack .../0-libgl1-mesa-dri_22.3.6-1ubuntu1_amd64.deb ... Unpacking libgl1-mesa-dri:amd64 (22.3.6-1ubuntu1) over (22.2.5-0ubuntu1) ... [1mdpkg:[0m error processing archive /tmp/apt-dpkg-install-CwQPZK/0-libgl1-mesa-dri_22.3.6-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2023-03-07 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230301.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic root=UUID=78e3203a-6ffc-477c-a477-6808bd319007 ro quiet splash Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.19ubuntu3 apt 2.5.5 SourcePackage: mesa Title: package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2009630/+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 1826294] Re: os-prober exits prematurely with "logger: socket /dev/log: Protocol wrong type for socket"
This bug was fixed in the package os-prober - 1.81ubuntu2
---
os-prober (1.81ubuntu2) lunar; urgency=medium
* Ignore logger socket-errors to workaround apparmor denials. (LP:
#1826294)
-- Dimitri John Ledkov Tue, 07 Mar 2023
13:28:14 +
** Changed in: os-prober (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1826294
Title:
os-prober exits prematurely with "logger: socket /dev/log: Protocol
wrong type for socket"
Status in AppArmor Profiles:
New
Status in os-prober package in Ubuntu:
Fix Released
Status in rsyslog package in Ubuntu:
New
Bug description:
Failure occurs on Ubuntu 16.04 with the apparmor-
profiles-2.10.95-0ubuntu2.10 package installed.
Running update-grub will run /usr/bin/os-prober, which spews about a
dozen of the following line to stderr:
logger: socket /dev/log: Protocol wrong type for socket
… but fails to report the existence of some installed operating
systems as expected.
Furthermore, /var/log/messages contains:
kernel: audit: type=1400 audit(1556043066.679:11460):
apparmor="ALLOWED" operation="sendmsg" info="Failed name lookup -
disconnected path" error=-13 profile="syslog-ng" name="dev/log"
pid=28566 comm="logger" requested_mask="r" denied_mask="r" fsuid=0
ouid=0
Here is a stripped-down skeleton of the /usr/bin/os-prober script, which
demonstrates the problem:
#!/bin/sh
set -e -x
newns () {
[ "$OS_PROBER_NEWNS" ] || exec /usr/lib/os-prober/newns "$0" "$@"
}
log() {
logger -t "$(basename "$0")" "$@"
}
debug() {
log "debug: $@"
}
ls -l /dev/log
debug "Hello world"
newns "$@"
The expected behavior is that it should write "debug: os-prober-
testcase Hello world" to /var/log/messages twice. However, it only
succeeds in writing "Hello world" once. After the script respawns
itself with /usr/lib/os-prober/newns (which is like `unshare -m`), the
second attempt to write to /dev/log fails as described above.
Since the os-prober Bash script runs with the -e flag, any error, even
just a logging error, causes the script to terminate prematurely.
(Arguably, the log() function should call `logger -t "$(basename
"$0")" "$@" || :` so that logging failures aren't fatal.)
The fix, for me, is to edit /etc/apparmor.d/sbin.syslog-ng, and change
profile syslog-ng /{usr/,}sbin/syslog-ng flags=(complain) {\
…
}
to
profile syslog-ng /{usr/,}sbin/syslog-ng
flags=(complain,attach_disconnected) {
…
}
… then run `aa-complain sbin.syslog-ng` and `service syslog-ng
restart`, before running update-grub again. I assume that similar
fixes would be required for the other logging daemons.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor-profiles/+bug/1826294/+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 2009630] [NEW] package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1
Public bug reported: Happens while using firefox, terminal (apt upgrade) and sudoku. Not sure what exactly trigerred that. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Tue Mar 7 21:38:45 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu DpkgTerminalLog: Preparing to unpack .../0-libgl1-mesa-dri_22.3.6-1ubuntu1_amd64.deb ... Unpacking libgl1-mesa-dri:amd64 (22.3.6-1ubuntu1) over (22.2.5-0ubuntu1) ... [1mdpkg:[0m error processing archive /tmp/apt-dpkg-install-CwQPZK/0-libgl1-mesa-dri_22.3.6-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2023-03-07 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230301.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic root=UUID=78e3203a-6ffc-477c-a477-6808bd319007 ro quiet splash Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.19ubuntu3 apt 2.5.5 SourcePackage: mesa Title: package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar single-occurrence ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2009630 Title: package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 Status in mesa package in Ubuntu: New Bug description: Happens while using firefox, terminal (apt upgrade) and sudoku. Not sure what exactly trigerred that. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Tue Mar 7 21:38:45 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu DpkgTerminalLog: Preparing to unpack .../0-libgl1-mesa-dri_22.3.6-1ubuntu1_amd64.deb ... Unpacking libgl1-mesa-dri:amd64 (22.3.6-1ubuntu1) over (22.2.5-0ubuntu1) ... [1mdpkg:[0m error processing archive /tmp/apt-dpkg-install-CwQPZK/0-libgl1-mesa-dri_22.3.6-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package
[Touch-packages] [Bug 2008952] Re: DNS failure while trying to fetch user-data
** Tags added: rls-ll-incoming -- 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/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: New Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 2008952] Re: DNS failure while trying to fetch user-data
Looking at the desktop ISOs, while the system is configured with Netplan to use NetworkManager, there seems to be some conflict here where systemd-networkd is trying to interact with the device. Some feedback would be appreciated. The practical result is that early boot cloud- init is not able to fetch data that it should be able to retrieve. ** Also affects: netplan Importance: Undecided Status: New ** 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/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: New Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps on Xorg
** Description changed: Test Case - From Ubuntu 23.04, install glib >= 2.75.3-3 + + Test 1: Log out Click your name on the login screen. Click the gear button to choose Ubuntu on Xorg Enter your password to finish logging in. Open Firefox (or Chromium) Try to enter text in the address bar. + Test 2: + Install the ibus-libpinyin package. + Log out and log in again. + Go to Settings -> Keyboard and add "Chinese (Intelligent Pinyin)" + to your input sources. + Log out + Click your name on the login screen. + Click the gear button to choose Ubuntu (on Wayland). + Enter your password to finish logging in. + Open Firefox (or Chromium) + Try to enter text in the address bar. + What Happens - No text is input + No text is inputted Other Info -- - This issue appears to only affects the Xorg session. + You see the issue as soon as IBus has been 'turned on'. With the current g-s-d version you need to somehow trigger a need to turn IBus on. In an X11 session IBus is always turned on due to im-config 0.55-1. In a Wayland session you need to tell it to turn IBus on by either adding an IBus input method to your input sources or make use of the Screen Keyboard feature. And I've only seen the issue with the Firefox and Chromium snaps. + Warning message if you start firefox from terminal: + + [Parent 3792, Main Thread] WARNING: Unable to connect to ibus: Could not + connect: Permission denied: 'glib warning', file + /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:167 + + (firefox:3792): IBUS-WARNING **: 15:23:11.814: Unable to connect to + ibus: Could not connect: Permission denied + gnome-settings-daemon - - It also affected the Wayland session with gnome-settings-daemon 44 Beta, but I reverted https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/27bc0889c so that we could continue with the update. See https://salsa.debian.org/gnome-team/gnome-settings-daemon/-/commit/baeeed93 + gnome-settings-daemon 44 Beta makes the situation worse since it always turns IBus on in both Wayland and X11, but I reverted https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/27bc0889c so that we could continue with the update. See https://salsa.debian.org/gnome-team/gnome-settings-daemon/-/commit/baeeed93 Before I did that, I tested disabling our patches but it didn't make a difference. - - The issue happens with kinetic's gnome-settings-daemon 43; it just looks - like the gnome-settings-daemon commit made the situation worse but that - commit was reverted. ** Summary changed: - glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps on Xorg + glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps ** Summary changed: - glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps + glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on -- 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/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on Status in glib2.0 package in Ubuntu: New Status in ibus package in Ubuntu: New Bug description: Test Case - From Ubuntu 23.04, install glib >= 2.75.3-3 Test 1: Log out Click your name on the login screen. Click the gear button to choose Ubuntu on Xorg Enter your password to finish logging in. Open Firefox (or Chromium) Try to enter text in the address bar. Test 2: Install the ibus-libpinyin package. Log out and log in again. Go to Settings -> Keyboard and add "Chinese (Intelligent Pinyin)" to your input sources. Log out Click your name on the login screen. Click the gear button to choose Ubuntu (on Wayland). Enter your password to finish logging in. Open Firefox (or Chromium) Try to enter text in the address bar. What Happens No text is inputted Other Info -- You see the issue as soon as IBus has been 'turned on'. With the current g-s-d version you need to somehow trigger a need to turn IBus on. In an X11 session IBus is always turned on due to im-config 0.55-1. In a Wayland session you need to tell it to turn IBus on by either adding an IBus input method to your input sources or make use of the Screen Keyboard feature. And I've only seen the issue with the Firefox and Chromium snaps. Warning message if you start firefox from terminal: [Parent 3792, Main Thread] WARNING: Unable to connect to ibus: Could not connect: Permission denied: 'glib warning', file /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:167 (firefox:3792): IBUS-WARNING **: 15:23:11.814: Unable to connect to ibus: Could not connect: Permission denied gnome-settings-daemon - gnome-settings-daemon 44 Beta makes the
[Touch-packages] [Bug 2009575] Re: Upgrade to 3.1.3-8ubuntu0.5 causing sync errors
So after looking further into the way the systems affected by this issue are configured, this is what is happening: 1- rsync client is requesting a directory: rsync -v -rp sshuser@server:/var/cache/foo /tmp/foo 2- the server has an ssh forced command configured that is returning the contents of a different directory: rsync --server --sender -pr . /var/cache/bar 3- The updated rsync client now gets files from a different directory than what was requested, and is bailing out The CVE-2022-29154 security update now validates that the server returns a list of files that match the list of files that were requested, instead of blindly accepting what the server sends, so I'm pretty confident the error message is normal. I will be recreating this scenario to confirm. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-29154 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/2009575 Title: Upgrade to 3.1.3-8ubuntu0.5 causing sync errors Status in rsync package in Ubuntu: Confirmed Bug description: Hi Several systems running Ubuntu 20.04 upgraded their rsync package from 3.1.3-8ubuntu0.4 to 3.1.3-8ubuntu0.5 overnight. Automated syncs that connect to a 16.04 ESM server are now failing with: receiving file list ... ERROR: rejecting unrequested file-list name: [redacted] rsync error: protocol incompatibility (code 2) at flist.c(916) [Receiver=3.1.3] Reverting to the previous release (3.1.3-8ubuntu0.4) on the client side solves the problem. This has been seen on multiple servers running 20.04 on amd64, I'll update this bug with details if we find it on other series too. The 16.04 ESM server being connected to is using the rsync package version 3.1.1-3ubuntu1.3+esm2, so no recent upgrades on that end. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2009575/+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 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps
** Description changed: Test Case - + From Ubuntu 23.04, install glib >= 2.75.3-3 + Log out + Click your name on the login screen. + Click the gear button to choose Ubuntu on Xorg + Enter your password to finish logging in. + Open Firefox (or Chromium) + Try to enter text in the address bar. + What Happens + + No text is input - Original Bug Report - --- - While preparing the gnome-settings-daemon 44 Beta update for Ubuntu 23.04, I noticed that I could no longer enter text in the address bars for the Chromium or Firefox snaps. + Other Info + -- + This issue appears to only affects the Xorg session. - Therefore, I reverted https://gitlab.gnome.org/GNOME/gnome-settings- + It also affected the Wayland session with gnome-settings-daemon 44 Beta, + but I reverted https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/commit/27bc0889c so that we could continue with the update. See https://salsa.debian.org/gnome-team/gnome-settings- daemon/-/commit/baeeed93 Before I did that, I tested disabling our patches but it didn't make a difference. - I was unable to reproduce the issue on Debian Testing but there may have - been differences in how snap was configured there. - - I'm filing this bug since ideally we would not be diverging from - upstream here. + The issue happens with kinetic's gnome-settings-daemon 43; it just looks + like the gnome-settings-daemon commit made the situation worse but that + commit was reverted. ** Description changed: Test Case - From Ubuntu 23.04, install glib >= 2.75.3-3 Log out Click your name on the login screen. Click the gear button to choose Ubuntu on Xorg Enter your password to finish logging in. Open Firefox (or Chromium) Try to enter text in the address bar. What Happens No text is input Other Info -- This issue appears to only affects the Xorg session. - It also affected the Wayland session with gnome-settings-daemon 44 Beta, - but I reverted https://gitlab.gnome.org/GNOME/gnome-settings- - daemon/-/commit/27bc0889c so that we could continue with the update. See - https://salsa.debian.org/gnome-team/gnome-settings- - daemon/-/commit/baeeed93 + And I've only seen the issue with the Firefox and Chromium snaps. + + gnome-settings-daemon + - + It also affected the Wayland session with gnome-settings-daemon 44 Beta, but I reverted https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/27bc0889c so that we could continue with the update. See https://salsa.debian.org/gnome-team/gnome-settings-daemon/-/commit/baeeed93 Before I did that, I tested disabling our patches but it didn't make a difference. The issue happens with kinetic's gnome-settings-daemon 43; it just looks like the gnome-settings-daemon commit made the situation worse but that commit was reverted. ** Summary changed: - glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps + glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps on Xorg -- 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/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps on Xorg Status in glib2.0 package in Ubuntu: New Status in ibus package in Ubuntu: New Bug description: Test Case - From Ubuntu 23.04, install glib >= 2.75.3-3 Log out Click your name on the login screen. Click the gear button to choose Ubuntu on Xorg Enter your password to finish logging in. Open Firefox (or Chromium) Try to enter text in the address bar. What Happens No text is input Other Info -- This issue appears to only affects the Xorg session. And I've only seen the issue with the Firefox and Chromium snaps. gnome-settings-daemon - It also affected the Wayland session with gnome-settings-daemon 44 Beta, but I reverted https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/27bc0889c so that we could continue with the update. See https://salsa.debian.org/gnome-team/gnome-settings-daemon/-/commit/baeeed93 Before I did that, I tested disabling our patches but it didn't make a difference. The issue happens with kinetic's gnome-settings-daemon 43; it just looks like the gnome-settings-daemon commit made the situation worse but that commit was reverted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+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 1826294] Re: os-prober exits prematurely with "logger: socket /dev/log: Protocol wrong type for socket"
Sorry, works just fine in this lunar vm here:
# id; logger before; ./reproducer.sh ; logger after
uid=0(root) gid=0(root) groups=0(root)
+ set -e
+ . /usr/share/os-prober/common.sh
+ cleanup_tmpdir=false
+ progname=
+ type mapdevfs
+ newns
+ [ ]
+ exec /usr/lib/os-prober/newns ./reproducer.sh
+ set -e
+ . /usr/share/os-prober/common.sh
+ cleanup_tmpdir=false
+ progname=
+ type mapdevfs
+ newns
+ [ 1 ]
+ log hello
+ cache_progname
+ progname=reproducer.sh
+ logger -t reproducer.sh hello
journal:
Mar 07 18:25:21 l-rsyslog-osprober root[2073]: before
Mar 07 18:25:21 l-rsyslog-osprober reproducer.sh[2075]: hello
Mar 07 18:25:21 l-rsyslog-osprober root[2076]: after
# uname -r
6.1.0-16-generic
# ps axwZ|grep rsyslog|grep -v grep
rsyslogd (enforce) 687 ?Ssl0:00 /usr/sbin/rsyslogd
-n -iNONE
systemd-journald-dev-log.socket is also running.
But I tried on amd64. Trying on arm64 will take more time.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1826294
Title:
os-prober exits prematurely with "logger: socket /dev/log: Protocol
wrong type for socket"
Status in AppArmor Profiles:
New
Status in os-prober package in Ubuntu:
New
Status in rsyslog package in Ubuntu:
New
Bug description:
Failure occurs on Ubuntu 16.04 with the apparmor-
profiles-2.10.95-0ubuntu2.10 package installed.
Running update-grub will run /usr/bin/os-prober, which spews about a
dozen of the following line to stderr:
logger: socket /dev/log: Protocol wrong type for socket
… but fails to report the existence of some installed operating
systems as expected.
Furthermore, /var/log/messages contains:
kernel: audit: type=1400 audit(1556043066.679:11460):
apparmor="ALLOWED" operation="sendmsg" info="Failed name lookup -
disconnected path" error=-13 profile="syslog-ng" name="dev/log"
pid=28566 comm="logger" requested_mask="r" denied_mask="r" fsuid=0
ouid=0
Here is a stripped-down skeleton of the /usr/bin/os-prober script, which
demonstrates the problem:
#!/bin/sh
set -e -x
newns () {
[ "$OS_PROBER_NEWNS" ] || exec /usr/lib/os-prober/newns "$0" "$@"
}
log() {
logger -t "$(basename "$0")" "$@"
}
debug() {
log "debug: $@"
}
ls -l /dev/log
debug "Hello world"
newns "$@"
The expected behavior is that it should write "debug: os-prober-
testcase Hello world" to /var/log/messages twice. However, it only
succeeds in writing "Hello world" once. After the script respawns
itself with /usr/lib/os-prober/newns (which is like `unshare -m`), the
second attempt to write to /dev/log fails as described above.
Since the os-prober Bash script runs with the -e flag, any error, even
just a logging error, causes the script to terminate prematurely.
(Arguably, the log() function should call `logger -t "$(basename
"$0")" "$@" || :` so that logging failures aren't fatal.)
The fix, for me, is to edit /etc/apparmor.d/sbin.syslog-ng, and change
profile syslog-ng /{usr/,}sbin/syslog-ng flags=(complain) {\
…
}
to
profile syslog-ng /{usr/,}sbin/syslog-ng
flags=(complain,attach_disconnected) {
…
}
… then run `aa-complain sbin.syslog-ng` and `service syslog-ng
restart`, before running update-grub again. I assume that similar
fixes would be required for the other logging daemons.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor-profiles/+bug/1826294/+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 1826294] Re: os-prober exits prematurely with "logger: socket /dev/log: Protocol wrong type for socket"
The syslog-ng profile needs flags=(attach_disconnected) added to it
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1826294
Title:
os-prober exits prematurely with "logger: socket /dev/log: Protocol
wrong type for socket"
Status in AppArmor Profiles:
New
Status in os-prober package in Ubuntu:
New
Status in rsyslog package in Ubuntu:
New
Bug description:
Failure occurs on Ubuntu 16.04 with the apparmor-
profiles-2.10.95-0ubuntu2.10 package installed.
Running update-grub will run /usr/bin/os-prober, which spews about a
dozen of the following line to stderr:
logger: socket /dev/log: Protocol wrong type for socket
… but fails to report the existence of some installed operating
systems as expected.
Furthermore, /var/log/messages contains:
kernel: audit: type=1400 audit(1556043066.679:11460):
apparmor="ALLOWED" operation="sendmsg" info="Failed name lookup -
disconnected path" error=-13 profile="syslog-ng" name="dev/log"
pid=28566 comm="logger" requested_mask="r" denied_mask="r" fsuid=0
ouid=0
Here is a stripped-down skeleton of the /usr/bin/os-prober script, which
demonstrates the problem:
#!/bin/sh
set -e -x
newns () {
[ "$OS_PROBER_NEWNS" ] || exec /usr/lib/os-prober/newns "$0" "$@"
}
log() {
logger -t "$(basename "$0")" "$@"
}
debug() {
log "debug: $@"
}
ls -l /dev/log
debug "Hello world"
newns "$@"
The expected behavior is that it should write "debug: os-prober-
testcase Hello world" to /var/log/messages twice. However, it only
succeeds in writing "Hello world" once. After the script respawns
itself with /usr/lib/os-prober/newns (which is like `unshare -m`), the
second attempt to write to /dev/log fails as described above.
Since the os-prober Bash script runs with the -e flag, any error, even
just a logging error, causes the script to terminate prematurely.
(Arguably, the log() function should call `logger -t "$(basename
"$0")" "$@" || :` so that logging failures aren't fatal.)
The fix, for me, is to edit /etc/apparmor.d/sbin.syslog-ng, and change
profile syslog-ng /{usr/,}sbin/syslog-ng flags=(complain) {\
…
}
to
profile syslog-ng /{usr/,}sbin/syslog-ng
flags=(complain,attach_disconnected) {
…
}
… then run `aa-complain sbin.syslog-ng` and `service syslog-ng
restart`, before running update-grub again. I assume that similar
fixes would be required for the other logging daemons.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor-profiles/+bug/1826294/+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 2009230] Re: AppArmor denials for rsyslog
Hi Chlo! I was just testing a fix that I did myself: https://launchpad.net/~georgiag/+archive/ubuntu/lp2009230/+packages and it seemed to work as expected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2009230 Title: AppArmor denials for rsyslog Status in gce-compute-image-packages package in Ubuntu: New Status in rsyslog package in Ubuntu: New Status in gce-compute-image-packages source package in Lunar: New Status in rsyslog source package in Lunar: New Bug description: The AppArmor profile for rsyslog, which had been disabled on previous Ubuntu versions, was enabled in lunar. The package google-compute-engine added a config file to rsyslog which requires rw access to /dev/console google:ubuntu-23.04-64 /root# cat /etc/rsyslog.d/90-google.conf # Google Compute Engine default console logging. # # daemon: logging from Google provided daemons. # kern: logging information in case of an unexpected crash during boot. # daemon,kern.* /dev/console google:ubuntu-23.04-64 /root# apt-file search /etc/rsyslog.d/90-google.conf google-compute-engine: /etc/rsyslog.d/90-google.conf So in gce cloud images, we are getting the following denials: [ 1500.302082] audit: type=1400 audit(1677876883.728:495): apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/dev/console" pid=603 comm=72733A6D61696E20513A526567 requested_mask="ac" denied_mask="ac" fsuid=101 ouid=0 To fix it, we just need to add /dev/console rw, to /etc/apparmor.d/usr.sbin.rsyslogd or the same permission should be added to a file in /etc/apparmor.d/rsyslog.d/ by the google-compute-engine package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2009230/+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 2009575] Re: Upgrade to 3.1.3-8ubuntu0.5 causing sync errors
I'm going to need a reproducer for this issue so I can figure out what's not working in your specific example. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/2009575 Title: Upgrade to 3.1.3-8ubuntu0.5 causing sync errors Status in rsync package in Ubuntu: Confirmed Bug description: Hi Several systems running Ubuntu 20.04 upgraded their rsync package from 3.1.3-8ubuntu0.4 to 3.1.3-8ubuntu0.5 overnight. Automated syncs that connect to a 16.04 ESM server are now failing with: receiving file list ... ERROR: rejecting unrequested file-list name: [redacted] rsync error: protocol incompatibility (code 2) at flist.c(916) [Receiver=3.1.3] Reverting to the previous release (3.1.3-8ubuntu0.4) on the client side solves the problem. This has been seen on multiple servers running 20.04 on amd64, I'll update this bug with details if we find it on other series too. The 16.04 ESM server being connected to is using the rsync package version 3.1.1-3ubuntu1.3+esm2, so no recent upgrades on that end. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2009575/+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 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps
Gunnar, can you add a test case to the bug description? I don't know how to reproduce this issue with a new Ubuntu 23.04 install (using American English). By the way, the issue still exists with glib 2.75.4-1 (currently in Debian Experimental and not in Ubuntu yet). ** Description changed: - While preparing the gnome-settings-daemon 44 Beta update for Ubuntu - 23.04, I noticed that I could no longer enter text in the address bars - for the Chromium or Firefox snaps. + Test Case + - + + + Original Bug Report + --- + While preparing the gnome-settings-daemon 44 Beta update for Ubuntu 23.04, I noticed that I could no longer enter text in the address bars for the Chromium or Firefox snaps. Therefore, I reverted https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/commit/27bc0889c so that we could continue with the update. See https://salsa.debian.org/gnome-team/gnome-settings- daemon/-/commit/baeeed93 Before I did that, I tested disabling our patches but it didn't make a difference. I was unable to reproduce the issue on Debian Testing but there may have been differences in how snap was configured there. I'm filing this bug since ideally we would not be diverging from upstream here. -- 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/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps Status in glib2.0 package in Ubuntu: New Status in ibus package in Ubuntu: New Bug description: Test Case - Original Bug Report --- While preparing the gnome-settings-daemon 44 Beta update for Ubuntu 23.04, I noticed that I could no longer enter text in the address bars for the Chromium or Firefox snaps. Therefore, I reverted https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/commit/27bc0889c so that we could continue with the update. See https://salsa.debian.org/gnome-team/gnome-settings- daemon/-/commit/baeeed93 Before I did that, I tested disabling our patches but it didn't make a difference. I was unable to reproduce the issue on Debian Testing but there may have been differences in how snap was configured there. I'm filing this bug since ideally we would not be diverging from upstream here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+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 2009575] Re: Upgrade to 3.1.3-8ubuntu0.5 causing sync errors
Provided requested details privately. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/2009575 Title: Upgrade to 3.1.3-8ubuntu0.5 causing sync errors Status in rsync package in Ubuntu: Confirmed Bug description: Hi Several systems running Ubuntu 20.04 upgraded their rsync package from 3.1.3-8ubuntu0.4 to 3.1.3-8ubuntu0.5 overnight. Automated syncs that connect to a 16.04 ESM server are now failing with: receiving file list ... ERROR: rejecting unrequested file-list name: [redacted] rsync error: protocol incompatibility (code 2) at flist.c(916) [Receiver=3.1.3] Reverting to the previous release (3.1.3-8ubuntu0.4) on the client side solves the problem. This has been seen on multiple servers running 20.04 on amd64, I'll update this bug with details if we find it on other series too. The 16.04 ESM server being connected to is using the rsync package version 3.1.1-3ubuntu1.3+esm2, so no recent upgrades on that end. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2009575/+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 2009230] Re: AppArmor denials for rsyslog
Hey Georgia! Thank you for the report - this is certainly something we could do on our end in the cloud image. Let us do some testing to ensure no regressions are introduced doing this. I'll come back with more information soon. All the best, Chlo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2009230 Title: AppArmor denials for rsyslog Status in gce-compute-image-packages package in Ubuntu: New Status in rsyslog package in Ubuntu: New Status in gce-compute-image-packages source package in Lunar: New Status in rsyslog source package in Lunar: New Bug description: The AppArmor profile for rsyslog, which had been disabled on previous Ubuntu versions, was enabled in lunar. The package google-compute-engine added a config file to rsyslog which requires rw access to /dev/console google:ubuntu-23.04-64 /root# cat /etc/rsyslog.d/90-google.conf # Google Compute Engine default console logging. # # daemon: logging from Google provided daemons. # kern: logging information in case of an unexpected crash during boot. # daemon,kern.* /dev/console google:ubuntu-23.04-64 /root# apt-file search /etc/rsyslog.d/90-google.conf google-compute-engine: /etc/rsyslog.d/90-google.conf So in gce cloud images, we are getting the following denials: [ 1500.302082] audit: type=1400 audit(1677876883.728:495): apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/dev/console" pid=603 comm=72733A6D61696E20513A526567 requested_mask="ac" denied_mask="ac" fsuid=101 ouid=0 To fix it, we just need to add /dev/console rw, to /etc/apparmor.d/usr.sbin.rsyslogd or the same permission should be added to a file in /etc/apparmor.d/rsyslog.d/ by the google-compute-engine package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2009230/+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 2009498] Re: autopkg test failure
** Bug watch added: Debian Bug tracker #1031765 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031765 ** Also affects: ganeti (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031765 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/2009498 Title: autopkg test failure Status in ganeti package in Ubuntu: New Status in procps package in Ubuntu: New Status in ganeti package in Debian: Unknown Bug description: pgrep -u '-1'; echo $? used to yield 1 but with procps 4.0.3 it yields 2. Negative uids don't exist in the Linux kernel. Function testRequestUnusedUid() is wrong in assuming that -1 will be considered an unused uid. See Debian bug#1031765: ganeti-testsuite: autopkgtest failure with procps 2:4.0.3-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ganeti/+bug/2009498/+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 1826294] Re: os-prober exits prematurely with "logger: socket /dev/log: Protocol wrong type for socket"
Steps i can reproduce:
wget https://bugs.launchpad.net/ubuntu/+source/os-
prober/+bug/1826294/+attachment/5652492/+files/reproducer.sh
chmod +x reproducer.sh
sudo journalctl -f -e &
clear
sudo ./reproducer.sh
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1826294
Title:
os-prober exits prematurely with "logger: socket /dev/log: Protocol
wrong type for socket"
Status in AppArmor Profiles:
New
Status in os-prober package in Ubuntu:
New
Status in rsyslog package in Ubuntu:
New
Bug description:
Failure occurs on Ubuntu 16.04 with the apparmor-
profiles-2.10.95-0ubuntu2.10 package installed.
Running update-grub will run /usr/bin/os-prober, which spews about a
dozen of the following line to stderr:
logger: socket /dev/log: Protocol wrong type for socket
… but fails to report the existence of some installed operating
systems as expected.
Furthermore, /var/log/messages contains:
kernel: audit: type=1400 audit(1556043066.679:11460):
apparmor="ALLOWED" operation="sendmsg" info="Failed name lookup -
disconnected path" error=-13 profile="syslog-ng" name="dev/log"
pid=28566 comm="logger" requested_mask="r" denied_mask="r" fsuid=0
ouid=0
Here is a stripped-down skeleton of the /usr/bin/os-prober script, which
demonstrates the problem:
#!/bin/sh
set -e -x
newns () {
[ "$OS_PROBER_NEWNS" ] || exec /usr/lib/os-prober/newns "$0" "$@"
}
log() {
logger -t "$(basename "$0")" "$@"
}
debug() {
log "debug: $@"
}
ls -l /dev/log
debug "Hello world"
newns "$@"
The expected behavior is that it should write "debug: os-prober-
testcase Hello world" to /var/log/messages twice. However, it only
succeeds in writing "Hello world" once. After the script respawns
itself with /usr/lib/os-prober/newns (which is like `unshare -m`), the
second attempt to write to /dev/log fails as described above.
Since the os-prober Bash script runs with the -e flag, any error, even
just a logging error, causes the script to terminate prematurely.
(Arguably, the log() function should call `logger -t "$(basename
"$0")" "$@" || :` so that logging failures aren't fatal.)
The fix, for me, is to edit /etc/apparmor.d/sbin.syslog-ng, and change
profile syslog-ng /{usr/,}sbin/syslog-ng flags=(complain) {\
…
}
to
profile syslog-ng /{usr/,}sbin/syslog-ng
flags=(complain,attach_disconnected) {
…
}
… then run `aa-complain sbin.syslog-ng` and `service syslog-ng
restart`, before running update-grub again. I assume that similar
fixes would be required for the other logging daemons.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor-profiles/+bug/1826294/+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 1826294] Re: os-prober exits prematurely with "logger: socket /dev/log: Protocol wrong type for socket"
This is Ubuntu desktop install. rsyslog.service is active and running,
systemd-journald-dev-log.socket is running.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1826294
Title:
os-prober exits prematurely with "logger: socket /dev/log: Protocol
wrong type for socket"
Status in AppArmor Profiles:
New
Status in os-prober package in Ubuntu:
New
Status in rsyslog package in Ubuntu:
New
Bug description:
Failure occurs on Ubuntu 16.04 with the apparmor-
profiles-2.10.95-0ubuntu2.10 package installed.
Running update-grub will run /usr/bin/os-prober, which spews about a
dozen of the following line to stderr:
logger: socket /dev/log: Protocol wrong type for socket
… but fails to report the existence of some installed operating
systems as expected.
Furthermore, /var/log/messages contains:
kernel: audit: type=1400 audit(1556043066.679:11460):
apparmor="ALLOWED" operation="sendmsg" info="Failed name lookup -
disconnected path" error=-13 profile="syslog-ng" name="dev/log"
pid=28566 comm="logger" requested_mask="r" denied_mask="r" fsuid=0
ouid=0
Here is a stripped-down skeleton of the /usr/bin/os-prober script, which
demonstrates the problem:
#!/bin/sh
set -e -x
newns () {
[ "$OS_PROBER_NEWNS" ] || exec /usr/lib/os-prober/newns "$0" "$@"
}
log() {
logger -t "$(basename "$0")" "$@"
}
debug() {
log "debug: $@"
}
ls -l /dev/log
debug "Hello world"
newns "$@"
The expected behavior is that it should write "debug: os-prober-
testcase Hello world" to /var/log/messages twice. However, it only
succeeds in writing "Hello world" once. After the script respawns
itself with /usr/lib/os-prober/newns (which is like `unshare -m`), the
second attempt to write to /dev/log fails as described above.
Since the os-prober Bash script runs with the -e flag, any error, even
just a logging error, causes the script to terminate prematurely.
(Arguably, the log() function should call `logger -t "$(basename
"$0")" "$@" || :` so that logging failures aren't fatal.)
The fix, for me, is to edit /etc/apparmor.d/sbin.syslog-ng, and change
profile syslog-ng /{usr/,}sbin/syslog-ng flags=(complain) {\
…
}
to
profile syslog-ng /{usr/,}sbin/syslog-ng
flags=(complain,attach_disconnected) {
…
}
… then run `aa-complain sbin.syslog-ng` and `service syslog-ng
restart`, before running update-grub again. I assume that similar
fixes would be required for the other logging daemons.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor-profiles/+bug/1826294/+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 1826294] Re: os-prober exits prematurely with "logger: socket /dev/log: Protocol wrong type for socket"
** Attachment added: "reproducer.sh"
https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1826294/+attachment/5652492/+files/reproducer.sh
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1826294
Title:
os-prober exits prematurely with "logger: socket /dev/log: Protocol
wrong type for socket"
Status in AppArmor Profiles:
New
Status in os-prober package in Ubuntu:
New
Status in rsyslog package in Ubuntu:
New
Bug description:
Failure occurs on Ubuntu 16.04 with the apparmor-
profiles-2.10.95-0ubuntu2.10 package installed.
Running update-grub will run /usr/bin/os-prober, which spews about a
dozen of the following line to stderr:
logger: socket /dev/log: Protocol wrong type for socket
… but fails to report the existence of some installed operating
systems as expected.
Furthermore, /var/log/messages contains:
kernel: audit: type=1400 audit(1556043066.679:11460):
apparmor="ALLOWED" operation="sendmsg" info="Failed name lookup -
disconnected path" error=-13 profile="syslog-ng" name="dev/log"
pid=28566 comm="logger" requested_mask="r" denied_mask="r" fsuid=0
ouid=0
Here is a stripped-down skeleton of the /usr/bin/os-prober script, which
demonstrates the problem:
#!/bin/sh
set -e -x
newns () {
[ "$OS_PROBER_NEWNS" ] || exec /usr/lib/os-prober/newns "$0" "$@"
}
log() {
logger -t "$(basename "$0")" "$@"
}
debug() {
log "debug: $@"
}
ls -l /dev/log
debug "Hello world"
newns "$@"
The expected behavior is that it should write "debug: os-prober-
testcase Hello world" to /var/log/messages twice. However, it only
succeeds in writing "Hello world" once. After the script respawns
itself with /usr/lib/os-prober/newns (which is like `unshare -m`), the
second attempt to write to /dev/log fails as described above.
Since the os-prober Bash script runs with the -e flag, any error, even
just a logging error, causes the script to terminate prematurely.
(Arguably, the log() function should call `logger -t "$(basename
"$0")" "$@" || :` so that logging failures aren't fatal.)
The fix, for me, is to edit /etc/apparmor.d/sbin.syslog-ng, and change
profile syslog-ng /{usr/,}sbin/syslog-ng flags=(complain) {\
…
}
to
profile syslog-ng /{usr/,}sbin/syslog-ng
flags=(complain,attach_disconnected) {
…
}
… then run `aa-complain sbin.syslog-ng` and `service syslog-ng
restart`, before running update-grub again. I assume that similar
fixes would be required for the other logging daemons.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor-profiles/+bug/1826294/+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 2009618] [NEW] GDB: function parameters have garbage values on function entry
Public bug reported:
After upgrading from Ubuntu 18.04 to Ubuntu 20.04 on my x86_64 desktop
machine, I've noticed a significant regression in the debug experience
with gdb. In particular, function parameters in GDB now seem to reliably
have garbage values on entry to the function until I step once inside
the function. Here is a reproducer:
$ cat test.c
#include
int f(int x, int y) {
printf ("%d, %d\n", x, y);
}
int main(void) {
f(2,3);
}
$ gcc -g3 test.c
$ gdb a.out
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04.1) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
[Touch-packages] [Bug 2009603] Re: apt autoremove doesn´t catch all old kernels
I didn't mark any kernel specifically on this machine. It's just a third one, all-purpose, carry-about laptop. My filing wasn't against autoremove, though against deprecation. You don't deprecate a utility that works significantly more effectively than the subsequent utility. The man-page currently says in the context of purge-old-kernels that functional problems should be filed like what I did. Unfortunately I didn't list all files and kernels (rc, ii) on /boot. But there had been a lot, accumulated over some 2 or 3 years since install. autoremove removed just one. Like it or not, the man page should rather say that apt autoremove does this job, too. But when a still tighter ship needs to be run, purge-old- kernels could well be tried out to remove additional remnants of older kernels. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2009603 Title: apt autoremove doesn´t catch all old kernels Status in apt package in Ubuntu: Incomplete Bug description: I have an install with nominally 500MB as /boot. I'm regularly running beyond that limit at updates. Instead of manually picking out old files and apt --purge, I found that more recently apt autoremove would do that task. That brought me down by 11 MB only, from 100%: 445 401 11 98% apt update apt upgrade apt autoremove and reboot didn't improve the situation. A tad reluctantly I installed byobu and ran one session of purge-old-kernels. Result: 445 277 135 68% I can live with that; though I couldn't with the result above. Of course, I'd prefer apt autoremove to do everything in a single go. But what it does, does not actually warrant the deprecation of purge-old-kernels. I'm surely not the only person with a tight budget when using a separate /boot of an old installation. Or, as in my case, a fresh install into an old, formerly partitioned drive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2009603/+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 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller
** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: Confirmed => Won't Fix -- 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/2007331 Title: Fix HFP mSBC support on Realtek Bluetooth USB controller Status in HWE Next: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in pulseaudio source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in pulseaudio source package in Kinetic: Fix Committed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in pulseaudio source package in Lunar: Fix Released Bug description: [Impact] When a BT headset is connected Realtek BT USB controller, HFP profile can't play or record sound when mSBC codec is used. [Fix] At Linux kernel side, add a Realtek specific quirk to support mSBC. At PulseAudio side, send more data frames until the connected device sends response. [Test] Connect different headsets to the said controller, HFP can play and record sounds now. Also verified A2DP profile is unaffected. [Where problems could occur] The kernel part is Realtek specific, so the regression risk is very limited. The pulseaudio side only affects HFP profile, since the codeflow only changes when a mic is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007331/+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 2009301] Re: package libxau-dev:amd64 1:1.0.9-1build5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura
Your root disk is fairly full, so I assume it got filled up at some point and the package got corrupted or something. Do as it suggests and reinstall libxau-dev ** Changed in: libxau (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxau in Ubuntu. https://bugs.launchpad.net/bugs/2009301 Title: package libxau-dev:amd64 1:1.0.9-1build5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libxau package in Ubuntu: Invalid Bug description: this is the fifth time it happens after few days of installing linux ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libxau-dev:amd64 1:1.0.9-1build5 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Sun Mar 5 23:04:38 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DuplicateSignature: package:libxau-dev:amd64:1:1.0.9-1build5 Setting up imagemagick-6-common (8:6.9.11.60+dfsg-1.3ubuntu0.22.04.1) ... dpkg: error processing package libxau-dev:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06b2] Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] [1028:06b2] InstallationDate: Installed on 2022-11-09 (115 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:5684 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Unidentified System ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=f99443b7-ddd9-46e2-8c17-95b2826ad7f2 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: libxau Title: package libxau-dev:amd64 1:1.0.9-1build5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2016 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.name: 04D1V1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd10/06/2016:br1.2:svnDellInc.:pnUnidentifiedSystem:pvr:rvnDellInc.:rn04D1V1:rvrA00:cvnDellInc.:ct9:cvr:sku06B2: dmi.product.name: Unidentified System dmi.product.sku: 06B2 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxau/+bug/2009301/+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 2009598] Re: Error when I run "sudo apt upgrade"
*** This bug is a duplicate of bug 2006744 *** https://bugs.launchpad.net/bugs/2006744 ** This bug has been marked a duplicate of bug 2006744 libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file conflict -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2009598 Title: Error when I run "sudo apt upgrade" Status in mesa package in Ubuntu: New Bug description: When I run sudo apt upgrade, I have this error : package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade: tentative de remplacement de « /usr/lib/x86_64-linux- gnu/dri/i915_dri.so », qui appartient aussi au paquet libgl1-amber- dri:amd64 21.3.7-0ubuntu1 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None Date: Tue Mar 7 14:07:39 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ErrorMessage: tentative de remplacement de « /usr/lib/x86_64-linux-gnu/dri/i915_dri.so », qui appartient aussi au paquet libgl1-amber-dri:amd64 21.3.7-0ubuntu1 ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] InstallationDate: Installed on 2023-02-25 (9 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230216) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-21-generic root=UUID=3274a782-2ac3-4126-ae6f-61555798cd06 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.20ubuntu2 apt 2.5.6 SourcePackage: mesa Title: package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade: tentative de remplacement de « /usr/lib/x86_64-linux-gnu/dri/i915_dri.so », qui appartient aussi au paquet libgl1-amber-dri:amd64 21.3.7-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/29/2014 dmi.bios.release: 1.11 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.11 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.54 dmi.chassis.asset.tag: CNU422B518 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 21.84 dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.11:bd04/29/2014:br1.11:efr21.84:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.54:cvnHewlett-Packard:ct10:cvr:skuF9W54UP#UUZ: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 840 G1 dmi.product.sku: F9W54UP#UUZ dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2009598/+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 2009603] Re: apt autoremove doesn´t catch all old kernels
APT automatically removes unnecessary kernels. If something depends on a specific kernel version or you marked that kernel as manually installed it will be kept of course. Also it will always keep 2 kernels around as a minimum, and of course the currently booted kernel. ** Changed in: apt (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2009603 Title: apt autoremove doesn´t catch all old kernels Status in apt package in Ubuntu: Incomplete Bug description: I have an install with nominally 500MB as /boot. I'm regularly running beyond that limit at updates. Instead of manually picking out old files and apt --purge, I found that more recently apt autoremove would do that task. That brought me down by 11 MB only, from 100%: 445 401 11 98% apt update apt upgrade apt autoremove and reboot didn't improve the situation. A tad reluctantly I installed byobu and ran one session of purge-old-kernels. Result: 445 277 135 68% I can live with that; though I couldn't with the result above. Of course, I'd prefer apt autoremove to do everything in a single go. But what it does, does not actually warrant the deprecation of purge-old-kernels. I'm surely not the only person with a tight budget when using a separate /boot of an old installation. Or, as in my case, a fresh install into an old, formerly partitioned drive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2009603/+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 2009481] Re: FFE: mesa 23.0.1
works fine on my machines, but I've amended the request to use 23.0.1 which should be released in a day or two, unless the upstream CI is acting up. ** Summary changed: - FFE: mesa 23.0.0 + FFE: mesa 23.0.1 ** Description changed: Mesa 23.0.0 was released on Feb 23rd, and this is the planned branch to use for Ubuntu 23.04. This release includes improvements across the board, and packaging adds a package for mesa-drm-shim. + + 23.0.1 should be released on week 10, so it's a good candidate for an + upload. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2009481 Title: FFE: mesa 23.0.1 Status in mesa package in Ubuntu: In Progress Bug description: Mesa 23.0.0 was released on Feb 23rd, and this is the planned branch to use for Ubuntu 23.04. This release includes improvements across the board, and packaging adds a package for mesa-drm-shim. 23.0.1 should be released on week 10, so it's a good candidate for an upload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2009481/+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 2009603] [NEW] apt autoremove doesn´t catch all old kernels
Public bug reported: I have an install with nominally 500MB as /boot. I'm regularly running beyond that limit at updates. Instead of manually picking out old files and apt --purge, I found that more recently apt autoremove would do that task. That brought me down by 11 MB only, from 100%: 445 401 11 98% apt update apt upgrade apt autoremove and reboot didn't improve the situation. A tad reluctantly I installed byobu and ran one session of purge-old-kernels. Result: 445 277 135 68% I can live with that; though I couldn't with the result above. Of course, I'd prefer apt autoremove to do everything in a single go. But what it does, does not actually warrant the deprecation of purge-old-kernels. I'm surely not the only person with a tight budget when using a separate /boot of an old installation. Or, as in my case, a fresh install into an old, formerly partitioned drive. ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: kernel purge -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2009603 Title: apt autoremove doesn´t catch all old kernels Status in apt package in Ubuntu: New Bug description: I have an install with nominally 500MB as /boot. I'm regularly running beyond that limit at updates. Instead of manually picking out old files and apt --purge, I found that more recently apt autoremove would do that task. That brought me down by 11 MB only, from 100%: 445 401 11 98% apt update apt upgrade apt autoremove and reboot didn't improve the situation. A tad reluctantly I installed byobu and ran one session of purge-old-kernels. Result: 445 277 135 68% I can live with that; though I couldn't with the result above. Of course, I'd prefer apt autoremove to do everything in a single go. But what it does, does not actually warrant the deprecation of purge-old-kernels. I'm surely not the only person with a tight budget when using a separate /boot of an old installation. Or, as in my case, a fresh install into an old, formerly partitioned drive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2009603/+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 2009575] Re: Upgrade to 3.1.3-8ubuntu0.5 causing sync errors
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/2009575 Title: Upgrade to 3.1.3-8ubuntu0.5 causing sync errors Status in rsync package in Ubuntu: Confirmed Bug description: Hi Several systems running Ubuntu 20.04 upgraded their rsync package from 3.1.3-8ubuntu0.4 to 3.1.3-8ubuntu0.5 overnight. Automated syncs that connect to a 16.04 ESM server are now failing with: receiving file list ... ERROR: rejecting unrequested file-list name: [redacted] rsync error: protocol incompatibility (code 2) at flist.c(916) [Receiver=3.1.3] Reverting to the previous release (3.1.3-8ubuntu0.4) on the client side solves the problem. This has been seen on multiple servers running 20.04 on amd64, I'll update this bug with details if we find it on other series too. The 16.04 ESM server being connected to is using the rsync package version 3.1.1-3ubuntu1.3+esm2, so no recent upgrades on that end. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2009575/+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 1826294] Re: os-prober exits prematurely with "logger: socket /dev/log: Protocol wrong type for socket"
** Merge proposal linked:
https://code.launchpad.net/~xnox/ubuntu/+source/os-prober/+git/os-prober/+merge/438461
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1826294
Title:
os-prober exits prematurely with "logger: socket /dev/log: Protocol
wrong type for socket"
Status in AppArmor Profiles:
New
Status in os-prober package in Ubuntu:
New
Status in rsyslog package in Ubuntu:
New
Bug description:
Failure occurs on Ubuntu 16.04 with the apparmor-
profiles-2.10.95-0ubuntu2.10 package installed.
Running update-grub will run /usr/bin/os-prober, which spews about a
dozen of the following line to stderr:
logger: socket /dev/log: Protocol wrong type for socket
… but fails to report the existence of some installed operating
systems as expected.
Furthermore, /var/log/messages contains:
kernel: audit: type=1400 audit(1556043066.679:11460):
apparmor="ALLOWED" operation="sendmsg" info="Failed name lookup -
disconnected path" error=-13 profile="syslog-ng" name="dev/log"
pid=28566 comm="logger" requested_mask="r" denied_mask="r" fsuid=0
ouid=0
Here is a stripped-down skeleton of the /usr/bin/os-prober script, which
demonstrates the problem:
#!/bin/sh
set -e -x
newns () {
[ "$OS_PROBER_NEWNS" ] || exec /usr/lib/os-prober/newns "$0" "$@"
}
log() {
logger -t "$(basename "$0")" "$@"
}
debug() {
log "debug: $@"
}
ls -l /dev/log
debug "Hello world"
newns "$@"
The expected behavior is that it should write "debug: os-prober-
testcase Hello world" to /var/log/messages twice. However, it only
succeeds in writing "Hello world" once. After the script respawns
itself with /usr/lib/os-prober/newns (which is like `unshare -m`), the
second attempt to write to /dev/log fails as described above.
Since the os-prober Bash script runs with the -e flag, any error, even
just a logging error, causes the script to terminate prematurely.
(Arguably, the log() function should call `logger -t "$(basename
"$0")" "$@" || :` so that logging failures aren't fatal.)
The fix, for me, is to edit /etc/apparmor.d/sbin.syslog-ng, and change
profile syslog-ng /{usr/,}sbin/syslog-ng flags=(complain) {\
…
}
to
profile syslog-ng /{usr/,}sbin/syslog-ng
flags=(complain,attach_disconnected) {
…
}
… then run `aa-complain sbin.syslog-ng` and `service syslog-ng
restart`, before running update-grub again. I assume that similar
fixes would be required for the other logging daemons.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor-profiles/+bug/1826294/+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 1826294] Re: os-prober exits prematurely with "logger: socket /dev/log: Protocol wrong type for socket"
I'll try to reproduce it and amend the profile as needed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1826294
Title:
os-prober exits prematurely with "logger: socket /dev/log: Protocol
wrong type for socket"
Status in AppArmor Profiles:
New
Status in os-prober package in Ubuntu:
New
Status in rsyslog package in Ubuntu:
New
Bug description:
Failure occurs on Ubuntu 16.04 with the apparmor-
profiles-2.10.95-0ubuntu2.10 package installed.
Running update-grub will run /usr/bin/os-prober, which spews about a
dozen of the following line to stderr:
logger: socket /dev/log: Protocol wrong type for socket
… but fails to report the existence of some installed operating
systems as expected.
Furthermore, /var/log/messages contains:
kernel: audit: type=1400 audit(1556043066.679:11460):
apparmor="ALLOWED" operation="sendmsg" info="Failed name lookup -
disconnected path" error=-13 profile="syslog-ng" name="dev/log"
pid=28566 comm="logger" requested_mask="r" denied_mask="r" fsuid=0
ouid=0
Here is a stripped-down skeleton of the /usr/bin/os-prober script, which
demonstrates the problem:
#!/bin/sh
set -e -x
newns () {
[ "$OS_PROBER_NEWNS" ] || exec /usr/lib/os-prober/newns "$0" "$@"
}
log() {
logger -t "$(basename "$0")" "$@"
}
debug() {
log "debug: $@"
}
ls -l /dev/log
debug "Hello world"
newns "$@"
The expected behavior is that it should write "debug: os-prober-
testcase Hello world" to /var/log/messages twice. However, it only
succeeds in writing "Hello world" once. After the script respawns
itself with /usr/lib/os-prober/newns (which is like `unshare -m`), the
second attempt to write to /dev/log fails as described above.
Since the os-prober Bash script runs with the -e flag, any error, even
just a logging error, causes the script to terminate prematurely.
(Arguably, the log() function should call `logger -t "$(basename
"$0")" "$@" || :` so that logging failures aren't fatal.)
The fix, for me, is to edit /etc/apparmor.d/sbin.syslog-ng, and change
profile syslog-ng /{usr/,}sbin/syslog-ng flags=(complain) {\
…
}
to
profile syslog-ng /{usr/,}sbin/syslog-ng
flags=(complain,attach_disconnected) {
…
}
… then run `aa-complain sbin.syslog-ng` and `service syslog-ng
restart`, before running update-grub again. I assume that similar
fixes would be required for the other logging daemons.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor-profiles/+bug/1826294/+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 1826294] Re: os-prober exits prematurely with "logger: socket /dev/log: Protocol wrong type for socket"
yeah i get apparmor="DENIED" info="Failed name loookup - disconnected
path", which breaks os-prober.
** Changed in: os-prober (Ubuntu)
Importance: Undecided => Critical
** Also affects: rsyslog (Ubuntu)
Importance: Undecided
Status: New
** Changed in: rsyslog (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1826294
Title:
os-prober exits prematurely with "logger: socket /dev/log: Protocol
wrong type for socket"
Status in AppArmor Profiles:
New
Status in os-prober package in Ubuntu:
New
Status in rsyslog package in Ubuntu:
New
Bug description:
Failure occurs on Ubuntu 16.04 with the apparmor-
profiles-2.10.95-0ubuntu2.10 package installed.
Running update-grub will run /usr/bin/os-prober, which spews about a
dozen of the following line to stderr:
logger: socket /dev/log: Protocol wrong type for socket
… but fails to report the existence of some installed operating
systems as expected.
Furthermore, /var/log/messages contains:
kernel: audit: type=1400 audit(1556043066.679:11460):
apparmor="ALLOWED" operation="sendmsg" info="Failed name lookup -
disconnected path" error=-13 profile="syslog-ng" name="dev/log"
pid=28566 comm="logger" requested_mask="r" denied_mask="r" fsuid=0
ouid=0
Here is a stripped-down skeleton of the /usr/bin/os-prober script, which
demonstrates the problem:
#!/bin/sh
set -e -x
newns () {
[ "$OS_PROBER_NEWNS" ] || exec /usr/lib/os-prober/newns "$0" "$@"
}
log() {
logger -t "$(basename "$0")" "$@"
}
debug() {
log "debug: $@"
}
ls -l /dev/log
debug "Hello world"
newns "$@"
The expected behavior is that it should write "debug: os-prober-
testcase Hello world" to /var/log/messages twice. However, it only
succeeds in writing "Hello world" once. After the script respawns
itself with /usr/lib/os-prober/newns (which is like `unshare -m`), the
second attempt to write to /dev/log fails as described above.
Since the os-prober Bash script runs with the -e flag, any error, even
just a logging error, causes the script to terminate prematurely.
(Arguably, the log() function should call `logger -t "$(basename
"$0")" "$@" || :` so that logging failures aren't fatal.)
The fix, for me, is to edit /etc/apparmor.d/sbin.syslog-ng, and change
profile syslog-ng /{usr/,}sbin/syslog-ng flags=(complain) {\
…
}
to
profile syslog-ng /{usr/,}sbin/syslog-ng
flags=(complain,attach_disconnected) {
…
}
… then run `aa-complain sbin.syslog-ng` and `service syslog-ng
restart`, before running update-grub again. I assume that similar
fixes would be required for the other logging daemons.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor-profiles/+bug/1826294/+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 2009598] [NEW] Error when I run "sudo apt upgrade"
Public bug reported: When I run sudo apt upgrade, I have this error : package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade: tentative de remplacement de « /usr/lib/x86_64-linux-gnu/dri/i915_dri.so », qui appartient aussi au paquet libgl1-amber-dri:amd64 21.3.7-0ubuntu1 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None Date: Tue Mar 7 14:07:39 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ErrorMessage: tentative de remplacement de « /usr/lib/x86_64-linux-gnu/dri/i915_dri.so », qui appartient aussi au paquet libgl1-amber-dri:amd64 21.3.7-0ubuntu1 ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] InstallationDate: Installed on 2023-02-25 (9 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230216) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-21-generic root=UUID=3274a782-2ac3-4126-ae6f-61555798cd06 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.20ubuntu2 apt 2.5.6 SourcePackage: mesa Title: package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade: tentative de remplacement de « /usr/lib/x86_64-linux-gnu/dri/i915_dri.so », qui appartient aussi au paquet libgl1-amber-dri:amd64 21.3.7-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/29/2014 dmi.bios.release: 1.11 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.11 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.54 dmi.chassis.asset.tag: CNU422B518 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 21.84 dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.11:bd04/29/2014:br1.11:efr21.84:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.54:cvnHewlett-Packard:ct10:cvr:skuF9W54UP#UUZ: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 840 G1 dmi.product.sku: F9W54UP#UUZ dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar single-occurrence ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2009598 Title: Error when I run "sudo apt upgrade" Status in mesa package in Ubuntu: New Bug description: When I run sudo apt upgrade, I have this error : package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade: tentative de remplacement de « /usr/lib/x86_64-linux- gnu/dri/i915_dri.so », qui appartient aussi au paquet libgl1-amber- dri:amd64 21.3.7-0ubuntu1 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None Date: Tue Mar 7 14:07:39 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ErrorMessage: tentative de remplacement de « /usr/lib/x86_64-linux-gnu/dri/i915_dri.so », qui appartient aussi au paquet libgl1-amber-dri:amd64 21.3.7-0ubuntu1 ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] InstallationDate: Installed on 2023-02-25 (9 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230216) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcKernelCmdLine:
Re: [Touch-packages] [Bug 2007913] Re: HDMI Output sound has disappeared after Ubuntu update
"Booting with linux-image-5.19.0-21-generic lists the audio devices again." So how do I do that? On Tue, Mar 7, 2023 at 5:20 AM William <2007...@bugs.launchpad.net> wrote: > Booting with linux-image-5.19.0-35-generic appears to be the problem in > 22.10. Booting with linux-image-5.19.0-21-generic lists the audio > devices again. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2007913 > > Title: > HDMI Output sound has disappeared after Ubuntu update > > Status in alsa-driver package in Ubuntu: > Confirmed > > Bug description: > After months using the HDMI output without problems, it has stopped > working after a system update two days ago. > HDMI output is not listed in the list of available output devices. > Same computer works with this sound output perfectly when booting with > Windows or an older installation of Ubuntu (18.04). > > ProblemType: Bug > DistroRelease: Ubuntu 22.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu7 > ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 > Uname: Linux 5.19.0-32-generic x86_64 > ApportVersion: 2.20.11-0ubuntu82.3 > Architecture: amd64 > CasperMD5CheckResult: pass > CurrentDesktop: ubuntu:GNOME > Date: Tue Feb 21 08:12:58 2023 > EcryptfsInUse: Yes > InstallationDate: Installed on 2022-04-30 (296 days ago) > InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 > (20220419) > PackageArchitecture: all > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=ca_ES.UTF-8 >SHELL=/bin/bash > SourcePackage: alsa-driver > Symptom: audio > Title: USB sound card not detected > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 10/20/2021 > dmi.bios.release: 5.13 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: M01EWR120 > dmi.board.asset.tag: OEM Default string000 > dmi.board.name: OEM Default string000 > dmi.board.vendor: OEM Default string000 > dmi.board.version: OEM Default string000 > dmi.chassis.asset.tag: OEM Default string000 > dmi.chassis.type: 10 > dmi.chassis.vendor: OEM Default string000 > dmi.chassis.version: OEM Default string000 > dmi.ec.firmware.release: 1.2 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000: > dmi.product.family: OEM Default string000 > dmi.product.name: CoreBox > dmi.product.sku: OEM Default string000 > dmi.product.version: OEM Default string000 > dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd > mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+subscriptions > > -- 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/2007913 Title: HDMI Output sound has disappeared after Ubuntu update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After months using the HDMI output without problems, it has stopped working after a system update two days ago. HDMI output is not listed in the list of available output devices. Same computer works with this sound output perfectly when booting with Windows or an older installation of Ubuntu (18.04). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 21 08:12:58 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-30 (296 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M01EWR120 dmi.board.asset.tag: OEM Default string000 dmi.board.name: OEM Default string000 dmi.board.vendor: OEM Default string000 dmi.board.version: OEM Default string000 dmi.chassis.asset.tag: OEM Default string000 dmi.chassis.type: 10 dmi.chassis.vendor: OEM Default string000 dmi.chassis.version: OEM Default string000 dmi.ec.firmware.release: 1.2 dmi.modalias:
[Touch-packages] [Bug 2009575] Re: Upgrade to 3.1.3-8ubuntu0.5 causing sync errors
I need to see the filenames that got rejected. You can send them to me in private is required. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/2009575 Title: Upgrade to 3.1.3-8ubuntu0.5 causing sync errors Status in rsync package in Ubuntu: Confirmed Bug description: Hi Several systems running Ubuntu 20.04 upgraded their rsync package from 3.1.3-8ubuntu0.4 to 3.1.3-8ubuntu0.5 overnight. Automated syncs that connect to a 16.04 ESM server are now failing with: receiving file list ... ERROR: rejecting unrequested file-list name: [redacted] rsync error: protocol incompatibility (code 2) at flist.c(916) [Receiver=3.1.3] Reverting to the previous release (3.1.3-8ubuntu0.4) on the client side solves the problem. This has been seen on multiple servers running 20.04 on amd64, I'll update this bug with details if we find it on other series too. The 16.04 ESM server being connected to is using the rsync package version 3.1.1-3ubuntu1.3+esm2, so no recent upgrades on that end. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2009575/+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 2009587] [NEW] Can't set sound output to Displayport screen - not listed anymore
Public bug reported: It's very recent, but I can't seem to set the audio output to my screens as they are not listed anymore in the Sound settings panel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 7 12:37:41 2023 InstallationDate: Installed on 2022-05-31 (280 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2016 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.00 dmi.board.asset.tag: Default string dmi.board.name: Z270 GAMING M7 (MS-7A57) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.00:bd12/06/2016:br5.12:svnMSI:pnMS-7A57:pvr1.0:rvnMSI:rnZ270GAMINGM7(MS-7A57):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7A57 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2009587 Title: Can't set sound output to Displayport screen - not listed anymore Status in alsa-driver package in Ubuntu: New Bug description: It's very recent, but I can't seem to set the audio output to my screens as they are not listed anymore in the Sound settings panel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 7 12:37:41 2023 InstallationDate: Installed on 2022-05-31 (280 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2016 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.00 dmi.board.asset.tag: Default string dmi.board.name: Z270 GAMING M7 (MS-7A57) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.00:bd12/06/2016:br5.12:svnMSI:pnMS-7A57:pvr1.0:rvnMSI:rnZ270GAMINGM7(MS-7A57):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7A57 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2009587/+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 2009575] Re: Upgrade to 3.1.3-8ubuntu0.5 causing sync errors
** Description changed: Hi - Several systems upgraded their rsync package from 3.1.3-8ubuntu0.4 to - 3.1.3-8ubuntu0.5 overnight. + Several systems running Ubuntu 20.04 upgraded their rsync package from + 3.1.3-8ubuntu0.4 to 3.1.3-8ubuntu0.5 overnight. - Automated syncs are now failing with: + Automated syncs that connect to a 16.04 ESM server are now failing with: - receiving file list ... + receiving file list ... ERROR: rejecting unrequested file-list name: [redacted] rsync error: protocol incompatibility (code 2) at flist.c(916) [Receiver=3.1.3] - Reverting to the previous release solves the problem. + Reverting to the previous release (3.1.3-8ubuntu0.4) on the client side + solves the problem. This has been seen on multiple servers running 20.04 on amd64, I'll update this bug with details if we find it on other series too. + + The 16.04 ESM server being connected to is using the rsync package + version 3.1.1-3ubuntu1.3+esm2, so no recent upgrades on that end. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/2009575 Title: Upgrade to 3.1.3-8ubuntu0.5 causing sync errors Status in rsync package in Ubuntu: Confirmed Bug description: Hi Several systems running Ubuntu 20.04 upgraded their rsync package from 3.1.3-8ubuntu0.4 to 3.1.3-8ubuntu0.5 overnight. Automated syncs that connect to a 16.04 ESM server are now failing with: receiving file list ... ERROR: rejecting unrequested file-list name: [redacted] rsync error: protocol incompatibility (code 2) at flist.c(916) [Receiver=3.1.3] Reverting to the previous release (3.1.3-8ubuntu0.4) on the client side solves the problem. This has been seen on multiple servers running 20.04 on amd64, I'll update this bug with details if we find it on other series too. The 16.04 ESM server being connected to is using the rsync package version 3.1.1-3ubuntu1.3+esm2, so no recent upgrades on that end. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2009575/+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 2000868] Re: backport required for virtio_gpu_dri.so
I'm not sure I can help here. I have been using kisak ppa with latest mesa. I dont want to downgrade mesa packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2000868 Title: backport required for virtio_gpu_dri.so Status in mesa package in Ubuntu: Incomplete Bug description: Hi, xorg crashing when using modsetting with virtio_gpu_dri as graphics driver in kvm guest. Kindly look into this conversation https://gitlab.freedesktop.org/virgl/virglrenderer/-/issues/291#note_1701920 I think we need to backport https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19655 to fix this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2000868/+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 2007913] Re: HDMI Output sound has disappeared after Ubuntu update
Booting with linux-image-5.19.0-35-generic appears to be the problem in 22.10. Booting with linux-image-5.19.0-21-generic lists the audio devices again. -- 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/2007913 Title: HDMI Output sound has disappeared after Ubuntu update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After months using the HDMI output without problems, it has stopped working after a system update two days ago. HDMI output is not listed in the list of available output devices. Same computer works with this sound output perfectly when booting with Windows or an older installation of Ubuntu (18.04). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 21 08:12:58 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-30 (296 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M01EWR120 dmi.board.asset.tag: OEM Default string000 dmi.board.name: OEM Default string000 dmi.board.vendor: OEM Default string000 dmi.board.version: OEM Default string000 dmi.chassis.asset.tag: OEM Default string000 dmi.chassis.type: 10 dmi.chassis.vendor: OEM Default string000 dmi.chassis.version: OEM Default string000 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000: dmi.product.family: OEM Default string000 dmi.product.name: CoreBox dmi.product.sku: OEM Default string000 dmi.product.version: OEM Default string000 dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+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 2006669] Re: Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915])
22.3.1+ includes these two commits: intel: factor out dispatch PS enabling logic intel: add missing restriction on fragment simd dispatch They are not in 22.2.x The other two commits: intel/common/intel_genX_state.h: Add intel_set_ps_dispatch_state() intel/blorp: Fix a hang caused by invalid dispatch enables on gfx7 are only in 23.0. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2006669 Title: Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915]) Status in mesa package in Ubuntu: New Status in mesa source package in Jammy: New Status in mesa source package in Kinetic: New Status in mesa source package in Lunar: New Bug description: GUI hard lock during zoom session and gnome-terminal kern.log shows a mix of errors __ kernel: [ 3627.948545] Asynchronous wait on fence :00:02.0:gnome-shell[4236]:40810 timed out (hint:intel_atomic_commit_ready [i915]) kernel: [ 3631.063832] i915 :00:02.0: [drm] GPU HANG: ecode 12:1:85db, in chrome [5521] kernel: [ 3631.064218] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 kernel: [ 3631.165642] i915 :00:02.0: [drm] chrome[5521] context reset due to GPU hang kernel: [ 3631.165719] i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin version 70.1 kernel: [ 3631.165725] i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 kernel: [ 3631.187377] i915 :00:02.0: [drm] HuC authenticated kernel: [ 3631.187670] i915 :00:02.0: [drm] GuC submission enabled kernel: [ 3631.187672] i915 :00:02.0: [drm] GuC SLPC enabled ___ I suspect this issue to be upstream: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7755 upstream commit: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20169/commits?commit_id=b9403b1c477e7af04114ae6a4e16ca370e22253c#d6ffde011ad32c6371611e7d64affaeb21b6b217 Reproducer: Although I don't have my own reproducer, the upstream mesa reproducer does trigger a hang on my machine. Upstream Reproducer: Open https://kartikmandhang.netlify.app/ when it loads, you will see pikachu. Press "S", he will go back. My whole system freezes from this in Wayland, regardless of the browser. Kernel: 6.0.0-1008-oem Mesa: 22.2.5-0ubuntu0.1~22.04.1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 ProcVersionSignature: Ubuntu 6.0.0-1008.8-oem 6.0.9 Uname: Linux 6.0.0-1008-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 8 21:40:19 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b1a] Subsystem: Dell Device [1028:0b1a] InstallationDate: Installed on 2022-07-13 (211 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: Dell Inc. Precision 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-1008-oem root=/dev/mapper/ubuntu--vg-ubuntu--lv ro pcie_aspm=force quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2022 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 03M8N5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd11/21/2022:br1.9:svnDellInc.:pnPrecision5570:pvr:rvnDellInc.:rn03M8N5:rvrA00:cvnDellInc.:ct10:cvr:sku0B1A: dmi.product.family: Precision dmi.product.name: Precision 5570 dmi.product.sku: 0B1A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
[Touch-packages] [Bug 2000868] Re: backport required for virtio_gpu_dri.so
22.2.5+ is now in jammy/kinetic/lunar updates. mohan43u and others, can you can confirm it is fixed for you now? ** Changed in: mesa (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2000868 Title: backport required for virtio_gpu_dri.so Status in mesa package in Ubuntu: Incomplete Bug description: Hi, xorg crashing when using modsetting with virtio_gpu_dri as graphics driver in kvm guest. Kindly look into this conversation https://gitlab.freedesktop.org/virgl/virglrenderer/-/issues/291#note_1701920 I think we need to backport https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19655 to fix this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2000868/+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 2006645] Re: Death Stranding(Video Game) crashes consistenly when moving right control stick with map open
Lunar is now at 22.3.6-1ubuntu1, including this fix. ** Changed in: mesa (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2006645 Title: Death Stranding(Video Game) crashes consistenly when moving right control stick with map open Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: New Status in mesa source package in Kinetic: New Bug description: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7735#note_1674704 99% sure it's this bug on Mesa's gitlab. Installing the kisak-mesa PPA fixed the issue for me. Any chance of a backport for the fix? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2006645/+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 2009435] Re: Xorg freeze
** Package changed: xorg (Ubuntu) => nautilus (Ubuntu) ** Summary changed: - Xorg freeze + Nautilus freeze -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2009435 Title: Nautilus freeze Status in nautilus package in Ubuntu: New Bug description: Files application hangs when switched to from other application. Only occurs when mounted to internal HDD. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 6 08:50:17 2023 DistUpgraded: 2022-09-30 11:53:10,478 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-67-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-32-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-35-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Lexa PRO [Radeon RX 550] [1da2:e367] InstallationDate: Installed on 2020-10-24 (862 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=9db35888-ce9e-4ddd-96ab-979cf2de8c9e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to jammy on 2022-09-30 (156 days ago) dmi.bios.date: 11/13/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2006 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2006:bd11/13/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2009435/+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 2009564] Re: Touchpad disabling while typing does not work
I assume you mean: org.gnome.desktop.peripherals.touchpad disable-while-typing true Does it work any better if you log into Ubuntu on Xorg instead? ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Also affects: libinput (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2009564 Title: Touchpad disabling while typing does not work Status in libinput package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: It makes my laptop much less usable. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.85.05 Sat Jan 14 00:49:50 UTC 2023 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 7 00:44:08 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: backport-iwlwifi/9858, 5.19.0-32-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) backport-iwlwifi/9858, 5.19.0-35-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia/525.85.05, 5.15.0-56-generic, x86_64: installed nvidia/525.85.05, 5.19.0-32-generic, x86_64: installed nvidia/525.85.05, 5.19.0-35-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. Device [1a58:201f] NVIDIA Corporation Device [10de:24e0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. Device [1a58:201f] InstallationDate: Installed on 2023-01-03 (62 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Razer x Lambda TensorBook (2022) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=4cd4fe61-a6ef-48c5-acc8-b96e7da91171 ro button.lid_init_state=open i915.enable_fbc=0 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2022 dmi.bios.release: 1.0 dmi.bios.vendor: Razer dmi.bios.version: 1.00 dmi.board.name: CH580 dmi.board.vendor: Razer x Lambda dmi.board.version: 4 dmi.chassis.type: 10 dmi.chassis.vendor: Razer x Lambda dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvnRazer:bvr1.00:bd07/29/2022:br1.0:efr1.0:svnRazerxLambda:pnTensorBook(2022):pvr8.04:rvnRazerxLambda:rnCH580:rvr4:cvnRazerxLambda:ct10:cvr:skuRZ09-0421NEL9: dmi.product.family: 1A58201F Razer x Lambda TensorBook dmi.product.name: TensorBook (2022) dmi.product.sku: RZ09-0421NEL9 dmi.product.version: 8.04 dmi.sys.vendor: Razer x Lambda version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1
[Touch-packages] [Bug 1993387] Re: Merge bridge-utils from Debian unstable for lunar
This was done by Graham Inggs in https://launchpad.net/ubuntu/+source/bridge-utils/1.7.1-1ubuntu1 and no other merge was needed. bridge-utils | 1.7.1-1ubuntu1 | lunar | source, amd64, arm64, armhf, ppc64el, riscv64, s390x => Done (and thanks Graham) ** Changed in: bridge-utils (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/1993387 Title: Merge bridge-utils from Debian unstable for lunar Status in bridge-utils package in Ubuntu: Fix Released Bug description: Scheduled-For: ubuntu-22.12 Upstream: 1.7.1 Debian: 1.7-2 Ubuntu: 1.7-1ubuntu3 ### New Debian Changes ### bridge-utils (1.7-2) unstable; urgency=medium * Add BRIDGE_DISABLE_LINKLOCAL_IPV6_ALSO_PHYS to /etc/default/bridge-utils to stop disabling IPv6 on physical interfaces of vlan ports if set to no. Closes: #989162. * Update interfaces man page, IPv6 works with STP on after DAD was fixed. Closes: #980507. * Treat vlan ports the same as ifupdown, avoid octal vlans. Closes: #995627. * Update NEWS file to fix us blaming the kernel for the MAC address selection that is really overridden by systemd. -- Santiago García Mantiñán Mon, 03 Oct 2022 23:11:46 +0200 ### Old Ubuntu Delta ### bridge-utils (1.7-1ubuntu3) jammy; urgency=medium * No-change rebuild for ppc64el baseline bump. -- Łukasz 'sil2100' Zemczak Wed, 23 Mar 2022 10:44:35 +0100 bridge-utils (1.7-1ubuntu2) impish; urgency=medium * No-change rebuild to build packages with zstd compression. -- Matthias Klose Thu, 07 Oct 2021 12:09:41 +0200 bridge-utils (1.7-1ubuntu1) impish; urgency=low * Merge from Debian unstable. Remaining changes: - Don't call ifup from bridge-network-interface, instead just call brctl and let udev/upstart bring the interface up. - debian/ifupdown.sh: Handle bridge params which use port and value - debian/bridge-utils-interface.5: + Update max, default value for path cost + Update unsettable gcint value for newer kernels -- Steve Langasek Wed, 17 Mar 2021 12:32:22 -0700 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1993387/+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 2009575] Re: Upgrade to 3.1.3-8ubuntu0.5 causing sync errors
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: rsync (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/2009575 Title: Upgrade to 3.1.3-8ubuntu0.5 causing sync errors Status in rsync package in Ubuntu: Confirmed Bug description: Hi Several systems upgraded their rsync package from 3.1.3-8ubuntu0.4 to 3.1.3-8ubuntu0.5 overnight. Automated syncs are now failing with: receiving file list ... ERROR: rejecting unrequested file-list name: [redacted] rsync error: protocol incompatibility (code 2) at flist.c(916) [Receiver=3.1.3] Reverting to the previous release solves the problem. This has been seen on multiple servers running 20.04 on amd64, I'll update this bug with details if we find it on other series too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2009575/+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 2009575] [NEW] Upgrade to 3.1.3-8ubuntu0.5 causing sync errors
Public bug reported: Hi Several systems upgraded their rsync package from 3.1.3-8ubuntu0.4 to 3.1.3-8ubuntu0.5 overnight. Automated syncs are now failing with: receiving file list ... ERROR: rejecting unrequested file-list name: [redacted] rsync error: protocol incompatibility (code 2) at flist.c(916) [Receiver=3.1.3] Reverting to the previous release solves the problem. This has been seen on multiple servers running 20.04 on amd64, I'll update this bug with details if we find it on other series too. ** Affects: rsync (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/2009575 Title: Upgrade to 3.1.3-8ubuntu0.5 causing sync errors Status in rsync package in Ubuntu: Confirmed Bug description: Hi Several systems upgraded their rsync package from 3.1.3-8ubuntu0.4 to 3.1.3-8ubuntu0.5 overnight. Automated syncs are now failing with: receiving file list ... ERROR: rejecting unrequested file-list name: [redacted] rsync error: protocol incompatibility (code 2) at flist.c(916) [Receiver=3.1.3] Reverting to the previous release solves the problem. This has been seen on multiple servers running 20.04 on amd64, I'll update this bug with details if we find it on other series too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2009575/+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 2009506] Re: Input from an external mic can be barely noticeable, or not hearable at all
** Summary changed: - PCI/internal sound card not detected + Input from an external mic can be barely noticeable, or not hearable at all ** Description changed: The microphone from an external device not working. Input from an external mic can be barely noticeable, or not hearable at all. The headset is connected by a jack port. + No option to adjust gain level for external Microphone(headset). + Checked with different working headset. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: maryna 1598 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: maryna 1598 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 6 17:26:30 2023 InstallationDate: Installed on 2023-02-03 (31 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0GGCMJ dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd09/06/2022:br1.19:svnDellInc.:pnVostro3500:pvr:rvnDellInc.:rn0GGCMJ:rvrA01:cvnDellInc.:ct10:cvr:sku0A24: dmi.product.family: Vostro dmi.product.name: Vostro 3500 dmi.product.sku: 0A24 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2023-02-13T11:13:28.057933 -- 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/2009506 Title: Input from an external mic can be barely noticeable, or not hearable at all Status in alsa-driver package in Ubuntu: New Bug description: The microphone from an external device not working. Input from an external mic can be barely noticeable, or not hearable at all. The headset is connected by a jack port. No option to adjust gain level for external Microphone(headset). Checked with different working headset. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maryna 1598 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 6 17:26:30 2023 InstallationDate: Installed on 2023-02-03 (31 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0GGCMJ dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd09/06/2022:br1.19:svnDellInc.:pnVostro3500:pvr:rvnDellInc.:rn0GGCMJ:rvrA01:cvnDellInc.:ct10:cvr:sku0A24: dmi.product.family: Vostro dmi.product.name: Vostro 3500 dmi.product.sku: 0A24 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2023-02-13T11:13:28.057933 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2009506/+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
