Am 21.01.2015 um 17:13 schrieb Michael Biebl:
Am 15.01.2015 um 18:53 schrieb Daniel Edwards:
I am running a Debian Wheezy system in a OpenVZ container and found that
systemd just shuts down when systemctl reboot is run. The container then
has to be started again via the control panel. A OpenVZ
Hi Martin, hi Michael,
Martin Pitt mp...@debian.org wrote:
I'm 99% sure that this is another duplicate of https://bugs.debian.org/775404
I take it you have a /run/systemd/generator.late/fetchmail.service
symlink which points to fetchmail.dpkg-dist.service?
Well, I have this file but it is a
controle: retitle -1 systemd: /run/log/journal is not readable by the adm group
Am 04.12.2014 um 14:00 schrieb Felipe Sateler:
I'm sorry I was unclear. The instructions in README.Debian are
perfectly fine. The problem is when persistent logging is not enabled,
as /run/log/journal does not
Hi Daniel,
Am 23.11.2014 um 19:02 schrieb Daniel Schepler:
I can't reproduce this with a vanilla pbuilder setup, so I'm not sure what's
causing the difference between the two builds.
Can you provide any steps how we can reproduce the issue?
Does this problem happen with a fresh checkout of
There's another case where brltty needs to see a vt when it isn't open. For
example, a command can be run asynchronously in a free vt via the openvt
command. After the command finishes, the output remains on the vt's screen even
though the vt itself has been closed. The user needs to still be
Dave Mielke, le Wed 21 Jan 2015 18:43:09 -0500, a écrit :
There's another case where brltty needs to see a vt when it isn't open. For
example, a command can be run asynchronously in a free vt via the openvt
command. After the command finishes, the output remains on the vt's screen
even
Processing control commands:
forcemerge 769728 -1
Bug #769728 [systemd] Logind does not start properly on freshly installed
minimal systems
Bug #772700 [systemd] systemd-logind.service fails to start if dbus is missing
Bug #775971 [systemd] systemd-logind is installed on minimal install, but
Control: forcemerge 769728 -1
Hey Michael,
Michael D [2015-01-22 5:29 +]:
When performing a new installation of Jessie using the current installer,
but without selecting anything on the tasksel screen (not even basic system
libraries), systemd-logind will error and fail to start on boot.
Michael D [2015-01-22 6:36 +]:
What exactly does systemd-logind do
See man systemd-logind(8) for a description. It also has some URLs at
the bottom for further docs.
and why do I get the feeling it isn't the only thing broken by lack
of dbus?
Could be; on a desktop you always want/need
but D-BUS is rather
uncommon in the server world (and a bit frowned upon, too).
I was just trying to figure out why some of my servers have it, and it
turns out openjdk-7-jdk depends on the non-headless JRE, which in turn
recommends some packages that depend on dbus.
I might open a bug for
Processing commands for cont...@bugs.debian.org:
tags 775889 + pending
Bug #775889 [systemd] breaks init scripts with .sh suffix
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
775889: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775889
Processing commands for cont...@bugs.debian.org:
tags 775404 + pending
Bug #775404 [systemd] [systemd] networking.service does not start
Bug #775692 [systemd] [systemd] keymap.service does not start
Bug #775903 [systemd] systemd: 'service initscript start' starts
initscript.dpkg-dist under
Processing control commands:
forcemerge 775404 775903
Bug #775404 [systemd] [systemd] networking.service does not start
Bug #775692 [systemd] [systemd] keymap.service does not start
Bug #775903 [systemd] systemd: 'service initscript start' starts
initscript.dpkg-dist under systemd
Added tag(s)
Control: forcemerge 775404 775903
Hey Florent,
Florent Rougon [2015-01-21 12:05 +0100]:
I tried systemd after a wheezy → sid upgrade and encountered an annoying
problem: after modifying a file related to my /etc/init.d/fetchmail script[1],
I decided to start the fetchmail service with
Package: systemd
Version: 215-9
Severity: serious
Tags: security
Dear maintainer,
I tried systemd after a wheezy → sid upgrade and encountered an annoying
problem: after modifying a file related to my /etc/init.d/fetchmail script[1],
I decided to start the fetchmail service with 'service
systemd_215-10_amd64.changes uploaded successfully to localhost
along with the files:
systemd_215-10.dsc
systemd_215-10.debian.tar.xz
systemd_215-10_amd64.deb
systemd-sysv_215-10_amd64.deb
libpam-systemd_215-10_amd64.deb
libsystemd0_215-10_amd64.deb
libsystemd-dev_215-10_amd64.deb
Processing commands for cont...@bugs.debian.org:
tags 775067 + pending
Bug #775067 [systemd] systemd: journald doesn't forward messages to syslog w/o
CAP_SYS_ADMIN (LXC)
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
775067:
Control: severity -1 important
This is still unreproducible, has no confirmations from other
reporters, does not cause actual damage or data loss, and does not
make the package completely unusable for everyone. Thus as per
https://www.debian.org/Bugs/Developer#severities I'm downgrading this
to
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 21 Jan 2015 13:18:05 +0100
Source: systemd
Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev
libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev
Hi,
Just out of curiosity, what init system are you using? Usually, these
weird bugs only occur when using something like systemd-shim and any
other of these hacky systemd work arounds.
Well, I have one system with systemd-shim + sysvinit-core and a few ones
with systemd as init. I can
Your message dated Wed, 21 Jan 2015 13:04:39 +
with message-id e1yduxb-0005qx...@franck.debian.org
and subject line Bug#739676: fixed in systemd 215-10
has caused the Debian Bug report #739676,
regarding systemd-user PAM config breaks some libpam-* modules
to be marked as done.
This means
Your message dated Wed, 21 Jan 2015 13:04:39 +
with message-id e1yduxb-0005r3...@franck.debian.org
and subject line Bug#775067: fixed in systemd 215-10
has caused the Debian Bug report #775067,
regarding systemd: journald doesn't forward messages to syslog w/o
CAP_SYS_ADMIN (LXC)
to be marked
Your message dated Wed, 21 Jan 2015 13:04:39 +
with message-id e1yduxb-0005r9...@franck.debian.org
and subject line Bug#775404: fixed in systemd 215-10
has caused the Debian Bug report #775404,
regarding systemd: 'service initscript start' starts initscript.dpkg-dist under
systemd
to be
Your message dated Wed, 21 Jan 2015 13:04:39 +
with message-id e1yduxb-0005r9...@franck.debian.org
and subject line Bug#775404: fixed in systemd 215-10
has caused the Debian Bug report #775404,
regarding [systemd] keymap.service does not start
to be marked as done.
This means that you claim
Hi
Am 21.01.2015 um 12:30 schrieb Martin Pitt:
Florent Rougon [2015-01-21 12:05 +0100]:
I tried systemd after a wheezy → sid upgrade and encountered an annoying
problem: after modifying a file related to my /etc/init.d/fetchmail
script[1],
I decided to start the fetchmail service with
Processing commands for cont...@bugs.debian.org:
tags 775903 + pending
Bug #775903 [systemd] sysv-generator: Do not create units for .dpkg-* files
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
775903:
Control: unmerge -1
Control: severity -1 normal
Control: retitle -1 sysv-generator: Do not create units for .dpkg-* files
Hey Michael,
Michael Biebl [2015-01-21 14:05 +0100]:
This bug is related, but might be considered a bug on its own, regarding
handling of temporary/backup conffiles.
See
Processing commands for cont...@bugs.debian.org:
tags 775903 - security
Bug #775903 [systemd] sysv-generator: Do not create units for .dpkg-* files
Removed tag(s) security.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
775903:
Hi,
Am 21.01.2015 um 10:52 schrieb Martin Pitt:
Control: tag 775404 patch
Michael Biebl [2015-01-20 17:56 +0100]:
I looked into this a bit more myself. Unfortunately, those .sh suffixes
are not the only ways to trigger this particular bug.
As can be seen in [1], this can also be caused by
Processing commands for cont...@bugs.debian.org:
reopen 775903
Bug #775903 {Done: Martin Pitt mp...@debian.org} [systemd] sysv-generator: Do
not create units for .dpkg-* files
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you
Processing commands for cont...@bugs.debian.org:
reassign 772910 libpam-systemd 215-8
Bug #772910 [mate-settings-daemon] mate-settings-daemon: Massive memory leak
Bug reassigned from package 'mate-settings-daemon' to 'libpam-systemd'.
No longer marked as found in versions
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 21 Jan 2015 15:57:50 +0100
Source: systemd
Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev
libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev
Your message dated Wed, 21 Jan 2015 15:22:02 +
with message-id e1ydx6y-0005w0...@franck.debian.org
and subject line Bug#739676: fixed in systemd 218-4
has caused the Debian Bug report #739676,
regarding systemd-user PAM config breaks some libpam-* modules
to be marked as done.
This means that
Your message dated Wed, 21 Jan 2015 15:22:03 +
with message-id e1ydx6z-0005wn...@franck.debian.org
and subject line Bug#775067: fixed in systemd 218-4
has caused the Debian Bug report #775067,
regarding systemd: journald doesn't forward messages to syslog w/o
CAP_SYS_ADMIN (LXC)
to be marked
Your message dated Wed, 21 Jan 2015 15:22:03 +
with message-id e1ydx6z-0005wz...@franck.debian.org
and subject line Bug#775404: fixed in systemd 218-4
has caused the Debian Bug report #775404,
regarding [systemd] keymap.service does not start
to be marked as done.
This means that you claim
On 01/21/2015 04:03 PM, Vlad Orlov wrote:
Well, I have one system with systemd-shim + sysvinit-core and a few ones
with systemd as init. I can reproduce the issue (as I described in [1] ) in
all
of them.
Ok, I just followed your steps to reproduce on a clean Jessie
installation and I
Your message dated Wed, 21 Jan 2015 15:22:03 +
with message-id e1ydx6z-0005wt...@franck.debian.org
and subject line Bug#775331: fixed in systemd 218-4
has caused the Debian Bug report #775331,
regarding systemd: Please enable AppArmor support again
to be marked as done.
This means that you
37 matches
Mail list logo
