*** This bug is a duplicate of bug 1431743 ***
https://bugs.launchpad.net/bugs/1431743
Thanks for the journal! Here we are:
Jun 07 14:03:23 gilbert-iMac systemd[1]: Starting Remount Root and Kernel File
Systems...
Jun 07 14:03:26 gilbert-iMac systemd-remount-fs[522]: mount: can't find
UUID=
For the record, we are going to switch to net.ifnames soon in wily and
Debian. See bug 1454254 and https://lists.ubuntu.com/archives/ubuntu-
devel/2015-May/038761.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-set
@Anders: There is no syslog for a systemd boot. Can you please do the
same exercise as in comment #9, attach the journal, and additioally
/etc/crypttab and /etc/fstab? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sy
Gunter,
sorry about the "none" comment #2, that was obviously bogus, I mis-
looked.
Can you please follow /usr/share/doc/systemd/README.Debian to boot with
a debug shell, then switch to it once it stalls, run "journalctl -ab >
/root/journal.txt", reboot, and attach /root/journal.txt here?
--
Yo
Does that happen with any service? Or is that specific to smbd and sssd?
I suppose 'service' is not the culprit here, and it also happens if you
directly call "sudo systemctl restart smbd.service"?
Can you please do
sudo systemd-analyze set-log-level debug
sudo systemctl restart systemd-udevd
Another thing, can you please give me the output of
systemctl list-jobs
systemctl status|head
thanks!
--
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/1456789
Title:
r
The sdb1 one is most likely an USB stick (FAT, not ext4). Your ext4 root
partition is sda5 which is shown as clean now. Could still be that a
previous fsck cured it, of course -- this wouldn't appear in
/var/log/syslog as it happens very early at boot already while the root
partition is still reado
** Also affects: linux (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/1458631
Title:
udev: /dev/input/js0 is created b
Adding a kernel task, as the /dev/input/js0 is created by the kernel
driver (usbhid) itself. udev does not create device nodes, it just adds
additional properties, runs extra programs on the device nodes, etc.
So cases a/ vs. b/ is interesting -- in both cases you get three HID
devices, just that
On that grounds I close the systemd/udev task, as this really needs to
be fixed in the hid-generic (or maybe other) kernel driver.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
For example, we have
#define BTN_TRIGGER…0x120
I. e. the capability bit mask whether the device claims to have a BTN_TRIGGER
is the 0x120th bit in capabilities/key, or IOW, the 32th bit in
bit 256: 0C01
which is zero. Likewise there's no BTN_A, nor BTN_1. Interestingl
In dmesg I see
[ 15.223526] asus_wmi: Unknown key cf pressed
which we indeed don't have in the "Asus" section of
/lib/udev/hwdb.d/60-keyboard.hwdb. We have the scan code "6b" there
instead, which presumably applies to older/other models.
To ensure that this was actually the touchpad toggle ke
Thanks. So it seems some of the Fn keys appear through the "Asus WMI
hotkeys" device, but others don't. The only other plausible device is
"AT Translated Set 2 keyboard" (i. e. the standard keyboard which also
sends the letters and numbers). Can you re-run "sudo evtest", select
that one, and repeat
> F1,F2,F5,F6: no change, no output
OK, that makes it a kernel bug then, reassigning. The driver needs to
send evdev events for these keys.
> F3,F4,F7,F9 : no output, did produce output in previous Asus device
test.
Yes, that's expected. They are appearing on the WMI device, not the AT
keyboard
Ah, thanks! That's a bit weird -- on powersave false wake-on-lan is
*enabled*. So it seems that with WOL disabled your computer doesn't stay
suspended, but with WOL enabled it does.
Cross-check:
sudo ethtool -s wlan0 wol g ; sudo systemctl suspend
-> that enables WOL on the usual magick packet
> % sudo restart network-manager
That doesn't work. "restart" is an upstart specific command. You need to
use the init-neutral "service" or "systemctl".
Will look at the logs soon, thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
Jun 15 09:46:54 djledkov-mobl1 systemd[1]: Found ordering cycle on
network-online.target/start
Jun 15 09:46:54 djledkov-mobl1 systemd[1]: Found dependency on
NetworkManager-wait-online.service/start
Jun 15 09:46:54 djledkov-mobl1 systemd[1]: Found dependency on
basic.target/start
Jun 15 09:46:54
** No longer affects: systemd (Ubuntu)
** Tags added: systemd-boot
** Summary changed:
- NetworkManager-wait-online job deleted to break ordering cycle
+ open-iscsi init script creates dependency cycle with NetworkManager
--
You received this bug notification because you are a member of Ubuntu
This was fixed in
https://launchpad.net/ubuntu/+source/systemd/220-6ubuntu1, I just
typo'ed the bug ref in the changelog.
** Changed in: systemd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, w
Your system isn't too happy because of bug 1452644. This is fixed in
vivid-proposed, but this hasn't made it into -updates yet. This causes
network mounts etc. to fail. That might be related to the shutdown
problems. To get this out of the way, could you install the -proposed
setserial and re-test?
** Changed in: systemd (Ubuntu)
Status: Triaged => In Progress
--
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 na
Hello Jan,
Jan Rathmann [2015-06-15 14:06 -]:
> - If I run the ethtool command before 'systemctl suspend', the bug
> hasn't appeared so far - and it does not seem to matter if I run ethtool
> with the 'wol g' (enable WOL) or with the 'wol d' flag!
That's indeed interesting -- After a clean b
** Changed in: systemd (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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1454254
Title:
Switch to ifnames persistent netw
Thanks for your patience! I believe this is sufficiently understood now.
I retitled the bug accordingly, this should indeed be fixed properly in
the driver then. In the meantime, putting that workaround into rc.local
or /lib/systemd/system-sleep/ (see man systemd-suspend.service) is fine.
** Summa
ed in: apport (Ubuntu)
Status: New => Triaged
** Changed in: apport (Ubuntu)
Importance: Undecided => High
** Changed in: apport (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Description changed:
Errors Bucket
-
https://errors.ubuntu.com/b
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
** This bug is no longer a duplicate of private bug 1494664
** This bug has been marked a duplicate of bug 1433320
systemd-journald, udev, logind crashed with SIGABRT -- get killed by 1 min
watchdog time
** Changed in: systemd (Ubuntu)
Status: Won't Fix => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1433320
Title:
systemd-journald, udev, logind crashed wit
** Changed in: upstart (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1384886
Title:
upstart shouldn't depend on libjson
** Changed in: hundredpapercuts
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1384886
Title:
upstart shouldn't depend on libjson0
** Changed in: libx11 (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 libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/518056
Title:
cedilla appears as accented c (ć ins
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
** This bug has been marked a duplicate of bug 1433320
systemd-journald, udev, logind crashed with SIGABRT -- get killed by 1 min
watchdog timeout on longer kernel lockups
--
You received this bug noti
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
** This bug has been marked a duplicate of bug 1433320
systemd-journald, udev, logind crashed with SIGABRT -- get killed by 1 min
watchdog timeout on longer kernel lockups
--
You received this bug noti
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
** This bug has been marked a duplicate of bug 1433320
systemd-journald, udev, logind crashed with SIGABRT -- get killed by 1 min
watchdog timeout on longer kernel lockups
--
You received this bug noti
*** This bug is a duplicate of bug 1495178 ***
https://bugs.launchpad.net/bugs/1495178
** This bug has been marked a duplicate of bug 1495178
Failed to set wall message, ignoring: Message recipient disconnected from
message bus without replying
--
You received this bug notification becau
Apparently this still happens a lot, reopening.
** Changed in: systemd (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: systemd (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
*** This bug is a duplicate of bug 1495178 ***
https://bugs.launchpad.net/bugs/1495178
** This bug has been marked a duplicate of bug 1495178
Failed to set wall message, ignoring: Message recipient disconnected from
message bus without replying
--
You received this bug notification becau
=> In Progress
** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-15.09
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to s
Fixed with https://github.com/systemd/systemd/commit/91b3e7f, pulled
that into the wily branch.
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: systemd (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a membe
udev-finish.service is gone, together with /lib/udev/udev-finish. That's
quite deliberate, we don't need it any more.
Please give me the output of "sudo systemctl status -l udev-
finish.service". Thanks!
** Package changed: udev (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
** Changed in: apport (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: systemd (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.lau
Can you please attach /etc/init.d/udev-finish? Did you perhaps modify
this? This file is usually cleaned up on upgrade from versions earlier
than 225-2.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https:
Ah well, it seems you downgraded to 219-7ubuntu6 again? If you upgrade
to wily again with
sudo apt-get install udev
can you please copy&paste the entire output?
** Summary changed:
- udev-finish.service still present in wily
+ /etc/init.d/udev-finish does not get cleaned up on upgrade
--
Yo
I pushed the fixes to trunk. Will do a new release and upload to wily
after beta freeze.
** Changed in: apport
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
http
New upstream release that contains the fixes:
https://launchpad.net/apport/trunk/2.19
** Changed in: apport
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https:
** Changed in: apport (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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1492570
Title:
/usr/share/apport/kernel_crash
Indeed, this should be fixed in /usr/lib/avahi/avahi-daemon-check-dns.sh
. When running under systemd ([ -d /run/systemd/system ]) then the
.socket needs to be stopped too, not just the .service.
** Changed in: avahi (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notificat
Is there maybe already a /usr/sbin/uuidd.bak with read-only permissions?
Or a non-writable /usr/sbin? Please show the output of
ls -ld /usr/sbin/
ls -l /usr/sbin/uuidd*
** Changed in: util-linux (Ubuntu)
Status: New => Fix Released
** Changed in: util-linux (Ubuntu)
Status: Fix
Making *all* devices from these two vendors world-writable is too
dangerous, this can't go into a default distro rule. This needs to be
restricted to either particular product IDs/patterns, or better yet, to
particular device classes. What are these anyway, something like
joysticks or game controll
> did restore a recent wily backup though, so these now obsolete udev
files in /etc/init & /etc/init.d files might stem from that
Ah, this would explain it then.
I just did a dist-upgrade from vivid to current wily, and it works as
intended:
Setting up udev (225-1ubuntu4) ...
Installing new ver
** No longer affects: upstart (Ubuntu)
** No longer affects: udev (Ubuntu)
** 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/1495116
Ti
Dmesg has tons of kernel errors, which are likely related. When this
happens again, can you please run "udevadm monitor -k"? Do you get lots
of events there? I. e. is udev merely trying to process a bazillion
events that the kernel throws at it, or is it busy with itself?
** Changed in: systemd (U
There is a whole chain of failures:
dpkg: dependency problems prevent configuration of systemd:
systemd depends on libcryptsetup4 (>= 2:1.4.3); however:
Package libcryptsetup4 is not configured yet.
dpkg: dependency problems prevent configuration of libcryptsetup4:
libcryptsetup4 depends on l
Can you please also attach a bootchart of 15.04? Otherwise we have
nothing to compare this against.
Indeed I/O really sucks -- most of the time it's between 2 and 10 MB/s,
and there's just a single peak at 23 MB/s. This would match what you'd
expect from a middle-aged rotational disk. There is vir
*** This bug is a duplicate of bug 1447807 ***
https://bugs.launchpad.net/bugs/1447807
** This bug has been marked a duplicate of bug 1447807
systemctl enable shows error on enabling a SysV service
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
Do you have a chance to try a current Ubuntu life session on this
machine, like 15.10 beta? http://releases.ubuntu.com/wily/
If this still happens there, please install the "evtest" package, run
"sudo evtest", select they keyboard, press the Alt/Shift/etc. keys, then
press Control-C, and copy&past
dpkg: cycle found while processing triggers:
chain of packages whose triggers are or may be responsible:
lubuntu-software-center -> libc-bin
This looks similar to bug 1496119, where lubuntu-software-center is the
common factor.
** Summary changed:
- package systemd 225-1ubuntu4 failed to inst
*** This bug is a duplicate of bug 1496038 ***
https://bugs.launchpad.net/bugs/1496038
Google translate of the error message:
dpkg: a loop is found while processing triggers:
packet chain whose triggers are or may be responsible:
lubuntu-software-center -> cups
packet pending triggers
*** This bug is a duplicate of bug 1436448 ***
https://bugs.launchpad.net/bugs/1436448
** This bug has been marked a duplicate of bug 1436448
Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was
reached (g-io-error-quark, 24)
--
You received this bug notification
*** This bug is a duplicate of bug 1406952 ***
https://bugs.launchpad.net/bugs/1406952
** This bug has been marked a duplicate of bug 1406952
systemd-udevd[471]: Error calling EVIOCSKEYCODE: Invalid argument
--
You received this bug notification because you are a member of Ubuntu
Touch se
That sounds a bit like fs corruption then. Can you please do
cd /usr/bin; sudo strace -fvvs1024 -o /tmp/trace ln uuidd uuidd.bak
and attach /tmp/trace? I guess it really fails in link(2) with EPERM
("old name is a directory") or EACCESS ("new path directory is not
writable"), but let's make dou
nee: (unassigned) => 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/1466081
Title:
[udev] no uevent when block devices change
Status in systemd package in
** Bug watch added: Debian Bug tracker #789060
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789060
** Also affects: systemd (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789060
Importance: Unknown
Status: Unknown
--
You received this bug notification because y
** Description changed:
Since July 7, udisks2 fails its tests: https://jenkins.qa.ubuntu.com/job
/wily-adt-udisks2/
After a file system operation like mkfs or e2label udisks2 does not
update its properties any more. This can be replicated easily locally
with e. g.
- sudo modprobe
This is fixed in upstream trunk already, with the daily packages from
https://launchpad.net/~pitti/+archive/ubuntu/systemd/+packages it works
fine.
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: systemd (Ubuntu)
Status: Fix Committed => In Progress
** Changed in: systemd (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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1466081
Title:
[udev] no uevent when block devic
** Package changed: udev (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: New => 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/1467
Fixed upstream in https://github.com/systemd/systemd/commit/bb5c512de22,
part of 221 release. I'll upload a backport if that's critical for
alpha-1.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: systemd (Ubuntu)
Assignee: (unassign
> Generally speaking people expect rc.local to be run as "the last thing
in boot".
This can't be taken literally, as services can and do come and go (stop
and start) all the time, and as any service can declare dependencies to
run after "your thing" this can't be enforced either.
For example, cou
** Changed in: apport (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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1468154
Title:
kerneloops-daemon crashes if "linux
So the gist of this is that rc.local writes to /dev/console but you
don't see this? I added this to /etc/rc.local on a normal installation:
echo hello_stdout
echo hello_console > /dev/console
and "systemctl start rc-local.service" does print the hello_console on
the console (you need to run it on
** Changed in: systemd (Ubuntu)
Importance: High => Low
--
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/1468102
Title:
rc.local output does not go to console
Status in
nee: (unassigned) => 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/1468102
Title:
rc.local output does not go to console
Status in systemd package in
> Independent of cloud-init, things in rc.local should be run as "the
last thing in boot".
So now we have "last thing except cloud-init" :-) There are other
services which order themselves after it, like getty@, plymouth-quit and
others, to avoid disturbing init.d/rc.local scripts with allocated V
Uploaded, thanks!
** Changed in: ust (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ust in Ubuntu.
https://bugs.launchpad.net/bugs/1468345
Title:
Merge ust 2.6.2-1 (main)
I'll drop the python-apt task as it's tracked in bug 1445949 but we
can't make this bug a duplicate because of the other tasks.
** No longer affects: python-apt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-
apturl fix committed to bzr and uploaded. Thanks!
** Changed in: apturl (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1465549
Titl
ufw uploaded too, thanks!
** Changed in: ufw (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1465549
Title:
Plainbox tests are bro
Fixed in http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=7cdf9f651a
** 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.
So that seems to be an artifact of using lsh-server? After ssh'ing in,
please copy&paste the output of "cat /proc/self/cgroups"
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, w
I'm afraid I don't speak Italian, but according to the log you might
have tried to remove/purge the "systemd" package? Unfortunately this
report doesn't contain the original problem log, just the follow up
error. What is the output of
sudo apt-get -f install
(say "yes" if it asks to repair)
**
Indeed, the log doesn't even show an attempt to unlock cryptstore. In
that debug shell, can you please do
tar cf /root/generator.tar /run/systemd/generator*
and attach /root/generator.tar here?
** Summary changed:
- systemd does not allow to boot with /home on dm-crypt
+ systemd does not unlo
No answer in over a month, closing. Please reopen once you can provide
the requested information. Thank you!
** 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
No answer in about two months, closing. Please reopen once you can
provide the requested information. Thank you!
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
Okay, closing then.
** 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/1436168
Title:
systemd-journald cr
http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=afb79c4
** Summary changed:
- package udev 219-7ubuntu5 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 1
+ package udev 219-7ubuntu5 failed to install/upgrade: group "input" al
Can you please give the output of
sudo systemctl status -l systemd-update-utmp.service
and do "sudo journalctl -ab > /tmp/journal.txt" and attach
/tmp/journal.txt ? Perhaps this contains an useful error message what's
going wrong with this. It would also be useful if you could boot with
the add
Can you please get a journal from shutdown, as described in
/usr/share/doc/systemd/README.Debian ? Once it hangs, switch to the
debug shell, and do
journalctl -ab > /root/journal.txt
reboot -f
and then attach /root/journal.txt here. I suppose it's the "umount"
which times out on the network f
Indeed your journal shows that systemd-tmpfiles-setup.service wasn't
called at all. After that happens, what is the output of
sudo systemctl status -l systemd-tmpfiles-setup.service
? Can you please boot with "systemd.log_level=debug" on the kernel
command line and reproduce this, then attach t
> Could it be that something about keeping daemons started during ifup
running be accidentally dropped?
Not that I know of, and in my wily VMs dhclient runs happily.
I don't know whether ifupdown has some useful debugging facilities. I
tried adding /usr/bin/strace -fvvs1024 -o /run/ifup.trace to
I meant /proc/self/cgroup, sorry.
> what ssh server have to do with this?
Because your process is in /system.slice/lsh-server.service, which your
user cannot access.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a m
;unity-services
7.2.5+14.04.20150521.1-0ubuntu1']
unity-2d-dbg is just a transitional package, and shouldn't trump the
-dbgsym package. We need some heuristic there, like "transitional" in
the package description, or size being < 10 kB.
** Affects: apport (Ubuntu)
Importa
Fixed in trunk r2977.
** Changed in: apport (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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1469635
Title:
Don't pick t
** Package changed: systemd (Ubuntu) => hdparm (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/1470014
Title:
systemd-udevd: Process '/lib/udev/hdparm' failed with
It's much more likely that this is due to the update of dnsmasq
(https://launchpad.net/ubuntu/+source/dnsmasq/2.73-1):
juin 30 09:51:14 u32 NetworkManager[812]: dnsmasq not available on the
bus, can't update servers.
juin 30 09:51:14 u32 NetworkManager[812]: [1435650674.886674]
[dns-manager/nm
When you get the hang, could you please check pstree if you get
something like
\_ systemctl restart systemd-udevd.service
\_ /bin/systemd-tty-ask-password-agent --watch
\_ /usr/bin/pkttyagent --notify-fd 5 --fallback
? It's a shot into the dark, but this might be the same issue as bu
So systemd-tmpfiles-setup-dev.service ran fine (don't worry about the
"does not match any include prefix", that's debugging output from setup-
dev), but systemd-tmpfiles-setup.service never actually ran, it seems
its waiting for local-fs.target to get active, which never actually
happens. But if yo
Thanks. So systemd-update-utmp.service started in no time, this is a red
herring. The problem is this:
Jun 30 09:07:31 M2 systemd[1]: Job
dev-disk-by\x2duuid-bb8b6759\x2d8fdb\x2d4e4b\x2d879b\x2d7701cb217d2a.device/start
timed out.
Jun 30 09:07:31 M2 systemd[1]: Timed out waiting for device
dev-
@god, which Ubuntu release is this? I just noticed that our patch to
support user LXC regressed in 221 in wily (Ubuntu 15.10), I'll look at
this. If you use 15.04 (vivid) that's a separate problem.
But indeed it seems that lsh somehow reconfigures the cgroups, and/or
does not invoke PAM.
** Summa
Oh, so networking actually works again now? Then there's no need to
downgrade dnsmasq-base indeed. You can still do it to investigate the
ntp regresssion though -- from
https://launchpad.net/ubuntu/+source/dnsmasq/2.72-3.1build1 you select
your architecture, and from there you can download the olde
Indeed this sounds like one of the recent cryptswap bugs: bug 1447282,
bug 953875 (which are both fixed in -updates) and perhaps bug 1453738
(but this only applies to LVM which you don't seem to use). Please
copy&paste the output of
sudo blkid
ls -lR /dev/disk/by-uuid
grep -v '^#' /etc/fstab
401 - 500 of 4146 matches
Mail list logo
