** Package changed: ubuntu = systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Importance: High = Medium
** Changed in: systemd (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in
** Changed in: systemd (Ubuntu)
Milestone: None = ubuntu-15.04
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
** Package changed: systemd (Ubuntu) = ifupdown (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs
It's very unlikely that this is related to systemd, as it's got nothing
at all to do with handling the user session and screen locking. This is
handled by unity. The most probable reason is that unity crashes when
it's trying to lock the screen. When this happens, do you get a crash
notification?
: Martin Pitt (pitti)
Status: Triaged
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
** Changed in: systemd (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
in: systemd (Ubuntu Vivid)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/953875
Title:
Encrypted swap no longer mounted at bootup
I fixed this upstream at
http://cgit.freedesktop.org/systemd/systemd/commit/?id=0e336347
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New = Fix Committed
** Also affects: udev (Ubuntu Precise)
Importance:
I suppose that merely reintroducing the Type=oneshot will make things
work again?
However, I don't really understand this yet. ifup@.service should have
nothing to do with how network-online.target behaves. For the record,
the design of this is as follows:
* ifup@.service should not be
** Package changed: systemd (Ubuntu) = colord (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1442050
Title:
(colord:832): Cd-WARNING **: failed to get session [pid 690]:
Network devices come and go, some are hotpluggable, some have
killswitches, etc. There is no such concept as wait for all network
devices to be present. NetworkManager listens to uevents and can handle
appearing and disappearing network interfaces just fine.
If that doesn't work for a particular
them (i. e. use 1.2.3.4...).
It's best to avoid those at all and use forward slashes for CIFS mounts.
** Changed in: systemd (Ubuntu)
Status: Triaged = Invalid
** Changed in: systemd (Ubuntu)
Assignee: Martin Pitt (pitti) = (unassigned)
--
You received this bug notification
*** This bug is a duplicate of bug 1439109 ***
https://bugs.launchpad.net/bugs/1439109
** This bug is no longer a duplicate of bug 1430675
fails to set up a bridged network interface
** This bug has been marked a duplicate of bug 1439109
Network interface not coming up due to missing
** Changed in: initramfs-tools (Ubuntu)
Status: New = In Progress
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided = High
** Tags added: systemd-boot
--
You received this bug
Shouldn't this rather be sudo update-rc.d networking defaults? That
won't actually put back a removed symlink as this counts as user change
that needs to be preserved. So the question is still what made this
disappear?
** No longer affects: systemd (Ubuntu)
** Tags added: systemd-boot
--
You
*** This bug is a duplicate of bug 1431107 ***
https://bugs.launchpad.net/bugs/1431107
** This bug has been marked a duplicate of bug 1431107
ordering cycles with lvm2 init script with inappropriate rc2.d links
--
You received this bug notification because you are a member of Ubuntu
Thanks for your report! Unfortunately the auto-generated stack trace is
totally useless, so I'm afraid there's not much that we can do with this
report; thus I'm closing it. Let's hope the next one looks better :-)
** Changed in: systemd (Ubuntu)
Status: New = Invalid
--
You received
The kernel log shows huge gaps in device detection, apparently the
hardware gets locked up during USB detection/enumeration?
[7.292422] input: HDA Intel HDMI HDMI/DP,pcm=7 as
/devices/pci:00/:00:03.0/sound/card0/input16
[ 10.918992] usb 1-3: device descriptor read/all, error -110
[
There has been no answer to the request for information above for a
month. I'm closing this bug report as in its current form it is not
actionable. I'll reopen this once that information has been provided.
Thank you for your report!
** Changed in: systemd (Ubuntu)
Status: Incomplete =
There has been no answer to the request for information above for a
month. I'm closing this bug report as in its current form it is not
actionable. I'll reopen this once that information has been provided.
Thank you for your report!
** Changed in: systemd (Ubuntu)
Status: Incomplete =
*** This bug is a duplicate of bug 1433198 ***
https://bugs.launchpad.net/bugs/1433198
** This bug has been marked a duplicate of bug 1433198
15.04 daily images don't reach X using VirtualBox - VESA error: Cannot read
int vect
--
You received this bug notification because you are a
Thanks for confirming. Tentatively closing for now. If anyone still sees
this, please yell.
** Changed in: systemd (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
Fixed both dependencies in http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=experimentalid=dd2f43c5bcb
** No longer affects: ifupdown (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a
Vivid switched to systemd, so this isn't a problem there any more. I
added an open utopic task, as that's still affected.
** Also affects: systemd (Ubuntu Utopic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Utopic)
Status: New = Triaged
** Changed in:
Originally this sounded like a duplicate of bug 1431200, as that's
pretty much the only point in time when an upgrade of the systemd
package could even remotely trigger a graphics state change, by
accidentally reloading/restarting some units like plymouth. But you said
that this happens on
Oh wait -- you are saying that the external monitor does not receive a
signal at any point in time? I thought the external monitor would stop
working *during/after* running dist-upgrade, and start working again
after a reboot.
That sounds like a kernel/video driver/X.org regression then,
bumblebeed itself fails in the modprobe call, so reassigning back for
now. This could also belong to kmod, but let's find out what's wrong
first. What does that command say?
grep -r off /etc/mod*
My suspicion is that there is some alias whatever off in
/etc/modprobe.d which bumblebee tries to
Do you actually have any remote file systems (NFS, cifs, etc.) in your
/etc/fstab?
systemctl list-dependencies systemd-user-sessions.service |grep remote
I don't have remote file systems, and this doesn't give any output for
me. Does it for you? Can you please also give me the output of
/etc/init/network-interface-security.conf is in ifupdown, so let's put
the corresponding system unit there, too.
** Package changed: systemd (Ubuntu) = ifupdown (Ubuntu)
** Tags added: systemd-boot
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
So at the moment, apparmor starts After=local-fs.target and
Before=sysinit.target.
network-interface-security.conf does:
start on (starting network-interface or starting network-manager or
starting networking)
network-interface corresponds to ifup@.service, networking is just the
ifupdown
It's already tagged systemd-boot, which is enough to make it appear on
our radar (https://bugs.launchpad.net/ubuntu/+bugs?field.tag=systemd-
boot)
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Thanks for confirming! Closing then.
** Changed in: systemd (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1435126
Title:
slow
*** This bug is a duplicate of bug 1432821 ***
https://bugs.launchpad.net/bugs/1432821
Judging by the /run/network/.ifstate.lock: No such file or directory
this is almost surely a duplicate, so marking as such.
** This bug has been marked a duplicate of bug 1432821
something deleting
This is an expected warning.
** Changed in: systemd (Ubuntu)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1422070
Title:
That's the error:
Setting up python-gi (3.14.0-1) ...
Traceback (most recent call last):
File /usr/bin/pycompile, line 35, in module
from debpython.version import SUPPORTED, debsorted, vrepr, \
File /usr/share/python/debpython/version.py, line 24, in module
from ConfigParser import
I just applied all v219-stable patches on top of our package, and
dropped the reverted patch. I now get the boot failures again, so I'm
afraid that wasn't it.
** Also affects: systemd (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1201964
Importance: Unknown
Status: Unknown
I think this overcomplicates things a lot. I see three options here:
1) My impression is that we don't actually care about persistant
interface names on the phone. Therefore, phone image builds could just
create/ship an empty /etc/udev/rules.d/75-persistent-net-generator.rules
which will disable
Confirmed on current snappy-devel.
** Changed in: systemd (Ubuntu)
Status: New = Triaged
** Summary changed:
- systemd-analyze plot not plotting appropriately
+ [snappy] systemd-analyze plot not plotting appropriately
** Also affects: snappy-ubuntu
Importance: Undecided
** Tags added: systemd-boot
** Package changed: systemd (Ubuntu) = network-manager (Ubuntu)
** Summary changed:
- a stop job is running for network manager on reboot
+ stopping network-manager takes several seconds
** Changed in: network-manager (Ubuntu)
Importance: Undecided = Low
--
You
Your system generally isn't the fastest, so there aren't many obvious
gaps, except this blatant one:
bře 18 17:57:26 P-IV ntpd[1174]: Listening on routing socket on fd #22 for
interface updates
bře 18 17:58:00 P-IV systemd-journal[268]: Forwarding to syslog missed 50
messages.
bře 18 17:58:47
Hm, your journal doesn't seem to contain an attempt to suspend, so this
might have been blocked by the upper layers. As you said that suspend
works correctly with the indicator menu, this looks like a bug with
unity-system-settings.
** Package changed: systemd (Ubuntu) = unity-settings-daemon
Thanks Scott for fixing this! However, this is awkward to have in
systemd: it meddles with ifupdown's and open-iscsi's internals and has
open-iscsi specific knowledge which really belongs into open-iscsi
itself. I. e. open-iscsi should ship the counterpart of debian/open-
You can build that using libsystemd-login-dev, they provide
compatibility shims for the obsolete libsystemd-logind0 (and similar)
libraries.
** Changed in: systemd (Ubuntu)
Status: New = Won't Fix
** Changed in: systemd (Ubuntu)
Status: Won't Fix = Invalid
--
You received this
That sounds like https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=779612 . Do you use plymouth, i. e. do you see the
graphical sphash screen and boot with splash? Your CurrentDmesg.txt
suggests that you aren't. Can you please try with that?
** Summary changed:
- after the upstart replacement
systemd has nothing at all to do with what happens on the keypresses.
udev only adjusts the kernel's keymaps during boot. But at runtime, the
keypresses are handled by the kernel, sent through /dev/input/* as evdev
events, and read by *-settings-daemon or other programs. So tentatively
assigning
Updating status for vivid tentatively, until the kernel team can
comment.
** Changed in: systemd (Ubuntu)
Status: Incomplete = Won't Fix
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Since we don't ship any ZFS support package in Ubuntu I suppose you are
using the upstream PPA. The bug report for that is logged at
https://github.com/zfsonlinux/pkg-zfs/issues/145, so closing this one.
Thanks!
** Changed in: systemd (Ubuntu)
Status: Confirmed = Invalid
** Package
This only works if you enable the persistant journal, see
/usr/share/doc/systemd/README.Debian . Otherwise the journal is kept in
memory and only applies to the current boot.
** Changed in: systemd (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a
So the sddm not enabled issue is a but in sddm, and the root
partition missing from /etc/fstab was a local problem. Hence I think
this can be closed.
** This bug is no longer a duplicate of bug 1432171
[udev] Shows starting version 219 boot message even with quiet
** Changed in: systemd
https://launchpad.net/ubuntu/+source/ubuntu-touch-meta/1.217
** Changed in: ubuntu-touch-meta (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
Indeed, thanks for the logs and your patience!
Mar 13 16:19:26 tigger systemd[1]: Stopped Network Manager.
Mar 13 16:19:28 tigger systemd[1]: Stopped target Remote File Systems.
Mar 13 16:19:28 tigger systemd[1]: Stopping Remote File Systems.
Mar 13 16:19:28 tigger systemd[1]: Unmounting
Ah, this is snappy, this explains all the errors about read-only
directories.
In the with ethernet case, boot started at 19:00:44, and eth0 DHCP is
done at 19:00:57, so 13 s. Then it spends half a minute or so in cloud-
init and click hooks, so that's not systemd's fault. So I consider the
with
: Debian Bug tracker #779606
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779606
** Also affects: systemd (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779606
Importance: Unknown
Status: Unknown
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) = Martin
You should have some unit usb_modeswitch@something.service in
systemctl --all | grep usb_modeswitch
When you have a boot where it was *not* enabled automatically, can you
please get me the output of
systemctl status -l usb_modeswitch@something.service
?
Note keeping for myself:
*** This bug is a duplicate of bug 1429544 ***
https://bugs.launchpad.net/bugs/1429544
** This bug is no longer a duplicate of bug 1363020
systemd-logind crashed with assertion failure in bus_manager_create_session()
** This bug has been marked a duplicate of bug 1429544
systemd-logind
*** This bug is a duplicate of bug 1429544 ***
https://bugs.launchpad.net/bugs/1429544
** This bug is no longer a duplicate of bug 1363020
systemd-logind crashed with assertion failure in bus_manager_create_session()
** This bug has been marked a duplicate of bug 1429544
systemd-logind
*** This bug is a duplicate of bug 1429544 ***
https://bugs.launchpad.net/bugs/1429544
** This bug is no longer a duplicate of bug 1363020
systemd-logind crashed with assertion failure in bus_manager_create_session()
** This bug has been marked a duplicate of bug 1429544
systemd-logind
Ah right, that makes more sense. By definition, shutdown -h now or
poweroff etc. are racy -- sometimes it survives and comes back,
sometimes the shutdown of the machine is too fast. It seems that with
systemd it's just a bit faster. I suggest calling shutdown -h +1, or
if you don't want to wait
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
** Changed in: upstart (Ubuntu)
Importance: Undecided = Critical
** Description changed:
I've today had two machines kill my X session during dist-upgrade, and
it happened during libc6 postinst. Dmesg shows
As of yesterday in vivid, this is now correct, as we switched to systemd
as init :-)
** Changed in: systemd (Ubuntu)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
This also affects /etc/init.d/postgresql stop, in degraded mode this
won't stop all the bound postgresql@.service instances.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
** Changed
This is reproducible with a default use full disk and encrypt my home
dir installation. This produces that kind of crypttab which apparently
never initializes the cryptswap partition. blkid -p on that partition is
empty, there is no LUKS file system on it. I'm not sure about the role
of UUID for a
Leaving a cryptsetup task, as somehow we need to clean up after that for
existing installations. (This might end up in a different package too)
** Package changed: systemd (Ubuntu) = cryptsetup (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
** Changed in: systemd (Ubuntu)
Status: Confirmed = Invalid
** Changed in: openssh (Ubuntu)
Status: Confirmed = In Progress
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
That looks like a crash in python-wxgtk2.8
** Package changed: pygobject (Ubuntu) = wxwidgets2.8 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1366291
Title:
** Summary changed:
- python2.7 crashed with SIGABRT in g_assertion_message()
+ ubuntu-after-install.py assertion failure: (gtk_widget_get_parent (child) ==
GTK_WIDGET (container))
** Package changed: pygobject (Ubuntu) = gtk+3.0 (Ubuntu)
--
You received this bug notification because you are
That's ok. It's a debug message from src/core/unit.c for the .service
files which are going to be created by the sysv-generator. They won't
appear without debug.
** Changed in: systemd (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
This looks related, were you trying to look at an iso? It sounds a bit
like you were trying to look at an ISO which got loop-mounted, then
tracker jumped at it, and tried to unmount it again?
Feb 14 22:39:23 duhast gnome-session[6392]: (tracker-extract:6756):
libmediaart-WARNING **: Unmount
I'm afraid we don't have any duplicates about that, and there's nothing
to go on here, so I'm closing this. Thanks for your report!
** Changed in: systemd (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1428811
Title:
Trusty hwe kernel (utopic) gpio
** Package changed: systemd (Ubuntu) = systemd-shim (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1426362
Title:
logind session files fill up /run space
To manage
Reassigning to X.org's evdev driver then. If evtest gets the correct
events, then kernel, keymaps, and evdev are alright, but it seems the
press events somehow get lost in X.org's input driver.
** Package changed: systemd (Ubuntu) = xserver-xorg-input-evdev
(Ubuntu)
--
You received this bug
That's just an (expected) debug message. It won't appear if you boot
without debug. Please don't regularly boot with debug, it'll only
slow down your system noticeably and inflate the logs.
** Changed in: systemd (Ubuntu)
Status: New = Invalid
--
You received this bug notification
Can you please show me the output of
systemctl status -l ureadahead.service
?
** Package changed: systemd (Ubuntu) = ureadahead (Ubuntu)
** Changed in: ureadahead (Ubuntu)
Status: New = Incomplete
** Project changed: systemd = null-and-void
** Changed in: null-and-void
it doesn't recognize that it already has a match, and applies the
second rule anyway.
** Affects: systemd (Ubuntu)
Importance: High
Assignee: Martin Pitt (pitti)
Status: In Progress
** Description changed:
With latest systemd we now get wrong permissions on /var/log when
That's a kernel regression, I'm afraid. They all map to the same scan
code now, so userspace cannot tell them apart any more.
** Package changed: systemd (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Also affects: systemd
Importance: Undecided
Status: New
** Changed in: systemd
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https
: (unassigned) = Martin Pitt (pitti)
** Changed in: systemd (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1424992
Title:
files in /tmp
** Bug watch added: Debian Bug tracker #778970
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778970
** Also affects: systemd (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778970
Importance: Unknown
Status: Unknown
--
You received this bug notification because
For the record, the chroot is done here:
# Work around absolute symlinks
if [ -d ${rootmnt} ] [ -h ${rootmnt}${checktarget} ]; then
case $(readlink ${rootmnt}${checktarget}) in /*)
checktarget=$(chroot ${rootmnt} readlink
${checktarget})
:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2324CTO
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO
** Affects: systemd (Ubuntu)
Importance: Critical
Assignee: Martin Pitt (pitti)
Status
No, this won't be backported. This is a classic bug fix for stable-
updates, I'll prepare uploads soon.
** Also affects: udev (Ubuntu)
Importance: Undecided
Status: New
** Also affects: udev (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: udisks (Ubuntu
Yes, I know, but -10 isn't in vivid yet; this bug will be auto-closed
once it migrates from vivid-proposed.
** Changed in: systemd (Ubuntu)
Status: Fix Released = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
in: systemd (Ubuntu)
Status: New = In Progress
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1421058
** Package changed: systemd (Ubuntu) = rtkit (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1421560
Title:
[/lib/systemd/system/rtkit-daemon.service:32] Unknown lvalue
reverts that during shutdown.
** Also affects: lxcfs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lxcfs (Ubuntu)
Importance: Undecided = High
** Changed in: lxcfs (Ubuntu)
Status: New = Triaged
** Changed in: lxcfs (Ubuntu)
Assignee: (unassigned) = Martin
@Patrick: That's why:
IMPORT 'udisks-part-id /dev/mmcblk0rpmb' /lib/udev/rules.d/80-udisks.rules:84
starting 'udisks-part-id /dev/mmcblk0rpmb'
'udisks-part-id /dev/mmcblk0rpmb' [10806] exit with return code 0
Apparently you still have the old udisks 1.x installed; can you try
sudo dpkg -P
The updated udev rule is of course fine for an SRU. Marked for trusty
for now, please add more releases as desired. Keeping the linux task for
vivid onwards to change the default in the virtio kernel driver itself
(pending feedback from the kernel team).
** Package changed: ubuntu = linux
The symlink warning is unrelated, it's just cosmetical.
timedated is not an NTP service; it's not supposed to keep the time
synchronized. That's either done by ntpdate (which is installed by
default on desktops) or ntp (which you can install yourself).
timedatectl only does one-time time
http://cgit.freedesktop.org/systemd/systemd/commit/?id=4b9bb683
** Package changed: linux (Ubuntu) = systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: Incomplete = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
http://cgit.freedesktop.org/systemd/systemd/commit/?id=4b9bb683
** Package changed: linux (Ubuntu) = systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
As you see in status, the actual name of that is ssh.service, and
sshd is just an Alias= name. As several units can have the same alias
(e. g. in the case of display-manager.service), it is deliberate that
you cannot enable aliases, but have to use the actual service name.
** Summary changed:
-
) = Martin Pitt (pitti)
** Bug watch added: Debian Bug tracker #777115
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777115
** Also affects: systemd (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777115
Importance: Unknown
Status: Unknown
--
You received this bug
)
Status: In Progress = Triaged
** Changed in: samba (Ubuntu)
Assignee: Martin Pitt (pitti) = (unassigned)
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
(Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1417010
Title:
systemd init gets stuck reloading smbd.service
To manage
Indeed I suppose that Tong is running upstart (which is the default and
ONLY supported init system in Ubuntu 14.10). Under systemd it works
fine, so I close the bug for now. If Tong confirms he's actually running
systemd I'll reopen and investigate. Thanks!
** Changed in: systemd (Ubuntu)
Which Ubuntu release and kernel version does that apply to? Please send
the uname -a output. Testing this under the current vivid kernel (3.18)
would be very much appreciated. Thanks!
** Package changed: udev (Ubuntu) = systemd (Ubuntu)
--
You received this bug notification because you are a
This is fixed in Ubuntu Vivid (and systemd/journal are not supported in
14.10 anyway).
** Changed in: systemd (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
OK, unduplicating then. As cdrom_id is okay, I'm moving this one level
up so far. When that happens, can you please copypaste the output of
udisksctl info -b /dev/sr0 here? Thanks!
** This bug is no longer a duplicate of bug 1168742
[udev] Disks are not unmounted when physical eject button is
) = Martin Pitt (pitti)
** Changed in: systemd (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1168742
Title:
[udev] Disks
There is no robust way how udisks could do this, but on the upstream
systemd list we discussed how to do this cleanup under systemd. For udev
under upstart there is a hack to call eject instead of cdrom_id
--eject in the udev rule for the eject request, but this relies on udev
not running under an
Sorry, misunderstanding. I restored the previous tags, which seem to be
correct.
** Tags removed: verification-done
** Tags added: verification-done-trusty verification-needed-utopic
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
701 - 800 of 7748 matches
Mail list logo
