[Touch-packages] [Bug 1451096] Re: wrong rsyslog dependency in ubuntu-minimal
As of 16.10 ubuntu-minimal "Recommends: rsyslog" which I thin is still wrong but not as bad as dependency. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1451096 Title: wrong rsyslog dependency in ubuntu-minimal Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: According to dependencies of ubuntu-minimal rsyslog is considered to be part of minimal supported system. With the switch to systemd it's obsolete: the journald is shipped and running anyway and it already provides secure logging by default. IT would be better to remove rsyslog from ubuntu-minimal dependencies (and, ideally, from default install as well) and enables "ForwardToSyslog=no" in /etc/systemd/journald.conf - the users who are willing to install advanced legacy logging will still be able to do that just fine, but really does not belong to the bare-minimum system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1451096/+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 1582421] Re: removing upstart breaks user login
16.10 is slightly better in this regard - at least login is possible when upstart is purged, but the fact that it's still installed by default is alarming: did they forgot to fix smth again? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1582421 Title: removing upstart breaks user login Status in ubuntu-meta package in Ubuntu: New Bug description: After "apt remove upstart" it's impossible to login into user's session via lightdm on xubuntu 16.04 - I thought we've finally ditched that junk, how come it still breaks the system on removal? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1582421/+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 1633695] [NEW] upgrade to 16.10 fails
Public bug reported:
Attempting to upgrade 16.04 -> 16.10 fails with cryptic error:
sudo update-manager
/usr/bin/update-manager:28: PyGIWarning: Gtk was imported without specifying a
version first. Use gi.require_version('Gtk', '3.0
') before import to ensure that the right version gets loaded.
from gi.repository import Gtk
/usr/lib/python3/dist-packages/UpdateManager/UnitySupport.py:29: PyGIWarning:
Dbusmenu was imported without specifying a version
first. Use gi.require_version('Dbusmenu', '0.4') before import to ensure that
the right version gets loaded.
from gi.repository import Dbusmenu, Unity
/usr/lib/python3/dist-packages/UpdateManager/UnitySupport.py:29: PyGIWarning:
Unity was imported without specifying a version first. Use
gi.require_version('Unity', '7.0') before import to ensure that the right
version gets loaded.
from gi.repository import Dbusmenu, Unity
Проверка наличия нового релиза Ubuntu
/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcher.py:23:
PyGIWarning: Gtk was imported without specifying a version first. Use
gi.require_version('Gtk', '3.0') before import to ensure that the right version
gets loaded.
from gi.repository import Gtk, Gdk
/usr/lib/python3/dist-packages/DistUpgrade/ReleaseNotesViewerWebkit.py:36:
PyGIWarning: WebKit was imported without specifying a version first. Use
gi.require_version('WebKit', '3.0') before import to ensure that the right
version gets loaded.
from gi.repository import WebKit
Traceback (most recent call last):
Traceback (most recent call last):
File "/usr/bin/do-release-upgrade", line 165, in
fetcher.run()
File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcherCore.py",
line 275, in run
if not self.showReleaseNotes():
File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcher.py", line
62, in showReleaseNotes
res = self._try_show_release_notes_webkit()
File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcher.py", line
74, in _try_show_release_notes_webkit
self.new_dist.releaseNotesHtmlUri)
File
"/usr/lib/python3/dist-packages/DistUpgrade/ReleaseNotesViewerWebkit.py", line
48, in __init__
self._on_navigation_policy_decision_requested)
AttributeError: 'ReleaseNotesViewerWebkit' object has no attribute
'_on_navigation_policy_decision_requested'
This is xubuntu 16.04 x86_64 with all the latest updates installed.
** Affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1633695
Title:
upgrade to 16.10 fails
Status in ubuntu-meta package in Ubuntu:
New
Bug description:
Attempting to upgrade 16.04 -> 16.10 fails with cryptic error:
sudo update-manager
/usr/bin/update-manager:28: PyGIWarning: Gtk was imported without specifying
a version first. Use gi.require_version('Gtk', '3.0
') before import to ensure that the right version gets loaded.
from gi.repository import Gtk
/usr/lib/python3/dist-packages/UpdateManager/UnitySupport.py:29: PyGIWarning:
Dbusmenu was imported without specifying a version
first. Use gi.require_version('Dbusmenu', '0.4') before import to ensure
that the right version gets loaded.
from gi.repository import Dbusmenu, Unity
/usr/lib/python3/dist-packages/UpdateManager/UnitySupport.py:29: PyGIWarning:
Unity was imported without specifying a version first. Use
gi.require_version('Unity', '7.0') before import to ensure that the right
version gets loaded.
from gi.repository import Dbusmenu, Unity
Проверка наличия нового релиза Ubuntu
/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcher.py:23:
PyGIWarning: Gtk was imported without specifying a version first. Use
gi.require_version('Gtk', '3.0') before import to ensure that the right version
gets loaded.
from gi.repository import Gtk, Gdk
/usr/lib/python3/dist-packages/DistUpgrade/ReleaseNotesViewerWebkit.py:36:
PyGIWarning: WebKit was imported without specifying a version first. Use
gi.require_version('WebKit', '3.0') before import to ensure that the right
version gets loaded.
from gi.repository import WebKit
Traceback (most recent call last):
Traceback (most recent call last):
File "/usr/bin/do-release-upgrade", line 165, in
fetcher.run()
File
"/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcherCore.py", line
275, in run
if not self.showReleaseNotes():
File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcher.py",
line 62, in showReleaseNotes
res = self._try_show_release_notes_webkit()
File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcher.py",
line 74, in _try_show_release_notes_webkit
self.new_dist.releaseNotesHtmlUri)
File
"/usr/lib/python3/dist-packages/DistUpgrade/ReleaseNotesViewerWebkit.py", line
48, in __init__
[Touch-packages] [Bug 1627546] [NEW] use safe mount for usb devices
Public bug reported: For years ubuntu has been plagued by horrible user experience when dealing with usb drives: - user forget to unmount device - fs is corrupted - user insert device back and is overwritten/lost Luckily solution is finally available: ubuntu should use systemd-mount for all usb devices so they are - mount only when it's really necessary - aggressively unmounted to prevent data loss - fscked before mounting This will lead to much nicer situation where new users will not blame ubuntu anymore for data loss. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1627546 Title: use safe mount for usb devices Status in ubuntu-meta package in Ubuntu: New Bug description: For years ubuntu has been plagued by horrible user experience when dealing with usb drives: - user forget to unmount device - fs is corrupted - user insert device back and is overwritten/lost Luckily solution is finally available: ubuntu should use systemd-mount for all usb devices so they are - mount only when it's really necessary - aggressively unmounted to prevent data loss - fscked before mounting This will lead to much nicer situation where new users will not blame ubuntu anymore for data loss. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1627546/+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 1582419] Re: mounting usb drives asks for password
Could be related to #1577227 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1582419 Title: mounting usb drives asks for password Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Every time I insert usb drive into my laptop xubuntu 16.04 asks for password (from udisks2). This is as dumb as windows and such stupidity have not happened in 15.10. I've check user's privileges and all is marked as allowed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1582419/+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 1577227] Re: shutdown fails with password request
Seems like xubuntu somehow managed to break user sessions: I'm member of sudo group and default .pkla in /var/lib/polkit-1 should allow me to shutdown without asking for password if there is an active session. Apparently polkit fails to see the session - I recall there's been some news regarding xfce and consolekit, not sure if it's related. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1577227 Title: shutdown fails with password request Status in ubuntu-meta package in Ubuntu: New Bug description: When trying to shutdown xubuntu 16.04 it asks for password. If I close the request window than it logs me out instead of shutting down. This is REGRESSION - such basic functionality as power down machine wasn't broken in 15.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1577227/+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 1582421] [NEW] removing upstart breaks user login
Public bug reported: After "apt remove upstart" it's impossible to login into user's session via lightdm on xubuntu 16.04 - I thought we've finally ditched that junk, how come it still breaks the system on removal? ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1582421 Title: removing upstart breaks user login Status in ubuntu-meta package in Ubuntu: New Bug description: After "apt remove upstart" it's impossible to login into user's session via lightdm on xubuntu 16.04 - I thought we've finally ditched that junk, how come it still breaks the system on removal? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1582421/+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 1577227] Re: shutdown fails with password request
I don't think WM have anything to do with it - you've probably meant DE. I'm using xfce on xubuntu - the same as in 15.10 from which I've upgraded. ** Changed in: ubuntu-meta (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1577227 Title: shutdown fails with password request Status in ubuntu-meta package in Ubuntu: New Bug description: When trying to shutdown xubuntu 16.04 it asks for password. If I close the request window than it logs me out instead of shutting down. This is REGRESSION - such basic functionality as power down machine wasn't broken in 15.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1577227/+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 1582419] [NEW] mounting usb drives asks for password
Public bug reported: Every time I insert usb drive into my laptop xubuntu 16.04 asks for password (from udisks2). This is as dumb as windows and such stupidity have not happened in 15.10. I've check user's privileges and all is marked as allowed. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1582419 Title: mounting usb drives asks for password Status in ubuntu-meta package in Ubuntu: New Bug description: Every time I insert usb drive into my laptop xubuntu 16.04 asks for password (from udisks2). This is as dumb as windows and such stupidity have not happened in 15.10. I've check user's privileges and all is marked as allowed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1582419/+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 1577227] [NEW] shutdown fails with password request
Public bug reported: When trying to shutdown xubuntu 16.04 it asks for password. If I close the request window than it logs me out instead of shutting down. This is REGRESSION - such basic functionality as power down machine wasn't broken in 15.10. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1577227 Title: shutdown fails with password request Status in ubuntu-meta package in Ubuntu: New Bug description: When trying to shutdown xubuntu 16.04 it asks for password. If I close the request window than it logs me out instead of shutting down. This is REGRESSION - such basic functionality as power down machine wasn't broken in 15.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1577227/+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 1573441] [NEW] upgrade to 16.04 fails
Public bug reported: The upgrade from 15.10 with all the updates installed fails: - when "sudo /usr/bin/python3 /usr/bin/do-release-upgrade --frontend=DistUpgradeViewGtk3" is executed it hangs forever: java version "1.7.0_95" OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.15.10.2) OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode) - when the same command is ran without sudo it downloads proper tar but fails with "no such file or directory" after trying to extract it: extracting 'xenial.tar.gz' Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Exactly the same behavior is observed than it's called indirectly from update-manager. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1573441 Title: upgrade to 16.04 fails Status in ubuntu-meta package in Ubuntu: New Bug description: The upgrade from 15.10 with all the updates installed fails: - when "sudo /usr/bin/python3 /usr/bin/do-release-upgrade --frontend=DistUpgradeViewGtk3" is executed it hangs forever: java version "1.7.0_95" OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.15.10.2) OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode) - when the same command is ran without sudo it downloads proper tar but fails with "no such file or directory" after trying to extract it: extracting 'xenial.tar.gz' Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Exactly the same behavior is observed than it's called indirectly from update-manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1573441/+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 1542861] [NEW] machinectl packaging broken
Public bug reported: When I type "machinectl" in 15.10 I got message which recommends me to do following: sudo apt-get install systemd This is obviously incorrect because systemd is already installed. Seems like a packaging error. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1542861 Title: machinectl packaging broken Status in systemd package in Ubuntu: New Bug description: When I type "machinectl" in 15.10 I got message which recommends me to do following: sudo apt-get install systemd This is obviously incorrect because systemd is already installed. Seems like a packaging error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1542861/+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 1453167] Re: replace resolvconf with systemd-resolvd
Thanks for the link. Would be nice to get the same features into desktop images as well. NM can complement systemd-networkd nicely in there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1453167 Title: replace resolvconf with systemd-resolvd Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: For the sake of smoother user experience and easier learning curve would be nice to get rid of legacy resolvconf package and use systemd- resolvd which is nicely integrated with the rest of the stack and uses unified configuration file systax and conventions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1453167/+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 1526824] [NEW] boot on uefi directly instead of grub
Public bug reported: Right now even on modern systems with UEFI, Ubuntu is booted via grub2 bootloader. This is slow, error-prone and completely unnecessary. Would be much better and faster to make GNU/Linux kernel bootable directly by UEFI firmware. This would also simplify dual-boot setups. An example of how to pass kernel command-line parameters is shown in: http://harald.hoyer.xyz/2015/02/25/single-uefi-executable-for-kernelinitrdcmdline/ ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1526824 Title: boot on uefi directly instead of grub Status in ubuntu-meta package in Ubuntu: New Bug description: Right now even on modern systems with UEFI, Ubuntu is booted via grub2 bootloader. This is slow, error-prone and completely unnecessary. Would be much better and faster to make GNU/Linux kernel bootable directly by UEFI firmware. This would also simplify dual-boot setups. An example of how to pass kernel command-line parameters is shown in: http://harald.hoyer.xyz/2015/02/25/single-uefi-executable-for-kernelinitrdcmdline/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1526824/+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 1480952] Re: Enable journal-remote
Will this arrive as part of wily-backports or we'll have to wait till 16.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/1480952 Title: Enable journal-remote Status in systemd package in Ubuntu: Triaged Status in systemd package in Debian: Fix Released Bug description: Right now there's nothing like systemd-journal-remote and systemd- journal-upload available in Ubuntu's repo. Would be great to have this packaged and installable in one command (or better yet - by default) to get modern remote logging to/from ubuntu as quickly and pain-free for users as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1480952/+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 993298] Re: Please make NetworkManager-controlled dnsmasq respect /etc/hosts
Much better solution would be adding wildcards support directly to /etc/hosts. Or at least to systemd-resolved. There is even RFE for the latter: https://github.com/systemd/systemd/issues/766 Having dns server running just to add wildcards is really an overkill. Systemd-resolved is much better suit. -- 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/993298 Title: Please make NetworkManager-controlled dnsmasq respect /etc/hosts Status in network-manager package in Ubuntu: Confirmed Bug description: Since 12.04 NetworkManager uses the dnsmasq plugin by default to resolve DNS requests. Unfortunately the dnsmasq plug-in has --no- hosts, etc. hard coded [1] which means (among other things) that after the upgrade to 12.04 /etc/hosts will no longer be used to resolve DNS requests. This changes the prior behavior of NetworkManager without any visible warning to the end user. AFAICS there's no other way to work around this problem as to manually revert the change and disable the dnsmasq plug-in in the NetworkManager config, see [2,3]: "To turn off dnsmasq in Network Manager, you need to edit /etc/NetworkManager/NetworkManager.conf and comment the 'dns=dnsmasq' line then do a 'sudo restart network-manager'." This is of course not a bug in the NetworkManager which just behaves as intended. The problem is in the change of the configuration of the Ubuntu packaging which will probably leave many wondering why their /etc/hosts suddenly no longer works. This cost me considerable time to debug and probably is a usability problem for others, too. Maybe you could provide a more visible documentation than that in [3]? E.g., *including a comment in /etc/hosts that explains the change* and how to work around it would have saved me a lot of time. It would have automatically alerted me on upgrade as manual changes to /etc/hosts would then have triggered a prompt while leaving those users with standard /etc/hosts in peace. Probably similar problems arise with other disabled config files and could be alerted to the users? Thinking of resolv.conf, etc. [1] http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/dnsmasq-manager/nm-dnsmasq-manager.c, line 285 [2] i.e. http://ubuntuforums.org/showthread.php?t=1968061 [3] http://www.stgraber.org/2012/02/24/dns-in-ubuntu-12-04/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/993298/+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 1479732] Re: systemd causes mess in /var/tmp
This bug is wontfix by upstream but patching systemd in ubuntu to prepend . to each systemd's folder in /var/tmp should be trivial. -- 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/1479732 Title: systemd causes mess in /var/tmp Status in systemd package in Ubuntu: New Bug description: There's enormous amount of directories like systemd-private- fdd28b0bfe4c47808e41dbb7a0300bdc-colord.service-vrglD7 in /var/tmp It's clear why they are necessary but it's still looks irritating and is magnified (compared to /tmp for example) by the fact that /var/tmp is not cleaned up (and of course it shouldn't be) on every reboot. The solution is trivial and already employed by lots of services for /tmp - just prepend . to the folder name so it's hidden from user's file manager. Would be excellent if ubuntu could apply this to systemd as well: the lesser is chance for user confusion (those directories are unaccessible to the user anyway so there's little sense in showing them) - the better. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1479732/+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 1480952] Re: Enable journal-remote
To clarify: since we don't know if users prefer push or pull model we should provide both systemd-journal-upload and systemd-journal- gatewayd and let user decide which one to enable. And systemd-journal- remote is required for both modes of operation anyway. -- 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/1480952 Title: Enable journal-remote Status in systemd package in Ubuntu: Triaged Bug description: Right now there's nothing like systemd-journal-remote and systemd- journal-upload available in Ubuntu's repo. Would be great to have this packaged and installable in one command (or better yet - by default) to get modern remote logging to/from ubuntu as quickly and pain-free for users as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1480952/+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 1480952] [NEW] remote logging missing
Public bug reported: Right now there's nothing like systemd-journal-remote and systemd- journal-upload available in Ubuntu's repo. Would be great to have this packaged and installable in one command (or better yet - by default) to get modern remote logging to/from ubuntu as quickly and pain-free for users as possible. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1480952 Title: remote logging missing Status in systemd package in Ubuntu: New Bug description: Right now there's nothing like systemd-journal-remote and systemd- journal-upload available in Ubuntu's repo. Would be great to have this packaged and installable in one command (or better yet - by default) to get modern remote logging to/from ubuntu as quickly and pain-free for users as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1480952/+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 1479732] [NEW] systemd causes mess in /var/tmp
Public bug reported: There's enormous amount of directories like systemd-private- fdd28b0bfe4c47808e41dbb7a0300bdc-colord.service-vrglD7 in /var/tmp It's clear why they are necessary but it's still looks irritating and is magnified (compared to /tmp for example) by the fact that /var/tmp is not cleaned up (and of course it shouldn't be) on every reboot. The solution is trivial and already employed by lots of services for /tmp - just prepend . to the folder name so it's hidden from user's file manager. Would be excellent if ubuntu could apply this to systemd as well: the lesser is chance for user confusion (those directories are unaccessible to the user anyway so there's little sense in showing them) - the better. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1479732 Title: systemd causes mess in /var/tmp Status in systemd package in Ubuntu: New Bug description: There's enormous amount of directories like systemd-private- fdd28b0bfe4c47808e41dbb7a0300bdc-colord.service-vrglD7 in /var/tmp It's clear why they are necessary but it's still looks irritating and is magnified (compared to /tmp for example) by the fact that /var/tmp is not cleaned up (and of course it shouldn't be) on every reboot. The solution is trivial and already employed by lots of services for /tmp - just prepend . to the folder name so it's hidden from user's file manager. Would be excellent if ubuntu could apply this to systemd as well: the lesser is chance for user confusion (those directories are unaccessible to the user anyway so there's little sense in showing them) - the better. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1479732/+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 583994] Re: Consider replacing ntpdate calls by 'ntpd -g'
Bug trackers are for information related to bugs. If you're unable to contribute something meaningful - go whine someplace else: there're forums, twitter, social networks for that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/583994 Title: Consider replacing ntpdate calls by 'ntpd -g' Status in NTP: Invalid Status in ntp package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Status in ntp package in Debian: New Bug description: Binary package hint: ntp Given that 'ntpdate' is being obsoleted upstream [1], we should replace 'ntpdate' usage by: * ntpd -qg (if we really want to set the time and exit), or * ntpd-g (if we want to keep ntpd running) the '-q' option will set the clock once, and exit; the 'g' allows for large corrections to the clock, like what is done by 'ntpdate'. [1] http://www.eecis.udel.edu/~mills/ntp/html/ntpdate.html To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/583994/+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 583994] Re: Consider replacing ntpdate calls by 'ntpd -g'
I'm not a systemd hater Don't flatter yourself. Since when exactly inability of some users to run sudo apt install ntpdate equals to systemd hegemony? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/583994 Title: Consider replacing ntpdate calls by 'ntpd -g' Status in NTP: Invalid Status in ntp package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Status in ntp package in Debian: New Bug description: Binary package hint: ntp Given that 'ntpdate' is being obsoleted upstream [1], we should replace 'ntpdate' usage by: * ntpd -qg (if we really want to set the time and exit), or * ntpd-g (if we want to keep ntpd running) the '-q' option will set the clock once, and exit; the 'g' allows for large corrections to the clock, like what is done by 'ntpdate'. [1] http://www.eecis.udel.edu/~mills/ntp/html/ntpdate.html To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/583994/+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 1477130] [NEW] timedatectl fails inside container
Public bug reported: lxc-attach -n mycont -- timedatectl Failed to create bus connection: No such file or directory while on the host timedatectl works just fine. lxc Version: 1.1.2-0ubuntu3 on ubuntu 15.04 x86_64 ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1477130 Title: timedatectl fails inside container Status in lxc package in Ubuntu: New Bug description: lxc-attach -n mycont -- timedatectl Failed to create bus connection: No such file or directory while on the host timedatectl works just fine. lxc Version: 1.1.2-0ubuntu3 on ubuntu 15.04 x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1477130/+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 1451247] Re: wrong ntpdate dependency in ubuntu-minimal
On a related note: systemd-timesyncd seems to be blindly imported from Debian so it defaults to *.debian.pool.ntp.org - if Ubuntu consider itself to be a separate product than it might make sense to apply for *.ubuntu.pool.ntp.org -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1451247 Title: wrong ntpdate dependency in ubuntu-minimal Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Ubuntu-minimal has a hardcoded dependency on ntpdate which is entirely unnecessary because for basic minimal task of syncing time with ntp server systemd-timesyncd is more than enough. Replacing this dependency will allow to save some space on install media and make learning easier for new users because timesyncd follows exact same configuration convention as the rest of the stack which makes it natural to get aquainted with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1451247/+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 1451096] Re: wrong rsyslog dependency in ubuntu-minimal
Not that I know of. Adding mkdir -p /var/log/journal to ubuntu's systemd package should be trivial though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1451096 Title: wrong rsyslog dependency in ubuntu-minimal Status in ubuntu-meta package in Ubuntu: New Bug description: According to dependencies of ubuntu-minimal rsyslog is considered to be part of minimal supported system. With the switch to systemd it's obsolete: the journald is shipped and running anyway and it already provides secure logging by default. IT would be better to remove rsyslog from ubuntu-minimal dependencies (and, ideally, from default install as well) and enables ForwardToSyslog=no in /etc/systemd/journald.conf - the users who are willing to install advanced legacy logging will still be able to do that just fine, but really does not belong to the bare-minimum system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1451096/+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 1453167] Re: replace resolvconf with systemd-resolvd
The link seems to be broken. Is there bug tracking transition to networkd? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1453167 Title: replace resolvconf with systemd-resolvd Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: For the sake of smoother user experience and easier learning curve would be nice to get rid of legacy resolvconf package and use systemd- resolvd which is nicely integrated with the rest of the stack and uses unified configuration file systax and conventions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1453167/+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 1474047] [NEW] pppoe fails inside container
Public bug reported: I've created privileged lxc container on ubuntu 15.04 x86_64 (sudo lxc- create...) added their ethernet interface connected to dsl modem - so far so good: pppoe-discovery from inside the container recognoze it, pppoeconf is able to configure it. The problem is that the container network fails to start automatically during the boot due to missing /dev/ppp device. I've added following line to the container config: lxc.cgroup.devices.allow = c 108:0 rwm On the host device is available: ls -alh /dev/ppp crw--- 1 root root 108, 0 Jul 13 17:37 /dev/ppp But inside the container there's nothing. Even more curious - if I manually call mknod from withing the container than dsl connection is established just fine: sudo lxc-attach -n mycontainer -- mknod /dev/ppp c 108 0 ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1474047 Title: pppoe fails inside container Status in lxc package in Ubuntu: New Bug description: I've created privileged lxc container on ubuntu 15.04 x86_64 (sudo lxc-create...) added their ethernet interface connected to dsl modem - so far so good: pppoe-discovery from inside the container recognoze it, pppoeconf is able to configure it. The problem is that the container network fails to start automatically during the boot due to missing /dev/ppp device. I've added following line to the container config: lxc.cgroup.devices.allow = c 108:0 rwm On the host device is available: ls -alh /dev/ppp crw--- 1 root root 108, 0 Jul 13 17:37 /dev/ppp But inside the container there's nothing. Even more curious - if I manually call mknod from withing the container than dsl connection is established just fine: sudo lxc-attach -n mycontainer -- mknod /dev/ppp c 108 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1474047/+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 1470580] Re: unprivileged lxc containers fails with custom bridge
Thanks for clarification! Would be kinda helpful if lxc-start could print actual numbers (X quota configured for bridge123, Y is in use). What's the upper limit on those quota numbers? Can I have 100 bridges with 400 interfaces in each? -- 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/1470580 Title: unprivileged lxc containers fails with custom bridge Status in lxc package in Ubuntu: Confirmed Bug description: Using 15.04 x86_64 with all the updates installed. I'd like 2 containers to communicate with each other via bridge interface. For that I've created interface as follows: /etc/systemd/network/internalbridge1.netdev: [NetDev] Name=ibr1 Kind=bridge /etc/lxc/lxc-usernet: # USERNAME TYPE BRIDGE COUNT x veth ibr1 8 The 'x' is my username, it's first and only user configured in the system so default id map should work fine. The container network is configured as follows: lxc.network.type = veth lxc.network.link = ibr1 lxc.network.flags = up lxc.network.name = internal lxc.network.ipv4 = 10.1.8.2/24 lxc.network.ipv4.gateway = 10.1.8.1 I've enabled the service and brought the bridge up - showing ok via 'ip a' and 'brctl show'. Also works fine with priviledged containers. However with unpriviledged containers it fails: lxc-start -n asterisk -l debug -F --logfile lxc-user.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1470580/+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 1470580] Re: unprivileged lxc containers fails with custom bridge
Also, what does Quota reached. mean? What kind of quota is that? -- 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/1470580 Title: unprivileged lxc containers fails with custom bridge Status in lxc package in Ubuntu: Confirmed Bug description: Using 15.04 x86_64 with all the updates installed. I'd like 2 containers to communicate with each other via bridge interface. For that I've created interface as follows: /etc/systemd/network/internalbridge1.netdev: [NetDev] Name=ibr1 Kind=bridge /etc/lxc/lxc-usernet: # USERNAME TYPE BRIDGE COUNT x veth ibr1 8 The 'x' is my username, it's first and only user configured in the system so default id map should work fine. The container network is configured as follows: lxc.network.type = veth lxc.network.link = ibr1 lxc.network.flags = up lxc.network.name = internal lxc.network.ipv4 = 10.1.8.2/24 lxc.network.ipv4.gateway = 10.1.8.1 I've enabled the service and brought the bridge up - showing ok via 'ip a' and 'brctl show'. Also works fine with priviledged containers. However with unpriviledged containers it fails: lxc-start -n asterisk -l debug -F --logfile lxc-user.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1470580/+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 1470580] Re: unprivileged lxc containers fails with custom bridge
lxc-start -n asterisk -F Quota reached. lxc-start: start.c: lxc_spawn: 1000 failed to create configured network lxc-start: start.c: __lxc_start: 1164 failed to spawn 'asterisk' lxc-start: start.c: main: 344 The container failed to start. lxc-start: start.c: main 348 Additional information can be obtained by setting the --logfile and --logpriority options. -- 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/1470580 Title: unprivileged lxc containers fails with custom bridge Status in lxc package in Ubuntu: Confirmed Bug description: Using 15.04 x86_64 with all the updates installed. I'd like 2 containers to communicate with each other via bridge interface. For that I've created interface as follows: /etc/systemd/network/internalbridge1.netdev: [NetDev] Name=ibr1 Kind=bridge /etc/lxc/lxc-usernet: # USERNAME TYPE BRIDGE COUNT x veth ibr1 8 The 'x' is my username, it's first and only user configured in the system so default id map should work fine. The container network is configured as follows: lxc.network.type = veth lxc.network.link = ibr1 lxc.network.flags = up lxc.network.name = internal lxc.network.ipv4 = 10.1.8.2/24 lxc.network.ipv4.gateway = 10.1.8.1 I've enabled the service and brought the bridge up - showing ok via 'ip a' and 'brctl show'. Also works fine with priviledged containers. However with unpriviledged containers it fails: lxc-start -n asterisk -l debug -F --logfile lxc-user.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1470580/+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 1470580] Re: unprivileged lxc containers fails with custom bridge
Btw, is there a way to make logging to actually work and log everything? Maybe add --logging-indeed-log or smth like that in addition to existing -l and --logfile? ** Changed in: lxc (Ubuntu) Status: Incomplete = Confirmed -- 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/1470580 Title: unprivileged lxc containers fails with custom bridge Status in lxc package in Ubuntu: Confirmed Bug description: Using 15.04 x86_64 with all the updates installed. I'd like 2 containers to communicate with each other via bridge interface. For that I've created interface as follows: /etc/systemd/network/internalbridge1.netdev: [NetDev] Name=ibr1 Kind=bridge /etc/lxc/lxc-usernet: # USERNAME TYPE BRIDGE COUNT x veth ibr1 8 The 'x' is my username, it's first and only user configured in the system so default id map should work fine. The container network is configured as follows: lxc.network.type = veth lxc.network.link = ibr1 lxc.network.flags = up lxc.network.name = internal lxc.network.ipv4 = 10.1.8.2/24 lxc.network.ipv4.gateway = 10.1.8.1 I've enabled the service and brought the bridge up - showing ok via 'ip a' and 'brctl show'. Also works fine with priviledged containers. However with unpriviledged containers it fails: lxc-start -n asterisk -l debug -F --logfile lxc-user.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1470580/+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 1470580] Re: unprivileged lxc containers fails with custom bridge
cat /etc/lxc/lxc-usernet # USERNAME TYPE BRIDGE COUNT x veth ibr1 8 x veth xbr1 8 x veth ubr1 8 cat .local/share/lxc/asterisk/config # Template used to create this container: /usr/share/lxc/templates/lxc-download # Parameters passed to the template: -d ubuntu -r vivid -a amd64 # For additional config options, please look at lxc.container.conf(5) # Distribution configuration lxc.include = /usr/share/lxc/config/ubuntu.common.conf lxc.include = /usr/share/lxc/config/ubuntu.userns.conf lxc.arch = x86_64 # Container specific configuration lxc.include = /etc/lxc/default.conf lxc.id_map = u 0 10 65536 lxc.id_map = g 0 10 65536 lxc.rootfs = /home/x/.local/share/lxc/asterisk/rootfs lxc.utsname = asterisk # Network configuration lxc.network.type = veth lxc.network.link = ubr1 lxc.network.flags = up lxc.network.name = internal #lxc.network.ipv4 = 10.1.8.2/24 #lxc.network.ipv4.gateway = 10.1.8.1 -- 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/1470580 Title: unprivileged lxc containers fails with custom bridge Status in lxc package in Ubuntu: Confirmed Bug description: Using 15.04 x86_64 with all the updates installed. I'd like 2 containers to communicate with each other via bridge interface. For that I've created interface as follows: /etc/systemd/network/internalbridge1.netdev: [NetDev] Name=ibr1 Kind=bridge /etc/lxc/lxc-usernet: # USERNAME TYPE BRIDGE COUNT x veth ibr1 8 The 'x' is my username, it's first and only user configured in the system so default id map should work fine. The container network is configured as follows: lxc.network.type = veth lxc.network.link = ibr1 lxc.network.flags = up lxc.network.name = internal lxc.network.ipv4 = 10.1.8.2/24 lxc.network.ipv4.gateway = 10.1.8.1 I've enabled the service and brought the bridge up - showing ok via 'ip a' and 'brctl show'. Also works fine with priviledged containers. However with unpriviledged containers it fails: lxc-start -n asterisk -l debug -F --logfile lxc-user.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1470580/+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 1471993] [NEW] coredump.conf is missing
Public bug reported: There is no /etc/systemd/coredump.conf, the man page for systemd-coredump and coredumpctl are absent as well in latest ubuntu 15.04 Please put it back - I'd like to configure coredump policy in a way coherent with the rest of the system. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1471993 Title: coredump.conf is missing Status in systemd package in Ubuntu: New Bug description: There is no /etc/systemd/coredump.conf, the man page for systemd-coredump and coredumpctl are absent as well in latest ubuntu 15.04 Please put it back - I'd like to configure coredump policy in a way coherent with the rest of the system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1471993/+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 1470580] Re: unprivileged lxc containers fails with custom bridge
Commenting those 2 lines change nothing - same error. Is there way to figure out what exactly went wrong while creating network? The log seems way too brief about it even with debug enabled. ** Changed in: lxc (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1470580 Title: unprivileged lxc containers fails with custom bridge Status in lxc package in Ubuntu: New Bug description: Using 15.04 x86_64 with all the updates installed. I'd like 2 containers to communicate with each other via bridge interface. For that I've created interface as follows: /etc/systemd/network/internalbridge1.netdev: [NetDev] Name=ibr1 Kind=bridge /etc/lxc/lxc-usernet: # USERNAME TYPE BRIDGE COUNT x veth ibr1 8 The 'x' is my username, it's first and only user configured in the system so default id map should work fine. The container network is configured as follows: lxc.network.type = veth lxc.network.link = ibr1 lxc.network.flags = up lxc.network.name = internal lxc.network.ipv4 = 10.1.8.2/24 lxc.network.ipv4.gateway = 10.1.8.1 I've enabled the service and brought the bridge up - showing ok via 'ip a' and 'brctl show'. Also works fine with priviledged containers. However with unpriviledged containers it fails: lxc-start -n asterisk -l debug -F --logfile lxc-user.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1470580/+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 1470580] [NEW] unprivileged lxc containers fails with custom bridge
Public bug reported: Using 15.04 x86_64 with all the updates installed. I'd like 2 containers to communicate with each other via bridge interface. For that I've created interface as follows: /etc/systemd/network/internalbridge1.netdev: [NetDev] Name=ibr1 Kind=bridge /etc/lxc/lxc-usernet: # USERNAME TYPE BRIDGE COUNT x veth ibr1 8 The 'x' is my username, it's first and only user configured in the system so default id map should work fine. The container network is configured as follows: lxc.network.type = veth lxc.network.link = ibr1 lxc.network.flags = up lxc.network.name = internal lxc.network.ipv4 = 10.1.8.2/24 lxc.network.ipv4.gateway = 10.1.8.1 I've enabled the service and brought the bridge up - showing ok via 'ip a' and 'brctl show'. Also works fine with priviledged containers. However with unpriviledged containers it fails: lxc-start -n asterisk -l debug -F --logfile lxc-user.log ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Attachment added: lxc-user.log https://bugs.launchpad.net/bugs/1470580/+attachment/4423002/+files/lxc-user.log -- 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/1470580 Title: unprivileged lxc containers fails with custom bridge Status in lxc package in Ubuntu: New Bug description: Using 15.04 x86_64 with all the updates installed. I'd like 2 containers to communicate with each other via bridge interface. For that I've created interface as follows: /etc/systemd/network/internalbridge1.netdev: [NetDev] Name=ibr1 Kind=bridge /etc/lxc/lxc-usernet: # USERNAME TYPE BRIDGE COUNT x veth ibr1 8 The 'x' is my username, it's first and only user configured in the system so default id map should work fine. The container network is configured as follows: lxc.network.type = veth lxc.network.link = ibr1 lxc.network.flags = up lxc.network.name = internal lxc.network.ipv4 = 10.1.8.2/24 lxc.network.ipv4.gateway = 10.1.8.1 I've enabled the service and brought the bridge up - showing ok via 'ip a' and 'brctl show'. Also works fine with priviledged containers. However with unpriviledged containers it fails: lxc-start -n asterisk -l debug -F --logfile lxc-user.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1470580/+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 1467611] Re: unprivileged lxc containers broken
I still don't get the point about lsh - I mean what's the difference with openssh? Are there some specific step by ssh server with regards to user session setup necessary? Or some specific system-wide configuration required somewhere? -- 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/1467611 Title: unprivileged lxc containers broken Status in lxc package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Seems like I've hit the bug #1413927 but as requested in comments I'm filing new one. lxc-start -n asterisk -l debug -F --logfile /dev/stdout lxc-start 1434992414.067 INFO lxc_start_ui - lxc_start.c:main:264 - using rcfile /home/x/.local/share/lxc/asterisk/config lxc-start 1434992414.067 INFO lxc_utils - utils.c:get_rundir:483 - XDG_RUNTIME_DIR isn't set in the environment. lxc-start 1434992414.067 WARN lxc_confile - confile.c:config_pivotdir:1768 - lxc.pivotdir is ignored. It will soon become an error. lxc-start 1434992414.069 INFO lxc_confile - confile.c:config_idmap:1376 - read uid map: type u nsid 0 hostid 10 range 65536 lxc-start 1434992414.069 INFO lxc_confile - confile.c:config_idmap:1376 - read uid map: type g nsid 0 hostid 10 range 65536 lxc-start 1434992414.069 WARN lxc_log - log.c:lxc_log_init:316 - lxc_log_init called with log already initialized lxc-start 1434992414.075 WARN lxc_cgmanager - cgmanager.c:cgm_get:963 - do_cgm_get exited with error lxc-start 1434992414.076 WARN lxc_start - start.c:lxc_check_inherited:224 - inherited fd 7 lxc-start 1434992414.076 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - LSM security driver AppArmor lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .reject_force_umount # comment this to allow umount -f; not recommended. lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for reject_force_umount action 0 lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:210 - Setting seccomp rule to reject force umounts lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for reject_force_umount action 0 lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:438 - Adding non-compat rule bc nr1 == nr2 (-1, -1) lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:210 - Setting seccomp rule to reject force umounts lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .[all]. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .kexec_load errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for kexec_load action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for kexec_load action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (283, 246) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .open_by_handle_at errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for open_by_handle_at action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for open_by_handle_at action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (342, 304) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .init_module errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for init_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for init_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (128, 175) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .finit_module errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for finit_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for finit_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp -
[Touch-packages] [Bug 1467611] Re: unprivileged lxc containers broken
cat /proc/self/cgroup 10:cpuset:/system.slice/lsh-server.service 9:memory:/system.slice/lsh-server.service 8:freezer:/system.slice/lsh-server.service 7:blkio:/system.slice/lsh-server.service 6:hugetlb:/system.slice/lsh-server.service 5:perf_event:/system.slice/lsh-server.service 4:cpu,cpuacct:/system.slice/lsh-server.service 3:net_cls,net_prio:/system.slice/lsh-server.service 2:devices:/system.slice/lsh-server.service 1:name=systemd:/system.slice/lsh-server.service ** Changed in: systemd (Ubuntu) Status: Incomplete = Confirmed -- 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/1467611 Title: unprivileged lxc containers broken Status in lxc package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Seems like I've hit the bug #1413927 but as requested in comments I'm filing new one. lxc-start -n asterisk -l debug -F --logfile /dev/stdout lxc-start 1434992414.067 INFO lxc_start_ui - lxc_start.c:main:264 - using rcfile /home/x/.local/share/lxc/asterisk/config lxc-start 1434992414.067 INFO lxc_utils - utils.c:get_rundir:483 - XDG_RUNTIME_DIR isn't set in the environment. lxc-start 1434992414.067 WARN lxc_confile - confile.c:config_pivotdir:1768 - lxc.pivotdir is ignored. It will soon become an error. lxc-start 1434992414.069 INFO lxc_confile - confile.c:config_idmap:1376 - read uid map: type u nsid 0 hostid 10 range 65536 lxc-start 1434992414.069 INFO lxc_confile - confile.c:config_idmap:1376 - read uid map: type g nsid 0 hostid 10 range 65536 lxc-start 1434992414.069 WARN lxc_log - log.c:lxc_log_init:316 - lxc_log_init called with log already initialized lxc-start 1434992414.075 WARN lxc_cgmanager - cgmanager.c:cgm_get:963 - do_cgm_get exited with error lxc-start 1434992414.076 WARN lxc_start - start.c:lxc_check_inherited:224 - inherited fd 7 lxc-start 1434992414.076 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - LSM security driver AppArmor lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .reject_force_umount # comment this to allow umount -f; not recommended. lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for reject_force_umount action 0 lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:210 - Setting seccomp rule to reject force umounts lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for reject_force_umount action 0 lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:438 - Adding non-compat rule bc nr1 == nr2 (-1, -1) lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:210 - Setting seccomp rule to reject force umounts lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .[all]. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .kexec_load errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for kexec_load action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for kexec_load action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (283, 246) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .open_by_handle_at errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for open_by_handle_at action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for open_by_handle_at action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (342, 304) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .init_module errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for init_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for init_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (128, 175) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .finit_module errno 1. lxc-start 1434992414.077 INFO
[Touch-packages] [Bug 1467611] Re: unprivileged lxc containers broken
How does this triggering happens normally? I mean should ssh server call something specific explicitly? -- 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/1467611 Title: unprivileged lxc containers broken Status in lxc package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Seems like I've hit the bug #1413927 but as requested in comments I'm filing new one. lxc-start -n asterisk -l debug -F --logfile /dev/stdout lxc-start 1434992414.067 INFO lxc_start_ui - lxc_start.c:main:264 - using rcfile /home/x/.local/share/lxc/asterisk/config lxc-start 1434992414.067 INFO lxc_utils - utils.c:get_rundir:483 - XDG_RUNTIME_DIR isn't set in the environment. lxc-start 1434992414.067 WARN lxc_confile - confile.c:config_pivotdir:1768 - lxc.pivotdir is ignored. It will soon become an error. lxc-start 1434992414.069 INFO lxc_confile - confile.c:config_idmap:1376 - read uid map: type u nsid 0 hostid 10 range 65536 lxc-start 1434992414.069 INFO lxc_confile - confile.c:config_idmap:1376 - read uid map: type g nsid 0 hostid 10 range 65536 lxc-start 1434992414.069 WARN lxc_log - log.c:lxc_log_init:316 - lxc_log_init called with log already initialized lxc-start 1434992414.075 WARN lxc_cgmanager - cgmanager.c:cgm_get:963 - do_cgm_get exited with error lxc-start 1434992414.076 WARN lxc_start - start.c:lxc_check_inherited:224 - inherited fd 7 lxc-start 1434992414.076 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - LSM security driver AppArmor lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .reject_force_umount # comment this to allow umount -f; not recommended. lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for reject_force_umount action 0 lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:210 - Setting seccomp rule to reject force umounts lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for reject_force_umount action 0 lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:438 - Adding non-compat rule bc nr1 == nr2 (-1, -1) lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:210 - Setting seccomp rule to reject force umounts lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .[all]. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .kexec_load errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for kexec_load action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for kexec_load action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (283, 246) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .open_by_handle_at errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for open_by_handle_at action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for open_by_handle_at action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (342, 304) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .init_module errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for init_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for init_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (128, 175) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .finit_module errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for finit_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for finit_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (350, 313) lxc-start 1434992414.077 INFO lxc_seccomp -
[Touch-packages] [Bug 1467611] Re: unprivileged lxc containers broken
cat /proc/self/cgroups cat: /proc/self/cgroups: No such file or directory Hmm.. what ssh server have to do with this? ** Changed in: systemd (Ubuntu) Status: Incomplete = Confirmed -- 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/1467611 Title: unprivileged lxc containers broken Status in lxc package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Seems like I've hit the bug #1413927 but as requested in comments I'm filing new one. lxc-start -n asterisk -l debug -F --logfile /dev/stdout lxc-start 1434992414.067 INFO lxc_start_ui - lxc_start.c:main:264 - using rcfile /home/x/.local/share/lxc/asterisk/config lxc-start 1434992414.067 INFO lxc_utils - utils.c:get_rundir:483 - XDG_RUNTIME_DIR isn't set in the environment. lxc-start 1434992414.067 WARN lxc_confile - confile.c:config_pivotdir:1768 - lxc.pivotdir is ignored. It will soon become an error. lxc-start 1434992414.069 INFO lxc_confile - confile.c:config_idmap:1376 - read uid map: type u nsid 0 hostid 10 range 65536 lxc-start 1434992414.069 INFO lxc_confile - confile.c:config_idmap:1376 - read uid map: type g nsid 0 hostid 10 range 65536 lxc-start 1434992414.069 WARN lxc_log - log.c:lxc_log_init:316 - lxc_log_init called with log already initialized lxc-start 1434992414.075 WARN lxc_cgmanager - cgmanager.c:cgm_get:963 - do_cgm_get exited with error lxc-start 1434992414.076 WARN lxc_start - start.c:lxc_check_inherited:224 - inherited fd 7 lxc-start 1434992414.076 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - LSM security driver AppArmor lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .reject_force_umount # comment this to allow umount -f; not recommended. lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for reject_force_umount action 0 lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:210 - Setting seccomp rule to reject force umounts lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for reject_force_umount action 0 lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:438 - Adding non-compat rule bc nr1 == nr2 (-1, -1) lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:210 - Setting seccomp rule to reject force umounts lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .[all]. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .kexec_load errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for kexec_load action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for kexec_load action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (283, 246) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .open_by_handle_at errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for open_by_handle_at action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for open_by_handle_at action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (342, 304) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .init_module errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for init_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for init_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (128, 175) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .finit_module errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for finit_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for finit_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat
[Touch-packages] [Bug 1467611] Re: unprivileged lxc containers broken
What is regular user session? Does ssh connection counts or it have to be local console login? ** Changed in: lxc (Ubuntu) Status: Incomplete = New ** Changed in: systemd (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1467611 Title: unprivileged lxc containers broken Status in lxc package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Seems like I've hit the bug #1413927 but as requested in comments I'm filing new one. lxc-start -n asterisk -l debug -F --logfile /dev/stdout lxc-start 1434992414.067 INFO lxc_start_ui - lxc_start.c:main:264 - using rcfile /home/x/.local/share/lxc/asterisk/config lxc-start 1434992414.067 INFO lxc_utils - utils.c:get_rundir:483 - XDG_RUNTIME_DIR isn't set in the environment. lxc-start 1434992414.067 WARN lxc_confile - confile.c:config_pivotdir:1768 - lxc.pivotdir is ignored. It will soon become an error. lxc-start 1434992414.069 INFO lxc_confile - confile.c:config_idmap:1376 - read uid map: type u nsid 0 hostid 10 range 65536 lxc-start 1434992414.069 INFO lxc_confile - confile.c:config_idmap:1376 - read uid map: type g nsid 0 hostid 10 range 65536 lxc-start 1434992414.069 WARN lxc_log - log.c:lxc_log_init:316 - lxc_log_init called with log already initialized lxc-start 1434992414.075 WARN lxc_cgmanager - cgmanager.c:cgm_get:963 - do_cgm_get exited with error lxc-start 1434992414.076 WARN lxc_start - start.c:lxc_check_inherited:224 - inherited fd 7 lxc-start 1434992414.076 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - LSM security driver AppArmor lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .reject_force_umount # comment this to allow umount -f; not recommended. lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for reject_force_umount action 0 lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:210 - Setting seccomp rule to reject force umounts lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for reject_force_umount action 0 lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:438 - Adding non-compat rule bc nr1 == nr2 (-1, -1) lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:210 - Setting seccomp rule to reject force umounts lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .[all]. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .kexec_load errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for kexec_load action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for kexec_load action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (283, 246) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .open_by_handle_at errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for open_by_handle_at action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for open_by_handle_at action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (342, 304) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .init_module errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for init_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for init_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (128, 175) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .finit_module errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for finit_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for finit_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 -
[Touch-packages] [Bug 1413927] Re: user lxc containers fail to start under systemd: login name=systemd cgroup is not owned by user
I've made separate Bug #1467611 as requested. -- 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/1413927 Title: user lxc containers fail to start under systemd: login name=systemd cgroup is not owned by user Status in systemd package in Ubuntu: Fix Released Bug description: When a user logs in, systemd-logind should create cgroups for the user, with the directory (i.e. /user.slice/user-1000.slice/session-c2.scope) owned by the user. This is no longer hapening for the name=systemd cgroup. This prevents containers from starting. (If lxc were to simply not create/use that controller, then it would prevent system in the container from using it). I wanted to test the new lxc with lxcfs. A system container (with upstart or systemd) works perfectly well now (great!), but user containers regressed: $ lxc-create -n v1 -t download -- -d ubuntu -r vivid -a amd64 $ lxc-start -n v1 -F lxc-start: cgmanager.c: lxc_cgmanager_enter: 694 call to cgmanager_move_pid_sync failed: invalid request lxc-start: start.c: __lxc_start: 1099 failed to spawn 'v1' lxc-start: lxc_start.c: main: 345 The container failed to start. My host is running systemd, but cgmanager is running (i. e. it's not bug 1400394, I enabled cgmanager.service). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0~rc1-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 23 10:35:55 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-20 (63 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141119) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx lxc.conf: lxc.lxcpath = /srv/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1413927/+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 1467611] Re: unprivileged lxc containers broken
Btw, cgmanager is started and keep reporting junk which I fail to interpret: systemctl status cgmanager ● cgmanager.service - Cgroup management daemon Loaded: loaded (/lib/systemd/system/cgmanager.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2015-06-22 16:57:30 CEST; 2h 25min ago Main PID: 589 (cgmanager) Memory: 724.0K CGroup: /system.slice/cgmanager.service ‣ 589 /sbin/cgmanager -m name=systemd Jun 22 19:22:39 xnode cgmanager[589]: cgmanager: Invalid path /run/cgmanager/fs/hugetlb/system.slice/lsh-server.service/lxc/asterisk Jun 22 19:22:39 xnode cgmanager[589]: cgmanager:per_ctrl_move_pid_main: Invalid path /run/cgmanager/fs/hugetlb/system.slice/lsh-server.service/lxc/asterisk Jun 22 19:22:39 xnode cgmanager[589]: cgmanager: Invalid path /run/cgmanager/fs/memory/system.slice/lsh-server.service/lxc/asterisk Jun 22 19:22:39 xnode cgmanager[589]: cgmanager:per_ctrl_move_pid_main: Invalid path /run/cgmanager/fs/memory/system.slice/lsh-server.service/lxc/asterisk Jun 22 19:22:39 xnode cgmanager[589]: cgmanager: Invalid path /run/cgmanager/fs/net_cls/system.slice/lsh-server.service/lxc/asterisk Jun 22 19:22:39 xnode cgmanager[589]: cgmanager:per_ctrl_move_pid_main: Invalid path /run/cgmanager/fs/net_cls/system.slice/lsh-server.service/lxc/asterisk Jun 22 19:22:39 xnode cgmanager[589]: cgmanager: Invalid path /run/cgmanager/fs/perf_event/system.slice/lsh-server.service/lxc/asterisk Jun 22 19:22:39 xnode cgmanager[589]: cgmanager:per_ctrl_move_pid_main: Invalid path /run/cgmanager/fs/perf_event/system.slice/lsh-server.service/lxc/asterisk Jun 22 19:22:39 xnode cgmanager[589]: cgmanager: Invalid path /run/cgmanager/fs/none,name=systemd/system.slice/lsh-server.service/lxc/asterisk Jun 22 19:22:39 xnode cgmanager[589]: cgmanager:per_ctrl_move_pid_main: Invalid path /run/cgmanager/fs/none,name=systemd/system.slice/lsh-server.se...c/asterisk Hint: Some lines were ellipsized, use -l to show in full. -- 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/1467611 Title: unprivileged lxc containers broken Status in systemd package in Ubuntu: New Bug description: Seems like I've hit the bug #1413927 but as requested in comments I'm filing new one. lxc-start -n asterisk -l debug -F --logfile /dev/stdout lxc-start 1434992414.067 INFO lxc_start_ui - lxc_start.c:main:264 - using rcfile /home/x/.local/share/lxc/asterisk/config lxc-start 1434992414.067 INFO lxc_utils - utils.c:get_rundir:483 - XDG_RUNTIME_DIR isn't set in the environment. lxc-start 1434992414.067 WARN lxc_confile - confile.c:config_pivotdir:1768 - lxc.pivotdir is ignored. It will soon become an error. lxc-start 1434992414.069 INFO lxc_confile - confile.c:config_idmap:1376 - read uid map: type u nsid 0 hostid 10 range 65536 lxc-start 1434992414.069 INFO lxc_confile - confile.c:config_idmap:1376 - read uid map: type g nsid 0 hostid 10 range 65536 lxc-start 1434992414.069 WARN lxc_log - log.c:lxc_log_init:316 - lxc_log_init called with log already initialized lxc-start 1434992414.075 WARN lxc_cgmanager - cgmanager.c:cgm_get:963 - do_cgm_get exited with error lxc-start 1434992414.076 WARN lxc_start - start.c:lxc_check_inherited:224 - inherited fd 7 lxc-start 1434992414.076 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - LSM security driver AppArmor lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .reject_force_umount # comment this to allow umount -f; not recommended. lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for reject_force_umount action 0 lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:210 - Setting seccomp rule to reject force umounts lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for reject_force_umount action 0 lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:438 - Adding non-compat rule bc nr1 == nr2 (-1, -1) lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:210 - Setting seccomp rule to reject force umounts lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .[all]. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .kexec_load errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for kexec_load action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for kexec_load action 327681
[Touch-packages] [Bug 1467611] Re: unprivileged lxc containers broken
That happens on x86_64 ubuntu 15.04 server btw. All the latest updates installed. -- 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/1467611 Title: unprivileged lxc containers broken Status in systemd package in Ubuntu: New Bug description: Seems like I've hit the bug #1413927 but as requested in comments I'm filing new one. lxc-start -n asterisk -l debug -F --logfile /dev/stdout lxc-start 1434992414.067 INFO lxc_start_ui - lxc_start.c:main:264 - using rcfile /home/x/.local/share/lxc/asterisk/config lxc-start 1434992414.067 INFO lxc_utils - utils.c:get_rundir:483 - XDG_RUNTIME_DIR isn't set in the environment. lxc-start 1434992414.067 WARN lxc_confile - confile.c:config_pivotdir:1768 - lxc.pivotdir is ignored. It will soon become an error. lxc-start 1434992414.069 INFO lxc_confile - confile.c:config_idmap:1376 - read uid map: type u nsid 0 hostid 10 range 65536 lxc-start 1434992414.069 INFO lxc_confile - confile.c:config_idmap:1376 - read uid map: type g nsid 0 hostid 10 range 65536 lxc-start 1434992414.069 WARN lxc_log - log.c:lxc_log_init:316 - lxc_log_init called with log already initialized lxc-start 1434992414.075 WARN lxc_cgmanager - cgmanager.c:cgm_get:963 - do_cgm_get exited with error lxc-start 1434992414.076 WARN lxc_start - start.c:lxc_check_inherited:224 - inherited fd 7 lxc-start 1434992414.076 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - LSM security driver AppArmor lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .reject_force_umount # comment this to allow umount -f; not recommended. lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for reject_force_umount action 0 lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:210 - Setting seccomp rule to reject force umounts lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for reject_force_umount action 0 lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:438 - Adding non-compat rule bc nr1 == nr2 (-1, -1) lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:210 - Setting seccomp rule to reject force umounts lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .[all]. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .kexec_load errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for kexec_load action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for kexec_load action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (283, 246) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .open_by_handle_at errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for open_by_handle_at action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for open_by_handle_at action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (342, 304) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .init_module errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for init_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for init_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (128, 175) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .finit_module errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for finit_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for finit_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (350, 313) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .delete_module errno 1.
[Touch-packages] [Bug 1467611] [NEW] unprivileged lxc containers broken
Public bug reported: Seems like I've hit the bug #1413927 but as requested in comments I'm filing new one. lxc-start -n asterisk -l debug -F --logfile /dev/stdout lxc-start 1434992414.067 INFO lxc_start_ui - lxc_start.c:main:264 - using rcfile /home/x/.local/share/lxc/asterisk/config lxc-start 1434992414.067 INFO lxc_utils - utils.c:get_rundir:483 - XDG_RUNTIME_DIR isn't set in the environment. lxc-start 1434992414.067 WARN lxc_confile - confile.c:config_pivotdir:1768 - lxc.pivotdir is ignored. It will soon become an error. lxc-start 1434992414.069 INFO lxc_confile - confile.c:config_idmap:1376 - read uid map: type u nsid 0 hostid 10 range 65536 lxc-start 1434992414.069 INFO lxc_confile - confile.c:config_idmap:1376 - read uid map: type g nsid 0 hostid 10 range 65536 lxc-start 1434992414.069 WARN lxc_log - log.c:lxc_log_init:316 - lxc_log_init called with log already initialized lxc-start 1434992414.075 WARN lxc_cgmanager - cgmanager.c:cgm_get:963 - do_cgm_get exited with error lxc-start 1434992414.076 WARN lxc_start - start.c:lxc_check_inherited:224 - inherited fd 7 lxc-start 1434992414.076 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - LSM security driver AppArmor lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .reject_force_umount # comment this to allow umount -f; not recommended. lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for reject_force_umount action 0 lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:210 - Setting seccomp rule to reject force umounts lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for reject_force_umount action 0 lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:438 - Adding non-compat rule bc nr1 == nr2 (-1, -1) lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:210 - Setting seccomp rule to reject force umounts lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .[all]. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .kexec_load errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for kexec_load action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for kexec_load action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (283, 246) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .open_by_handle_at errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for open_by_handle_at action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for open_by_handle_at action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (342, 304) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .init_module errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for init_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for init_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (128, 175) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .finit_module errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for finit_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for finit_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (350, 313) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .delete_module errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for delete_module action 327681 lxc-start 1434992414.078 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for delete_module action 327681 lxc-start 1434992414.078 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (129, 176)
[Touch-packages] [Bug 1461274] Re: dependency cycles
Ah, my bad - failed to make a proper unit, will dig deeper into docs. Hopefully upstream issue will get fixed so this would be easier to troubleshoot in future. ** Changed in: systemd (Ubuntu) Status: Incomplete = Invalid -- 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/1461274 Title: dependency cycles Status in systemd package in Ubuntu: Invalid Bug description: There are several dependency cycles reported during the boot of xubuntu 15.04 x86_64: see attached log. Those cycles should be resoled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1461274/+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 583994] Re: Consider replacing ntpdate calls by 'ntpd -g'
Yes, I thought it would be more clear cause I can't change the title of this bug. Once the patch is applied and updated meta-packages pushed both bugs could be safely closed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/583994 Title: Consider replacing ntpdate calls by 'ntpd -g' Status in NTP: Invalid Status in ntp package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Triaged Status in ntp package in Debian: New Bug description: Binary package hint: ntp Given that 'ntpdate' is being obsoleted upstream [1], we should replace 'ntpdate' usage by: * ntpd -qg (if we really want to set the time and exit), or * ntpd-g (if we want to keep ntpd running) the '-q' option will set the clock once, and exit; the 'g' allows for large corrections to the clock, like what is done by 'ntpdate'. [1] http://www.eecis.udel.edu/~mills/ntp/html/ntpdate.html To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/583994/+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 1461274] Re: dependency cycles
Here it is. Is there some systemd command which could check all enabled units for cycles and report them? ** Attachment added: journal.txt https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1461274/+attachment/4409314/+files/journal.txt -- 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/1461274 Title: dependency cycles Status in systemd package in Ubuntu: Incomplete Bug description: There are several dependency cycles reported during the boot of xubuntu 15.04 x86_64: see attached log. Those cycles should be resoled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1461274/+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 1454253] Re: external usb breaks suspend
I thought xfce4-session overrides systemd hybernation? -- 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/1454253 Title: external usb breaks suspend Status in systemd package in Ubuntu: New Bug description: After booting xubuntu 15.04 it's possible to suspend it the normal way BUT - only until you've plugged external usb hard drive. After that (even if it was unmounted and removed) it becomes impossible: the system goes to suspend briefly (for bout 1 second) but immediately wakes up for no apparent reason. I suspect there's some weird bug in xfce power management - is there a way to disable it alltogether and rely on systemd directly instead? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1454253/+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 1461274] [NEW] dependency cycles
Public bug reported: There are several dependency cycles reported during the boot of xubuntu 15.04 x86_64: see attached log. Those cycles should be resoled. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: boot.log https://bugs.launchpad.net/bugs/1461274/+attachment/4408820/+files/boot.log -- 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/1461274 Title: dependency cycles Status in systemd package in Ubuntu: New Bug description: There are several dependency cycles reported during the boot of xubuntu 15.04 x86_64: see attached log. Those cycles should be resoled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1461274/+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 1454253] Re: external usb breaks suspend
echo mem | sudo tee /sys/power/state - that fails the same way as suspending through xfce, dmesg is attached. ** Attachment added: dmesg https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1454253/+attachment/4408837/+files/dmesg ** Changed in: systemd (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1454253 Title: external usb breaks suspend Status in systemd package in Ubuntu: New Bug description: After booting xubuntu 15.04 it's possible to suspend it the normal way BUT - only until you've plugged external usb hard drive. After that (even if it was unmounted and removed) it becomes impossible: the system goes to suspend briefly (for bout 1 second) but immediately wakes up for no apparent reason. I suspect there's some weird bug in xfce power management - is there a way to disable it alltogether and rely on systemd directly instead? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1454253/+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 1459305] [NEW] log to journald by default
Public bug reported: For quite some time now CUPS support structured logging to journald, see http://cyberelk.net/tim/2013/10/25/cups-adding-support-for-system- journal/ With the move to systemd stack it would be beneficial to switch to cups logging to journald by default so the additional information could be stored in structured and secure manner. The only required change is to replace following lines in /etc/cups /cups-files.conf: AccessLog journal ErrorLog journal PageLog journal Users wishing to preserve old behavior with insecure logging would utilize standard dpkg request about configuration change on upgrade. ** 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/1459305 Title: log to journald by default Status in cups package in Ubuntu: New Bug description: For quite some time now CUPS support structured logging to journald, see http://cyberelk.net/tim/2013/10/25/cups-adding-support-for-system- journal/ With the move to systemd stack it would be beneficial to switch to cups logging to journald by default so the additional information could be stored in structured and secure manner. The only required change is to replace following lines in /etc/cups /cups-files.conf: AccessLog journal ErrorLog journal PageLog journal Users wishing to preserve old behavior with insecure logging would utilize standard dpkg request about configuration change on upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1459305/+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 1451247] Re: wrong ntpdate dependency in ubuntu-minimal
I think it should be replaced with systemd-timesynd dependency instead of removing - we still want proper time in the minimal installation, we jsut should use proper tool for that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1451247 Title: wrong ntpdate dependency in ubuntu-minimal Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu-minimal has a hardcoded dependency on ntpdate which is entirely unnecessary because for basic minimal task of syncing time with ntp server systemd-timesyncd is more than enough. Replacing this dependency will allow to save some space on install media and make learning easier for new users because timesyncd follows exact same configuration convention as the rest of the stack which makes it natural to get aquainted with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1451247/+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 1453167] [NEW] replace resolvconf with systemd-resolvd
Public bug reported: For the sake of smoother user experience and easier learning curve would be nice to get rid of legacy resolvconf package and use systemd-resolvd which is nicely integrated with the rest of the stack and uses unified configuration file systax and conventions. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1453167 Title: replace resolvconf with systemd-resolvd Status in ubuntu-meta package in Ubuntu: New Bug description: For the sake of smoother user experience and easier learning curve would be nice to get rid of legacy resolvconf package and use systemd- resolvd which is nicely integrated with the rest of the stack and uses unified configuration file systax and conventions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1453167/+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 391576] Re: smartmontools should be installed on a default system
*** This bug is a duplicate of bug 197881 *** https://bugs.launchpad.net/bugs/197881 ** This bug has been marked a duplicate of bug 197881 Include smart-notifier in Ubuntu by default -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/391576 Title: smartmontools should be installed on a default system Status in ubuntu-meta package in Ubuntu: Confirmed Status in openSUSE: Fix Released Bug description: This is a wish: On a competing proprietary OS, a default installation exploits S.M.A.R.T capabilities of disks to ensure stable disk-usage. I think to fix bug 1, it is necessary to have smartmontools to be installed and activated on default installations (both desktop/laptop and server variants). Before I switched to ubuntu I succeeding in convincing the SuSE people to have that package installed and activated on a default system, see https://bugzilla.novell.com:443/show_bug.cgi?id=201715, further see bug 103681 regarding default activation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/391576/+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 1451098] Re: hardcoded bash dependency
Logon works just fine just thought that this dependency is very odd. Ironically the bug you're referring to was introduced exactly by some bashism dropped into place where it did not belong to. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1451098 Title: hardcoded bash dependency Status in lightdm package in Ubuntu: Incomplete Bug description: lightdm has hardcoded dependency on bash (= 4.3) which is very strange - I expect DM to work regardless of which shell is installed in my system. The dependency should be changed to dash and all the bashisms in source code (if any) should be eliminated to improve portability. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1451098/+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 583994] Re: Consider replacing ntpdate calls by 'ntpd -g'
It would be much better to replace it with systemd-timesyncd calls and drop ntpdate dependency altogether. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/583994 Title: Consider replacing ntpdate calls by 'ntpd -g' Status in NTP: Invalid Status in ntp package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Triaged Status in ntp package in Debian: New Bug description: Binary package hint: ntp Given that 'ntpdate' is being obsoleted upstream [1], we should replace 'ntpdate' usage by: * ntpd -qg (if we really want to set the time and exit), or * ntpd-g (if we want to keep ntpd running) the '-q' option will set the clock once, and exit; the 'g' allows for large corrections to the clock, like what is done by 'ntpdate'. [1] http://www.eecis.udel.edu/~mills/ntp/html/ntpdate.html To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/583994/+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 1451102] Re: upstart user sessions needs replacement
Note: systemd --user is started by default anyway but in addition to it there are still some upstart leftovers hanging around which is highly confusing for users and is a maintenance hell in a long run. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1451102 Title: upstart user sessions needs replacement Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: While the system init now works much faster, more reliable and maintainable the user session is still a mess. Would be great to git rid of upstart in here as well or at least document workaround which would allow to manually disable upstart for user sessions and replace it with systemd units. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1451102/+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 1451247] [NEW] wrong ntpdate dependency in ubuntu-minimal
Public bug reported: Ubuntu-minimal has a hardcoded dependency on ntpdate which is entirely unnecessary because for basic minimal task of syncing time with ntp server systemd-timesyncd is more than enough. Replacing this dependency will allow to save some space on install media and make learning easier for new users because timesyncd follows exact same configuration convention as the rest of the stack which makes it natural to get aquainted with. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1451247 Title: wrong ntpdate dependency in ubuntu-minimal Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu-minimal has a hardcoded dependency on ntpdate which is entirely unnecessary because for basic minimal task of syncing time with ntp server systemd-timesyncd is more than enough. Replacing this dependency will allow to save some space on install media and make learning easier for new users because timesyncd follows exact same configuration convention as the rest of the stack which makes it natural to get aquainted with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1451247/+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 1451102] [NEW] upstart user sessions needs replacement
Public bug reported: While the system init now works much faster, more reliable and maintainable the user session is still a mess. Would be great to git rid of upstart in here as well or at least document workaround which would allow to manually disable upstart for user sessions and replace it with systemd units. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1451102 Title: upstart user sessions needs replacement Status in ubuntu-meta package in Ubuntu: New Bug description: While the system init now works much faster, more reliable and maintainable the user session is still a mess. Would be great to git rid of upstart in here as well or at least document workaround which would allow to manually disable upstart for user sessions and replace it with systemd units. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1451102/+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 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
Is there some detailed notes on why upstart is still used for user sessions instead of systemd? Is it just lack of time or there are some technical reasons not to switch to systemd here as well? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in init-system-helpers package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in init-system-helpers source package in Vivid: Fix Released Status in ubuntu-meta source package in Vivid: Fix Released Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+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 1399766] Re: ubuntu-minimal should depend on either upstart or systemd
*** This bug is a duplicate of bug 1427654 *** https://bugs.launchpad.net/bugs/1427654 Questions and flamewars belong to forums not to bug tracker. ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed = Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/ubuntu-meta/+question/266323 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1399766 Title: ubuntu-minimal should depend on either upstart or systemd Status in ubuntu-meta package in Ubuntu: Invalid Bug description: It seems to me, that ubuntu-minimal metapackage should depend on either systemd or upstart, because both of them are completely usable, but now if I remove upstart, ubuntu-miminal is also removed and it can cause some problems with packages to be autoremoved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1399766/+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 1451098] [NEW] hardcoded bash dependency
Public bug reported: lightdm has hardcoded dependency on bash (= 4.3) which is very strange - I expect DM to work regardless of which shell is installed in my system. The dependency should be changed to dash and all the bashisms in source code (if any) should be eliminated to improve portability. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1451098 Title: hardcoded bash dependency Status in lightdm package in Ubuntu: New Bug description: lightdm has hardcoded dependency on bash (= 4.3) which is very strange - I expect DM to work regardless of which shell is installed in my system. The dependency should be changed to dash and all the bashisms in source code (if any) should be eliminated to improve portability. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1451098/+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 1451103] [NEW] ubuntu-standard depends on cron
Public bug reported: ubuntu-standard have a hardcoded dependency on cron package. Instead it should depend on systemd-cron to decrease learning curve for new users and simplify system maintenance: it's much easier if periodic tasks are administered the same way as all other tasks - via standard units. People who need legacy software for some reason could easily install it from the repository. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1451103 Title: ubuntu-standard depends on cron Status in ubuntu-meta package in Ubuntu: New Bug description: ubuntu-standard have a hardcoded dependency on cron package. Instead it should depend on systemd-cron to decrease learning curve for new users and simplify system maintenance: it's much easier if periodic tasks are administered the same way as all other tasks - via standard units. People who need legacy software for some reason could easily install it from the repository. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1451103/+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 1429938] Re: reboot does not return under systemd
I think mentioning this bug in release notes would only confuse users: the bug here is in the person who relied on undocumented racy behavior - this have nothing to do with systemd or ubuntu or sshd. -- 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/1429938 Title: reboot does not return under systemd Status in systemd package in Ubuntu: Invalid Bug description: If you send a shutdown or reboot command over SSH to a Trusty or Utopic host, the command will consistently finish successfully prior to the SSH connection being closed, meaning your SSH client will exit with a return-code of zero: For example: $ ssh root@myhost shutdown -h now $ echo $? 0 Or $ ssh root@myhost reboot $ echo $? 0 However, on Vivid now that the switch-over to systemd has happened, running the same consistently results in the abrupt closure of the SSH connection prior to the command finishing, meaning your SSH client will exit with a return-code of 255: $ ssh root@my_vivid_host shutdown -h now Connection to localhost closed by remote host. $ echo $? 255 Although in retrospect is was a bit naive for me to rely on this (actually quite fragile) behavior, it had at least been consistent in Ubuntu for some time (back to at least Raring from my personal experience, but likely back even farther). This isn't technically a systemd bug, but I still think it's something worth mentioning in the release notes as I bet I'm not the only person who built some clever hacks around the previous behavior :P To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1429938/+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 1289047] Re: [Trusty] hostapd package is broken
So what's the proper workaround for 14.04 to automatically start hostapd on boot? Do I have to put smth into /etc/network/interfaces? Or disable interface in NetworkManager.conf? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1289047 Title: [Trusty] hostapd package is broken Status in One Hundred Papercuts: Triaged Status in wpa package in Ubuntu: Triaged Bug description: When trying to create an access point, I am met with a fatal error with hostapd: nl80211: Could not configure driver mode nl80211 driver initialization failed. hostapd_free_hapd_data: Interface wlan0 wasn't started What worked before no longer works today after a package upgrade. After installing hostapd deb from Ubuntu 13.10, it works. WORKAROUND: For this to persist through reboots, execute the following in a terminal: sudo nano /etc/NetworkManager/NetworkManager.conf Add the following entry where the x's are replaced with your WiFi MAC address, save, and then reboot: [keyfile] unmanaged-devices=mac:xx:xx:xx:xx:xx:xx ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: hostapd 1:2.1-0ubuntu1 Uname: Linux 3.14.0-031400rc5-lowlatency x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Thu Mar 6 16:57:20 2014 InstallationDate: Installed on 2014-02-01 (33 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140121.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 LANGUAGE=en_CA:en SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1289047/+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
