** Changed in: sysvinit (Ubuntu Wily)
Status: In Progress => Fix Committed
--
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/1456670
Title:
debootstrap failure: insse
Applied upstream, thanks Marc!
** Changed in: upower (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1449051
Title:
Upower does
This was applied upstream a while ago:
http://cgit.freedesktop.org/upower/commit/?id=f8104a112eb
** No longer affects: gnome-power-manager (Ubuntu)
** Changed in: upower (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
T
** No longer affects: upower (Ubuntu)
** No longer affects: libgpod (Ubuntu)
** No longer affects: libplist (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libimobiledevice in
Ubuntu.
https://bugs.launchpad.net/bugs
This was applied upstream in
http://cgit.freedesktop.org/upower/commit/?id=3a5f3e552 and released in
0.99.2, and thus fixed in Ubuntu 15.04.
** Changed in: upower (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: upower (Ubuntu)
Status: Fix Committed => Fix Released
--
Yo
it cannot listen to the audit socket (as the kernel doesn't allow
that -- the audit subsystem isn't fit for namespaces right now), and
"sudo journalctl" should show the journal and systemd-journald.service
should be running.
** Affects: systemd (Ubuntu)
Importance: Medium
Upstream discussion: http://lists.freedesktop.org/archives/systemd-
devel/2015-May/032113.html
--
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/1457054
Title:
journal is bro
Daniel [2015-05-20 16:19 -]:
> Is this bug really fixed? I have very similar errors with the version
> from the vivid live cd (systemd 219-7ubuntu3) when trying to start user-
> space LXC containers
I haven't tried creating/running containers on a live system, as that
environment is quite a bi
Fixed upstream:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=417a7fdc418
http://cgit.freedesktop.org/systemd/systemd/commit/?id=01906c76c
However, there's one more detail to fix in unprivileged containers:
root@v:/# getpcaps $$
Capabilities for `608': =
cap_chown,cap_dac_override,
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-
vivid&id=8db397eef12d6
** Changed in: systemd (Ubuntu Wily)
Status: In Progress => Fix Committed
** Changed in: systemd (Ubuntu Vivid)
Status: Confirmed => In Progress
** No longer affects: lxc (Ubuntu Vivid)
> To be pedantic, it is not a lie - you have that capability against
your own user namespace,
Ah, so that says "you can do it", but it's never actually going to work?
I guess that's just another expression of audit not working in
namespaces then..
> Unfortunately that will be tough coordinate wit
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
--
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/1432171
Title:
[udev] Shows "starting version 219" b
a similar UPS
responder in a container, but that seems like a theoretical scenario only.
- There is no change for VMs or "real" hardware.
** Affects: systemd (Ubuntu)
Importance: Medium
Assignee: Martin Pitt (pitti)
Status: In Progress
** Affects: systemd (Ubuntu Vivid)
** Description changed:
lxc-stop sends SIGPWR to a container's pid 1 to notify it that it should
shut down. This merely starts sigpwr.target right now, but nothing is
hooked into it. That's deliberate for "real iron" systems as there it's
usually UPSes sending that, which should be handled
** Description changed:
Test case
-
- Under Ubuntu 15.04 (or 15.10), set up an unprivileged container as in
https://www.stgraber.org/2014/01/17/lxc-1-0-unprivileged-containers/
- Boot it. You'll get a lot of errors like
[FAILED] Failed to start Journal Service.
syst
Fix for Debian/wily: http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=experimental&id=44c3369f97b
Backported for vivid: http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=ubuntu-vivid&id=7c45c5bc168df
** Changed in: systemd (Ubuntu Wily)
Status: In Progress
*** This bug is a duplicate of bug 102 ***
https://bugs.launchpad.net/bugs/102
This is almost certainly a duplicate of bug 102. I'll upload a fix
to vivid-proposed soon, in the meantime you can test the fix in
https://launchpad.net/~pitti/+archive/ubuntu/sru-test . Please yell if
t
Can you please boot with dropping "quiet" and "splash", by editing the
"linux" line in the GRUB boot menu. Where do you end up? Do you get a
"login:" prompt where you can login? If not, please do a screenshot
(with a camera) and attach that, there's hopefully some text which shows
where exactly i
Can you please start a debug shell as described in
/usr/share/doc/systemd/README.Debian, shut down, and when it hangs run
loginctl session-status c2 > /root/session-c2.txt
Apparently there is a process in your user session which does not shut
down but hangs, so we need to find out what it is. I
** Summary changed:
- Ubuntu taking long to shutdown
+ linconnect_server.py hangs on shut down
--
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/1457400
Title:
linconnect_se
What happens at shutdown is that all processes are sent SIGTERM, so that
they have a chance to intercept, save their state/clean up, etc. After a
timeout (default 90s) SIGKILL is sent. So it seems linconnect_server.py
does not actually shut down on SIGTERM?
I tried to download and install it, but
This probably got introduced with the fix for bug 1448259. So, this
general behaviour is "correct" in the sense that processes should not be
killed immediately after SIGTERMing them. But 90s is a bit much for
session shutdowns, this could be reduced to something like 30 s. This is
still a long sess
Thank you! Pushed with trivial fix for this warning:
up-device-supply.c: In function 'up_device_supply_coldplug':
up-device-supply.c:989:6: warning: suggest parentheses around assignment used
as truth value [-Wparentheses]
if (dir = g_dir_open (subdir, 0, &error)) {
^
--
You receive
** No longer affects: systemd (Ubuntu Vivid)
** No longer affects: systemd (Ubuntu)
--
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/1447282
Title:
Does not use encrypted s
*** This bug is a duplicate of bug 1385817 ***
https://bugs.launchpad.net/bugs/1385817
Duplicate of bug 1385817. /etc/init.d/smfpd is a third-party SysV init
script which is missing LSB header information.
** This bug has been marked a duplicate of bug 1385817
initscripts package fails to
>1 ? Ss 0:06 /sbin/init splash
This looks really broken. How did you boot this system exactly? I. e.
please give the output of /proc/cmdline. Did you maybe include "splash"
into the argument of init=? This isn't an argument for "init", but a
kernel command line part which is read by plymouth.
>1 ? Ss 0:06 /sbin/init splash
Nevermind, this is normal. However, what is the actual *problem* that
this causes for you?
Note that neither upstart nor systemd's /sbin/init actually evaluate
this (and aren't supposed to).
--
You received this bug notification because you are a member of Ubu
** Summary changed:
- fscking btrfs mount fails with non-unique UUIDs
+ fscking btrfs consisting of multiple partitions fails
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Quick answer: it's probably better to ask that on
http://lists.freedesktop.org/mailman/listinfo/systemd-devel , there are
a bunch of people familiar with both btrfs and systemd. Also, systemd-
fsck-root.service apparently succeeded, so it's a different partition.
What does this say?
sudo systemc
in: resolvconf (Ubuntu)
Status: New => Fix Committed
** Changed in: resolvconf (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: resolvconf (Ubuntu)
Importance: Undecided => Low
** Tags removed: systemd-boot
--
You received this bug notification bec
@Thomas: I found it best to simply drop that part of our delta, which
both fixes this bug again and makes maintenance easier.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bug
This has happened a fair while ago already.
** Changed in: util-linux (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/90629
Daniel Kulesz [2015-05-27 23:28 -]:
> Problems still persists, although policykit-1 should be the patched
> release. Please re-open!
It is already open again (the floating task). I haven't managed to
reproduce this yet, sorry.
Martin
--
Martin Pitt
: friendly-recovery (Ubuntu)
Status: New => Triaged
** Changed in: friendly-recovery (Ubuntu)
Importance: Undecided => Low
** Changed in: friendly-recovery (Ubuntu)
Status: Triaged => In Progress
** Changed in: friendly-recovery (Ubuntu)
Assignee: (unassigned) =>
** Bug watch added: Debian Bug tracker #772095
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772095
** Also affects: upower (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772095
Importance: Unknown
Status: Unknown
--
You received this bug notification because yo
*** This bug is a duplicate of bug 1449051 ***
https://bugs.launchpad.net/bugs/1449051
** This bug has been marked a duplicate of bug 1449051
Upower doesn't handle bluetooth mice properly
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Bug watch added: Debian Bug tracker #785725
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785725
** Also affects: upower (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785725
Importance: Unknown
Status: Unknown
--
You received this bug notification because yo
There is nothing in debian/ which would fill the two udebs (ubuntu
delta) with anything -- no *.install files, no code in debian/rules. And
indeed libcurl3-udeb and curl-udeb are empty. While this is certainly
not the fault of *this* merge, this should be rectified.
Please do some research when th
There is no patch attached here, I assume it got removed? And this very
much does sound like the upower patch referenced from above. I'm
unsubscribing sponsors, and tentatively close this. If this is still an
issue in vivid, or you have a backported patch to sponsor etc., please
reopen/re-subscribe
Note that the patch is a no-op. The source package format is 1.0 and it
doesn't call quilt explicitly. The precise package uses inline patches.
I tried to apply it manually, but it doesn't fit at all..
Can you please backport the patch to the precise version and change it
inline?
** Changed in:
Unsubscribing sponsors, please re-subscribe when you attach a working
patch. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1006898
Title:
[SRU] dnsmasq fails at l
Please forward the patches to upstream
(http://sourceforge.net/projects/g15tools). Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libusb in Ubuntu.
https://bugs.launchpad.net/bugs/1357556
Title:
Does not stop/resta
Right, please forward this to http://bugzilla.sudo.ws/index.cgi . I
don't want to patch this central piece of security sensitive software
with some upstream review; and in general, we avoid having non-Ubuntu
specific patches in Ubuntu only. Thanks!
--
You received this bug notification because yo
** Changed in: init-system-helpers (Ubuntu)
Status: Triaged => In Progress
** Changed in: init-system-helpers (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
** Changed in: init-system-helpers (Ubuntu)
Status: In Progress => Fix Committed
--
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/1458630
Title:
broken pa
Thanks Thomas for the review! I cleaned up the three issues you
mentioned.
Out of interest, do you plan to keep /etc/resolvconf/run in Debian? To
me this has always appeared to be a transitional thing in Debian, as
going through that indirection is a bit confusing and also cluttering of
/etc.
+
Fixed in wily with https://launchpad.net/ubuntu/+source/upower/0.99.3-1,
just the changelog referred to the wrong bug, sorry.
** Changed in: upower (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages
Hey THomas,
Thomas Hood [2015-06-01 8:35 -]:
> Is there something we should do to silence those insserv warnings?
> insserv: warning: current start runlevel(s) (2 3 4 5) of script `resolvconf'
> overrides LSB defaults (S).
> insserv: warning: current stop runlevel(s) (0 1 6) of script `resol
http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=4a268404
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a
@Ross: I already prepared the fix some two weeks ago, it's waiting in
https://launchpad.net/ubuntu/vivid/+queue?queue_state=1 to be processed
by the SRU team.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** 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/1450009
Title:
suspends on closed lid, does not recognized
*** This bug is a duplicate of bug 1450009 ***
https://bugs.launchpad.net/bugs/1450009
** This bug has been marked a duplicate of bug 1450009
suspends on closed lid, does not recognized external monitors/dock
--
You received this bug notification because you are a member of Ubuntu
Touch s
*** This bug is a duplicate of bug 1450009 ***
https://bugs.launchpad.net/bugs/1450009
** This bug has been marked a duplicate of bug 1450009
suspends on closed lid, does not recognized external monitors/dock
--
You received this bug notification because you are a member of Ubuntu
Touch s
*** This bug is a duplicate of bug 1450009 ***
https://bugs.launchpad.net/bugs/1450009
** This bug is no longer a duplicate of bug 1438301
suspends after a few minutes on machines with a bogus (closed) lid switch
** This bug has been marked a duplicate of bug 1450009
suspends on closed l
Background: logind has some "failsafe" logic to go to suspend after 30 s
if the lid is closed and there are no external monitors connected
(http://cgit.freedesktop.org/systemd/systemd/commit/?id=ed4ba7e4f65215).
This would lead to effects like this if the lid switch is broken and
always says "close
Hey Thomas,
can you pleae copy&paste the output of
udevadm test-builtin input_id /class/input/js0 ?
This will show the precise capabilities that the device reports.
>From your udevadm info output it appears that this isn't just an
input_id mis-interpretation though, but that the usbhid kernel
To narrow this down, please do:
* Under systemd, run
echo mem | sudo tee /sys/power/state
check if suspend works or fails, and if it fails attach the output
of "dmesg".
* If the former works, try again with "sudo systemctl suspend". If it
fails, please attach "dmesg". If it works
If it's broken at the kernel level, you can also try running 15.04 with
the 14.10 kernel.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1454253
Title:
external usb breaks
ureadahead needs an out-of-tree kernel patch to add trace events for
open(), exec() and uselib() syscalls that take file paths, see bug
462111. This needs to be changed to use fanotify() which is available in
the standard kernels. However, it needs to be checked whether it's also
available on the U
> How can i reproduce this if i dont want to erase the machine complete
and recover the backup again?
Do you have /var/log/journal/ , i. e. enabled persistant journal? If so,
you could try and move it away (or just delete it if you don't care).
If not, the journal is just kept in /run/log/journal
OK, thanks. So it seems there is a broken acpi_video0 which doesn't
appear in the grep. Can you please give me the output of
ls -l /sys/class/backlight/
? If that's a broken symlink or so, then systemd-
backlight@backlight:acpi_video0.service is okay to fail. However, there
should be another on
The main difference here is that under upstart we still run pm-suspend
with its quirks, while under systemd there are no quirks being run any
more. As suspend quirks have supposed to be obsolete for many years
and should be fixed properly in drivers/kernel, I add a linux task.
To find out which
This isn't really blkid's fault. The problem is motherboards that have a
floppy controller with no actual floppy attached to it -- each time you
try and send a command to that, the entire controller hangs for some 30
seconds before it finally fails. This affects anything that tries to
talk to it, n
"systemctl status foo.service" ought to have an error message that the
unit file is broken. However, comments in ExecStart= are just passed on
verbatim to whatever you execute, so this should reflect in some
specific error message? I. e. if I have
$ cat /etc/systemd/system/broken.service
[Service
> crypt /dev/mapper/main-cryptstore none luks,noearly,discard
This looks really curious -- the source device is "none", so how is that
finding out where the underlying encrypted device is? This should
usually be something like UUID=12345, or /dev/sdb3 or whatever.
Can you please boot with the sys
Hm, when I do this it seems to be correct:
$ sudo systemd-nspawn -b -D /tmp/schroot-wily-systemd/
"machinectl status schroot-wily-systemd" shows
Unit: machine-schroot\x2dwily\x2dsystemd.scope
├─12745 /lib/systemd/systemd
[...]
and systemd-cgls shows
├─
OK, thanks, so /var/log/syslog is useless here. Can you please boot with
the systemd debug shell as described in
/usr/share/doc/systemd/README.Debian and also drop "quiet" and "splash"
from the "linux" line in grub. Do you get some output then? Can you
switch to the debug shell at Ctrl+Alt+F9? If s
*** This bug is a duplicate of bug 1449638 ***
https://bugs.launchpad.net/bugs/1449638
Indeed the log looks just fine -- it starts sddm and the user session.
As you now reinstalled, any further evidence is lost I'm afraid, so I'll
just duplicate this.
** This bug has been marked a duplicate o
Interesting, pm-suspend uses no quirks at all. Can you double-check that
running "sudo pm-suspend" is reliable while "sudo systemctl suspend" is
not? The two do exactly the same without quirks, i.e. writing "mem" into
/sys/power/state..
--
You received this bug notification because you are a memb
No, I'm running what is in Ubuntu 15.10 (not too different from 15.04),
and we don't have that patch yet. Anyway, if that helps (you can easily
apply it locally), that clarifies this matter for sure. :-) Thanks for
digging out the link!
** Changed in: systemd (Ubuntu)
Status: Incomplete =>
Unfortunately that log only mentions that cycles exist, but not what
they are. Please attach /var/log/syslog, or better yet, run "sudo
journalctl -b > /tmp/journal.txt" and attach /tmp/journal.txt. Thanks!
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug
Thanks for confirming! Reassigning to the kernel then.
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
--
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:
OK, then it might be one of the other hooks in /usr/lib/pm-utils/sleep.d
that pm-suspend runs. According to your dmesg it's unlikely that you
have the "alx" module loaded ("lsmod | grep alx" should be empty).
Can you please attach your /var/log/pm-suspend.log?
60_wpa_supplicant could be a likely
Thanks. So we need to find out which hook does the magic. For each value
of in the below list, can you please run
sudo /usr/lib/pm-utils/sleep.d/ suspend ; sudo systemctl
suspend; sudo /usr/lib/pm-utils/sleep.d/ resume
In descending order of likelyhood, I recommend the following list for
:
@Simon: I'm going to give you a brutally honest answer, as that's going
to be more helpful than just silence: Most Linux developers haven't had
systems with floppy drives for many many years (me included), and it's
actually not that easy these days to find a computer with a floppy these
days, at le
Thanks Jan. Note that you can make this a little faster too -- you can
start with testing (i. e. starting with "suspend") all five hooks at the
same time, to confirm whether it's actually any of these five. If it
still doesn't help, then the problem is somewhere entirely different. If
it does help,
*** Bug 86510 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1449051
Title:
Upower doesn't handle bluetooth mice properly
S
macfix@eth0.service seems to be the culprit. It seems to not have
DefaultDependencies=no, but wants to run before networ-pre.target. What
is that? Is that coming from any Ubuntu package? What's the output of
systemctl status macfix@eth0.service
systemctl cat macfix@.service
?
--
You receive
> Is there some systemd command which could check all enabled units for
cycles and report them?
Not right now, but there is an upstream bug about that:
https://github.com/systemd/systemd/issues/69
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, wh
Is there anything left to do/analyze here?
--
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/1436168
Title:
systemd-journald crashed with SIGABRT in journal_file_move_to_obje
[ 16.371747] systemd[1]: Found dependency on screen-
cleanup.service/start
This seems to be the culprit. screen-cleanup is a service which needs to
run before the very early sysinit.target, but requires remote-fs.target,
which is unsatisfiable once you have remote file systems like openafs.
Is tha
Uh, from screen .. What happened to /lib/systemd/system/screen-
cleanup.service ? It should be a symlink to /dev/null.
What does
ls -l /lib/systemd/system/screen-cleanup.service
dpkg -s screen
show to you? Is screen perhaps removed, but not purged?
** Package changed: systemd (Ubuntu) => s
Indeed, I completely forgot about the sudo/admin groups. Indeed "admin"
has been the one introduced by Ubuntu since the very beginning; later
"sudo" was introduced by Debian, and Ubuntu moved to it. So "admin" can
safely be dropped once all sudo users got moved into "sudo".
** Changed in: policyki
> Since we are in the early development, I proposed to sed them out and
see if any regression (unlikely) is spotted.
Works for me. If this got broken pre-trusty it's indeed unlikely to
still be needed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages
Looks good now, thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/1459685
Title:
please merge curl from debian
Status in curl package in Ubuntu:
Confirmed
Bug des
I verified that Erkan's .service file crashes current vivid-updates
systemd, and works fine (with a proper error message) with the -proposed
package.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Tou
** Summary changed:
- Hang after installing and running serviio
+ Hangs on shutdown after installing and running serviio
--
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/14567
Indeed, thanks for spotting! Fixed in http://bazaar.launchpad.net
/~apport-hackers/apport/trunk/revision/2968 , this also cleaned up a few
other errors to consistently use apport.fatal().
** Changed in: apport (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification bec
The "/usr appears to be on its own filesystem ..." is just a warning.
Booting with separate /usr is supported, as long as it's a local
partition and not a remote one (the latter could work, but really nobody
tests this). I just did a 15.04 installation with separate /usr, and it
works fine.
Could
With the original (failing) fstab, can you please do a boot, log in, do
sudo journalctl -b > /tmp/journal.txt
and attach /tmp/journal.txt here? Thanks!
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
T
I wonder if that is a side effect of bug 1423811. Any chance you could
try this on a wily daily CD and see if it still hangs? If not, then that
fix would be a likely candidate. I can provide a systemd in a PPA for
testing then.
--
You received this bug notification because you are a member of Ubu
Ah, thanks. I'm afraid there is not that much that we can do about this
then, it's a conflict with a local non-system group. Unless you actually
use that, I suggest removing it, and let udev re-create it as a system
group.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Won't Fix
--
>I've been working with Linux for 20 years, I really doubt there was
anything wrong with my fstab.
systemd reports errors which sysvinit and upstart just ignore (i. e.
silently ignoring wrong UUIDs, and just not pointing that partition,
etc.). We got a lot of bug reports due to that, which is why
> So what I can do is to install a 14.04 system with LVM and separate
/home, /tmp/, /usr, and /var, upgrade that to 14.10 and 15.04, and see
if I can reproduce this.
I just did that, and the upgrade worked without a hitch. So I'm afraid
we still don't have a reproducer for this..
/dev/vda1 on /bo
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
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/1452204
Title:
evdev device for retro-bit NES controller ad
assigned) => Martin Pitt (pitti)
--
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/1454254
Title:
Switch to ifnames persistent network names
Status in systemd package in Ubuntu
Thanks for your report. I don't see anything immediately wrong with your
/etc/fstab, blkid looks fine and has matching UUIDs. So I'm afraid I
need a full log to see what happened.
In the grub boot menu under "Advanced options", please select the one-
time boot with systemd (you don't need to chang
Ah, great. So can you confirm that this works:
sudo pm-powersave false; sudo systemctl suspend; sudo pm-powersave
true
? If so, can you repeat the bisecting exercise with the hooks in
/usr/lib/pm-utils/power.d/ to find out which one is the important one
here?
Thanks!
--
You received this bug
Hans-Gregor, this looks like bug 1453738 (broken swap with LVM+home dir
encryption).
--
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/1431743
Title:
fails to boot with brok
udev's preinst only has some standard autogenerated debhelper code,
mostly related to the ancient sysvinit->upstart migration. So this
rather looks like some random error induced by a memory or hard disk
problem? Can you please run a memory test (grub boot menu) and file
system check (also in grub
301 - 400 of 4146 matches
Mail list logo
