[Touch-packages] [Bug 1829730] [NEW] init hangs when debug is specified
Public bug reported: When specifying "debug" on the kernel command line in order to catch initramfs debug info, the init hangs. It's quite early in the boot process (certainly before pre-mount is called, as I don't see anything relating to btrfs scan and resuming from hibernation). ╰─▶ uname -a Linux regan 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ╰─▶ dpkg -l initramfs-tools 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) ||/ NameVersion Architecture Description +++-===--- ii initramfs-tools 0.133ubuntu2 all generic modular initramfs generator (automation) ╰─▶ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Eoan Ermine (development branch) Release:19.10 Codename: eoan ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Description changed: When specifying "debug" on the kernel command line in order to catch initramfs debug info, the init hangs. It's quite early in the boot process (certainly before pre-mount is called, as I don't see anything relating to btrfs scan and resuming from hibernation). + + ╰─▶ uname -a + Linux regan 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux + + ╰─▶ dpkg -l initramfs-tools + 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) + ||/ NameVersion Architecture Description + +++-===--- + ii initramfs-tools 0.133ubuntu2 all generic modular initramfs generator (automation) + + ╰─▶ lsb_release -a + No LSB modules are available. + Distributor ID: Ubuntu + Description: Ubuntu Eoan Ermine (development branch) + Release: 19.10 + Codename: eoan -- 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/1829730 Title: init hangs when debug is specified Status in initramfs-tools package in Ubuntu: New Bug description: When specifying "debug" on the kernel command line in order to catch initramfs debug info, the init hangs. It's quite early in the boot process (certainly before pre-mount is called, as I don't see anything relating to btrfs scan and resuming from hibernation). ╰─▶ uname -a Linux regan 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ╰─▶ dpkg -l initramfs-tools 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) ||/ NameVersion Architecture Description +++-===--- ii initramfs-tools 0.133ubuntu2 all generic modular initramfs generator (automation) ╰─▶ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Codename: eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1829730/+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 1829726] [NEW] resume after hibernation fails because resume script is never executed
Public bug reported: In recent versions of initramfs-tools-core, the hibernation resume script (/usr/share/initramfs-tools/scripts/local-premount/resume) is no longer +x, so it's silently skipped during boot, causing resume after hibernation to fail. I'm not sure when this change was introduced. All I can see is that it worked fine on 18.04, but that it's broken in current 19.10-dev. ╰─▶ ls -la /usr/share/initramfs-tools/scripts/local-premount/resume -rw-r--r-- 1 root root 1,5K apr 29 09:24 /usr/share/initramfs-tools/scripts/local-premount/resume Unpacking the initramfs confirms this: ╰─▶ unmkinitramfs /boot/initrd.img-5.0.0-13-generic initramfs ╰─▶ ls -la initramfs/main/scripts/local-premount/ total 32K drwxr-xr-x 2 bas bas 4,0K mei 20 10:49 ./ drwxr-xr-x 10 bas bas 4,0K mei 20 10:49 ../ -rw-r--r-- 1 bas bas 246 mei 20 10:29 ORDER -rwxr-xr-x 1 bas bas 270 mrt 12 04:53 btrfs* -rwxr-xr-x 1 bas bas 4,1K apr 29 09:24 fixrtc* -rwxr-xr-x 1 bas bas 226 mei 3 07:49 ntfs_3g* -rw-r--r-- 1 bas bas 1,5K apr 29 09:24 resume ╰─▶ cat initramfs/main/scripts/local-premount/ORDER /scripts/local-premount/btrfs "$@" [ -e /conf/param.conf ] && . /conf/param.conf /scripts/local-premount/fixrtc "$@" [ -e /conf/param.conf ] && . /conf/param.conf /scripts/local-premount/ntfs_3g "$@" [ -e /conf/param.conf ] && . /conf/param.conf ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Summary changed: - resume afte hibernation fails because resume script is never executed + resume after hibernation fails because resume script is never executed -- 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/1829726 Title: resume after hibernation fails because resume script is never executed Status in initramfs-tools package in Ubuntu: New Bug description: In recent versions of initramfs-tools-core, the hibernation resume script (/usr/share/initramfs-tools/scripts/local-premount/resume) is no longer +x, so it's silently skipped during boot, causing resume after hibernation to fail. I'm not sure when this change was introduced. All I can see is that it worked fine on 18.04, but that it's broken in current 19.10-dev. ╰─▶ ls -la /usr/share/initramfs-tools/scripts/local-premount/resume -rw-r--r-- 1 root root 1,5K apr 29 09:24 /usr/share/initramfs-tools/scripts/local-premount/resume Unpacking the initramfs confirms this: ╰─▶ unmkinitramfs /boot/initrd.img-5.0.0-13-generic initramfs ╰─▶ ls -la initramfs/main/scripts/local-premount/ total 32K drwxr-xr-x 2 bas bas 4,0K mei 20 10:49 ./ drwxr-xr-x 10 bas bas 4,0K mei 20 10:49 ../ -rw-r--r-- 1 bas bas 246 mei 20 10:29 ORDER -rwxr-xr-x 1 bas bas 270 mrt 12 04:53 btrfs* -rwxr-xr-x 1 bas bas 4,1K apr 29 09:24 fixrtc* -rwxr-xr-x 1 bas bas 226 mei 3 07:49 ntfs_3g* -rw-r--r-- 1 bas bas 1,5K apr 29 09:24 resume ╰─▶ cat initramfs/main/scripts/local-premount/ORDER /scripts/local-premount/btrfs "$@" [ -e /conf/param.conf ] && . /conf/param.conf /scripts/local-premount/fixrtc "$@" [ -e /conf/param.conf ] && . /conf/param.conf /scripts/local-premount/ntfs_3g "$@" [ -e /conf/param.conf ] && . /conf/param.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1829726/+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 1815742] Re: latest network-manager segfaults in disco
Yes, this version works perfectly. Thanks!
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
Fix Released
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] Re: latest network-manager segfaults in disco
The problem still occurs with the .91 version from disco-proposed.
I'll attach the requested files to the upstream report.
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] Re: latest network-manager segfaults in disco
reopened
** Changed in: network-manager (Ubuntu)
Status: Fix Released => Confirmed
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] Re: latest network-manager segfaults in disco
Unfortunately, NetworkManager is still segfaulting at the same line (src/settings/nm-settings-plugin.c:147) ╰─▶ dpkg -l network-manager|cat 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) ||/ NameVersion Architecture Description +++-===-===--= ii network-manager 1.15.2-0ubuntu2 amd64network management framework (daemon and userspace tools) feb 26 14:15:31 regan systemd[1]: Started Process Core Dump (PID 27019/UID 0). feb 26 14:15:32 regan systemd-coredump[27022]: Process 26991 (NetworkManager) of user 0 dumped core. Stack trace of thread 26991: #0 0x7f566794f077 __GI_raise (libc.so.6) #1 0x7f5667930535 __GI_abort (libc.so.6) #2 0x7f5667efadc3 g_assertion_message (libglib-2.0.so.0) #3 0x7f5667f55b7a g_assertion_message_expr (libglib-2.0.so.0) #4 0x562133f2d6d6 _nm_settings_plugin_emit_signal_connection_added ( #5 0x7f56683e059c initialize (libnm-settings-plugin-ifupdown.so) #6 0x562133ec7d90 add_plugin (NetworkManager) #7 0x562133ecb3a5 add_plugin_load_file (NetworkManager) #8 0x562133d6a0b1 nm_manager_start (NetworkManager) #9 0x562133d2efe9 main (NetworkManager) #10 0x7f566793209b __libc_start_main (libc.so.6) #11 0x562133d2f31a _start (NetworkManager) Stack trace of thread 27006: #0 0x7f5667a22219 syscall (libc.so.6) #1 0x7f5667f78a3a g_cond_wait_until (libglib-2.0.so.0) #2 0x7f5667eff0c1 g_async_queue_pop_intern_unlocked (libglib-2.0.so. #3 0x7f5667f57412 g_thread_pool_wait_for_new_task (libglib-2.0.so.0) #4 0x7f5667f5690d g_thread_proxy (libglib-2.0.so.0) #5 0x7f5667b00164 start_thread (libpthread.so.0) #6 0x7f5667a28def __clone (libc.so.6) Stack trace of thread 27003: #0 0x7f5667a1c6d9 __GI___poll (libc.so.6) #1 0x7f5667f2dc76 g_main_context_poll (libglib-2.0.so.0) #2 0x7f5667f2dd9c g_main_context_iteration (libglib-2.0.so.0) #3 0x7f5667f2dde1 glib_worker_main (libglib-2.0.so.0) #4 0x7f5667f5690d g_thread_proxy (libglib-2.0.so.0) #5 0x7f5667b00164 start_thread (libpthread.so.0) #6 0x7f5667a28def __clone (libc.so.6) Stack trace of thread 27010: #0 0x7f5667a22219 syscall (libc.so.6) #1 0x7f5667f78a3a g_cond_wait_until (libglib-2.0.so.0) #2 0x7f5667eff0c1 g_async_queue_pop_intern_unlocked (libglib-2.0.so. #3 0x7f5667f57412 g_thread_pool_wait_for_new_task (libglib-2.0.so.0) #4 0x7f5667f5690d g_thread_proxy (libglib-2.0.so.0) #5 0x7f5667b00164 start_thread (libpthread.so.0) #6 0x7f5667a28def __clone (libc.so.6) Stack trace of thread 27007: #0 0x7f5667a1c6d9 __GI___poll (libc.so.6)
[Touch-packages] [Bug 1815742] Re: latest network-manager segfaults in disco
** Attachment added: "coredumpctl.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+attachment/5238665/+files/coredumpctl.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] Re: latest network-manager segfaults in disco
It took some effort getting a backtrace (apport didn't pick it up, for
some reason, so I had to resort to systemd-corectl), but anyway, here is
is. I'll add it to the upstream bug, too.
** Attachment added: "backtrace.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+attachment/5238664/+files/backtrace.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] RfKill.txt
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238269/+files/RfKill.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] nmcli-con.txt
apport information
** Attachment added: "nmcli-con.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238272/+files/nmcli-con.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] nmcli-dev.txt
apport information
** Attachment added: "nmcli-dev.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238273/+files/nmcli-dev.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238270/+files/WifiSyslog.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] modified.conffile..etc.NetworkManager.NetworkManager.conf.txt
apport information
** Attachment added:
"modified.conffile..etc.NetworkManager.NetworkManager.conf.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238271/+files/modified.conffile..etc.NetworkManager.NetworkManager.conf.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238267/+files/ProcCpuinfoMinimal.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] NetworkManager.conf.txt
apport information
** Attachment added: "NetworkManager.conf.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238265/+files/NetworkManager.conf.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238268/+files/ProcEnviron.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] PciNetwork.txt
apport information
** Attachment added: "PciNetwork.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238266/+files/PciNetwork.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] NetDevice.virbr1-nic.txt
apport information
** Attachment added: "NetDevice.virbr1-nic.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238262/+files/NetDevice.virbr1-nic.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] NetDevice.wlan0.txt
apport information
** Attachment added: "NetDevice.wlan0.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238264/+files/NetDevice.wlan0.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] NetDevice.vnet0.txt
apport information
** Attachment added: "NetDevice.vnet0.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238263/+files/NetDevice.vnet0.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] NetDevice.virbr1.txt
apport information
** Attachment added: "NetDevice.virbr1.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238261/+files/NetDevice.virbr1.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] NetDevice.virbr0-nic.txt
apport information
** Attachment added: "NetDevice.virbr0-nic.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238260/+files/NetDevice.virbr0-nic.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] NetDevice.ovpn-surf.txt
apport information
** Attachment added: "NetDevice.ovpn-surf.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238257/+files/NetDevice.ovpn-surf.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] NetDevice.tinc0.txt
apport information
** Attachment added: "NetDevice.tinc0.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238258/+files/NetDevice.tinc0.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] NetDevice.virbr0.txt
apport information
** Attachment added: "NetDevice.virbr0.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238259/+files/NetDevice.virbr0.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] IwConfig.txt
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238252/+files/IwConfig.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] NetDevice.lo.txt
apport information
** Attachment added: "NetDevice.lo.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238256/+files/NetDevice.lo.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] Dependencies.txt
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238248/+files/Dependencies.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] NetDevice.eth0.txt
apport information
** Attachment added: "NetDevice.eth0.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238255/+files/NetDevice.eth0.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] NetDevice.docker0.txt
apport information
** Attachment added: "NetDevice.docker0.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238254/+files/NetDevice.docker0.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] NetDevice.br-2c9cac607cd8.txt
apport information
** Attachment added: "NetDevice.br-2c9cac607cd8.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238253/+files/NetDevice.br-2c9cac607cd8.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] IpRoute.txt
apport information
** Attachment added: "IpRoute.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238251/+files/IpRoute.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] IpAddr.txt
apport information
** Attachment added: "IpAddr.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238250/+files/IpAddr.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] IfupdownConfig.txt
apport information
** Attachment added: "IfupdownConfig.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238249/+files/IfupdownConfig.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] CRDA.txt
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238247/+files/CRDA.txt
--
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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] [NEW] latest network-manager segfaults in disco
Public bug reported:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version in
cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612] ifupdown:
management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process exited,
code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI
WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-collected disco
** Attachment added: "network-manager journal output during upgrade"
https://bugs.launchpad.net/bugs/1815742/+attachment/5238246/+files/journal.txt
** Tags added: apport-collected disco
** Description changed:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version in
cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu20
+ Architecture: amd64
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 19.04
+ InstallationDate: Installed on 2016-12-22 (782 days ago)
+ InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
+ NetworkManager.state:
+ [main]
+ NetworkingEnabled=true
+ WirelessEnabled=true
+ WWANEnabled=true
+ Package: network-manager 1.12.4-1ubuntu1.2
+ PackageArchitecture: amd64
+ Tags: disco
+ Uname: Linux 4.19.0-1-amd64 x86_64
+ UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
+ UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
+ _MarkForUpload: True
+ mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
+ nmcli-nm:
+ RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
+ running 1.12.4 connected started full enabled enabled
enabled 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/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
New
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows
[Touch-packages] [Bug 1751006] [NEW] Journalctl compiled without pattern matching support
Public bug reported: Please add pattern matching support to journalctl. At the moment, the -g (--grep) option as described in the man page doesn't work: ╰─▶ journalctl --grep=xhci-hcd Compiled without pattern matching support ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1751006 Title: Journalctl compiled without pattern matching support Status in systemd package in Ubuntu: New Bug description: Please add pattern matching support to journalctl. At the moment, the -g (--grep) option as described in the man page doesn't work: ╰─▶ journalctl --grep=xhci-hcd Compiled without pattern matching support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1751006/+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 1750763] [NEW] local-premount/resume script broken, resume fails
Public bug reported:
On bionic, the initramfs pre-mount/resume script contains this call to
/bin/resume:
/bin/resume ${DEV}
Unfortunately, the ${DEV} variable is never set, causing all resumes to fail,
with this error in initramfs.debug:
+ /scripts/local-premount/resume
+ PREREQ=
+ [ -z UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 ]
+ [ ! -e /sys/power/resume ]
+ . /scripts/functions
+ . /scripts/local
+ wait-for-root UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 5
+ SWAPTYPE=swsuspend
+ [ -x /bin/plymouth ]
+ plymouth --ping
+ [ -n ]
+ /bin/resume
Usage: /bin/resume /dev/ [offset]
This seems a porting bug: the Debian version
(https://anonscm.debian.org/cgit/kernel/initramfs-tools.git/tree/scripts
/local-premount/resume) calls local_device_setup(), whioch sets DEV.
This call is missing in the Ubuntu (bionic, 0.130ubuntu2) version.
In my case, a simple
DEV=$(resolve_device "${resume}")
also solved the issue, but I guess the Debian solution is nicer.
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
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/1750763
Title:
local-premount/resume script broken, resume fails
Status in initramfs-tools package in Ubuntu:
New
Bug description:
On bionic, the initramfs pre-mount/resume script contains this call to
/bin/resume:
/bin/resume ${DEV}
Unfortunately, the ${DEV} variable is never set, causing all resumes to fail,
with this error in initramfs.debug:
+ /scripts/local-premount/resume
+ PREREQ=
+ [ -z UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 ]
+ [ ! -e /sys/power/resume ]
+ . /scripts/functions
+ . /scripts/local
+ wait-for-root UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 5
+ SWAPTYPE=swsuspend
+ [ -x /bin/plymouth ]
+ plymouth --ping
+ [ -n ]
+ /bin/resume
Usage: /bin/resume /dev/ [offset]
This seems a porting bug: the Debian version
(https://anonscm.debian.org/cgit/kernel/initramfs-
tools.git/tree/scripts/local-premount/resume) calls
local_device_setup(), whioch sets DEV. This call is missing in the
Ubuntu (bionic, 0.130ubuntu2) version.
In my case, a simple
DEV=$(resolve_device "${resume}")
also solved the issue, but I guess the Debian solution is nicer.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1750763/+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 1697789] Re: Xorg: page allocation failure: order:0, mode:0x14210d2(GFP_HIGHUSER|__GFP_NORETRY|__GFP_RECLAIMABLE), nodemask=(null)
I'm seeing the same, also with kernel 4.12 -- 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/1697789 Title: Xorg: page allocation failure: order:0, mode:0x14210d2(GFP_HIGHUSER|__GFP_NORETRY|__GFP_RECLAIMABLE), nodemask=(null) Status in X.Org X server: Unknown Status in xorg package in Ubuntu: Confirmed Status in xorg-server package in Arch Linux: New Bug description: dmesg: [23559.058500] Xorg: page allocation failure: order:0, mode:0x14210d2(GFP_HIGHUSER|__GFP_NORETRY|__GFP_RECLAIMABLE), nodemask=(null) [23559.058509] Xorg cpuset=/ mems_allowed=0 [23559.058516] CPU: 1 PID: 1797 Comm: Xorg Not tainted 4.12.0-041200rc5-generic #201706112031 [23559.058517] Hardware name: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/SAMSUNG_NP1234567890, BIOS P14AAJ 04/15/2013 [23559.058519] Call Trace: [23559.058528] dump_stack+0x63/0x8d [23559.058532] warn_alloc+0x114/0x1c0 [23559.058535] __alloc_pages_slowpath+0xe07/0xe10 [23559.058539] __alloc_pages_nodemask+0x233/0x250 [23559.058543] alloc_pages_vma+0xab/0x250 [23559.058547] shmem_alloc_page+0x70/0xc0 [23559.058550] ? __radix_tree_insert+0x45/0x220 [23559.058553] ? __vm_enough_memory+0x29/0x130 [23559.058555] shmem_alloc_and_acct_page+0x72/0x1b0 [23559.058558] ? find_get_entry+0x1e/0xc0 [23559.058561] shmem_getpage_gfp+0x195/0xbd0 [23559.058564] shmem_read_mapping_page_gfp+0x44/0x80 [23559.058611] i915_gem_object_get_pages_gtt+0x204/0x5a0 [i915] [23559.058643] i915_gem_object_get_pages+0x20/0x60 [i915] [23559.058673] __i915_gem_object_get_pages+0x5c/0x70 [i915] [23559.058706] __i915_vma_do_pin+0x1c6/0x3a0 [i915] [23559.058737] i915_gem_execbuffer_reserve_vma.isra.29+0x14d/0x1b0 [i915] [23559.058765] i915_gem_execbuffer_reserve.isra.30+0x3b7/0x3e0 [i915] [23559.058794] i915_gem_do_execbuffer.isra.36+0x577/0x16c0 [i915] [23559.058799] ? unix_stream_recvmsg+0x54/0x70 [23559.058801] ? unix_state_double_lock+0x70/0x70 [23559.058830] i915_gem_execbuffer2+0x96/0x1b0 [i915] [23559.058849] drm_ioctl+0x216/0x4c0 [drm] [23559.058877] ? i915_gem_execbuffer+0x2f0/0x2f0 [i915] [23559.058881] ? __remove_hrtimer+0x3c/0x70 [23559.058885] do_vfs_ioctl+0xa3/0x600 [23559.05] ? do_setitimer+0xe0/0x240 [23559.058891] ? SyS_setitimer+0xf1/0x120 [23559.058894] SyS_ioctl+0x79/0x90 [23559.058897] entry_SYSCALL_64_fastpath+0x1e/0xa9 [23559.058900] RIP: 0033:0x7fd8c5c7e987 [23559.058901] RSP: 002b:7ffd494ac738 EFLAGS: 0246 ORIG_RAX: 0010 [23559.058904] RAX: ffda RBX: 0006 RCX: 7fd8c5c7e987 [23559.058905] RDX: 7ffd494ac790 RSI: 40406469 RDI: 000c [23559.058907] RBP: 0028 R08: 0001 R09: 000c [23559.058908] R10: 0001 R11: 0246 R12: 0040 [23559.058909] R13: 0008 R14: 5581c086a6c0 R15: [23559.058912] Mem-Info: [23559.058918] active_anon:1016643 inactive_anon:298858 isolated_anon:0 active_file:395940 inactive_file:1147459 isolated_file:0 unevictable:129 dirty:124022 writeback:21146 unstable:0 slab_reclaimable:57926 slab_unreclaimable:23062 mapped:283483 shmem:248113 pagetables:23247 bounce:0 free:29069 free_pcp:245 free_cma:0 [23559.058923] Node 0 active_anon:4066572kB inactive_anon:1195432kB active_file:1583760kB inactive_file:4589836kB unevictable:516kB isolated(anon):0kB isolated(file):0kB mapped:1133932kB dirty:496088kB writeback:84584kB shmem:992452kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 976896kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no [23559.058924] Node 0 DMA free:15360kB min:84kB low:104kB high:124kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15984kB managed:15360kB mlocked:0kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB [23559.058930] lowmem_reserve[]: 0 3226 11726 11726 11726 [23559.058935] Node 0 DMA32 free:52176kB min:18568kB low:23208kB high:27848kB active_anon:718716kB inactive_anon:177564kB active_file:228516kB inactive_file:2067540kB unevictable:0kB writepending:203112kB present:3438520kB managed:3354852kB mlocked:0kB slab_reclaimable:98764kB slab_unreclaimable:3004kB kernel_stack:576kB pagetables:4384kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB [23559.058941] lowmem_reserve[]: 0 0 8500 8500 8500 [23559.058945] Node 0 Normal free:48740kB min:48924kB low:61152kB high:73380kB active_anon:3347648kB inactive_anon:1017448kB active_file:1354180kB inactive_file:2521736kB unevictable:516kB writepending:377444kB present:8902656kB managed:8704148kB mlocked:516kB slab
[Touch-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook
I can confirm that everything works as expected on Zesty. -- 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/1590590 Title: Touchpad not recognized on Dell Latitude E7470 Ultrabook Status in linux package in Ubuntu: Triaged Status in systemd package in Ubuntu: Fix Released Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Status in linux source package in Xenial: New Status in systemd source package in Xenial: New Status in xserver-xorg-input-synaptics source package in Xenial: New Status in linux source package in Yakkety: New Status in systemd source package in Yakkety: New Status in xserver-xorg-input-synaptics source package in Yakkety: New Bug description: Expected: Touchpad settings available in Mouse & Touchpad Settings dialog Actual result: Touchpad settings missing entirely Details: The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. The settings for the touchpad are not available at all in the Mouse and Touchpad settings (see http://i.imgur.com/YRGiOrj.png). Two-finger scrolling works as expected except it's using "Natural Scrolling" by default and there is no way to change it. xinput list does not display a touchpad at all: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎜ ↳ ImPS/2 Generic Wheel Mouse id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_FHD id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ Dell WMI hotkeysid=14 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] /proc/bus/input/devices lists the device as a "Generic Wheel Mouse" Output of `lsb_release -rd`: Description: Ubuntu 16.04 LTS Release: 16.04 xserver-xorg-input-synaptics version information: xserver-xorg-input-synaptics: Installed: 1.8.2-1ubuntu3 Candidate: 1.8.2-1ubuntu3 Version table: *** 1.8.2-1ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+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 1653495] Re: systemd-resolved breaks Steam
** Attachment added: "packet capture when using resolved" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1653495/+attachment/4799004/+files/dns-resolved.pcap -- 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/1653495 Title: systemd-resolved breaks Steam Status in systemd package in Ubuntu: New Bug description: When systemd-resolved is active and /etc/resolv.conf points to 127.0.0.53, steam fails to resolve domain names, and refuses to update or install games. Often, it doesn't even start, because it wants to update itself, but cannot reach its content servers. Manually (dig/host/nslookup/etc), resolving works fine, and also Chrome etc do'nt show any problems. It seems Steam uses some uncommon type of DNS records or so? If I change the nameserver in /etc/resolv.conf to 8.8.8.8, of to my local resolver, everything works fine again. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-8 ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0 Uname: Linux 4.9.0-11-generic x86_64 ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jan 2 11:04:03 2017 InstallationDate: Installed on 2016-12-22 (10 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude E7470 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-11-generic.efi.signed root=/dev/mapper/hostname-root ro nosplash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.3:bd11/09/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.systemd.resolved.conf: 2016-12-27T13:33:33.754548 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1653495/+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 1653495] Re: systemd-resolved breaks Steam
I'm attaching DNS logs of a steam session using systemd-resolved, and of one using Google directly. ** Attachment added: "dns packet capture without resoled" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1653495/+attachment/4799003/+files/dns-google.pcap -- 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/1653495 Title: systemd-resolved breaks Steam Status in systemd package in Ubuntu: New Bug description: When systemd-resolved is active and /etc/resolv.conf points to 127.0.0.53, steam fails to resolve domain names, and refuses to update or install games. Often, it doesn't even start, because it wants to update itself, but cannot reach its content servers. Manually (dig/host/nslookup/etc), resolving works fine, and also Chrome etc do'nt show any problems. It seems Steam uses some uncommon type of DNS records or so? If I change the nameserver in /etc/resolv.conf to 8.8.8.8, of to my local resolver, everything works fine again. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-8 ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0 Uname: Linux 4.9.0-11-generic x86_64 ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jan 2 11:04:03 2017 InstallationDate: Installed on 2016-12-22 (10 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude E7470 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-11-generic.efi.signed root=/dev/mapper/hostname-root ro nosplash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.3:bd11/09/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.systemd.resolved.conf: 2016-12-27T13:33:33.754548 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1653495/+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 1653495] [NEW] systemd-resolved breaks Steam
Public bug reported: When systemd-resolved is active and /etc/resolv.conf points to 127.0.0.53, steam fails to resolve domain names, and refuses to update or install games. Often, it doesn't even start, because it wants to update itself, but cannot reach its content servers. Manually (dig/host/nslookup/etc), resolving works fine, and also Chrome etc do'nt show any problems. It seems Steam uses some uncommon type of DNS records or so? If I change the nameserver in /etc/resolv.conf to 8.8.8.8, of to my local resolver, everything works fine again. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-8 ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0 Uname: Linux 4.9.0-11-generic x86_64 ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jan 2 11:04:03 2017 InstallationDate: Installed on 2016-12-22 (10 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude E7470 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-11-generic.efi.signed root=/dev/mapper/hostname-root ro nosplash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.3:bd11/09/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.systemd.resolved.conf: 2016-12-27T13:33:33.754548 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed zesty -- 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/1653495 Title: systemd-resolved breaks Steam Status in systemd package in Ubuntu: New Bug description: When systemd-resolved is active and /etc/resolv.conf points to 127.0.0.53, steam fails to resolve domain names, and refuses to update or install games. Often, it doesn't even start, because it wants to update itself, but cannot reach its content servers. Manually (dig/host/nslookup/etc), resolving works fine, and also Chrome etc do'nt show any problems. It seems Steam uses some uncommon type of DNS records or so? If I change the nameserver in /etc/resolv.conf to 8.8.8.8, of to my local resolver, everything works fine again. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-8 ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0 Uname: Linux 4.9.0-11-generic x86_64 ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jan 2 11:04:03 2017 InstallationDate: Installed on 2016-12-22 (10 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude E7470 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-11-generic.efi.signed root=/dev/mapper/hostname-root ro nosplash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.3:bd11/09/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.systemd.resolved.conf: 2016-12-27T13:33:33.754548 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1653495/+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 1533833] Re: unprivileged lxc containers won't start, need to put sessions into "pids" cgroup controller
strangely enough, adding the aa_allow_incomplete option doesn't seem to make a difference; container startup keeps failing at the same point. In any case, it does seem to initialize the container correctly, and I seem to hit a different issue. The entire cgroup thing seems to work now, at least: lxc-start 1455916829.396 INFO lxc_start - start.c:lxc_init:474 - 'aansluitform-deploy' is initialized lxc-start 1455916829.396 DEBUGlxc_start - start.c:__lxc_start:1186 - Not dropping cap_sys_boot or watching utmp lxc-start 1455916829.396 INFO lxc_start - start.c:resolve_clone_flags:883 - Cloning a new user namespace lxc-start 1455916829.396 INFO lxc_cgroup - cgroup.c:cgroup_init:65 - cgroup driver cgmanager initing for aansluitform-deploy lxc-start 1455916829.507 NOTICE lxc_start - start.c:do_start:699 - switching to gid/uid 0 in new user namespace lxc-start 1455916829.509 DEBUGlxc_conf - conf.c:setup_rootfs:1295 - mounted '/home/bas/.local/share/lxc/aansluitform-deploy/rootfs' on '/usr/lib/x86_64-linux-gnu/lxc' lxc-start 1455916829.509 INFO lxc_conf - conf.c:setup_utsname:928 - 'aansluitform-deploy' hostname has been setup lxc-start 1455916829.509 DEBUGlxc_conf - conf.c:setup_netdev:2595 - 'eth0' has been setup lxc-start 1455916829.509 INFO lxc_conf - conf.c:setup_network:2616 - network has been setup lxc-start 1455916829.509 INFO lxc_conf - conf.c:mount_autodev:1157 - Mounting container /dev lxc-start 1455916829.509 INFO lxc_conf - conf.c:mount_autodev:1179 - Mounted tmpfs onto /usr/lib/x86_64-linux-gnu/lxc/dev lxc-start 1455916829.509 INFO lxc_conf - conf.c:mount_autodev:1197 - Mounted container /dev which seems to pass the point where it failed before. A little bit later, it now fails with lxc-start 1455916829.616 WARN lxc_apparmor - lsm/apparmor.c:apparmor_process_label_set:167 - Incomplete AppArmor support in your kernel lxc-start 1455916829.616 ERRORlxc_apparmor - lsm/apparmor.c:apparmor_process_label_set:183 - No such file or directory - failed to change apparmor profile to lxc-container-default lxc-start 1455916829.616 ERRORlxc_sync - sync.c:__sync_wait:51 - invalid sequence number 1. expected 4 lxc-start 1455916829.616 ERRORlxc_start - start.c:__lxc_start:1213 - failed to spawn 'aansluitform-deploy' lxc-start 1455916829.616 WARN lxc_commands - commands.c:lxc_cmd_rsp_recv:172 - command get_init_pid failed to receive response lxc-start 1455916829.616 WARN lxc_cgmanager - cgmanager.c:cgm_get:994 - do_cgm_get exited with error lxc-start 1455916829.616 ERRORlxc_cgmanager - cgmanager.c:cgm_remove_cgroup:523 - call to cgmanager_remove_sync failed: invalid request lxc-start 1455916829.616 ERRORlxc_cgmanager - cgmanager.c:cgm_remove_cgroup:525 - Error removing all:lxc/aansluitform-deploy-10 lxc-start 1455916834.621 ERRORlxc_start_ui - lxc_start.c:main:344 - The container failed to start. lxc-start 1455916834.621 ERRORlxc_start_ui - lxc_start.c:main:346 - To get more details, run the container in foreground mode. lxc-start 1455916834.621 ERRORlxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options. even if the apparmor setting is set in the config file. -- 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/1533833 Title: unprivileged lxc containers won't start, need to put sessions into "pids" cgroup controller Status in lxc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in lxc source package in Wily: New Status in systemd source package in Wily: Fix Committed Bug description: I'n trying to get (unpriviliged) lxc containers to run on wily. I create a container like this: > lxc-create -t download -n u1 -- -d ubuntu -r wily -a amd64 that works. However, starting the container fails: > lxc-start -n u1 lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. Setting the log priority to debug shows the following (relevant part only): lxc-start 1452717530.484 INFO lxc_start - start.c:lxc_init:474 - 'u1' is initialized lxc-start 1452717530.484 DEBUGlxc_start - start.c:__lxc_start:1186 - Not dropping cap_sys_boot or watching utmp lxc-start 1452717530.484 INFO lxc_start - start.c:resolve_clone_flags:883 - Cloning a new user namespace lxc-start 1452717530.484 INFO lxc_cgroup - cgroup.c:c
[Touch-packages] [Bug 1533833] Re: unprivileged lxc containers won't start, need to put sessions into "pids" cgroup controller
I've downgraded systemd to 225-1ubuntu9.1 from wily/proposed. Kernel is still linux-image-4.5.0-040500rc4-generic and lxc is 1.1.5-0ubuntu0.15.10.3 from wily-updates. Unfortunately, when I now start the lxc container, I seem to hit a different bug. I get: lxc-start 1455870309.289 INFO lxc_conf - conf.c:setup_tty:1080 - 4 tty(s) has been setup lxc-start 1455870309.289 INFO lxc_conf - conf.c:setup_personality:1473 - set personality to '0x0' lxc-start 1455870309.289 DEBUGlxc_conf - conf.c:setup_caps:2279 - drop capability 'mac_admin' (33) lxc-start 1455870309.289 DEBUGlxc_conf - conf.c:setup_caps:2279 - drop capability 'mac_override' (32) lxc-start 1455870309.289 DEBUGlxc_conf - conf.c:setup_caps:2279 - drop capability 'sys_time' (25) lxc-start 1455870309.289 DEBUGlxc_conf - conf.c:setup_caps:2279 - drop capability 'sys_module' (16) lxc-start 1455870309.289 DEBUGlxc_conf - conf.c:setup_caps:2288 - capabilities have been setup lxc-start 1455870309.289 NOTICE lxc_conf - conf.c:lxc_setup:4026 - 'aansluitform-deploy' is setup. lxc-start 1455870309.289 WARN lxc_apparmor - lsm/apparmor.c:apparmor_process_label_set:167 - Incomplete AppArmor support in your kernel lxc-start 1455870309.289 ERRORlxc_apparmor - lsm/apparmor.c:apparmor_process_label_set:169 - If you really want to start this container, set lxc-start 1455870309.289 ERRORlxc_apparmor - lsm/apparmor.c:apparmor_process_label_set:170 - lxc.aa_allow_incomplete = 1 lxc-start 1455870309.289 ERRORlxc_apparmor - lsm/apparmor.c:apparmor_process_label_set:171 - in your container configuration file lxc-start 1455870309.289 ERRORlxc_sync - sync.c:__sync_wait:51 - invalid sequence number 1. expected 4 lxc-start 1455870309.289 ERRORlxc_start - start.c:__lxc_start:1213 - failed to spawn 'aansluitform-deploy' lxc-start 1455870309.290 ERRORlxc_cgmanager - cgmanager.c:cgm_remove_cgroup:523 - call to cgmanager_remove_sync failed: invalid request lxc-start 1455870309.290 ERRORlxc_cgmanager - cgmanager.c:cgm_remove_cgroup:525 - Error removing all:lxc/aansluitform-deploy-8 lxc-start 1455870309.317 WARN lxc_commands - commands.c:lxc_cmd_rsp_recv:172 - command get_init_pid failed to receive response lxc-start 1455870309.317 WARN lxc_cgmanager - cgmanager.c:cgm_get:994 - do_cgm_get exited with error lxc-start 1455870314.321 ERRORlxc_start_ui - lxc_start.c:main:344 - The container failed to start. lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start 1455870314.321 ERRORlxc_start_ui - lxc_start.c:main:346 - To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode. lxc-start 1455870314.321 ERRORlxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. When adding the suggested apparmor parameter to the config file, the apparmor error disappear, but the cgmanager errors are identical (but different than before)... Any ideas? -- 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/1533833 Title: unprivileged lxc containers won't start, need to put sessions into "pids" cgroup controller Status in lxc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in lxc source package in Wily: New Status in systemd source package in Wily: Fix Committed Bug description: I'n trying to get (unpriviliged) lxc containers to run on wily. I create a container like this: > lxc-create -t download -n u1 -- -d ubuntu -r wily -a amd64 that works. However, starting the container fails: > lxc-start -n u1 lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. Setting the log priority to debug shows the following (relevant part only): lxc-start 1452717530.484 INFO lxc_start - start.c:lxc_init:474 - 'u1' is initialized lxc-start 1452717530.484 DEBUGlxc_start - start.c:__lxc_start:1186 - Not dropping cap_sys_boot or watching utmp lxc-start 1452717530.484 INFO lxc_start - start.c:resolve_clone_flags:883 - Cloning a new user namespace lxc-start 1452717530.484 INFO lxc_cgroup - cgroup.c:cgroup_init:65 - cgroup driver cg
[Touch-packages] [Bug 1533833] Re: unprivileged lxc containers won't start, need to put sessions into "pids" cgroup controller
This was systemd and kernel from xenial. I'll try again tomorrov with the wily-proposed systemd and xenial kernel. -- 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/1533833 Title: unprivileged lxc containers won't start, need to put sessions into "pids" cgroup controller Status in lxc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in lxc source package in Wily: New Status in systemd source package in Wily: Fix Committed Bug description: I'n trying to get (unpriviliged) lxc containers to run on wily. I create a container like this: > lxc-create -t download -n u1 -- -d ubuntu -r wily -a amd64 that works. However, starting the container fails: > lxc-start -n u1 lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. Setting the log priority to debug shows the following (relevant part only): lxc-start 1452717530.484 INFO lxc_start - start.c:lxc_init:474 - 'u1' is initialized lxc-start 1452717530.484 DEBUGlxc_start - start.c:__lxc_start:1186 - Not dropping cap_sys_boot or watching utmp lxc-start 1452717530.484 INFO lxc_start - start.c:resolve_clone_flags:883 - Cloning a new user namespace lxc-start 1452717530.484 INFO lxc_cgroup - cgroup.c:cgroup_init:65 - cgroup driver cgmanager initing for u1 lxc-start 1452717530.489 ERRORlxc_cgmanager - cgmanager.c:lxc_cgmanager_enter:698 - call to cgmanager_move_pid_sync failed: invalid request lxc-start: cgmanager.c: lxc_cgmanager_enter: 698 call to cgmanager_move_pid_sync failed: invalid request lxc-start 1452717530.490 ERRORlxc_start - start.c:__lxc_start:1213 - failed to spawn 'u1' lxc-start: start.c: __lxc_start: 1213 failed to spawn 'u1' lxc-start 1452717530.513 ERRORlxc_start_ui - lxc_start.c:main:344 - The container failed to start. lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start 1452717530.513 ERRORlxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. lxc-start 1452717530.484 INFO lxc_start - start.c:lxc_init:474 - 'u1' is initialized lxc-start 1452717530.484 DEBUGlxc_start - start.c:__lxc_start:1186 - Not dropping cap_sys_boot or watching utmp lxc-start 1452717530.484 INFO lxc_start - start.c:resolve_clone_flags:883 - Cloning a new user namespace lxc-start 1452717530.484 INFO lxc_cgroup - cgroup.c:cgroup_init:65 - cgroup driver cgmanager initing for u1 lxc-start 1452717530.489 ERRORlxc_cgmanager - cgmanager.c:lxc_cgmanager_enter:698 - call to cgmanager_move_pid_sync failed: invalid request lxc-start: cgmanager.c: lxc_cgmanager_enter: 698 call to cgmanager_move_pid_sync failed: invalid request lxc-start 1452717530.490 ERRORlxc_start - start.c:__lxc_start:1213 - failed to spawn 'u1' lxc-start: start.c: __lxc_start: 1213 failed to spawn 'u1' lxc-start 1452717530.513 ERRORlxc_start_ui - lxc_start.c:main:344 - The container failed to start. lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start 1452717530.513 ERRORlxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. So it seems a cgmanager issue. Syslog shows: Jan 13 21:37:58 miranda cgmanager[22010]: cgmanager:do_create_main: pid 25615 (uid 1000 gid 1000) may not create under /run/cgmanager/fs/pids Jan 13 21:37:58 miranda cgmanager[22010]: cgmanager: Invalid path /run/cgmanager/fs/pids/lxc/u1 Jan 13 21:37:58 miranda cgmanager[22010]: cgmanager:per_ctrl_move_pid_main: Invalid path /run/cgmanager/fs/pids/lxc/u1 Jan 13 21:38:50 miranda cgmanager[22010]: cgmanager:do_create_main: pid 25632 (uid 1000 gid 1000) may not create under /run/cgmanager/fs/pids Jan 13 21:38:50 miranda cgmanager[22010]: cgmanager: Invalid path /run/cgmanager/fs/pids/lxc/u1 Jan 13 21:38:50 miranda cgmanager[22010]: cgmanager:per_ctrl_move_pid_main: Invalid path /run/cgmanager/fs/pids/lxc/u1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1533833/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-pack
[Touch-packages] [Bug 1533833] Re: unprivileged lxc containers won't start, need to put sessions into "pids" cgroup controller
I've just tried with an upstream 4.5.0-rc4 kernel (which does boot on my laptop). Unfortunately, it doesn't work yet. linux-image linux-image-4.5.0-040500rc4-generic systemd 229-1ubuntu2 lxc 1.1.5-0ubuntu0.15.10.3 starting a container gives: lxc-start 1455712091.086 DEBUGlxc_console - console.c:lxc_console_peer_default:536 - no console peer lxc-start 1455712091.092 INFO lxc_monitor - monitor.c:lxc_monitor_sock_name:178 - using monitor sock name lxc/1139bd77ce7a3a6c//home/bas/.local/share/lxc lxc-start 1455712091.132 INFO lxc_start - start.c:lxc_init:474 - 'aansluitform-deploy' is initialized lxc-start 1455712091.132 DEBUGlxc_start - start.c:__lxc_start:1186 - Not dropping cap_sys_boot or watching utmp lxc-start 1455712091.133 INFO lxc_start - start.c:resolve_clone_flags:883 - Cloning a new user namespace lxc-start 1455712091.133 INFO lxc_cgroup - cgroup.c:cgroup_init:65 - cgroup driver cgmanager initing for aansluitform-deploy lxc-start 1455712091.138 ERRORlxc_cgmanager - cgmanager.c:lxc_cgmanager_enter:698 - call to cgmanager_move_pid_sync failed: invalid request lxc-start 1455712091.138 ERRORlxc_start - start.c:__lxc_start:1213 - failed to spawn 'aansluitform-deploy' lxc-start 1455712091.163 WARN lxc_commands - commands.c:lxc_cmd_rsp_recv:172 - command get_init_pid failed to receive response lxc-start 1455712091.164 WARN lxc_cgmanager - cgmanager.c:cgm_get:994 - do_cgm_get exited with error lxc-start 1455712096.169 ERRORlxc_start_ui - lxc_start.c:main:344 - The container failed to start. -- 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/1533833 Title: unprivileged lxc containers won't start, need to put sessions into "pids" cgroup controller Status in lxc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in lxc source package in Wily: New Status in systemd source package in Wily: Fix Committed Bug description: I'n trying to get (unpriviliged) lxc containers to run on wily. I create a container like this: > lxc-create -t download -n u1 -- -d ubuntu -r wily -a amd64 that works. However, starting the container fails: > lxc-start -n u1 lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. Setting the log priority to debug shows the following (relevant part only): lxc-start 1452717530.484 INFO lxc_start - start.c:lxc_init:474 - 'u1' is initialized lxc-start 1452717530.484 DEBUGlxc_start - start.c:__lxc_start:1186 - Not dropping cap_sys_boot or watching utmp lxc-start 1452717530.484 INFO lxc_start - start.c:resolve_clone_flags:883 - Cloning a new user namespace lxc-start 1452717530.484 INFO lxc_cgroup - cgroup.c:cgroup_init:65 - cgroup driver cgmanager initing for u1 lxc-start 1452717530.489 ERRORlxc_cgmanager - cgmanager.c:lxc_cgmanager_enter:698 - call to cgmanager_move_pid_sync failed: invalid request lxc-start: cgmanager.c: lxc_cgmanager_enter: 698 call to cgmanager_move_pid_sync failed: invalid request lxc-start 1452717530.490 ERRORlxc_start - start.c:__lxc_start:1213 - failed to spawn 'u1' lxc-start: start.c: __lxc_start: 1213 failed to spawn 'u1' lxc-start 1452717530.513 ERRORlxc_start_ui - lxc_start.c:main:344 - The container failed to start. lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start 1452717530.513 ERRORlxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. lxc-start 1452717530.484 INFO lxc_start - start.c:lxc_init:474 - 'u1' is initialized lxc-start 1452717530.484 DEBUGlxc_start - start.c:__lxc_start:1186 - Not dropping cap_sys_boot or watching utmp lxc-start 1452717530.484 INFO lxc_start - start.c:resolve_clone_flags:883 - Cloning a new user namespace lxc-start 1452717530.484 INFO lxc_cgroup - cgroup.c:cgroup_init:65 - cgroup driver cgmanager initing for u1 lxc-start 1452717530.489 ERRORlxc_cgmanager - cgmanager.c:lxc_cgmanager_enter:698 - call to cgmanager_move_pid_sync failed: invalid request lxc-start: cgmanager.c: lxc_cgmanager_enter: 698 call to cgmanager_move_pid_sync failed: invalid request lxc-start 1452717530.490 ERRORlxc_start - start.c:__lxc_start:1213 - failed to spawn 'u1'
Re: [Touch-packages] [Bug 1533833] Re: unprivileged lxc containers won't start, need to put sessions into "pids" cgroup controller
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Martin, > On 11-02-16 10:24, Martin Pitt wrote: >> Bas, any chance to test the update in -proposed so that we can >> release that? > > I'll try to test it later this week, if that's ok. Unfortunately, the xenial 4.4 kernel won't boot for me at the moment (keyboard doesn't work while inputting disk decryption key), so I can't test if thisis fixed... Gr, Bas. -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJWw4LgAAoJENGDpRe/qY3mp+QQAM5EESKhWB5MjZUn3cvDh+ku IGKEqKjDg+luKuHxvHHiXh1KNNCdHCffko33Qa2LSMsivX1WHNocN+n7Hvv1Wq0N DmUHqth5b+BefemEF+sfJVz+gyV6W9r37QtJxKbjb8pUr05vnlzdMma7qF9qkZmv rA+bOQbjP20JSuohWvMM0tRC9+gNX4GBiZYD/8Ac3WGMLA8l2FNXjnCrWFgyb+oF hhPcgudcv9L2JAx+7JlXs7oNMoXjQ57k/d1dIQW+uyGL/24X2CV1btcEmznowYMo lYZPP99i3PpsmhnhwAd+VYYPd1o1052HfkEYIx/dVMoK5usxgpcwl5wsdgFLaTog hpPA/poC7RCIFdGpXFt31dhjQMIOR4mQ41NiuJtPxXrp5H3Bu5Q0bCgq3o5WJMNw 85bzJ5uxE3cGFDSeeBb/j8gxeK1yW1hqP5t051f40C98sfX4hyOyZmuKLyakKyW9 I/h8kQOFaLFi8MlmcV6MnA0E66nIO5J+ODWeSmdAeMLWAzA9b911YfecCB8PMboq RtR/ddc0/cttmtDWgQ8sz3lO7d2vNwzWqMIJW2qDy4IexK9jOIlHiOw9CLuJdjqm f2sfZZWhNjeGIddAJ0tZB6TKmCHuZ07XYeaiyOaFTGSTF5MhDmPtyV7/51d6pOU4 QqbgijCYBiyM1m04NNep =HBJX -END PGP SIGNATURE- -- 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/1533833 Title: unprivileged lxc containers won't start, need to put sessions into "pids" cgroup controller Status in lxc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in lxc source package in Wily: New Status in systemd source package in Wily: Fix Committed Bug description: I'n trying to get (unpriviliged) lxc containers to run on wily. I create a container like this: > lxc-create -t download -n u1 -- -d ubuntu -r wily -a amd64 that works. However, starting the container fails: > lxc-start -n u1 lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. Setting the log priority to debug shows the following (relevant part only): lxc-start 1452717530.484 INFO lxc_start - start.c:lxc_init:474 - 'u1' is initialized lxc-start 1452717530.484 DEBUGlxc_start - start.c:__lxc_start:1186 - Not dropping cap_sys_boot or watching utmp lxc-start 1452717530.484 INFO lxc_start - start.c:resolve_clone_flags:883 - Cloning a new user namespace lxc-start 1452717530.484 INFO lxc_cgroup - cgroup.c:cgroup_init:65 - cgroup driver cgmanager initing for u1 lxc-start 1452717530.489 ERRORlxc_cgmanager - cgmanager.c:lxc_cgmanager_enter:698 - call to cgmanager_move_pid_sync failed: invalid request lxc-start: cgmanager.c: lxc_cgmanager_enter: 698 call to cgmanager_move_pid_sync failed: invalid request lxc-start 1452717530.490 ERRORlxc_start - start.c:__lxc_start:1213 - failed to spawn 'u1' lxc-start: start.c: __lxc_start: 1213 failed to spawn 'u1' lxc-start 1452717530.513 ERRORlxc_start_ui - lxc_start.c:main:344 - The container failed to start. lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start 1452717530.513 ERRORlxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. lxc-start 1452717530.484 INFO lxc_start - start.c:lxc_init:474 - 'u1' is initialized lxc-start 1452717530.484 DEBUGlxc_start - start.c:__lxc_start:1186 - Not dropping cap_sys_boot or watching utmp lxc-start 1452717530.484 INFO lxc_start - start.c:resolve_clone_flags:883 - Cloning a new user namespace lxc-start 1452717530.484 INFO lxc_cgroup - cgroup.c:cgroup_init:65 - cgroup driver cgmanager initing for u1 lxc-start 1452717530.489 ERRORlxc_cgmanager - cgmanager.c:lxc_cgmanager_enter:698 - call to cgmanager_move_pid_sync failed: invalid request lxc-start: cgmanager.c: lxc_cgmanager_enter: 698 call to cgmanager_move_pid_sync failed: invalid request lxc-start 1452717530.490 ERRORlxc_start - start.c:__lxc_start:1213 - failed to spawn 'u1' lxc-start: start.c: __lxc_start: 1213 failed to spawn 'u1' lxc-start 1452717530.513 ERRORlxc_start_ui - lxc_start.c:main:344 - The container failed to start. lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start 1452717530.513 ERRORlxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority opti
Re: [Touch-packages] [Bug 1533833] Re: unprivileged lxc containers won't start, need to put sessions into "pids" cgroup controller
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Martin, On 11-02-16 10:24, Martin Pitt wrote: > Bas, any chance to test the update in -proposed so that we can > release that? I'll try to test it later this week, if that's ok. Best regards, Bas. - -- And what shoulder and what art Could twist the sinews of thy heart? And when thy heart began to beat What dread hand and what dread feet? -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJWwaVGAAoJENGDpRe/qY3m3hEP/Rl0oDvDYBiVQLr8L0ziSW4B CC19e9WaR76hhtuKnPpARqY9KteOeIOfJ2JC37DoAIi39k6I3ze5r61KGqxmB72W Kgajvjy3AcqzWOxEAZC5wEJX9wMI/cT8vSgtUjhQT8TIsTKsGCXXDzBlICzQ51eU CfkFtDJPrTJtkxS/IewomwvQwEy+vYM9sdBAVt/eEeBB2h0V0oNlD5k41p5p80ll 1Go9C9b0KHN0fWmkrjcT69b0GJG94/tsLbP/vMCsOpcH9f1RiLz02ruBSeNsrB8s OUD9xi+hbB55Qvg3dtHjD0InqOn2eOxp+UOoeIwr4IbOP15IenK/7wLVQAvzi0yO GysISesys69zRAAWOEpFHyHb/YX9DBlnRcEO+cRCRXCDV8mod4Y/CUWFPMk37Plv +HCJhl3dlf8eZc3YKXOSCfL70ue25JXo/s+/KKoAai4cQyuWzGZ1cMk4RGQRjnhT 26WL2pOAnB02UqmVTcO4xRx452AFVZbOG0+qi1CdzvTc1zlgRYQrGZPzz2h2fsA3 /+iZzMfcd1N45kr/UMavslhWgkye6wJ5hRJdyMG+n6lyNo3oqGMLyvTuC5v8xVbV m5UaHDULX3NDkk9d1joMsw02qzTuMIZuPdlzTHPr/VPpw15B0b+x4gzHbOxPsACx DKLdRCkiKPUEkXMY2Fbl =oRTc -END PGP SIGNATURE- -- 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/1533833 Title: unprivileged lxc containers won't start, need to put sessions into "pids" cgroup controller Status in lxc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in lxc source package in Wily: New Status in systemd source package in Wily: Fix Committed Bug description: I'n trying to get (unpriviliged) lxc containers to run on wily. I create a container like this: > lxc-create -t download -n u1 -- -d ubuntu -r wily -a amd64 that works. However, starting the container fails: > lxc-start -n u1 lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. Setting the log priority to debug shows the following (relevant part only): lxc-start 1452717530.484 INFO lxc_start - start.c:lxc_init:474 - 'u1' is initialized lxc-start 1452717530.484 DEBUGlxc_start - start.c:__lxc_start:1186 - Not dropping cap_sys_boot or watching utmp lxc-start 1452717530.484 INFO lxc_start - start.c:resolve_clone_flags:883 - Cloning a new user namespace lxc-start 1452717530.484 INFO lxc_cgroup - cgroup.c:cgroup_init:65 - cgroup driver cgmanager initing for u1 lxc-start 1452717530.489 ERRORlxc_cgmanager - cgmanager.c:lxc_cgmanager_enter:698 - call to cgmanager_move_pid_sync failed: invalid request lxc-start: cgmanager.c: lxc_cgmanager_enter: 698 call to cgmanager_move_pid_sync failed: invalid request lxc-start 1452717530.490 ERRORlxc_start - start.c:__lxc_start:1213 - failed to spawn 'u1' lxc-start: start.c: __lxc_start: 1213 failed to spawn 'u1' lxc-start 1452717530.513 ERRORlxc_start_ui - lxc_start.c:main:344 - The container failed to start. lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start 1452717530.513 ERRORlxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. lxc-start 1452717530.484 INFO lxc_start - start.c:lxc_init:474 - 'u1' is initialized lxc-start 1452717530.484 DEBUGlxc_start - start.c:__lxc_start:1186 - Not dropping cap_sys_boot or watching utmp lxc-start 1452717530.484 INFO lxc_start - start.c:resolve_clone_flags:883 - Cloning a new user namespace lxc-start 1452717530.484 INFO lxc_cgroup - cgroup.c:cgroup_init:65 - cgroup driver cgmanager initing for u1 lxc-start 1452717530.489 ERRORlxc_cgmanager - cgmanager.c:lxc_cgmanager_enter:698 - call to cgmanager_move_pid_sync failed: invalid request lxc-start: cgmanager.c: lxc_cgmanager_enter: 698 call to cgmanager_move_pid_sync failed: invalid request lxc-start 1452717530.490 ERRORlxc_start - start.c:__lxc_start:1213 - failed to spawn 'u1' lxc-start: start.c: __lxc_start: 1213 failed to spawn 'u1' lxc-start 1452717530.513 ERRORlxc_start_ui - lxc_start.c:main:344 - The container failed to start. lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start 1452717530.513 ERRORlxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options. lxc-sta
[Touch-packages] [Bug 1538681] [NEW] custom pre/post suspend scripts shoud not live in /lib
Public bug reported: The systemd-sleep manpage mentions the following: Finally, systemd-hybrid-sleep.service is pulled in by hybrid- sleep.target to execute hybrid hibernation with system suspend. Immediately before entering system suspend and/or hibernation systemd-suspend.service (and the other mentioned units, respectively) will run all executables in /lib/systemd/system-sleep/ and pass two arguments to them. The first argument will be "pre", the second either "suspend", "hibernate", or "hybrid-sleep" depending on the chosen action. Immediately after leaving system suspend and/or hibernation the same executables are run, but the first argument is now "post". All executables in this directory are executed in parallel, and execution of the action is not continued until all executables have finished. Note that scripts or binaries dropped in /lib/systemd/system-sleep/ are intended for local use only and should be considered hacks. If applications want to be notified of system suspend/hibernation and resume, there are much nicer interfaces available. It is unfortunate that such "hacks" are generally still required to get a laptop to suspend/hibernate and resume correctly. However, I don't think /lib is the proper place for such scripts, especially for those that are added by local administrators. As far as I know, /lib is handled by dpkg and it should never be required to add stuff there manually. Note that the FHS is also quite specific in this regard: "The /lib directory contains those shared library images needed to boot the system and run the commands in the root filesystem, ie. by binaries in /bin and /sbin.". This doesn't seem to include custom scripts as used here. A better place would probably be /etc/systemd (similar to the obsolete /etc/pm/sleep.d). At the very least, /lib/systemd/systemd-sleep should contain a script that calls user-provided scripts from a more appropriate location. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1538681 Title: custom pre/post suspend scripts shoud not live in /lib Status in systemd package in Ubuntu: New Bug description: The systemd-sleep manpage mentions the following: Finally, systemd-hybrid-sleep.service is pulled in by hybrid- sleep.target to execute hybrid hibernation with system suspend. Immediately before entering system suspend and/or hibernation systemd-suspend.service (and the other mentioned units, respectively) will run all executables in /lib/systemd/system-sleep/ and pass two arguments to them. The first argument will be "pre", the second either "suspend", "hibernate", or "hybrid-sleep" depending on the chosen action. Immediately after leaving system suspend and/or hibernation the same executables are run, but the first argument is now "post". All executables in this directory are executed in parallel, and execution of the action is not continued until all executables have finished. Note that scripts or binaries dropped in /lib/systemd/system-sleep/ are intended for local use only and should be considered hacks. If applications want to be notified of system suspend/hibernation and resume, there are much nicer interfaces available. It is unfortunate that such "hacks" are generally still required to get a laptop to suspend/hibernate and resume correctly. However, I don't think /lib is the proper place for such scripts, especially for those that are added by local administrators. As far as I know, /lib is handled by dpkg and it should never be required to add stuff there manually. Note that the FHS is also quite specific in this regard: "The /lib directory contains those shared library images needed to boot the system and run the commands in the root filesystem, ie. by binaries in /bin and /sbin.". This doesn't seem to include custom scripts as used here. A better place would probably be /etc/systemd (similar to the obsolete /etc/pm/sleep.d). At the very least, /lib/systemd/systemd- sleep should contain a script that calls user-provided scripts from a more appropriate location. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1538681/+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 1533833] Re: unprivileged lxc containers won't start
Ah, right, that explains things: I'm running a xenial kernel, I think. For completeness sake, these are the versions: [bas@miranda]~> uname -a Linux miranda 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux [bas@miranda]~> dpkg -l linux-image-\* systemd 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 +++-==---= un linux-image-3. (no description available) ii linux-image-4. 4.2.0-23.28 amd64Linux kernel image for version 4. ii linux-image-4. 4.3.0-5.16 amd64Linux kernel image for version 4. ii linux-image-ex 4.2.0-23.28 amd64Linux kernel extra modules for ve ii linux-image-ex 4.3.0-5.16 amd64Linux kernel extra modules for ve ii linux-image-ge 4.2.0.23.25 amd64Generic Linux kernel image ii systemd225-1ubuntu9 amd64system and service manager -- 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/1533833 Title: unprivileged lxc containers won't start Status in lxc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in lxc source package in Wily: New Status in systemd source package in Wily: New Bug description: I'n trying to get (unpriviliged) lxc containers to run on wily. I create a container like this: > lxc-create -t download -n u1 -- -d ubuntu -r wily -a amd64 that works. However, starting the container fails: > lxc-start -n u1 lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. Setting the log priority to debug shows the following (relevant part only): lxc-start 1452717530.484 INFO lxc_start - start.c:lxc_init:474 - 'u1' is initialized lxc-start 1452717530.484 DEBUGlxc_start - start.c:__lxc_start:1186 - Not dropping cap_sys_boot or watching utmp lxc-start 1452717530.484 INFO lxc_start - start.c:resolve_clone_flags:883 - Cloning a new user namespace lxc-start 1452717530.484 INFO lxc_cgroup - cgroup.c:cgroup_init:65 - cgroup driver cgmanager initing for u1 lxc-start 1452717530.489 ERRORlxc_cgmanager - cgmanager.c:lxc_cgmanager_enter:698 - call to cgmanager_move_pid_sync failed: invalid request lxc-start: cgmanager.c: lxc_cgmanager_enter: 698 call to cgmanager_move_pid_sync failed: invalid request lxc-start 1452717530.490 ERRORlxc_start - start.c:__lxc_start:1213 - failed to spawn 'u1' lxc-start: start.c: __lxc_start: 1213 failed to spawn 'u1' lxc-start 1452717530.513 ERRORlxc_start_ui - lxc_start.c:main:344 - The container failed to start. lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start 1452717530.513 ERRORlxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. lxc-start 1452717530.484 INFO lxc_start - start.c:lxc_init:474 - 'u1' is initialized lxc-start 1452717530.484 DEBUGlxc_start - start.c:__lxc_start:1186 - Not dropping cap_sys_boot or watching utmp lxc-start 1452717530.484 INFO lxc_start - start.c:resolve_clone_flags:883 - Cloning a new user namespace lxc-start 1452717530.484 INFO lxc_cgroup - cgroup.c:cgroup_init:65 - cgroup driver cgmanager initing for u1 lxc-start 1452717530.489 ERRORlxc_cgmanager - cgmanager.c:lxc_cgmanager_enter:698 - call to cgmanager_move_pid_sync failed: invalid request lxc-start: cgmanager.c: lxc_cgmanager_enter: 698 call to cgmanager_move_pid_sync failed: invalid request lxc-start 1452717530.490 ERRORlxc_start - start.c:__lxc_start:1213 - failed to spawn 'u1' lxc-start: start.c: __lxc_start: 1213 failed to spawn 'u1' lxc-start 1452717530.513 ERRORlxc_start_ui - lxc_start.c:main:344 - The container failed to start. lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start 1452717530.513 ERRORlxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. So it seems a cgmanager issu
[Touch-packages] [Bug 1533833] [NEW] unprivileged lxc containers won't start
Public bug reported: I'n trying to get (unpriviliged) lxc containers to run on wily. I create a container like this: > lxc-create -t download -n u1 -- -d ubuntu -r wily -a amd64 that works. However, starting the container fails: > lxc-start -n u1 lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. Setting the log priority to debug shows the following (relevant part only): lxc-start 1452717530.484 INFO lxc_start - start.c:lxc_init:474 - 'u1' is initialized lxc-start 1452717530.484 DEBUGlxc_start - start.c:__lxc_start:1186 - Not dropping cap_sys_boot or watching utmp lxc-start 1452717530.484 INFO lxc_start - start.c:resolve_clone_flags:883 - Cloning a new user namespace lxc-start 1452717530.484 INFO lxc_cgroup - cgroup.c:cgroup_init:65 - cgroup driver cgmanager initing for u1 lxc-start 1452717530.489 ERRORlxc_cgmanager - cgmanager.c:lxc_cgmanager_enter:698 - call to cgmanager_move_pid_sync failed: invalid request lxc-start: cgmanager.c: lxc_cgmanager_enter: 698 call to cgmanager_move_pid_sync failed: invalid request lxc-start 1452717530.490 ERRORlxc_start - start.c:__lxc_start:1213 - failed to spawn 'u1' lxc-start: start.c: __lxc_start: 1213 failed to spawn 'u1' lxc-start 1452717530.513 ERRORlxc_start_ui - lxc_start.c:main:344 - The container failed to start. lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start 1452717530.513 ERRORlxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. lxc-start 1452717530.484 INFO lxc_start - start.c:lxc_init:474 - 'u1' is initialized lxc-start 1452717530.484 DEBUGlxc_start - start.c:__lxc_start:1186 - Not dropping cap_sys_boot or watching utmp lxc-start 1452717530.484 INFO lxc_start - start.c:resolve_clone_flags:883 - Cloning a new user namespace lxc-start 1452717530.484 INFO lxc_cgroup - cgroup.c:cgroup_init:65 - cgroup driver cgmanager initing for u1 lxc-start 1452717530.489 ERRORlxc_cgmanager - cgmanager.c:lxc_cgmanager_enter:698 - call to cgmanager_move_pid_sync failed: invalid request lxc-start: cgmanager.c: lxc_cgmanager_enter: 698 call to cgmanager_move_pid_sync failed: invalid request lxc-start 1452717530.490 ERRORlxc_start - start.c:__lxc_start:1213 - failed to spawn 'u1' lxc-start: start.c: __lxc_start: 1213 failed to spawn 'u1' lxc-start 1452717530.513 ERRORlxc_start_ui - lxc_start.c:main:344 - The container failed to start. lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start 1452717530.513 ERRORlxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. So it seems a cgmanager issue. Syslog shows: Jan 13 21:37:58 miranda cgmanager[22010]: cgmanager:do_create_main: pid 25615 (uid 1000 gid 1000) may not create under /run/cgmanager/fs/pids Jan 13 21:37:58 miranda cgmanager[22010]: cgmanager: Invalid path /run/cgmanager/fs/pids/lxc/u1 Jan 13 21:37:58 miranda cgmanager[22010]: cgmanager:per_ctrl_move_pid_main: Invalid path /run/cgmanager/fs/pids/lxc/u1 Jan 13 21:38:50 miranda cgmanager[22010]: cgmanager:do_create_main: pid 25632 (uid 1000 gid 1000) may not create under /run/cgmanager/fs/pids Jan 13 21:38:50 miranda cgmanager[22010]: cgmanager: Invalid path /run/cgmanager/fs/pids/lxc/u1 Jan 13 21:38:50 miranda cgmanager[22010]: cgmanager:per_ctrl_move_pid_main: Invalid path /run/cgmanager/fs/pids/lxc/u1 ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- 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/1533833 Title: unprivileged lxc containers won't start Status in lxc package in Ubuntu: New Bug description: I'n trying to get (unpriviliged) lxc containers to run on wily. I create a container like this: > lxc-create -t download -n u1 -- -d ubuntu -r wily -a amd64 that works. However, starting the container fails: > lxc-start -n u1 lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 348 Additional information can be obtained b
[Touch-packages] [Bug 1510098] Re: /etc/network/interfaces ipv6 static gateway not set
Exact same problem here. Setup worked flawlessly in 15.04, but in 15.10 the default gateway isn't set. After manually adding it, eveything works fine again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1510098 Title: /etc/network/interfaces ipv6 static gateway not set Status in ifupdown package in Ubuntu: New Bug description: After installing 15.10 ipv6 gateway not set on start up. In 15.04 it worked fine andrej@nikel:~$ cat /etc/network/interfaces auto lo enp4s0 iface lo inet loopback iface enp4s0 inet manual iface enp4s0 inet6 static address :200:8221::--- netmask 64 gateway 198:20- andrej@nikel:~$ ip -6 route ---0:8221::/64 dev enp4s0 proto kernel metric 256 mtu 1500 pref medium fe80::/64 dev enp4s0 proto kernel metric 256 mtu 1500 pref medium fe80::/64 dev lxcbr0 proto kernel metric 256 pref medium fe80::/64 dev docker0 proto kernel metric 256 pref medium 3: enp4s0: mtu 9000 qdisc pfifo_fast state UP group default qlen 1000 link/ether --7:98 brd ff:ff:ff:ff:ff:ff inet 10.0.4.1/8 brd 10.255.255.255 scope global enp4s0 valid_lft forever preferred_lft forever inet6 200:8221::--/64 scope global valid_lft forever preferred_lft forever inet6 -15:17ff:fe9e:b798/64 scope global mngtmpaddr dynamic valid_lft 83024sec preferred_lft 11024sec inet6 fe80::215:17ff:fe9e:b798/64 scope link valid_lft forever preferred_lft forever andrej@nikel:~$ cat /etc/sysctl.conf net.ipv4.conf.default.rp_filter= 1 net.ipv4.conf.all.rp_filter= 1 net.ipv4.tcp_syncookies= 1 net.ipv6.conf.all.use_tempaddr = 2 net.ipv6.conf.default.use_tempaddr = 2 net.ipv6.conf.enp4s0.use_tempaddr = 2 andrej@nikel:/proc/sys/net/ipv6/conf/enp4s0$ for i in *; do echo -n "$i: " ; cat $i ; done accept_dad: 1 accept_ra: 0 accept_ra_defrtr: 1 accept_ra_from_local: 0 accept_ra_mtu: 1 accept_ra_pinfo: 1 accept_ra_rt_info_max_plen: 0 accept_ra_rtr_pref: 1 accept_redirects: 1 accept_source_route: 0 autoconf: 0 dad_transmits: 1 disable_ipv6: 0 force_mld_version: 0 force_tllao: 0 forwarding: 0 hop_limit: 64 max_addresses: 16 max_desync_factor: 600 mc_forwarding: 0 mldv1_unsolicited_report_interval: 1 mldv2_unsolicited_report_interval: 1000 mtu: 1500 ndisc_notify: 0 proxy_ndp: 0 regen_max_retry: 3 router_probe_interval: 60 router_solicitation_delay: 1 router_solicitation_interval: 4 router_solicitations: 3 cat: stable_secret: Permission denied stable_secret: suppress_frag_ndisc: 1 temp_prefered_lft: 86400 temp_valid_lft: 604800 use_tempaddr: 2 Maybe related: https://bugs.launchpad.net/ubuntu/+source/miredo/+bug/1510047 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ifupdown 0.7.54ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 26 14:41:55 2015 JournalErrors: No journal files were found. -- No entries -- SourcePackage: ifupdown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1510098/+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
