[Touch-packages] [Bug 1030022] Re: Port from legacy Xlib to modern XCB
This bug has been open for 10 years now and I don't think it's reasonable to ask that legacy apps be redesigned, if those apps even have developers anymore. They may well use "legacy" Xlib but also XCB is "legacy" now too. Please focus on Wayland for new projects. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1030022 Title: Port from legacy Xlib to modern XCB Status in 9wm package in Ubuntu: New Status in aewm package in Ubuntu: New Status in aewm++ package in Ubuntu: New Status in afterstep package in Ubuntu: New Status in amiwm package in Ubuntu: Invalid Status in blackbox package in Ubuntu: New Status in cairo package in Ubuntu: New Status in compiz package in Ubuntu: Invalid Status in ctwm package in Ubuntu: New Status in dwm package in Ubuntu: Opinion Status in enlightenment package in Ubuntu: New Status in fvwm package in Ubuntu: New Status in fvwm1 package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Status in icewm package in Ubuntu: New Status in jwm package in Ubuntu: Invalid Status in larswm package in Ubuntu: New Status in lwm package in Ubuntu: New Status in matchbox-window-manager package in Ubuntu: New Status in metacity package in Ubuntu: Invalid Status in miwm package in Ubuntu: New Status in muffin package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in pekwm package in Ubuntu: New Status in ratpoison package in Ubuntu: New Status in sapphire package in Ubuntu: New Status in sawfish package in Ubuntu: New Status in spectrwm package in Ubuntu: Fix Released Status in tinywm package in Ubuntu: New Status in tritium package in Ubuntu: New Status in twm package in Ubuntu: New Status in vtwm package in Ubuntu: New Status in w9wm package in Ubuntu: New Status in windowlab package in Ubuntu: New Status in wm2 package in Ubuntu: New Status in wmaker package in Ubuntu: Opinion Status in xmonad package in Ubuntu: New Bug description: Port/rewrite the window manager to use the modern XCB (X C Binding) library instead of the old legacy Xlib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/9wm/+bug/1030022/+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 1984327] Re: Component mismatch: new lerc support requires universe package
Andreas, can you revert this change now? Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1984327 Title: Component mismatch: new lerc support requires universe package Status in tiff package in Ubuntu: Fix Released Bug description: tiff is in sync with debian, and version tiff 4.4.0-1[1] enabled lerc support. Unfortunately lerc[2] is in ubuntu universe, and tiff is in main, so we either MIR lerc, or disable it in tiff. For now, let's disable lerc support. 1. https://launchpad.net/ubuntu/+source/tiff/4.4.0-1 2. https://launchpad.net/ubuntu/+source/lerc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1984327/+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 1981103] Re: System with DNS server in /etc/network/interfaces has bogus systemd-resolved config after upgrade to 22.04
This is affecting me too. It's only happening on systems that started
life as Ubuntu 18.04 and earlier - any server that was installed as
20.04 is upgrading to 22.04 without problem. Once I make the same change
as Uwe, systemd-resolved is getting configured correctly.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1981103
Title:
System with DNS server in /etc/network/interfaces has bogus systemd-
resolved config after upgrade to 22.04
Status in ifupdown package in Ubuntu:
Confirmed
Bug description:
Description:Ubuntu 22.04 LTS
Release:22.04
ifupdown:
Installed: 0.8.36+nmu1ubuntu3
Candidate: 0.8.36+nmu1ubuntu3
Version table:
*** 0.8.36+nmu1ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
100 /var/lib/dpkg/status
After upgrading a server with classic ifupdown configuration after
reboot the machine had no valid dns servers anymore.
The problem is that the state file created by ifupdown using
/etc/network/if-up.d/resolved looks like this:
root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
"DNS"="134.102.20.20 134.102.200.14"
"DOMAINS"="marum.de"
The script later sources this file and causes the following errors,
easy to see when you execute this:
root@pangaea-pm:~# ifdown ens13; ifup ens13
/etc/network/if-down.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 71: DNS: not found
/etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13:
DNS=134.102.20.20 134.102.200.14: not found
/etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13:
DOMAINS=marum.de: not found
Failed to parse DNS server address: DNS
Failed to set DNS configuration: Invalid argument
This happened to me on three different servers, so this is a serious
bug and should be fixed before 22.04 upgrades are allowed for
everybody. Most servers provided by data centers like Hetzner
(Germany) are configure like that. After a do-release-upgrade you have
no working DNS anymore, unless you disable systemd-resolved. I don't
want to use netplan, so changing to this is no option.
The fix is easy - remove the quotes in the script on the left side
"$DNS" => $DNS; same for DOMAINS:
if [ -n "$NEW_DNS" ]; then
cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DNS="$NEW_DNS"
EOF
if [ -n "$NEW_DOMAINS" ]; then
cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DOMAINS="$NEW_DOMAINS"
EOF
fi
fi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103/+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 1983794] Re: Evolution not deleting autosave files
I notified Milan Crha (@mcrha) who's a GNOME maintainer of Evolution on
the GNOME branch of this bug,
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972#note_1529229.
He's written new features for Evolution, which have been pushed into the
GNOME upstream pacakge, so he knows the code. I know I initiated this
report, but you and @mcrha are far more capable of getting to the bottom
of this bug than am I. I would hope that he would be reading this and
possibly work with you on stomping it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in evolution package in Ubuntu:
In Progress
Status in gtk+3.0 package in Ubuntu:
In Progress
Bug description:
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1983794/+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 1981103] Re: System with DNS server in /etc/network/interfaces has bogus systemd-resolved config after upgrade to 22.04
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ifupdown (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1981103
Title:
System with DNS server in /etc/network/interfaces has bogus systemd-
resolved config after upgrade to 22.04
Status in ifupdown package in Ubuntu:
Confirmed
Bug description:
Description:Ubuntu 22.04 LTS
Release:22.04
ifupdown:
Installed: 0.8.36+nmu1ubuntu3
Candidate: 0.8.36+nmu1ubuntu3
Version table:
*** 0.8.36+nmu1ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
100 /var/lib/dpkg/status
After upgrading a server with classic ifupdown configuration after
reboot the machine had no valid dns servers anymore.
The problem is that the state file created by ifupdown using
/etc/network/if-up.d/resolved looks like this:
root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
"DNS"="134.102.20.20 134.102.200.14"
"DOMAINS"="marum.de"
The script later sources this file and causes the following errors,
easy to see when you execute this:
root@pangaea-pm:~# ifdown ens13; ifup ens13
/etc/network/if-down.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 71: DNS: not found
/etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13:
DNS=134.102.20.20 134.102.200.14: not found
/etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13:
DOMAINS=marum.de: not found
Failed to parse DNS server address: DNS
Failed to set DNS configuration: Invalid argument
This happened to me on three different servers, so this is a serious
bug and should be fixed before 22.04 upgrades are allowed for
everybody. Most servers provided by data centers like Hetzner
(Germany) are configure like that. After a do-release-upgrade you have
no working DNS anymore, unless you disable systemd-resolved. I don't
want to use netplan, so changing to this is no option.
The fix is easy - remove the quotes in the script on the left side
"$DNS" => $DNS; same for DOMAINS:
if [ -n "$NEW_DNS" ]; then
cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DNS="$NEW_DNS"
EOF
if [ -n "$NEW_DOMAINS" ]; then
cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DOMAINS="$NEW_DOMAINS"
EOF
fi
fi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103/+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 1983794] Re: Evolution not deleting autosave files
Thank you for the bug report!
I rebuilt and installed GTK3 with Ubuntu specific patches disabled, but
the problem still occurs in Xorg. :/
In two occasions I got
(evolution:3367): evolution-mail-composer-CRITICAL **: 20:45:02.635:
e_msg_composer_is_soft_busy: assertion 'E_IS_MSG_COMPOSER (composer)' failed
(evolution:3367): module-composer-autosave-CRITICAL **: 20:45:02.635:
e_composer_save_snapshot: assertion 'E_IS_MSG_COMPOSER (composer)' failed
in stderr. We could hardly wish for a better trail to follow.
With fatal-criticals one can backtrace that, though I still don't know
what triggers it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in evolution package in Ubuntu:
In Progress
Status in gtk+3.0 package in Ubuntu:
In Progress
Bug description:
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1983794/+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
Re: [Touch-packages] [Bug 1986860] Re: [MIR] krb5 (bin:krb5-user)
I asked security and they said they would prefer a MIR in this case On Wed, Aug 17, 2022, 18:25 Steve Langasek <1986...@bugs.launchpad.net> wrote: > I don't believe MIR is required for binary packages unless they have > been excluded from main for a reason as part of a prior MIR. You should > only need to seed it. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1986860 > > Title: > [MIR] krb5 (bin:krb5-user) > > Status in krb5 package in Ubuntu: > New > > Bug description: > Placeholder bug to MIR bin:krb5-user (src:krb5 is in main already). > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1986860/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=krb5; component=main; > status=New; importance=Undecided; assignee=andr...@canonical.com; > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: ahasenack vorlon > Launchpad-Bug-Reporter: Andreas Hasenack (ahasenack) > Launchpad-Bug-Modifier: Steve Langasek (vorlon) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: ahasenack > > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1986860 Title: [MIR] krb5 (bin:krb5-user) Status in krb5 package in Ubuntu: New Bug description: Placeholder bug to MIR bin:krb5-user (src:krb5 is in main already). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1986860/+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 1986860] Re: [MIR] krb5 (bin:krb5-user)
I don't believe MIR is required for binary packages unless they have been excluded from main for a reason as part of a prior MIR. You should only need to seed it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1986860 Title: [MIR] krb5 (bin:krb5-user) Status in krb5 package in Ubuntu: New Bug description: Placeholder bug to MIR bin:krb5-user (src:krb5 is in main already). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1986860/+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 1986861] [NEW] pulseaudio stops accepting connections
Public bug reported: After a while, pulseaudio clients get connections refused and are unable to play audio / receive microphone input. journalctl shows lots of messages like: Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] native-common.c: Expected 1 memfd fd to be received over pipe; got 0 Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] native-common.c: Did we reach our open file descriptors limit? Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] protocol-native.c: protocol error, kicking client as well as Aug 17 13:03:52 taplop pulseaudio[2244465]: [pulseaudio] protocol- native.c: Warning! Too many connections (64), dropping incoming connection. killing the pulseaudio daemon makes audio work for a little while until the same thing repeats. not sure what's triggering it though, or how to best find out. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 Uname: Linux 5.17.0-051700drmtip20220329-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2265029 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Aug 17 14:13:56 2022 InstallationDate: Installed on 2019-08-17 (1096 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2022-03-18 (152 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1986861 Title: pulseaudio stops accepting connections Status in pulseaudio package in Ubuntu: New Bug description: After a while, pulseaudio clients get connections refused and are unable to play audio / receive microphone input. journalctl shows lots of messages like: Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] native-common.c: Expected 1 memfd fd to be received over pipe; got 0 Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] native-common.c: Did we reach our open file descriptors limit? Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] protocol-native.c: protocol error, kicking client as well as Aug 17 13:03:52 taplop pulseaudio[2244465]: [pulseaudio] protocol- native.c: Warning! Too many connections (64), dropping incoming connection. killing the pulseaudio daemon makes audio work for a little while until the same thing repeats. not sure what's triggering it though, or how to best find out. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 Uname: Linux 5.17.0-051700drmtip20220329-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2265029 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Aug 17 14:13:56 2022 InstallationDate: Installed on 2019-08-17 (1096 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2022-03-18 (152 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1986861/+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 1986860] [NEW] [MIR] krb5 (bin:krb5-user)
Public bug reported: Placeholder bug to MIR bin:krb5-user (src:krb5 is in main already). ** Affects: krb5 (Ubuntu) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1986860 Title: [MIR] krb5 (bin:krb5-user) Status in krb5 package in Ubuntu: New Bug description: Placeholder bug to MIR bin:krb5-user (src:krb5 is in main already). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1986860/+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 1934559] Re: Typo in capital of Ukraine
There seems to be a first step into that direction in version 2022b (still to be packaged for Ubuntu) https://data.iana.org/time- zones/tzdb/NEWS -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1934559 Title: Typo in capital of Ukraine Status in tzdata package in Ubuntu: New Bug description: During installation on a map and in timezone settings there's "Kiev" city, but it's not correct. Should be Kyiv - https://en.wikipedia.org/wiki/Kyiv. Ubuntu 21.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1934559/+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 1969671] Re: Misspelled Ukrainian cities in tzdata
There seems to be a first step into that direction in version 2022b (still to be packaged for Ubuntu) https://data.iana.org/time- zones/tzdb/NEWS -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1969671 Title: Misspelled Ukrainian cities in tzdata Status in tzdata package in Ubuntu: New Bug description: When user is prompted to choose a city in the region 'Europe' they have a choice of 4 cities in Ukraine: 23. Kiev -> should be Kyiv 46. Simferopol - > OK 54. Uzhgorod -> should be Uzhhorod 62. Zaporozhye -> should be Zaporizhzhia The 'should be' variant is the only correct transliteration from Ukrainian into English. Possible useful pieces of ubuntu-bug report (run in a headless ubuntu/latest docker image): DistroRelease: Ubuntu 20.04 Package: tzdata 2022a-0ubuntu0.20.04 Tags: focal PackageArchitecture: all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1969671/+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 1980146] Re: dnsmasq often using 100% of CPU if the upstream nameserver is unreachable
** Summary changed:
- dnsmasq often using 100% of CPU
+ dnsmasq often using 100% of CPU if the upstream nameserver is unreachable
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1980146
Title:
dnsmasq often using 100% of CPU if the upstream nameserver is
unreachable
Status in dnsmasq package in Ubuntu:
Triaged
Status in dnsmasq source package in Focal:
Triaged
Status in dnsmasq source package in Jammy:
Triaged
Status in dnsmasq source package in Kinetic:
Triaged
Bug description:
Release: 22.04
Codename: jammy
Kernel: Linux 5.15.0-40-generic x86_64
⏵ apt-cache policy dnsmasq
Installed: 2.86-1.1ubuntu0.1
dnsmasq is caught in a loop after every dns request, resulting in 100%
CPU usage for several minutes each time. This leads to a hot and
lethargic computer. During this time thousands of the following
messages (see below) are printed from strace.
The loop tends to obsess on denied connections, but there are so many
I'm not 100% sure.
systemd-resolved is _not_ running, some bugs refer to that.
⏵ head /etc/dnsmasq.d/foo.conf
address=/#/127.0.0.2
port=53
resolv-file=/var/run/NetworkManager/resolv.conf
⏵ sudo strace -p 3519 (dnsmasq)
poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5,
events=POLLIN}, {fd=6, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8,
events=POLLIN}, {fd=9, events=POLLIN}, {fd=13, events=POLLIN}, {fd=14,
events=POLLIN}], 9, -1) = 1 ([{fd=4, revents=POLLIN}])
recvmsg(4, {msg_name={sa_family=AF_INET, sin_port=htons(60224),
sin_addr=inet_addr("127.0.0.1")}, msg_namelen=28 => 16,
msg_iov=[{iov_base="\302\221\1\0\0\1\0\0\0\0\0\0\17classify-
client\10ser"..., iov_len=4096}], msg_iovlen=1,
msg_control=[{cmsg_len=28, cmsg_level=SOL_IP, cmsg_type=IP_PKTINFO,
cmsg_data={ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"),
ipi_addr=inet_addr("127.0.0.53")}}], msg_controllen=32, msg_flags=0},
0) = 54
ioctl(4, SIOCGIFNAME, {ifr_ifindex=1, ifr_name="lo"}) = 0
sendto(14, "\302\221\1\0\0\1\0\0\0\0\0\0\17classify-client\10ser"...,
54, 0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("127.0.0.53")}, 16) = 54
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1980146/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
This is also affecting the MSI MEG Z690I Unify motherboard; can not boot
any live disk images of Ubuntu 22.04
--
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/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Confirmed
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c” but I use the
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
Thus it should not impact them.
* There is a “#if defined(__x86_64__)” which intent to limit the >
32bits code in i386 system and also
```
#if defined (__code_model_large__)
-#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
+#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
#else
#define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
#endif
```
If everything works as expected, then i386 should working good.
If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
4GB memory region and never be able to access.
[Other Info]
* Upstream grub2 bug #61058
https://savannah.gnu.org/bugs/index.php?61058
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320
* Test grubx64.efi:
https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320
* Test source code: https://github.com/os369510/grub2/tree/lp1842320
* If you built the package, then test grubx64.efi is under
“obj/monolithic/grub-efi-amd64/grubx64.efi”, in my case:
[Touch-packages] [Bug 1983794] Re: Evolution not deleting autosave files
** Changed in: evolution (Ubuntu)
Status: Confirmed => In Progress
** Changed in: gtk+3.0 (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in evolution package in Ubuntu:
In Progress
Status in gtk+3.0 package in Ubuntu:
In Progress
Bug description:
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1983794/+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 1986841] Re: canon pixma g2010 printer connected through usb, added in printer settings but unable to print through print command
** Package changed: ubuntu => cups (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1986841 Title: canon pixma g2010 printer connected through usb, added in printer settings but unable to print through print command Status in cups package in Ubuntu: New Bug description: canon pixma g2010 printer connected through usb, added in printer settings when i searched for it but when i give print command to print a page it sends command and still no print out and also there is no pending jobs showing, and when i tried to print test page it is also not printing. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckMismatches: ./pool/main/l/linux-oem-5.17/linux-modules-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Wed Aug 17 21:37:30 2022 InstallationDate: Installed on 2022-07-11 (36 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lpstat: device for CUPS-BRF-Printer: cups-brf:/ device for G2010: usb://Canon/G2010%20series?serial=20B026=1 MachineType: SAMSUNG ELECTRONICS CO., LTD. RV411/RV511/E3511/S3511/RV711/E3411 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/G2010.ppd', '/etc/cups/ppd/CUPS-BRF-Printer.ppd'] failed with exit code 2: grep: /etc/cups/ppd/G2010.ppd: Permission denied grep: /etc/cups/ppd/CUPS-BRF-Printer.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2011 dmi.bios.release: 4.0 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04PA.M006.20110615.XW dmi.board.asset.tag: Tag 12345 dmi.board.name: RV411/RV511/E3511/S3511/RV711/E3411 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04PA.M006.20110615.XW:bd06/15/2011:br4.0:svnSAMSUNGELECTRONICSCO.,LTD.:pnRV411/RV511/E3511/S3511/RV711/E3411:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRV411/RV511/E3511/S3511/RV711/E3411:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:sku: dmi.product.name: RV411/RV511/E3511/S3511/RV711/E3411 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1986841/+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 1986841] [NEW] canon pixma g2010 printer connected through usb, added in printer settings but unable to print through print command
You have been subscribed to a public bug: canon pixma g2010 printer connected through usb, added in printer settings when i searched for it but when i give print command to print a page it sends command and still no print out and also there is no pending jobs showing, and when i tried to print test page it is also not printing. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckMismatches: ./pool/main/l/linux-oem-5.17/linux-modules-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Wed Aug 17 21:37:30 2022 InstallationDate: Installed on 2022-07-11 (36 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lpstat: device for CUPS-BRF-Printer: cups-brf:/ device for G2010: usb://Canon/G2010%20series?serial=20B026=1 MachineType: SAMSUNG ELECTRONICS CO., LTD. RV411/RV511/E3511/S3511/RV711/E3411 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/G2010.ppd', '/etc/cups/ppd/CUPS-BRF-Printer.ppd'] failed with exit code 2: grep: /etc/cups/ppd/G2010.ppd: Permission denied grep: /etc/cups/ppd/CUPS-BRF-Printer.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2011 dmi.bios.release: 4.0 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04PA.M006.20110615.XW dmi.board.asset.tag: Tag 12345 dmi.board.name: RV411/RV511/E3511/S3511/RV711/E3411 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04PA.M006.20110615.XW:bd06/15/2011:br4.0:svnSAMSUNGELECTRONICSCO.,LTD.:pnRV411/RV511/E3511/S3511/RV711/E3411:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRV411/RV511/E3511/S3511/RV711/E3411:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:sku: dmi.product.name: RV411/RV511/E3511/S3511/RV711/E3411 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- canon pixma g2010 printer connected through usb, added in printer settings but unable to print through print command https://bugs.launchpad.net/bugs/1986841 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986521] Re: ssh client spins if output fd closed
Thanks for taking the time to report the bug and make Ubuntu better.
I can reproduce the bug using your testcase, but that requires a VM with
a graphical environment installed. Another way to reproduce the bug is
(from the upstream bug report):
$ lxc launch ubuntu-daily:jammy ssh-cpu
$ lxc shell ssh-cpu
# ssh HOST 2> >({exec 1>&2})
You can shell into the container from another terminal and use "htop" to
verify that ssh is using 100% of one of the CPU cores.
This seems to have been fixed upstream by the following commit:
https://github.com/openssh/openssh-
portable/commit/d6556de1db0822c76ba2745cf5c097d9472adf7c
I confirmed that this only happens on Jammy. Focal and Kinetic are not
affected.
** Also affects: openssh (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: openssh (Ubuntu)
Status: New => Fix Released
** Changed in: openssh (Ubuntu Jammy)
Status: New => Triaged
** Changed in: openssh (Ubuntu Jammy)
Importance: Undecided => Medium
** Bug watch added: OpenSSH Portable Bugzilla #3405
https://bugzilla.mindrot.org/show_bug.cgi?id=3405
** Also affects: openssh via
https://bugzilla.mindrot.org/show_bug.cgi?id=3405
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1986521
Title:
ssh client spins if output fd closed
Status in portable OpenSSH:
Unknown
Status in openssh package in Ubuntu:
Fix Released
Status in openssh source package in Jammy:
Triaged
Bug description:
The OpenSSH package 8.9p1 as shipped with U22.04 (8.9p1-3) suffers from the
bug described at
https://bugzilla.mindrot.org/show_bug.cgi?id=3411 and
https://bugzilla.mindrot.org/show_bug.cgi?id=3405
A command such as "xterm -e 'ssh -f remote.host sleep 60'" will pop up
an xterm, ask for whatever authentication is needed, close the xterm,
and leave the ssh client spinning consuming CPU time for 60 seconds
before it exits. It should leave the ssh client idle for 60 seconds.
Many uses of ssh to launch graphical applications will be caught by
this bug.
This is fixed in OpenSSH 9.0p1 as the first bugfix listed in its
release notes at https://www.openssh.com/txt/release-9.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1986521/+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 1952107] Re: Google Contacts API Deprecated
I added a Bionic task. This is blocked because we haven't been able to find a working patch to fix this issue. You can see one attempt in the comment history of this bug. I added some notes from my attempt at https://salsa.debian.org/gnome-team/evolution/-/merge_requests/3 ** Also affects: evolution (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: evolution-data-server (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: evolution-data-server (Ubuntu Bionic) Status: New => Triaged ** Changed in: evolution (Ubuntu Bionic) Status: New => Triaged ** Changed in: evolution (Ubuntu Focal) Assignee: Jeremy Bicha (jbicha) => (unassigned) ** Changed in: evolution-data-server (Ubuntu Focal) Assignee: Jeremy Bicha (jbicha) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Fix Released Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Bionic: Triaged Status in evolution-data-server source package in Bionic: Triaged Status in evolution source package in Focal: Triaged Status in evolution-data-server source package in Focal: Triaged Status in evolution source package in Impish: Fix Released Status in evolution-data-server source package in Impish: Fix Released Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+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 1980408] Autopkgtest regression report (glib2.0/2.72.3-0ubuntu1)
All autopkgtests for the newly accepted glib2.0 (2.72.3-0ubuntu1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: systemd/249.11-0ubuntu3.4 (armhf) flatpak/1.12.7-1 (arm64) libaperture-0/0.1.0+git20200908-3 (armhf) automake-1.16/1:1.16.5-1.3 (arm64) booth/1.0-237-gdd88847-4ubuntu2.2 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#glib2.0 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1980408 Title: Update glib to 2.72.3 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 2.72 series https://gitlab.gnome.org/GNOME/glib/-/blob/2.72.3/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopgktest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1980408/+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 1980146] Re: dnsmasq often using 100% of CPU
Thanks for the extra details, I was able to reproduce the problem here.
Here are the steps:
$ lxc launch ubuntu-daily:jammy dnsmasq-cpu-bug
$ lxc shell dnsmasq-cpu-bug
# apt update
# apt install -y dnsmasq
# systemctl disable --now systemd-resolved.service
# systemctl start dnsmasq.service
# dig gnu.org
In another terminal, you can shell into the container and do an "htop"
to check that dnsmasq will be using 100% of one CPU core.
I was able to reproduce this all the way back to Focal, but Bionic isn't
impacted by this bug.
I believe it's worth trying to report it upstream and seeing if this
rings any bells. I'm going to include this bug in our backlog; right
now everybody from the Ubuntu Server team is busy with the upcoming
Kinetic release.
mixmastamyk, if you feel like reporting this upstream please post the
link to the email thread here so that we can keep an eye on it.
Thanks.
** Also affects: dnsmasq (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: dnsmasq (Ubuntu Kinetic)
Importance: Undecided
Status: Incomplete
** Also affects: dnsmasq (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: dnsmasq (Ubuntu Focal)
Status: New => Triaged
** Changed in: dnsmasq (Ubuntu Jammy)
Status: New => Triaged
** Changed in: dnsmasq (Ubuntu Kinetic)
Status: Incomplete => Triaged
** Changed in: dnsmasq (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: dnsmasq (Ubuntu Kinetic)
Importance: Undecided => Medium
** Changed in: dnsmasq (Ubuntu Jammy)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1980146
Title:
dnsmasq often using 100% of CPU
Status in dnsmasq package in Ubuntu:
Triaged
Status in dnsmasq source package in Focal:
Triaged
Status in dnsmasq source package in Jammy:
Triaged
Status in dnsmasq source package in Kinetic:
Triaged
Bug description:
Release: 22.04
Codename: jammy
Kernel: Linux 5.15.0-40-generic x86_64
⏵ apt-cache policy dnsmasq
Installed: 2.86-1.1ubuntu0.1
dnsmasq is caught in a loop after every dns request, resulting in 100%
CPU usage for several minutes each time. This leads to a hot and
lethargic computer. During this time thousands of the following
messages (see below) are printed from strace.
The loop tends to obsess on denied connections, but there are so many
I'm not 100% sure.
systemd-resolved is _not_ running, some bugs refer to that.
⏵ head /etc/dnsmasq.d/foo.conf
address=/#/127.0.0.2
port=53
resolv-file=/var/run/NetworkManager/resolv.conf
⏵ sudo strace -p 3519 (dnsmasq)
poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5,
events=POLLIN}, {fd=6, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8,
events=POLLIN}, {fd=9, events=POLLIN}, {fd=13, events=POLLIN}, {fd=14,
events=POLLIN}], 9, -1) = 1 ([{fd=4, revents=POLLIN}])
recvmsg(4, {msg_name={sa_family=AF_INET, sin_port=htons(60224),
sin_addr=inet_addr("127.0.0.1")}, msg_namelen=28 => 16,
msg_iov=[{iov_base="\302\221\1\0\0\1\0\0\0\0\0\0\17classify-
client\10ser"..., iov_len=4096}], msg_iovlen=1,
msg_control=[{cmsg_len=28, cmsg_level=SOL_IP, cmsg_type=IP_PKTINFO,
cmsg_data={ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"),
ipi_addr=inet_addr("127.0.0.53")}}], msg_controllen=32, msg_flags=0},
0) = 54
ioctl(4, SIOCGIFNAME, {ifr_ifindex=1, ifr_name="lo"}) = 0
sendto(14, "\302\221\1\0\0\1\0\0\0\0\0\0\17classify-client\10ser"...,
54, 0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("127.0.0.53")}, 16) = 54
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1980146/+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 1952107] Re: Google Contacts API Deprecated
Brian, Sebastien, do either of you have the ability to mark this as a bug in Bionic as well for tracking purposes? (I don't seem to have permission to do that). It would be excellent for your patches to be backported to Bionic, regardless of _who_ submits such a patch. Thank you very much in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Fix Released Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Focal: Triaged Status in evolution-data-server source package in Focal: Triaged Status in evolution source package in Impish: Fix Released Status in evolution-data-server source package in Impish: Fix Released Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+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 1959469] Re: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)
libnettle8 3.8.1-2 finally landed in kinetic, hence updating the status to Fix Released and closing this ticket. ** Changed in: nettle (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nettle in Ubuntu. https://bugs.launchpad.net/bugs/1959469 Title: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto) Status in Ubuntu on IBM z Systems: Fix Released Status in nettle package in Ubuntu: Fix Released Status in nettle package in Debian: New Bug description: Upgrade nettle to latest version >= 3.7.4 (crypto) Description Upgrade nettle to latest version >= 3.7.4 to provide CPACF Support for Crypto Libraries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959469/+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 1979879] Re: Apparmor profile in 22.04 jammy - fails to start when printing enabled
Waiting for a review of MP ** Changed in: apparmor (Ubuntu Jammy) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1979879 Title: Apparmor profile in 22.04 jammy - fails to start when printing enabled Status in apparmor package in Ubuntu: Invalid Status in samba package in Ubuntu: Fix Released Status in apparmor source package in Jammy: In Progress Status in samba source package in Jammy: Triaged Bug description: See bug here: https://bugzilla.opensuse.org/show_bug.cgi?id=1191532 Fix was backported, but the path to samba-bgqd is wrong on 22.04. Currently apparmor profile has it like this: /usr/lib*/samba/samba-bgqd When in fact 22.04 has it on /usr/lib/x86_64-linux-gnu/samba/samba- bgqd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1979879/+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 1971523] Re: Static build does not work for libmnl (-lmnl)
** Changed in: libmnl (Ubuntu Jammy)
Assignee: Michał Małoszewski (michal-maloszewski99) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libmnl in Ubuntu.
https://bugs.launchpad.net/bugs/1971523
Title:
Static build does not work for libmnl (-lmnl)
Status in libmnl package in Ubuntu:
Fix Released
Status in libmnl source package in Jammy:
Won't Fix
Status in libmnl package in Debian:
Fix Committed
Bug description:
[Test Case]
$ cat > /tmp/hello.c <
int main() {
printf("Hello world! (and LP: #1971523)\n");
}
EOF
$ gcc -o /tmp/hello /tmp/hello.c -lmnl
(dynamic libs work)
$ gcc -static -o /tmp/hello /tmp/hello.c -lmnl
/usr/bin/ld: cannot find -lmnl: No such file or directory
[Original Report]
My program uses both -lmnl and -lnetfilter_queue and in Ubuntu 20.04 the
-lnetfilter_queue did not work and -lmnl worked for static builds. In Ubuntu
22.04 the problem is reversed, -lnetfilter_queue works but -lmnl doesn't for
static builds. This is very awkward during the transition 20.04->22.04 when
both should be supported.
I compensated in Ubuntu 20.04 by building netfilter_queue locally;
https://github.com/Nordix/nfqueue-loadbalancer#build
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libmnl0:amd64 1.0.4-3build2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Wed May 4 07:33:26 2022
InstallationDate: Installed on 2018-09-07 (1334 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: libmnl
UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmnl/+bug/1971523/+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 1897932] Re: systemd-repart not packaged
> In addition to that though, I notice that mkosi in Jammy does refer to /usr/bin/systemd-repart. Will the Jammy packaged mkosi therefore change behaviour if you start shipping it in Ubuntu? Those references are for the dracut configuration, i.e. to get those files from the target image to the target image's initrd. What is available on the host is independent of that. -- 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/1897932 Title: systemd-repart not packaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Confirmed Status in systemd package in Debian: Fix Released Bug description: [Impact] systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? The bug reporter would like to use it in their new raspberry pi images where they don't have cloud-init installed. The reporter is already using systemd-growfs, but they are missing the nice partition resizing part (so are using cloud-initramfs-growroot). Furthermore, in the mkosi image builder (https://github.com/systemd/mkosi), the systemd/mkosi developers would like to start using systemd-repart for partitioning. Unfortunately, they're currently blocked on this because 22.04 doesn't ship systemd- repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy and will do so until the next Ubuntu LTS is released. If we have to wait for the next LTS to be released, we'll have to wait for a considerable amount of time before we're able to start using systemd- repart. Being able to use systemd-repart will allow the systemd/mkosi developers to take advantage of its improved interface compared to sfdisk, as well as its builtin protections against race conditions surrounding the use of loop devices. The systemd/mkosi developers expect to be able to get rid of some nasty loop device failure in mkosi by using systemd-repart. [Test Plan] This is a missing extra executable. Once enabled it has self-tests in the build-time unit tests, and also a regression test in the autopkgtest 'upstream' suite. [Where problems could occur] Shipping systemd-repart will come with no additional risk. While there is a systemd-repart.service that runs on boot, it's configured to not do anything if no config files are shipped with the system or provided by the user. As such, the service, if enabled, will effectively be a noop. Aside from the service, there's the CLI tool systemd-repart and the accompanying man pages that will be shipped as part of the systemd package. Given that there's no risk involved with enabling systemd-repart, and given the useful features it provides, the systemd/mkosi developers would like to request that systemd-repart be enabled in Ubuntu and backported to Jammy so that they can start adopting it in mkosi. Runtime behavior of existing components is not affected by the build config change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897932/+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 1897932] Re: systemd-repart not packaged
There's further discussion in the ubuntu-devel ML thread. In addition to that though, I notice that mkosi in Jammy does refer to /usr/bin/systemd-repart. Will the Jammy packaged mkosi therefore change behaviour if you start shipping it in Ubuntu? -- 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/1897932 Title: systemd-repart not packaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Confirmed Status in systemd package in Debian: Fix Released Bug description: [Impact] systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? The bug reporter would like to use it in their new raspberry pi images where they don't have cloud-init installed. The reporter is already using systemd-growfs, but they are missing the nice partition resizing part (so are using cloud-initramfs-growroot). Furthermore, in the mkosi image builder (https://github.com/systemd/mkosi), the systemd/mkosi developers would like to start using systemd-repart for partitioning. Unfortunately, they're currently blocked on this because 22.04 doesn't ship systemd- repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy and will do so until the next Ubuntu LTS is released. If we have to wait for the next LTS to be released, we'll have to wait for a considerable amount of time before we're able to start using systemd- repart. Being able to use systemd-repart will allow the systemd/mkosi developers to take advantage of its improved interface compared to sfdisk, as well as its builtin protections against race conditions surrounding the use of loop devices. The systemd/mkosi developers expect to be able to get rid of some nasty loop device failure in mkosi by using systemd-repart. [Test Plan] This is a missing extra executable. Once enabled it has self-tests in the build-time unit tests, and also a regression test in the autopkgtest 'upstream' suite. [Where problems could occur] Shipping systemd-repart will come with no additional risk. While there is a systemd-repart.service that runs on boot, it's configured to not do anything if no config files are shipped with the system or provided by the user. As such, the service, if enabled, will effectively be a noop. Aside from the service, there's the CLI tool systemd-repart and the accompanying man pages that will be shipped as part of the systemd package. Given that there's no risk involved with enabling systemd-repart, and given the useful features it provides, the systemd/mkosi developers would like to request that systemd-repart be enabled in Ubuntu and backported to Jammy so that they can start adopting it in mkosi. Runtime behavior of existing components is not affected by the build config change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897932/+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 1971523] Re: Static build does not work for libmnl (-lmnl)
Set is as a 'Won't Fix'.
Assigning the Jammy part of the bug to Nobody.
I think there is no urgent case to take care of it now, if there exists a real
workaround.
In any trouble and in case of problem which will be still felt, please reach
out to me
and I will continue with the SRU.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libmnl in Ubuntu.
https://bugs.launchpad.net/bugs/1971523
Title:
Static build does not work for libmnl (-lmnl)
Status in libmnl package in Ubuntu:
Fix Released
Status in libmnl source package in Jammy:
Won't Fix
Status in libmnl package in Debian:
Fix Committed
Bug description:
[Test Case]
$ cat > /tmp/hello.c <
int main() {
printf("Hello world! (and LP: #1971523)\n");
}
EOF
$ gcc -o /tmp/hello /tmp/hello.c -lmnl
(dynamic libs work)
$ gcc -static -o /tmp/hello /tmp/hello.c -lmnl
/usr/bin/ld: cannot find -lmnl: No such file or directory
[Original Report]
My program uses both -lmnl and -lnetfilter_queue and in Ubuntu 20.04 the
-lnetfilter_queue did not work and -lmnl worked for static builds. In Ubuntu
22.04 the problem is reversed, -lnetfilter_queue works but -lmnl doesn't for
static builds. This is very awkward during the transition 20.04->22.04 when
both should be supported.
I compensated in Ubuntu 20.04 by building netfilter_queue locally;
https://github.com/Nordix/nfqueue-loadbalancer#build
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libmnl0:amd64 1.0.4-3build2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Wed May 4 07:33:26 2022
InstallationDate: Installed on 2018-09-07 (1334 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: libmnl
UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmnl/+bug/1971523/+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 1971323] Re: Merge six from Debian unstable for kinetic
** Changed in: six (Ubuntu) Milestone: ubuntu-22.06 => later -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to six in Ubuntu. https://bugs.launchpad.net/bugs/1971323 Title: Merge six from Debian unstable for kinetic Status in six package in Ubuntu: New Bug description: Upstream: tbd Debian: 1.16.0-3 Ubuntu: 1.16.0-3ubuntu1 Debian typically updates six every 2 months on average, but it was last updated 21.12 and looks overdue. Check back in on this monthly. ### New Debian Changes ### six (1.16.0-3) unstable; urgency=medium [ Debian Janitor ] * Bump debhelper from old 12 to 13. * Update standards version to 4.5.1, no changes needed. [ Colin Watson ] * Link directly to upstream in Homepage and debian/copyright. -- Colin Watson Sun, 26 Dec 2021 02:24:26 + six (1.16.0-2) unstable; urgency=medium * Team upload. [ Andreas Beckmann ] * python-six/python3-six: Copy Breaks: python (<< 2.7.18), python-minimal (<< 2.7.18), libpython-stdlib (<< 2.7.18), python-iso8601 (<< 0.1.12-2~), python-pbr (<< 5.4.5) from python2.7 to ensure removal of the unversioned python packages (and some persisting obsolete Python 2 module packages) on upgrades from buster. In some upgrade scenarios (mostly involving openstack packages) these Breaks in python2.7 were ineffective because the unversioned python packages got higher scores than python2.7. python-six/python3-six are usually very high scoring Python module packages in these cases, making them ideal candidates for such copies of the Breaks. (Closes: #991433) -- Stefano Rivera Tue, 27 Jul 2021 11:44:18 -0400 six (1.16.0-1) unstable; urgency=medium * New upstream release. -- Colin Watson Sun, 09 May 2021 11:40:54 +0100 six (1.15.0-2) unstable; urgency=medium [ Ondřej Nový ] * d/control: Update Maintainer field with new Debian Python Team contact address. * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. [ Colin Watson ] * Remove Barry Warsaw from Uploaders, with thanks for their previous contributions (closes: #970181). -- Colin Watson Tue, 10 Nov 2020 00:16:45 + six (1.15.0-1) unstable; urgency=medium [ Debian Janitor ] * Update standards version to 4.5.0, no changes needed. [ Colin Watson ] * New upstream release. -- Colin Watson Sun, 24 May 2020 10:23:22 +0100 six (1.14.0-3) unstable; urgency=medium * Dont run unittests for python2 binary, to reduce pytest rdeps -- Sandro Tosi Mon, 13 Apr 2020 20:16:04 -0400 six (1.14.0-2) unstable; urgency=medium * Build-depend on python2 rather than python. -- Colin Watson Tue, 21 Jan 2020 09:44:26 + six (1.14.0-1) unstable; urgency=medium [ Debian Janitor ] * Remove unnecessary team-upload line in changelog. * Set upstream metadata fields: Bug-Database, Repository. * Set upstream metadata fields: Bug-Submit, Repository-Browse. [ Colin Watson ] * New upstream release. -- Colin Watson Mon, 20 Jan 2020 21:39:42 + six (1.13.0-1) unstable; urgency=medium [ Emmanuel Arias ] * New upstream version 1.13.0 * d/control: Bump Standard-Version to 4.4.1 * d/control: Bump debhelper-compat to 12 (from 9) [ Colin Watson ] * Replace manually-written basic autopkgtests with 'Testsuite: autopkgtest-pkg-python'. * Remove build-dependencies on python-py and python3-py, no longer used upstream. * Fix HTML paths in doc-base control file. -- Colin Watson Tue, 12 Nov 2019 08:10:54 + six (1.12.0-2) unstable; urgency=medium ### Old Ubuntu Delta ### six (1.16.0-3ubuntu1) jammy; urgency=medium * Drop Breaks on python to allow python-is-python2 to remain when upgrading from Focal (LP: #1958720) -- Robie Basak Wed, 13 Apr 2022 21:08:40 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/six/+bug/1971323/+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 1982462] Re: Some modprobe loading services requested by the pstore service fail
** Merge proposal linked: https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/428487 -- 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/1982462 Title: Some modprobe loading services requested by the pstore service fail Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Confirmed Status in systemd source package in Jammy: Triaged Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] It has been detected that some modprobe services fail on UC22 after the jammy upgrade 249.11-0ubuntu3.4: $ systemctl --system --no-ask-password --no-pager list-units --state=failed Failed units: UNIT LOAD ACTIVE SUBDESCRIPTION ● modprobe@chromeos_pstore.service loaded failed failed Load Kernel Module chromeos_pstore ● modprobe@efi_pstore.service loaded failed failed Load Kernel Module efi_pstore ● modprobe@mtdpstore.service loaded failed failed Load Kernel Module mtdpstore ● modprobe@pstore_blk.service loaded failed failed Load Kernel Module pstore_blk ● modprobe@pstore_zone.service loaded failed failed Load Kernel Module pstore_zone ● modprobe@ramoops.service loaded failed failed Load Kernel Module ramoops This happens because of some changes to systemd-pstore.service that now has: After=modprobe@efi_pstore.service modprobe@mtdpstore.service modprobe@chromeos_pstore.service modprobe@ramoops.service modprobe@pstore_zone.service modprobe@pstore_blk.service Wants=modprobe@efi_pstore.service modprobe@mtdpstore.service modprobe@chromeos_pstore.service modprobe@ramoops.service modprobe@pstore_zone.service modprobe@pstore_blk.service This causes too many tries of the modprobe services, that fail in the end with Jul 20 09:02:39 ubuntu systemd[1]: modprobe@chromeos_pstore.service: Start request repeated too quickly. Although we have seen this only on UC22, it potentially can affect classic systems as well, as systemd-pstore.service is re-tried there a few times too. See https://github.com/snapcore/core-base/issues/72 for more details. A fix for this is available upstream: https://github.com/systemd/systemd/commit/9625350e5381a68c1179ae4581e7586c206663e1 [Test Plan] Start the device and check that there is no modprobe-pstore related failed service. This is racy, so a few tries will be needed to make sure things are fine. [Where problems could occur] The modprobe services are usually dependencies from other services, so it should be fine if the retry behavior is controlled by those other services. Risk should be small. If something goes wrong we might see a lot of restarts for these services. [Other Info] Testing should happen on UC22 too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982462/+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 1943441] Re: lxc: lxc-test-parse-config-file failure (expected value and retrieved value do not match)
Failing with 2022.08.08/focal/linux-fips/5.4.0-1060.68 (note that 1059.67 was a security release so we don't have test data for it) ** Tags added: sru-20220808 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1943441 Title: lxc: lxc-test-parse-config-file failure (expected value and retrieved value do not match) Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Focal: New Status in lxc source package in Impish: Confirmed Bug description: I'm getting the following error with the lxc kernel autotest on impish: 08:46:04 DEBUG| parse_config_file.c: 60: set_get_compare_clear_save_load: expected value "system_u:system_r:lxc_t:s0:c22" and retrieved value "" for config key "lxc.selinux.context" do not match 08:46:04 DEBUG| 08:46:04 DEBUG| parse_config_file.c: 382: main: lxc.selinux.context 08:46:06 INFO | ERRORubuntu_lxc.lxc-test-parse-config-file ubuntu_lxc.lxc-test-parse-config-filetimestamp=1631090766localtime=Sep 08 08:46:06Command failed, rc=1, Command returned non-zero exit status * Command: /tmp/lxc-pkg-ubuntu/src/tests/lxc-test-parse-config-file Exit status: 1 Duration: 0.0550210475922 stderr: parse_config_file.c: 60: set_get_compare_clear_save_load: expected value "system_u:system_r:lxc_t:s0:c22" and retrieved value "" for config key "lxc.selinux.context" do not match parse_config_file.c: 382: main: lxc.selinux.context I haven't investigated very much, but it looks like a (mis)configuration change / issue. Does it ring any bell? Otherwise I'll investigate more. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1943441/+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 1971523] Re: Static build does not work for libmnl (-lmnl)
** Changed in: libmnl (Ubuntu Jammy)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libmnl in Ubuntu.
https://bugs.launchpad.net/bugs/1971523
Title:
Static build does not work for libmnl (-lmnl)
Status in libmnl package in Ubuntu:
Fix Released
Status in libmnl source package in Jammy:
Won't Fix
Status in libmnl package in Debian:
Fix Committed
Bug description:
[Test Case]
$ cat > /tmp/hello.c <
int main() {
printf("Hello world! (and LP: #1971523)\n");
}
EOF
$ gcc -o /tmp/hello /tmp/hello.c -lmnl
(dynamic libs work)
$ gcc -static -o /tmp/hello /tmp/hello.c -lmnl
/usr/bin/ld: cannot find -lmnl: No such file or directory
[Original Report]
My program uses both -lmnl and -lnetfilter_queue and in Ubuntu 20.04 the
-lnetfilter_queue did not work and -lmnl worked for static builds. In Ubuntu
22.04 the problem is reversed, -lnetfilter_queue works but -lmnl doesn't for
static builds. This is very awkward during the transition 20.04->22.04 when
both should be supported.
I compensated in Ubuntu 20.04 by building netfilter_queue locally;
https://github.com/Nordix/nfqueue-loadbalancer#build
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libmnl0:amd64 1.0.4-3build2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Wed May 4 07:33:26 2022
InstallationDate: Installed on 2018-09-07 (1334 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: libmnl
UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmnl/+bug/1971523/+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 1979952] Re: Bind mount to NFS mount fails on Ubuntu 22.04
** Description changed: + [Impact] + Some NFS setups that have worked on previous versions of Ubuntu are now broken. Specifically, when creating a bind mount, systemd will fail if the directory already exists on NFS. + + [Test Plan] + This test plan requires an NFS server to be in place. The exact setup is not important, but for the purposes of this test plan we will assume the server exports /data, which contains a directory called home. + + * Make sure nfs-common is installed: + + $ apt install nfs-common -y + + * Check the NFS server exports using showmount: + + $ showmount -e $NFS_SERVER_IP + Export list for $NFS_SERVER_IP: + /data * + + * Add the appropriate entries to /etc/fstab. In this example, we will + make /home2 a bind mount to /data/home: + + # /etc/fstab + $NFS_SERVER_IP:/data /data nfs defaults,nfsvers=3 0 0 + /data/home /home2 none bind,_netdev,x-systemd.requires-mounts-for=/data 0 0 + + * Check systemctl status home2.mount. On an affected system, we should + see a permission denied error: + + $ systemctl status home2.mount + x home2.mount - /home2 + Loaded: loaded (/etc/fstab; generated) + Active: failed (Result: resources) +Where: /home2 + What: /data/home + Docs: man:fstab(5) + man:systemd-fstab-generator(8) + + systemd[1]: home2.mount: Failed to make bind mount source '/data/home': Permission denied + systemd[1]: home2.mount: Failed to run 'mount' task: Permission denied + systemd[1]: home2.mount: Failed with result 'resources'. + systemd[1]: Failed to mount /home2. + + * On a patched system, we expect /home2 to be mounted successfully. + + [Where problems could occur] + The patch makes it so that systemd will not fail bind mounts immediately if creating the directory fails. Thus, any regressions would be seen during bind mounts with systemd. N.B. that this patch restores previous behavior in systemd. + + [Original Description] I have the following setup: - /data is an NFS mount. - /home is a bind mount to /data/home. Configured in /etc/fstab with these lines: $FILE_SERVER:/data /data nfs defaults 0 0 /data/home /home none bind,_netdev,x-systemd.requires-mounts-for=/data 0 0 This has worked with the same configuration for me on at least Ubuntu 18.04 and Ubuntu 20.04, but on Ubuntu 22.04 the mount of /home fails when attempted by systemd. So not only is /home not mounted after boot, but also when I run "sudo systemctl start home.mount", it fails. The journal entries are this: sudo[1316]: wendler : TTY=pts/0 ; PWD=/home/wendler ; USER=root ; COMMAND=/usr/bin/systemctl start home.mount sudo[1316]: pam_unix(sudo:session): session opened for user root(uid=0) by wendler(uid=1000) systemd[1]: home.mount: Directory /home to mount over is not empty, mounting anyway. systemd[1]: home.mount: Failed to make bind mount source '/data/home': Permission denied systemd[1]: home.mount: Failed to run 'mount' task: Permission denied systemd[1]: home.mount: Failed with result 'resources'. systemd[1]: Failed to mount /home. However, when I run "sudo mount /home" it works. Now the weird thing is that after I have mounted /home manually once and unmounted it again, then "sudo systemctl start home.mount" suddenly also works! But of course only until the next reboot. And even if I just do "ls /data" once (either as root or as my user), it also makes "sudo systemctl start home.mount" start working! To be fully clear: - Booting the system (/home fails to mount) - sudo systemctl start home.mount # fails - sudo ls /data # shows correct output - sudo systemctl start home.mount # works! - Additional information: The NFS export for /data has root_squash set and if I remove this option, the bind mount of /home works as it should. However, both /data and /data/home have mode rwxr-xr-x, so root is able to enter and read these directories even despite root_squash. It is not a network or mount-order problem. Not only is the bind mount to /home correctly attempted after /data is mounted during boot, remember that the bind mount also fails when I try it with "sudo systemctl start home.mount" minutes afterwards. Versions (system is a recent installation with all updates applied): - Ubuntu 22.04 - Linux 5.15.0-40-generic - systemd 249.11-0ubuntu3.3 - util-linux 2.37.2-4ubuntu3 This appears on both Ubuntu 22.04 machines that I have (a hardware machine and a VM). -- 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/1979952 Title: Bind mount to NFS mount fails on Ubuntu 22.04 Status in systemd: Unknown Status in systemd package in Ubuntu: In Progress Status in systemd source package in Jammy: New Status in systemd source package in Kinetic: In Progress Bug description:
[Touch-packages] [Bug 1871465] Re: ssh_config(5) contains outdated information
> Fixing this is nice for the users, but OTOH very low severity and would cause a package download and update on almost every Ubuntu in the world. Therefore we will mark this as block-proposed and keep it in focal-proposed so that a later real update (security or functional) will pick this up from -proposed and then fix it in the field for real. Note that then the tag should be block-proposed-focal, not block- proposed. ** Tags removed: block-proposed ** Tags added: block-proposed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1871465 Title: ssh_config(5) contains outdated information Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Focal: Triaged Status in openssh source package in Hirsute: Won't Fix Status in openssh source package in Impish: Won't Fix Bug description: [Impact] The problem here is straightforward. The case is to fix manpages. They need to reflect a change done to the code some time ago. That problem might be annoying for users before being fixed. Backport upstream fix to Focal Origin: https://github.com/openssh/openssh-portable/commit/53ea05e09b04fd7b6dea66b42b34d65fe61b9636 [Test Plan] Make a container for testing: First option: $ lxc launch images:ubuntu/bionic focal-test $ lxc shell focal-test Simply install the openssh package using ‘apt install’ and check both ssh_config.5 and sshd_config.5 files. You should be able to spot the ‘ssh_rsa’ in these files. [Where problems could occur] Any code change might change the behavior of the package in a specific situation and cause other errors. Next things which might cause regression are new dependencies which might not align and it is obvious the dependencies are upgraded and it might be a problem, but it is really unlikely. Even none of the rather generic cases above does apply here as we only change non-functional content in the form of the man page; Therefore the only risk is out of re-building the package which could pick up something from e.g. a changed toolchain. [Other Info] Fixing this is nice for the users, but OTOH very low severity and would cause a package download and update on almost every Ubuntu in the world. Therefore we will mark this as block-proposed and keep it in focal-proposed so that a later real update (security or functional) will pick this up from -proposed and then fix it in the field for real. original report--- The release of OpenSSH 8.2 has removed `ssh-rsa` from the default list of CACertificateAlgorithms. However the latest `openssh-client` still ships the man page for ssh_config(5) that contains the following description: CASignatureAlgorithms Specifies which algorithms are allowed for signing of certificates by certificate authorities (CAs). The default is: ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521, ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa ssh(1) will not accept host certificates signed using algorithms other than those specified. As far as I am concerned, `ssh-rsa` should be dropped from the list so as to match the behavior of ssh(1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1871465/+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 1030022] Re: Port from legacy Xlib to modern XCB
** No longer affects: compiz ** Changed in: compiz (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1030022 Title: Port from legacy Xlib to modern XCB Status in 9wm package in Ubuntu: New Status in aewm package in Ubuntu: New Status in aewm++ package in Ubuntu: New Status in afterstep package in Ubuntu: New Status in amiwm package in Ubuntu: Invalid Status in blackbox package in Ubuntu: New Status in cairo package in Ubuntu: New Status in compiz package in Ubuntu: Invalid Status in ctwm package in Ubuntu: New Status in dwm package in Ubuntu: Opinion Status in enlightenment package in Ubuntu: New Status in fvwm package in Ubuntu: New Status in fvwm1 package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Status in icewm package in Ubuntu: New Status in jwm package in Ubuntu: Invalid Status in larswm package in Ubuntu: New Status in lwm package in Ubuntu: New Status in matchbox-window-manager package in Ubuntu: New Status in metacity package in Ubuntu: Invalid Status in miwm package in Ubuntu: New Status in muffin package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in pekwm package in Ubuntu: New Status in ratpoison package in Ubuntu: New Status in sapphire package in Ubuntu: New Status in sawfish package in Ubuntu: New Status in spectrwm package in Ubuntu: Fix Released Status in tinywm package in Ubuntu: New Status in tritium package in Ubuntu: New Status in twm package in Ubuntu: New Status in vtwm package in Ubuntu: New Status in w9wm package in Ubuntu: New Status in windowlab package in Ubuntu: New Status in wm2 package in Ubuntu: New Status in wmaker package in Ubuntu: Opinion Status in xmonad package in Ubuntu: New Bug description: Port/rewrite the window manager to use the modern XCB (X C Binding) library instead of the old legacy Xlib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/9wm/+bug/1030022/+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 1721955] Re: Human, Human-Clearlooks and other themes have incorrect gray window title color
** Changed in: compiz (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1721955 Title: Human, Human-Clearlooks and other themes have incorrect gray window title color Status in human-theme: New Status in community-themes package in Ubuntu: New Status in compiz package in Ubuntu: Invalid Status in gtk+2.0 package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Status in human-theme package in Ubuntu: Confirmed Status in marco package in Ubuntu: Invalid Status in mate-themes package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 MATE or 18.04 LTS MATE 2. Install Human theme from `human-theme` package 3. Select Human theme from `mate-control-center` Appearance Expected results: window title color is set to Ubuntu's orange (#FFBE6B) Actual results: window title color is set to different gray/silver color (#a5a5a2) Note: other themes are affected too. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: human-theme 0.39.2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu2 Architecture: i386 CurrentDesktop: MATE Date: Sat Oct 7 15:43:03 2017 InstallationDate: Installed on 2017-10-07 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 (20170925.1) PackageArchitecture: all SourcePackage: human-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/human-theme/+bug/1721955/+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 1986817] [NEW] package vim-common 2:8.1.2269-1ubuntu5.7 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo
Public bug reported: no further details. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: vim-common 2:8.1.2269-1ubuntu5.7 ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 AptOrdering: libwebkit2gtk-4.0-37:amd64: Install libjavascriptcoregtk-4.0-18:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Aug 17 09:39:48 2022 ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. InstallationDate: Installed on 2021-12-28 (231 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: vim Title: package vim-common 2:8.1.2269-1ubuntu5.7 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vim (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1986817 Title: package vim-common 2:8.1.2269-1ubuntu5.7 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Status in vim package in Ubuntu: New Bug description: no further details. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: vim-common 2:8.1.2269-1ubuntu5.7 ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 AptOrdering: libwebkit2gtk-4.0-37:amd64: Install libjavascriptcoregtk-4.0-18:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Aug 17 09:39:48 2022 ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. InstallationDate: Installed on 2021-12-28 (231 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: vim Title: package vim-common 2:8.1.2269-1ubuntu5.7 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1986817/+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 1981592] Re: Please remove wpewebkit and block syncs from Debian
** Changed in: gst-plugins-bad1.0 (Ubuntu) Status: New => Fix Committed ** Changed in: gst-plugins-bad1.0 (Ubuntu) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1981592 Title: Please remove wpewebkit and block syncs from Debian Status in cog package in Ubuntu: New Status in gst-plugins-bad1.0 package in Ubuntu: Fix Committed Status in wpewebkit package in Ubuntu: Incomplete Bug description: The wpewebkit package contains a whole webkit browser engine. It is currently not used by anything of substance in Ubuntu: $ reverse-depends src:wpewebkit Reverse-Depends * cog (for libwpewebkit-1.1-0) * gstreamer1.0-wpe (for libwpewebkit-1.1-0) cog is a single-window browser for embedded devices that is not used by anything else in the archive. gstreamer1.0-wpe is a plugin based on wpewebkit that is not used by anything else in the archive. Using this browser engine on the Internet is very risky as it it not currently maintained and contains hundreds of security flaws, and maintaining it requires a tremendous amount of work. As such, I don't believe this package is suitable for the Ubuntu archive. I recommend we disable the build in gstreamer and remove both cog and wpewebkit, and put on block on syncs from Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cog/+bug/1981592/+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 1982553] Re: Search domains not working after upgrading to Ubuntu 22.04
I'm seeing a similar issue as well. Hostnames on my local network no longer resolve after upgrading to Ubuntu 22.04.1 >cat 01-network-manager-all.yaml # Let NetworkManager manage all devices on this system network: version: 2 renderer: NetworkManager jpschewe@jon-2019:/etc/netplan >cat 01-network-manager-all.yaml # Let NetworkManager manage all devices on this system network: version: 2 renderer: NetworkManager /etc/netplan jpschewe@jon-2019:/etc/netplan >resolvectl Global Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: foreign Link 2 (enp8s0f1) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 3 (wlp0s20f3) Current Scopes: DNS Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 192.168.46.1 DNS Servers: 192.168.46.1 DNS Domain: mn.mtu.net Link 4 (vboxnet0) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported jpschewe@jon-2019:/etc/netplan >ping eggplant-2013 ping: eggplant-2013: Name or service not known /etc/netplan jpschewe@jon-2019:/etc/netplan >ping eggplant-2013.mn.mtu.net PING eggplant-2013.mn.mtu.net (192.168.42.129) 56(84) bytes of data. -- 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/1982553 Title: Search domains not working after upgrading to Ubuntu 22.04 Status in netplan.io package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: Hello, After upgrading to Ubuntu 22.04, I noticed that search domains are not working anymore. Either I configure search domains via netplan or with graphical "nm- connection-editor", this is not taken into account when resolving domain names. For instance if I configure "domain.com" in search domains list, looking for "host" does not look for "host.domain.com". This is confirmed with a wireshark capture. Consequently if I want to connect with SSH to host.domain.com, I have to type the entire url. In Ubuntu 20.04 this works correctly. With a packet capture I can see one domain lookup for each of my search domains configured. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1982553/+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 1982553] Re: Search domains not working after upgrading to Ubuntu 22.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1982553 Title: Search domains not working after upgrading to Ubuntu 22.04 Status in netplan.io package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: Hello, After upgrading to Ubuntu 22.04, I noticed that search domains are not working anymore. Either I configure search domains via netplan or with graphical "nm- connection-editor", this is not taken into account when resolving domain names. For instance if I configure "domain.com" in search domains list, looking for "host" does not look for "host.domain.com". This is confirmed with a wireshark capture. Consequently if I want to connect with SSH to host.domain.com, I have to type the entire url. In Ubuntu 20.04 this works correctly. With a packet capture I can see one domain lookup for each of my search domains configured. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1982553/+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 1983481] Re: _run_hook called with ui=None
Fixed crash upstream:
https://github.com/canonical/apport/commit/f8edc7280d492e710218c193e53542f1f86cfa91
** Changed in: apport
Status: New => Fix Committed
** Changed in: apport
Milestone: None => 2.23.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1983481
Title:
_run_hook called with ui=None
Status in Apport:
Fix Committed
Status in apport package in Ubuntu:
Triaged
Bug description:
When totem crashes and I try to report the crash with ubuntu-bug,
sometimes I get a stack trace:
jik@jik5:~$ ubuntu-bug /var/crash/_usr_bin_totem.1000.crash
ERROR: hook /usr/share/apport/package-hooks/source_totem.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in
_run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_totem.py", line 9, in add_info
response = ui.choice("How would you describe the issue?", ["The totem
interface is not working correctly", "No sound is being played", "Some audio
files or videos are not being played correctly"], False)
AttributeError: 'NoneType' object has no attribute 'choice'
jik@jik5:~$
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: totem-common 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 3 10:35:28 2022
InstallationDate: Installed on 2019-01-02 (1308 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
LogAlsaMixer:
Simple mixer control 'Line',0
Capabilities: cvolume cvolume-joined cswitch cswitch-joined
Capture channels: Mono
Limits: Capture 0 - 15
Mono: Capture 15 [100%] [15.00dB] [on]
PackageArchitecture: all
SourcePackage: totem
UpgradeStatus: Upgraded to jammy on 2022-02-20 (163 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1983481/+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 1897932] Re: systemd-repart not packaged
We got some response from the SRU team (@racb): https://lists.ubuntu.com/archives/ubuntu-devel/2022-August/042250.html Basically he suggests doing this change in a PPA/jammy-backports, or as a entirely new package: * "what if you were to put systemd-repart as a new package into a PPA, or into jammy-backports?" * "In general, adding new entirely new packages is considered OK from a regression risk perspective." Would this work for you @bluca? -- 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/1897932 Title: systemd-repart not packaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Confirmed Status in systemd package in Debian: Fix Released Bug description: [Impact] systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? The bug reporter would like to use it in their new raspberry pi images where they don't have cloud-init installed. The reporter is already using systemd-growfs, but they are missing the nice partition resizing part (so are using cloud-initramfs-growroot). Furthermore, in the mkosi image builder (https://github.com/systemd/mkosi), the systemd/mkosi developers would like to start using systemd-repart for partitioning. Unfortunately, they're currently blocked on this because 22.04 doesn't ship systemd- repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy and will do so until the next Ubuntu LTS is released. If we have to wait for the next LTS to be released, we'll have to wait for a considerable amount of time before we're able to start using systemd- repart. Being able to use systemd-repart will allow the systemd/mkosi developers to take advantage of its improved interface compared to sfdisk, as well as its builtin protections against race conditions surrounding the use of loop devices. The systemd/mkosi developers expect to be able to get rid of some nasty loop device failure in mkosi by using systemd-repart. [Test Plan] This is a missing extra executable. Once enabled it has self-tests in the build-time unit tests, and also a regression test in the autopkgtest 'upstream' suite. [Where problems could occur] Shipping systemd-repart will come with no additional risk. While there is a systemd-repart.service that runs on boot, it's configured to not do anything if no config files are shipped with the system or provided by the user. As such, the service, if enabled, will effectively be a noop. Aside from the service, there's the CLI tool systemd-repart and the accompanying man pages that will be shipped as part of the systemd package. Given that there's no risk involved with enabling systemd-repart, and given the useful features it provides, the systemd/mkosi developers would like to request that systemd-repart be enabled in Ubuntu and backported to Jammy so that they can start adopting it in mkosi. Runtime behavior of existing components is not affected by the build config change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897932/+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 1833161] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all
Hi, I had the same problem. Comment #5 worked for me (after reboot): 1. Open terminal 2. sudo nano /etc/modprobe.d/alsa-base.conf 3. Add mentioned line in comment at the bottom of the conf file: options snd-hda-intel model=clevo-p950 4. CTRL+O -> CTRL+C 5. sudo reboot 6. test your sound My relevant specs: OS: Ubuntu 22.04LTS Soundcard: HDA Intel PCH Chip: Realtek ALC1220 Thank you! -- 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/1833161 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hello to all, My Ubuntu version is 18.04.02 LTS and I've setup a dual-boot with windows 10. Speakers and audio jack work totally fine under Windows 10, but they never work with Ubuntu. List of some of the things I've tried: 1) I've tried all the steps from the "Sound Troubleshooting Procedure" 2) I've tried installing the "oem-audio-hda-daily-dkms" package; 3) I've tried to install/remove/reinstall alsa-base, alsa-utils, pulseaudio, pavucontrol many times 4) I've played with the options in the file /etc/modprobe.d/alsa-base.conf: a) I've tried to add "options snd-hda-intel model=auto" and I also tried different models: auto, clevo, laptop-eapd, clevo m-720, generic, basic and even z71v position_fix=1. 5) I've tried adding : Code: [General] description = Headphones + Digital Output (S/PDIF) in the file "/usr/share/pulseaudio/alsa-mixer/paths/iec958-stereo-output.conf" 6) I've even tried a live USB stick with Ubuntu 19.04 (after reading somewhere that this was fixed on 19.04), but I found out that there was no sound on Ubuntu 19.04 as well. Also, you can find my ALSA information here: http://alsa- project.org/db/?f=bcdf5c8be31ce8b9e848a29ef292e9125f26def0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jproberge 1737 F pulseaudio /dev/snd/controlC0: jproberge 1737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jun 17 20:37:29 2019 InstallationDate: Installed on 2019-06-15 (2 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: HDA NVidia - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1236 F pulseaudio jproberge 1737 F pulseaudio /dev/snd/controlC0: gdm1236 F pulseaudio jproberge 1737 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08P dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08P:bd05/07/2019:svnNotebook:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnNotebook:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_96_97Ex,Rx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833161/+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 1983481] Re: _run_hook called with ui=None
** Also affects: apport
Importance: Undecided
Status: New
** Changed in: apport
Importance: Undecided => Medium
** Changed in: apport (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1983481
Title:
_run_hook called with ui=None
Status in Apport:
New
Status in apport package in Ubuntu:
Triaged
Bug description:
When totem crashes and I try to report the crash with ubuntu-bug,
sometimes I get a stack trace:
jik@jik5:~$ ubuntu-bug /var/crash/_usr_bin_totem.1000.crash
ERROR: hook /usr/share/apport/package-hooks/source_totem.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in
_run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_totem.py", line 9, in add_info
response = ui.choice("How would you describe the issue?", ["The totem
interface is not working correctly", "No sound is being played", "Some audio
files or videos are not being played correctly"], False)
AttributeError: 'NoneType' object has no attribute 'choice'
jik@jik5:~$
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: totem-common 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 3 10:35:28 2022
InstallationDate: Installed on 2019-01-02 (1308 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
LogAlsaMixer:
Simple mixer control 'Line',0
Capabilities: cvolume cvolume-joined cswitch cswitch-joined
Capture channels: Mono
Limits: Capture 0 - 15
Mono: Capture 15 [100%] [15.00dB] [on]
PackageArchitecture: all
SourcePackage: totem
UpgradeStatus: Upgraded to jammy on 2022-02-20 (163 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1983481/+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
