On 4/10/15, shirish शिरीष wrote:
> in-line :-
> Yup. have turned off systemd.log_level=debug few months ago
turned on, sorry.
--
Regards,
Shirish Agarwal शिरीष अग्रवाल
My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://
in-line :-
On 4/9/15, Martin Pitt wrote:
> Hello shirish,
Hello Martin,
Thank you for taking time and helping out.
> shirish शिरीष [2015-04-09 21:37 +0530]:
>> Apr 09 13:42:55 debian systemd[1]: Failed to load configuration for
>> plymouth-start.service: No such file or directory
>> Apr 09 13:4
iTunes Lieber Kunde ,
Wir entschuldigen uns für die Unannehmlichkeiten, aber wir benötigen Ihre sofortige Aufmerksamkeit.
aufgrund einiger Probleme, die in unserem System aufgetreten sind, müssen wir Sie bitten, Ihren iTunes-Konto kontrollieren.
tun Sie es bitte innerhalb von 48 Stunden oder wir
Hello shirish,
shirish शिरीष [2015-04-09 21:37 +0530]:
> Apr 09 13:42:55 debian systemd[1]: Failed to load configuration for
> plymouth-start.service: No such file or directory
> Apr 09 13:42:55 debian systemd[1]: Failed to load configuration for
> plymouth-quit.service: No such file or director
Package: systemd
Version: 219-6
Severity: normal
Dear Maintainer,
Every time I boot or reboot into Debian with the new systemd (from
experimental) I get quite a number of messages where systemd tries to
get plymouth. I don't use plymouth as I like to see any and all
messages instead of a pretty pr
iTunes Lieber Kunde ,
Wir entschuldigen uns für die Unannehmlichkeiten, aber wir benötigen Ihre sofortige Aufmerksamkeit.
aufgrund einiger Probleme, die in unserem System aufgetreten sind, müssen wir Sie bitten, Ihren iTunes-Konto kontrollieren.
tun Sie es bitte innerhalb von 48 Stunden oder wir
Processing commands for cont...@bugs.debian.org:
> retitle 772272 systemd: Journalctl fail to print logs from user session
> without persistent journal
Bug #772272 [systemd] systemd: Journalctl fail to print logs from user session
Changed Bug title to 'systemd: Journalctl fail to print logs from
Am 20.11.2014 um 22:40 schrieb Simon McVittie:
> On Mon, 29 Sep 2014 at 11:06:06 +0200, Laurent Bigonville wrote:
>> Apparently there is still some kind of loop here.
>
> Piping the output of the attached script to tsort(1) says:
>
> tsort: -: input contains a loop:
> tsort: firewalld.service
> t
Your message dated Thu, 09 Apr 2015 14:22:57 +0200
with message-id <55266f21.7000...@debian.org>
and subject line Re: Bug#755844: libudev.so.0.13.0: Re: libudev.so.0.13.0:
applications crash in libudev (under memory pressure?)
has caused the Debian Bug report #755844,
regarding libudev.so.0.13.0:
We believe that the bug you reported is now fixed; the following
changes were made to the overrides...
Concerning package libsystemd-journal-dev...
Operating on the unstable suite
Changed priority from optional to extra
Changed section from libdevel to oldlibs
Thank you for reporting the bug, wh
Your message dated Thu, 09 Apr 2015 09:37:03 +
with message-id
and subject line Bug#766429: fixed in systemd 215-15
has caused the Debian Bug report #766429,
regarding sysstat service fails to start after installation without
daemon-reload
to be marked as done.
This means that you claim that
Your message dated Thu, 09 Apr 2015 09:37:03 +
with message-id
and subject line Bug#780711: fixed in systemd 215-15
has caused the Debian Bug report #780711,
regarding nspawn: getty restart loop
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
Your message dated Thu, 09 Apr 2015 09:37:03 +
with message-id
and subject line Bug#781602: fixed in systemd 215-15
has caused the Debian Bug report #781602,
regarding systemd: Invalid DBus call causes systemd to stop responding to DBus
alltogether
to be marked as done.
This means that you c
Your message dated Thu, 09 Apr 2015 09:37:03 +
with message-id
and subject line Bug#766429: fixed in systemd 215-15
has caused the Debian Bug report #766429,
regarding new services are not automatically picked up without explicit
systemctl daemon-reload
to be marked as done.
This means that
Your message dated Thu, 09 Apr 2015 09:37:03 +
with message-id
and subject line Bug#778608: fixed in systemd 215-15
has caused the Debian Bug report #778608,
regarding systemd: please consider backporting logind CAP_SYS_ADMIN fixes
to be marked as done.
This means that you claim that the prob
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 09 Apr 2015 10:12:37 +0200
Source: systemd
Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev
libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev
libsystemd-journal
systemd_215-15_amd64.changes uploaded successfully to localhost
along with the files:
systemd_215-15.dsc
systemd_215-15.debian.tar.xz
systemd_215-15_amd64.deb
systemd-sysv_215-15_amd64.deb
libpam-systemd_215-15_amd64.deb
libsystemd0_215-15_amd64.deb
libsystemd-dev_215-15_amd64.deb
l
17 matches
Mail list logo
