Public bug reported:
Description of the problem
It appears that cron will go on to crash if it finds a crontab owned by uid who
does not map to a valid user.
Steps to reproduce:
1. Create a crontab with an Active Directory user set up via SSSD?
2. Switch AD domains so user's uid is entirely
Wild guess: this might be because you have only one network interface
that is set to use DHCP but the DHCP server is set not to return any
routers. See https://github.com/systemd/systemd/issues/3752 for this
type of scenario.
** Bug watch added: github.com/systemd/systemd/issues #3752
Attach patch to solve PMP attached device persistent naming
** Patch added: "ee26c33ede684138ba9fdc7f286bfa402860aff3.patch"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1611945/+attachment/4874796/+files/ee26c33ede684138ba9fdc7f286bfa402860aff3.patch
--
You received this bug
@zbyszek-in: would you be willing to take patches that upstream refuse?
There's a fix for this via
https://github.com/sitsofe/systemd/commit/ee26c33ede684138ba9fdc7f286bfa402860aff3
but upstream have a clear "no more changes will ever be made to systemd
provided storage udev rules" rule :
I should also note 14.04 live CDs are also available:
http://releases.ubuntu.com/14.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/1611945
Title:
/dev/disk/by-path
I thought everything in /sys was built by udev rules? If so any path
changes could be down to changes there rather than in the kernel.
http://cdimage.ubuntu.com/daily-live/20160811/ is likely a new yaketty
build but use at your own risk etc.
--
You received this bug notification because you are
A quick search digs up that the path is created by this:
https://github.com/systemd/systemd/blob/09541e49ebd17b41482e447dd8194942f39788c0/src/udev/udev-builtin-path_id.c#L349
. This code in that region was added in
I guess it would also be good to have the same output for different disk
in the same enclosure...
--
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/1611945
Title:
Chris:
Could you attach the output of
sudo udevadm test /sys/class/block/sda
?
--
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/1611945
Title:
/dev/disk/by-path not
Just a quick note: using
sudo -s
or
su -
before using service will work around the issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1605290
Title:
Please add
Adding patch that always uses the system upstart session.
** Patch added: "initctl-system.patch"
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1605290/+attachment/4704733/+files/initctl-system.patch
--
You received this bug notification because you are a member of Ubuntu
Touch
Public bug reported:
Description of the problem:
If the user is using the service command they are almost certainly trying to
control system daemons but can wind up looking at only user session daemons.
Steps to reproduce:
1. Install KUbuntu 14.04.
2. Graphically log in as a regular user.
3.
Further investigation on what I was seeing showed this to be a race
between X starting and the intel i915 graphics kernel module being
loaded (because it's not built into the kernel).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I've just seen this on Ubuntu 16.04 on an EeePC and in one start up
configuration it always happens and autologin always fails.
It seems to be highly dependent on what else is happening as lightdm is
starting. When the problem occurs looking at the lightdm log shows that
it is trying to log using
** Attachment added: "auth.log"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1250875/+attachment/4645857/+files/auth.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
** Attachment added: "lightdm.log"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1250875/+attachment/4645856/+files/lightdm.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
Changing component to cups-filters.
** Package changed: lsb (Ubuntu) => cups-filters (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lsb in Ubuntu.
https://bugs.launchpad.net/bugs/1573893
Title:
Can't use Epson
Till: Could you undo fixed released on cups-filters? It looks like the
cups-filters-lsb has already been deleted
(http://www.ubuntuupdates.org/package/core/xenial/main/base/cups-
filters-lsb ) but the epson debs still depend on lsb which doesn't
exist.
--
You received this bug notification
Looking closer this sounds like a duplicate of bug #1536353 ...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lsb in Ubuntu.
https://bugs.launchpad.net/bugs/1573893
Title:
Can't use Epson XP-310 printer with 16.04 no lsb
Changing component. I'm also seeing this on 16.04 trying to use a
WF-3520 printer - it learns about the epson-inkjet-printer-201212w deb
from Epson but the deb can't be installed because xenial no longer has
an lsb package:
# apt-get install epson-inkjet-printer-201212w
Reading package lists...
Chris Leach started posted patches that would fix some of what is needed
to support this on open-iscsi mailing list
(https://groups.google.com/d/msg/open-iscsi/vWbi_LTMEeM/P8-oUDkb14YJ )
but they stalled and are incomplete (https://groups.google.com/d/msg
/open-iscsi/kgjck_GixsM/U_FqTbYhCgAJ ).
21 matches
Mail list logo
