Hi again,
Am Sonntag, den 23.11.2014, 14:43 +0100 schrieb Andreas Messer:
Am Samstag, den 22.11.2014, 10:20 + schrieb Simon McVittie:
On Wed, 19 Nov 2014 at 21:29:33 +0100, Andreas Messer wrote:
I'm observing the same behavior on an x86_64 wheezy system running my
HTPC setup after
Control: reassign 760142 dbus
Control: forcemerge 769069 760142
On 01/12/14 19:58, Andreas Messer wrote:
Am Sonntag, den 23.11.2014, 14:43 +0100 schrieb Andreas Messer:
Am Samstag, den 22.11.2014, 10:20 + schrieb Simon McVittie:
That effectively reverts the problematic part of the changes
Am Donnerstag, den 20.11.2014, 03:15 +0200 schrieb Andrei POPESCU:
On Mi, 19 nov 14, 21:29:33, Andreas Messer wrote:
Unfortunately I can only attach a cut from messages and daemon, I don't
use the systemd journal.
Unless you deliberately set Storage=none in /etc/systemd/journald.conf
Am Samstag, den 22.11.2014, 10:20 + schrieb Simon McVittie:
On Wed, 19 Nov 2014 at 21:29:33 +0100, Andreas Messer wrote:
I'm observing the same behavior on an x86_64 wheezy system running my
HTPC setup after updating the system some weeks ago.
Andreas, I think your bug is #769069,
On Wed, 19 Nov 2014 at 21:29:33 +0100, Andreas Messer wrote:
I'm observing the same behavior on an x86_64 wheezy system running my
HTPC setup after updating the system some weeks ago.
Andreas, I think your bug is #769069, which is a recent regression:
your system is presumably much less slow
On Sat, Nov 22, 2014 at 11:20 PM, Simon McVittie s...@debian.org wrote:
On Wed, 19 Nov 2014 at 21:29:33 +0100, Andreas Messer wrote:
I'm observing the same behavior on an x86_64 wheezy system running my
HTPC setup after updating the system some weeks ago.
Andreas, I think your bug is
On Mi, 19 nov 14, 21:29:33, Andreas Messer wrote:
Unfortunately I can only attach a cut from messages and daemon, I don't
use the systemd journal.
Unless you deliberately set Storage=none in /etc/systemd/journald.conf
journald will have entries for the current boot (only). Please try if
On 01/09/14 22:55, Chris Tillman wrote:
Sep 02 09:44:00 debian dbus[767]: [system] Failed to activate service
'org.freedesktop.Avahi': timed out
Sep 02 09:44:01 debian dbus[767]: [system] Failed to activate service
'org.freedesktop.PolicyKit1': timed out
Sep 02 09:44:25 debian dbus[767]:
Chris, your Debian root filesystem appears to be on a USB-attached disk
(device ID 067b:2507, which according to
https://bbs.archlinux.org/viewtopic.php?id=58737 seems to be a
Prolific Technology, Inc. PL2507 Hi-speed USB to IDE bridge
controller). Please confirm whether this is the case?
Yes, it is installed on a USB hard disk. I mentioned it in the first
bug report I filed, but that one was rejected because I was
inadvertantly booting with the wrong kernel, and I forgot to mention
it in the second version. And yes, I think the timing issue could be
getting exacerbated because of
Package: systemd
Version: 208.8
(note: for some reason reportbug originally inserted the package and
version into the subject ...)
Dear Maintainer,
* What led up to the situation?
I installed from a testing CD downloaded in early August. I
ran into login problems, but discovered I
Am 01.09.2014 11:04, schrieb Chris Tillman:
Activation of org.freedesktop.systemd1 timed out
There are quite a few more D-Bus services besides
org.freedesktop.systemd1 which time out.
It seems also that all services which use Type=dbus in their .service
file enter the failed state.
So
On 9/1/14, Michael Biebl bi...@debian.org wrote:
Am 01.09.2014 11:04, schrieb Chris Tillman:
Activation of org.freedesktop.systemd1 timed out
There are quite a few more D-Bus services besides
org.freedesktop.systemd1 which time out.
It seems also that all services which use Type=dbus
13 matches
Mail list logo
