[Touch-packages] [Bug 2025116] [NEW] apt-key saves key in legacy trusted.gpg keyring (/etc/apt/trusted.gpg)
Public bug reported: Hi Everyone, I want to install Firefox from Mozilla PPA. I added issued apt-key (from apt package) to fetch the signing key, and then enabled the PPA in /etc/apt/sources.list.d/mozillateam-ubuntu-ppa-jammy.list. The apt-key command used was: sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 9BDB3D89CE49EC21 Then, upon apt-get update: # sudo apt-get update Hit:1 http://us.archive.ubuntu.com/ubuntu jammy InRelease ... Reading package lists... Done W: https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. - In the old days, we were supposed to put keys at /etc/apt/trusted.gpg.d. If I am parsing things correctly nowadays... a new method is supposed to be used: adding [signed-by=] to the sources.list line and putting the key in /usr/share/keyrings or /etc/apt/keyrings [1]. [1] https://lists.debian.org/debian-user/2023/06/msg00722.html - A related bug appears to be https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/1995825. The 1995825 appears to trigger after an upgrade. For me, this is a fresh install. There was no upgrade. - This is Ubuntu 22.04 LTS, x86_64, fully patched. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.2 LTS Release:22.04 Codename: jammy - $ dpkg -S /usr/bin/apt-key apt: /usr/bin/apt-key $ apt-cache show apt Package: apt Architecture: amd64 Version: 2.4.9 Priority: important Section: admin Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: APT Development Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 4156 Provides: apt-transport-https (= 2.4.9) Depends: adduser, gpgv | gpgv2 | gpgv1, libapt-pkg6.0 (>= 2.4.9), ubuntu-keyring, libc6 (>= 2.34), libgcc-s1 (>= 3.3.1), libgnutls30 (>= 3.7.0), libseccomp2 (>= 2.4.2), libstdc++6 (>= 11), libsystemd0 Recommends: ca-certificates ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- 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/2025116 Title: apt-key saves key in legacy trusted.gpg keyring (/etc/apt/trusted.gpg) Status in apt package in Ubuntu: New Bug description: Hi Everyone, I want to install Firefox from Mozilla PPA. I added issued apt-key (from apt package) to fetch the signing key, and then enabled the PPA in /etc/apt/sources.list.d/mozillateam-ubuntu-ppa-jammy.list. The apt- key command used was: sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 9BDB3D89CE49EC21 Then, upon apt-get update: # sudo apt-get update Hit:1 http://us.archive.ubuntu.com/ubuntu jammy InRelease ... Reading package lists... Done W: https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. - In the old days, we were supposed to put keys at /etc/apt/trusted.gpg.d. If I am parsing things correctly nowadays... a new method is supposed to be used: adding [signed-by=] to the sources.list line and putting the key in /usr/share/keyrings or /etc/apt/keyrings [1]. [1] https://lists.debian.org/debian-user/2023/06/msg00722.html - A related bug appears to be https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/1995825. The 1995825 appears to trigger after an upgrade. For me, this is a fresh install. There was no upgrade. - This is Ubuntu 22.04 LTS, x86_64, fully patched. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.2 LTS Release:22.04 Codename: jammy - $ dpkg -S /usr/bin/apt-key apt: /usr/bin/apt-key $ apt-cache show apt Package: apt Architecture: amd64 Version: 2.4.9 Priority: important Section: admin Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: APT Development Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 4156 Provides: apt-transport-https (= 2.4.9) Depends: adduser, gpgv | gpgv2 | gpgv1, libapt-pkg6.0 (>= 2.4.9), ubuntu-keyring, libc6 (>= 2.34), libgcc-s1 (>= 3.3.1), libgnutls30 (>= 3.7.0), libseccomp2 (>= 2.4.2), libstdc++6 (>= 11), libsystemd0 Recommends: ca-certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2025116/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post
[Touch-packages] [Bug 1906729] Re: Suspend and hibernate work, but hybrid-suspend does not
Yes, I have just confirmed: * Suspend works * Hibernate works * Hybrid Sleep does not work More specifically, Hybrid sleep results in what appears to be a successful suspend (after a longer period, because it is saving hibernation data). When an awakening is attempted, it fails, and the system must be forced to shutdown. During the failed awakening, you can see a brief flash of the screen (without the lock screen) and then it goes black again. After forced/BIOS shutdown, the system doesn't recover from hibernation -- but that's not really surprising, because it most likely attempted to wake from memory and fudged things then. My system fails in a fairly similar way when I try to sleep using 'freeze' (which *should* be less intrusive than 'mem', but 'mem' works). suspend-then-hibernate works great, though. Only hybrid-suspend is broken for me. ** Changed in: systemd (Ubuntu) Status: Incomplete => New ** Description changed: I have a Lenovo e585, if it's relevant. I'm running Ubuntu 20.04, and `systemd 245 (245.4-4ubuntu3.3)`. + EDIT: This is now 22.04 and `249 (249.11-0ubuntu3.9)` Suspend on my system doesn't wake up consistently, but hibernate does. Hybrid suspend would make an excellent fallback if wake fails. Since both work independently, they *should* work together. Happy to help debug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 16:58:44 2020 InstallationDate: Installed on 2020-05-06 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20KVCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-56-generic root=UUID=17333443-bf13-4111-b659-028e71aff61a ro rootflags=subvol=@ resume=UUID=5d93ce37-7478-43d9-9564-618e60725242 quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [MASKED] /etc/systemd/system/samba-ad-dc.service → /usr/lib/systemd/system/samba-ad-dc.service [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0UET74W (1.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0UET74W(1.54):bd07/23/2019:svnLENOVO:pn20KVCTO1WW:pvrThinkPadE585:rvnLENOVO:rn20KVCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E585 dmi.product.name: 20KVCTO1WW dmi.product.sku: LENOVO_MT_20KV_BU_Think_FM_ThinkPad E585 dmi.product.version: ThinkPad E585 dmi.sys.vendor: LENOVO mtime.conffile..etc.systemd.sleep.conf: 2020-12-03T16:22:33.696671 -- 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/1906729 Title: Suspend and hibernate work, but hybrid-suspend does not Status in systemd package in Ubuntu: New Bug description: I have a Lenovo e585, if it's relevant. I'm running Ubuntu 20.04, and `systemd 245 (245.4-4ubuntu3.3)`. EDIT: This is now 22.04 and `249 (249.11-0ubuntu3.9)` Suspend on my system doesn't wake up consistently, but hibernate does. Hybrid suspend would make an excellent fallback if wake fails. Since both work independently, they *should* work together. Happy to help debug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 16:58:44 2020 InstallationDate: Installed on 2020-05-06 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20KVCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-56-generic root=UUID=17333443-bf13-4111-b659-028e71aff61a ro rootflags=subvol=@ resume=UUID=5d93ce37-7478-43d9-9564-618e60725242 quiet splash vt.handoff=7
[Touch-packages] [Bug 2024948] Re: librtaudio-dev has unresolvable dependencies on 22.04.2.
You are correct, it was set to 'security updates only.' After changing to 'All updates' and updating, I was able to install librtaudio-dev finally and some related dependencies were updated with that operation (pulse things). I think my issue is solved! :) -- 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/2024948 Title: librtaudio-dev has unresolvable dependencies on 22.04.2. Status in pulseaudio package in Ubuntu: Incomplete Bug description: sudo apt install librtaudio-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libpulse-dev : Depends: libpulse0 (= 1:15.99.1+dfsg1-1ubuntu1) but 1:15.99.1+dfsg1-1ubuntu2.1 is to be installed Depends: libpulse-mainloop-glib0 (= 1:15.99.1+dfsg1-1ubuntu1) but 1:15.99.1+dfsg1-1ubuntu2.1 is to be installed E: Unable to correct problems, you have held broken packages. I have no held packages. I have seen chatter around a project that depends on librtaudio-dev suggesting it is a package maintenance issue but not sure myself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2024948/+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 2024926] Re: add-apt-repository has a misleading error message when the launchpad api is down
Note that this was due to a very specialized kind of outage, namely
where the machine-readable API description file fetched from
api.launchpad.net refers to api.launchpad.test (which only exists in
some development setups and shouldn't be referred to from production).
This part of the problem was on us (the Launchpad team), and we've fixed
it.
It's also a little surprising, since we had other reports of clients
(including at least one that was also running Ubuntu 22.04) instead
raising the rather clearer `httplib2.error.ServerNotFoundError: Unable
to find the server at api.launchpad.test` (still a bit confusing of
course, but it points to the problem about as well as it can). I don't
know why `socket.getaddrinfo` would raise `EBUSY` in this case, though.
--
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/2024926
Title:
add-apt-repository has a misleading error message when the launchpad
api is down
Status in software-properties package in Ubuntu:
New
Bug description:
On Ubuntu 22.04.2
Package software-properties-common 0.99.22.7
During the launchpad outage on the 23rd June 2023, add-apt-repository was
crashing with the following:
Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 364, in
sys.exit(0 if addaptrepo.main() else 1)
File "/usr/bin/add-apt-repository", line 347, in main
shortcut = handler(source, **shortcut_params)
File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line
40, in shortcut_handler
return handler(shortcut, **kwargs)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 82,
in __init__
if self.lpppa.publish_debug_symbols:
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 120,
in lpppa
self._lpppa = self.lpteam.getPPAByName(name=self.ppaname)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 107,
in lpteam
self._lpteam = self.lp.people(self.teamname)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 98,
in lp
self._lp = login_func("%s.%s" % (self.__module__,
self.__class__.__name__),
File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 494,
in login_anonymously
return cls(
File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 230,
in __init__
super(Launchpad, self).__init__(
File "/usr/lib/python3/dist-packages/lazr/restfulclient/resource.py", line
477, in __init__
self._browser.get(root_resource), 'application/json')
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line
439, in get
response, content = self._request(url, extra_headers=headers)
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line
389, in _request
response, content = self._request_and_retry(
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line
359, in _request_and_retry
response, content = self._connection.request(
File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1725, in
request
(response, content) = self._request(
File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 144,
in _request
response, content = super(LaunchpadOAuthAwareHttp, self)._request(
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line
184, in _request
return super(RestfulHttp, self)._request(
File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1441, in
_request
(response, content) = self._conn_request(conn, request_uri, method, body,
headers)
File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1363, in
_conn_request
conn.connect()
File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1139, in
connect
address_info = socket.getaddrinfo(host, port, 0, socket.SOCK_STREAM)
File "/usr/lib/python3.10/socket.py", line 955, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
OSError: [Errno 16] Device or resource busy
This was misleading as it seemed to indicate a problem with the client and
not with the server. The error message should be improved as to make it clear
where the error is located.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2024926/+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 2025098] [NEW] man page for limits.conf (part of libpam-modules) incorrectly describes core dump settings
Public bug reported: `man limits.conf` reports that the "core" setting "limits the core file size (KB)". However, if I set the size to 3200: # Limit the size of core dumps (32GB = 3200KB) * soft core 3200 * hard core 3200 Then reboot and check the size with ulimit: $ ulimit -a | grep core core file size (blocks, -c) 3200 ulimit reports that the setting is in 512-byte blocks, not 1024-byte KBs. In other words, according to ulimit, rather than getting 32GB I'm getting 16GB. Is the man page correct and the setting is in KB or is ulimit correct in reporting the setting in blocks? One of them is wrong. -- FWIW, I tried to report this as an issue with the libpam-modules package because dpkg says that's the package limits.conf is shipped with: $ dpkg -S /etc/security/limits.conf libpam-modules:amd64: /etc/security/limits.conf However, when I tried to do that Launchpad responded: "libpam-modules" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Tags: libpam-modules limits.conf manpage ulimit -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2025098 Title: man page for limits.conf (part of libpam-modules) incorrectly describes core dump settings Status in pam package in Ubuntu: New Bug description: `man limits.conf` reports that the "core" setting "limits the core file size (KB)". However, if I set the size to 3200: # Limit the size of core dumps (32GB = 3200KB) * soft core 3200 * hard core 3200 Then reboot and check the size with ulimit: $ ulimit -a | grep core core file size (blocks, -c) 3200 ulimit reports that the setting is in 512-byte blocks, not 1024-byte KBs. In other words, according to ulimit, rather than getting 32GB I'm getting 16GB. Is the man page correct and the setting is in KB or is ulimit correct in reporting the setting in blocks? One of them is wrong. -- FWIW, I tried to report this as an issue with the libpam-modules package because dpkg says that's the package limits.conf is shipped with: $ dpkg -S /etc/security/limits.conf libpam-modules:amd64: /etc/security/limits.conf However, when I tried to do that Launchpad responded: "libpam-modules" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2025098/+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 2024948] Re: librtaudio-dev has unresolvable dependencies on 22.04.2.
>I don't know all the vagaries of the package versioning but it seems my apt isn't finding the latest libpulse-dev or something. Yes, exactly :) If we do a little comparison here: ~$ apt policy libpulse-dev libpulse0 libpulse-dev: Installed: (none) Candidate: 1:15.99.1+dfsg1-1ubuntu2.1 Version table: 1:15.99.1+dfsg1-1ubuntu2.1 500 500 http://no.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 1:15.99.1+dfsg1-1ubuntu1 500 500 http://no.archive.ubuntu.com/ubuntu jammy/main amd64 Packages libpulse0: Installed: 1:15.99.1+dfsg1-1ubuntu2.1 Candidate: 1:15.99.1+dfsg1-1ubuntu2.1 Version table: *** 1:15.99.1+dfsg1-1ubuntu2.1 500 500 http://no.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:15.99.1+dfsg1-1ubuntu1 500 500 http://no.archive.ubuntu.com/ubuntu jammy/main amd64 Packages I reckon installed version is pretty straight-forward. Candidate is picking the latest version from the table below, in other words if I install this package this is the version I would get. In this case we have the ubuntu1 version from jammy/main which is the unchanged version from the time 22.04 was released. And then we get the ubuntu2.1 version in jammy/updates with a newer version number made after the initial release. There's jammy/updates as well as jammy/security and other third party repos like the postgres one and it will resolve these to pick the candidate. So like you correctly said, you have the ubuntu2.1 version for some of the packages but when you try to install more they only know about the ubuntu1 versions. And since the packages should stay consistent a conflict occurs. This is also confirmed by your apt-cache policy, you'll see you have jammy/* and jammy-security/* but not jammy-updates/*. So you get the security updates, but not the regular updates. What you could try is go to `software-properties-gtk` -> "Updates" -> "Subscribed to". I suspect this is set to "Security updates only" and if you switch to "All updates" I believe this should enabled jammy/updates. There might be other ways, but you want to check that you get jammy- updates/* for the archives where you have jammy/* and jammy-security/* enabled. ** Package changed: rtaudio (Ubuntu) => pulseaudio (Ubuntu) -- 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/2024948 Title: librtaudio-dev has unresolvable dependencies on 22.04.2. Status in pulseaudio package in Ubuntu: Incomplete Bug description: sudo apt install librtaudio-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libpulse-dev : Depends: libpulse0 (= 1:15.99.1+dfsg1-1ubuntu1) but 1:15.99.1+dfsg1-1ubuntu2.1 is to be installed Depends: libpulse-mainloop-glib0 (= 1:15.99.1+dfsg1-1ubuntu1) but 1:15.99.1+dfsg1-1ubuntu2.1 is to be installed E: Unable to correct problems, you have held broken packages. I have no held packages. I have seen chatter around a project that depends on librtaudio-dev suggesting it is a package maintenance issue but not sure myself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2024948/+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 2024864] Re: systemd-networkd crashes with SIGSEGV
** Description changed:
+ [ Impact ]
+
Customer reported that this issue happens randomly during their
automated regression runs. It's not consistent and hard to reproduce.
They have shared a coredump:
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x555962aa1c34 in link_drop_foreign_config
(link=link@entry=0x555963583f30) at ../src/network/networkd-link.c:2741
2741 ../src/network/networkd-link.c: No such file or directory.
(gdb) bt
#0 0x555962aa1c34 in link_drop_foreign_config
(link=link@entry=0x555963583f30) at ../src/network/networkd-link.c:2741
#1 0x555962aa233d in link_carrier_lost.lto_priv.328 (link=, link=) at ../src/network/networkd-link.c:3462
#2 0x555962a8e9b2 in link_update (m=0x5559635702c0, link=)
at ../src/network/networkd-link.c:3698
#3 manager_rtnl_process_link (rtnl=, message=0x5559635702c0,
userdata=) at ../src/network/networkd-manager.c:713
#4 0x555962a48a16 in process_match (m=0x5559635702c0,
rtnl=0x55596355d990) at ../src/libsystemd/sd-netlink/sd-netlink.c:388
#5 process_running (ret=0x0, rtnl=0x55596355d990) at
../src/libsystemd/sd-netlink/sd-netlink.c:418
#6 sd_netlink_process (rtnl=0x55596355d990, ret=ret@entry=0x0) at
../src/libsystemd/sd-netlink/sd-netlink.c:452
#7 0x555962a48cb3 in time_callback (s=, usec=, userdata=) at ../src/libsystemd/sd-netlink/sd-netlink.c:759
#8 0x555962a4dbae in source_dispatch (s=s@entry=0x55596355dce0) at
../src/libsystemd/sd-event/sd-event.c:2311
#9 0x555962a4de2a in sd_event_dispatch (e=,
e@entry=0x55596355bf70) at ../src/libsystemd/sd-event/sd-event.c:2663
#10 0x555962a4dfb9 in sd_event_run (e=,
e@entry=0x55596355bf70, timeout=timeout@entry=18446744073709551615) at
../src/libsystemd/sd-event/sd-event.c:2723
#11 0x555962a4e1fb in sd_event_loop (e=) at
../src/libsystemd/sd-event/sd-event.c:2744
#12 0x555962a223d6 in main (argc=, argv=)
at ../src/network/networkd.c:158
- The following patch fixes the issue:
-
https://github.com/systemd/systemd/commit/b1b0b42e48303134731e017a108c6c334ef5f4c8
- I was able simulate it to happen on gdb, by breaking once the manager is
- setup, getting the loopback device and running link_drop_foreign_config
- on the loopback device:
+ This can be fixed by simply null checking link->network before doing anything
with it. Upstream has fixed it on this commit:
https://github.com/systemd/systemd/commit/b1b0b42e48303134731e017a108c6c334ef5f4c8
+
+ [ Test Plan ]
+
+ Since this issue is hard to reproduce, I was able trigger it on gdb, by
+ adding a breakpoint once the manager is setup, getting the loopback
+ device and running link_drop_foreign_config on the loopback device:
(gdb) b src/network/networkd.c:150
Breakpoint 1 at 0x2f38f: file ../src/network/networkd.c, line 150.
(gdb) r
Starting program: /lib/systemd/systemd-networkd
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
eth0: IPv6 successfully enabled
eth0: Gained IPv6LL
Breakpoint 1, main (argc=, argv=) at
../src/network/networkd.c:152
152 log_info("Enumeration completed");
(gdb) p *m->links
$1 = {b = {hash_ops = 0x5578f230 , {indirect = {storage
= 0x2e, hash_key = "\200\376yUUU\000\000\001\000\000\000\000\000\000",
n_entries = 1434074992, n_buckets = 21845, idx_lowest_entry = 256,
_pad = "\000\000"}, direct = {
storage =
".\000\000\000\000\000\000\000\200\376yUUU\000\000\001\000\000\000\000\000\000\000p?zUUU\000\000\000\001\000\000\000\000"}},
type = HASHMAP_TYPE_PLAIN, has_indirect = false, n_direct_entries = 2,
from_pool = true}}
(gdb) set $mylink = (Link **) malloc(sizeof(Link *))
(gdb) call link_get(m, 1, $mylink)
$2 = 0
(gdb) p *$mylink
$3 = (Link *) 0x557a3f70
(gdb) p **$mylink
$4 = {manager = 0x55796940, n_ref = 2, ifindex = 1, master_ifindex = 0,
ifname = 0x557a0060 "lo", kind = 0x0, iftype = 772,
state_file = 0x5579c670 "/run/systemd/netif/links/1", mac =
{ether_addr_octet = "\000\000\000\000\000"}, ipv6ll_address = {__in6_u = {
__u6_addr8 = '\000' , __u6_addr16 = {0, 0, 0, 0, 0,
0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, mtu = 65536, udev_device = 0x0,
flags = 65609, kernel_operstate = 0 '\000', network = 0x0, state =
LINK_STATE_UNMANAGED, operstate = LINK_OPERSTATE_CARRIER, address_messages = 0,
address_label_messages = 0, route_messages = 0,
routing_policy_rule_messages = 0, routing_policy_rule_remove_messages = 0,
enslaving = 0,
addresses = 0x0, addresses_foreign = 0x55796120, routes = 0x0,
routes_foreign = 0x55796180, addresses_configured = false,
addresses_ready = false, dhcp_client = 0x0, dhcp_lease = 0x0, lease_file =
0x5579c620 "/run/systemd/netif/leases/1", original_mtu = 0,
dhcp4_messages = 0, dhcp4_configured = false, dhcp6_configured = false,
ndisc_messages = 0, ndisc_configured = false, ipv4ll =
[Touch-packages] [Bug 1990542] Re: initrd starts dhclient on interfaces that are not supposed to get an IP address
Right. The handover from basic networking in initrd to the full Netplan setup in the booting/booted system could probably be improved (in may ways), e.g. flushing the IP addresses. I guess that's something we'd need to implement in systemd-networkd when taking over the interfaces. I wonder if NetworkManager is handling this situation any different here? Did you try installing the "network- manager" package and using the global "renderer: NetworkManager" setting in your Netplan configuration? Does it show the same result? ** Changed in: netplan.io (Ubuntu) Importance: Medium => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1990542 Title: initrd starts dhclient on interfaces that are not supposed to get an IP address Status in initramfs-tools package in Ubuntu: Triaged Status in netplan.io package in Ubuntu: Triaged Bug description: After trying several setups, I think this is a bug. If not - I can't find how to fix things. Setup: Ubuntu 22.04, with ubuntu-minimal installed (which depends on isc-dhcp-client). A network with a bridge interface. This can be anything, even an old /etc/network/interfaces file will do. For simplicity, the following netplan setup is used: network: version: 2 ethernets: enp4s0: wakeonlan: true dhcp4: no dhcp6: no bridges: br0: interfaces: [enp4s0] dhcp4: yes dhcp6: yes parameters: stp: false forward-delay: 0 What happens: Starting this machine will, during initrd phase, make dhclient fetch an IP address for enp4s0. Then netplan takes over and fetches an address for br0. If both enp4s0 and br0 have the same IP address from the DHCP-server, the machine will not be reachable. What should happen: enp4s0 should not get an IP address, as the netplan-configuration clearly says. A workaround is to remove isc-dhcp-client (which, in turn, removes meta-package ubuntu-minimal) and run update-initramfs -k all -u; afterwards, the dhclient in initrd is (obviously) not there anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1990542/+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 2020229] Re: settings doesn't show all sound devices
See attached output as requested. As I noted in a comment above, this problem appears to have been fixed in one of the patches since I submitted the initial report. It's now working correctly. ** Attachment added: "log.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2020229/+attachment/5682103/+files/log.txt -- 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/2020229 Title: settings doesn't show all sound devices Status in alsa-driver package in Ubuntu: Incomplete Bug description: After upgrading to 23.04, the settings -> sound -> output device and input device menus no longer show a class-compliant usb audio interface. aplay -l shows the audio device is present (see attached screenshot). This was working correctly before upgrading. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 19 16:58:53 2023 InstallationDate: Installed on 2022-07-29 (294 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to lunar on 2023-04-22 (27 days ago) dmi.bios.date: 04/10/2022 dmi.bios.release: 1.18 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E155LAMS.112 dmi.board.asset.tag: Default string dmi.board.name: MS-155L dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE155LAMS.112:bd04/10/2022:br1.18:svnMicro-StarInternationalCo.,Ltd.:pnModern15A5M:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-155L:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku155L.1: dmi.product.family: Modern dmi.product.name: Modern 15 A5M dmi.product.sku: 155L.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2020229/+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 2024870] Re: accountsservice package
** Changed in: accountsservice (Ubuntu) Importance: Undecided => High ** Changed in: accountsservice (Ubuntu) Status: New => Fix Committed ** Summary changed: - accountsservice package + accountsservice segfault when toggling autologin -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2024870 Title: accountsservice segfault when toggling autologin Status in accountsservice package in Ubuntu: Fix Committed Bug description: Error encountered after first boot ubuntu-gnome-desktop installed on LiveServer Daily 23.10 attempting to set AutoLogin in Settings>User. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: accountsservice 23.13.9-1ubuntu1 Uname: Linux 6.3.0-7-generic x86_64 Architecture: amd64 Date: Thu Jun 22 21:28:14 2023 ExecutablePath: /usr/libexec/accounts-daemon ExecutableTimestamp: 1687359023 ProcCmdline: /usr/libexec/accounts-daemon ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) Signal: 11 SourcePackage: accountsservice UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2024870/+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 2024585] Re: dbus-daemon segfault if group lookup fails
Thanks, interesting discussion. It's also worth noting that newer Ubuntu
versions have the current dbus serie with SO_PEERGROUPS support so the
issue should be resolved there
** Changed in: dbus (Ubuntu)
Importance: Undecided => High
** Changed in: dbus (Ubuntu)
Status: New => Triaged
** Changed in: dbus (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/2024585
Title:
dbus-daemon segfault if group lookup fails
Status in D-Bus:
Unknown
Status in dbus package in Ubuntu:
Fix Released
Bug description:
Ubuntu release: Ubuntu 22.04.2 LTS (but also tested on Ubuntu 20.04.6 LTS)
dbus version: 1.12.20-2ubuntu4.1
This is related to
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2023598, in which
an sssd was upgraded before its libraries. This caused dbus-daemon to
crash, which in turn ended the user's X session along with many other
programs. It also triggered NetworkManager to exit so it was no longer
doing DHCP renewals; he network connection was lost a few hours later
when the lease expired.
The failure of dbus-daemon was triggered by it reloading its
configuration while group lookups were not functioning, which revealed
an error in the dbus's error handling code.
The failure happened in two stages.
First, it failed to load the policy, and reported this error:
dbus-daemon[1207]: Unable to reload configuration: (null)
Then, a few seconds later, dbus-daemon reloaded its config again, and
this time it segfaulted.
dbus-daemon[1207]: segfault at 0 ip 5602b18336e4 sp 7ffe2579de28
error 6 in dbus-daemon[5602b181b000+24000]
Code: 00 00 00 48 83 c4 08 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f
1e fa 83 07 01 48 89 f8 c3
0f 1f 44 00 00 f3 0f 1e fa <83> 2f 01 74 07 c3 66 0f 1f 44 00 00 e9 bb
fb ff ff 66 66 2e 0f 1f
The code corresponds to policy->refcount -= 1, inside
bus_client_policy_unref(). This error can only happen if policy was
NULL on entry.
bus_connections_reload_policy() has this code:
// connection.c line 1644
bus_client_policy_unref (d->policy);
d->policy = bus_context_create_client_policy (connections->context,
connection,
error);
if (d->policy == NULL)
{
_dbus_verbose ("Failed to create security policy for connection
%p\n",
connection);
_DBUS_ASSERT_ERROR_IS_SET (error);
return FALSE;
}
If bus_context_create_client_policy fails, the code decrements the
policy reference count and sets d->policy to NULL. The second time
round, the reference count is decremented again, but policy is already
NULL from last time round, hence the crash.
I've included a patch that I think should fix the error, but note that
it is not well tested!
Peter
To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/2024585/+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 2024585] Re: dbus-daemon segfault if group lookup fails
Closing since the problem is fixed in the current Ubuntu serie, if we
decide to SRU a fix to 22.04 we will add that target serie to the report
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/2024585
Title:
dbus-daemon segfault if group lookup fails
Status in D-Bus:
Unknown
Status in dbus package in Ubuntu:
Fix Released
Bug description:
Ubuntu release: Ubuntu 22.04.2 LTS (but also tested on Ubuntu 20.04.6 LTS)
dbus version: 1.12.20-2ubuntu4.1
This is related to
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2023598, in which
an sssd was upgraded before its libraries. This caused dbus-daemon to
crash, which in turn ended the user's X session along with many other
programs. It also triggered NetworkManager to exit so it was no longer
doing DHCP renewals; he network connection was lost a few hours later
when the lease expired.
The failure of dbus-daemon was triggered by it reloading its
configuration while group lookups were not functioning, which revealed
an error in the dbus's error handling code.
The failure happened in two stages.
First, it failed to load the policy, and reported this error:
dbus-daemon[1207]: Unable to reload configuration: (null)
Then, a few seconds later, dbus-daemon reloaded its config again, and
this time it segfaulted.
dbus-daemon[1207]: segfault at 0 ip 5602b18336e4 sp 7ffe2579de28
error 6 in dbus-daemon[5602b181b000+24000]
Code: 00 00 00 48 83 c4 08 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f
1e fa 83 07 01 48 89 f8 c3
0f 1f 44 00 00 f3 0f 1e fa <83> 2f 01 74 07 c3 66 0f 1f 44 00 00 e9 bb
fb ff ff 66 66 2e 0f 1f
The code corresponds to policy->refcount -= 1, inside
bus_client_policy_unref(). This error can only happen if policy was
NULL on entry.
bus_connections_reload_policy() has this code:
// connection.c line 1644
bus_client_policy_unref (d->policy);
d->policy = bus_context_create_client_policy (connections->context,
connection,
error);
if (d->policy == NULL)
{
_dbus_verbose ("Failed to create security policy for connection
%p\n",
connection);
_DBUS_ASSERT_ERROR_IS_SET (error);
return FALSE;
}
If bus_context_create_client_policy fails, the code decrements the
policy reference count and sets d->policy to NULL. The second time
round, the reference count is decremented again, but policy is already
NULL from last time round, hence the crash.
I've included a patch that I think should fix the error, but note that
it is not well tested!
Peter
To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/2024585/+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 2024661] Re: Unable to configure Wireguard connection at NetworkManager interface
https://github.com/canonical/netplan/pull/371 ** Changed in: netplan.io (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2024661 Title: Unable to configure Wireguard connection at NetworkManager interface Status in netplan.io package in Ubuntu: In Progress Status in network-manager package in Ubuntu: Invalid Bug description: Repro steps: 1) Open NetworkManager GUI. 2) Click "Add new Connection" and select "Wireguard" connection type. 3) Then you have to configure new connection. Basic configuration looks like that: a) Write down connection name, b) Write down local private key, c) Create new peer and populate peer's parameters: public key of the peer, allowed IPs (i.e. 0.0.0.0/0), peer's IP address and port. 4) Click "OK" and "Save". 5) Open "Peers" again. Ensure that settings were not stored. All fields are empty. Found in Kubuntu flavor version 23.10 (development), Plasma Network Manager interface. netplan.io 0.106.1-2 network-manager 1.42.4-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2024661/+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 2024585] Re: dbus-daemon segfault if group lookup fails
** Also affects: dbus via
https://gitlab.freedesktop.org/dbus/dbus/-/issues/343
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/2024585
Title:
dbus-daemon segfault if group lookup fails
Status in D-Bus:
Unknown
Status in dbus package in Ubuntu:
Fix Released
Bug description:
Ubuntu release: Ubuntu 22.04.2 LTS (but also tested on Ubuntu 20.04.6 LTS)
dbus version: 1.12.20-2ubuntu4.1
This is related to
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2023598, in which
an sssd was upgraded before its libraries. This caused dbus-daemon to
crash, which in turn ended the user's X session along with many other
programs. It also triggered NetworkManager to exit so it was no longer
doing DHCP renewals; he network connection was lost a few hours later
when the lease expired.
The failure of dbus-daemon was triggered by it reloading its
configuration while group lookups were not functioning, which revealed
an error in the dbus's error handling code.
The failure happened in two stages.
First, it failed to load the policy, and reported this error:
dbus-daemon[1207]: Unable to reload configuration: (null)
Then, a few seconds later, dbus-daemon reloaded its config again, and
this time it segfaulted.
dbus-daemon[1207]: segfault at 0 ip 5602b18336e4 sp 7ffe2579de28
error 6 in dbus-daemon[5602b181b000+24000]
Code: 00 00 00 48 83 c4 08 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f
1e fa 83 07 01 48 89 f8 c3
0f 1f 44 00 00 f3 0f 1e fa <83> 2f 01 74 07 c3 66 0f 1f 44 00 00 e9 bb
fb ff ff 66 66 2e 0f 1f
The code corresponds to policy->refcount -= 1, inside
bus_client_policy_unref(). This error can only happen if policy was
NULL on entry.
bus_connections_reload_policy() has this code:
// connection.c line 1644
bus_client_policy_unref (d->policy);
d->policy = bus_context_create_client_policy (connections->context,
connection,
error);
if (d->policy == NULL)
{
_dbus_verbose ("Failed to create security policy for connection
%p\n",
connection);
_DBUS_ASSERT_ERROR_IS_SET (error);
return FALSE;
}
If bus_context_create_client_policy fails, the code decrements the
policy reference count and sets d->policy to NULL. The second time
round, the reference count is decremented again, but policy is already
NULL from last time round, hence the crash.
I've included a patch that I think should fix the error, but note that
it is not well tested!
Peter
To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/2024585/+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 2025027] Re: When I disconnect PC from LAN, I can't turn on Wi-Fi software-wise. The option to enable Wi-Fi is not available (does not pop up and it is hidden while on LAN). Ther
I have to correct the information - currently even if I rebooted several times, the option "Enable Wireless" is not available :-o -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2025027 Title: When I disconnect PC from LAN, I can't turn on Wi-Fi software-wise. The option to enable Wi-Fi is not available (does not pop up and it is hidden while on LAN). Therefore, I can't see any available WiFi networks. The issue gets resolved when I reboot the PC. Status in network-manager package in Ubuntu: Incomplete Bug description: See my public question open here: https://askubuntu.com/questions/1474771/wifi-control-gone-after-used-lan-cable-22-04-mate I'd expect, to see the option "dis/enable wifi" at least when I disconnect from LAN, (if not regardless on LAN connection). But I can not see that option to enable wifi, nor available wifi networks even when I disconnect the LAN cable.. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.6-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-75.82-generic 5.15.99 Uname: Linux 5.15.0-75-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon Jun 26 09:48:33 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2023-02-09 (136 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IpRoute: default via 192.168.1.1 dev enx00051b9a09b6 proto dhcp metric 100 169.254.0.0/16 dev enx00051b9a09b6 scope link metric 1000 192.168.1.0/24 dev enx00051b9a09b6 proto kernel scope link src 192.168.1.2 metric 100 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.6 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2025027/+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 2025027] Re: When I disconnect PC from LAN, I can't turn on Wi-Fi software-wise. The option to enable Wi-Fi is not available (does not pop up and it is hidden while on LAN). Ther
1. I boot my PC with LAN cable connected. Lan works, but I only see "Enable networking" when I open the network manager options in the top right corner of the screen. I guess, the "Enable Wireless" option is disabled deliberately, while on LAN - which is not the best idea IMHO. Can't screenshot as this view hides when I click anything else - like screenshot utility. 2. Then I disconnect my LAN cable. The wired network icon changes and message shows LAN network disconnected. I click the disconnected network icon to open the roll - down menu and enable wireless => I would expect this option will be available now. 3. But the "Enable Wireless" option is still NOT AVAILABLE. Hence I can not choose from available wifi networks and must only use LAN connection. 4. When I reboot PC WITH LAN CABLE DISCONNECTED, the WiFi automatically connects and the "Enable Wireless" is available again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2025027 Title: When I disconnect PC from LAN, I can't turn on Wi-Fi software-wise. The option to enable Wi-Fi is not available (does not pop up and it is hidden while on LAN). Therefore, I can't see any available WiFi networks. The issue gets resolved when I reboot the PC. Status in network-manager package in Ubuntu: Incomplete Bug description: See my public question open here: https://askubuntu.com/questions/1474771/wifi-control-gone-after-used-lan-cable-22-04-mate I'd expect, to see the option "dis/enable wifi" at least when I disconnect from LAN, (if not regardless on LAN connection). But I can not see that option to enable wifi, nor available wifi networks even when I disconnect the LAN cable.. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.6-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-75.82-generic 5.15.99 Uname: Linux 5.15.0-75-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon Jun 26 09:48:33 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2023-02-09 (136 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IpRoute: default via 192.168.1.1 dev enx00051b9a09b6 proto dhcp metric 100 169.254.0.0/16 dev enx00051b9a09b6 scope link metric 1000 192.168.1.0/24 dev enx00051b9a09b6 proto kernel scope link src 192.168.1.2 metric 100 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.6 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2025027/+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 2020229] Re: settings doesn't show all sound devices
Thank you for your bug report. Could you provide the output of $ pw-cli ls in a logfile attached to the bug? Are the devices listed for example in pavucontrol? ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- 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/2020229 Title: settings doesn't show all sound devices Status in alsa-driver package in Ubuntu: Incomplete Bug description: After upgrading to 23.04, the settings -> sound -> output device and input device menus no longer show a class-compliant usb audio interface. aplay -l shows the audio device is present (see attached screenshot). This was working correctly before upgrading. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 19 16:58:53 2023 InstallationDate: Installed on 2022-07-29 (294 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to lunar on 2023-04-22 (27 days ago) dmi.bios.date: 04/10/2022 dmi.bios.release: 1.18 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E155LAMS.112 dmi.board.asset.tag: Default string dmi.board.name: MS-155L dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE155LAMS.112:bd04/10/2022:br1.18:svnMicro-StarInternationalCo.,Ltd.:pnModern15A5M:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-155L:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku155L.1: dmi.product.family: Modern dmi.product.name: Modern 15 A5M dmi.product.sku: 155L.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2020229/+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 1971715] Re: 22.04 idn -a domain.com idn: could not convert from ASCII to UTF-8
Hi, I confirm that the patch fixes input encoding detection issue for me (22.04.2 LTS) Current package: free1 : ~ [0] # echo $LC_ALL en_US.UTF-8 free1 : ~ [0] # dpkg -l idn libidn12 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii idn1.38-4build1 amd64Command line interface to GNU Libidn ii libidn12:amd64 1.38-4build1 amd64GNU Libidn library, implementation of IETF IDN specifications free1 : ~ [0] # idn xxx-tést.eu idn: could not convert from ASCII to UTF-8 free1 : ~ [1] # idn -u xxx-tést.eu idn: could not convert from ASCII to UTF-8 free1 : ~ [1] # idn -a xxx-tést.eu idn: could not convert from ASCII to UTF-8 free1 : ~ [1] # echo ü | idn idn: could not convert from ASCII to UTF-8 free1 : ~ [1] # Package from jammy-proposed: free1 : ~ [130] # echo $LC_ALL en_US.UTF-8 free1 : ~ [0] # dpkg -l idn libidn12 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--= ii idn1.38-4build1 amd64Command line interface to GNU Libidn ii libidn12:amd64 1.38-4ubuntu1 amd64GNU Libidn library, implementation of IETF IDN specifications free1 : ~ [0] # idn xxx-tést.eu xn--xxx-tst-fya.eu free1 : ~ [0] # idn -u xxx-tést.eu xxx-tést.eu free1 : ~ [0] # idn -a xxx-tést.eu xn--xxx-tst-fya.eu free1 : ~ [0] # echo ü | idn xn--tda free1 : ~ [0] # No problems after upgrade so far. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1971715 Title: 22.04 idn -a domain.com idn: could not convert from ASCII to UTF-8 Status in libidn package in Ubuntu: Fix Released Status in libidn source package in Jammy: Fix Committed Status in libidn source package in Kinetic: Fix Released Bug description: [ Impact ] idn cannot handle non-ASCII characters [ Test Plan ] Existing state in 22.04: $ echo ü | idn idn: could not convert from ASCII to UTF-8 Fixed output: $ echo ü | idn xn--tda [ Where problems could occur ] The patch enables an extra autotools features, so the most likely problem is a build failure. Currently non-ASCII characters are entirely unhandled, so there's no risk of regression there, but this could potentially turn clean failures into crashes or incorrect output. [Original report] On Ubuntu 22.04 Jammy: idn -a "xxx-tést.eu" idn: could not convert from ASCII to UTF-8 And idn -u "xn--xxx-tst-fya.eu" idn: could not convert from UTF-8 to ASCII Expected: Successfully conversion from ASCII to UTF-8 Ubuntu 20.04 / 18.04 it works fine Also with idn2 from UTF-8 to ASCII works as expected how ever support lacks from ASCII to UTF-8 Description: Ubuntu 22.04 LTS Release: 22.04 root@test:~# echo $LC_ALL C.UTF-8 root@test:~# apt-cache policy idn idn: Installed: 1.38-4build1 Candidate: 1.38-4build1 Version table: *** 1.38-4build1 500 500 https://mirror.hetzner.com/ubuntu/packages jammy/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1971715/+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 2025027] Re: When I disconnect PC from LAN, I can't turn on Wi-Fi software-wise. The option to enable Wi-Fi is not available (does not pop up and it is hidden while on LAN). Ther
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2025027 Title: When I disconnect PC from LAN, I can't turn on Wi-Fi software-wise. The option to enable Wi-Fi is not available (does not pop up and it is hidden while on LAN). Therefore, I can't see any available WiFi networks. The issue gets resolved when I reboot the PC. Status in network-manager package in Ubuntu: Incomplete Bug description: See my public question open here: https://askubuntu.com/questions/1474771/wifi-control-gone-after-used-lan-cable-22-04-mate I'd expect, to see the option "dis/enable wifi" at least when I disconnect from LAN, (if not regardless on LAN connection). But I can not see that option to enable wifi, nor available wifi networks even when I disconnect the LAN cable.. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.6-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-75.82-generic 5.15.99 Uname: Linux 5.15.0-75-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon Jun 26 09:48:33 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2023-02-09 (136 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IpRoute: default via 192.168.1.1 dev enx00051b9a09b6 proto dhcp metric 100 169.254.0.0/16 dev enx00051b9a09b6 scope link metric 1000 192.168.1.0/24 dev enx00051b9a09b6 proto kernel scope link src 192.168.1.2 metric 100 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.6 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2025027/+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 2025027] [NEW] When I disconnect PC from LAN, I can't turn on Wi-Fi software-wise. The option to enable Wi-Fi is not available (does not pop up and it is hidden while on LAN). Th
Public bug reported: See my public question open here: https://askubuntu.com/questions/1474771/wifi-control-gone-after-used-lan-cable-22-04-mate I'd expect, to see the option "dis/enable wifi" at least when I disconnect from LAN, (if not regardless on LAN connection). But I can not see that option to enable wifi, nor available wifi networks even when I disconnect the LAN cable.. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.6-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-75.82-generic 5.15.99 Uname: Linux 5.15.0-75-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon Jun 26 09:48:33 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2023-02-09 (136 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IpRoute: default via 192.168.1.1 dev enx00051b9a09b6 proto dhcp metric 100 169.254.0.0/16 dev enx00051b9a09b6 scope link metric 1000 192.168.1.0/24 dev enx00051b9a09b6 proto kernel scope link src 192.168.1.2 metric 100 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.6 connected started full enabled enabled disabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Low Status: Incomplete ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2025027 Title: When I disconnect PC from LAN, I can't turn on Wi-Fi software-wise. The option to enable Wi-Fi is not available (does not pop up and it is hidden while on LAN). Therefore, I can't see any available WiFi networks. The issue gets resolved when I reboot the PC. Status in network-manager package in Ubuntu: Incomplete Bug description: See my public question open here: https://askubuntu.com/questions/1474771/wifi-control-gone-after-used-lan-cable-22-04-mate I'd expect, to see the option "dis/enable wifi" at least when I disconnect from LAN, (if not regardless on LAN connection). But I can not see that option to enable wifi, nor available wifi networks even when I disconnect the LAN cable.. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.6-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-75.82-generic 5.15.99 Uname: Linux 5.15.0-75-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon Jun 26 09:48:33 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2023-02-09 (136 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IpRoute: default via 192.168.1.1 dev enx00051b9a09b6 proto dhcp metric 100 169.254.0.0/16 dev enx00051b9a09b6 scope link metric 1000 192.168.1.0/24 dev enx00051b9a09b6 proto kernel scope link src 192.168.1.2 metric 100 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.6 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2025027/+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 1974056] Comment bridged from LTC Bugzilla
--- Comment From wint...@de.ibm.com 2023-06-26 03:07 EDT--- I was not able to reproduce this. Runs fine on my machine (see below). Any ideas how to continue? root@m8360007:~/# cat /etc/os-release PRETTY_NAME="Ubuntu 22.04.2 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.2 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy root@m8360007:~# pull-lp-source iptables Found iptables 1.8.7-1ubuntu7 in mantic Downloading iptables_1.8.7-1ubuntu7.dsc from ports.ubuntu.com (0.003 MiB) [=>]100% Public key not found, could not verify signature Downloading iptables_1.8.7.orig.tar.bz2 from ports.ubuntu.com (0.685 MiB) [=>]100% Downloading iptables_1.8.7-1ubuntu7.debian.tar.xz from ports.ubuntu.com (0.084 MiB) [=>]100% root@m8360007:~# cd iptables-1.8.7/ root@m8360007:~/iptables-1.8.7# ll ./iptables/tests/shell/testcases/iptables/0007-zero-counters_0 -rw-r--r-- 1 root root 1682 Jun 26 08:59 ./iptables/tests/shell/testcases/iptables/0007-zero-counters_0 root@m8360007:~/iptables-1.8.7# chmod +x ./iptables/tests/shell/testcases/iptables/0007-zero-counters_0 root@m8360007:~/iptables-1.8.7# cd iptables/tests/shell root@m8360007:~/iptables-1.8.7/iptables/tests/shell# sudo ./run-tests.sh --host I: [OK] ././testcases/arptables/0001-arptables-save-restore_0 I: [OK] ././testcases/arptables/0002-arptables-restore-defaults_0 I: [OK] ././testcases/arptables/0003-arptables-verbose-output_0 I: [OK] ././testcases/chain/0001duplicate_1 [...] I: [OK] ././testcases/nft-only/0007-mid-restore-flush_0 I: [OK] ././testcases/nft-only/0008-basechain-policy_0 I: [OK] ././testcases/nft-only/0009-needless-bitwise_0 I: nft results: [OK] 50 [FAILED] 0 [TOTAL] 50 I: combined results: [OK] 100 [FAILED] 0 [TOTAL] 100 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1974056 Title: iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless- bitwise_0 fails on s390x Status in iptables: Unknown Status in Ubuntu on IBM z Systems: In Progress Status in iptables package in Ubuntu: New Bug description: In Ubuntu, we execute the full iptables shell testcases across all architectures. They seem to all pass everywhere, however iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless- bitwise_0 is currently failing on s390x like so: command17FAIL stderr: W: [FAILED] ././testcases/nft- only/0009-needless-bitwise_0: expected 0 but got 1 i wonder if there is some endian bug, as this is currently Ubuntu's only big-endian architecture. this can be reproduced with: pull-lp-source iptables cd iptables-1.8.7/ chmod +x ./iptables/tests/shell/testcases/iptables/0007-zero-counters_0 cd iptables/tests/shell sudo ./run-tests.sh --host To manage notifications about this bug go to: https://bugs.launchpad.net/iptables/+bug/1974056/+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 2024985] Re: MT7922 Bluetooth doesn't enable
** Summary changed: - Bluetooth doesn't enable + MT7922 Bluetooth doesn't enable ** Package changed: bluez (Ubuntu) => linux-lowlatency-hwe-5.19 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2024985 Title: MT7922 Bluetooth doesn't enable Status in linux-lowlatency-hwe-5.19 package in Ubuntu: New Bug description: martin@studio-as6:~$ sudo dmesg | egrep -i 'blue|firm' [0.119642] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.278739] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [2.462372] [drm] Loading DMUB firmware via PSP: version=0x0422 [2.463264] [drm] Found VCN firmware Version ENC: 1.21 DEC: 2 VEP: 0 Revision: 10 [2.463267] amdgpu :e6:00.0: amdgpu: Will use PSP to load VCN firmware [4.073508] Bluetooth: Core ver 2.22 [4.074051] NET: Registered PF_BLUETOOTH protocol family [4.074053] Bluetooth: HCI device and connection manager initialized [4.074057] Bluetooth: HCI socket layer initialized [4.074059] Bluetooth: L2CAP socket layer initialized [4.074064] Bluetooth: SCO socket layer initialized [4.257367] mt7921e :03:00.0: WM Firmware Version: 00, Build Time: 20220908203253 [6.223611] Bluetooth: hci0: Opcode 0x c03 failed: -110 [7.328550] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [7.328553] Bluetooth: BNEP filters: protocol multicast [7.328556] Bluetooth: BNEP socket layer initialized Note the line: [6.223611] Bluetooth: hci0: Opcode 0x c03 failed: -110 UI carries on, but the error is fatal and no devices can be found. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.19.0-1017.18~22.04.1-lowlatency 5.19.17 Uname: Linux 5.19.0-1017-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Jun 25 14:25:34 2023 InstallationDate: Installed on 2023-06-25 (0 days ago) InstallationMedia: Ubuntu-Studio 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230221) InterestingModules: bnep bluetooth MachineType: ASUSTeK COMPUTER INC. MINIPC PN53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-1017-lowlatency root=UUID=933611e5-18b7-4290-98f3-d60eb962bdad ro threadirqs quiet splash vt.handoff=1 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2023 dmi.bios.release: 2.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 20300 dmi.board.asset.tag: Default string dmi.board.name: PN53 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr20300:bd02/02/2023:br2.3:svnASUSTeKCOMPUTERINC.:pnMINIPCPN53:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPN53:rvrRev1.xx:cvnDefaultstring:ct35:cvrDefaultstring:skuSKU: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN53 dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: rfkill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency-hwe-5.19/+bug/2024985/+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 2024968] Re: [Dell Latitude 7390] Screen remains dark after wake-up
** Summary changed: - Issue from wake up + [Dell Latitude 7390] Screen remains dark after wake-up ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2024968 Title: [Dell Latitude 7390] Screen remains dark after wake-up Status in linux package in Ubuntu: New Bug description: Screen remain dark after wake-up. Mostly it happens when Firefox browser remains open. Only remedy is hard restart ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Sat Jun 24 14:53:18 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:081b] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:58ca Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7390 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-23-generic root=UUID=83d832f6-75ac-446a-b253-7d234af09979 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2023 dmi.bios.release: 1.32 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.32.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.32.0:bd04/10/2023:br1.32:svnDellInc.:pnLatitude7390:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku081B: dmi.product.family: Latitude dmi.product.name: Latitude 7390 dmi.product.sku: 081B dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu3 version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 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/linux/+bug/2024968/+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 2024889] Re: Laptop screen show an one pixel row corruption
Please try adding this kernel parameter: i915.enable_psr=0 Please also use the 'Additional Drivers' app to install an NVIDIA driver. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/2024889 Title: Laptop screen show an one pixel row corruption Status in linux package in Ubuntu: Incomplete Bug description: I am using Asus TUF F15 RTX4060 gaming laptop with external LG 4k monitor. All runs very smooth until today appears only on laptop screen one pixel row corruption. What is weird on this row? It show up at any resolution and copy X-position of window Color by movement any windows on screen. I think is from Xorg. because I restarted many times and replaced nvidia open-source to proprietary drivers. Still appears this row. I have dual boot with Windows 11 and here it not happen any screen issues. So must be in Ubuntu OS. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-73.80-generic 5.15.98 Uname: Linux 5.15.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Prístup odmietnutý: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Fri Jun 23 11:33:43 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:277d] NVIDIA Corporation Device [10de:28e0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:277d] InstallationDate: Installed on 2023-06-13 (9 days ago) InstallationMedia: Xubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F15 FX507ZV4_FX507ZV4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-73-generic root=UUID=7a64d27e-63d8-449f-b29f-df2b76bfaab2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2023 dmi.bios.release: 5.26 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FX507ZV4.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX507ZV4 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.67 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFX507ZV4.315:bd05/11/2023:br5.26:efr0.67:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX507ZV4_FX507ZV4:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX507ZV4:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ASUS TUF Gaming F15 dmi.product.name: ASUS TUF Gaming F15 FX507ZV4_FX507ZV4 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER 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.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/linux/+bug/2024889/+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
