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: system
Keeping this bug for the message. This is just cosmetical, and entirely
independent of sddm not starting. Please file a bug against sddm for
that. Thanks!
** Summary changed:
- Starting version 219 "systemd-boot"
+ Shows "starting version 219" boot message even with quiet
** Summary changed:
-
Please have a look at /usr/share/doc/systemd/README.Debian and boot with
a debug shell. Please wait until it hangs, then run
systemctl list-jobs > /root/jobs.txt
journalctl -b > /root/journal.txt
and then attach the two files here. Thanks!
** This bug is no longer a duplicate of bug 1432171
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
--
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/1435126
Title:
slow boot: systemd-fsck Cannot communicate
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
Touch seeded p
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 to
The "duplicate line" is expected and just a red herring. It shouldn't
fail to start up; this smells like a duplicate of bug 1431107, can you
please have a look there and give me the output of "journalctl -b -p
warning"?
--
You received this bug notification because you are a member of Ubuntu
Touc
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
I reverted this for now. Building a package with that patch causes the
upgrade to hang (logind and other services don't restart) and boot to
fail. Did you test this on an installed desktop as well or just on the
live system?
** Changed in: systemd (Ubuntu)
Status: Fix Committed => Triaged
The boot hang reproduces with applying the patch on top of upstream v219
and installing the built "systemd".
--
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/1411140
Title:
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 change
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1420544
Title:
[SRU] Ubuntu instances on GCE should use
** Information type changed from Private to Public
** Summary changed:
- systemd-journald crashed with SIGABRT
+ systemd-journald crashed with SIGABRT in journal_file_move_to_object()
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
** Summary changed:
- systemd-journald crashed with SIGABRT in __epoll_wait_nocancel()
+ systemd-journald crashed with SIGABRT in sd_event_wait()
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs
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 mem
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 (Ub
** 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
--
Yo
> sudo shutdown -h now
> [ wait a couple of minutes, don't enter in one's password ]
Can you please clarify what you mean here? If you don't enter sudo's password,
then the actual command is irrelevant, and this would be a bug in sudo. Or do
you mean shutdown actually runs and you need some other
If this works under upstart, it's very likely that this is just another
fallout from bug 1432821. Can you please re-try this with current vivid?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
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 P-
I let sudo sit there without entering a password for about 10 minutes,
but it doesn't seem to time out. So I guess you don't mean the sudo
password but something else?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
** Changed in: systemd (Ubuntu)
Importance: Undecided => 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/1432197
Title:
[snappy] systemd-analyze plot not plotting ap
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
Status
*** This bug is a duplicate of bug 1430675 ***
https://bugs.launchpad.net/bugs/1430675
Treating it as a duplicate for now.
** This bug has been marked a duplicate of bug 1430675
fails to set up a bridged network interface
--
You received this bug notification because you are a member of
gravy45, this sounds like bug 953875 (or similar). Please file a new
bug, this is unrelated to this FFE and doesn't affect all installations
(i. e. it's specific to your system).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
We do use --enable-compat-libs. libsystemd-daemon.so.0 doesn't exist any
more as nothing in Ubuntu uses it any more. But as I said you can build
software whose ./configure is still checking for the old split out
libraries with libsystemd-login-dev and friends (and then it will end up
being linked a
Cristian, sorry I had been on vac for two weeks. For ssh you either need
to be able to ssh to a public host where I can ssh to as well (a server
of your's, a cloud instance, etc.) and forward your port 22, as you are
behind a NATed network. Or open port 22 on your router; but I guess that
isn't ava
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1435126
Title:
*** 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 /ru
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
ntu)
Status: Triaged => Fix Committed
** Changed in: open-iscsi (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 systemd in Ubuntu.
https://bugs.launchpad
I'll revert the systemd 219-4ubuntu7 changes on the next upload.
** Changed in: systemd (Ubuntu)
Status: Fix Released => 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
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1422070
Title:
systemd-tmp
Ah, sorry about that. Indeed I get this on my system as well.
I asked upstream about this on http://lists.freedesktop.org/archives
/systemd-devel/2015-March/029890.html
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
** Changed in: systemd (Ubuntu)
Status: New => Triaged
That's the error:
Setting up python-gi (3.14.0-1) ...
Traceback (most recent call last):
File "/usr/bin/pycompile", line 35, in
from debpython.version import SUPPORTED, debsorted, vrepr, \
File "/usr/share/python/debpython/version.py", line 24, in
from ConfigParser import SafeConfigP
These should still work (in mean in principle, the structure of the
files didn't change). After applying the rules, can you please do
udevadm info --export-db > /tmp/udev.txt
and attach /tmp/udev.txt here? Apparently you filed the bug without the
headset being connected.
** Changed in: systemd
IMHO the simplest fix would just be to call it with full path, i. e.
/sbin/upstart --user ... ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1435492
Title:
Xsession cra
** Changed in: wpa (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: wpa (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 network-manager in
Yes, I agree.
** Package changed: lightdm (Ubuntu) => upstart (Ubuntu)
** Changed in: upstart (Ubuntu)
Status: New => Triaged
** Summary changed:
- Xsession crash after login (fix for #678421 breaks)
+ Xsession.d script assumes that /sbin is in $PATH
--
You received this bug notificati
** 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/1411140
Title:
systemd-machine-id-commit.service fai
This sounds like bug 953875. Can you please give me the output of
systemd-analyze critical-chain
cat /etc/fstab
cat /etc/crypttab
sudo blkid
? Thanks!
** Summary changed:
- Tripled boot times - Virtualbox
+ cryptswap is hanging during boot
** Changed in: systemd (Ubuntu)
Status
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
Touch seeded packages, which is subsc
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 t
I tried this with Philip's config, but I still can't reproduce this, I'm
afraid. I launch a VM with two network cards, like this:
qemu-system-x86_64 -enable-kvm -m 2048 -snapshot -drive file=/srv/vm
/adt-vivid-amd64-cloud.img,if=virtio -net nic,model=virtio -net user
-net nic,vlan=1,macaddr=10:1
Please follow /usr/share/doc/systemd/README.Debian for debugging this
shutdown hang. In the debug shell, please do
journalctl -b > /root/journal.txt
and the next time you boot, attach /root/journal.txt here. Thanks!
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Incomplete
@Nick: The NFS unmount issue is bug 1431774.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1431998
Title:
stopping network-manager takes several seconds
Status i
Can you please try this:
sudo mv /lib/udev/rules.d/61-accelerometer.rules{,.disabled}
and check if that changes anything? If so, can you please give me the
output of
sudo SYSTEMD_LOG_LEVEL=debug /lib/udev/accelerometer
/devices/platform/lis3lv02d/input/input23
? (It was input23 in your log;
So who of the reporters still has this issue?
> It should work to add an After=dbus.service to
/lib/systemd/system/NetworkManager.service's [Unit] section, but that
smells like a workaround to me.
If you have, can you please try this workaround, if it resolves these
problems?
** Summary changed
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
syst
/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
Touch seeded packages,
ifup@.service is shipped by systemd, let's just add the After= there.
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (p
To clarify: even if this introduces a stronger boot ordering than
necessary, it's just a temporary solution until bug 1385414 lands. So
IMHO we should keep this simple.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown
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 in
> it sounds like you are saying that ifup@.service will always run
before networking comes up or NetworkManager.
Not necessarily. We need to make sure that all three run
After=apparmor.service. This is already the case for NetworkManager, but
not the other two.
** Changed in: systemd (Ubuntu)
Your dmesg contains that:
[ 8849.688210] [drm:intel_dp_complete_link_train [i915]] *ERROR* failed to
train DP, aborting
[ 9438.466017] [drm:intel_dp_complete_link_train [i915]] *ERROR* failed to
train DP, aborting
[ 9464.436928] [drm:intel_dp_complete_link_train [i915]] *ERROR* failed to
train
> $ journalctl -b -u systemd-logind.service
> No journal files were found.
Ah, apparently you are not in the "adm" group. Can you please re-try
with
sudo journalctl -b -u systemd-logind.service
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whi
The log shows that something requests the suspend over D-Bus. The most
probable candidate for this is logind. After this happens, can you
please copy&paste the output of "journalctl -f -b -u systemd-logind"
here? That should show key presses and which buttons it listens to.
To confirm that it's lo
Fixed both dependencies in http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=experimental&id=dd2f43c5bcb
** No longer affects: ifupdown (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a me
I can't fix that in general, as I don't know what causes these invalid
rc2.d/ to rc5.d/ links with rcS init scripts. But for /etc/init.d/lvm2
in particular we can avoid running this pointless dummy script at all, I
committed a change for this.
** Changed in: systemd (Ubuntu)
Status: Triaged
For the record, I don't see the behaviour from comment 1 with current
systemd any more.
--
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/1431200
Title:
daemon-reload runs al
Interesting.. so logind does *not* log a button event; here I get
something like
Mär 31 11:04:09 donald systemd-logind[805]: Power key pressed.
on a button event. Can you check if the bug happens:
1) if you just log into VT1 after boot, not into X, and run "sudo
systemctl stop lightdm"
2
jobs.txt shows that there are no outstanding jobs, and journal.txt shows
that the boot went all the way through. However, it seems you don't have
any display manager installed/configured? Do you known which one should
be running? lightdm/gdm/sddm etc.?
Please give me the output of
systemctl sta
I tried with apt-get install --reinstall systemd udev, several
"systemctl daemon-reexec" and "daemon-reload", but I just don't get this
bug any more. Unit193, do you?
** Changed in: systemd (Ubuntu)
Status: In Progress => Incomplete
** Changed in: systemd (Ubuntu)
Importance: High => Me
Colin, can you please get me a journalctl output without the workaround
when this happens? (see comment 3). Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/143
Colin: I meant with latest wpasupplicant (we already have previous
journals here)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1431774
Title:
network mount hangs
Ah, ok; Some more ideas:
- "sudo systemctl stop acpid", to rule out acpid and acpi-support
- install "evtest" and run "sudo evtest", select the lid switch, and
check if you actually get an event after ~ 3 minutes? I don't actually
expect one, as logind should then log a "Lid closed." event whi
Stopping D-Bus System Message Bus Socket.
A quick workaround is to add After=dbus.service to
/lib/systemd/system/NetworkManager.service's [Unit] section, but this
should be fixed in a more general fashion.
** Affects: dbus (Ubuntu)
Importance: High
Assignee: Martin Pitt (pitti)
@Colin: nevermind, I can reproduce the wrong shutdown ordering here now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1431774
Title:
network mount hangs on shutd
The original issue here was fixed in network-manager 0.9.10.0-4ubuntu11
(see comment 20), and that's what the bug title says too, so closing the
NetworkManager task again. The remaining issue, D-Bus stopping too
early, is tracked in bug 1438612.
** Changed in: network-manager (Ubuntu)
Statu
Actually, this isn't the full story, as NetworkManager doesn't tear down
interfaces when it shuts down. So Colin, I'm afraid I need a shutdown
journal output from current vivid after all..
** Changed in: dbus (Ubuntu)
Status: Triaged => Incomplete
** Summary changed:
- D-Bus stops too ear
@Colin: I need a journal after all, see bug 1438612. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1431774
Title:
network mount hangs on shutdown - Networ
Debugging notes:
- I see tons of "Refusing operation, as it is turned off" in the logs
now, which is due to the disabled HandleLidSwitch (before it was
"Suspending...")
- I see no event at all in evtest
- I believe stopping acpid does not help, I still see the "Refusing
operation..." messages
** Changed in: dbus (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1438612
Title:
remote file systems hang on shutdown
Status in db
Can you confirm that you have wpasupplicant 2.1-0ubuntu7 ? I. e. you
should see
$ systemctl cat wpa_supplicant.service |grep Before
Before=network.target
Your journal looks like it would stop wpa_supplicant before
network.target.
--
You received this bug notification because you are a member of
Andy gets this issue as well (http://paste.ubuntu.com/10711795/)
** Changed in: dbus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/143
*** This bug is a duplicate of bug 1438612 ***
https://bugs.launchpad.net/bugs/1438612
** This bug has been marked a duplicate of bug 1438612
remote file systems hang on shutdown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subsc
** Summary changed:
- remote file systems hang on shutdown
+ remote file systems hang on shutdown, D-BUS stops too early
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1438612
Andy, Colin, can you please revert the workaround in
/lib/systemd/system/NetworkManager.service (remove After=dbus.service),
and instead append these lines in /lib/systemd/system/dbus.service, to
the [Service] section:
ExecStop=/bin/true
KillMode=none
This makes things work in my tests, and is a
Lowering severity a bit. This only affects a particular piece of yet
unreleased hardware, and thus it isn't very widespread.
** Changed in: systemd (Ubuntu)
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is su
It's worth testing this with earlier kernels; do you have one where this
was known to work still? You shold still have some older kernels in the
grub boot menu, under "Advanced options".
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
--
You received this bug notification because you a
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,
reassign
@Joe: unduplicating then, following up on your original bug
--
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/1431200
Title:
daemon-reload runs alsa-restore.service and other
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 upgradin
I started a discussion with upstream in the linked fd.o bug, and
uploaded this in the meantime.
** Bug watch added: freedesktop.org Bugzilla #89847
https://bugs.freedesktop.org/show_bug.cgi?id=89847
** Also affects: dbus via
https://bugs.freedesktop.org/show_bug.cgi?id=89847
Importance:
This might actually be on purpose?
$ systemd-inhibit
[...]
Who: martin (UID 1000/martin, PID 2278/unity-settings-)
What: handle-lid-switch
Why: Multiple displays attached
Mode: block
I for one really welcome this. Finally my laptop stopped suspending when
it's sitting in the do
*** This bug is a duplicate of bug 953875 ***
https://bugs.launchpad.net/bugs/953875
** This bug has been marked a duplicate of bug 953875
Encrypted swap no longer mounted at bootup
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is su
Sorry, but there are tons of things which are broken in utopic with
systemd (e. g. every other package update will fail); we don't support
booting utopic or earlier with systemd. If you want to identify the
particular commit that fixes this, that's ok of course, but I'm afraid I
don't have time to
Can you reproduce it with (possibly several runs of) sudo systemctl
daemon-reload? If so, please attach "journalctl -b" afterwards. 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.launch
As for tracking systemd bugs I'd like to reduce importance, as we have
bug 1438249 for tracking the fallback for vivid. So this is mostly
optimization now, it shouldn't make a difference security wise, right?
Please set back to High if I misunderstood this. Thanks!
** Changed in: systemd (Ubuntu)
Iain, you said on IRC that you got a clean shutdown with
https://launchpad.net/ubuntu/+source/dbus/1.8.12-1ubuntu5 . Can you
confirm that this is stable now with several shutdowns? If so, this
would then be a duplicate of bug 1438612.
--
You received this bug notification because you are a member
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: syste
For the record, systemd actually checks for "docked/undocked" events, so
in a VT you should not actually get this behaviour. Only under Unity,
because unity-settings-daemon doesn't seem to check for dock events in
particular but just checks the connected monitors. Can you confirm this?
** Package
ttons), and most importantly event2 (sleep button).
It's also worthwhile copying my locally built systemd-logind, stopping
the system one, running the local one under gdb and breaking on
manager_handle_action().
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pi
Apport fixed upstream in r2941, thanks Brian!
** Changed in: apport (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: apport (Ubuntu)
Assignee: (unassigned) => Brian Murray (brian-murray)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
This happens around the time when this fires:
Breakpoint 1, manager_handle_action (m=0x55616010,
inhibit_key=INHIBIT_HANDLE_LID_SWITCH, handle=HANDLE_IGNORE,
ignore_inhibited=true, is_edge=false) at src/login/logind-action.c:36
36 in src/login/logind-action.c
(gdb) bt full
#0 mana
** Changed in: systemd (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
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/1438301
Title:
suspends after a
This looks like an effect of
http://cgit.freedesktop.org/systemd/systemd/commit/?id=ed4ba7e4f65215.
This introduced logic which deliberately checks for a closed lid and
suspends the machine again, to guard against wakeups which happen when a
laptop lid is closed (and the machine is potentially bein
At this point we have two options:
(1) fix the kernel or hardware to not claim that there's a closed lid
(2) disable that safety feature and cause some laptops to burn in your bag again
If possible, I'd like to keep this and fix (1), but if this turns out to
affect too many machines we might also
*** This bug is a duplicate of bug 1438612 ***
https://bugs.launchpad.net/bugs/1438612
This is most likely a duplicate of bug 1438612. If you still get this
problem in latest vivid, can you please yell here and provide the
journal output as in comment #3? I'll unduplicate it then. Thanks!
**
It's also not that easy to reproduce -- I don't see that string on
either my laptop nor my VMs, as plymouth makes that invisible. I don't
even see it when I boot without plymouth, i. e. drop "splash" from the
kernel command line.
--
You received this bug notification because you are a member of U
801 - 900 of 4146 matches
Mail list logo
