[Touch-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Hi, for Gnome-packagekit it's related to this behavior : https://bugs.launchpad.net/ubuntu/+source/gnome-packagekit/+bug/2046843 I run Ubuntu development branch 24.04 and I have a problem with Gnome PackageKit 43.0-2 : application launches well, but if I write a program / package name in the search field and click on"Enter", it crashes and closes : $ gpk-application (gpk-application:6130): PackageKit-CRITICAL **: 10:51:02.410: pk_client_generic_finish: assertion 'G_IS_TASK (res)' failed Erreur de segmentation (core dumped) It stills occurs on my computer… -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in AppArmor: New Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Confirmed Status in freecad package in Ubuntu: Invalid Status in geary package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Incomplete Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Fix Released Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in loupe package in Ubuntu: Confirmed Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Fix Released Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Released Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+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 2047447] Re: No valid source.list found while upgrading from mantic to noble
I can confirm that putting aside vscode.list allowed me to do the upgrade Thanks Xavier -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in python-apt source package in Mantic: Confirmed Status in ubuntu-release-upgrader source package in Mantic: Invalid Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Fix released for Firrefox (Nightly) 125. Since a few days, I can't launch Gpodder (podcast program) anymore, is it also related to this bug or is it something different ? "[gpodder.log] ERROR: Uncaught exception: Traceback (most recent call last): File "/usr/bin/gpodder", line 181, in main() File "/usr/bin/gpodder", line 173, in main from gpodder.gtkui import app File "/usr/lib/python3/dist-packages/gpodder/gtkui/app.py", line 31, in from gpodder import core, util File "/usr/lib/python3/dist-packages/gpodder/core.py", line 25, in from gpodder import config, dbsqlite, extensions, model, util File "/usr/lib/python3/dist-packages/gpodder/extensions.py", line 34, in import imp ModuleNotFoundError: No module named 'imp' Traceback (most recent call last): File "/usr/bin/gpodder", line 181, in main() File "/usr/bin/gpodder", line 173, in main from gpodder.gtkui import app File "/usr/lib/python3/dist-packages/gpodder/gtkui/app.py", line 31, in from gpodder import core, util File "/usr/lib/python3/dist-packages/gpodder/core.py", line 25, in from gpodder import config, dbsqlite, extensions, model, util File "/usr/lib/python3/dist-packages/gpodder/extensions.py", line 34, in import imp ModuleNotFoundError: No module named 'imp'" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in AppArmor: New Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Confirmed Status in freecad package in Ubuntu: Confirmed Status in geary package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Fix Released Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in loupe package in Ubuntu: Confirmed Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Fix Released Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Released Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+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 2047447] Re: No valid source.list found while upgrading from mantic to noble
Files attached ** Attachment added: "aptsources.tar.bz2" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2047447/+attachment/5755869/+files/aptsources.tar.bz2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python-apt source package in Mantic: New Status in ubuntu-release-upgrader source package in Mantic: New Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+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 2047447] Re: No valid source.list found while upgrading from mantic to noble
Yes I have some more : [xavier@imladris ~]$ ll /etc/apt/sources.list.d/*sources -rw-r--r-- 1 root root 122 Sep 1 2023 /etc/apt/sources.list.d/alessandro-strada-ubuntu-ppa-groovy.sources -rw-r--r-- 1 root root 1805 Sep 12 2023 /etc/apt/sources.list.d/ancestris-ubuntu-ancestris-stable-lunar.sources -rw-r--r-- 1 root root 92 Sep 1 2023 /etc/apt/sources.list.d/archive_uri-https_download_docker_com_linux_ubuntu-hirsute.sources -rw-r--r-- 1 root root 111 Sep 1 2023 /etc/apt/sources.list.d/fortine.sources -rw-r--r-- 1 root root 99 Sep 1 2023 /etc/apt/sources.list.d/google-earth-pro.sources -rw-r--r-- 1 root root 114 Sep 1 2023 /etc/apt/sources.list.d/inkscape_dev-ubuntu-stable-hirsute.sources -rw-r--r-- 1 root root 97 Sep 1 2023 /etc/apt/sources.list.d/jtaylor-ubuntu-keepass-impish.sources -rw-r--r-- 1 root root 112 Sep 1 2023 /etc/apt/sources.list.d/mscore-ubuntu-ubuntu-mscore3-stable-hirsute.sources -rw-r--r-- 1 root root 133 Sep 1 2023 /etc/apt/sources.list.d/musicbrainz-developers-ubuntu-stable-kinetic.sources -rw-r--r-- 1 root root 1541 Sep 1 2023 /etc/apt/sources.list.d/noobslab-ubuntu-macbuntu-cosmic.sources -rw-r--r-- 1 root root 122 Sep 1 2023 /etc/apt/sources.list.d/pgadmin4.sources -rw-r--r-- 1 root root 107 Sep 1 2023 /etc/apt/sources.list.d/pgdg.sources -rw-r--r-- 1 root root 113 Sep 1 2023 /etc/apt/sources.list.d/python2-stuff.sources -rw-r--r-- 1 root root 86 Sep 1 2023 /etc/apt/sources.list.d/rudder.sources -rw-r--r-- 1 root root 118 Mar 4 13:50 /etc/apt/sources.list.d/runner_gitlab-runner.sources -rw-r--r-- 1 root root 107 Sep 1 2023 /etc/apt/sources.list.d/teams.sources -rw-r--r-- 1 root root 114 Sep 1 2023 /etc/apt/sources.list.d/teamviewer.sources -rw-r--r-- 1 root root 146 Sep 1 2023 /etc/apt/sources.list.d/third-party.sources -rw-r--r-- 1 root root 128 Sep 1 2023 /etc/apt/sources.list.d/ubuntu-esm-apps.sources -rw-r--r-- 1 root root 131 Sep 1 2023 /etc/apt/sources.list.d/ubuntu-esm-infra.sources -rw-r--r-- 1 root root 585 Sep 1 2023 /etc/apt/sources.list.d/ubuntu.sources -rw-r--r-- 1 root root 759 Sep 1 2023 /etc/apt/sources.list.d/yannubuntu-ubuntu-boot-repair-jammy.sources -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python-apt source package in Mantic: New Status in ubuntu-release-upgrader source package in Mantic: New Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository
[Touch-packages] [Bug 2047447] Re: No valid source.list found while upgrading from mantic to noble
Hi Nick This file : Types: deb URIs: http://fr.archive.ubuntu.com/ubuntu/ Suites: mantic mantic-updates mantic-backports Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Types: deb URIs: http://security.ubuntu.com/ubuntu Suites: mantic-security Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Enabled: no Types: deb URIs: http://fr.archive.ubuntu.com/ubuntu/ Suites: lunar-proposed Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Regards -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python-apt source package in Mantic: New Status in ubuntu-release-upgrader source package in Mantic: New Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
I reported the bug upstream for Firefox - if you have a Bugzilla account on Mozilla and are affected, you could confirm it please : https://bugzilla.mozilla.org/show_bug.cgi?id=1884347 ** Bug watch added: Mozilla Bugzilla #1884347 https://bugzilla.mozilla.org/show_bug.cgi?id=1884347 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in AppArmor: New Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Confirmed Status in freecad package in Ubuntu: Confirmed Status in geary package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Fix Released Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in loupe package in Ubuntu: Confirmed Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Fix Released Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Committed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Yes, since today's updates, Firefox Nightly 125.0a1 from Mozilla repositery which worked very fined until now, stopped : program still well starts, but every tab gets a crash error and doesn't laod the page (even the start about:blank one)… -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Confirmed Status in freecad package in Ubuntu: Confirmed Status in geary package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Fix Released Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Fix Released Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Committed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2046844/+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 2054560] [NEW] Xorg freeze
Public bug reported: Random freezes occur since the installation of 6.5.x kernel. Freeze occur several times a day, probably after touching the mouse or keyboard, but I'm not sure. App continue to work sound is OK, there is just no dispay updated. Booting to old 6.2 kernel solves the problem. I have tried all 6.5 updates since the first released, but each time, I had a freeze after a few hours. Example of last mesg in dmesg when freeze occur : Feb 21 11:03:59 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 21 11:04:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:04:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 21 11:04:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 21 11:05:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:05:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 21 11:05:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:05:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:274:DP-5] commit wait timed out Feb 21 11:05:22 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 21 11:05:32 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:05:32 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 21 11:05:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:05:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:274:DP-5] commit wait timed out Feb 21 11:05:53 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 21 11:06:03 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:06:03 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 21 11:06:13 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:06:13 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:274:DP-5] commit wait timed out Feb 21 11:06:23 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out or : Feb 13 10:37:18 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 13 10:39:06 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 10:39:06 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 13 11:22:09 pf46avw7 kernel: perf: interrupt took too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 79750 Feb 13 11:35:00 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 13 11:35:10 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:35:10 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 13 11:35:21 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:35:21 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:282:DP-5] commit wait timed out Feb 13 11:35:31 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 13 11:35:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:35:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 13 11:35:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:35:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:282:DP-5] commit wait timed out Feb 13 11:36:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 13 11:36:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:36:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 13 11:36:22 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:36:22 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:282:DP-5] commit wait timed out Feb 13 11:36:32 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 13 11:37:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:37:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out or Feb 01 09:37:11 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 01 09:37:23 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 01 09:37:23 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 01 09:37:45 pf46avw7 kernel: rfkill: input handler enabled Feb 01 09:37:55 pf46avw7 kernel: i915 :00:02.0: [drm]
[Touch-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Hi, sorry for this newbie question: I see many KDE applications for which a fix is released, great news. Does it mean that every program has to be patched separately, and not directly AppArmor ? If yes, are Gnome developers aware oh this bug upstream ?… -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Confirmed Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Confirmed Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: In Progress Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: In Progress Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: In Progress Status in konqueror package in Ubuntu: In Progress Status in kontact package in Ubuntu: In Progress Status in marble package in Ubuntu: In Progress Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Confirmed Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Confirmed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: In Progress Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2046844/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Also affects: gnome-packagekit (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-packagekit (Ubuntu) Status: New => Confirmed ** Also affects: evolution (Ubuntu) Importance: Undecided Status: New ** Changed in: evolution (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in apparmor package in Ubuntu: Confirmed Status in digikam package in Ubuntu: Confirmed Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in falkon package in Ubuntu: Confirmed Status in freecad package in Ubuntu: Confirmed Status in gnome-packagekit package in Ubuntu: Confirmed Status in kontact package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop
Unfortunately I do not know the answer. It's been a while since I stopped using ubuntu on raspberrypi and i went back to using the official system for the device and since then I haven't changed system anymore. Also, for other personal interests I haven't used raspberrypi so often lately. Em qua., 12 de out. de 2022 às 22:45, Daniel van Vugt < 1924...@bugs.launchpad.net> escreveu: > Which package should be marked as Fix Released for 22.10? > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1946664). > https://bugs.launchpad.net/bugs/1924251 > > Title: > Embedded browser display corruption under Wayland on Pi desktop > > Status in gtk+3.0 package in Ubuntu: > Confirmed > Status in webkit2gtk package in Ubuntu: > Confirmed > Status in yelp package in Ubuntu: > Confirmed > > Bug description: > On the jammy Pi desktop, under a wayland session, the body of a window > containing an HTML renderer (e.g. help text or a login page) displays > corruption. > > These reproduction cases may not be entirely reliable given that > *some* pages appear to render correctly, but I'll include a couple in > the hopes of making it reliably reproducible: > > 1. Open the Lights Off game > 2. Select "Help" from the menu > 3. In the help window that appears, select any link > > "Basics", "Rules", and "Strategy" all reliably reproduce the issue for > me, but "Help Translate" doesn't so you may need to click around some > links until the corruption appears -- however, once it does even > navigating back to the prior page which rendered happily now displays > the same corruption. > > Another reproduction case: > > 1. Open the Settings application > 2. Select the Online Applications option from the left > 3. Select the Google entry in the list > 4. The login window that appears always displays corruption for me > > The Microsoft option always reliably corrupts for me, but the Facebook > one doesn't so again I wonder how reproducible this may be for others > (might be worth trying several options if the first doesn't display > corruption). > > The corruption appears in the form of "shredded" content as if a > horizontal stride is set incorrectly somewhere, but only appears in > the body of the window; the window decorations are unaffected. I'll > attach a screenshot of the corrupted help window to illustrate. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1924251 Title: Embedded browser display corruption under Wayland on Pi desktop Status in gtk+3.0 package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Status in yelp package in Ubuntu: Confirmed Bug description: On the jammy Pi desktop, under a wayland session, the body of a window containing an HTML renderer (e.g. help text or a login page) displays corruption. These reproduction cases may not be entirely reliable given that *some* pages appear to render correctly, but I'll include a couple in the hopes of making it reliably reproducible: 1. Open the Lights Off game 2. Select "Help" from the menu 3. In the help window that appears, select any link "Basics", "Rules", and "Strategy" all reliably reproduce the issue for me, but "Help Translate" doesn't so you may need to click around some links until the corruption appears -- however, once it does even navigating back to the prior page which rendered happily now displays the same corruption. Another reproduction case: 1. Open the Settings application 2. Select the Online Applications option from the left 3. Select the Google entry in the list 4. The login window that appears always displays corruption for me The Microsoft option always reliably corrupts for me, but the Facebook one doesn't so again I wonder how reproducible this may be for others (might be worth trying several options if the first doesn't display corruption). The corruption appears in the form of "shredded" content as if a horizontal stride is set incorrectly somewhere, but only appears in the body of the window; the window decorations are unaffected. I'll attach a screenshot of the corrupted help window to illustrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+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 1989240] Re: Graphics crash when login to gnome desktop environemnt
** Package changed: xorg (Ubuntu) => gnome-session (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1989240 Title: Graphics crash when login to gnome desktop environemnt Status in gnome-session package in Ubuntu: New Bug description: Unable to log in after upgrade to `kinetic-proposed`. On Wayland session, the screen turn to black and back to gdm3 login greeter after about 30s. On X.Org session, the screen turn to black, then shows an white screen notice that some unrecoverable error occurred and click the button to go back to the login screen. Unity and KDE(plasma, Wayland session) looks fine. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7 Uname: Linux 5.19.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown Date: Sat Sep 10 14:58:03 2022 DistUpgraded: 2022-09-07 10:21:27,934 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms/22.07.00, 5.15.0-47-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms/22.07.00, 5.19.0-15-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms/22.07.00, 5.19.0-16-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:380c] NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2560] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GA106M [GeForce RTX 3060 Mobile / Max-Q] [17aa:3803] MachineType: LENOVO 82TF ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-16-generic root=/dev/mapper/vgroot-lvroot ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2022-09-07 (3 days ago) dmi.bios.date: 06/16/2022 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: JYCN39WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76479WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y9000X IAH7 dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvrJYCN39WW:bd06/16/2022:br1.39:efr1.39:svnLENOVO:pn82TF:pvrLegionY9000XIAH7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrLegionY9000XIAH7:skuLENOVO_MT_82TF_BU_idea_FM_LegionY9000XIAH7: dmi.product.family: Legion Y9000X IAH7 dmi.product.name: 82TF dmi.product.sku: LENOVO_MT_82TF_BU_idea_FM_Legion Y9000X IAH7 dmi.product.version: Legion Y9000X IAH7 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.112-3ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.1.7-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1989240/+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 1989240] [NEW] Graphics crash when login to gnome desktop environemnt
Public bug reported: Unable to log in after upgrade to `kinetic-proposed`. On Wayland session, the screen turn to black and back to gdm3 login greeter after about 30s. On X.Org session, the screen turn to black, then shows an white screen notice that some unrecoverable error occurred and click the button to go back to the login screen. Unity and KDE(plasma, Wayland session) looks fine. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7 Uname: Linux 5.19.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown Date: Sat Sep 10 14:58:03 2022 DistUpgraded: 2022-09-07 10:21:27,934 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms/22.07.00, 5.15.0-47-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms/22.07.00, 5.19.0-15-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms/22.07.00, 5.19.0-16-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:380c] NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2560] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GA106M [GeForce RTX 3060 Mobile / Max-Q] [17aa:3803] MachineType: LENOVO 82TF ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-16-generic root=/dev/mapper/vgroot-lvroot ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2022-09-07 (3 days ago) dmi.bios.date: 06/16/2022 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: JYCN39WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76479WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y9000X IAH7 dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvrJYCN39WW:bd06/16/2022:br1.39:efr1.39:svnLENOVO:pn82TF:pvrLegionY9000XIAH7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrLegionY9000XIAH7:skuLENOVO_MT_82TF_BU_idea_FM_LegionY9000XIAH7: dmi.product.family: Legion Y9000X IAH7 dmi.product.name: 82TF dmi.product.sku: LENOVO_MT_82TF_BU_idea_FM_Legion Y9000X IAH7 dmi.product.version: Legion Y9000X IAH7 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.112-3ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.1.7-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash kinetic third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1989240 Title: Graphics crash when login to gnome desktop environemnt Status in xorg package in Ubuntu: New Bug description: Unable to log in after upgrade to `kinetic-proposed`. On Wayland session, the screen turn to black and back to gdm3 login greeter after about 30s. On X.Org session, the screen turn to black, then shows an white screen notice that some unrecoverable error occurred and click the button to go back to the login screen. Unity and KDE(plasma, Wayland session) looks fine. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7 Uname: Linux 5.19.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp
[Touch-packages] [Bug 1987168] [NEW] Video problems
Public bug reported: Video doesn't show options for other resolutions ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 20 11:26:01 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Core Processor Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2022-08-20 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. H55M-S2V ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=7695fd9a-b5ed-4bac-a4ca-5ca31eec559d ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F3 dmi.board.name: H55M-S2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd09/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-S2V:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-S2V:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: H55M-S2V dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1987168 Title: Video problems Status in xorg package in Ubuntu: New Bug description: Video doesn't show options for other resolutions ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 20 11:26:01 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Core Processor Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2022-08-20 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. H55M-S2V ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=7695fd9a-b5ed-4bac-a4ca-5ca31eec559d ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F3 dmi.board.name: H55M-S2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd09/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-S2V:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-S2V:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: H55M-S2V dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications
[Touch-packages] [Bug 1966849] Re: gzip exec format error under WSL
I download the file https://ftp.gnu.org/gnu/gzip/gzip-1.12.tar.gz I Untar it tar xvzf with ubuntu 20 I copy all the files to Ubuntu 22 I run the ./configure I run make I run sudo make install I exit the terminal I log in again and the new gzip 1.12 work very good -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1966849 Title: gzip exec format error under WSL Status in gzip: New Status in gzip package in Ubuntu: Confirmed Bug description: gzip version 1.10-4ubuntu3 fails to run under WSL1 on Windows 19044.1620, making WSL pretty much unusable. bash: /usr/bin/gzip: cannot execute binary file: Exec format error ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gzip 1.10-4ubuntu3 ProcVersionSignature: Microsoft 4.4.0-19041.1237-Microsoft 4.4.35 Uname: Linux 4.4.0-19041-Microsoft x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Mar 29 06:40:33 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/usr/bin/fish SourcePackage: gzip UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gzip/+bug/1966849/+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 1970279] [NEW] My monitor image turned yellow.
Public bug reported: I had to switch from Wayland to Xorg on the login screen, and after login the screen had a yellow filter. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 25 18:59:04 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] InstallationDate: Installed on 2022-04-23 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=6abdccf1-2e9d-4265-a466-6dcef0abc427 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: A320M-HD dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd07/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA320M-HD:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- 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/1970279 Title: My monitor image turned yellow. Status in xorg package in Ubuntu: New Bug description: I had to switch from Wayland to Xorg on the login screen, and after login the screen had a yellow filter. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 25 18:59:04 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] InstallationDate: Installed on 2022-04-23 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=6abdccf1-2e9d-4265-a466-6dcef0abc427 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: A320M-HD dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd07/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA320M-HD:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To
[Touch-packages] [Bug 1966418] Re: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc)
Evolution and Online Accounts seems fixed in Jammy now. However devhelp still cannot display documentation pages. Maybe unrelated issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc) Status in Gnome DevHelp: Invalid Status in Mesa: Unknown Status in Webkit: Confirmed Status in epiphany-browser package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in liferea package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in webkit2gtk package in Ubuntu: Invalid Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/devhelp/+bug/1966418/+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 1966871] Re: Unable to play music in gnome but able to play in "speaker-test" after upgrade
Fixed after checking pipewire-media-session release note. Thanks for your reply! ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1966871 Title: Unable to play music in gnome but able to play in "speaker-test" after upgrade Status in pulseaudio package in Ubuntu: Invalid Bug description: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 == pulseaudio: Installed：1:15.99.1+dfsg1-1ubuntu1 pipewire: Installed：0.3.48-1ubuntu1 == After upgrade to 22.04 dev branch, it seems that gnome the desktop environment and applications can't detect sound output devices. But "speaker-test" and "aplay" works fine with root privileges. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 29 15:01:27 2022 InstallationDate: Installed on 2021-05-01 (332 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to jammy on 2022-01-23 (64 days ago) dmi.bios.date: 09/11/2020 dmi.bios.release: 106.117 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: XMAKB5R0P0E07 dmi.board.asset.tag: Any dmi.board.name: TM1701 dmi.board.vendor: Timi dmi.board.version: MP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Timi dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 0.7 dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB5R0P0E07:bd09/11/2020:br106.117:efr0.7:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:skuTM1701-16773: dmi.product.family: Timibook dmi.product.name: TM1701 dmi.product.sku: TM1701-16773 dmi.sys.vendor: Timi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1966871/+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 1966871] [NEW] Unable to play music in gnome but able to play in "speaker-test" after upgrade
Public bug reported: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 == pulseaudio: Installed：1:15.99.1+dfsg1-1ubuntu1 pipewire: Installed：0.3.48-1ubuntu1 == After upgrade to 22.04 dev branch, it seems that gnome the desktop environment and applications can't detect sound output devices. But "speaker-test" and "aplay" works fine with root privileges. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 29 15:01:27 2022 InstallationDate: Installed on 2021-05-01 (332 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to jammy on 2022-01-23 (64 days ago) dmi.bios.date: 09/11/2020 dmi.bios.release: 106.117 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: XMAKB5R0P0E07 dmi.board.asset.tag: Any dmi.board.name: TM1701 dmi.board.vendor: Timi dmi.board.version: MP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Timi dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 0.7 dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB5R0P0E07:bd09/11/2020:br106.117:efr0.7:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:skuTM1701-16773: dmi.product.family: Timibook dmi.product.name: TM1701 dmi.product.sku: TM1701-16773 dmi.sys.vendor: Timi ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1966871 Title: Unable to play music in gnome but able to play in "speaker-test" after upgrade Status in pulseaudio package in Ubuntu: New Bug description: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 == pulseaudio: Installed：1:15.99.1+dfsg1-1ubuntu1 pipewire: Installed：0.3.48-1ubuntu1 == After upgrade to 22.04 dev branch, it seems that gnome the desktop environment and applications can't detect sound output devices. But "speaker-test" and "aplay" works fine with root privileges. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 29 15:01:27 2022 InstallationDate: Installed on 2021-05-01 (332 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to jammy on 2022-01-23 (64 days ago) dmi.bios.date: 09/11/2020 dmi.bios.release: 106.117 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: XMAKB5R0P0E07 dmi.board.asset.tag: Any dmi.board.name: TM1701 dmi.board.vendor: Timi dmi.board.version: MP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Timi dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 0.7 dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB5R0P0E07:bd09/11/2020:br106.117:efr0.7:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:skuTM1701-16773: dmi.product.family: Timibook dmi.product.name: TM1701 dmi.product.sku: TM1701-16773 dmi.sys.vendor: Timi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1966871/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1917152] Re: File moved with Cut-Paste from a search filter still appears on original screen and if deleted disappears from new folder
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1723 https://gitlab.gnome.org/GNOME/nautilus/-/issues/1723 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/1723 Importance: Unknown Status: Unknown ** Also affects: tracker (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1917152 Title: File moved with Cut-Paste from a search filter still appears on original screen and if deleted disappears from new folder Status in Nautilus: Unknown Status in nautilus package in Ubuntu: New Status in tracker package in Ubuntu: New Bug description: Affected version Nautilus 3.38 on Ubuntu 20.10 (but I also saw this bug some months and versions ago) I don't know if it's a specific Ubuntu bug or an upstream one, I reported it 1.5 month ago on Gitlab Gnome without any answer nor review: https://gitlab.gnome.org/GNOME/nautilus/-/issues/1723 Resume: File moved with "Cut" from a window with an active search filter, and pasted in another folder on a second Nautilus window (not a subfolder), still appears on the first original screen (list is not automatically updated) - and if deleted from here, actually they disappear from the new folder ! It can occur to loose important documents - I often make direct shift-deletes, without recycler storage... Steps to reproduce I open a Nautilus window, go to a folder and make a search filter, for example 20 files appear on the window which name contains my search filter. If I select one of them, make Cut / Ctrl-X, open a new Nautilus window, go to another folder (which is not a subfolder of the first) and make Paste / Ctrl-V, it wells copy the file in the new folder. If I switch to the first Nautilus window with the original folder and search filter active, the moved file still appears on the list and I can open it. I think I've made an error (Ctrl-C instead of Ctrl-X) so I shift-delete it, it disappears from the list and only 19 files remain. Current behavior But… If I go to the second Nautilus window and the 2nd folder, the file has also disappeared from it ! File in the first window was "transformed" to a link instead of being removed, and suppressing it also deletes the file in its new folder - in my case, I lost several documents like this because of Shift-Delete and not trash use. Expected behavior After Cut - Paste, in the case of 2 Nautilus windows are opened, the file(s) moved from the first one should not be still visible in the search list, there should be an automatic refresh. If I do a Copy-Paste instead of a Cut-Paste, problem does not occur: delete only removes file in the fist original folder, not on the second. If I close the search filter, it's also OK, file(s) moved no more visible. And of course, if after Cut I stay in the same Nautilus window and go to another folder to paste, no problem: bug only occurs in case of a second window opened. Thanks in advance and best regards. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1917152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1946664] Re: account setup window becomes unconfigured
Sebastian, I have not noticed any similar problem in any other application that I have used on the system. I am sorry but I am new to using the system and I did not understand if the rendering problems you mentioned refer to any application that I need to test? (...rendering problems in yelp , devhelp or epiphany-browser?) Em ter., 12 de out. de 2021 às 11:35, Sebastien Bacher < 1946...@bugs.launchpad.net> escreveu: > Thank you for your bug report, it seems corruption in webkitgtk views. > Do you get similar rendering problems in yelp , devhelp or epiphany- > browser? > > ** Changed in: xorg (Ubuntu) >Status: New => Incomplete > > ** Summary changed: > > - account setup window becomes unconfigured > + [raspi] screen correct on online accounts webviews > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1946664 > > Title: > [raspi] screen correct on online accounts webviews > > Status in xorg package in Ubuntu: > Incomplete > > Bug description: > I installed ubuntu desktop on my Raspberrypi 4b. I set up the ubuntu > sign-one account, but to set up the Google and Microsoft account, the > window to enter the account data gets misconfigured on the screen and > does not read the fields to enter the data and set up access to my > accounts. > > ProblemType: Bug > DistroRelease: Ubuntu 21.04 > Package: xorg 1:7.7+22ubuntu1 > ProcVersionSignature: Ubuntu 5.11.0-1019.20-raspi 5.11.22 > Uname: Linux 5.11.0-1019-raspi aarch64 > ApportVersion: 2.20.11-0ubuntu65.3 > Architecture: arm64 > BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' > CasperMD5CheckResult: unknown > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Mon Oct 11 12:12:33 2021 > DistUpgraded: Fresh install > DistroCodename: hirsute > DistroVariant: ubuntu > GraphicsCard: > > ImageMediaBuild: 20210421 > Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 > USB 3.0 Host Controller > ProcEnviron: >LANGUAGE=pt_BR:pt:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=pt_BR.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 > snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 > video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:BB:4B:64 > vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 dwc_otg.lpm_enable=0 > console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait > fixrtc quiet splash > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > acpidump: > > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.105-3~21.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 > version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1946664/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1946664 Title: [raspi] screen corruption on online accounts webviews Status in xorg package in Ubuntu: Incomplete Bug description: I installed ubuntu desktop on my Raspberrypi 4b. I set up the ubuntu sign-one account, but to set up the Google and Microsoft account, the window to enter the account data gets misconfigured on the screen and does not read the fields to enter the data and set up access to my accounts. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-1019.20-raspi 5.11.22 Uname: Linux 5.11.0-1019-raspi aarch64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: arm64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 11 12:12:33 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu GraphicsCard: ImageMediaBuild: 20210421 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:BB:4B:64 vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 dwc_otg.lpm_enable=0 console=tty1
[Touch-packages] [Bug 1866371] Re: Mouse cursor disappears in Ubuntu 20.04 on Wayland since 5th March update
I'm not sure it is exactly the same bug, but some users have a similar problem on Fedora 32, so it might be an upstream problem : https://gitlab.gnome.org/GNOME/mutter/issues/1058 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #1058 https://gitlab.gnome.org/GNOME/mutter/issues/1058 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1866371 Title: Mouse cursor disappears in Ubuntu 20.04 on Wayland since 5th March update Status in mutter package in Ubuntu: Confirmed Status in wayland package in Ubuntu: Confirmed Bug description: Hi, I run Ubuntu 20.04 (Gnome Shell) development version. Since I made the updates on 5th March, I have no more mouse cursor visible, on the login screen nor on the desktop session. Mouse is OK, as if I move it I can see some items / buttons highlighted, and if I click the mouse, it works well. I tried Yaru and DMZ Black themes, no cursor, it's completely invisible. I started several times, always no cursor. But if I switch to the Xorg (X11) session, mouse cursor is well back and visible. My graphic card : description: VGA compatible controller produit: Cape Verde XT [Radeon HD 7770/8760 / R7 250X] fabricant: Advanced Micro Devices, Inc. [AMD/ATI] identifiant matériel: 0 information bus: pci@:01:00.0 version: 00 bits: 64 bits horloge: 33MHz fonctionnalités: pm pciexpress msi vga_controller bus_master cap_list rom configuration : driver=radeon latency=0 Thanks ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1866371/+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 1866371] [NEW] Mouse cursor disappears in Ubuntu 20.04 on Wayland since 5th March update
Public bug reported: Hi, I run Ubuntu 20.04 (Gnome Shell) development version. Since I made the updates on 5th March, I have no more mouse cursor visible, on the login screen nor on the desktop session. Mouse is OK, as if I move it I can see some items / buttons highlighted, and if I click the mouse, it works well. I tried Yaru and DMZ Black themes, no cursor, it's completely invisible. I started several times, always no cursor. But if I switch to the Xorg (X11) session, mouse cursor is well back and visible. My graphic card : description: VGA compatible controller produit: Cape Verde XT [Radeon HD 7770/8760 / R7 250X] fabricant: Advanced Micro Devices, Inc. [AMD/ATI] identifiant matériel: 0 information bus: pci@:01:00.0 version: 00 bits: 64 bits horloge: 33MHz fonctionnalités: pm pciexpress msi vga_controller bus_master cap_list rom configuration : driver=radeon latency=0 Thanks ! ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1866371 Title: Mouse cursor disappears in Ubuntu 20.04 on Wayland since 5th March update Status in mutter package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: Hi, I run Ubuntu 20.04 (Gnome Shell) development version. Since I made the updates on 5th March, I have no more mouse cursor visible, on the login screen nor on the desktop session. Mouse is OK, as if I move it I can see some items / buttons highlighted, and if I click the mouse, it works well. I tried Yaru and DMZ Black themes, no cursor, it's completely invisible. I started several times, always no cursor. But if I switch to the Xorg (X11) session, mouse cursor is well back and visible. My graphic card : description: VGA compatible controller produit: Cape Verde XT [Radeon HD 7770/8760 / R7 250X] fabricant: Advanced Micro Devices, Inc. [AMD/ATI] identifiant matériel: 0 information bus: pci@:01:00.0 version: 00 bits: 64 bits horloge: 33MHz fonctionnalités: pm pciexpress msi vga_controller bus_master cap_list rom configuration : driver=radeon latency=0 Thanks ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1866371/+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 1863873] Re: Systemd fails to configure bridged network in LXC container
Thank you so much for your very detailed answer! I understand my mistake and fixed our set-up. -- 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/1863873 Title: Systemd fails to configure bridged network in LXC container Status in systemd package in Ubuntu: Invalid Bug description: In all our LXC containers running Bionic Beaver, Eoan Ermine or Focal Fossa, installing the latest systemd package results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. An example is provided, followed by a complete procedure to reproduce the issue. Affected container distributions Xenial Xerus systemd 229-4ubuntu21.27: OK, not affected Bionic Beaver systemd 237-3ubuntu10.38: OK, not affected Bionic Beaver systemd 237-3ubuntu10.39: BUGGY Disco Dingo systemd 240-6ubuntu5.8: OK, not affected Eoan Ermine systemd 242-7ubuntu3.6: OK, not affected Eoan Ermine systemd 242-7ubuntu3.7: BUGGY Focal Fossa systemd 244.2-1ubuntu1: BUGGY Affected hosts == Debian Buster with default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 kernel Ubuntu 16.04 lxc 2.0.8-0ubuntu1~16.04.2 (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/7) Example === Example host bridge configuration - 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc mq master br0 state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff 3: eth1: mtu 1500 qdisc mq master br1 state DOWN group default qlen 1000 link/ether 00:25:90:2b:f1:61 brd ff:ff:ff:ff:ff:ff 4: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff inet 192.168.252.24/24 brd 192.168.252.255 scope global br0 valid_lft forever preferred_lft forever inet 192.168.193.203/24 brd 192.168.193.255 scope global br0:1 valid_lft forever preferred_lft forever inet6 fe80::225:90ff:fe2b:f160/64 scope link valid_lft forever preferred_lft forever Example container network configuration --- lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Example steps to reproduce, inside the container root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n]
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
** Description changed: - In all our LXC containers running Bionic Beaver, installing systemd - 237-3ubuntu10.39 results in losing network configuration. + In all our LXC containers running Bionic Beaver, Eoan Ermine or Focal + Fossa, installing the latest systemd package results in losing network + configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. An example is provided, followed by a complete procedure to reproduce the issue. Affected container distributions Xenial Xerus systemd 229-4ubuntu21.27: OK, not affected Bionic Beaver systemd 237-3ubuntu10.38: OK, not affected Bionic Beaver systemd 237-3ubuntu10.39: BUGGY Disco Dingo systemd 240-6ubuntu5.8: OK, not affected Eoan Ermine systemd 242-7ubuntu3.6: OK, not affected Eoan Ermine systemd 242-7ubuntu3.7: BUGGY Focal Fossa systemd 244.2-1ubuntu1: BUGGY Affected hosts == Debian Buster with default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 kernel Ubuntu 16.04 lxc 2.0.8-0ubuntu1~16.04.2 (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/7) Example === Example host bridge configuration - 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc mq master br0 state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff 3: eth1: mtu 1500 qdisc mq master br1 state DOWN group default qlen 1000 link/ether 00:25:90:2b:f1:61 brd ff:ff:ff:ff:ff:ff 4: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff inet 192.168.252.24/24 brd 192.168.252.255 scope global br0 valid_lft forever preferred_lft forever inet 192.168.193.203/24 brd 192.168.193.255 scope global br0:1 valid_lft forever preferred_lft forever inet6 fe80::225:90ff:fe2b:f160/64 scope link valid_lft forever preferred_lft forever Example container network configuration --- lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Example steps to reproduce, inside the container root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB]
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
** Description changed: In all our LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. An example is provided, followed by a complete procedure to reproduce the issue. Affected container distributions Xenial Xerus systemd 229-4ubuntu21.27: OK, not affected Bionic Beaver systemd 237-3ubuntu10.38: OK, not affected Bionic Beaver systemd 237-3ubuntu10.39: BUGGY Disco Dingo systemd 240-6ubuntu5.8: OK, not affected Eoan Ermine systemd 242-7ubuntu3.6: OK, not affected Eoan Ermine systemd 242-7ubuntu3.7: BUGGY Focal Fossa systemd 244.2-1ubuntu1: BUGGY Affected hosts == Debian Buster with default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 kernel Ubuntu 16.04 lxc 2.0.8-0ubuntu1~16.04.2 (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/7) Example === Example host bridge configuration - 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc mq master br0 state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff 3: eth1: mtu 1500 qdisc mq master br1 state DOWN group default qlen 1000 link/ether 00:25:90:2b:f1:61 brd ff:ff:ff:ff:ff:ff 4: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff inet 192.168.252.24/24 brd 192.168.252.255 scope global br0 valid_lft forever preferred_lft forever inet 192.168.193.203/24 brd 192.168.193.255 scope global br0:1 valid_lft forever preferred_lft forever inet6 fe80::225:90ff:fe2b:f160/64 scope link valid_lft forever preferred_lft forever Example container network configuration --- lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Example steps to reproduce, inside the container root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.39 [2912 kB] Get:4 http://archive.ubuntu.com/ubuntu
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
** Description changed: In all our LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. An example is provided, followed by a complete procedure to reproduce the issue. Affected container distributions Xenial Xerus systemd 229-4ubuntu21.27: OK, not affected Bionic Beaver systemd 237-3ubuntu10.38: OK, not affected Bionic Beaver systemd 237-3ubuntu10.39: BUGGY Disco Dingo systemd 240-6ubuntu5.8: OK, not affected Eoan Ermine systemd 242-7ubuntu3.6: OK, not affected Eoan Ermine systemd 242-7ubuntu3.7: BUGGY Focal Fossa systemd 244.2-1ubuntu1: BUGGY Affected hosts == Debian Buster with default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 kernel Ubuntu 16.04 lxc 2.0.8-0ubuntu1~16.04.2 (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/7) Example === Example host bridge configuration - 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc mq master br0 state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff 3: eth1: mtu 1500 qdisc mq master br1 state DOWN group default qlen 1000 link/ether 00:25:90:2b:f1:61 brd ff:ff:ff:ff:ff:ff 4: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff inet 192.168.252.24/24 brd 192.168.252.255 scope global br0 valid_lft forever preferred_lft forever inet 192.168.193.203/24 brd 192.168.193.255 scope global br0:1 valid_lft forever preferred_lft forever inet6 fe80::225:90ff:fe2b:f160/64 scope link valid_lft forever preferred_lft forever Example container network configuration --- lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Example steps to reproduce, inside the container root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.39 [2912 kB] Get:4 http://archive.ubuntu.com/ubuntu
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
** Description changed: In all our LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. - Affected distributions - == - - Bionic Beaver systemd 237-3ubuntu10.38: OK + A complete procedure to reproduce the issue is available below. + + Affected container distributions + + + Xenial Xerus systemd 229-4ubuntu21.27: OK, not affected + Bionic Beaver systemd 237-3ubuntu10.38: OK, not affected Bionic Beaver systemd 237-3ubuntu10.39: BUGGY - Disco Dingo 240-6ubuntu5.8: OK - Eoan Ermine systemd 242-7ubuntu3.6: OK + Disco Dingo systemd 240-6ubuntu5.8: OK, not affected + Eoan Ermine systemd 242-7ubuntu3.6: OK, not affected Eoan Ermine systemd 242-7ubuntu3.7: BUGGY Focal Fossa systemd 244.2-1ubuntu1: BUGGY Affected hosts == Debian Buster with default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 kernel Ubuntu 16.04 lxc 2.0.8-0ubuntu1~16.04.2 (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/7) Example === Example host bridge configuration - 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc mq master br0 state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff 3: eth1: mtu 1500 qdisc mq master br1 state DOWN group default qlen 1000 link/ether 00:25:90:2b:f1:61 brd ff:ff:ff:ff:ff:ff 4: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff inet 192.168.252.24/24 brd 192.168.252.255 scope global br0 valid_lft forever preferred_lft forever inet 192.168.193.203/24 brd 192.168.193.255 scope global br0:1 valid_lft forever preferred_lft forever inet6 fe80::225:90ff:fe2b:f160/64 scope link valid_lft forever preferred_lft forever Example container network configuration --- lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Steps to reproduce, inside the container root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
** Description changed: - In all our unprivileged LXC containers running Bionic Beaver, installing - systemd 237-3ubuntu10.39 results in losing network configuration. + In all our LXC containers running Bionic Beaver, installing systemd + 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. A complete procedure to reproduce the issue is here: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/6 - Affected distributions: + Affected distributions + == Bionic Beaver systemd 237-3ubuntu10.38: OK Bionic Beaver systemd 237-3ubuntu10.39: BUGGY Disco Dingo 240-6ubuntu5.8: OK Eoan Ermine systemd 242-7ubuntu3.6: OK Eoan Ermine systemd 242-7ubuntu3.7: BUGGY Focal Fossa systemd 244.2-1ubuntu1: BUGGY - - Hosts: - - Debian Buster - default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 kernel - - Example container network configuration: + + Affected hosts + == + + Debian Buster with default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 + kernel + + Example host bridge configuration + = + + 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 + link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 + inet 127.0.0.1/8 scope host lo +valid_lft forever preferred_lft forever + inet6 ::1/128 scope host +valid_lft forever preferred_lft forever + 2: eth0: mtu 1500 qdisc mq master br0 state UP group default qlen 1000 + link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff + 3: eth1: mtu 1500 qdisc mq master br1 state DOWN group default qlen 1000 + link/ether 00:25:90:2b:f1:61 brd ff:ff:ff:ff:ff:ff + 4: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 + link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff + inet 192.168.252.24/24 brd 192.168.252.255 scope global br0 +valid_lft forever preferred_lft forever + inet 192.168.193.203/24 brd 192.168.193.255 scope global br0:1 +valid_lft forever preferred_lft forever + inet6 fe80::225:90ff:fe2b:f160/64 scope link +valid_lft forever preferred_lft forever + + Example container network configuration + === lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 - Steps to reproduce, inside the container: + Steps to reproduce, inside the container + root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3 http://archive.ubuntu.com/ubuntu
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
** Description changed: In all our unprivileged LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. A complete procedure to reproduce the issue is here: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/6 Affected distributions: Bionic Beaver systemd 237-3ubuntu10.38: OK Bionic Beaver systemd 237-3ubuntu10.39: BUGGY Disco Dingo 240-6ubuntu5.8: OK Eoan Ermine systemd 242-7ubuntu3.6: OK Eoan Ermine systemd 242-7ubuntu3.7: BUGGY - + Focal Fossa systemd 244.2-1ubuntu1: BUGGY + Hosts: Debian Buster default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 kernel Example container network configuration: lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Steps to reproduce, inside the container: root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.39 [2912 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsystemd0 amd64 237-3ubuntu10.39 [206 kB] Fetched 3330 kB in 3s (1274 kB/s) (Reading database ... 18195 files and directories currently installed.) Preparing to unpack .../libnss-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libnss-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libpam-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libpam-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../systemd_237-3ubuntu10.39_amd64.deb ... Unpacking systemd (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libsystemd0_237-3ubuntu10.39_amd64.deb ... Unpacking libsystemd0:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Setting up libsystemd0:amd64 (237-3ubuntu10.39) ... Setting up systemd (237-3ubuntu10.39) ... Setting up libnss-systemd:amd64 (237-3ubuntu10.39) ... Setting up libpam-systemd:amd64 (237-3ubuntu10.39) ... Processing triggers for dbus (1.12.2-1ubuntu1.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
** Description changed: In all our unprivileged LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. A complete procedure to reproduce the issue is here: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/6 - + + Affected distributions: + + Bionic Beaver systemd 237-3ubuntu10.38: OK + Bionic Beaver systemd 237-3ubuntu10.39: BUGGY + Disco Dingo 240-6ubuntu5.8: OK + Eoan Ermine systemd 242-7ubuntu3.6: OK + Eoan Ermine systemd 242-7ubuntu3.7: BUGGY + Hosts: Debian Buster default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 kernel Example container network configuration: lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Steps to reproduce, inside the container: root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.39 [2912 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsystemd0 amd64 237-3ubuntu10.39 [206 kB] Fetched 3330 kB in 3s (1274 kB/s) (Reading database ... 18195 files and directories currently installed.) Preparing to unpack .../libnss-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libnss-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libpam-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libpam-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../systemd_237-3ubuntu10.39_amd64.deb ... Unpacking systemd (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libsystemd0_237-3ubuntu10.39_amd64.deb ... Unpacking libsystemd0:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Setting up libsystemd0:amd64 (237-3ubuntu10.39) ... Setting up systemd (237-3ubuntu10.39) ... Setting up libnss-systemd:amd64 (237-3ubuntu10.39) ... Setting up libpam-systemd:amd64 (237-3ubuntu10.39) ... Processing triggers for dbus (1.12.2-1ubuntu1.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
** Description changed: In all our unprivileged LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. + A complete procedure to reproduce the issue is here: + https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/6 + Hosts: Debian Buster - custom 5.3.9, 5.4.8 or 5.4.13 kernel + default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 kernel Example container network configuration: lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Steps to reproduce, inside the container: root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: - Installed: 237-3ubuntu10.38 - Candidate: 237-3ubuntu10.39 - Version table: - 237-3ubuntu10.39 500 - 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages - *** 237-3ubuntu10.38 500 - 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages - 100 /var/lib/dpkg/status - 237-3ubuntu10 500 - 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages + Installed: 237-3ubuntu10.38 + Candidate: 237-3ubuntu10.39 + Version table: + 237-3ubuntu10.39 500 + 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages + *** 237-3ubuntu10.38 500 + 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages + 100 /var/lib/dpkg/status + 237-3ubuntu10 500 + 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 - link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 - inet 127.0.0.1/8 scope host lo -valid_lft forever preferred_lft forever - inet6 ::1/128 scope host -valid_lft forever preferred_lft forever + link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 + inet 127.0.0.1/8 scope host lo + valid_lft forever preferred_lft forever + inet6 ::1/128 scope host + valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 - link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 - inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 -valid_lft forever preferred_lft forever - inet6 ::x:xx::x:/128 scope global -valid_lft forever preferred_lft forever - inet6 ::xx::/64 scope link -valid_lft forever preferred_lft forever + link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 + inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 + valid_lft forever preferred_lft forever + inet6 ::x:xx::x:/128 scope global + valid_lft forever preferred_lft forever + inet6 ::xx::/64 scope link + valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: - libnss-systemd libpam-systemd libsystemd0 + libnss-systemd libpam-systemd libsystemd0 Suggested packages: - systemd-container policykit-1 + systemd-container policykit-1 The following packages will be upgraded: - libnss-systemd libpam-systemd libsystemd0 systemd + libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.39 [2912 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsystemd0 amd64 237-3ubuntu10.39 [206 kB] Fetched 3330 kB in 3s (1274 kB/s) (Reading database ... 18195 files and directories currently installed.) Preparing to unpack .../libnss-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libnss-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libpam-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libpam-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
Here is a full procedure to reproduce the issue. Set-up == 1. Install an amd64 Debian Buster (default network install), 2. install lxc and create a bionic amd64 container, ```bash apt install lxc lxc-create -t download -n bionic lxc-start -n bionic ``` 3. inside the container, deactivate dhcp (dhcp4: false )in `/etc/netplan/10-lxc.yaml`, and install the systemd packages without the bug, ```bash lxc-attach -n bionic sed -i 's/true/false/' /etc/netplan/10-lxc.yaml apt install systemd=237-3ubuntu10.38 libsystemd0=237-3ubuntu10.38 libnss-systemd=237-3ubuntu10.38 libpam-systemd=237-3ubuntu10.38 exit ``` 4. create a bridge on the host with a static IP and deactivate dhcp, in `/etc/network/interfaces`, ``` # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback ## The primary network interface #allow-hotplug ens18 #iface ens18 inet dhcp ## This is an autoconfigured IPv6 interface #iface ens18 inet6 auto iface ens18 inet manual auto br0 iface br0 inet static address 192.168.1.168 netmask 255.255.255.0 gateway 192.168.1.220 bridge_ports ens18 bridge_stp off bridge_waitport 0 bridge_fd 0 ``` 5. on the host, modify the network configuration of the container to use the bridge with a static IP in `/var/lib/lxc/bionic/config`, ``` # Template used to create this container: /usr/share/lxc/templates/lxc-download # Parameters passed to the template: # Template script checksum (SHA-1): 273c51343604eb85f7e294c8da0a5eb769d648f3 # For additional config options, please look at lxc.container.conf(5) # Uncomment the following line to support nesting containers: #lxc.include = /usr/share/lxc/config/nesting.conf # (Be aware this has security implications) # Distribution configuration lxc.include = /usr/share/lxc/config/common.conf # For Ubuntu 14.04 lxc.mount.entry = /sys/kernel/debug sys/kernel/debug none bind,optional 0 0 lxc.mount.entry = /sys/kernel/security sys/kernel/security none bind,optional 0 0 lxc.mount.entry = /sys/fs/pstore sys/fs/pstore none bind,optional 0 0 lxc.mount.entry = mqueue dev/mqueue mqueue rw,relatime,create=dir,optional 0 0 lxc.arch = linux64 # Container specific configuration lxc.apparmor.profile = generated lxc.apparmor.allow_nesting = 1 lxc.rootfs.path = dir:/var/lib/lxc/bionic/rootfs lxc.uts.name = bionic ## Network configuration #lxc.net.0.type = empty # Network configuration lxc.net.0.type = veth lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.1.220 lxc.net.0.ipv4.address = 192.168.1.169/32 ``` 6. reboot the host. ```bash reboot ``` Let’s do it === 1. Start the container and check the IP config, which should be ok, ```bash lxc-start -n bionic lxc-attach -n bionic ip a ``` 2. upgrade the system and check the IP config, the static is gone. ```bash apt upgrade ip a exit ``` If systemd is downgraded again to 237-3ubuntu10.38, the IP is back at the next reboot of the container. -- 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/1863873 Title: Systemd fails to configure bridged network in LXC container Status in systemd package in Ubuntu: Incomplete Bug description: In all our unprivileged LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. A complete procedure to reproduce the issue is here: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/6 Hosts: Debian Buster default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 kernel Example container network configuration: lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Steps to reproduce, inside the container: root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
Just in case, I also removed any arptables or iptables on the host. The problem is still present. Here is an even simpler LXC configuration file to reproduce (privileged LXC container on Debian Buster, 5.4.13 kernel): # Distribution configuration lxc.include = /usr/share/lxc/config/common.conf lxc.arch = linux64 # Container specific configuration lxc.hook.pre-start = /usr/local/share/lxc/hooks/pre-start.sh vps526706 lxc.hook.post-stop = /usr/local/share/lxc/hooks/post-stop.sh vps526706 lxc.hook.destroy = /usr/local/share/lxc/hooks/destroy.sh vps526706 lxc.mount.fstab = /lxc/vps526706/fstab lxc.rootfs.path = dir:/lxc/vps526706/rootfs lxc.uts.name = vps526706 # Network configuration lxc.net.0.type = veth lxc.net.0.veth.pair = vps526706 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:67:06 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.171/32 -- 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/1863873 Title: Systemd fails to configure bridged network in LXC container Status in systemd package in Ubuntu: Incomplete Bug description: In all our unprivileged LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. Hosts: Debian Buster custom 5.3.9, 5.4.8 or 5.4.13 kernel Example container network configuration: lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Steps to reproduce, inside the container: root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.39 [2912 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsystemd0 amd64 237-3ubuntu10.39 [206 kB] Fetched 3330 kB in 3s (1274 kB/s) (Reading database ... 18195 files and directories currently installed.) Preparing to unpack .../libnss-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libnss-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libpam-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libpam-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../systemd_237-3ubuntu10.39_amd64.deb ... Unpacking systemd (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libsystemd0_237-3ubuntu10.39_amd64.deb ... Unpacking
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
The problem is also present in eoan and focal, but not disco (unprivileged LXC containers, 5.4.13 kernel). -- 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/1863873 Title: Systemd fails to configure bridged network in LXC container Status in systemd package in Ubuntu: Incomplete Bug description: In all our unprivileged LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. Hosts: Debian Buster custom 5.3.9, 5.4.8 or 5.4.13 kernel Example container network configuration: lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Steps to reproduce, inside the container: root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.39 [2912 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsystemd0 amd64 237-3ubuntu10.39 [206 kB] Fetched 3330 kB in 3s (1274 kB/s) (Reading database ... 18195 files and directories currently installed.) Preparing to unpack .../libnss-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libnss-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libpam-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libpam-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../systemd_237-3ubuntu10.39_amd64.deb ... Unpacking systemd (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libsystemd0_237-3ubuntu10.39_amd64.deb ... Unpacking libsystemd0:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Setting up libsystemd0:amd64 (237-3ubuntu10.39) ... Setting up systemd (237-3ubuntu10.39) ... Setting up libnss-systemd:amd64 (237-3ubuntu10.39) ... Setting up libpam-systemd:amd64 (237-3ubuntu10.39) ... Processing triggers for dbus (1.12.2-1ubuntu1.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
The problem is also present in privileged LXC containers. Example with full LXC configuration below, on a host with a custom 5.4.13 kernel. # Distribution configuration lxc.include = /usr/share/lxc/config/common.conf # For Ubuntu 14.04 lxc.mount.entry = /sys/kernel/debug sys/kernel/debug none bind,optional 0 0 lxc.mount.entry = /sys/kernel/security sys/kernel/security none bind,optional 0 0 lxc.mount.entry = /sys/fs/pstore sys/fs/pstore none bind,optional 0 0 lxc.mount.entry = mqueue dev/mqueue mqueue rw,relatime,create=dir,optional 0 0 lxc.include = /usr/share/lxc/config/userns.conf # For Ubuntu 14.04 lxc.mount.entry = /sys/firmware/efi/efivars sys/firmware/efi/efivars none bind,optional 0 0 lxc.mount.entry = /proc/sys/fs/binfmt_misc proc/sys/fs/binfmt_misc none bind,optional 0 0 lxc.arch = linux64 lxc.hook.pre-start = /usr/local/share/lxc/hooks/pre-start.sh vps526706 lxc.hook.post-stop = /usr/local/share/lxc/hooks/post-stop.sh vps526706 lxc.hook.destroy = /usr/local/share/lxc/hooks/destroy.sh vps526706 lxc.mount.fstab = /lxc/vps526706/fstab lxc.rootfs.path = dir:/lxc/vps526706/rootfs lxc.uts.name = vps526706 # Network configuration lxc.net.0.type = veth lxc.net.0.veth.pair = vps526706 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:67:06 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.171/32 -- 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/1863873 Title: Systemd fails to configure bridged network in LXC container Status in systemd package in Ubuntu: Incomplete Bug description: In all our unprivileged LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. Hosts: Debian Buster custom 5.3.9, 5.4.8 or 5.4.13 kernel Example container network configuration: lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Steps to reproduce, inside the container: root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.39 [2912 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsystemd0 amd64 237-3ubuntu10.39 [206 kB] Fetched 3330 kB in 3s (1274 kB/s) (Reading database ... 18195 files and directories currently installed.) Preparing to unpack
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
Did you do your test in an unprivileged LXC container? -- 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/1863873 Title: Systemd fails to configure bridged network in LXC container Status in systemd package in Ubuntu: Incomplete Bug description: In all our unprivileged LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. Hosts: Debian Buster custom 5.3.9, 5.4.8 or 5.4.13 kernel Example container network configuration: lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Steps to reproduce, inside the container: root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.39 [2912 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsystemd0 amd64 237-3ubuntu10.39 [206 kB] Fetched 3330 kB in 3s (1274 kB/s) (Reading database ... 18195 files and directories currently installed.) Preparing to unpack .../libnss-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libnss-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libpam-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libpam-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../systemd_237-3ubuntu10.39_amd64.deb ... Unpacking systemd (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libsystemd0_237-3ubuntu10.39_amd64.deb ... Unpacking libsystemd0:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Setting up libsystemd0:amd64 (237-3ubuntu10.39) ... Setting up systemd (237-3ubuntu10.39) ... Setting up libnss-systemd:amd64 (237-3ubuntu10.39) ... Setting up libpam-systemd:amd64 (237-3ubuntu10.39) ... Processing triggers for dbus (1.12.2-1ubuntu1.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet6
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
** Description changed: In all our unprivileged LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. + + It is still possible to configure the network "by hand" with + /usr/sbin/ip, but of course, the configuration is lost at reboot. Hosts: Debian Buster - custom 5.3.9 or 5.4.8 kernel + custom 5.3.9, 5.4.8 or 5.4.13 kernel Example container network configuration: lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Steps to reproduce, inside the container: root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: - Installed: 237-3ubuntu10.38 - Candidate: 237-3ubuntu10.39 - Version table: - 237-3ubuntu10.39 500 - 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages - *** 237-3ubuntu10.38 500 - 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages - 100 /var/lib/dpkg/status - 237-3ubuntu10 500 - 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages + Installed: 237-3ubuntu10.38 + Candidate: 237-3ubuntu10.39 + Version table: + 237-3ubuntu10.39 500 + 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages + *** 237-3ubuntu10.38 500 + 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages + 100 /var/lib/dpkg/status + 237-3ubuntu10 500 + 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 - link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 - inet 127.0.0.1/8 scope host lo - valid_lft forever preferred_lft forever - inet6 ::1/128 scope host - valid_lft forever preferred_lft forever + link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 + inet 127.0.0.1/8 scope host lo +valid_lft forever preferred_lft forever + inet6 ::1/128 scope host +valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 - link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 - inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 - valid_lft forever preferred_lft forever - inet6 ::x:xx::x:/128 scope global - valid_lft forever preferred_lft forever - inet6 ::xx::/64 scope link - valid_lft forever preferred_lft forever + link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 + inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 +valid_lft forever preferred_lft forever + inet6 ::x:xx::x:/128 scope global +valid_lft forever preferred_lft forever + inet6 ::xx::/64 scope link +valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: - libnss-systemd libpam-systemd libsystemd0 + libnss-systemd libpam-systemd libsystemd0 Suggested packages: - systemd-container policykit-1 + systemd-container policykit-1 The following packages will be upgraded: - libnss-systemd libpam-systemd libsystemd0 systemd + libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.39 [2912 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsystemd0 amd64 237-3ubuntu10.39 [206 kB] Fetched 3330 kB in 3s (1274 kB/s) (Reading database ... 18195 files and directories currently installed.) Preparing to unpack .../libnss-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libnss-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libpam-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libpam-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../systemd_237-3ubuntu10.39_amd64.deb ... Unpacking systemd (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libsystemd0_237-3ubuntu10.39_amd64.deb ... Unpacking
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
** Description changed: In all our unprivileged LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. - Host: + Hosts: debian buster - custom 5.3.9 or 5.4.8 kernel + custom 5.3.9 or 5.4.8 kernel Example container network configuration: lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Steps to reproduce, inside the container: root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.39 [2912 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsystemd0 amd64 237-3ubuntu10.39 [206 kB] Fetched 3330 kB in 3s (1274 kB/s) (Reading database ... 18195 files and directories currently installed.) Preparing to unpack .../libnss-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libnss-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libpam-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libpam-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../systemd_237-3ubuntu10.39_amd64.deb ... Unpacking systemd (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libsystemd0_237-3ubuntu10.39_amd64.deb ... Unpacking libsystemd0:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Setting up libsystemd0:amd64 (237-3ubuntu10.39) ... Setting up systemd (237-3ubuntu10.39) ... Setting up libnss-systemd:amd64 (237-3ubuntu10.39) ... Setting up libpam-systemd:amd64 (237-3ubuntu10.39) ... Processing triggers for dbus (1.12.2-1ubuntu1.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet6 fe80::ff:fe52:5389/64 scope link valid_lft forever preferred_lft forever ** Description changed: In all our unprivileged LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. Hosts: - debian buster + Debian Buster custom 5.3.9 or 5.4.8 kernel Example container network configuration: lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
** Description changed: In all our unprivileged LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. Host: debian buster - custom 5.3.9 kernel + custom 5.3.9 or 5.4.8 kernel Example container network configuration: lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Steps to reproduce, inside the container: root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever - inet6 ::x:xx::x:/128 scope global -valid_lft forever preferred_lft forever - inet6 ::xx::/64 scope link -valid_lft forever preferred_lft forever + inet6 ::x:xx::x:/128 scope global + valid_lft forever preferred_lft forever + inet6 ::xx::/64 scope link + valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.39 [2912 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsystemd0 amd64 237-3ubuntu10.39 [206 kB] Fetched 3330 kB in 3s (1274 kB/s) (Reading database ... 18195 files and directories currently installed.) Preparing to unpack .../libnss-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libnss-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libpam-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libpam-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../systemd_237-3ubuntu10.39_amd64.deb ... Unpacking systemd (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libsystemd0_237-3ubuntu10.39_amd64.deb ... Unpacking libsystemd0:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Setting up libsystemd0:amd64 (237-3ubuntu10.39) ... Setting up systemd (237-3ubuntu10.39) ... Setting up libnss-systemd:amd64 (237-3ubuntu10.39) ... Setting up libpam-systemd:amd64 (237-3ubuntu10.39) ... Processing triggers for dbus (1.12.2-1ubuntu1.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet6 fe80::ff:fe52:5389/64 scope link valid_lft forever preferred_lft forever -- 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/1863873 Title:
[Touch-packages] [Bug 1863873] [NEW] Systemd fails to configure bridged network in LXC container
Public bug reported: In all our unprivileged LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. Host: debian buster custom 5.3.9 or 5.4.8 kernel Example container network configuration: lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Steps to reproduce, inside the container: root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.39 [2912 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsystemd0 amd64 237-3ubuntu10.39 [206 kB] Fetched 3330 kB in 3s (1274 kB/s) (Reading database ... 18195 files and directories currently installed.) Preparing to unpack .../libnss-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libnss-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libpam-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libpam-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../systemd_237-3ubuntu10.39_amd64.deb ... Unpacking systemd (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libsystemd0_237-3ubuntu10.39_amd64.deb ... Unpacking libsystemd0:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Setting up libsystemd0:amd64 (237-3ubuntu10.39) ... Setting up systemd (237-3ubuntu10.39) ... Setting up libnss-systemd:amd64 (237-3ubuntu10.39) ... Setting up libpam-systemd:amd64 (237-3ubuntu10.39) ... Processing triggers for dbus (1.12.2-1ubuntu1.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet6 fe80::ff:fe52:5389/64 scope link valid_lft forever preferred_lft forever ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: - In all unprivileged LXC container running Bionic Beaver, installing + In all our unprivileged LXC container running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. Host: debian buster custom 5.3.9 kernel Example container network configuration: lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0
[Touch-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
I also have the problem with 18.04.4 LTS (up to date at time of writting). It seems to be related to the Wifi infrastructure since the problem appeared for me a few months ago (running successfully from May 2018 to Oct 2019). However many other devices can connect successfully to the Wifi Infrastructure so there should be an incompatibility with it. The problem is with the following Auth: WPA2 Enterprise, PEAP, No CA check, automatic PEAP version, MSCHAPv2. Feb 1 12:21:34 ubuntu wpa_supplicant[1203]: wifi: SME: Trying to authenticate with F2-28-3C-99-C2-78 (SSID='ACME-staff' freq=5220 MHz) Feb 1 12:21:34 ubuntu wpa_supplicant[1203]: wifi: Trying to associate with F2-28-3C-99-C2-78 (SSID='ACME-staff' freq=5220 MHz) Feb 1 12:21:34 ubuntu wpa_supplicant[1203]: wifi: Associated with F2-28-3C-99-C2-78 Feb 1 12:21:34 ubuntu wpa_supplicant[1203]: wifi: CTRL-EVENT-EAP-STARTED EAP authentication started Feb 1 12:21:34 ubuntu wpa_supplicant[1203]: wifi: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Feb 1 12:21:34 ubuntu wpa_supplicant[1203]: wifi: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25 Feb 1 12:21:34 ubuntu wpa_supplicant[1203]: wifi: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected Feb 1 12:21:35 ubuntu wpa_supplicant[1203]: wifi: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='***HIDDEN' hash=2ac69dd2691f34f4408106fa96dd4da66dca716d3068cc33f54d1c8887cc325a Feb 1 12:21:35 ubuntu wpa_supplicant[1203]: wifi: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:***HIDDEN Feb 1 12:21:35 ubuntu wpa_supplicant[1203]: wifi: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:***HIDDEN Feb 1 12:21:35 ubuntu wpa_supplicant[1203]: wifi: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='***HIDDEN' hash=2ac69dd2691f34f4408106fa96dd4da66dca716d3068cc33f54d1c8887cc325a Feb 1 12:21:35 ubuntu wpa_supplicant[1203]: wifi: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:***HIDDEN Feb 1 12:21:35 ubuntu wpa_supplicant[1203]: wifi: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:***HIDDEN Feb 1 12:21:35 ubuntu wpa_supplicant[1203]: OpenSSL: tls_connection_decrypt - Decryption failed - SSL_read error::lib(0):func(0):reason(0) Feb 1 12:21:35 ubuntu wpa_supplicant[1203]: SSL: Failed to decrypt Phase 2 data Feb 1 12:21:59 ubuntu wpa_supplicant[1203]: wifi: CTRL-EVENT-DISCONNECTED bssid=F2-28-3C-99-C2-78 reason=3 locally_generated=1 Feb 1 12:22:11 ubuntu wpa_supplicant[1203]: FT: Invalid key management type (1) So there is definitely a problem in LTS which is still not fixed. -- 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/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: This problem is also happened on my desktop. After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no CA certificate/true username and password. I tried to solve the problem following URL link; however, it could not help me also. https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, OS: Ubuntu 18.04.1 (64-bit). root@joe-UBTPC:/root # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI
[Touch-packages] [Bug 1850103] Re: gnome-tweak-tool window keeps flickering on cursor hovering [Intel Penryn: Core 2 T6600]
Well, the same problem happens in the "Parameters" dashboard. If I get it well, there are three breakpoints: * no left-menu displayed * a narrow left-menu displayed * a larger left-menu displayed In the case of a narrow left menu, flicker happens at least in the Tweak tool and Parameters app. See attached screenshot (flickering happens at a much higher framerate than the gif displays it, as if width were computed in a loop) ** Attachment added: "Peek 31-10-2019 14-01.gif" https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1850103/+attachment/5301770/+files/Peek%2031-10-2019%2014-01.gif -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1850103 Title: gnome-tweak-tool window keeps flickering on cursor hovering [Intel Penryn: Core 2 T6600] Status in gnome-tweaks package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: the gnome-tweak-tool window keeps flickering abnormally. this might be a bug as i have seen somebody else mention the issue somewhere in the internet. i do have the screencast of the phenomenon i can send it to you for the review of the problem i am facing. i am on ubuntu 19.10 system installed via bootable usb. before i had interrupted network upgrade of the system which was recovered via grub recovery mode. since i thought the flickering was due to all this, i fresh installed the system via bootable usb. still the problem is persistent and its abnormal irrespective of the animation button turned on or off. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-26 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: mutter PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Tags: wayland-session eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1850103/+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 1850103] Re: gnome-tweak-tool window keeps flickering on cursor hovering [Intel Penryn: Core 2 T6600]
I can confirm the bug, exact same behavior here. Upgraded from ubuntu 19.04 and same flickering effect. * I open the Tweak tool window * I try to hover one of the left menu's items -> it flickers, I can not manage to click on a menu item sucessfully * If I resize the window (I have to make it larger so that the menu displays larger), then the menu works as expected and the flickering effect disappears - I have to do it everytime I launch the app, though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1850103 Title: gnome-tweak-tool window keeps flickering on cursor hovering [Intel Penryn: Core 2 T6600] Status in gnome-tweaks package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: the gnome-tweak-tool window keeps flickering abnormally. this might be a bug as i have seen somebody else mention the issue somewhere in the internet. i do have the screencast of the phenomenon i can send it to you for the review of the problem i am facing. i am on ubuntu 19.10 system installed via bootable usb. before i had interrupted network upgrade of the system which was recovered via grub recovery mode. since i thought the flickering was due to all this, i fresh installed the system via bootable usb. still the problem is persistent and its abnormal irrespective of the animation button turned on or off. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-26 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: mutter PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Tags: wayland-session eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1850103/+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 1812474] Re: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive
The bug was apparently a dupe of https://gitlab.gnome.org/GNOME/evolution-ews/issues/18 and should be fixed in "3.30.2+". However if I understood correctly if I already have a crashing addressbook, even with the bugfix it will keep on crashing unless I manually delete the cache file buried somewhere in $HOME/.cache/evolution/ - which is not very user-friendly ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1812474 Title: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive Status in evolution-data-server package in Ubuntu: Incomplete Bug description: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive; the GUI doesn't respond (gnome-shell's clock is stopped, the mouse pointer is stopped) and it lasts for a few minutes, then goes back to normal. If I wait long enough, the addressbook crashes (not enough memory ?). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evolution-data-server 3.30.1-1build1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jan 19 09:59:18 2019 ExecutablePath: /usr/lib/evolution/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2017-01-09 (740 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evolution-data-server UpgradeStatus: Upgraded to cosmic on 2018-10-19 (92 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1812474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1812474] Re: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive
Oh I wasn't notified about Milan's answer. Sure I'll reinstall the addressbook (I've deleted it for now) and get a backtrace - in my copious spare time. Cheers, Xav -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1812474 Title: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive Status in evolution-data-server package in Ubuntu: Incomplete Bug description: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive; the GUI doesn't respond (gnome-shell's clock is stopped, the mouse pointer is stopped) and it lasts for a few minutes, then goes back to normal. If I wait long enough, the addressbook crashes (not enough memory ?). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evolution-data-server 3.30.1-1build1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jan 19 09:59:18 2019 ExecutablePath: /usr/lib/evolution/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2017-01-09 (740 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evolution-data-server UpgradeStatus: Upgraded to cosmic on 2018-10-19 (92 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1812474/+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 1812474] Re: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive
Sure. How do I do that ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1812474 Title: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive Status in evolution-data-server package in Ubuntu: Incomplete Bug description: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive; the GUI doesn't respond (gnome-shell's clock is stopped, the mouse pointer is stopped) and it lasts for a few minutes, then goes back to normal. If I wait long enough, the addressbook crashes (not enough memory ?). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evolution-data-server 3.30.1-1build1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jan 19 09:59:18 2019 ExecutablePath: /usr/lib/evolution/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2017-01-09 (740 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evolution-data-server UpgradeStatus: Upgraded to cosmic on 2018-10-19 (92 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1812474/+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 1812474] Re: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive
Done: https://gitlab.gnome.org/GNOME/evolution-data-server/issues/78 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1812474 Title: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive Status in evolution-data-server package in Ubuntu: New Bug description: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive; the GUI doesn't respond (gnome-shell's clock is stopped, the mouse pointer is stopped) and it lasts for a few minutes, then goes back to normal. If I wait long enough, the addressbook crashes (not enough memory ?). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evolution-data-server 3.30.1-1build1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jan 19 09:59:18 2019 ExecutablePath: /usr/lib/evolution/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2017-01-09 (740 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evolution-data-server UpgradeStatus: Upgraded to cosmic on 2018-10-19 (92 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1812474/+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 1812474] Re: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive
FWIW my system has 8GB RAM. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1812474 Title: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive Status in evolution-data-server package in Ubuntu: New Bug description: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive; the GUI doesn't respond (gnome-shell's clock is stopped, the mouse pointer is stopped) and it lasts for a few minutes, then goes back to normal. If I wait long enough, the addressbook crashes (not enough memory ?). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evolution-data-server 3.30.1-1build1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jan 19 09:59:18 2019 ExecutablePath: /usr/lib/evolution/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2017-01-09 (740 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evolution-data-server UpgradeStatus: Upgraded to cosmic on 2018-10-19 (92 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1812474/+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 1812474] [NEW] /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive
Public bug reported: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive; the GUI doesn't respond (gnome-shell's clock is stopped, the mouse pointer is stopped) and it lasts for a few minutes, then goes back to normal. If I wait long enough, the addressbook crashes (not enough memory ?). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evolution-data-server 3.30.1-1build1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jan 19 09:59:18 2019 ExecutablePath: /usr/lib/evolution/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2017-01-09 (740 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evolution-data-server UpgradeStatus: Upgraded to cosmic on 2018-10-19 (92 days ago) ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1812474 Title: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive Status in evolution-data-server package in Ubuntu: New Bug description: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive; the GUI doesn't respond (gnome-shell's clock is stopped, the mouse pointer is stopped) and it lasts for a few minutes, then goes back to normal. If I wait long enough, the addressbook crashes (not enough memory ?). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evolution-data-server 3.30.1-1build1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jan 19 09:59:18 2019 ExecutablePath: /usr/lib/evolution/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2017-01-09 (740 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evolution-data-server UpgradeStatus: Upgraded to cosmic on 2018-10-19 (92 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1812474/+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 1794280] Re: gdm doesn't start on a fresh installation of Cosmic Desktop
Hi, I have the same problem since 3 weeks on a fresh install of Ubuntu Cosmic, with Wayland session enabled by default : 2/3 of the time, login screen doesn't appear and screen remains black, pushing power button makes Ubuntu background visible again and computer stops. I join some Auth.log since 17th September, here is an extract - will do some further tests : Session c1 logged out. Waiting for processes to exit. Unregistered Authentication Agent for unix-session:c1 (system bus name :1.35, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8) (disconnected from bus) Removed session c1. session closed for user gdm session opened for user root by (uid=1000) Executing command [USER=root] [TTY=unknown] [CWD=/home/valeryan24] [COMMAND=/usr/lib/update-notifier/package-system-locked] Operator of unix-session:2 successfully authenticated as unix-user:valeryan24 to gain TEMPORARY authorization for action org.debian.apt.install-or-remove-packages for system-bus-name::1.336 [/usr/bin/python3 /usr/bin/update-manager --no-update --no-focus-on-map] (owned by unix-user:valeryan24) asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Registered Authentication Agent for unix-session:2 (system bus name :1.190 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8) New seat seat0. pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0) New session c1 of user gdm. session opened for user gdm by (uid=0) gdm-launch-environment]: pam_unix(gdm-launch-environment:session): session closed for user gdm Session c1 logged out. Waiting for processes to exit. Removed session c1. pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0) New session c2 of user gdm. pam_systemd(gdm-launch-environment:session): Failed to create session: Start job for unit user-121.slice failed with 'canceled' session closed for user gdm session opened for user gdm by (uid=0) pam_unix(gdm-launch-environment:session): session closed for user gdm Session c2 logged out. Waiting for processes to exit. Removed session c2. systemd: pam_unix(systemd-user:session): session closed for user gdm systemd-logind[815]: Power key pressed. systemd-logind[815]: Powering Off... systemd-logind[815]: System is powering down. ** Attachment added: "Auth.log" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794280/+attachment/5199069/+files/Auth.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1794280 Title: gdm doesn't start on a fresh installation of Cosmic Desktop Status in gdm3 package in Ubuntu: Won't Fix Status in kmod package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-video-fbdev package in Ubuntu: Fix Released Status in gdm3 source package in Cosmic: Won't Fix Status in kmod source package in Cosmic: Invalid Status in linux source package in Cosmic: Invalid Status in xorg-server source package in Cosmic: Confirmed Status in xserver-xorg-video-fbdev source package in Cosmic: Fix Released Bug description: ubuntu cosmic desktop 20180925 After installation gdm fails to start and there is only a black screen with a blinking cursor on the top left of the screen. gdm3 can be started manually from a tty When this issue happens there is a plymouth crash reported in bug 1794292 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 Date: Tue Sep 25 13:54:45 2018 InstallationDate: Installed on 2018-09-25 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794280/+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 1788868] [NEW] installed systemd-shim package post-removal script subprocess returned error exit status 2cess returned error exit status 2grade: installed systemd-shim package po
Public bug reported: erreur sur mise à jour partielle ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Aug 22 11:44:47 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2014-01-03 (1693 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic third-party-packages -- 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/1788868 Title: installed systemd-shim package post-removal script subprocess returned error exit status 2cess returned error exit status 2grade: installed systemd-shim package post-removal script subprocess returned error exit status 2 Status in systemd package in Ubuntu: New Bug description: erreur sur mise à jour partielle ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Aug 22 11:44:47 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2014-01-03 (1693 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1788868/+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 1583237] Re: lxc-attach strange tty behavior (kills command) when stderr is redirected to a file
Another demonstration: * This one does not work: sudo lxc-attach --name utest_generic_tests -- /bin/bash -c "/usr/bin/python -c 'from ctypes import *; memset(0,1,1)'"; echo $? 0 * This one works: sudo lxc-attach --name utest_generic_tests -- /bin/bash -c "/usr/bin/python -c 'from ctypes import *; memset(0,1,1)' 2>&2"; echo $? /bin/bash: line 1: 2286 Segmentation fault (core dumped) /usr/bin/python -c 'from ctypes import *; memset(0,1,1)' 2>&2 139 -- 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/1583237 Title: lxc-attach strange tty behavior (kills command) when stderr is redirected to a file Status in lxc package in Ubuntu: New Bug description: On a fresh Ubuntu 16 release, commands started by lxc-attach such as dd are being killed WHEN REDIRECTING stderr (to a file), and lxc- attach return a zero status. Command works fine without the redirection. This scenario is working on Ubuntu 15 with previous lxc release, but not on new LXC 2.0.0 (same issue on 2.0.1 too) sudo apt-get -y install lxc sudo lxc-create -n utest -t ubuntu -- -a amd64 -b $USER sudo lxc-start -d --name utest sudo lxc-attach -n utest -- dd if=/dev/zero of=/tmp/foo bs=1M count=10 2>/tmp/bar sudo lxc-attach -n utest -- ls -lh /tmp/foo -rw-r--r-- 1 root root 0 May 18 05:46 /tmp/foo Might be related to bug 1553097 (and/or https://github.com/lxc/lxc/pull/873) NOTE: Sometimes the "sudo lxc-attach -n utest_bizio_tests -- ls -lh /tmp/foo" ALSO does not return anything (no output) I'm available for any additional info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1583237/+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 1764743] Re: ssh asks for passphrase
Ok, I understood what's going on here! I had many ssh private keys and some of them have length <1024 but my main one is 2048. ssh-add doesn't add any key just because one of them is unsafe. I removed old keys and the problem is fixed. I guess this is an upstream bug and not Ubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1764743 Title: ssh asks for passphrase Status in openssh package in Ubuntu: New Bug description: Every time I open gnome-terminal to connect to a remote host using ssh, it's asking me the passphrase of my ssh key. It was working fine on both my laptops (Ubuntu 16.04 and 17.10) and stopped working on both after the upgrade to 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openssh-client 1:7.6p1-4 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 17 09:30:03 2018 InstallationDate: Installed on 2018-01-09 (97 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n 7 Dec 2017 SourcePackage: openssh UpgradeStatus: Upgraded to bionic on 2018-04-12 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1764743/+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 1764743] Re: ssh asks for passphrase
xclaesse@xclaesse-PC:~$ env | grep SSH SSH_AUTH_SOCK=/run/user/1000/keyring/ssh SSH_AGENT_PID=2183 xclaesse@xclaesse-PC:~$ ps aux | grep ssh root 1263 0.0 0.0 72296 5720 ?Ss 09:26 0:00 /usr/sbin/sshd -D xclaesse 2183 0.0 0.0 11304 320 ?Ss 09:26 0:00 /usr/bin/ssh-agent /usr/bin/im-launch env GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu xclaesse 3454 0.0 0.0 11304 1520 ?S09:27 0:00 /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh xclaesse 4924 0.0 0.0 15664 1048 pts/0S+ 09:37 0:00 grep --color=auto ssh xclaesse@xclaesse-PC:~$ ssh pasanda Enter passphrase for key '/home/xclaesse/.ssh/id_rsa': -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1764743 Title: ssh asks for passphrase Status in openssh package in Ubuntu: New Bug description: Every time I open gnome-terminal to connect to a remote host using ssh, it's asking me the passphrase of my ssh key. It was working fine on both my laptops (Ubuntu 16.04 and 17.10) and stopped working on both after the upgrade to 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openssh-client 1:7.6p1-4 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 17 09:30:03 2018 InstallationDate: Installed on 2018-01-09 (97 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n 7 Dec 2017 SourcePackage: openssh UpgradeStatus: Upgraded to bionic on 2018-04-12 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1764743/+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 1764743] [NEW] ssh asks for passphrase
Public bug reported: Every time I open gnome-terminal to connect to a remote host using ssh, it's asking me the passphrase of my ssh key. It was working fine on both my laptops (Ubuntu 16.04 and 17.10) and stopped working on both after the upgrade to 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openssh-client 1:7.6p1-4 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 17 09:30:03 2018 InstallationDate: Installed on 2018-01-09 (97 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n 7 Dec 2017 SourcePackage: openssh UpgradeStatus: Upgraded to bionic on 2018-04-12 (4 days ago) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1764743 Title: ssh asks for passphrase Status in openssh package in Ubuntu: New Bug description: Every time I open gnome-terminal to connect to a remote host using ssh, it's asking me the passphrase of my ssh key. It was working fine on both my laptops (Ubuntu 16.04 and 17.10) and stopped working on both after the upgrade to 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openssh-client 1:7.6p1-4 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 17 09:30:03 2018 InstallationDate: Installed on 2018-01-09 (97 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n 7 Dec 2017 SourcePackage: openssh UpgradeStatus: Upgraded to bionic on 2018-04-12 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1764743/+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 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys
I don't agree with the last comme,nt : I have a fresh install of 18.04 and get the same error when trying to recover my old savec Private directory : Enter your MOUNT passphrase: mount: /tmp/ecryptfs.fSC9TkTG : échec de l’appel système mount(2) : Aucun fichier ou dossier de ce type. ERROR: Failed to mount private data at [/tmp/ecryptfs.fSC9TkTG]. -- 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/1718658 Title: ecryptfs-mount-private fails to initialize ecryptfs keys Status in ecryptfs-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: ecryptfs-mount-private fails to mount the ecryptfs after the 1st reboot after creating the ecryptfs by ecryptfs-setup-private. After the unsucessful attempt dmesg contains: [ 1265.695388] Could not find key with description: [] [ 1265.695393] process_request_key_err: No key [ 1265.695394] Could not find valid key in user session keyring for sig specified in mount option: [] [ 1265.695395] One or more global auth toks could not properly register; rc = [-2] [ 1265.695396] Error parsing options; rc = [-2] Note: The correct key ID has been replaced in the "". I also accidentally found an workaround - just running ecrytpfs- manager and then the ecryptfs-mount-private (it does not ask for password for the second time and mounts the ecryptfs correctly): host:~$ ecryptfs-manager eCryptfs key management menu --- 1. Add passphrase key to keyring 2. Add public key to keyring 3. Generate new public/private keypair 4. Exit Make selection: 4 host:~$ ls Private/ Access-Your-Private-Data.desktop README.txt host:~$ ecryptfs-mount-private host:~$ ls Private/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+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 1516564] Re: Remove 'Ç' key from Portuguese (PT-PT) layout
** No longer affects: ubuntu-keyboard
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1516564
Title:
Remove 'Ç' key from Portuguese (PT-PT) layout
Status in ubuntu-keyboard package in Ubuntu:
New
Bug description:
Hi,
The current ubuntu keyboard layout for Portuguese from Portugal
displays the 'ç' key, which is unnecessary because with a long-press
in the 'c' key we can get 'ç'.
Triage: http://bazaar.launchpad.net/~phablet-team/ubuntu-
keyboard/trunk/view/head:/plugins/pt/qml/Keyboard_pt.qml
Row {
anchors.horizontalCenter: parent.horizontalCenter;
spacing: 0
CharKey { label: "a"; shifted: "A"; extended:
["ã","á","à","â","ª","ä","å","æ"]; extendedShifted:
["Ã","Á","À","Â","ª","Ä","Å","Æ"]; leftSide: true; }
CharKey { label: "s"; shifted: "S"; extended: ["ß","$"];
extendedShifted: ["$"] }
CharKey { label: "d"; shifted: "D"; extended: ["ð"];
extendedShifted: ["Ð"] }
CharKey { label: "f"; shifted: "F"; }
CharKey { label: "g"; shifted: "G"; }
CharKey { label: "h"; shifted: "H"; }
CharKey { label: "j"; shifted: "J"; }
CharKey { label: "k"; shifted: "K"; }
CharKey { label: "l"; shifted: "L"; }
CharKey { label: "ç"; shifted: "Ç"; rightSide: true; } <--'ç'
}
Row {
anchors.horizontalCenter: parent.horizontalCenter;
spacing: 0
ShiftKey {}
CharKey { label: "z"; shifted: "Z"; }
CharKey { label: "x"; shifted: "X"; }
CharKey { label: "c"; shifted: "C"; extended: ["ç"];
extendedShifted: ["Ç"] } <--'ç'
CharKey { label: "v"; shifted: "V"; }
CharKey { label: "b"; shifted: "B"; }
CharKey { label: "n"; shifted: "N"; extended: ["ñ"];
extendedShifted: ["Ñ"] }
CharKey { label: "m"; shifted: "M"; }
BackspaceKey {}
}
Even the android/ios doesn't have the 'ç' key, see the attachment.
It's a bit difficult to handle the current layout with the 'Ç' key.
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1516564/+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 1644530] Re: keepalived fails to restart cleanly due to the wrong systemd settings
Affects aswell 17.10 and 18.04.
--
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/1644530
Title:
keepalived fails to restart cleanly due to the wrong systemd settings
Status in keepalived package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Opinion
Status in keepalived source package in Xenial:
Fix Released
Status in systemd source package in Xenial:
Opinion
Status in keepalived package in Debian:
Fix Released
Bug description:
[Impact]
* Restarts of keepalived can leave stale processes with the old
configuration around.
* The systemd detection of the MainPID is suboptimal, and combined
with not waiting on signals being handled it can fail on second
restart killing the (still) remaining process of the first start.
* Upstream has a PIDFile statement, this has proven to avoid the
issue in the MainPID guessing code of systemd.
[Test Case]
* Set up keepalived, the more complex the config is the "bigger" is the
reace window, below in the description is a trivial sample config that works
well.
* As a test run the loop restarting the service head-to-head while staying
under the max-restart limit
$ for j in $(seq 1 20); do sleep 11s; time for i in $(seq 1 5); do sudo
systemctl restart keepalived; sudo systemctl status keepalived | egrep
'Main.*exited'; done; done
Expectation: no output other than timing
Without fix: sometimes MainPIDs do no more exist, in these cases the child
processes are the "old" ones from last execution with the old config.
[Regression Potential]
* Low because
* A PIDFile statement is recommended by systemd for type=forking services
anyway.
* Upstream keepalived has this statement in their service file
* By the kind of change, it should have no functional impact to other
parts of the service other than for the PID detection of the job by Systemd.
* Yet regression potential is never zero. There might be the unlikely
case, which were considered working before due to a new config not
properly being picked up. After the fix they will behave correctly and
might show up as false-positives then if e.g. config was bad.
[Other Info]
* Usually a fix has to be in at least the latest Development release before
SRUing it. But as I outlined below in later Releases than Xenial systemd seems
to have improved making this change not-required. We haven't identified the
bits for this (there is a bug task here), and they might as well be very
complex. I think it is correct to fix Xenial in this regard with the simple
change to the service file for now.
* To eventually match I created a Debian bug task to ask them for the
inclusion of the PIDFile so it can slowly tickle back down to newer
Ubuntu Releases - also there more often people run backports where the
issue might occur on older systemd versions (just as it does for us on
Xenial)
---
Because "PIDFile=" directive is missing in the systemd unit file,
keepalived sometimes fails to kill all old processes. The old
processes remain with old settings and cause unexpected behaviors. The
detail of this bug is described in this ticket in upstream:
https://github.com/acassen/keepalived/issues/443.
The official systemd unit file is available since version 1.2.24 by
this commit:
https://github.com/acassen/keepalived/commit/635ab69afb44cd8573663e62f292c6bb84b44f15
This includes "PIDFile" directive correctly:
PIDFile=/var/run/keepalived.pid
We should go the same way.
I am using Ubuntu 16.04.1, kernel 4.4.0-45-generic.
Package: keepalived
Version: 1.2.19-1
===
How to reproduce:
I used the two instances of Ubuntu 16.04.2 on DigitalOcean:
Configurations
--
MASTER server's /etc/keepalived/keepalived.conf:
vrrp_script chk_nothing {
script "/bin/true"
interval 2
}
vrrp_instance G1 {
interface eth1
state BACKUP
priority 100
virtual_router_id 123
unicast_src_ip
unicast_peer {
}
track_script {
chk_nothing
}
}
BACKUP server's /etc/keepalived/keepalived.conf:
vrrp_script chk_nothing {
script "/bin/true"
interval 2
}
vrrp_instance G1 {
interface eth1
state MASTER
priority 200
virtual_router_id 123
unicast_src_ip
unicast_peer {
}
track_script {
chk_nothing
}
}
Loop based probing for the Error to exist:
--
After the setup above start keepalived on both servers:
$ sudo systemctl start keepalived.service
Then run the following loop
$ for j in $(seq 1 20); do sleep 11s; time for i in $(seq 1 5); do sudo
systemctl restart
[Touch-packages] [Bug 1728067] [NEW] CUPS : wrong imageable area A4 for Canon MG4200
Public bug reported: Prints are shifted to the bottom, end of the page is never printed. I have a look on the ppd file of my printer and the imageablearea for size A4 seems wrong. It's should be ImageableArea A4/A4: "18 36 577 806" but it's ImageableArea A4: "18 106 577 819" I tried to edit and change it, but on each reload of cups the wrong version come in place. ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1728067 Title: CUPS : wrong imageable area A4 for Canon MG4200 Status in cups package in Ubuntu: New Bug description: Prints are shifted to the bottom, end of the page is never printed. I have a look on the ppd file of my printer and the imageablearea for size A4 seems wrong. It's should be ImageableArea A4/A4: "18 36 577 806" but it's ImageableArea A4: "18 106 577 819" I tried to edit and change it, but on each reload of cups the wrong version come in place. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1728067/+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 1725644] [NEW] package linux-firmware 1.169 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Error appears during upgrade from 17.04 to 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-firmware 1.169 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sat Oct 21 10:33:30 2017 Dependencies: ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: initramfs-tools Title: package linux-firmware 1.169 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- 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/1725644 Title: package linux-firmware 1.169 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Error appears during upgrade from 17.04 to 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-firmware 1.169 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sat Oct 21 10:33:30 2017 Dependencies: ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: initramfs-tools Title: package linux-firmware 1.169 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1725644/+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 1725643] [NEW] package linux-image-4.13.0-16-generic 4.13.0-16.19 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: Fail occurs during upgrade from 17.04 to 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sat Oct 21 10:21:00 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=2840141a-e97a-45b4-ba77-708bf58324fa MachineType: Dell Inc. XPS 8500 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=UUID=271ba9b9-ca1b-4af8-9c5d-6f039ad2a1d6 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7 SourcePackage: initramfs-tools Title: package linux-image-4.13.0-16-generic 4.13.0-16.19 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0YJPT1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd08/28/2013:svnDellInc.:pnXPS8500:pvr:rvnDellInc.:rn0YJPT1:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8500 dmi.sys.vendor: Dell Inc. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- 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/1725643 Title: package linux-image-4.13.0-16-generic 4.13.0-16.19 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Fail occurs during upgrade from 17.04 to 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sat Oct 21 10:21:00 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=2840141a-e97a-45b4-ba77-708bf58324fa MachineType: Dell Inc. XPS 8500 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=UUID=271ba9b9-ca1b-4af8-9c5d-6f039ad2a1d6 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7 SourcePackage: initramfs-tools Title: package linux-image-4.13.0-16-generic 4.13.0-16.19 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0YJPT1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd08/28/2013:svnDellInc.:pnXPS8500:pvr:rvnDellInc.:rn0YJPT1:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8500 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1725643/+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 1725638] [NEW] package linux-image-generic 4.13.0.16.17 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: Error appears during system upgrade from 17.04 to 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-generic 4.13.0.16.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sat Oct 21 10:33:03 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=2840141a-e97a-45b4-ba77-708bf58324fa MachineType: Dell Inc. XPS 8500 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=UUID=271ba9b9-ca1b-4af8-9c5d-6f039ad2a1d6 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7 SourcePackage: initramfs-tools Title: package linux-image-generic 4.13.0.16.17 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0YJPT1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd08/28/2013:svnDellInc.:pnXPS8500:pvr:rvnDellInc.:rn0YJPT1:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8500 dmi.sys.vendor: Dell Inc. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- 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/1725638 Title: package linux-image-generic 4.13.0.16.17 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Error appears during system upgrade from 17.04 to 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-generic 4.13.0.16.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sat Oct 21 10:33:03 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=2840141a-e97a-45b4-ba77-708bf58324fa MachineType: Dell Inc. XPS 8500 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=UUID=271ba9b9-ca1b-4af8-9c5d-6f039ad2a1d6 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7 SourcePackage: initramfs-tools Title: package linux-image-generic 4.13.0.16.17 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0YJPT1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd08/28/2013:svnDellInc.:pnXPS8500:pvr:rvnDellInc.:rn0YJPT1:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8500 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1725638/+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 1723577] Re: Artful won't start with Wayland activated (AMD?)
Yes, I donwgraded in chroot Gnome Shell to this version : https://launchpad.net/ubuntu/+source/gnome-shell/3.26.0-0ubuntu2/+build/13517504 After it boots normally and I get the login screen, then the Ubuntu Gnome Shell session, all works. Developers are testing commits: I tried the 2 here (reverse of Shell headless mode) https://launchpad.net/~didrocks/+archive/ubuntu/ppa/+build/13591531 And it still goes until the end of the boot without freezing anymore valeryan24@valeryan24-desktop:~/Bureau/GShell$ sudo dpkg -i gnome-shell_3.26.1-0ubuntu4~revertheadless1_amd64.deb gnome-shell-common_3.26.1-0ubuntu4~revertheadless1_all.deb [sudo] Mot de passe de valeryan24 : (Lecture de la base de données... 343326 fichiers et répertoires déjà installés.) Préparation du dépaquetage de gnome-shell_3.26.1-0ubuntu4~revertheadless1_amd64.deb ... Dépaquetage de gnome-shell (3.26.1-0ubuntu4~revertheadless1) sur (3.26.0-0ubuntu2) ... Préparation du dépaquetage de gnome-shell-common_3.26.1-0ubuntu4~revertheadless1_all.deb ... Dépaquetage de gnome-shell-common (3.26.1-0ubuntu4~revertheadless1) sur (3.26.0-0ubuntu2) ... Paramétrage de gnome-shell-common (3.26.1-0ubuntu4~revertheadless1) ... Traitement des actions différées (« triggers ») pour gconf2 (3.2.6-4ubuntu1) ... Traitement des actions différées (« triggers ») pour libglib2.0-0:amd64 (2.54.1-1ubuntu1) ... Paramétrage de gnome-shell (3.26.1-0ubuntu4~revertheadless1) ... Traitement des actions différées (« triggers ») pour libc-bin (2.26-0ubuntu2) ... Traitement des actions différées (« triggers ») pour gnome-menus (3.13.3-6ubuntu5) ... Traitement des actions différées (« triggers ») pour desktop-file-utils (0.23-1ubuntu3) ... Traitement des actions différées (« triggers ») pour mime-support (3.60ubuntu1) ... Traitement des actions différées (« triggers ») pour man-db (2.7.6.1-2) ... apt policy gnome-shell gnome-shell-common valeryan24@valeryan24-desktop:~$ apt policy gnome-shell gnome-shell-common gnome-shell: Installé : 3.26.1-0ubuntu4~revertheadless1 Candidat : 3.26.1-0ubuntu4~revertheadless1 Table de version : *** 3.26.1-0ubuntu4~revertheadless1 100 100 /var/lib/dpkg/status 3.26.1-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3.25.91-0ubuntu5~ppa1 500 500 http://ppa.launchpad.net/ubuntu-desktop/transitions/ubuntu artful/main amd64 Packages gnome-shell-common: Installé : 3.26.1-0ubuntu4~revertheadless1 Candidat : 3.26.1-0ubuntu4~revertheadless1 Table de version : *** 3.26.1-0ubuntu4~revertheadless1 100 100 /var/lib/dpkg/status 3.26.1-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu artful/main i386 Packages 3.25.91-0ubuntu5~ppa1 500 500 http://ppa.launchpad.net/ubuntu-desktop/transitions/ubuntu artful/main amd64 Packages 500 http://ppa.launchpad.net/ubuntu-desktop/transitions/ubuntu artful/main i386 Packages valeryan24@valeryan24-desktop:~$ sudo modetest sudo: modetest : commande introuvable -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1723577 Title: Artful won't start with Wayland activated (AMD?) Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Incomplete Bug description: On a fresch install, ubuntu stop and freeze before gdm is opened With no splah i have "started user manager for uid 121" and then it freeze need to uncomment WaylandEnable=false in custom.conf to start ubuntu so with xorg. lspci -nn | grep VGA return 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 14 07:36:30 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 'simple-scan.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Touch-packages] [Bug 1723577] Re: Artful won't start with Wayland activated (AMD?)
Tried to downgrade Gnome Shell : sudo dpkg -i gnome-shell_3.26.0-0ubuntu2_amd64.deb gnome-shell- common_3.26.0-0ubuntu2_all.deb root@ubuntu:/home/GShell# sudo dpkg -i gnome-shell_3.26.0-0ubuntu2_amd64.deb gnome-shell-common_3.26.0-0ubuntu2_all.deb dpkg: avertissement: dégradation (« downgrade ») de gnome-shell depuis 3.26.1-0ubuntu3 vers 3.26.0-0ubuntu2 (Lecture de la base de données... 343326 fichiers et répertoires déjà installés.) Préparation du dépaquetage de gnome-shell_3.26.0-0ubuntu2_amd64.deb ... Dépaquetage de gnome-shell (3.26.0-0ubuntu2) sur (3.26.1-0ubuntu3) ... dpkg: avertissement: dégradation (« downgrade ») de gnome-shell-common depuis 3.26.1-0ubuntu3 vers 3.26.0-0ubuntu2 Préparation du dépaquetage de gnome-shell-common_3.26.0-0ubuntu2_all.deb ... Dépaquetage de gnome-shell-common (3.26.0-0ubuntu2) sur (3.26.1-0ubuntu3) ... Paramétrage de gnome-shell-common (3.26.0-0ubuntu2) ... Traitement des actions différées (« triggers ») pour gconf2 (3.2.6-4ubuntu1) ... Traitement des actions différées (« triggers ») pour libglib2.0-0:amd64 (2.54.1-1ubuntu1) ... Paramétrage de gnome-shell (3.26.0-0ubuntu2) ... Traitement des actions différées (« triggers ») pour libc-bin (2.26-0ubuntu2) ... Traitement des actions différées (« triggers ») pour gnome-menus (3.13.3-6ubuntu5) ... Traitement des actions différées (« triggers ») pour desktop-file-utils (0.23-1ubuntu3) ... Traitement des actions différées (« triggers ») pour mime-support (3.60ubuntu1) ... Traitement des actions différées (« triggers ») pour man-db (2.7.6.1-2) ... It works, I can login on the GS Ubuntu session ! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1723577 Title: Artful won't start with Wayland activated (AMD?) Status in gdm3 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Incomplete Bug description: On a fresch install, ubuntu stop and freeze before gdm is opened With no splah i have "started user manager for uid 121" and then it freeze need to uncomment WaylandEnable=false in custom.conf to start ubuntu so with xorg. lspci -nn | grep VGA return 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 14 07:36:30 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 'simple-scan.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+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 1723577] Re: Artful won't start with Wayland activated (AMD?)
My home is encrypted (ecryptFS) so gdm can't access to ~/.config/monitors.xml There is not another one : root@ubuntu:/# sudo updatedb root@ubuntu:/# locate monitors.xml root@ubuntu:/# I added to /etc/environment : export MUTTER_VERBOSE=1 export MUTTER_VERBOSE=1 export MUTTER_DEBUG=1 export MUTTER_USE_LOGFILE=/tmp/mutterlogs export MUTTER_DEBUG_SM=1 export MUTTER_DEBUG_BUTTON_GRABS=1 export WAYLAND_DEBUG=1 Here is the Mutter log. ** Attachment added: "Mutter log" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+attachment/4974765/+files/mutter-1305-debug-log-ZBXK8Y -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1723577 Title: Artful won't start with Wayland activated (AMD?) Status in gdm3 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Incomplete Bug description: On a fresch install, ubuntu stop and freeze before gdm is opened With no splah i have "started user manager for uid 121" and then it freeze need to uncomment WaylandEnable=false in custom.conf to start ubuntu so with xorg. lspci -nn | grep VGA return 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 14 07:36:30 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 'simple-scan.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+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 1723577] Re: Artful won't start with Wayland activated (AMD?)
And the last syslog... ** Attachment added: "Syslog4" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+attachment/4974766/+files/Syslog4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1723577 Title: Artful won't start with Wayland activated (AMD?) Status in gdm3 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Incomplete Bug description: On a fresch install, ubuntu stop and freeze before gdm is opened With no splah i have "started user manager for uid 121" and then it freeze need to uncomment WaylandEnable=false in custom.conf to start ubuntu so with xorg. lspci -nn | grep VGA return 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 14 07:36:30 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 'simple-scan.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+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 1723577] Re: Artful won't start with Wayland activated (AMD?)
In /etc/gdm3/custom.conf, on [debug] section, I activated Enable=true, here is the complete startup log. But following command didn't work in chroot (to get more infos from gdm) : root@ubuntu:/# sudo journalctl -b -u gdm No journal files were found. -- No entries -- ** Attachment added: "Syslog3" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+attachment/4973896/+files/Syslog3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1723577 Title: Artful won't start with Wayland activated (AMD?) Status in gdm3 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Incomplete Bug description: On a fresch install, ubuntu stop and freeze before gdm is opened With no splah i have "started user manager for uid 121" and then it freeze need to uncomment WaylandEnable=false in custom.conf to start ubuntu so with xorg. lspci -nn | grep VGA return 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 14 07:36:30 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 'simple-scan.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+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 1723577] Re: Artful won't start with Wayland activated (AMD?)
** Attachment added: "Syslog2" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+attachment/4973287/+files/Syslog2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1723577 Title: Artful won't start with Wayland activated (AMD?) Status in gdm3 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Incomplete Bug description: On a fresch install, ubuntu stop and freeze before gdm is opened With no splah i have "started user manager for uid 121" and then it freeze need to uncomment WaylandEnable=false in custom.conf to start ubuntu so with xorg. lspci -nn | grep VGA return 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 14 07:36:30 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 'simple-scan.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+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 1723577] Re: Artful won't start with Wayland activated (AMD?)
After having also downgraded libdrm (of course I did not reapply updates on my main system after other reverts), it still doesn't start and stays at Ubuntu screen (UID 121)... Logs attached to help. ** Attachment added: "Libdrm" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+attachment/4973286/+files/Libdrm-1710 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1723577 Title: Artful won't start with Wayland activated (AMD?) Status in gdm3 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Incomplete Bug description: On a fresch install, ubuntu stop and freeze before gdm is opened With no splah i have "started user manager for uid 121" and then it freeze need to uncomment WaylandEnable=false in custom.conf to start ubuntu so with xorg. lspci -nn | grep VGA return 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 14 07:36:30 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 'simple-scan.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+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 1723577] Re: Artful won't start with Wayland activated (AMD?)
Daniel, sorry, I did not complete my post after #18 and apt policy result - we were discussing with didrocks and frenchy82 on the French forum with the details, I tried to resume here all steps in order other people and developers involved in bug also got the informations. http://forum.ubuntu-fr.org/viewtopic.php?pid=21810017#p21810017 So I did (always in chroot mode) : sudo dpkg -i libegl1-mesa_17.2.1-0ubuntu1_amd64.deb libgbm1_17.2.1-0ubuntu1_amd64.deb libgl1-mesa-dri_17.2.1-0ubuntu1_amd64.deb libgl1-mesa-glx_17.2.1-0ubuntu1_amd64.deb libglapi-mesa_17.2.1-0ubuntu1_amd64.deb libgles2-mesa_17.2.1-0ubuntu1_amd64.deb libwayland-egl1-mesa_17.2.1-0ubuntu1_amd64.deb libxatracker2_17.2.1-0ubuntu1_amd64.deb mesa-va-drivers_17.2.1-0ubuntu1_amd64.deb mesa-vdpau-drivers_17.2.1-0ubuntu1_amd64.deb It downgraded the 10 packages installed in 17.2.1 version. But when I rebooted normally, it was still frozen at Ubuntu screen and message 'Started User Manager for UID 121' My graphic card : Gallium 0.4 on AMD CAPE VERDE (DRM 2.49.0 / 4.10.0-19-generic, LLVM 4.0.0) After dpwngrading mesa, I tried downgrading mutter, xserver-xorg-video- ati, xorg-server, then booting on the grub to older kernels : nothing worked, I still have the bug on startup. You're right, I don't know if I missed something on the instructions to come back on previous versions with the risk to eliminate the good direction to search, or if bug comes from something else... I was afraid of that, but frenchy82 test seems to confirm downgrading mesa is not enough to solve the problem. I can continue to do some testings if you need. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1723577 Title: Artful won't start with Wayland activated (AMD?) Status in gdm3 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Incomplete Bug description: On a fresch install, ubuntu stop and freeze before gdm is opened With no splah i have "started user manager for uid 121" and then it freeze need to uncomment WaylandEnable=false in custom.conf to start ubuntu so with xorg. lspci -nn | grep VGA return 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 14 07:36:30 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 'simple-scan.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+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 1704419] [NEW] mouse dramaticaly slow after upgrade to 17.04
Public bug reported: After upgrade from ubuntu 16.10 to ubuntu 17.04, the wireless mouse pointer of my desktop is dramatically slow. On the system parameter/mouse, the speed pointer cursor doesn't work (while it used to work in 16.10). I can speed it updating xinpout Transformation Matrix (Coordinate Transformation Matrix (155): 2.50, 0.00, 0.00, 0.00, 2.50, 0.00, 0.00, 0.00, 1.00). The mouse pointer speed is then ok. But, with this Transformation Matrix, when I drag and drop (for instance to move a tab in Firefox, a mail in Thunderbird, a selected word in LO Writer) the cursor jumps to the right edge of the screen. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.66 Mon May 1 15:29:16 PDT 2017 GCC version: gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7 Date: Fri Jul 14 16:55:17 2017 DistUpgraded: 2017-05-14 17:24:55,510 DEBUG icon theme changed, re-reading DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK104 [GeForce GTX 760] [1462:2848] InstallationDate: Installed on 2013-12-10 (1312 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Lsusb: Bus 002 Device 003: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic.efi.signed root=UUID=46f205b7-40a4-461c-a221-3d06c9c1749f ro quiet splash nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to zesty on 2017-05-14 (60 days ago) dmi.bios.date: 07/01/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1207 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1207:bd07/01/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-A:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1 xserver.bootTime: Fri Jul 14 16:03:02 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu zesty ** Attachment added: "xinput list-props.txt" https://bugs.launchpad.net/bugs/1704419/+attachment/4914678/+files/xinput%20list-props.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is
[Touch-packages] [Bug 1698604] [NEW] login will show unmasked password if user types too fast on a slow system
Public bug reported: At the login, from the terminal, the user must login using his username and password. The program first displays " login:", then the user enters his username. Once the user has pressed "enter", he must enter his password. The user may type too quickly before "Password:" appears and thus what he types before "Password:" was displayed will appear on the screen. This occurs when the computer is slow when verifying the login username. Users that are used to fast computer will start typing right their password right after pressing "enter" and the characters will appear on the screen. The result would be something like this: Ubuntu 16.04.2 LTS computername tty2 computername login: myusername mypPassword: People who may look at my screen will see that my password starts with "myp". The other characters typed after that "Password:" was displayed are invisible. The solution would be to make every characters that are typed after the user has entered his password invisible. It could also be a good idea to give the user a sound cue (a PC speaker beep) when he enters a character in the case where he starts typing his password too fast. ** Affects: shadow (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1698604 Title: login will show unmasked password if user types too fast on a slow system Status in shadow package in Ubuntu: New Bug description: At the login, from the terminal, the user must login using his username and password. The program first displays " login:", then the user enters his username. Once the user has pressed "enter", he must enter his password. The user may type too quickly before "Password:" appears and thus what he types before "Password:" was displayed will appear on the screen. This occurs when the computer is slow when verifying the login username. Users that are used to fast computer will start typing right their password right after pressing "enter" and the characters will appear on the screen. The result would be something like this: Ubuntu 16.04.2 LTS computername tty2 computername login: myusername mypPassword: People who may look at my screen will see that my password starts with "myp". The other characters typed after that "Password:" was displayed are invisible. The solution would be to make every characters that are typed after the user has entered his password invisible. It could also be a good idea to give the user a sound cue (a PC speaker beep) when he enters a character in the case where he starts typing his password too fast. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1698604/+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 1693779] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 Public bug reported: Crash ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Fri May 26 09:32:54 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-11 (14 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1693779 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: New Bug description: Crash ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Fri May 26 09:32:54 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-11 (14 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1693779/+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 1442670] Re: Ubuntu Phone BQ: Camera makes blur images
Yesterday I went to the beach and took photos with my e4.5. See the difference between the capture and a screenshot before the photo capture and the output. The photo on the left is way more accurate. Channel: Stable OS: OTA14 Device: Krillin ** Attachment added: "Captura de ecrã 2016-12-09, às 12.56.30.png" https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1442670/+attachment/4789482/+files/Captura%20de%20ecr%C3%A3%202016-12-09%2C%20%C3%A0s%2012.56.30.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1442670 Title: Ubuntu Phone BQ: Camera makes blur images Status in Canonical System Image: Confirmed Status in camera-app package in Ubuntu: Confirmed Bug description: Hi! A lot of times the camera is getting a really bad images (blur effect) in all resolutions. And yes, I click previously for a focus. I'm sending you an example: That picture looked perfect in the mobile, but in the PC is really bad :( Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1442670/+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 1506753] Re: keyboard does pop up not after update to r26
Hi everyone, I'm having a similar issue on my E4.5 with the latest rc-proposed builds, now I'm at r485. I can reproduce this behavior every time: 1) Open Browser 2) Switch to private tab 3) tap search bar 4) Keyboard won't popup. So, to fix it I do this: 1) Open message app 2) Create a new message OR tap a existent chat 3) Tap text field 4) Keyboard popup 5) Switch back to browser 6) Keyboard pop ups and fully working I don't know if my report match to the same bug reported here. If not, sorry :) Big hug -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1506753 Title: keyboard does pop up not after update to r26 Status in Canonical System Image: Incomplete Status in ubuntu-keyboard package in Ubuntu: Incomplete Bug description: Ubuntu bq 4.5. Checked with browser, dekko, calendar and system settings (changing the pin). Turned the phone off and on. No change. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1506753/+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 1607291] Re: Dual SIM devices show "No SIM" icon in indicators if there is only one SIM installed
And the bar indicator is getting very populated. For the network indicator we now have 3 icons, the wifi indicator can convergence between wifi connection and mobile data. The first time I saw it was confusing, because I was thinking that my only SIM card was having problems. We are repeating information...the user see the icon, then swipe down, and then see the same info. If the purpose is to warning the user, why not set this as a notification? Then people could enable or disable it in notifications panel. I think it would be a more elegant way of doing this. 1) turn on the phone; 2) insert SIM PIN; 3) A notification bobble appears saying NO SIM2 is detected; 4) User dismiss the notification. 5) If is annoying doing this on every reboot, disable system-settings notifications in notifications panel. With this you match carriers requirements, and still provide a elegant way for that. As the way it is, the user is being 'almost forced' to add a second SIM card. Hope you're mind change on this -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1607291 Title: Dual SIM devices show "No SIM" icon in indicators if there is only one SIM installed Status in Ubuntu UX: New Status in indicator-network package in Ubuntu: Invalid Bug description: rc-proposed, since about a week I have 2 SIM icons in the indicators panel. One that shows the signal strength for the installed SIM card (which is fine), and then a second one which shows the "no SIM card" icon. When there is a SIM card installed, the indicator should not show a "no SIM installed" icon, even though there would be a second free slot available. See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1607291/+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 1508905] Re: Graphics disorder, a large "claw" ('>') appearing
For the ones who have this issue, and if a reboot is not convenient, you
can unpin the scope, then pin it again and the issue is gone.
@victor-gonzalez-0 I will try this later. Hope next gen Scopes does not
suffer from this :).
Big hug to everyone!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1508905
Title:
Graphics disorder, a large "claw" ('>') appearing
Status in Canonical System Image:
Confirmed
Status in Today Scope:
Invalid
Status in unity8 package in Ubuntu:
Confirmed
Bug description:
Hi,
Currently I have this bug. It was already present in the OTA-6.
Usually a reboot fix the problem, but after a while it come back
again.
It only appears ate the bottom of the scope! If I swipe back to the
top the "claw" fade out.
I've attached a screenshot.
Thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1508905/+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 1508905] Re: Graphics disorder, a large "claw" ('>') appearing
Good morning everybody,
Today this claw/arrow appeared again. There isn't a way to reproduce it
exactly the same way everytime, but the behavior is almost the same, at
least with me. Scrooling up and down, enable and disable "show results
from (...)" click on cards, get back, scooling up and down, enable and
disable "show results from (...)" , doing this consistently and the
claw/arrow appears. Today Scope is the only one affected by this, I've
tried to do the same on NearBy Scope, but nothing happens.
The upcoming refresh of scopes also suffers from this bug?
** Attachment added: "screenshot2"
https://bugs.launchpad.net/today-scope/+bug/1508905/+attachment/4739983/+files/Sem%20t%C3%ADtulo.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1508905
Title:
Graphics disorder, a large "claw" ('>') appearing
Status in Today Scope:
Invalid
Status in unity8 package in Ubuntu:
Confirmed
Bug description:
Hi,
Currently I have this bug. It was already present in the OTA-6.
Usually a reboot fix the problem, but after a while it come back
again.
It only appears ate the bottom of the scope! If I swipe back to the
top the "claw" fade out.
I've attached a screenshot.
Thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1508905/+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 1508905] Re: Graphics disorder, a "claw" appearing
Hi @saviq, Sadly the claw is back again. Today, I've enable the twitter feed in the Today Scope, schooled up and down a few times and this graphic disorder return again, see screenshot. One thing I notice, is that this graph is bigger then previous ones. Device name: Krillin OS: OTA12 ** Attachment added: "Screenshot" https://bugs.launchpad.net/today-scope/+bug/1508905/+attachment/4739389/+files/photo_2016-09-12_17-35-34.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1508905 Title: Graphics disorder, a "claw" appearing Status in Today Scope: Invalid Status in unity8 package in Ubuntu: Expired Bug description: Hi, Currently I have this bug. It was already present in the OTA-6. Usually a reboot fix the problem, but after a while it come back again. It only appears ate the bottom of the scope! If I swipe back to the top the "claw" fade out. I've attached a screenshot. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1508905/+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 1618364] [NEW] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemas com dependências - a deixar triggers por processar
Public bug reported: After upgrade from xenial to yakkety ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Aug 30 09:34:31 2016 ErrorMessage: problemas com dependências - a deixar triggers por processar InstallationDate: Installed on 2016-02-15 (196 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3~rc2ubuntu3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemas com dependências - a deixar triggers por processar UpgradeStatus: Upgraded to yakkety on 2016-08-30 (0 days ago) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1618364 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemas com dependências - a deixar triggers por processar Status in gconf package in Ubuntu: New Bug description: After upgrade from xenial to yakkety ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Aug 30 09:34:31 2016 ErrorMessage: problemas com dependências - a deixar triggers por processar InstallationDate: Installed on 2016-02-15 (196 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3~rc2ubuntu3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemas com dependências - a deixar triggers por processar UpgradeStatus: Upgraded to yakkety on 2016-08-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1618364/+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 1616492] Re: [Design]Bottom Tab Manager Makes WebView of Footer Pages Difficult
** Attachment added: "Screenshot 1" https://bugs.launchpad.net/ubuntu-rtm/+source/webbrowser-app/+bug/1616492/+attachment/4727057/+files/browser3.jpg ** Package changed: webbrowser-app (Ubuntu RTM) => webbrowser-app (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1616492 Title: [Design]Bottom Tab Manager Makes WebView of Footer Pages Difficult Status in webbrowser-app package in Ubuntu: New Bug description: The Bottom Tab Manager makes difficult to see the footer of webpages difficult. I've reproduced it in private mode and "normal mode" See attachments. I've tried to find the bug here in Launchpad, but I couldn't (sorry, if it is already reported). System version: OTA12 Device name: Krillin Channel: ubuntu/stable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1616492/+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 1530947] Re: Ubuntu One account was deleted
Hi, if it is well the bug opened after discussion of #1507668 I have exactly the same problem : https://bugs.launchpad.net/ubuntu-system-settings-online- accounts/+bug/1606230 Click on "Install" for "Spider" game deletes Ubuntu One account -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntuone-credentials in Ubuntu. https://bugs.launchpad.net/bugs/1530947 Title: Ubuntu One account was deleted Status in ubuntuone-credentials package in Ubuntu: Confirmed Bug description: I came into the office, checked for updates, hit the bug where it spins forever (meaning the 3G network was there but not accessible), turned on wifi, checked again and it showed me two app updates with the message to sign in to ubuntu one MX4 on rc-proposed r209 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntuone-credentials/+bug/1530947/+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 1569718] Re: Ubuntu Touch (BQ Aquaris 4.5) - Does not boot after "[Volume Up] + [Power]" factory reset
@PatMcGowan Thanks a lot for the answer and solution, it worked perfectly, I was just able to reinstall Ubuntu on the E4.5, then restart, restore contacts + messages, all seems to work. Now, no more exotic manipulation with non-native programs ! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1569718 Title: Ubuntu Touch (BQ Aquaris 4.5) - Does not boot after "[Volume Up] + [Power]" factory reset Status in Canonical System Image: Incomplete Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity-system-compositor package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Today, I tried to factory reset my BQ Aquaris 4.5 Ubuntu Touch Edition with the [Volume Up] + [Power] method but since then, the phone won't boot. It only displays the BQ logo and then a black screen (it is still on but it's displaying nothing). I tried to connect the phone with adb but it doesn't seem to be recognized by the computer. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1569718/+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 1569718] Re: Ubuntu Touch (BQ Aquaris 4.5) - Does not boot after "[Volume Up] + [Power]" factory reset
I still have access to "Recovery menu" if I start with "Power + Volume Up", I can re-do Wipe cache partition, datas and factory reset, but again phone doesn't boot well : fastboot does nothing, normal boot stays on a black screen ever... Is there a way to reinstall Ubuntu Touch via terminal or something else, or do I have to send my phone to BQ ? Thanks ! ** Attachment added: "BQ-UT.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1569718/+attachment/4703527/+files/BQ-UT.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1569718 Title: Ubuntu Touch (BQ Aquaris 4.5) - Does not boot after "[Volume Up] + [Power]" factory reset Status in Canonical System Image: Incomplete Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity-system-compositor package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Today, I tried to factory reset my BQ Aquaris 4.5 Ubuntu Touch Edition with the [Volume Up] + [Power] method but since then, the phone won't boot. It only displays the BQ logo and then a black screen (it is still on but it's displaying nothing). I tried to connect the phone with adb but it doesn't seem to be recognized by the computer. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1569718/+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 1569718] Re: Ubuntu Touch (BQ Aquaris 4.5) - Does not boot after "[Volume Up] + [Power]" factory reset
Hi Julia, Thanks for the answer. I didn't know for the update break, I'll be careful on the future and wait that some programs get a native Ubuntu Touch program - or forget them. For the factory reset, I didn't do it via reboot "Power + Volume Up", but in the menu you have an icon for Parameters, and below the "Updates" row there is a command for doing a factory reset, one just for the launcher, the other for a complete reset. That's what I choose, confirmed the message for all datas that will be lost, the phone restarted, reset process began but E4.5 never started completely on Ubuntu, and since I get only a dark screen -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1569718 Title: Ubuntu Touch (BQ Aquaris 4.5) - Does not boot after "[Volume Up] + [Power]" factory reset Status in Canonical System Image: Incomplete Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity-system-compositor package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Today, I tried to factory reset my BQ Aquaris 4.5 Ubuntu Touch Edition with the [Volume Up] + [Power] method but since then, the phone won't boot. It only displays the BQ logo and then a black screen (it is still on but it's displaying nothing). I tried to connect the phone with adb but it doesn't seem to be recognized by the computer. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1569718/+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 1569718] Re: Ubuntu Touch (BQ Aquaris 4.5) - Does not boot after "[Volume Up] + [Power]" factory reset
Hi, did you get an answer from BQ support ? I have the same issue. Some weeks ago, I tried to install Prey on Ubuntu Touch BQ Aquaris E4.5 with this method : http://wayneward.co.uk/ubuntu-touch/prey-on-ubuntu-touch/ It failed, but after that, even if I can't affirm it's correlated, updates apps were working but not OS : I got the notifications of OTA 33 available, if I ran the update, phone reboot, began installation, then continued the process, started... and I was still on the current version, unable to update to the last system. So I decided to save my contacts + SMS / Calls, and did a factory reset, directly from the GUI Parameters menu. Phone restarted, stayed long minutes / hours on black screen without anything written. Sometimes I make a long press on "Start" button, I well see the BQ logo on the white screen, like Antoine Denis described, but just after the complete empty black screen comes again, and nothing else... I'm in big trouble now, as I used it with 2 lines, a professional one included. Any help on this, something to do to get logs ? Thanks in advance ! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1569718 Title: Ubuntu Touch (BQ Aquaris 4.5) - Does not boot after "[Volume Up] + [Power]" factory reset Status in Canonical System Image: Incomplete Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity-system-compositor package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Today, I tried to factory reset my BQ Aquaris 4.5 Ubuntu Touch Edition with the [Volume Up] + [Power] method but since then, the phone won't boot. It only displays the BQ logo and then a black screen (it is still on but it's displaying nothing). I tried to connect the phone with adb but it doesn't seem to be recognized by the computer. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1569718/+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 1574020] Re: Can't use networkmanager from lightdm
A notification comes up the greeter advertising that wireless networks are available. The greeter should at least not invite you to connect if you can't... -- 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/1574020 Title: Can't use networkmanager from lightdm Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Bug description: After upgrading to 16.04 desktop (unity) (clean install) from 14.04, (so not really upgrading, but you get the point) I noticed that lightdm with unity-greeter (all stock, nothing changed) can't connect to WiFi with network-manager. WiFi works after loggin it, but it should be working before also, if not, what's the point in having an icon there :) I get the following message: Failed to add/activate connection. - (1) Insufficient privileges. - see image. This worked fine in 14.04. I have noticed this problem in both my desktop (Broadcom WiFi) and Laptop (Intel WiFi) - So it has nothing to be with the chip. Feel free to ask for more info. Edit: From syslog: Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed Apr 23 16:50:46 desktop NetworkManager[979]: [1461423046.1662] audit: op="connection-add-activate" pid=1275 uid=108 result="fail" reason="Insufficient privileges." Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1574020/+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 1574020] Re: Can't use networkmanager from lightdm
I have two configured wifi connections. For each I went to the config files and they both had the "permissions=user:username:;" I removed "user:username:;" to restore "permissions=" Login out, I still had the insufficient privilege problem. But restarting solved the problem!!! Thank you modolo! -- 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/1574020 Title: Can't use networkmanager from lightdm Status in network-manager package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Bug description: After upgrading to 16.04 desktop (unity) (clean install) from 14.04, (so not really upgrading, but you get the point) I noticed that lightdm with unity-greeter (all stock, nothing changed) can't connect to WiFi with network-manager. WiFi works after loggin it, but it should be working before also, if not, what's the point in having an icon there :) I get the following message: Failed to add/activate connection. - (1) Insufficient privileges. - see image. This worked fine in 14.04. I have noticed this problem in both my desktop (Broadcom WiFi) and Laptop (Intel WiFi) - So it has nothing to be with the chip. Feel free to ask for more info. Edit: From syslog: Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed Apr 23 16:50:46 desktop NetworkManager[979]: [1461423046.1662] audit: op="connection-add-activate" pid=1275 uid=108 result="fail" reason="Insufficient privileges." Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574020/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1508905] Re: Graphics disorder, a "claw" appearing
Hi Albert, As I mentioned only happens once in a while. But, I'll once again disable the day info and enable it in a few days to see what happens. There's any logs I can provide when it happens? On Tue, Jun 21, 2016 at 2:09 PM, Albert Astals Cid < albert.ast...@canonical.com> wrote: > Ah, the good old giant arrow. > > Is this something you can reproduce consistently or only happens once in > a while? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1508905 > > Title: > Graphics disorder, a "claw" appearing > > Status in Today Scope: > New > Status in unity8 package in Ubuntu: > New > > Bug description: > Hi, > > Currently I have this bug. It was already present in the OTA-6. > Usually a reboot fix the problem, but after a while it come back > again. > > It only appears ate the bottom of the scope! If I swipe back to the > top the "claw" fade out. > > I've attached a screenshot. > > Thanks! > > To manage notifications about this bug go to: > https://bugs.launchpad.net/today-scope/+bug/1508905/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1508905 Title: Graphics disorder, a "claw" appearing Status in Today Scope: New Status in unity8 package in Ubuntu: New Bug description: Hi, Currently I have this bug. It was already present in the OTA-6. Usually a reboot fix the problem, but after a while it come back again. It only appears ate the bottom of the scope! If I swipe back to the top the "claw" fade out. I've attached a screenshot. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1508905/+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 1586608] [NEW] Can not start nested trusty container inside trusty container
Public bug reported: On Xenial, can not start a nested Trusty container inside a Trusty container. (All containers are privileged, tests done on two different machines, one is a fresh Xenial install) Steps to reproduce: * Create a nested Trusty container (ie. Trusty container in a trusty container) on a Xenial machine * Observe the result: # lxc-start -d --name testt --logfile=/tmp/log lxc-start: lxc_start.c: main: 341 The container failed to start. lxc-start: lxc_start.c: main: 343 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 345 Additional information can be obtained by setting the --logfile and --logpriority options. # cat /tmp/log lxc-start 1464425901.410 ERRORlxc_cgfs - cgfs.c:cgfs_init:2246 - cgroupfs failed to detect cgroup metadata lxc-start 1464425901.411 ERRORlxc_start - start.c:lxc_spawn:884 - failed initializing cgroup support lxc-start 1464425901.467 ERRORlxc_start - start.c:__lxc_start:1121 - failed to spawn 'testt' lxc-start 1464425901.467 ERRORlxc_start_ui - lxc_start.c:main:341 - The container failed to start. lxc-start 1464425901.467 ERRORlxc_start_ui - lxc_start.c:main:343 - To get more details, run the container in foreground mode. lxc-start 1464425901.467 ERRORlxc_start_ui - lxc_start.c:main:345 - Additional information can be obtained by setting the --logfile and --logpriority options. Unsure if this is a Xenial or Trusty issue (tested on original 4.4.0-22-generic and 4.5.3 kernels) Works successfully (tested): * On Xenial, Xenial container inside Xenial container * On Xenial, Trusty container inside Xenial container * On Trusty, Trusty container inside Trusty container Does NOT work: * On Xenial, Trusty container inside Trusty container Setup details: * Create container: apt-get update --yes apt-get dist-upgrade --yes apt-get install lxc --yes lxc-create -n NAME -t ubuntu -- -r trusty -a amd64 --or-- lxc-create -n NAME -t ubuntu -- -r xenial -a amd64 And add in config: lxc.include = /usr/share/lxc/config/nesting.conf Also, for Xenial: lxc.aa_allow_incomplete = 1 Then start and attach to create the nested container. Additional information: * On the Trusty container on a Xenial machine: # cat /proc/cgroups #subsys_namehierarchy num_cgroups enabled cpuset 9 12 1 cpu 2 164 1 cpuacct 2 164 1 blkio 7 164 1 memory 5 702 1 devices 10 319 1 freezer 11 28 1 net_cls 8 12 1 perf_event 3 12 1 net_prio8 12 1 hugetlb 6 12 1 pids4 305 1 # uname -a Linux testt 4.5.3 #1 SMP Mon May 9 08:18:24 CEST 2016 x86_64 x86_64 x86_64 GNU/Linux Also tested on a regular 4.4.0-22 kernel: # uname -a Linux xavier-test 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/self/mountinfo 164 119 202:1 /var/lib/lxc/testt/rootfs / rw,noatime master:1 - ext4 /dev/xvda1 rw,nobarrier,errors=remount-ro,data=ordered 165 164 0:44 / /dev rw,relatime - tmpfs none rw,size=492k,mode=755 166 164 0:43 / /proc rw,nosuid,nodev,noexec,relatime - proc proc rw 167 168 0:43 /sys/net /proc/sys/net rw,nosuid,nodev,noexec,relatime - proc proc rw 168 166 0:43 /sys /proc/sys ro,nosuid,nodev,noexec,relatime - proc proc rw 169 166 0:43 /sysrq-trigger /proc/sysrq-trigger ro,nosuid,nodev,noexec,relatime - proc proc rw 170 164 0:45 / /sys rw,nosuid,nodev,noexec,relatime - sysfs sysfs rw 171 170 0:45 / /sys rw,nosuid,nodev,noexec,relatime - sysfs sysfs rw 172 171 0:45 / /sys/devices/virtual/net rw,relatime - sysfs sysfs rw 173 172 0:45 /devices/virtual/net /sys/devices/virtual/net rw,nosuid,nodev,noexec,relatime - sysfs sysfs rw 174 171 0:37 / /sys/fs/fuse/connections rw,relatime master:28 - fusectl fusectl rw 175 171 0:7 / /sys/kernel/debug rw,relatime master:25 - debugfs debugfs rw 176 171 0:12 / /sys/kernel/security rw,nosuid,nodev,noexec,relatime master:8 - securityfs securityfs rw 177 171 0:23 / /sys/fs/pstore rw,nosuid,nodev,noexec,relatime master:11 - pstore pstore rw 178 165 0:42 / /dev/mqueue rw,relatime - mqueue mqueue rw 179 165 0:43 / /dev/.lxc/proc rw,relatime - proc proc rw 180 165 0:45 / /dev/.lxc/sys rw,relatime - sysfs sys rw 181 166 0:40 /proc/cpuinfo /proc/cpuinfo rw,nosuid,nodev,relatime master:98 - fuse.lxcfs lxcfs rw,user_id=0,group_id=0,allow_other 182 166 0:40 /proc/diskstats /proc/diskstats rw,nosuid,nodev,relatime master:98 - fuse.lxcfs lxcfs rw,user_id=0,group_id=0,allow_other 183 166 0:40 /proc/meminfo /proc/meminfo rw,nosuid,nodev,relatime master:98 - fuse.lxcfs lxcfs rw,user_id=0,group_id=0,allow_other 184 166 0:40 /proc/stat /proc/stat rw,nosuid,nodev,relatime master:98 - fuse.lxcfs lxcfs rw,user_id=0,group_id=0,allow_other 185 166 0:40 /proc/swaps /proc/swaps rw,nosuid,nodev,relatime master:98 - fuse.lxcfs lxcfs rw,user_id=0,group_id=0
[Touch-packages] [Bug 1574020] Re: Can't use networkmanager from lightdm
I can confirm this behavior on a fresh install of 16.04 on the Dell XPS 13 developer edition. I get the same error message when trying to setup a wireless connection in lightdm. I don't whether this connected or not but the hotkeys (volume up/down, screen brightness) also don't work in lightdm. I installed kernel 4.6 because of the wireless toggle not working in 4.4. That solved the wireless toggle but did not change the issue in lightdm. -- 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/1574020 Title: Can't use networkmanager from lightdm Status in network-manager package in Ubuntu: Confirmed Bug description: After upgrading to 16.04 desktop (unity) (clean install) from 14.04, (so not really upgrading, but you get the point) I noticed that lightdm with unity-greeter (all stock, nothing changed) can't connect to WiFi with network-manager. WiFi works after loggin it, but it should be working before also, if not, what's the point in having an icon there :) I get the following message: Failed to add/activate connection. - (1) Insufficient privileges. - see image. This worked fine in 14.04. I have noticed this problem in both my desktop (Broadcom WiFi) and Laptop (Intel WiFi) - So it has nothing to be with the chip. Feel free to ask for more info. Edit: From syslog: Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed Apr 23 16:50:46 desktop NetworkManager[979]: [1461423046.1662] audit: op="connection-add-activate" pid=1275 uid=108 result="fail" reason="Insufficient privileges." Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574020/+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 1583237] Re: lxc-attach strange tty behavior with dd
** Also affects: lxc (Ubuntu) Importance: Undecided Status: New ** Description changed: On a fresh Ubuntu 16 release, commands started by lxc-attach such as dd are being killed, and lxc-attach return a zero status. This scenario is working on Ubuntu 15 with previous lxc release, but not on new LXC 2.0.0 (same issue on 2.0.1 too) sudo apt-get -y install lxc sudo lxc-create -n utest -t ubuntu -- -a amd64 -b $USER sudo lxc-start -d --name utest - sudo lxc-attach -n container -- dd if=/dev/zero of=/tmp/foo bs=1M count=10 2>/tmp/bar - sudo lxc-attach -n utest_bizio_tests -- ls -lh /tmp/foo + sudo lxc-attach -n utest -- dd if=/dev/zero of=/tmp/foo bs=1M count=10 2>/tmp/bar + sudo lxc-attach -n utest -- ls -lh /tmp/foo -rw-r--r-- 1 root root 0 May 18 05:46 /tmp/foo Might be related to bug 1553097 NOTE: Sometimes the "sudo lxc-attach -n utest_bizio_tests -- ls -lh /tmp/foo" ALSO does not return anything (no output) I'm available for any additional info. ** Description changed: On a fresh Ubuntu 16 release, commands started by lxc-attach such as dd - are being killed, and lxc-attach return a zero status. + are being killed WHEN REDIRECTING stderr (to a file), and lxc-attach + return a zero status. Command works fine without the redirection. This scenario is working on Ubuntu 15 with previous lxc release, but not on new LXC 2.0.0 (same issue on 2.0.1 too) sudo apt-get -y install lxc sudo lxc-create -n utest -t ubuntu -- -a amd64 -b $USER sudo lxc-start -d --name utest sudo lxc-attach -n utest -- dd if=/dev/zero of=/tmp/foo bs=1M count=10 2>/tmp/bar sudo lxc-attach -n utest -- ls -lh /tmp/foo -rw-r--r-- 1 root root 0 May 18 05:46 /tmp/foo Might be related to bug 1553097 NOTE: Sometimes the "sudo lxc-attach -n utest_bizio_tests -- ls -lh /tmp/foo" ALSO does not return anything (no output) I'm available for any additional info. ** Summary changed: - lxc-attach strange tty behavior with dd + lxc-attach strange tty behavior when stderr is redirected to a file ** Summary changed: - lxc-attach strange tty behavior when stderr is redirected to a file + lxc-attach strange tty behavior (kills command) when stderr is redirected to a 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/1583237 Title: lxc-attach strange tty behavior (kills command) when stderr is redirected to a file Status in autopkgtest package in Ubuntu: New Status in lxc package in Ubuntu: New Bug description: On a fresh Ubuntu 16 release, commands started by lxc-attach such as dd are being killed WHEN REDIRECTING stderr (to a file), and lxc- attach return a zero status. Command works fine without the redirection. This scenario is working on Ubuntu 15 with previous lxc release, but not on new LXC 2.0.0 (same issue on 2.0.1 too) sudo apt-get -y install lxc sudo lxc-create -n utest -t ubuntu -- -a amd64 -b $USER sudo lxc-start -d --name utest sudo lxc-attach -n utest -- dd if=/dev/zero of=/tmp/foo bs=1M count=10 2>/tmp/bar sudo lxc-attach -n utest -- ls -lh /tmp/foo -rw-r--r-- 1 root root 0 May 18 05:46 /tmp/foo Might be related to bug 1553097 (and/or https://github.com/lxc/lxc/pull/873) NOTE: Sometimes the "sudo lxc-attach -n utest_bizio_tests -- ls -lh /tmp/foo" ALSO does not return anything (no output) I'm available for any additional info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1583237/+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 1583237] Re: lxc-attach strange tty behavior (kills command) when stderr is redirected to a file
** Description changed: On a fresh Ubuntu 16 release, commands started by lxc-attach such as dd are being killed WHEN REDIRECTING stderr (to a file), and lxc-attach return a zero status. Command works fine without the redirection. This scenario is working on Ubuntu 15 with previous lxc release, but not on new LXC 2.0.0 (same issue on 2.0.1 too) sudo apt-get -y install lxc sudo lxc-create -n utest -t ubuntu -- -a amd64 -b $USER sudo lxc-start -d --name utest sudo lxc-attach -n utest -- dd if=/dev/zero of=/tmp/foo bs=1M count=10 2>/tmp/bar sudo lxc-attach -n utest -- ls -lh /tmp/foo -rw-r--r-- 1 root root 0 May 18 05:46 /tmp/foo - Might be related to bug 1553097 + Might be related to bug 1553097 (and/or + https://github.com/lxc/lxc/pull/873) NOTE: Sometimes the "sudo lxc-attach -n utest_bizio_tests -- ls -lh /tmp/foo" ALSO does not return anything (no output) I'm available for any additional info. -- 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/1583237 Title: lxc-attach strange tty behavior (kills command) when stderr is redirected to a file Status in autopkgtest package in Ubuntu: New Status in lxc package in Ubuntu: New Bug description: On a fresh Ubuntu 16 release, commands started by lxc-attach such as dd are being killed WHEN REDIRECTING stderr (to a file), and lxc- attach return a zero status. Command works fine without the redirection. This scenario is working on Ubuntu 15 with previous lxc release, but not on new LXC 2.0.0 (same issue on 2.0.1 too) sudo apt-get -y install lxc sudo lxc-create -n utest -t ubuntu -- -a amd64 -b $USER sudo lxc-start -d --name utest sudo lxc-attach -n utest -- dd if=/dev/zero of=/tmp/foo bs=1M count=10 2>/tmp/bar sudo lxc-attach -n utest -- ls -lh /tmp/foo -rw-r--r-- 1 root root 0 May 18 05:46 /tmp/foo Might be related to bug 1553097 (and/or https://github.com/lxc/lxc/pull/873) NOTE: Sometimes the "sudo lxc-attach -n utest_bizio_tests -- ls -lh /tmp/foo" ALSO does not return anything (no output) I'm available for any additional info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1583237/+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 1532607] Re: Phone not usable while a call comes in - followed by "restart"
Until the moment I did not have this bug, at least with phone calls, because I have those reboots when I receive SMS. In OTA-8.5, the phone was great, no reboots, everything worked as expected. My phone is the E4.5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1532607 Title: Phone not usable while a call comes in - followed by "restart" Status in Canonical System Image: Confirmed Status in Mir: New Status in mir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: My system: current build number: 225 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-01-09 06:52:53 version version: 225 version ubuntu: 20160109 version device: 20151216-378d4f3 version custom: 2015--36-46-vivid What happened: Someone called me and I wanted to take the call on the phone (nothing attached to the phone). The screen was locked and I pressed the power button to unlock the screen. The phone did not react on any pushed buttons. The phone continued ringing but I was not able to do anything with the phone during this time. During the next minute the phone was blocked. After this period a "restart" followed. "Restart": The restart was not a real reset. The phone screen was black. Then approx. 1 - 2 minutes after the call was gone, the screen went on again and the ubuntu logo with the dots appeared (same screen when you start the phone but without the "bq"-screen). I did not need to enter the PIN code of the SIM card. The phone was again fully operational. This happened on January, 10th at approx. 13:30 h. I have attached the sys.log for your review and hopefully for tracing back the issue to the root cause. Matthias To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532607/+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 1276186] Re: System becomes unresponsive, ibus-ui-daemon takes ~150 % cpu
Ubuntu 14.04 - Confirmed as well. Everything lags, and non responsive. Disabling ibus get rids of the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1276186 Title: System becomes unresponsive, ibus-ui-daemon takes ~150 % cpu Status in ibus package in Ubuntu: Confirmed Bug description: As stated the graphical desktop became unresponsive. Dropping to CTRL + ALT + F1 terminal and `top`showed ibus-ui-daemon taking around 150 % cpu time and ibus-ui-gtk3 taking around 50 % cpu time. (names may contain minor errors) Tried to kill processes, rebooted. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ibus 1.5.3-6ubuntu2.1 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Tue Feb 4 16:41:03 2014 InstallationDate: Installed on 2013-09-10 (147 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: ibus UpgradeStatus: Upgraded to saucy on 2013-10-23 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1276186/+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 1373463] Re: [indicators] Impossible to disable cellular data from indicator
I will comment this, bug, with my experience, trying to help the decision of what to do. I think this issue its all about customization. By the which, for the moment, ubuntu touch is not famous for. Yet again, every person has it owns requirements, so we end up on customization. In my country the button to toggle the celular data is very used. Off course adding this button has advantages and disadvantages, at least for moment. Mine are: *I use celular data, I have it most of the time turned on. In my country (Portugal), my carrier (Meo) offers a tariff (Moche) with free traffic for apps like whats app, facebook messenger, instagram, viber, iMessage, Skype and a plus 500mb to surfer the web, view email etc. Its mostly design for people under 26 years of age, we use it a lot. In my case, and many others, we use the celular data button to stay "offline" to our social media, to all apps. But I can't remember a situation when I used the airplane mode (this mode for me is useless), because I still want my phone be capable of receiving sms and calls from my parents, or even in emergency situations. In this case, adding this button saves time, because it can turn of celular data with on just click and save celular data. Some people say that also saves power, but I don't see that as the principal argument. *Ubuntu phone experience. As someone mentioned in the mailing list, if we add this button to the indicator network, we can put ourselves exposed to risks. But yet again, I think is a matter of customization, for some its make sense for others not. If other people couldn't change the settings right up from the indicators, at least with the screen locked with passcode, we wouldn't be talking about this specific issue. So, every person has its own requirements. Adding this button will make every person happy? No. Not adding this button will make everybody happy? No. In my opinion, adding a functionality that let's users to add or remove buttons from each indicator would be the best option. Off course, canonical has to make a default option and decide to put it by default or not, but users will also have the possibility to add or remove. I remember Cyanogenmod 10.1.3 with android 4.2.2 has this functionality, and I loved it, letting users to setting up what they want to see (http://cdn.arstechnica.net/wp- content/uploads/2013/02/Screenshot_2013-02-22-16-58-13.png). But, for the moment, if the only option is to add or not to add, I will go to: Add the button. Hope I've helped with some ideas. Good work people. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1373463 Title: [indicators] Impossible to disable cellular data from indicator Status in Canonical System Image: Confirmed Status in Ubuntu UX: Triaged Status in indicator-network package in Ubuntu: Triaged Bug description: I was wondering : Why it isn't possible to disable data from the network indicator ? Probably with a switch button that offer the choice between no data or data activated (with the last data activated state (2g only or 2G,3G,4G). Why this ? Because it's the first setting to change to save battery, and probably one of the most used (I asked around me, everyone agreed they would prefer that over Wi-Fi if only one was possible). I think it's stupid to go to the settings app for the most common action (and very frustrating). Of course, this also apply for the battery setting page (that already contain Wi-Fi, GPS, Bluetooth and brightness settings). I asked that on the phone ML, I've been invited to file a wishlist bug there to "help" designers with next iteration of network indicator. So here it is ! [1] : mailing list discussion with already some support to this idea : https://lists.launchpad.net/ubuntu-phone/msg09910.html To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1373463/+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 1328260] Re: mighty mouse bluetooth not pairing
I was getting this same thing with a Microsoft Designer Mouse but after running `bluez-simple-agent` and using pin the mouse pairs and the 'New Device Setup' says "Succesfully set up device 'Designer Mouse'" but it doesn't work. In the Bluetooth devices it says 'Paired Yes' but the 'switch' on Connection is set to OFF and is disabled. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1328260 Title: mighty mouse bluetooth not pairing Status in bluez package in Ubuntu: Confirmed Bug description: Using the default GUI, I cannot pair my Apple Mighty Mouse. The mouse is detected, but when trying to pair, nothing happens and it is impossible to connect. It seems there should be an agent running to handle the pairing/pin stuff, I found that here: http://askubuntu.com/questions/453655/ubuntu-14-04-bluetooth-magic-mouse-doesnt-pair-no-agent-available It might be an issue with more devices, I did not test it. So the fix: In a terminal as a normal user do: bluez-simple-agent then use pin (worked in my case). Description: Ubuntu 14.04 LTS Release: 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1328260/+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 1522579] Re: ip rule list broken with kernel 3.19.0-37.42-generic on Ubuntu 14.04.3
I had the same problem. Upgrading to 3.19.0-39 fixes the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1522579 Title: ip rule list broken with kernel 3.19.0-37.42-generic on Ubuntu 14.04.3 Status in iproute2 package in Ubuntu: New Bug description: When running Ubuntu 14.04.3 with kernel 3.19.0-37.42-generic, the command ip rule list scrolls 0: from all lookup local until ^c is used to break out. With the previous kernel, in my case 3.19.0-25.26-generic the command ip rule list displays; 0:from all lookup local 32766:from all lookup main 32767:from all lookup default as it should. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: iproute2 3.12.0-2ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-37.42~14.04.1-generic 3.19.8-ckt9 Uname: Linux 3.19.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Thu Dec 3 13:35:14 2015 InstallationDate: Installed on 2015-12-03 (0 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1522579/+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
