[Touch-packages] [Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
Thank you Seb, I had the issue reported in this bug in a WeWork today (first time connecting since updating to Jammy) and the package in -proposed resolved the issue for me as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Committed Bug description: * Impact Connecting to some PEAP wifi doesn't work anymore since the openssl3 transition Details on the issue can be found on http://lists.infradead.org/pipermail/hostap/2022-May/040511.html * Test case Try using a PEAP wifi not implementing RFC5746, it should be able to connect * Regression potential The change allows to connect to less secure WiFis the same way that wpa allowed before openssl3, lower security enforcement isn't ideal but still better than non working hardware. WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
Promotion from -proposed sure would be nice. I see verification has been done but a update excuses shows an netplan.io regression[1]. I'm not sure if the test is flaky but I see that seb retried it a few times[2] last week and it failed consistently, so maybe not. I'm just curious if there's any status on the test failure. (Also, I started writing this thinking it had been a month but it's been less than a week and I can't tell time. I know it wouldn't be promoted with less than a week in -proposed anyway.) [1] https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#wpa [2] https://autopkgtest.ubuntu.com/packages/netplan.io/jammy/arm64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Committed Bug description: * Impact Connecting to some PEAP wifi doesn't work anymore since the openssl3 transition Details on the issue can be found on http://lists.infradead.org/pipermail/hostap/2022-May/040511.html * Test case Try using a PEAP wifi not implementing RFC5746, it should be able to connect * Regression potential The change allows to connect to less secure WiFis the same way that wpa allowed before openssl3, lower security enforcement isn't ideal but still better than non working hardware. WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962018] [NEW] pypy3compile errors during postinst confuses user
Public bug reported: Could you add some clarifying output in the postinst around pypy3compile failures to give context to an end user? The errors as they stand don't indicate that this is pyp3 specific and can be concerning (they also give the impression that QA isn't catching basic python bugs which isn't the case). pypy3 support was added to dh-python3 towards the end of 2018 as "WIP" such that postinst will call `pypy3compile $PACKAGE || true` to ignore errors if pypy3 is installed. I was talking with a user that saw this fail when installing an update for python3-software-properties and the error message was cause for concern and confusion, for that package it looked like this: Setting up python3-software-properties (0.99.19) ... Failed to byte-compile /usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py: File "/usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py", line 436 def __init__(self, sourceslist=None, /, files=None): ^ SyntaxError: invalid syntax (expected ')') That's all fine, the author has introduced the positional-only parameter (PEP570) new to python 3.8 and that's supported in cpython shipped by default in the distro, but it isn't supported by pypy3. I think it's reasonable for the maintainer of a package to decide that they want to use new features and that they might not have testing with pypy3 installed as a requirement. The fact that the failure is pypy3compile and not python3compile isn't communicated for the failure nor that it's optional. The user might think that the package is broken for the default interpreter. Would you consider adding a message before each compilation step to call out which interpreter is byte-compiling the module as well as pypy3 being optional/best-effort and may fail? Preferably you might also indicate the impact (i.e. the package is usable with the system python3 interpreter but pypy3) to set expectations with the end user. Thank you Piotr! ** Affects: dh-python (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1962018 Title: pypy3compile errors during postinst confuses user Status in dh-python package in Ubuntu: New Bug description: Could you add some clarifying output in the postinst around pypy3compile failures to give context to an end user? The errors as they stand don't indicate that this is pyp3 specific and can be concerning (they also give the impression that QA isn't catching basic python bugs which isn't the case). pypy3 support was added to dh-python3 towards the end of 2018 as "WIP" such that postinst will call `pypy3compile $PACKAGE || true` to ignore errors if pypy3 is installed. I was talking with a user that saw this fail when installing an update for python3-software-properties and the error message was cause for concern and confusion, for that package it looked like this: Setting up python3-software-properties (0.99.19) ... Failed to byte-compile /usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py: File "/usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py", line 436 def __init__(self, sourceslist=None, /, files=None): ^ SyntaxError: invalid syntax (expected ')') That's all fine, the author has introduced the positional-only parameter (PEP570) new to python 3.8 and that's supported in cpython shipped by default in the distro, but it isn't supported by pypy3. I think it's reasonable for the maintainer of a package to decide that they want to use new features and that they might not have testing with pypy3 installed as a requirement. The fact that the failure is pypy3compile and not python3compile isn't communicated for the failure nor that it's optional. The user might think that the package is broken for the default interpreter. Would you consider adding a message before each compilation step to call out which interpreter is byte-compiling the module as well as pypy3 being optional/best-effort and may fail? Preferably you might also indicate the impact (i.e. the package is usable with the system python3 interpreter but pypy3) to set expectations with the end user. Thank you Piotr! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1962018/+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 1918190] [NEW] Enabling/Disabling VPN crashes window manager
Public bug reported:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the session login screen.
$ lsb_release -rd
Description:Ubuntu Hirsute Hippo (development branch)
Release:21.04
$ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk -F=
'{print $2}'
wayland
$ apt-cache policy network-manager
network-manager:
Installed: 1.30.0-1ubuntu1
Candidate: 1.30.0-1ubuntu1
Version table:
*** 1.30.0-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: network-manager 1.30.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 8 14:12:44 2021
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2017-04-21 (1416 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404)
RebootRequiredPkgs:
libssl1.1
libssl1.1
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI
WWAN-HW WWAN
running 1.30.0 connected started full enabled enabled
disabled enabled enabled
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug hirsute wayland-session
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1918190
Title:
Enabling/Disabling VPN crashes window manager
Status in network-manager package in Ubuntu:
New
Bug description:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the session login screen.
$ lsb_release -rd
Description: Ubuntu Hirsute Hippo (development branch)
Release: 21.04
$ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk
-F= '{print $2}'
wayland
$ apt-cache policy network-manager
network-manager:
Installed: 1.30.0-1ubuntu1
Candidate: 1.30.0-1ubuntu1
Version table:
*** 1.30.0-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: network-manager 1.30.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 8 14:12:44 2021
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2017-04-21 (1416 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404)
RebootRequiredPkgs:
libssl1.1
libssl1.1
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.30.0 connected started full enabled enabled
disabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1918190/+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 1918190] Re: Enabling/Disabling VPN crashes window manager
This looks to be around the time of the issue where I disabled a VPN
connection (from syslog):
Mar 8 14:11:54 splat gnome-shell[677801]: **
Mar 8 14:11:54 splat gnome-shell[677801]:
Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed:
assertion failed: (!clutter_actor_get_reactive (actor))
Mar 8 14:11:54 splat gnome-shell[677801]: Bail out!
Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed:
assertion failed: (!clutter_actor_get_reactive (actor))
Mar 8 14:11:54 splat gnome-shell[677801]: GNOME Shell crashed with signal 6
Mar 8 14:11:54 splat gnome-shell[677801]: == Stack trace for context
0x556edc56f150 ==
Mar 8 14:11:54 splat gnome-shell[677801]: #0 556edea1ffc0 i
resource:///org/gnome/shell/ui/popupMenu.js:390 (1162dc8fad80 @ 138)
Mar 8 14:11:54 splat gnome-shell[677801]: #1 556edea1ff18 i
resource:///org/gnome/shell/ui/status/network.js:1429 (2ab06bf803d0 @ 171)
Mar 8 14:11:54 splat gnome-shell[677801]: #2 556edea1fe80 i
resource:///org/gnome/shell/ui/status/network.js:171 (2ab06bf82560 @ 111)
Mar 8 14:11:54 splat gnome-shell[677801]: #3 7ffef0da2770 b
self-hosted:850 (b5d5c736d80 @ 454)
Mar 8 14:11:54 splat gnome-shell[677801]: #4 556edea1fde0 i
resource:///org/gnome/shell/ui/popupMenu.js:411 (1162dc8face0 @ 56)
Mar 8 14:11:54 splat gnome-shell[677801]: #5 556edea1fd48 i
resource:///org/gnome/shell/ui/popupMenu.js:398 (1162dc8fad30 @ 41)
Mar 8 14:11:54 splat gnome-shell[677801]: #6 556edea1fca8 i
resource:///org/gnome/shell/ui/popupMenu.js:138 (1162dc8fb4c0 @ 88)
Mar 8 14:11:54 splat systemd[1]: Starting Network Manager Script Dispatcher
Service...
Mar 8 14:11:54 splat dbus-daemon[1286]: [system] Successfully activated
service 'org.freedesktop.nm_dispatcher'
** Attachment added: "journal"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1918190/+attachment/5474636/+files/journal
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the session login screen.
$ lsb_release -rd
Description: Ubuntu Hirsute Hippo (development branch)
Release: 21.04
$ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk
-F= '{print $2}'
wayland
$ apt-cache policy network-manager
network-manager:
- Installed: 1.30.0-1ubuntu1
- Candidate: 1.30.0-1ubuntu1
+ Installed: 1.30.0-1ubuntu1
+ Candidate: 1.30.0-1ubuntu1
+ Version table:
+ *** 1.30.0-1ubuntu1 500
+ 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
+ 100 /var/lib/dpkg/status
+
+ $ apt-cache policy gnome-shell
+ gnome-shell:
+ Installed: 3.38.3-3ubuntu1
+ Candidate: 3.38.3-3ubuntu1
Version table:
- *** 1.30.0-1ubuntu1 500
+ *** 3.38.3-3ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: network-manager 1.30.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 8 14:12:44 2021
IfupdownConfig:
- # interfaces(5) file used by ifup(8) and ifdown(8)
- auto lo
- iface lo inet loopback
+ # interfaces(5) file used by ifup(8) and ifdown(8)
+ auto lo
+ iface lo inet loopback
InstallationDate: Installed on 2017-04-21 (1416 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404)
RebootRequiredPkgs:
- libssl1.1
- libssl1.1
+ libssl1.1
+ libssl1.1
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
- RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
- running 1.30.0 connected started full enabled enabled
disabled enabled enabled
+ RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
+ running 1.30.0 connected started full enabled enabled
disabled enabled enabled
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1918190
Title:
Enabling/Disabling VPN crashes window manager
Status in gnome-shell package in Ubuntu:
New
Status in network-manager package in Ubuntu:
New
Bug description:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the session login screen.
$ lsb_release -rd
Descr
[Touch-packages] [Bug 1918190] Re: Enabling/Disabling VPN crashes window manager
As a workaround for anyone, you can use nmcli to bring up a VPN
connection.
Run `nmcli c` to get a list of connections, once you have the name you
can enable it with `nmcli c up $name` or disable it with `nmcli c down
$name`.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1918190
Title:
Enabling/Disabling VPN crashes window manager
Status in gnome-shell package in Ubuntu:
New
Status in network-manager package in Ubuntu:
New
Bug description:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the session login screen.
$ lsb_release -rd
Description: Ubuntu Hirsute Hippo (development branch)
Release: 21.04
$ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk
-F= '{print $2}'
wayland
$ apt-cache policy network-manager
network-manager:
Installed: 1.30.0-1ubuntu1
Candidate: 1.30.0-1ubuntu1
Version table:
*** 1.30.0-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
$ apt-cache policy gnome-shell
gnome-shell:
Installed: 3.38.3-3ubuntu1
Candidate: 3.38.3-3ubuntu1
Version table:
*** 3.38.3-3ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: network-manager 1.30.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 8 14:12:44 2021
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2017-04-21 (1416 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404)
RebootRequiredPkgs:
libssl1.1
libssl1.1
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.30.0 connected started full enabled enabled
disabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918190/+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 1918190] Re: Enabling/Disabling VPN crashes window manager
@3v1n0 (Marco Trevisan) has pointed out
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1651 as a
possible fix
** Description changed:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the session login screen.
$ lsb_release -rd
Description: Ubuntu Hirsute Hippo (development branch)
Release: 21.04
$ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk
-F= '{print $2}'
wayland
$ apt-cache policy network-manager
network-manager:
Installed: 1.30.0-1ubuntu1
Candidate: 1.30.0-1ubuntu1
Version table:
*** 1.30.0-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
$ apt-cache policy gnome-shell
gnome-shell:
- Installed: 3.38.3-3ubuntu1
- Candidate: 3.38.3-3ubuntu1
- Version table:
- *** 3.38.3-3ubuntu1 500
- 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
- 100 /var/lib/dpkg/status
+ Installed: 3.38.3-3ubuntu1
+ Candidate: 3.38.3-3ubuntu1
+ Version table:
+ *** 3.38.3-3ubuntu1 500
+ 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
+ 100 /var/lib/dpkg/status
+
+ $ dpkg-query -W|grep mutter
+ gir1.2-mutter-7:amd64 3.38.3-3ubuntu1
+ libmutter-7-0:amd64 3.38.3-3ubuntu1
+ mutter3.38.3-3ubuntu1
+ mutter-common 3.38.3-3ubuntu1
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: network-manager 1.30.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 8 14:12:44 2021
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2017-04-21 (1416 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404)
RebootRequiredPkgs:
libssl1.1
libssl1.1
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.30.0 connected started full enabled enabled
disabled enabled enabled
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1918190
Title:
Enabling/Disabling VPN crashes window manager
Status in gnome-shell package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Status in network-manager package in Ubuntu:
New
Bug description:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the session login screen.
$ lsb_release -rd
Description: Ubuntu Hirsute Hippo (development branch)
Release: 21.04
$ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk
-F= '{print $2}'
wayland
$ apt-cache policy network-manager
network-manager:
Installed: 1.30.0-1ubuntu1
Candidate: 1.30.0-1ubuntu1
Version table:
*** 1.30.0-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
$ apt-cache policy gnome-shell
gnome-shell:
Installed: 3.38.3-3ubuntu1
Candidate: 3.38.3-3ubuntu1
Version table:
*** 3.38.3-3ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
$ dpkg-query -W|grep mutter
gir1.2-mutter-7:amd64 3.38.3-3ubuntu1
libmutter-7-0:amd64 3.38.3-3ubuntu1
mutter3.38.3-3ubuntu1
mutter-common 3.38.3-3ubuntu1
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: network-manager 1.30.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 8 14:12:44 2021
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2017-04-21 (1416 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404)
RebootRequiredPkgs:
libssl1.1
libssl1.1
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1
[Touch-packages] [Bug 1992688] Re: firefox deb not installed
FYI, if a user has a 22.04 install where they have explicitly removed snapd/firefox this will add them back. Not sure if this was a consideration in the fix/testing. Also, the apt resolver is pulling in snapd while holding ubuntu-desktop back during staging which made finding the cause of the snapd/firefox installation a bit hard to track down since no packages upgraded in the same unattended-upgrades operation had dependencies on them. (thread: https://hachyderm.io/@rcj4747/110667685702206834) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1992688 Title: firefox deb not installed Status in firefox package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Status in firefox source package in Jammy: Invalid Status in ubuntu-meta source package in Jammy: Fix Released Bug description: Impact -- Applications which use x-www-browser to launch a browser will not work on a freshly installed Ubuntu 22.04 system as the firefox deb (which provides x-www-browser) is not installed. Test Plan - 1) Install Ubuntu 22.04.2 using an amd64 desktop iso image 2) Open a terminal 3) Run x-www-browser www.ubuntu.com 4) Observe a command not found message which recommends installing firefox Installing of a daily build of Ubuntu 22.04 with -proposed enabled and ubuntu-desktop version 1.481.1 will not exhibit the above problem. Where problems could occur -- Other Info -- I tested an upgrade from Ubuntu 20.04 to Ubuntu 22.04 and the firefox deb was not removed during the upgrade process so upgrades are a non-issue. Original Description Bug 1964036 leads me to believe that the firefox deb provides some important functionality (the firefox favourite icon in the gnome shell dock) but there is nothing that would require the deb to be installed (it is not seeded nor has an rdep) and the package description indicates that it can be safely removed. Is there some important functionality that it provides? ProblemType: BugDistroRelease: Ubuntu 22.10 Package: ubuntu-release-upgrader-core 1:22.10.8 ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 11:30:46 2022 InstallationDate: Installed on 2022-04-27 (167 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992688/+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 1844868] Re: cloud-images should not contain plymouth
Dimitri, I thought we looked into plymouth and it was doing additional setup during boot that caused us to leave it in the image. I wish I could recall what all that way. Anyhow, if that has changed we'd be open to it. Can you make the description a lot more descriptive and discuss 'why' we want to remove it and the priority? Thank you. ** Changed in: cloud-images Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1844868 Title: cloud-images should not contain plymouth Status in cloud-images: Incomplete Status in ubuntu-meta package in Ubuntu: New Bug description: cloud-images should not contain plymouth To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1844868/+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 1759440] Re: Docker trusty image is very slow
** Also affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1759440 Title: Docker trusty image is very slow Status in cloud-images: New Status in apt package in Ubuntu: New Bug description: I have strange slowness using the trusty image. I see no such slowness with the Artful image. I expect there is something wrong with my system/configuration, but I'm at a loss to explain what is going on. The difference appears to be IO related: root@gisli:~# docker run -it ubuntu:trusty /bin/bash root@5e4f73d56fa7:/# time apt-cache search iorate real0m8.666s user0m0.710s sys 0m7.957s root@5e4f73d56fa7:/# exit root@gisli:~# docker run -it ubuntu:artful /bin/bash root@5da05fb579d5:/# time apt-cache search iorate real0m0.049s user0m0.029s sys 0m0.020s Basic things feel very sluggish in it. apt-get update, installing packages, etc. However dd output looks fine: root@gisli:~# docker run -it ubuntu:trusty /bin/bash root@87749c754dc9:/# dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc 1024+0 records in 1024+0 records out 1073741824 bytes (1.1 GB) copied, 1.43277 s, 749 MB/s root@gisli:~# docker run -it ubuntu:artful /bin/bash root@7ab8fa9cd28a:/# dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc status=progress 1024+0 records in 1024+0 records out 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 1.37745 s, 780 MB/s As do things like transferring data to the image via nc, running sha256sum on large files. I haven't been able to pin down what the problem is. This is running on an Ubuntu Artful host using Docker 18.03.0-ce. root@gisli:~# docker pull ubuntu:trusty trusty: Pulling from library/ubuntu Digest: sha256:ed49036f63459d6e5ed6c0f238f5e94c3a0c70d24727c793c48fded60f70aa96 Status: Image is up to date for ubuntu:trusty Is there anything I could try? Or should this be expected? Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1759440/+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 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
I'll mention this here because I believe it's related, if not please correct me and I'll file a separate bug. When cron jobs are run /snap/bin is not in the path. -- 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/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in snapd source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: Won't Fix Status in snapd source package in Cosmic: Confirmed Status in systemd source package in Cosmic: Won't Fix Bug description: This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. Specifically, this is evident by e.g. $ systemd-run env. Or any other daemons that spawn shell scripts (e.g. cloud-init metadata acquired shell hooks, etc.). Since v232 systemd provides support for environment generators, snapd should package/ship a snippet that injects the correct snapd path into systemd environment. E.g.: $ sudo mkdir -p /usr/lib/systemd/system-environment-generators $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \ sudo tee /usr/lib/systemd/system-environment-generators/90-snapd Something similar can be done for user-environment-generators too. Note that user-environment-generators can generate unique variables per user. Note please use /usr/lib path, as it appears that /lib/systemd path is not working atm. Will check if that needs to be fixed up. systemd in xenial does not support system-environment-generators, thus we probably need to upload a patch to change the DEFAULT_PATH compiled in default there. [Testcase] $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1775219] [NEW] incorrectly reports package as unsupported if apt cache is empty
Public bug reported:
Cloud images ship with empty /var/lib/apt/lists/ to save on size.
Running 'ubuntu-bug ' will erroneously report that
the package is unsupported:
$ ubuntu-bug coreutils
*** Collecting problem information
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.
*** Problem in coreutils
The problem cannot be reported:
This is not an official Ubuntu package. Please remove any third party
package and try again.
A simpler recreate is:
$ python3 -c 'import
apport;print(apport.packaging.is_distro_package("coreutils"))'
False
$ sudo apt update -qq
All packages are up to date.
$ python3 -c 'import
apport;print(apport.packaging.is_distro_package("coreutils"))'
True
Desired result:
The message should instruct the user to run 'apt update' as root if they
think this is in error. That would improve usability and avoid false
reports about apport incorrectly flagging a package as unsupported.
Additionally, if the user is root (and optionally if the set of package
candidates only contains a 'now' component) self._cache.update();
self._cache.open() could be called to download lists.
** Affects: apport (Ubuntu)
Importance: Undecided
Status: New
--
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/1775219
Title:
incorrectly reports package as unsupported if apt cache is empty
Status in apport package in Ubuntu:
New
Bug description:
Cloud images ship with empty /var/lib/apt/lists/ to save on size.
Running 'ubuntu-bug ' will erroneously report that
the package is unsupported:
$ ubuntu-bug coreutils
*** Collecting problem information
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.
*** Problem in coreutils
The problem cannot be reported:
This is not an official Ubuntu package. Please remove any third
party package and try again.
A simpler recreate is:
$ python3 -c 'import
apport;print(apport.packaging.is_distro_package("coreutils"))'
False
$ sudo apt update -qq
All packages are up to date.
$ python3 -c 'import
apport;print(apport.packaging.is_distro_package("coreutils"))'
True
Desired result:
The message should instruct the user to run 'apt update' as root if
they think this is in error. That would improve usability and avoid
false reports about apport incorrectly flagging a package as
unsupported.
Additionally, if the user is root (and optionally if the set of
package candidates only contains a 'now' component)
self._cache.update(); self._cache.open() could be called to download
lists.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1775219/+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 1775219] Re: incorrectly reports package as unsupported if apt cache is empty
** Description changed:
Cloud images ship with empty /var/lib/apt/lists/ to save on size.
Running 'ubuntu-bug ' will erroneously report that
the package is unsupported:
- $ ubuntu-bug coreutils
+ $ ubuntu-bug coreutils
- *** Collecting problem information
+ *** Collecting problem information
- The collected information can be sent to the developers to improve the
- application. This might take a few minutes.
- .
+ The collected information can be sent to the developers to improve the
+ application. This might take a few minutes.
+ .
- *** Problem in coreutils
+ *** Problem in coreutils
- The problem cannot be reported:
+ The problem cannot be reported:
- This is not an official Ubuntu package. Please remove any third party
+ This is not an official Ubuntu package. Please remove any third party
package and try again.
A simpler recreate is:
$ python3 -c 'import
apport;print(apport.packaging.is_distro_package("coreutils"))'
False
$ sudo apt update -qq
All packages are up to date.
$ python3 -c 'import
apport;print(apport.packaging.is_distro_package("coreutils"))'
True
Desired result:
The message should instruct the user to run 'apt update' as root if they
think this is in error. That would improve usability and avoid false
reports about apport incorrectly flagging a package as unsupported.
Additionally, if the user is root (and optionally if the set of package
candidates only contains a 'now' component) self._cache.update();
self._cache.open() could be called to download lists.
+
+ Alternatively it could just check to see if lists have been downloaded.
--
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/1775219
Title:
incorrectly reports package as unsupported if apt cache is empty
Status in apport package in Ubuntu:
New
Bug description:
Cloud images ship with empty /var/lib/apt/lists/ to save on size.
Running 'ubuntu-bug ' will erroneously report that
the package is unsupported:
$ ubuntu-bug coreutils
*** Collecting problem information
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.
*** Problem in coreutils
The problem cannot be reported:
This is not an official Ubuntu package. Please remove any third
party package and try again.
A simpler recreate is:
$ python3 -c 'import
apport;print(apport.packaging.is_distro_package("coreutils"))'
False
$ sudo apt update -qq
All packages are up to date.
$ python3 -c 'import
apport;print(apport.packaging.is_distro_package("coreutils"))'
True
Desired result:
The message should instruct the user to run 'apt update' as root if
they think this is in error. That would improve usability and avoid
false reports about apport incorrectly flagging a package as
unsupported.
Additionally, if the user is root (and optionally if the set of
package candidates only contains a 'now' component)
self._cache.update(); self._cache.open() could be called to download
lists.
Alternatively it could just check to see if lists have been
downloaded.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1775219/+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 1775219] Re: incorrectly reports package as unsupported if apt cache is empty
Brian, the hack doesn't seem workable. Touching channel.ini would then
flag all images as being supported, which isn't true. It's unclear what
knock-on effects we would have touching this file (i.e. what other tools
see it and take different code-paths). The existence of the file
indicates that the image is a read-only system image, this is untrue for
minimal.
I would still like to see this resolved, even if that is just an
improvement in the error message suggesting 'apt-get update' and
retrying.
Hack details:
* packaging-apt-dpkg.py, is_distro_package(): If there is no origin and
/etc/system-image/channel.ini exists, assume the package is from a
read-only system image and accept it as distro package. With this we don't
need /var/lib/apt/lists/ indexes any more just to confirm the origin.
(LP: #1489410)
--
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/1775219
Title:
incorrectly reports package as unsupported if apt cache is empty
Status in apport package in Ubuntu:
New
Bug description:
Cloud images ship with empty /var/lib/apt/lists/ to save on size.
Running 'ubuntu-bug ' will erroneously report that
the package is unsupported:
$ ubuntu-bug coreutils
*** Collecting problem information
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.
*** Problem in coreutils
The problem cannot be reported:
This is not an official Ubuntu package. Please remove any third
party package and try again.
A simpler recreate is:
$ python3 -c 'import
apport;print(apport.packaging.is_distro_package("coreutils"))'
False
$ sudo apt update -qq
All packages are up to date.
$ python3 -c 'import
apport;print(apport.packaging.is_distro_package("coreutils"))'
True
Desired result:
The message should instruct the user to run 'apt update' as root if
they think this is in error. That would improve usability and avoid
false reports about apport incorrectly flagging a package as
unsupported.
Additionally, if the user is root (and optionally if the set of
package candidates only contains a 'now' component)
self._cache.update(); self._cache.open() could be called to download
lists.
Alternatively it could just check to see if lists have been
downloaded.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1775219/+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 1775219] Re: incorrectly reports package as unsupported if apt cache is empty
** Tags added: id-5b1fe4c2babaab7ab6fd5d37
--
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/1775219
Title:
incorrectly reports package as unsupported if apt cache is empty
Status in apport package in Ubuntu:
New
Bug description:
Cloud images ship with empty /var/lib/apt/lists/ to save on size.
Running 'ubuntu-bug ' will erroneously report that
the package is unsupported:
$ ubuntu-bug coreutils
*** Collecting problem information
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.
*** Problem in coreutils
The problem cannot be reported:
This is not an official Ubuntu package. Please remove any third
party package and try again.
A simpler recreate is:
$ python3 -c 'import
apport;print(apport.packaging.is_distro_package("coreutils"))'
False
$ sudo apt update -qq
All packages are up to date.
$ python3 -c 'import
apport;print(apport.packaging.is_distro_package("coreutils"))'
True
Desired result:
The message should instruct the user to run 'apt update' as root if
they think this is in error. That would improve usability and avoid
false reports about apport incorrectly flagging a package as
unsupported.
Additionally, if the user is root (and optionally if the set of
package candidates only contains a 'now' component)
self._cache.update(); self._cache.open() could be called to download
lists.
Alternatively it could just check to see if lists have been
downloaded.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1775219/+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 1775291] Re: 'df /dev/sda1' (rootfs) returns result for /dev on gce minimal images
** Also affects: coreutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1775291 Title: 'df /dev/sda1' (rootfs) returns result for /dev on gce minimal images Status in cloud-images: New Status in coreutils package in Ubuntu: New Bug description: On base images the root FS shows up as /dev/sda1 in mount and df output. For minimized images the root FS shows up in df output as /dev/root. Scripts that call 'df /dev/sda1' to get information about the root FS will instead match to /dev not / To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1775291/+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 1780316] [NEW] netcat-openbsd is in main but netcat-standard has a netcat dummy package
Public bug reported: For installations that don't have netcat-openbsd somewhere in the seed then any package/user that installs 'netcat' will get 'netcat-standard' from universe rather than 'netcat-openbsd' from main. (One example is the ubuntu-fan package that recommends netcat) Suggested action: * Remove the 'netcat' dummy package from the netcat-standard package * Add a 'netcat' dummy package to the netcat-openbsd package ** Affects: netcat (Ubuntu) Importance: Undecided Status: New ** Affects: netcat-openbsd (Ubuntu) Importance: Undecided Status: New ** Also affects: netcat (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu. https://bugs.launchpad.net/bugs/1780316 Title: netcat-openbsd is in main but netcat-standard has a netcat dummy package Status in netcat package in Ubuntu: New Status in netcat-openbsd package in Ubuntu: New Bug description: For installations that don't have netcat-openbsd somewhere in the seed then any package/user that installs 'netcat' will get 'netcat- standard' from universe rather than 'netcat-openbsd' from main. (One example is the ubuntu-fan package that recommends netcat) Suggested action: * Remove the 'netcat' dummy package from the netcat-standard package * Add a 'netcat' dummy package to the netcat-openbsd package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat/+bug/1780316/+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 1780316] Re: netcat-openbsd is in main but netcat-standard has a netcat dummy package
This issue crops up on the Bionic minimal cloud images which don't have netcat-openbsd installed by default (it is in the Xenial image). When docker.io is installed with recommends it pulls in netcat-standard (via ubuntu-fan). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu. https://bugs.launchpad.net/bugs/1780316 Title: netcat-openbsd is in main but netcat-standard has a netcat dummy package Status in netcat package in Ubuntu: New Status in netcat-openbsd package in Ubuntu: New Bug description: For installations that don't have netcat-openbsd somewhere in the seed then any package/user that installs 'netcat' will get 'netcat- standard' from universe rather than 'netcat-openbsd' from main. (One example is the ubuntu-fan package that recommends netcat) Suggested action: * Remove the 'netcat' dummy package from the netcat-standard package * Add a 'netcat' dummy package to the netcat-openbsd package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat/+bug/1780316/+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 1741563] [NEW] initramfs compression changed in bionic for shipped kernel
Public bug reported: The shipped initrd doesn't match the compression that you'd get if you update the initrd on bionic: # A clean bionic cloud-image $ file /boot/initrd.img-4.13.0-17-generic /boot/initrd.img-4.13.0-17-generic: LZMA compressed data, streamed # Update the initramfs (notice the deprecation warnings too) $ sudo update-initramfs -k all -u update-initramfs: Generating /boot/initrd.img-4.13.0-17-generic WARNING: Setting CRYPTSETUP in /etc/initramfs-tools/initramfs.conf is deprecated and will stop working in the future. Use /etc/cryptsetup-initramfs/conf-hook instead. # Now initramfs is gzip compressed when packaged initramfs was LZMA $ file /boot/initrd.img-4.13.0-17-generic /boot/initrd.img-4.13.0-17-generic: gzip compressed data, last modified: Fri Jan 5 20:54:07 2018, from Unix $ apt-cache policy initramfs-tools initramfs-tools: Installed: 0.125ubuntu13 Candidate: 0.125ubuntu13 Version table: *** 0.125ubuntu13 500 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: Incomplete -- 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/1741563 Title: initramfs compression changed in bionic for shipped kernel Status in initramfs-tools package in Ubuntu: Incomplete Bug description: The shipped initrd doesn't match the compression that you'd get if you update the initrd on bionic: # A clean bionic cloud-image $ file /boot/initrd.img-4.13.0-17-generic /boot/initrd.img-4.13.0-17-generic: LZMA compressed data, streamed # Update the initramfs (notice the deprecation warnings too) $ sudo update-initramfs -k all -u update-initramfs: Generating /boot/initrd.img-4.13.0-17-generic WARNING: Setting CRYPTSETUP in /etc/initramfs-tools/initramfs.conf is deprecated and will stop working in the future. Use /etc/cryptsetup-initramfs/conf-hook instead. # Now initramfs is gzip compressed when packaged initramfs was LZMA $ file /boot/initrd.img-4.13.0-17-generic /boot/initrd.img-4.13.0-17-generic: gzip compressed data, last modified: Fri Jan 5 20:54:07 2018, from Unix $ apt-cache policy initramfs-tools initramfs-tools: Installed: 0.125ubuntu13 Candidate: 0.125ubuntu13 Version table: *** 0.125ubuntu13 500 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1741563/+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 1741563] Re: initramfs compression changed in bionic for shipped kernel
Maybe it's this change in the linux source package: linux (4.11.0-1.6) artful; urgency=low * Miscellaneous Ubuntu changes - [Debian] Use default compression for all packages I'll check with the kernel team. But I thought if the kernel package was changing which compression was used then initramfs-tools should be updated to match what is there. -- 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/1741563 Title: initramfs compression changed in bionic for shipped kernel Status in initramfs-tools package in Ubuntu: Incomplete Bug description: The shipped initrd doesn't match the compression that you'd get if you update the initrd on bionic: # A clean bionic cloud-image $ file /boot/initrd.img-4.13.0-17-generic /boot/initrd.img-4.13.0-17-generic: LZMA compressed data, streamed # Update the initramfs (notice the deprecation warnings too) $ sudo update-initramfs -k all -u update-initramfs: Generating /boot/initrd.img-4.13.0-17-generic WARNING: Setting CRYPTSETUP in /etc/initramfs-tools/initramfs.conf is deprecated and will stop working in the future. Use /etc/cryptsetup-initramfs/conf-hook instead. # Now initramfs is gzip compressed when packaged initramfs was LZMA $ file /boot/initrd.img-4.13.0-17-generic /boot/initrd.img-4.13.0-17-generic: gzip compressed data, last modified: Fri Jan 5 20:54:07 2018, from Unix $ apt-cache policy initramfs-tools initramfs-tools: Installed: 0.125ubuntu13 Candidate: 0.125ubuntu13 Version table: *** 0.125ubuntu13 500 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1741563/+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 1741563] Re: initramfs compression changed in bionic for shipped kernel
My understanding had been incorrect and this is not an issue in this package at all. The initramfs present in the cloud-image at first boot is created by live-build with lzma compression. Subsequent kernel installs that produce a new initramfs or updates to an existing initramfs will be compressed with the default gzip compression per the shipped default in initramfs-tools. This mismatch is due to live-build invocation and not this package. Marking invalid. ** Changed in: initramfs-tools (Ubuntu) Status: Incomplete => Invalid -- 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/1741563 Title: initramfs compression changed in bionic for shipped kernel Status in initramfs-tools package in Ubuntu: Invalid Bug description: The shipped initrd doesn't match the compression that you'd get if you update the initrd on bionic: # A clean bionic cloud-image $ file /boot/initrd.img-4.13.0-17-generic /boot/initrd.img-4.13.0-17-generic: LZMA compressed data, streamed # Update the initramfs (notice the deprecation warnings too) $ sudo update-initramfs -k all -u update-initramfs: Generating /boot/initrd.img-4.13.0-17-generic WARNING: Setting CRYPTSETUP in /etc/initramfs-tools/initramfs.conf is deprecated and will stop working in the future. Use /etc/cryptsetup-initramfs/conf-hook instead. # Now initramfs is gzip compressed when packaged initramfs was LZMA $ file /boot/initrd.img-4.13.0-17-generic /boot/initrd.img-4.13.0-17-generic: gzip compressed data, last modified: Fri Jan 5 20:54:07 2018, from Unix $ apt-cache policy initramfs-tools initramfs-tools: Installed: 0.125ubuntu13 Candidate: 0.125ubuntu13 Version table: *** 0.125ubuntu13 500 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1741563/+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 1792189] Re: linux-firmware does not depend on initramfs-tools
** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid -- 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/1792189 Title: linux-firmware does not depend on initramfs-tools Status in initramfs-tools package in Ubuntu: Invalid Bug description: In bug #1646197 the linux-firmware.postinst was added to call update- initramfs (provided by initramfs-tools. If the initramfs-tools package is not installed the installation of linux-firmware will fail. Recreate: sudo apt-get purge --assume-yes '^linux-.*' 'linux-base+' initramfs* sudo apt-get install --assume-yes linux-generic Result: Setting up linux-modules-4.15.0-34-generic (4.15.0-34.37) ... Setting up linux-headers-4.15.0-34 (4.15.0-34.37) ... Setting up linux-headers-4.15.0-34-generic (4.15.0-34.37) ... Setting up initramfs-tools-bin (0.130ubuntu3.3) ... Setting up linux-firmware (1.173.1) ... update-initramfs: Generating /boot/initrd.img-4.15.0-1021-kvm /usr/sbin/mkinitramfs: 66: .: Can't open /etc/initramfs-tools/initramfs.conf update-initramfs: failed for /boot/initrd.img-4.15.0-1021-kvm with 2. dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 2 ... Errors were encountered while processing: linux-firmware linux-image-generic linux-generic E: Sub-process /usr/bin/dpkg returned an error code (1) Impact: Builds of minimized images start with an image that has the linux-kvm kernel but lack initramfs-tools. Derivative builds that require a different kernel, linux-generic for example, will purge the existing kernel and install the correct kernel which could pull in linux-firmware and initramfs-tools. In that case the builds fail unless initramfs-tools is installed prior to kernel installation as a workaround for this missing package dependency. This has been recreated on cosmic and bionic, a fix is desired on each. (I was unable to recreate on Xenial but that package lacks the dependency as well). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1792189/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
Action plan: Stage 1 - Configure lxc-net at boot rather than at install. * This addresses the network failure for 15.10 containers started on 15.10 hosts (patch above in comment #6) Stage 2 - Start lxc-net through systemd on the first launch of an LXC container. * This mitigates the unroutable 10.0.x.0/16 network issue for general cloud image users. With this step we’re back to Trusty function. * This will work for privileged users, like Juju, without any interaction. Unprivileged users will be directed to start the service on the first container launch. Next action: - serge-hallyn working on patch (last update in comment #7) and code in ppa:serge-hallyn/lxc-natty. Patch is not yet ready for upload and serge will update as he progresses. - Once ready, uploaded, and published in -proposed, email ring rcj/utlemming and we'll ensure cloud image builder picks this up ASAP to build -proposed images -- 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/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers Status in lxc package in Ubuntu: Confirmed Bug description: [Problem] The released wily image preinstalls lxc, which breaks the assumption that lxc's preinst packaging script makes: It inspects the network to try to pick a 10.0.N.0 network that isn't being used, with N starting at 3, so this appears to have picked 10.0.3.0 when it was installed on whatever system was generating the image. When a container is started, it will dhcp on eth0 and get 10.0.3.X as expected. The problem comes when the lxc-net service that is already installed in that container starts and configures *its* lxcbr0 with 10.0.3.X. The networking inside the container is broken at that point. This affects LXC containers, and should affect LXD containers but doesn't currently, as the metadata used for lxd images is still pointing to a beta2 release (bug 1509390). The easiest way to reproduce this is to use the ubuntu-cloud lxc template on a wily host. [Test Case] 1.) Verify expectation for each image - -disk1.img cloud image, check for file - -root.tar.xz image (used by lxd) and check for file - -root.tar.gz image (used by lxc) For each of those images, verify: a.) A cloud image should not have /etc/default/lxc-net b.) lxd should be installed (dpkg-query --show | grep lxd) 2.) Start instance from updated image and start instance in lxc inside launch instance on openstack or kvm or other verify lxcbr0 bridge exists lxc-create -t ubuntu-cloud -n bugcheck -- --release=wily --stream=daily # wait until lxc-ls --fancy shows 'running' lxc-attach -n bugcheck wget http://ubuntu.com 3.) Start instance from updated image and start instance in lxd inside launch instance on openstack or kvm or other verify lxcbr0 bridge exists lxd import-images ubuntu wily lxc launch ubuntu # wait some amount lxc attach bugcheck wget http://ubuntu.com [Regression Potentional] The highest chance for fallout is a change in the /16 network that is chosen conflicting with some existing service. [Other Info] Default apt install of lxc has always picked some 10.0.X.0/16 network to use for its lxcbr0 bridge. That network (often 10.0.3.0/16) would then be unreachable from the host. The same behavior occurs with libvirt-bin and many other such services. We are moving that logic to happen the first time that 'lxc-net' service starts. This means first boot for a cloud instance rather than cloud-image build time. [Work around] To patch / fix an existing cloud image to make lxc and lxd guests start simply change the config of /etc/default/lxc-net to have something other than 10.0.3.0. sudo sed -i '/^LXC.*10[.]0[.][0-9][.]/s/10.0.[0-9]./10.0.4./g' /etc/default/lxc-net && sudo service lxc-net stop && sudo service lxc-net start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
The cloud-image builder picked up the change and is building images. They are with the LP buildds now. I will update this bug once publication completes. -- 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/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers Status in lxc package in Ubuntu: Confirmed Bug description: [Problem] The released wily image preinstalls lxc, which breaks the assumption that lxc's preinst packaging script makes: It inspects the network to try to pick a 10.0.N.0 network that isn't being used, with N starting at 3, so this appears to have picked 10.0.3.0 when it was installed on whatever system was generating the image. When a container is started, it will dhcp on eth0 and get 10.0.3.X as expected. The problem comes when the lxc-net service that is already installed in that container starts and configures *its* lxcbr0 with 10.0.3.X. The networking inside the container is broken at that point. This affects LXC containers, and should affect LXD containers but doesn't currently, as the metadata used for lxd images is still pointing to a beta2 release (bug 1509390). The easiest way to reproduce this is to use the ubuntu-cloud lxc template on a wily host. [Test Case] 1.) Verify expectation for each image - -disk1.img cloud image, check for file - -root.tar.xz image (used by lxd) and check for file - -root.tar.gz image (used by lxc) For each of those images, verify: a.) A cloud image should not have /etc/default/lxc-net b.) lxd should be installed (dpkg-query --show | grep lxd) 2.) Start instance from updated image and start instance in lxc inside launch instance on openstack or kvm or other verify lxcbr0 bridge exists lxc-create -t ubuntu-cloud -n bugcheck -- --release=wily --stream=daily # wait until lxc-ls --fancy shows 'running' lxc-attach -n bugcheck wget http://ubuntu.com 3.) Start instance from updated image and start instance in lxd inside launch instance on openstack or kvm or other verify lxcbr0 bridge exists lxd import-images ubuntu wily lxc launch ubuntu # wait some amount lxc attach bugcheck wget http://ubuntu.com [Regression Potentional] The highest chance for fallout is a change in the /16 network that is chosen conflicting with some existing service. [Other Info] Default apt install of lxc has always picked some 10.0.X.0/16 network to use for its lxcbr0 bridge. That network (often 10.0.3.0/16) would then be unreachable from the host. The same behavior occurs with libvirt-bin and many other such services. We are moving that logic to happen the first time that 'lxc-net' service starts. This means first boot for a cloud instance rather than cloud-image build time. [Work around] To patch / fix an existing cloud image to make lxc and lxd guests start simply change the config of /etc/default/lxc-net to have something other than 10.0.3.0. sudo sed -i '/^LXC.*10[.]0[.][0-9][.]/s/10.0.[0-9]./10.0.4./g' /etc/default/lxc-net && sudo service lxc-net stop && sudo service lxc-net start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
Cloud image downloads for amd64, i386, and ppc64el are available @ http ://cloud-images.ubuntu.com/proposed/wily/20151024/ The amd64 image is also available in canonistack lcy02 region as lp1509414/wily-proposed -- 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/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers Status in lxc package in Ubuntu: Confirmed Bug description: [Problem] The released wily image preinstalls lxc, which breaks the assumption that lxc's preinst packaging script makes: It inspects the network to try to pick a 10.0.N.0 network that isn't being used, with N starting at 3, so this appears to have picked 10.0.3.0 when it was installed on whatever system was generating the image. When a container is started, it will dhcp on eth0 and get 10.0.3.X as expected. The problem comes when the lxc-net service that is already installed in that container starts and configures *its* lxcbr0 with 10.0.3.X. The networking inside the container is broken at that point. This affects LXC containers, and should affect LXD containers but doesn't currently, as the metadata used for lxd images is still pointing to a beta2 release (bug 1509390). The easiest way to reproduce this is to use the ubuntu-cloud lxc template on a wily host. [Test Case] 1.) Verify expectation for each image - -disk1.img cloud image, check for file - -root.tar.xz image (used by lxd) and check for file - -root.tar.gz image (used by lxc) For each of those images, verify: a.) A cloud image should not have /etc/default/lxc-net b.) lxd should be installed (dpkg-query --show | grep lxd) 2.) Start instance from updated image and start instance in lxc inside launch instance on openstack or kvm or other verify lxcbr0 bridge exists lxc-create -t ubuntu-cloud -n bugcheck -- --release=wily --stream=daily # wait until lxc-ls --fancy shows 'running' lxc-attach -n bugcheck wget http://ubuntu.com 3.) Start instance from updated image and start instance in lxd inside launch instance on openstack or kvm or other verify lxcbr0 bridge exists lxd import-images ubuntu wily lxc launch ubuntu # wait some amount lxc attach bugcheck wget http://ubuntu.com [Regression Potentional] The highest chance for fallout is a change in the /16 network that is chosen conflicting with some existing service. [Other Info] Default apt install of lxc has always picked some 10.0.X.0/16 network to use for its lxcbr0 bridge. That network (often 10.0.3.0/16) would then be unreachable from the host. The same behavior occurs with libvirt-bin and many other such services. We are moving that logic to happen the first time that 'lxc-net' service starts. This means first boot for a cloud instance rather than cloud-image build time. [Work around] To patch / fix an existing cloud image to make lxc and lxd guests start simply change the config of /etc/default/lxc-net to have something other than 10.0.3.0. sudo sed -i '/^LXC.*10[.]0[.][0-9][.]/s/10.0.[0-9]./10.0.4./g' /etc/default/lxc-net && sudo service lxc-net stop && sudo service lxc-net start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
Cloud images build from proposed are available. Next action: - Verification of proposed package. -- 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/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers Status in lxc package in Ubuntu: Confirmed Bug description: [Problem] The released wily image preinstalls lxc, which breaks the assumption that lxc's preinst packaging script makes: It inspects the network to try to pick a 10.0.N.0 network that isn't being used, with N starting at 3, so this appears to have picked 10.0.3.0 when it was installed on whatever system was generating the image. When a container is started, it will dhcp on eth0 and get 10.0.3.X as expected. The problem comes when the lxc-net service that is already installed in that container starts and configures *its* lxcbr0 with 10.0.3.X. The networking inside the container is broken at that point. This affects LXC containers, and should affect LXD containers but doesn't currently, as the metadata used for lxd images is still pointing to a beta2 release (bug 1509390). The easiest way to reproduce this is to use the ubuntu-cloud lxc template on a wily host. [Test Case] 1.) Verify expectation for each image - -disk1.img cloud image, check for file - -root.tar.xz image (used by lxd) and check for file - -root.tar.gz image (used by lxc) For each of those images, verify: a.) A cloud image should not have /etc/default/lxc-net b.) lxd should be installed (dpkg-query --show | grep lxd) 2.) Start instance from updated image and start instance in lxc inside launch instance on openstack or kvm or other verify lxcbr0 bridge exists lxc-create -t ubuntu-cloud -n bugcheck -- --release=wily --stream=daily # wait until lxc-ls --fancy shows 'running' lxc-attach -n bugcheck wget http://ubuntu.com 3.) Start instance from updated image and start instance in lxd inside launch instance on openstack or kvm or other verify lxcbr0 bridge exists lxd import-images ubuntu wily lxc launch ubuntu # wait some amount lxc attach bugcheck wget http://ubuntu.com [Regression Potentional] The highest chance for fallout is a change in the /16 network that is chosen conflicting with some existing service. [Other Info] Default apt install of lxc has always picked some 10.0.X.0/16 network to use for its lxcbr0 bridge. That network (often 10.0.3.0/16) would then be unreachable from the host. The same behavior occurs with libvirt-bin and many other such services. We are moving that logic to happen the first time that 'lxc-net' service starts. This means first boot for a cloud instance rather than cloud-image build time. [Work around] To patch / fix an existing cloud image to make lxc and lxd guests start simply change the config of /etc/default/lxc-net to have something other than 10.0.3.0. sudo sed -i '/^LXC.*10[.]0[.][0-9][.]/s/10.0.[0-9]./10.0.4./g' /etc/default/lxc-net && sudo service lxc-net stop && sudo service lxc-net start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
Cloud images build from proposed are available. Next action: -- 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/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers Status in lxc package in Ubuntu: Confirmed Bug description: [Problem] The released wily image preinstalls lxc, which breaks the assumption that lxc's preinst packaging script makes: It inspects the network to try to pick a 10.0.N.0 network that isn't being used, with N starting at 3, so this appears to have picked 10.0.3.0 when it was installed on whatever system was generating the image. When a container is started, it will dhcp on eth0 and get 10.0.3.X as expected. The problem comes when the lxc-net service that is already installed in that container starts and configures *its* lxcbr0 with 10.0.3.X. The networking inside the container is broken at that point. This affects LXC containers, and should affect LXD containers but doesn't currently, as the metadata used for lxd images is still pointing to a beta2 release (bug 1509390). The easiest way to reproduce this is to use the ubuntu-cloud lxc template on a wily host. [Test Case] 1.) Verify expectation for each image - -disk1.img cloud image, check for file - -root.tar.xz image (used by lxd) and check for file - -root.tar.gz image (used by lxc) For each of those images, verify: a.) A cloud image should not have /etc/default/lxc-net b.) lxd should be installed (dpkg-query --show | grep lxd) 2.) Start instance from updated image and start instance in lxc inside launch instance on openstack or kvm or other verify lxcbr0 bridge exists lxc-create -t ubuntu-cloud -n bugcheck -- --release=wily --stream=daily # wait until lxc-ls --fancy shows 'running' lxc-attach -n bugcheck wget http://ubuntu.com 3.) Start instance from updated image and start instance in lxd inside launch instance on openstack or kvm or other verify lxcbr0 bridge exists lxd import-images ubuntu wily lxc launch ubuntu # wait some amount lxc attach bugcheck wget http://ubuntu.com [Regression Potentional] The highest chance for fallout is a change in the /16 network that is chosen conflicting with some existing service. [Other Info] Default apt install of lxc has always picked some 10.0.X.0/16 network to use for its lxcbr0 bridge. That network (often 10.0.3.0/16) would then be unreachable from the host. The same behavior occurs with libvirt-bin and many other such services. We are moving that logic to happen the first time that 'lxc-net' service starts. This means first boot for a cloud instance rather than cloud-image build time. [Work around] To patch / fix an existing cloud image to make lxc and lxd guests start simply change the config of /etc/default/lxc-net to have something other than 10.0.3.0. sudo sed -i '/^LXC.*10[.]0[.][0-9][.]/s/10.0.[0-9]./10.0.4./g' /etc/default/lxc-net && sudo service lxc-net stop && sudo service lxc-net start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
Be aware in your testing that the lxd-net's service can come up slowly depending on the speed of your cloud instance. Without the bridge (lxcbr0) the container's networking will function prior to that service starting; watch out for this false positive in your testing. -- 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/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers Status in lxc package in Ubuntu: Confirmed Bug description: [Problem] The released wily image preinstalls lxc, which breaks the assumption that lxc's preinst packaging script makes: It inspects the network to try to pick a 10.0.N.0 network that isn't being used, with N starting at 3, so this appears to have picked 10.0.3.0 when it was installed on whatever system was generating the image. When a container is started, it will dhcp on eth0 and get 10.0.3.X as expected. The problem comes when the lxc-net service that is already installed in that container starts and configures *its* lxcbr0 with 10.0.3.X. The networking inside the container is broken at that point. This affects LXC containers, and should affect LXD containers but doesn't currently, as the metadata used for lxd images is still pointing to a beta2 release (bug 1509390). The easiest way to reproduce this is to use the ubuntu-cloud lxc template on a wily host. [Test Case] 1.) Verify expectation for each image - -disk1.img cloud image, check for file - -root.tar.xz image (used by lxd) and check for file - -root.tar.gz image (used by lxc) For each of those images, verify: a.) A cloud image should not have /etc/default/lxc-net b.) lxd should be installed (dpkg-query --show | grep lxd) 2.) Start instance from updated image and start instance in lxc inside launch instance on openstack or kvm or other verify lxcbr0 bridge exists lxc-create -t ubuntu-cloud -n bugcheck -- --release=wily --stream=daily # wait until lxc-ls --fancy shows 'running' lxc-attach -n bugcheck wget http://ubuntu.com 3.) Start instance from updated image and start instance in lxd inside launch instance on openstack or kvm or other verify lxcbr0 bridge exists lxd import-images ubuntu wily lxc launch ubuntu # wait some amount lxc attach bugcheck wget http://ubuntu.com [Regression Potentional] The highest chance for fallout is a change in the /16 network that is chosen conflicting with some existing service. [Other Info] Default apt install of lxc has always picked some 10.0.X.0/16 network to use for its lxcbr0 bridge. That network (often 10.0.3.0/16) would then be unreachable from the host. The same behavior occurs with libvirt-bin and many other such services. We are moving that logic to happen the first time that 'lxc-net' service starts. This means first boot for a cloud instance rather than cloud-image build time. [Work around] To patch / fix an existing cloud image to make lxc and lxd guests start simply change the config of /etc/default/lxc-net to have something other than 10.0.3.0. sudo sed -i '/^LXC.*10[.]0[.][0-9][.]/s/10.0.[0-9]./10.0.4./g' /etc/default/lxc-net && sudo service lxc-net stop && sudo service lxc-net start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
My testing with the cloud image containing the proposed package has been successful. Just a note again that the test case detailed in the description is fine with the understanding that network testing needs to ensure the lxc-net service has started lxcbr0 or a false positive is possible (per comment #18). -- 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/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers Status in lxc package in Ubuntu: Confirmed Bug description: [Problem] The released wily image preinstalls lxc, which breaks the assumption that lxc's preinst packaging script makes: It inspects the network to try to pick a 10.0.N.0 network that isn't being used, with N starting at 3, so this appears to have picked 10.0.3.0 when it was installed on whatever system was generating the image. When a container is started, it will dhcp on eth0 and get 10.0.3.X as expected. The problem comes when the lxc-net service that is already installed in that container starts and configures *its* lxcbr0 with 10.0.3.X. The networking inside the container is broken at that point. This affects LXC containers, and should affect LXD containers but doesn't currently, as the metadata used for lxd images is still pointing to a beta2 release (bug 1509390). The easiest way to reproduce this is to use the ubuntu-cloud lxc template on a wily host. [Test Case] 1.) Verify expectation for each image - -disk1.img cloud image, check for file - -root.tar.xz image (used by lxd) and check for file - -root.tar.gz image (used by lxc) For each of those images, verify: a.) A cloud image should not have /etc/default/lxc-net b.) lxd should be installed (dpkg-query --show | grep lxd) 2.) Start instance from updated image and start instance in lxc inside launch instance on openstack or kvm or other verify lxcbr0 bridge exists lxc-create -t ubuntu-cloud -n bugcheck -- --release=wily --stream=daily # wait until lxc-ls --fancy shows 'running' lxc-attach -n bugcheck wget http://ubuntu.com 3.) Start instance from updated image and start instance in lxd inside launch instance on openstack or kvm or other verify lxcbr0 bridge exists lxd import-images ubuntu wily lxc launch ubuntu # wait some amount lxc attach bugcheck wget http://ubuntu.com [Regression Potentional] The highest chance for fallout is a change in the /16 network that is chosen conflicting with some existing service. [Other Info] Default apt install of lxc has always picked some 10.0.X.0/16 network to use for its lxcbr0 bridge. That network (often 10.0.3.0/16) would then be unreachable from the host. The same behavior occurs with libvirt-bin and many other such services. We are moving that logic to happen the first time that 'lxc-net' service starts. This means first boot for a cloud instance rather than cloud-image build time. [Work around] To patch / fix an existing cloud image to make lxc and lxd guests start simply change the config of /etc/default/lxc-net to have something other than 10.0.3.0. sudo sed -i '/^LXC.*10[.]0[.][0-9][.]/s/10.0.[0-9]./10.0.4./g' /etc/default/lxc-net && sudo service lxc-net stop && sudo service lxc-net start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
Séphane, When this was added to the cloud seed we changed this from "users that install LXC will loose connectivity to a 10.0.x.0/24 network" to "all cloud users do not have connectivity to a 10.0.x.0/24 network at boot" and the cause/effect will not be as clear to an end user. This had come up in conversation but had not been documented in the bug. So let us continue to search for a solution like what you have outlined in the last paragraph of comment #29. -- 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/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers Status in lxc package in Ubuntu: Confirmed Bug description: [Problem] The released wily image preinstalls lxc, which breaks the assumption that lxc's preinst packaging script makes: It inspects the network to try to pick a 10.0.N.0 network that isn't being used, with N starting at 3, so this appears to have picked 10.0.3.0 when it was installed on whatever system was generating the image. When a container is started, it will dhcp on eth0 and get 10.0.3.X as expected. The problem comes when the lxc-net service that is already installed in that container starts and configures *its* lxcbr0 with 10.0.3.X. The networking inside the container is broken at that point. This affects LXC containers, and should affect LXD containers but doesn't currently, as the metadata used for lxd images is still pointing to a beta2 release (bug 1509390). The easiest way to reproduce this is to use the ubuntu-cloud lxc template on a wily host. [Test Case] 1.) Verify expectation for each image - -disk1.img cloud image, check for file - -root.tar.xz image (used by lxd) and check for file - -root.tar.gz image (used by lxc) For each of those images, verify: a.) A cloud image should not have /etc/default/lxc-net b.) lxd should be installed (dpkg-query --show | grep lxd) 2.) Start instance from updated image and start instance in lxc inside launch instance on openstack or kvm or other verify lxcbr0 bridge exists lxc-create -t ubuntu-cloud -n bugcheck -- --release=wily --stream=daily # wait until lxc-ls --fancy shows 'running' lxc-attach -n bugcheck wget http://ubuntu.com 3.) Start instance from updated image and start instance in lxd inside launch instance on openstack or kvm or other verify lxcbr0 bridge exists lxd import-images ubuntu wily lxc launch ubuntu # wait some amount lxc attach bugcheck wget http://ubuntu.com [Regression Potentional] The highest chance for fallout is a change in the /16 network that is chosen conflicting with some existing service. [Other Info] Default apt install of lxc has always picked some 10.0.X.0/16 network to use for its lxcbr0 bridge. That network (often 10.0.3.0/16) would then be unreachable from the host. The same behavior occurs with libvirt-bin and many other such services. We are moving that logic to happen the first time that 'lxc-net' service starts. This means first boot for a cloud instance rather than cloud-image build time. [Work around] To patch / fix an existing cloud image to make lxc and lxd guests start simply change the config of /etc/default/lxc-net to have something other than 10.0.3.0. sudo sed -i '/^LXC.*10[.]0[.][0-9][.]/s/10.0.[0-9]./10.0.4./g' /etc/default/lxc-net && sudo service lxc-net stop && sudo service lxc-net start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
I agree that this shuffling around is not pretty, but we need a solution that makes 10.0.0.0/16 routable in cloud images where lxc/lxd are not in use as had prior to http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/ubuntu.wily/revision/2360 The current situation conflicts with how clouds are instructing users to set up private networks. [1] [2] [1] http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Subnets.html [2] https://azure.microsoft.com/en-us/documentation/articles/virtual-networks-reserved-private-ip/ -- 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/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers Status in lxc package in Ubuntu: Confirmed Bug description: [Problem] The released wily image preinstalls lxc, which breaks the assumption that lxc's preinst packaging script makes: It inspects the network to try to pick a 10.0.N.0 network that isn't being used, with N starting at 3, so this appears to have picked 10.0.3.0 when it was installed on whatever system was generating the image. When a container is started, it will dhcp on eth0 and get 10.0.3.X as expected. The problem comes when the lxc-net service that is already installed in that container starts and configures *its* lxcbr0 with 10.0.3.X. The networking inside the container is broken at that point. This affects LXC containers, and should affect LXD containers but doesn't currently, as the metadata used for lxd images is still pointing to a beta2 release (bug 1509390). The easiest way to reproduce this is to use the ubuntu-cloud lxc template on a wily host. [Test Case] 1.) Verify expectation for each image - -disk1.img cloud image, check for file - -root.tar.xz image (used by lxd) and check for file - -root.tar.gz image (used by lxc) For each of those images, verify: a.) A cloud image should not have /etc/default/lxc-net b.) lxd should be installed (dpkg-query --show | grep lxd) 2.) Start instance from updated image and start instance in lxc inside launch instance on openstack or kvm or other verify lxcbr0 bridge exists lxc-create -t ubuntu-cloud -n bugcheck -- --release=wily --stream=daily # wait until lxc-ls --fancy shows 'running' lxc-attach -n bugcheck wget http://ubuntu.com 3.) Start instance from updated image and start instance in lxd inside launch instance on openstack or kvm or other verify lxcbr0 bridge exists lxd import-images ubuntu wily lxc launch ubuntu # wait some amount lxc attach bugcheck wget http://ubuntu.com [Regression Potentional] The highest chance for fallout is a change in the /16 network that is chosen conflicting with some existing service. [Other Info] Default apt install of lxc has always picked some 10.0.X.0/16 network to use for its lxcbr0 bridge. That network (often 10.0.3.0/16) would then be unreachable from the host. The same behavior occurs with libvirt-bin and many other such services. We are moving that logic to happen the first time that 'lxc-net' service starts. This means first boot for a cloud instance rather than cloud-image build time. [Work around] To patch / fix an existing cloud image to make lxc and lxd guests start simply change the config of /etc/default/lxc-net to have something other than 10.0.3.0. sudo sed -i '/^LXC.*10[.]0[.][0-9][.]/s/10.0.[0-9]./10.0.4./g' /etc/default/lxc-net && sudo service lxc-net stop && sudo service lxc-net start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1501456] [NEW] pytz.country_names UnicodeDecodeError exception
Public bug reported:
Wily:
# python3 -c 'from pytz import country_names
for item in country_names.items():
print(item)'
Traceback (most recent call last):
File "", line 2, in
File "/usr/lib/python3.4/_collections_abc.py", line 497, in __iter__
for key in self._mapping:
File "/usr/lib/python3/dist-packages/pytz/lazy.py", line 41, in __iter__
self._fill()
File "/usr/lib/python3/dist-packages/pytz/__init__.py", line 350, in _fill
line = line.decode('US-ASCII')
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 3: ordinal
not in range(128)
# python -c 'from pytz import country_names
print(country_names)'
Traceback (most recent call last):
File "", line 2, in
File "/usr/lib/python2.7/UserDict.py", line 172, in __repr__
return repr(dict(self.iteritems()))
File "/usr/lib/python2.7/UserDict.py", line 110, in iteritems
for k in self:
File "/usr/lib/python2.7/dist-packages/pytz/lazy.py", line 41, in __iter__
self._fill()
File "/usr/lib/python2.7/dist-packages/pytz/__init__.py", line 350, in _fill
line = line.decode('US-ASCII')
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 3: ordinal
not in range(128)
# dpkg-query -l python-tz python3-tz tzdata
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==---=
ii python-tz 2014.10~dfsg all Python version of the Olson timez
ii python3-tz 2014.10~dfsg all Python3 version of the Olson time
ii tzdata 2015f-1 all time zone and daylight-saving tim
Also affect trusty and vivid in the same way. Testing on trusty shows that
this broke with the release of tzdata=2015f-0ubuntu0.14.04, prior to that
tzdata version country_names could parse the data. debdiff shows that
tzdata=2015f-0ubuntu0.14.04 changes this file, and others to utf-8 from ascii.
** Affects: python-tz (Ubuntu)
Importance: Undecided
Status: New
** Affects: tzdata (Ubuntu)
Importance: Undecided
Status: New
** Also affects: tzdata (Ubuntu)
Importance: Undecided
Status: New
--
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/1501456
Title:
pytz.country_names UnicodeDecodeError exception
Status in python-tz package in Ubuntu:
New
Status in tzdata package in Ubuntu:
New
Bug description:
Wily:
# python3 -c 'from pytz import country_names
for item in country_names.items():
print(item)'
Traceback (most recent call last):
File "", line 2, in
File "/usr/lib/python3.4/_collections_abc.py", line 497, in __iter__
for key in self._mapping:
File "/usr/lib/python3/dist-packages/pytz/lazy.py", line 41, in __iter__
self._fill()
File "/usr/lib/python3/dist-packages/pytz/__init__.py", line 350, in _fill
line = line.decode('US-ASCII')
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 3:
ordinal not in range(128)
# python -c 'from pytz import country_names
print(country_names)'
Traceback (most recent call last):
File "", line 2, in
File "/usr/lib/python2.7/UserDict.py", line 172, in __repr__
return repr(dict(self.iteritems()))
File "/usr/lib/python2.7/UserDict.py", line 110, in iteritems
for k in self:
File "/usr/lib/python2.7/dist-packages/pytz/lazy.py", line 41, in __iter__
self._fill()
File "/usr/lib/python2.7/dist-packages/pytz/__init__.py", line 350, in _fill
line = line.decode('US-ASCII')
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 3:
ordinal not in range(128)
# dpkg-query -l python-tz python3-tz tzdata
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==---=
ii python-tz 2014.10~dfsg all Python version of the Olson timez
ii python3-tz 2014.10~dfsg all Python3 version of the Olson time
ii tzdata 2015f-1 all time zone and daylight-saving tim
Also affect trusty and vivid in the same way. Testing on trusty shows that
this broke with the release of tzdata=2015f-0ubuntu0.14.04, prior to that
tzdata version country_names could parse the data. debdiff shows that
tzdata=2015f-0ubuntu0.14.04 changes this file, and others to utf-8 from ascii.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/1501456/+subscriptions
--
Mailing list: https://lau
[Touch-packages] [Bug 1501456] Re: pytz.country_names UnicodeDecodeError exception
*** This bug is a duplicate of bug 1473533 ***
https://bugs.launchpad.net/bugs/1473533
drat, wrong bug. I meant to put that in bug #1473533
** No longer affects: tzdata (Ubuntu)
** This bug has been marked a duplicate of bug 1473533
CountryNameDict function trying to parse UTF-8 iso3166.tab as US-ASCII
--
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/1501456
Title:
pytz.country_names UnicodeDecodeError exception
Status in python-tz package in Ubuntu:
Confirmed
Bug description:
Wily:
# python3 -c 'from pytz import country_names
for item in country_names.items():
print(item)'
Traceback (most recent call last):
File "", line 2, in
File "/usr/lib/python3.4/_collections_abc.py", line 497, in __iter__
for key in self._mapping:
File "/usr/lib/python3/dist-packages/pytz/lazy.py", line 41, in __iter__
self._fill()
File "/usr/lib/python3/dist-packages/pytz/__init__.py", line 350, in _fill
line = line.decode('US-ASCII')
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 3:
ordinal not in range(128)
# python -c 'from pytz import country_names
print(country_names)'
Traceback (most recent call last):
File "", line 2, in
File "/usr/lib/python2.7/UserDict.py", line 172, in __repr__
return repr(dict(self.iteritems()))
File "/usr/lib/python2.7/UserDict.py", line 110, in iteritems
for k in self:
File "/usr/lib/python2.7/dist-packages/pytz/lazy.py", line 41, in __iter__
self._fill()
File "/usr/lib/python2.7/dist-packages/pytz/__init__.py", line 350, in _fill
line = line.decode('US-ASCII')
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 3:
ordinal not in range(128)
# dpkg-query -l python-tz python3-tz tzdata
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==---=
ii python-tz 2014.10~dfsg all Python version of the Olson timez
ii python3-tz 2014.10~dfsg all Python3 version of the Olson time
ii tzdata 2015f-1 all time zone and daylight-saving tim
Also affect trusty and vivid in the same way. Testing on trusty shows that
this broke with the release of tzdata=2015f-0ubuntu0.14.04, prior to that
tzdata version country_names could parse the data. debdiff shows that
tzdata=2015f-0ubuntu0.14.04 changes this file, and others to utf-8 from ascii.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/1501456/+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 1501456] Re: pytz.country_names UnicodeDecodeError exception
*** This bug is a duplicate of bug 1473533 ***
https://bugs.launchpad.net/bugs/1473533
This affects precise, trusty, and vivid. Please backport this low-risk
fix for those releases. Thank you.
--
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/1501456
Title:
pytz.country_names UnicodeDecodeError exception
Status in python-tz package in Ubuntu:
Confirmed
Bug description:
Wily:
# python3 -c 'from pytz import country_names
for item in country_names.items():
print(item)'
Traceback (most recent call last):
File "", line 2, in
File "/usr/lib/python3.4/_collections_abc.py", line 497, in __iter__
for key in self._mapping:
File "/usr/lib/python3/dist-packages/pytz/lazy.py", line 41, in __iter__
self._fill()
File "/usr/lib/python3/dist-packages/pytz/__init__.py", line 350, in _fill
line = line.decode('US-ASCII')
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 3:
ordinal not in range(128)
# python -c 'from pytz import country_names
print(country_names)'
Traceback (most recent call last):
File "", line 2, in
File "/usr/lib/python2.7/UserDict.py", line 172, in __repr__
return repr(dict(self.iteritems()))
File "/usr/lib/python2.7/UserDict.py", line 110, in iteritems
for k in self:
File "/usr/lib/python2.7/dist-packages/pytz/lazy.py", line 41, in __iter__
self._fill()
File "/usr/lib/python2.7/dist-packages/pytz/__init__.py", line 350, in _fill
line = line.decode('US-ASCII')
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 3:
ordinal not in range(128)
# dpkg-query -l python-tz python3-tz tzdata
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==---=
ii python-tz 2014.10~dfsg all Python version of the Olson timez
ii python3-tz 2014.10~dfsg all Python3 version of the Olson time
ii tzdata 2015f-1 all time zone and daylight-saving tim
Also affect trusty and vivid in the same way. Testing on trusty shows that
this broke with the release of tzdata=2015f-0ubuntu0.14.04, prior to that
tzdata version country_names could parse the data. debdiff shows that
tzdata=2015f-0ubuntu0.14.04 changes this file, and others to utf-8 from ascii.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/1501456/+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 1468091] Re: Ubuntu 15.10 Alpha-1 candidates do not boot in EC2
Last good test for EC2 occurred on June 9th with serial 20150608 https://jerff.canonical.com/job/NG_Test-EC2/376/ Ben is trying out: wily server daily 20150608ebs-ssd amd64 us-east-1 ami-6f9e7404hvm -- 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/1468091 Title: Ubuntu 15.10 Alpha-1 candidates do not boot in EC2 Status in systemd package in Ubuntu: Confirmed Bug description: Ubuntu 15.10 Alpha-1 Candidates are not booting in EC2. Instances are dropping to - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/disk/by-uuid/e420d299-69ee-46eb-a1a4-893b54ab89a7 does not exist. Dropping to a shell! This is happening on all instances and whether disks are mounted by label or UUID. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1468091/+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 1468091] Re: Ubuntu 15.10 Alpha-1 candidates do not boot in EC2
So the it's just udev and systemd changes here. utlemming took the working 20150608 ami, booted, upgraded, and rebooted and the instance didn't survive the reboot. This affects HVM only, PV is unaffected. -- 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/1468091 Title: Ubuntu 15.10 Alpha-1 candidates do not boot in EC2 Status in systemd package in Ubuntu: Confirmed Bug description: Ubuntu 15.10 Alpha-1 Candidates are not booting in EC2. Instances are dropping to - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/disk/by-uuid/e420d299-69ee-46eb-a1a4-893b54ab89a7 does not exist. Dropping to a shell! This is happening on all instances and whether disks are mounted by label or UUID. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1468091/+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 1468091] Re: Ubuntu 15.10 Alpha-1 candidates do not boot in EC2
Here are the package changes between the last working and first failing builds: 20150608 good 20150610 bad $ diff manifest-amd64-daily-20150608.txt manifest-amd64-daily-20150610.txt 101c101 < iso-codes 3.57-1 --- > iso-codes 3.58-1 248c248 < libpam-systemd:amd64 219-10ubuntu1 --- > libpam-systemd:amd64 220-5ubuntu2 296c296 < libsystemd0:amd64 219-10ubuntu1 --- > libsystemd0:amd64 220-5ubuntu2 306c306 < libudev1:amd64 219-10ubuntu1 --- > libudev1:amd64 220-5ubuntu2 458,459c458,459 < systemd 219-10ubuntu1 < systemd-sysv 219-10ubuntu1 --- > systemd 220-5ubuntu2 > systemd-sysv 220-5ubuntu2 476c476 < udev 219-10ubuntu1 --- > udev 220-5ubuntu2 -- 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/1468091 Title: Ubuntu 15.10 Alpha-1 candidates do not boot in EC2 Status in systemd package in Ubuntu: Confirmed Bug description: Ubuntu 15.10 Alpha-1 Candidates are not booting in EC2. Instances are dropping to - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/disk/by-uuid/e420d299-69ee-46eb-a1a4-893b54ab89a7 does not exist. Dropping to a shell! This is happening on all instances and whether disks are mounted by label or UUID. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1468091/+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 1724623] [NEW] Update ubuntu cloud info
Public bug reported: add_cloud_info() in data/general-hooks/ubuntu.py needs an overhaul. Issues: - Using the presence of cloud-init to flag an image as a cloud image is incorrect now that ubuntu-server includes cloud-init (and ubuntu-core images) - Using the presence of EC2 metadata source is incorrect as many non-EC2 clouds provide EC2 metadata. Thus we have bugs like bug #1722946 that are tagged as an 'ec2-images' bug which are clearly on openstack - Marking all bugs that have cloud-init but no EC2 metadata source as an 'uec-images' bug uses a name that no longer has meaning. Solution: - If cloud-init is present, check for /etc/cloud/build.info to indicate an Ubuntu cloud images, tag as 'cloud-images'. Pull the build_name and serial from that file into the bug comments. - If cloud-init is present, check for the presence of /run/cloud-init/cloud.cfg. Parse this yaml to determine the datasource type. Add the datasource used to the bug comment. I have filed bug #1724626 to ask cloud-init development to surface more information from ds-identify to help ID the cloud so that we can better tag/annotate the bug. There may also be some info we can get to indicate the image ID on more clouds than just AWS. At a minimum I would like to see dsidentify make the EC2 platform it found available for consumers in cloud.cfg. This would allow us to identify AWS EC2 from look-alike datasources so that we can tag a bug as ec2-images for bug really on AWS and add EC2 specific fields to the description/attachments. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: cloud-images ** Description changed: add_cloud_info() in data/general-hooks/ubuntu.py needs an overhaul. Issues: - - Using the presence of cloud-init to flag an image as a cloud image is incorrect now that ubuntu-server includes cloud-init (and ubuntu-core images) - - Using the presence of EC2 metadata source is incorrect as many non-EC2 clouds provide EC2 metadata. Thus we have bugs like bug #1722946 that are tagged as an 'ec2-images' bug which are clearly on openstack - - Marking all bugs that have cloud-init but no EC2 metadata source as an 'uec-images' bug uses a name that no longer has meaning. + - Using the presence of cloud-init to flag an image as a cloud image is incorrect now that ubuntu-server includes cloud-init (and ubuntu-core images) + - Using the presence of EC2 metadata source is incorrect as many non-EC2 clouds provide EC2 metadata. Thus we have bugs like bug #1722946 that are tagged as an 'ec2-images' bug which are clearly on openstack + - Marking all bugs that have cloud-init but no EC2 metadata source as an 'uec-images' bug uses a name that no longer has meaning. Solution: - - If cloud-init is present, check for /etc/cloud/build.info to indicate an Ubuntu cloud images, tag as 'cloud-images'. Pull the build_name and serial from that file into the bug comments. - - If cloud-init is present, check for the presence of /run/cloud-init/cloud.cfg. Parse this yaml to determine the datasource type. Add the datasource used to the bug comment. + - If cloud-init is present, check for /etc/cloud/build.info to indicate an Ubuntu cloud images, tag as 'cloud-images'. Pull the build_name and serial from that file into the bug comments. + - If cloud-init is present, check for the presence of /run/cloud-init/cloud.cfg. Parse this yaml to determine the datasource type. Add the datasource used to the bug comment. - We should also ask cloud-init development to surface more information - from ds-identify to help ID the cloud so that we can better tag/annotate - the bug. There may also be some info we can get to indicate the image - ID on more clouds than just AWS. At a minimum I would like to see - dsidentify make the EC2 platform it found available for consumers in - cloud.cfg. This would allow us to identify AWS EC2 from look-alike - datasources so that we can tag a bug as ec2-images for bug really on AWS - and add EC2 specific fields to the description/attachments. + I have filed bug #1724626 to ask cloud-init development to surface more + information from ds-identify to help ID the cloud so that we can better + tag/annotate the bug. There may also be some info we can get to + indicate the image ID on more clouds than just AWS. At a minimum I + would like to see dsidentify make the EC2 platform it found available + for consumers in cloud.cfg. This would allow us to identify AWS EC2 + from look-alike datasources so that we can tag a bug as ec2-images for + bug really on AWS and add EC2 specific fields to the + description/attachments. -- 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/1724623 Title: Update ubuntu cloud info Status in apport package in Ubuntu: New Bug description: add_cloud_info() in data/general-hooks/ubunt
[Touch-packages] [Bug 1724623] Re: Update ubuntu cloud info
** Tags added: cloud-images -- 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/1724623 Title: Update ubuntu cloud info Status in apport package in Ubuntu: New Bug description: add_cloud_info() in data/general-hooks/ubuntu.py needs an overhaul. Issues: - Using the presence of cloud-init to flag an image as a cloud image is incorrect now that ubuntu-server includes cloud-init (and ubuntu-core images) - Using the presence of EC2 metadata source is incorrect as many non-EC2 clouds provide EC2 metadata. Thus we have bugs like bug #1722946 that are tagged as an 'ec2-images' bug which are clearly on openstack - Marking all bugs that have cloud-init but no EC2 metadata source as an 'uec-images' bug uses a name that no longer has meaning. Solution: - If cloud-init is present, check for /etc/cloud/build.info to indicate an Ubuntu cloud images, tag as 'cloud-images'. Pull the build_name and serial from that file into the bug comments. - If cloud-init is present, check for the presence of /run/cloud-init/cloud.cfg. Parse this yaml to determine the datasource type. Add the datasource used to the bug comment. I have filed bug #1724626 to ask cloud-init development to surface more information from ds-identify to help ID the cloud so that we can better tag/annotate the bug. There may also be some info we can get to indicate the image ID on more clouds than just AWS. At a minimum I would like to see dsidentify make the EC2 platform it found available for consumers in cloud.cfg. This would allow us to identify AWS EC2 from look-alike datasources so that we can tag a bug as ec2-images for bug really on AWS and add EC2 specific fields to the description/attachments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1724623/+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 1698181] Re: Switch to netplan renderer in Artful
I just learned that this doesn't need changes in cloud-init, or shouldn't. I was target this to ubuntu-meta for ifupdate to be removed from the seed in 17.10. From that we should just switch to netplan like magic. ;) I'll let the owners of the other affected packages close their own bits of this bug once they've evaluated the impact. ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1698181 Title: Switch to netplan renderer in Artful Status in cloud-images: New Status in cloud-init package in Ubuntu: New Status in lxd package in Ubuntu: Invalid Status in maas package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu server ISOs are moving to netplan and cloud images must follow suit. We are requesting that the default renderer in 17.10 be switched to netplan to be consistent across all cloud images and ISO installs. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1698181/+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 1824227] [NEW] console-setup failure due to race with systemd-tmpfiles
Public bug reported: I'm seeing a console-setup.service failure quite regularly in testing where the temp file that should have been created can't be found. This is a regular xenial cloud image. 19:51:13 systemd-tmpfiles[485]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. ... 19:51:13 systemd[1]: Starting Set console font and keymap... 19:51:15 setupcon[455]: /bin/setupcon: 809: /bin/setupcon: cannot open /tmp/tmpkbd.a8FGSs: No such file 19:51:15 systemd[1]: console-setup.service: Main process exited, code=exited, status=1/FAILURE 19:51:15 systemd[1]: Failed to start Set console font and keymap. 19:51:15 systemd[1]: console-setup.service: Unit entered failed state. 19:51:15 systemd[1]: console-setup.service: Failed with result 'exit-code'. ... /bin/setupcon has a lovely tempfile function that looks like: if \ TMPFILE=`mktemp /tmp/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /run/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /dev/.tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /lib/init/rw/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp 2>/dev/null` Here's our edited IRC conversation on the bug: <@vorlon> so I do think you're being hit by the tmp cleaner <@vorlon> also this seems like bad pathological default behavior for the tmp cleaner, to delete files that have just been created <@vorlon> but we should fix console-setup to not rely on /tmp <@vorlon> and I prefer that we do that instead of trying to fiddle with the ordering of the systemd units on startup <@vorlon> i.e. console-setup has an undeclared dependency on systemd-tmpfiles-clean; let's remove the dependency instead of declaring it <@vorlon> are you failing the race more often now than in the past? <@rcj>vorlon: it feels like it's failing more often but I don't have data to answer that. <@vorlon> are we shipping an image with a dirty rootfs? <@vorlon> dirty in the sense that e2fsck doesn't take one look at it, say "yep, nothing to do here" and exit <@vorlon> in the sense that this is what would make dev-sda1.device slow to complete AIUI <@rcj>would filesystem resize on first boot mark it dirty? Because that will happen <@vorlon> huh good question <@vorlon> it might rcj, unclean shutdown? <@rcj>xnox: first boot ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: console-setup 1.108ubuntu15.4 ProcVersionSignature: User Name 4.15.0-1029.31~16.04.1-gcp 4.15.18 Uname: Linux 4.15.0-1029-gcp x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Apr 10 19:24:12 2019 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-setup (Ubuntu) Importance: High Status: Triaged ** Affects: console-setup (Ubuntu Bionic) Importance: High Status: Triaged ** Affects: console-setup (Ubuntu Cosmic) Importance: High Status: Triaged ** Affects: console-setup (Ubuntu Disco) Importance: High Status: Triaged ** Tags: amd64 apport-bug uec-images xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1824227 Title: console-setup failure due to race with systemd-tmpfiles Status in console-setup package in Ubuntu: Triaged Status in console-setup source package in Bionic: Triaged Status in console-setup source package in Cosmic: Triaged Status in console-setup source package in Disco: Triaged Bug description: I'm seeing a console-setup.service failure quite regularly in testing where the temp file that should have been created can't be found. This is a regular xenial cloud image. 19:51:13 systemd-tmpfiles[485]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. ... 19:51:13 systemd[1]: Starting Set console font and keymap... 19:51:15 setupcon[455]: /bin/setupcon: 809: /bin/setupcon: cannot open /tmp/tmpkbd.a8FGSs: No such file 19:51:15 systemd[1]: console-setup.service: Main process exited, code=exited, status=1/FAILURE 19:51:15 systemd[1]: Failed to start Set console font and keymap. 19:51:15 systemd[1]: console-setup.service: Unit entered failed state. 19:51:15 systemd[1]: console-setup.service: Failed with result 'exit-code'. ... /bin/setupcon has a lovely tempfile function that looks like: if \ TMPFILE=`mktemp /tmp/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /run/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /dev/.tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /lib/init/rw/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp 2>/dev/null`
[Touch-packages] [Bug 1824227] Re: console-setup failure due to race with systemd-tmpfiles
** Attachment added: "journal" https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1824227/+attachment/5254776/+files/journal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1824227 Title: console-setup failure due to race with systemd-tmpfiles Status in console-setup package in Ubuntu: Triaged Status in console-setup source package in Bionic: Triaged Status in console-setup source package in Cosmic: Triaged Status in console-setup source package in Disco: Triaged Bug description: I'm seeing a console-setup.service failure quite regularly in testing where the temp file that should have been created can't be found. This is a regular xenial cloud image. 19:51:13 systemd-tmpfiles[485]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. ... 19:51:13 systemd[1]: Starting Set console font and keymap... 19:51:15 setupcon[455]: /bin/setupcon: 809: /bin/setupcon: cannot open /tmp/tmpkbd.a8FGSs: No such file 19:51:15 systemd[1]: console-setup.service: Main process exited, code=exited, status=1/FAILURE 19:51:15 systemd[1]: Failed to start Set console font and keymap. 19:51:15 systemd[1]: console-setup.service: Unit entered failed state. 19:51:15 systemd[1]: console-setup.service: Failed with result 'exit-code'. ... /bin/setupcon has a lovely tempfile function that looks like: if \ TMPFILE=`mktemp /tmp/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /run/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /dev/.tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /lib/init/rw/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp 2>/dev/null` Here's our edited IRC conversation on the bug: <@vorlon> so I do think you're being hit by the tmp cleaner <@vorlon> also this seems like bad pathological default behavior for the tmp cleaner, to delete files that have just been created <@vorlon> but we should fix console-setup to not rely on /tmp <@vorlon> and I prefer that we do that instead of trying to fiddle with the ordering of the systemd units on startup <@vorlon> i.e. console-setup has an undeclared dependency on systemd-tmpfiles-clean; let's remove the dependency instead of declaring it <@vorlon> are you failing the race more often now than in the past? <@rcj>vorlon: it feels like it's failing more often but I don't have data to answer that. <@vorlon> are we shipping an image with a dirty rootfs? <@vorlon> dirty in the sense that e2fsck doesn't take one look at it, say "yep, nothing to do here" and exit <@vorlon> in the sense that this is what would make dev-sda1.device slow to complete AIUI <@rcj>would filesystem resize on first boot mark it dirty? Because that will happen <@vorlon> huh good question <@vorlon> it might rcj, unclean shutdown? <@rcj>xnox: first boot ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: console-setup 1.108ubuntu15.4 ProcVersionSignature: User Name 4.15.0-1029.31~16.04.1-gcp 4.15.18 Uname: Linux 4.15.0-1029-gcp x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Apr 10 19:24:12 2019 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1824227/+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 1824227] Re: console-setup failure due to race with systemd-tmpfiles
I have built cosmic, bionic, and xenial images in GCE with the packages from -proposed and tested that console setup is functioning correctly with the change. Thanks. I will be marking each of the releases as tested. ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-cosmic verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1824227 Title: console-setup failure due to race with systemd-tmpfiles Status in console-setup package in Ubuntu: Fix Released Status in console-setup source package in Xenial: Fix Committed Status in console-setup source package in Bionic: Fix Committed Status in console-setup source package in Cosmic: Fix Committed Status in console-setup source package in Disco: Fix Released Bug description: [SRU Justification] I'm seeing a console-setup.service failure quite regularly in testing where the temp file that should have been created can't be found. This is a regular xenial cloud image. 19:51:13 systemd-tmpfiles[485]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. ... 19:51:13 systemd[1]: Starting Set console font and keymap... 19:51:15 setupcon[455]: /bin/setupcon: 809: /bin/setupcon: cannot open /tmp/tmpkbd.a8FGSs: No such file 19:51:15 systemd[1]: console-setup.service: Main process exited, code=exited, status=1/FAILURE 19:51:15 systemd[1]: Failed to start Set console font and keymap. 19:51:15 systemd[1]: console-setup.service: Unit entered failed state. 19:51:15 systemd[1]: console-setup.service: Failed with result 'exit-code'. ... /bin/setupcon has a lovely tempfile function that looks like: if \ TMPFILE=`mktemp /tmp/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /run/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /dev/.tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /lib/init/rw/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp 2>/dev/null` Here's our edited IRC conversation on the bug: <@vorlon> so I do think you're being hit by the tmp cleaner <@vorlon> also this seems like bad pathological default behavior for the tmp cleaner, to delete files that have just been created <@vorlon> but we should fix console-setup to not rely on /tmp <@vorlon> and I prefer that we do that instead of trying to fiddle with the ordering of the systemd units on startup <@vorlon> i.e. console-setup has an undeclared dependency on systemd-tmpfiles-clean; let's remove the dependency instead of declaring it <@vorlon> are you failing the race more often now than in the past? <@rcj>vorlon: it feels like it's failing more often but I don't have data to answer that. <@vorlon> are we shipping an image with a dirty rootfs? <@vorlon> dirty in the sense that e2fsck doesn't take one look at it, say "yep, nothing to do here" and exit <@vorlon> in the sense that this is what would make dev-sda1.device slow to complete AIUI <@rcj>would filesystem resize on first boot mark it dirty? Because that will happen <@vorlon> huh good question <@vorlon> it might rcj, unclean shutdown? <@rcj>xnox: first boot [Test case] 1. Install console-setup from -proposed 2. Reboot 3. Verify that `systemctl status console-setup` shows that the service has completed successfully. Since this is a race, additional fuzz testing may be warranted for the cloud images to confirm that the issue experienced in GCE is really fixed. However, that should not block promotion of this SRU fix since there definitely is a race here that should be fixed per se even if there are other issues still causing a failure in GCE. [Regression potential] None known. /run is guaranteed to be mounted rw very early in boot - generally before /tmp is mounted, due to /tmp being on the rootfs that needs to be fscked before remount. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: console-setup 1.108ubuntu15.4 ProcVersionSignature: User Name 4.15.0-1029.31~16.04.1-gcp 4.15.18 Uname: Linux 4.15.0-1029-gcp x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Apr 10 19:24:12 2019 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1824227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-pa
[Touch-packages] [Bug 1871451] Re: powerpc segfault on exponential of negative in python
This would be an issue for the package, I will close the track for cloud-images. ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-images Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1871451 Title: powerpc segfault on exponential of negative in python Status in cloud-images: Invalid Status in python3-defaults package in Ubuntu: New Status in qemu package in Ubuntu: New Bug description: When calculating the exponential of a negative number in python 3.6 with the Ubuntu 18.04 Docker image (ppcle64), I receive a segfault. ``` python3 -c "import math; math.exp(-1)" qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault ``` I am running this in Docker on macOS. Here are the steps to reproduce the error. ``` docker run --rm -it --platform linux/ppc64le ubuntu:18.04 apt-get update -qq && apt-get install -y -qq python3 python3 -c "import math; print(math.exp(0))" # 1.0 python3 -c "import math; print(math.exp(-0))" # 1.0 python3 -c "import math; print(math.exp(1))" # 2.718281828459045 python3 -c "import math; print(math.exp(-1))" ``` This error does not happen when using the debian:10 or alpine images. Here is the output of docker version on my machine: ``` Client: Docker Engine - Community Version: 19.03.8 API version: 1.40 Go version:go1.12.17 Git commit:afacb8b Built: Wed Mar 11 01:21:11 2020 OS/Arch: darwin/amd64 Experimental: true Server: Docker Engine - Community Engine: Version: 19.03.8 API version: 1.40 (minimum version 1.12) Go version: go1.12.17 Git commit: afacb8b Built:Wed Mar 11 01:29:16 2020 OS/Arch: linux/amd64 Experimental: true containerd: Version: v1.2.13 GitCommit:7ad184331fa3e55e52b890ea95e65ba581ae3429 runc: Version: 1.0.0-rc10 GitCommit:dc9208a3303feef5b3839f4323d9beb36df0a9dd docker-init: Version: 0.18.0 GitCommit:fec3683 ``` Cross-posted to StackOverflow: https://stackoverflow.com/questions/61084969/python-segfault- calculating-exponential-of-negative-ppc64le To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1871451/+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 1872145] [NEW] explicit key offered after all agent keys, auth fails before explicit key used
Public bug reported: A user creates an ssh key and specifies it on the cmdline with 'ssh -i new_key user@host'. The connection fails with the message "Too many authentication failures" displayed to the user. This would lead the user to believe that they failed to put the public portion of the new key on the destination and it will probably be hard for the average user to debug this. The root of this issue is that the user has a number of keys in ~/.ssh/ registered with their ssh agent. The ssh command is offering each of these keys from the agent to the remote system before trying the explicit key from the command line. There are enough agent keys to reach the failure limit (usually 5 keys) with the remote before they get to the explicit key. The solution today for the user is to head down into the ssh_config man page to find '-o IdentitiesOnly=yes' to skip the agent keys and only use the specified key. But they're unlikely to do this because '-i' in the ssh man page doesn't suggest this and they'd only look for this if they actually understood the root cause of the problem, which is a bit cruel. We should consider changing the order of the keys offered to the remote to use explicit keys first followed by agent keys. It would seem to me that this would honor the users intent of explicitly specifying a key to use. The current order makes this difficult for anyone fielding a user's authentication failure report as they must double check that ssh managed to actually try the key the user specified before it raised an error message about authentication failures. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- 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/1872145 Title: explicit key offered after all agent keys, auth fails before explicit key used Status in openssh package in Ubuntu: New Bug description: A user creates an ssh key and specifies it on the cmdline with 'ssh -i new_key user@host'. The connection fails with the message "Too many authentication failures" displayed to the user. This would lead the user to believe that they failed to put the public portion of the new key on the destination and it will probably be hard for the average user to debug this. The root of this issue is that the user has a number of keys in ~/.ssh/ registered with their ssh agent. The ssh command is offering each of these keys from the agent to the remote system before trying the explicit key from the command line. There are enough agent keys to reach the failure limit (usually 5 keys) with the remote before they get to the explicit key. The solution today for the user is to head down into the ssh_config man page to find '-o IdentitiesOnly=yes' to skip the agent keys and only use the specified key. But they're unlikely to do this because '-i' in the ssh man page doesn't suggest this and they'd only look for this if they actually understood the root cause of the problem, which is a bit cruel. We should consider changing the order of the keys offered to the remote to use explicit keys first followed by agent keys. It would seem to me that this would honor the users intent of explicitly specifying a key to use. The current order makes this difficult for anyone fielding a user's authentication failure report as they must double check that ssh managed to actually try the key the user specified before it raised an error message about authentication failures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1872145/+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 1872145] Re: explicit key offered after all agent keys, auth can fail before explicit key used
** Summary changed: - explicit key offered after all agent keys, auth fails before explicit key used + explicit key offered after all agent keys, auth can fail before explicit key used -- 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/1872145 Title: explicit key offered after all agent keys, auth can fail before explicit key used Status in openssh package in Ubuntu: New Bug description: A user creates an ssh key and specifies it on the cmdline with 'ssh -i new_key user@host'. The connection fails with the message "Too many authentication failures" displayed to the user. This would lead the user to believe that they failed to put the public portion of the new key on the destination and it will probably be hard for the average user to debug this. The root of this issue is that the user has a number of keys in ~/.ssh/ registered with their ssh agent. The ssh command is offering each of these keys from the agent to the remote system before trying the explicit key from the command line. There are enough agent keys to reach the failure limit (usually 5 keys) with the remote before they get to the explicit key. The solution today for the user is to head down into the ssh_config man page to find '-o IdentitiesOnly=yes' to skip the agent keys and only use the specified key. But they're unlikely to do this because '-i' in the ssh man page doesn't suggest this and they'd only look for this if they actually understood the root cause of the problem, which is a bit cruel. We should consider changing the order of the keys offered to the remote to use explicit keys first followed by agent keys. It would seem to me that this would honor the users intent of explicitly specifying a key to use. The current order makes this difficult for anyone fielding a user's authentication failure report as they must double check that ssh managed to actually try the key the user specified before it raised an error message about authentication failures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1872145/+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 1872485] Re: virtualbox-guest-utils fails to install on 20.04
** Tags added: champagne -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1872485 Title: virtualbox-guest-utils fails to install on 20.04 Status in apt package in Ubuntu: New Status in virtualbox package in Ubuntu: New Bug description: Attempting to install virtualbox-guest-utils 6.1.4-dfsg-2 on ubuntu:focal (20.04) produces a broken state. Debug of `apt-get install virtualbox-guest-utils` below. Steps to reproduce: 1. pull a fresh 20.04 image for testing (ex: lxc launch ubuntu-daily:20.04 test-container) 2. lxc exec test-container bash 3. apt update 4. apt full-upgrade 5. apt-get install virtualbox-guest-utils Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: glib-networking : Depends: gsettings-desktop-schemas but it is not going to be installed init : PreDepends: systemd-sysv but it is not going to be installed Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < none -> 6.1.4-dfsg-2 @un puN > Considering virtualbox-guest-utils:amd64 9998 as a solution to systemd-timesyncd:amd64 14 Removing systemd-timesyncd:amd64 rather than change virtualbox-guest-utils:amd64 Investigating (1) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mR > Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59 Added systemd-timesyncd:amd64 to the remove list Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H > Considering openntpd:amd64 0 as a solution to systemd:amd64 59 Added openntpd:amd64 to the remove list Fixing systemd:amd64 via keep of systemd-timesyncd:amd64 Fixing systemd:amd64 via keep of openntpd:amd64 Investigating (1) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < none -> 6.1.4-dfsg-2 @un puN > Considering virtualbox-guest-utils:amd64 9998 as a solution to systemd-timesyncd:amd64 14 Removing systemd-timesyncd:amd64 rather than change virtualbox-guest-utils:amd64 Investigating (2) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mR > Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59 Added systemd-timesyncd:amd64 to the remove list Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H > Considering openntpd:amd64 0 as a solution to systemd:amd64 59 Added openntpd:amd64 to the remove list Fixing systemd:amd64 via keep of systemd-timesyncd:amd64 Fixing systemd:amd64 via keep of openntpd:amd64 Investigating (2) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < none -> 6.1.4-dfsg-2 @un puN > Considering virtualbox-guest-utils:amd64 9998 as a solution to systemd-timesyncd:amd64 59 Removing systemd-timesyncd:amd64 rather than change virtualbox-guest-utils:amd64 Investigating (3) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mR > Considering systemd-timesyncd:amd64 9998 as a solution to systemd:amd64 59 Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H > Considering openntpd:amd64 59 as a solution to systemd:amd64 59 Or group remove for systemd:amd64 Investigating (3) libpam-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken libpam-systemd:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR > (= 245.4-2ubuntu1) Considering systemd:amd64 59 as a solution to libpam-systemd:amd64 23 Removing libpam-systemd:amd64 rather than change systemd:amd64 Investigating (3) libnss-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken libnss-systemd:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR > (= 245.4-2ubuntu1) Considering systemd:amd64 59 as a solution to libnss-systemd:amd64 14 Removing libnss-systemd:amd64 rather than change systemd:amd64 Investigating (3) plymouth:amd64 < 0.9.4git20200323-0ubuntu6 @ii mK Ib > Broken plymouth:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR > (>= 232-8~) Considering systemd:amd64 59 as a solution to plymouth:amd64 12 Removing plymouth:amd64 rath
[Touch-packages] [Bug 1872485] Re: virtualbox-guest-utils fails to install on 20.04
systemd-timesyncd is conflicting with virtualbox-guest-utils but
virtualbox-guest-utils isn't providing time-daemon... debian/control in
virtualbox contains:
Package: virtualbox-guest-utils
Architecture: amd64 i386
Depends: adduser,
pciutils,
virtualbox-guest-dkms (= ${source:Version}) | virtualbox-guest-source
(= ${source:Version}) | virtualbox-guest-modules,
${misc:Depends},
${shlibs:Depends}
#Conflicts: time-daemon, ntp
#Provides: time-daemon
#Replaces: time-daemon
** No longer affects: apt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1872485
Title:
virtualbox-guest-utils fails to install on 20.04
Status in virtualbox package in Ubuntu:
Triaged
Bug description:
Attempting to install virtualbox-guest-utils 6.1.4-dfsg-2 on
ubuntu:focal (20.04) produces a broken state. Debug of `apt-get
install virtualbox-guest-utils` below.
Steps to reproduce:
1. pull a fresh 20.04 image for testing (ex: lxc launch ubuntu-daily:20.04
test-container)
2. lxc exec test-container bash
3. apt update
4. apt full-upgrade
5. apt-get install virtualbox-guest-utils
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
glib-networking : Depends: gsettings-desktop-schemas but it is not going to
be installed
init : PreDepends: systemd-sysv but it is not going to be installed
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 <
none -> 6.1.4-dfsg-2 @un puN >
Considering virtualbox-guest-utils:amd64 9998 as a solution to
systemd-timesyncd:amd64 14
Removing systemd-timesyncd:amd64 rather than change
virtualbox-guest-utils:amd64
Investigating (1) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii
mR >
Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59
Added systemd-timesyncd:amd64 to the remove list
Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
Considering openntpd:amd64 0 as a solution to systemd:amd64 59
Added openntpd:amd64 to the remove list
Fixing systemd:amd64 via keep of systemd-timesyncd:amd64
Fixing systemd:amd64 via keep of openntpd:amd64
Investigating (1) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 <
none -> 6.1.4-dfsg-2 @un puN >
Considering virtualbox-guest-utils:amd64 9998 as a solution to
systemd-timesyncd:amd64 14
Removing systemd-timesyncd:amd64 rather than change
virtualbox-guest-utils:amd64
Investigating (2) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii
mR >
Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59
Added systemd-timesyncd:amd64 to the remove list
Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
Considering openntpd:amd64 0 as a solution to systemd:amd64 59
Added openntpd:amd64 to the remove list
Fixing systemd:amd64 via keep of systemd-timesyncd:amd64
Fixing systemd:amd64 via keep of openntpd:amd64
Investigating (2) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 <
none -> 6.1.4-dfsg-2 @un puN >
Considering virtualbox-guest-utils:amd64 9998 as a solution to
systemd-timesyncd:amd64 59
Removing systemd-timesyncd:amd64 rather than change
virtualbox-guest-utils:amd64
Investigating (3) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii
mR >
Considering systemd-timesyncd:amd64 9998 as a solution to systemd:amd64 59
Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
Considering openntpd:amd64 59 as a solution to systemd:amd64 59
Or group remove for systemd:amd64
Investigating (3) libpam-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
Broken libpam-systemd:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR
> (= 245.4-2ubuntu1)
Considering systemd:amd64 59 as a solution to libpam-systemd:amd64 23
Removing libpam-systemd:amd64 rather than change systemd:amd64
Investigating (3) libnss-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
Broken libnss-
[Touch-packages] [Bug 1873528] [NEW] sshd overrides from /etc/ssh/sshd_config.d/*conf apply in reverse lexographic order
Public bug reported: I am looking at the addition of 'Include /etc/ssh/sshd_config.d/*conf' for use in Ubuntu cloud images. I wanted to add a config file and see if I had done things correctly. I assumed that the files were sourced lexographically (based on use of glob() in readconf.h) so that I could document how users could override our tuning. But it appears from 'sshd -T' output and observed behavior that the first file in /etc/sshd_config.d/ to define a parameter wins. I see in 'sshd -ddd' output that they are parsed lexographically but it seems that their settings apply in reverse (or whichever comes first) if that makes sense. I'd like to understand if this is correct behavior and get it documented. Steps to reproduce on focal with openssh-server 1:8.2p1-4: 1. Create the following files in /etc/ssh/sshd_config.d/ with the content shown below: 40-cloudimg-settings.conf: ClientAliveInterval 110 PasswordAuthentication yes PermitRootLogin no 50-cloudimg-settings.conf: ClientAliveInterval 120 PermitRootLogin yes 60-cloudimg-settings.conf: ClientAliveInterval 180 2. Check what sshd thinks the values will be with 'sshd -T|grep -i clientaliveinterval' and 'sshd -T|grep permitrootlogin' clientaliveinterval 110 permitrootlogin no (The tuning I cared about was ClientAliveInterval for my work but PermitRootLogin is easier to demonstrate) 3. Run '/usr/sbin/sshd -ddd' to check debug output for config file parsing behavior: debug2: load_server_config: filename /etc/ssh/sshd_config debug2: load_server_config: done config len = 296 debug2: parse_server_config_depth: config /etc/ssh/sshd_config len 296 debug2: /etc/ssh/sshd_config line 13: new include /etc/ssh/sshd_config.d/*.conf debug2: /etc/ssh/sshd_config line 13: including /etc/ssh/sshd_config.d/40-cloudimg-settings.conf debug2: load_server_config: filename /etc/ssh/sshd_config.d/40-cloudimg-settings.conf debug2: load_server_config: done config len = 71 debug2: parse_server_config_depth: config /etc/ssh/sshd_config.d/40-cloudimg-settings.conf len 71 debug3: /etc/ssh/sshd_config.d/40-cloudimg-settings.conf:1 setting ClientAliveInterval 110 debug3: /etc/ssh/sshd_config.d/40-cloudimg-settings.conf:2 setting PasswordAuthentication yes debug3: /etc/ssh/sshd_config.d/40-cloudimg-settings.conf:3 setting PermitRootLogin no debug2: /etc/ssh/sshd_config line 13: including /etc/ssh/sshd_config.d/50-cloudimg-settings.conf debug2: load_server_config: filename /etc/ssh/sshd_config.d/50-cloudimg-settings.conf debug2: load_server_config: done config len = 46 debug2: parse_server_config_depth: config /etc/ssh/sshd_config.d/50-cloudimg-settings.conf len 46 debug3: /etc/ssh/sshd_config.d/50-cloudimg-settings.conf:1 setting ClientAliveInterval 120 debug3: /etc/ssh/sshd_config.d/50-cloudimg-settings.conf:2 setting PermitRootLogin yes debug2: /etc/ssh/sshd_config line 13: including /etc/ssh/sshd_config.d/60-cloudimg-settings.conf debug2: load_server_config: filename /etc/ssh/sshd_config.d/60-cloudimg-settings.conf debug2: load_server_config: done config len = 25 debug2: parse_server_config_depth: config /etc/ssh/sshd_config.d/60-cloudimg-settings.conf len 25 debug3: /etc/ssh/sshd_config.d/60-cloudimg-settings.conf:1 setting ClientAliveInterval 180 4. Set a root password and unlock the account. 5. Attempt to ssh as root to the instance with a password. Observation: * Root password login is denied if PermitRootLogin is 'no' in 40-foo.conf and 'yes' in 50-foo.conf * Root password login is allowed if PermitRootLogin is 'yes' in 40-foo.conf and 'no' in 50-foo.conf It appears in 'sshd -ddd' output that files are parsed in lexographic order (40-foo.conf before 50-foo.conf) but the behavior observed indicates that the value set in 40-foo.conf overrides 50-foo.conf which is counter to expectations. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: champagne -- 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/1873528 Title: sshd overrides from /etc/ssh/sshd_config.d/*conf apply in reverse lexographic order Status in openssh package in Ubuntu: New Bug description: I am looking at the addition of 'Include /etc/ssh/sshd_config.d/*conf' for use in Ubuntu cloud images. I wanted to add a config file and see if I had done things correctly. I assumed that the files were sourced lexographically (based on use of glob() in readconf.h) so that I could document how users could override our tuning. But it appears from 'sshd -T' output and observed behavior that the first file in /etc/sshd_config.d/ to define a parameter wins. I see in 'sshd -ddd' output that they are parsed lexographically but it seems that their settings apply in reverse (or whichever comes first) if that makes sense. I'd like to understand if this is correct behavior and get it documented. Step
[Touch-packages] [Bug 1873528] Re: sshd overrides from /etc/ssh/sshd_config.d/*conf apply in reverse lexographic order
Drat, I see that now in sshd_config. I think I tried searching for "first" and maybe by that point I was just looking at sshd's man page. Okay, well then this is fine for me It's documented and stable. We can comfortably make this change for cloud-images. Thanks Colin! ** Changed in: openssh (Ubuntu) Status: Confirmed => Invalid -- 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/1873528 Title: sshd overrides from /etc/ssh/sshd_config.d/*conf apply in reverse lexographic order Status in openssh package in Ubuntu: Invalid Bug description: I am looking at the addition of 'Include /etc/ssh/sshd_config.d/*conf' for use in Ubuntu cloud images. I wanted to add a config file and see if I had done things correctly. I assumed that the files were sourced lexographically (based on use of glob() in readconf.h) so that I could document how users could override our tuning. But it appears from 'sshd -T' output and observed behavior that the first file in /etc/sshd_config.d/ to define a parameter wins. I see in 'sshd -ddd' output that they are parsed lexographically but it seems that their settings apply in reverse (or whichever comes first) if that makes sense. I'd like to understand if this is correct behavior and get it documented. Steps to reproduce on focal with openssh-server 1:8.2p1-4: 1. Create the following files in /etc/ssh/sshd_config.d/ with the content shown below: 40-cloudimg-settings.conf: ClientAliveInterval 110 PasswordAuthentication yes PermitRootLogin no 50-cloudimg-settings.conf: ClientAliveInterval 120 PermitRootLogin yes 60-cloudimg-settings.conf: ClientAliveInterval 180 2. Check what sshd thinks the values will be with 'sshd -T|grep -i clientaliveinterval' and 'sshd -T|grep permitrootlogin' clientaliveinterval 110 permitrootlogin no (The tuning I cared about was ClientAliveInterval for my work but PermitRootLogin is easier to demonstrate) 3. Run '/usr/sbin/sshd -ddd' to check debug output for config file parsing behavior: debug2: load_server_config: filename /etc/ssh/sshd_config debug2: load_server_config: done config len = 296 debug2: parse_server_config_depth: config /etc/ssh/sshd_config len 296 debug2: /etc/ssh/sshd_config line 13: new include /etc/ssh/sshd_config.d/*.conf debug2: /etc/ssh/sshd_config line 13: including /etc/ssh/sshd_config.d/40-cloudimg-settings.conf debug2: load_server_config: filename /etc/ssh/sshd_config.d/40-cloudimg-settings.conf debug2: load_server_config: done config len = 71 debug2: parse_server_config_depth: config /etc/ssh/sshd_config.d/40-cloudimg-settings.conf len 71 debug3: /etc/ssh/sshd_config.d/40-cloudimg-settings.conf:1 setting ClientAliveInterval 110 debug3: /etc/ssh/sshd_config.d/40-cloudimg-settings.conf:2 setting PasswordAuthentication yes debug3: /etc/ssh/sshd_config.d/40-cloudimg-settings.conf:3 setting PermitRootLogin no debug2: /etc/ssh/sshd_config line 13: including /etc/ssh/sshd_config.d/50-cloudimg-settings.conf debug2: load_server_config: filename /etc/ssh/sshd_config.d/50-cloudimg-settings.conf debug2: load_server_config: done config len = 46 debug2: parse_server_config_depth: config /etc/ssh/sshd_config.d/50-cloudimg-settings.conf len 46 debug3: /etc/ssh/sshd_config.d/50-cloudimg-settings.conf:1 setting ClientAliveInterval 120 debug3: /etc/ssh/sshd_config.d/50-cloudimg-settings.conf:2 setting PermitRootLogin yes debug2: /etc/ssh/sshd_config line 13: including /etc/ssh/sshd_config.d/60-cloudimg-settings.conf debug2: load_server_config: filename /etc/ssh/sshd_config.d/60-cloudimg-settings.conf debug2: load_server_config: done config len = 25 debug2: parse_server_config_depth: config /etc/ssh/sshd_config.d/60-cloudimg-settings.conf len 25 debug3: /etc/ssh/sshd_config.d/60-cloudimg-settings.conf:1 setting ClientAliveInterval 180 4. Set a root password and unlock the account. 5. Attempt to ssh as root to the instance with a password. Observation: * Root password login is denied if PermitRootLogin is 'no' in 40-foo.conf and 'yes' in 50-foo.conf * Root password login is allowed if PermitRootLogin is 'yes' in 40-foo.conf and 'no' in 50-foo.conf It appears in 'sshd -ddd' output that files are parsed in lexographic order (40-foo.conf before 50-foo.conf) but the behavior observed indicates that the value set in 40-foo.conf overrides 50-foo.conf which is counter to expectations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1873528/+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 1875882] Re: debconf attempts interactive configuration; breaks Docker image builds
** Changed in: cloud-images Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1875882 Title: debconf attempts interactive configuration; breaks Docker image builds Status in cloud-images: Invalid Status in debconf package in Ubuntu: New Bug description: When I build a container image using a Dockerfile based on the official "ubuntu" image, if I try to install packages that use debconf to obtain configuration information, the build fails because debconf tries to interact with the user (which is not possible when building a container, since the build process must be non-interactive). How to reproduce: 1) install Docker (the version doesn't seem to matter; tried with various 19.03 variants) 2) run the following command to try and build an image: ``` docker build -
[Touch-packages] [Bug 1780316] Re: netcat-openbsd is in main but netcat-standard has a netcat dummy package
** Description changed: For installations that don't have netcat-openbsd somewhere in the seed then any package/user that installs 'netcat' will get 'netcat-standard' from universe rather than 'netcat-openbsd' from main. (One example is the ubuntu-fan package that recommends netcat) + Installing the 'netcat' transitional package should provide users a + supported package as one exists. + Suggested action: * Remove the 'netcat' dummy package from the netcat-standard package * Add a 'netcat' dummy package to the netcat-openbsd package -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu. https://bugs.launchpad.net/bugs/1780316 Title: netcat-openbsd is in main but netcat-standard has a netcat dummy package Status in netcat package in Ubuntu: New Status in netcat-openbsd package in Ubuntu: New Bug description: For installations that don't have netcat-openbsd somewhere in the seed then any package/user that installs 'netcat' will get 'netcat- standard' from universe rather than 'netcat-openbsd' from main. (One example is the ubuntu-fan package that recommends netcat) Installing the 'netcat' transitional package should provide users a supported package as one exists. Suggested action: * Remove the 'netcat' dummy package from the netcat-standard package * Add a 'netcat' dummy package to the netcat-openbsd package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat/+bug/1780316/+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 1866012] Re: depmod ERROR during Setting up linux-modules-5.4.0-17-generic
** Tags added: champagne -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1866012 Title: depmod ERROR during Setting up linux-modules-5.4.0-17-generic Status in kmod package in Ubuntu: New Status in linux package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Deploy Focal on a KVM ndoe, enable proposed 2. Run sudo apt dist-upgrade The console will be flushed with: Setting up libisc1105:amd64 (1:9.11.16+dfsg-3~build1) ... Setting up linux-modules-5.4.0-17-generic (5.4.0-17.21) ... depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' Setting up apt-utils (1.9.12) ... Setting up libselinux1-dev:amd64 (3.0-1build2) ... Setting up libglib2.0-0:amd64 (2.64.0-1) ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: User Name 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 4 08:29 seq crw-rw 1 root audio 116, 33 Mar 4 08:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 4 09:06:42 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=36e162f3-41b5-4487-a6dc-09ba4e37d3bf ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-5.4 StagingDrivers: exfat UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1866012/+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 1866616] [NEW] 2nd display stopped working
Public bug reported: The 2nd display (attached to DVI) has stopped being detected but is used by bios and grub (output ceases once the spinning boot animation starts). I was away for a week but it was working prior to leaving. I've notices that Xorg.0.log shows DVI-D-0 disconnected where the 2nd monitor should be. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 9 06:13:23 2020 DistUpgraded: 2020-01-31 09:33:31,151 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] InstallationDate: Installed on 2017-04-21 (1052 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-01-31 (37 days ago) dmi.bios.date: 01/23/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.M0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.M0:bd01/23/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Oct 15 10:44:00 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.1-3ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug champagne focal regression reproducible ubuntu ** Description changed: The 2nd display (attached to DVI) has stopped being detected but is used by bios and grub (output ceases once the spinning boot animation starts). I was away for a week but it was working prior to leaving. - I've notices that Xorg.0.log shows fbdev rather than amdgpu in use (as - it had in the past). + I've notices that Xorg.0.log shows DVI-D-0 disconnected where the 2nd + monitor should be. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 9 06:13:23 2020 DistUpgraded: 2020-01-31 09:33:31,151 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) -Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] + Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) + Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] InstallationDate: Installed on 2017-04-21 (1052 days ago) InstallationMedia: Ubuntu
[Touch-packages] [Bug 1866616] Re: 2nd display stopped working
The log shows "open /dev/dri/card0: No such file or directory" but it does exist: $ ls -l /dev/dri/card0 crw-rw+ 1 root render 226, 0 Mar 9 06:12 /dev/dri/card0 Unplugging the display from DVI-D-0 and plugging it back in does not result in showing up in xrandr output. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1866616 Title: 2nd display stopped working Status in xorg package in Ubuntu: New Bug description: The 2nd display (attached to DVI) has stopped being detected but is used by bios and grub (output ceases once the spinning boot animation starts). I was away for a week but it was working prior to leaving. I've notices that Xorg.0.log shows DVI-D-0 disconnected where the 2nd monitor should be. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 9 06:13:23 2020 DistUpgraded: 2020-01-31 09:33:31,151 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] InstallationDate: Installed on 2017-04-21 (1052 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-01-31 (37 days ago) dmi.bios.date: 01/23/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.M0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.M0:bd01/23/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Oct 15 10:44:00 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.1-3ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1866616/+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 1866616] Re: 2nd display stopped working
Attaching the 2nd display via DisplayPort rather than DVI allows me to use it again, so I happen to have a solution, but not everyone may be so lucky. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1866616 Title: 2nd display stopped working Status in xorg package in Ubuntu: New Bug description: The 2nd display (attached to DVI) has stopped being detected but is used by bios and grub (output ceases once the spinning boot animation starts). I was away for a week but it was working prior to leaving. I've notices that Xorg.0.log shows DVI-D-0 disconnected where the 2nd monitor should be. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 9 06:13:23 2020 DistUpgraded: 2020-01-31 09:33:31,151 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] InstallationDate: Installed on 2017-04-21 (1052 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-01-31 (37 days ago) dmi.bios.date: 01/23/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.M0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.M0:bd01/23/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Oct 15 10:44:00 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.1-3ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1866616/+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 1342875] Re: Unable to delete currently logged in user
I tested the vivid package. 1:4.1.5.1-1.1ubuntu3 recreated the issue but in 1:4.1.5.1-1.1ubuntu4 --force works. Requesting SRU of fixes from bug #1436937 back to Trusty/Utopic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1342875 Title: Unable to delete currently logged in user Status in shadow package in Ubuntu: Triaged Status in shadow source package in Trusty: Won't Fix Status in shadow source package in Utopic: Won't Fix Bug description: A user can not delete themselves using the command 'sudo userdel -rf ', this is common in cloud tools that clean up running images prior to capture. A quick test shows that this worked from Precise (didn't look back further) to Raring and stopped working with Saucy. Here's a quick example of the failure (from trusty): # sudo adduser test # sudo usermod -aG sudo test ## As the 'test' user # sudo userdel -rf test userdel: user test is currently used by process 9600 userdel: cannot open /etc/subuid ## User is not removed Previously (output from precise) # sudo userdel -rf test userdel: user test is currently logged in userdel: warning: can't remove /var/mail/test: No such file or directory ## User is removed This is being run as the last command by tools that remove the 'ubuntu' user to clean the image prior to capture. This had previously worked and it is preferable that this could be made to work again. The alternative is removal by root, but the root user on cloud images is locked down and we would not want the user to enable root to run userdel on the risk of it not getting disabled properly prior to image capture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1342875/+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 1631519] [NEW] No X on boot with external monitor connected
Public bug reported: Running from today's (201610907) daily yakkety livecd I can boot to the desktop if only using the laptop's LCD (ThinkPad x230, intel graphics). Attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. Also, when booting from the livecd with the external display attached X does not start. This is a regression from Xenial. $ lsb_release -rd Description:Ubuntu Yakkety Yak (development branch) Release:16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Oct 7 20:18:12 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: New Bug description: Running from today's (201610907) daily yakkety livecd I can boot to the desktop if only using the laptop's LCD (ThinkPad x230, intel graphics). Attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. Also, when booting from the livecd with the external display attached X does not start. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 CompizPlugins: No va
[Touch-packages] [Bug 1631519] Re: No X on boot with external monitor connected
** Summary changed: - xorg hall-of-mirrors on external display + No X on boot with external monitor connected ** Description changed: - Running from today's (201610907) daily yakkety livecd I can boot to the - desktop if only using the laptop's LCD (ThinkPad x230, intel graphics). - Attaching a 1920x1080 LCD via miniDP extends the desktop but windows - moved around produce a trail of windows that persist even after the - window is closed. + When booting from today's (201610907) daily yakkety livecd with an + external display attached X does not start. - Also, when booting from the livecd with the external display attached X - does not start. + If the external monitor is attached after X has started I can boot to + the desktop using only using the laptop's LCD (ThinkPad x230, intel + graphics). The attaching a 1920x1080 LCD via miniDP extends the desktop + but windows moved around produce a trail of windows that persist even + after the window is closed. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: - Installed: 1:7.7+13ubuntu4 - Candidate: 1:7.7+13ubuntu4 - Version table: - *** 1:7.7+13ubuntu4 500 - 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1:7.7+13ubuntu4 + Candidate: 1:7.7+13ubuntu4 + Version table: + *** 1:7.7+13ubuntu4 500 + 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages + 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: - + ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] + Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Oct 7 20:18:12 2016 xserver.configfile: default xserver.errors: - + xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset ** Changed in: xorg (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631519 Title: No X on boot with ex
[Touch-packages] [Bug 1631519] Re: No X on boot with external monitor connected
** Attachment added: "moving a window across the display" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631519/+attachment/4757009/+files/ezgif.com-video-to-gif%20%282%29.gif -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: New Bug description: When booting from today's (201610907) daily yakkety livecd with an external display attached X does not start. If the external monitor is attached after X has started I can boot to the desktop using only using the laptop's LCD (ThinkPad x230, intel graphics). The attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Oct 7 20:18:12 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631519/+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 1631519] Re: No X on boot with external monitor connected
The attached gif tries to show the effect of moving a window across the screen. Not captured in the low-framerate gif is that the trails of the window are flickering and moving (compiz cpu usage is high when this happens). Hitting WIN+w to display windows and then drop back to the desktop clears the current trail. But that is not a reasonable workaround and does not address the basic issue that the livecd (or a fully installed desktop) does not boot to X with an external monitor attached. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: New Bug description: When booting from today's (201610907) daily yakkety livecd with an external display attached X does not start. If the external monitor is attached after X has started I can boot to the desktop using only using the laptop's LCD (ThinkPad x230, intel graphics). The attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Oct 7 20:18:12 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631519/+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 1631519] Re: No X on boot with external monitor connected
A monitor attached to the Thinkpad x230 via the docking station DVI port is fine (boots to X and no crazy window trails). This is seen when attaching a monitor via DP on the dock or mDP from the laptop. I was using an mDP to HDMI cable or a DP to DualLink-DVI adapter to connect monitors when I found this issue. Multiple monitors were tried and all experienced the issue when connect to the monitor's HDMI port from the laptop's mDP port. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: New Bug description: When booting from today's (201610907) daily yakkety livecd with an external display attached X does not start. If the external monitor is attached after X has started I can boot to the desktop using only using the laptop's LCD (ThinkPad x230, intel graphics). The attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Oct 7 20:18:12 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631519/+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 1631519] Re: No X on boot with external monitor connected
Still failing with http://cdimage.ubuntu.com/daily-live/20161008 /yakkety-desktop-amd64.iso (Yakkety Final) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: Confirmed Bug description: When booting from today's (201610907) daily yakkety livecd with an external display attached X does not start. If the external monitor is attached after X has started I can boot to the desktop using only using the laptop's LCD (ThinkPad x230, intel graphics). The attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Oct 7 20:18:12 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631519/+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 1631519] Re: No X on boot with external monitor connected
I have tried two monitors of different brands and a random television. The resolution selected is 1920x1080. On Mon, Oct 10, 2016 at 7:19 PM, Mathieu Trudel-Lapierre < mathieu...@gmail.com> wrote: > Could you please try with a different monitor or share more of the > details of how you are using this, such as which resolution is picked? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1631519 > > Title: > No X on boot with external monitor connected > > Status in xorg package in Ubuntu: > Incomplete > > Bug description: > When booting from today's (201610907) daily yakkety livecd with an > external display attached X does not start. > > If the external monitor is attached after X has started I can boot to > the desktop using only using the laptop's LCD (ThinkPad x230, intel > graphics). The attaching a 1920x1080 LCD via miniDP extends the > desktop but windows moved around produce a trail of windows that > persist even after the window is closed. > > This is a regression from Xenial. > > $ lsb_release -rd > Description: Ubuntu Yakkety Yak (development branch) > Release: 16.10 > > $ apt-cache policy xorg > xorg: > Installed: 1:7.7+13ubuntu4 > Candidate: 1:7.7+13ubuntu4 > Version table: >*** 1:7.7+13ubuntu4 500 > 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages > 100 /var/lib/dpkg/status > > ProblemType: Bug > DistroRelease: Ubuntu 16.10 > Package: xorg 1:7.7+13ubuntu4 > ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 > Uname: Linux 4.8.0-19-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.3-0ubuntu7 > Architecture: amd64 > CasperVersion: 1.379 > CompizPlugins: No value set for `/apps/compiz-1/general/ > screen0/options/active_plugins' > CompositorRunning: compiz > CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' > CompositorUnredirectFSW: true > CurrentDesktop: Unity > Date: Fri Oct 7 20:23:46 2016 > DistUpgraded: Fresh install > DistroCodename: yakkety > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation 3rd Gen Core processor Graphics Controller > [8086:0166] (rev 09) (prog-if 00 [VGA controller]) > Subsystem: Lenovo 3rd Gen Core processor Graphics Controller > [17aa:21fa] > LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) > MachineType: LENOVO 2306CTO > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi > file=/cdrom/preseed/username.seed boot=casper quiet splash --- > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 10/25/2013 > dmi.bios.vendor: LENOVO > dmi.bios.version: G2ET97WW (2.57 ) > dmi.board.asset.tag: Not Available > dmi.board.name: 2306CTO > dmi.board.vendor: LENOVO > dmi.board.version: Not Defined > dmi.chassis.asset.tag: No Asset Information > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: Not Available > dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO: > pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO: > rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: > dmi.product.name: 2306CTO > dmi.product.version: ThinkPad X230 > dmi.sys.vendor: LENOVO > version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 > version.ia32-libs: ia32-libs N/A > version.libdrm2: libdrm2 2.4.70-1 > version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 > version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A > version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 > version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev > 1:2.10.2-1ubuntu1 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20160706-1ubuntu1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau > 1:1.0.12-2 > xserver.bootTime: Fri Oct 7 20:18:12 2016 > xserver.configfile: default > xserver.errors: > > xserver.logfile: /var/log/Xorg.0.log > xserver.version: 2:1.18.4-1ubuntu6 > xserver.video_driver: modeset > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631519/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: Incomplete Bug description: When booting from today's (201610907) daily yakkety livecd with an external display attached X does not start. If the e
[Touch-packages] [Bug 1631519] Re: No X on boot with external monitor connected
Also, the bug was opened with the system running BIOS version 2.57: dmi.bios.version: G2ET97WW (2.57 ) I have upgraded to the latest version and recreated there as well: Version: G2ETA7WW (2.67 ) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: Incomplete Bug description: When booting from today's (201610907) daily yakkety livecd with an external display attached X does not start. If the external monitor is attached after X has started I can boot to the desktop using only using the laptop's LCD (ThinkPad x230, intel graphics). The attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Oct 7 20:18:12 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631519/+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 1631519] Re: No X on boot with external monitor connected
These are working with 16.04 perfectly, I updated to 16.10 and had to restore from backups to get back to 16.10. Then I booted from the live- cd to capture this bug. Scenarios: 1. mDP to HDMI cable connected to a 1080p monitor (Dell E248Wfp); that is the simple example and they all fail with the same result. 2. same Dell via DP2 on the doc using a DP to single-link DVI adapter (like http://www.monoprice.com/product?c_id=104&cp_id=10428&cs_id=1042801&p_id=4827) 3. DP2 on the doc connected to a Shimian LCD running at 2560x1440 connected via a Dell (BizLink) DisplayPort to DVI Dual Link Adapter (like https://www.amazon.com/Dell-BIZLINK-DisplayPort-Adapter-Powered/dp/B003XYBA72). But I didn't want to confuse the issue with that more niche bit of hardware. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: Incomplete Bug description: When booting from today's (201610907) daily yakkety livecd with an external display attached X does not start. If the external monitor is attached after X has started I can boot to the desktop using only using the laptop's LCD (ThinkPad x230, intel graphics). The attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Oct 7 20:18:12 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages Mor
[Touch-packages] [Bug 1618525] Re: Failure to remove kernel partition mappings in yakkety (2.28.1-1ubuntu1)
Running the recreate.sh script with util-linux 2.28.1-1ubuntu1 results in a failure when growpart attempts to write the new partition table and update the kernel indicating that the partition table was not cleared from the kernel when we ran 'kpartx -s -v -d /dev/loop0' In this case we have run: kpartx -s -v -a file # create the loopback device for 'file' and add partition mappings kpartx -s -v -d /dev/loop0 # delete the partition mappings, but keep the loopback device growpart /dev/loop0 1 # grow the 1st partition on /dev/loop0 ** Attachment added: "failure.output" https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1618525/+attachment/4730931/+files/failure.output -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1618525 Title: Failure to remove kernel partition mappings in yakkety (2.28.1-1ubuntu1) Status in util-linux package in Ubuntu: New Bug description: In the move from 2.28-5ubuntu2 and 2.28.1-1ubuntu1 of util-linux we see a regression when asking kpartx to remove kernel partition mappings where the appear to remain. Context: We create and modify disk images heavily. The example recreate creates a 2GB disk image with a single partition. From that 2GB image we will resize it to 8GB and grow the partition/filesystem. This stopped working in yakkety with 2.28.1-1ubuntu1. We do have a work-around which is call growpart on the file rather on the loopback device. Recreate script is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1618525/+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 1618525] Re: Failure to remove kernel partition mappings in yakkety (2.28.1-1ubuntu1)
Running the recreate.sh script with util-linux 2.28-5ubuntu2 gives us a successful run. ** Attachment added: "success.output" https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1618525/+attachment/4730930/+files/success.output -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1618525 Title: Failure to remove kernel partition mappings in yakkety (2.28.1-1ubuntu1) Status in util-linux package in Ubuntu: New Bug description: In the move from 2.28-5ubuntu2 and 2.28.1-1ubuntu1 of util-linux we see a regression when asking kpartx to remove kernel partition mappings where the appear to remain. Context: We create and modify disk images heavily. The example recreate creates a 2GB disk image with a single partition. From that 2GB image we will resize it to 8GB and grow the partition/filesystem. This stopped working in yakkety with 2.28.1-1ubuntu1. We do have a work-around which is call growpart on the file rather on the loopback device. Recreate script is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1618525/+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 1618525] [NEW] Failure to remove kernel partition mappings in yakkety (2.28.1-1ubuntu1)
Public bug reported: In the move from 2.28-5ubuntu2 and 2.28.1-1ubuntu1 of util-linux we see a regression when asking kpartx to remove kernel partition mappings where the appear to remain. Context: We create and modify disk images heavily. The example recreate creates a 2GB disk image with a single partition. From that 2GB image we will resize it to 8GB and grow the partition/filesystem. This stopped working in yakkety with 2.28.1-1ubuntu1. We do have a work-around which is call growpart on the file rather on the loopback device. Recreate script is attached. ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "recreate.sh" https://bugs.launchpad.net/bugs/1618525/+attachment/4730929/+files/recreate.sh -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1618525 Title: Failure to remove kernel partition mappings in yakkety (2.28.1-1ubuntu1) Status in util-linux package in Ubuntu: New Bug description: In the move from 2.28-5ubuntu2 and 2.28.1-1ubuntu1 of util-linux we see a regression when asking kpartx to remove kernel partition mappings where the appear to remain. Context: We create and modify disk images heavily. The example recreate creates a 2GB disk image with a single partition. From that 2GB image we will resize it to 8GB and grow the partition/filesystem. This stopped working in yakkety with 2.28.1-1ubuntu1. We do have a work-around which is call growpart on the file rather on the loopback device. Recreate script is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1618525/+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 1566930] [NEW] wget does not support IPv6 address with scoped zone (RFC 4007)
Public bug reported: IMPACT: wget is not usable in the default configuration for LXD containers in Xenial Summary: A scoped zone address in the form [%http://[fe80::1%eth0]:13128'. $ lxc exec test -- wget http://www.google.com Error parsing proxy URL http://[fe80::1%eth0]:13128: Invalid IPv6 numeric address. Steps to recreate: - Install lxd 2.0.0~rc8-0ubuntu5 - Launch a conatiner (lxc launch ubuntu-daily:xenial test) - lxc exec test -- wget 'http://www.google.com' These instructions use an LXD environment as an easy way to create a test environment with an IPv6 proxy using a scoped address. ** Affects: wget (Ubuntu) Importance: Critical Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1566930 Title: wget does not support IPv6 address with scoped zone (RFC 4007) Status in wget package in Ubuntu: New Bug description: IMPACT: wget is not usable in the default configuration for LXD containers in Xenial Summary: A scoped zone address in the form [%http://[fe80::1%eth0]:13128'. $ lxc exec test -- wget http://www.google.com Error parsing proxy URL http://[fe80::1%eth0]:13128: Invalid IPv6 numeric address. Steps to recreate: - Install lxd 2.0.0~rc8-0ubuntu5 - Launch a conatiner (lxc launch ubuntu-daily:xenial test) - lxc exec test -- wget 'http://www.google.com' These instructions use an LXD environment as an easy way to create a test environment with an IPv6 proxy using a scoped address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1566930/+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 1566930] Re: wget does not support IPv6 address with scoped zone (RFC 4007)
RFC 4007 : https://www.ietf.org/rfc/rfc4007.txt Discussion upstream : http://lists.gnu.org/archive/html/bug-wget/2009-06/msg0.html Attaching a POC patch from upstream mailing list to demonstrate the fix, but it is hackish. ** Attachment added: "Naive-IPv6-zone-identifier-implementation-for-HTTP" https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1566930/+attachment/4626106/+files/Naive-IPv6-zone-identifier-implementation-for-HTTP -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1566930 Title: wget does not support IPv6 address with scoped zone (RFC 4007) Status in wget package in Ubuntu: New Bug description: IMPACT: wget is not usable in the default configuration for LXD containers in Xenial Summary: A scoped zone address in the form [%http://[fe80::1%eth0]:13128'. $ lxc exec test -- wget http://www.google.com Error parsing proxy URL http://[fe80::1%eth0]:13128: Invalid IPv6 numeric address. Steps to recreate: - Install lxd 2.0.0~rc8-0ubuntu5 - Launch a conatiner (lxc launch ubuntu-daily:xenial test) - lxc exec test -- wget 'http://www.google.com' These instructions use an LXD environment as an easy way to create a test environment with an IPv6 proxy using a scoped address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1566930/+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 1342875] [NEW] Unable to delete currently logged in user
Public bug reported: A user can not delete themselves using the command 'sudo userdel -rf ', this is common in cloud tools that clean up running images prior to capture. A quick test shows that this worked from Precise (didn't look back further) to Raring and stopped working with Saucy. Here's a quick example of the failure (from trusty): # sudo adduser test # sudo usermod -aG sudo test ## As the 'test' user # sudo userdel -rf test userdel: user test is currently used by process 9600 userdel: cannot open /etc/subuid ## User is not removed Previously (output from precise) # sudo userdel -rf test userdel: user test is currently logged in userdel: warning: can't remove /var/mail/test: No such file or directory ## User is removed This is being run as the last command by tools that remove the 'ubuntu' user to clean the image prior to capture. This had previously worked and it is preferable that this could be made to work again. The alternative is removal by root, but the root user on cloud images is locked down and we would not want the user to enable root to run userdel on the risk of it not getting disabled properly prior to image capture. ** Affects: shadow (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1342875 Title: Unable to delete currently logged in user Status in “shadow” package in Ubuntu: New Bug description: A user can not delete themselves using the command 'sudo userdel -rf ', this is common in cloud tools that clean up running images prior to capture. A quick test shows that this worked from Precise (didn't look back further) to Raring and stopped working with Saucy. Here's a quick example of the failure (from trusty): # sudo adduser test # sudo usermod -aG sudo test ## As the 'test' user # sudo userdel -rf test userdel: user test is currently used by process 9600 userdel: cannot open /etc/subuid ## User is not removed Previously (output from precise) # sudo userdel -rf test userdel: user test is currently logged in userdel: warning: can't remove /var/mail/test: No such file or directory ## User is removed This is being run as the last command by tools that remove the 'ubuntu' user to clean the image prior to capture. This had previously worked and it is preferable that this could be made to work again. The alternative is removal by root, but the root user on cloud images is locked down and we would not want the user to enable root to run userdel on the risk of it not getting disabled properly prior to image capture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1342875/+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
