Processing control commands:
> tag 775404 patch
Bug #775404 [systemd] [systemd] networking.service does not start
Bug #775692 [systemd] [systemd] keymap.service does not start
Added tag(s) patch.
Added tag(s) patch.
--
775265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775265
775404: http:
Processing control commands:
> tag 775404 patch
Bug #775404 [systemd] [systemd] networking.service does not start
Bug #775692 [systemd] [systemd] keymap.service does not start
Ignoring request to alter tags of bug #775404 to the same tags previously set
Ignoring request to alter tags of bug #77569
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 backup/temporary
> files, i.e. the name of the
Hey Christian,
Christian Kastner [2014-12-28 21:55 +0100]:
> Trying to run as a user instance, but $XDG_RUNTIME_DIR is not set.
>
> I assume that this is because common-session also includes
> pam_systemd.so, whereas -noninteractive does not, so switching to the
> latter drops it from systemd-u
Processing commands for cont...@bugs.debian.org:
> tags 739676 + pending
Bug #739676 [systemd] systemd-user PAM config breaks some libpam-* modules
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
739676: http://bugs.debian.org/cgi-bin/bugrepo
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 fetchmai
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
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 'serv
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)
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 syst
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: http://bugs.d
Processing control commands:
> severity -1 important
Bug #774020 [systemd] systemd: black screen with backlight on start. rescue
mode plus Ctrl-D allows normal boot
Severity set to 'important' from 'critical'
--
774020: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774020
Debian Bug Tracking
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 im
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
l
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
libsystemd-journal
Your message dated Wed, 21 Jan 2015 13:04:39 +
with message-id
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 that you claim that the problem has bee
Your message dated Wed, 21 Jan 2015 13:04:39 +
with message-id
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 as done.
This means that you claim
Your message dated Wed, 21 Jan 2015 13:04:39 +
with message-id
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 marked as done.
This means that you clai
Your message dated Wed, 21 Jan 2015 13:04:39 +
with message-id
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 that the problem has been dealt with.
Your message dated Wed, 21 Jan 2015 13:04:39 +
with message-id
and subject line Bug#775404: fixed in systemd 215-10
has caused the Debian Bug report #775404,
regarding [systemd] networking.service does not start
to be marked as done.
This means that you claim that the problem has been dealt w
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 wi
Your message dated Wed, 21 Jan 2015 13:04:39 +
with message-id
and subject line Bug#775889: fixed in systemd 215-10
has caused the Debian Bug report #775889,
regarding breaks init scripts with .sh suffix
to be marked as done.
This means that you claim that the problem has been dealt with.
If
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
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.
>
>
Processing control commands:
> unmerge -1
Bug #775903 {Done: Martin Pitt } [systemd] systemd: 'service
initscript start' starts initscript.dpkg-dist under systemd
Bug #775404 {Done: Martin Pitt } [systemd] [systemd]
networking.service does not start
Bug #775692 {Done: Martin Pitt } [systemd] [sy
Processing commands for cont...@bugs.debian.org:
> reopen 775903
Bug #775903 {Done: Martin Pitt } [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 may need to re-add
Hi Martin,
On 2015-01-21 11:35, Martin Pitt wrote:
> On both my Debian sid and my Ubuntu system, the only difference
> between common-session and common-session-noninteractive is that the
> latter does not include libpam-systemd.
Generally speaking, I believe (but haven't verified) that this will
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: http://bugs.debian.org/cgi-bin/bu
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 mate-settings-daemon/1.
> 1. Init system installed on my system is systemd.
> root@localhost:~# ps -p1 f
> PID TTY STAT TIME COMMAND
> 1 ?Ss 0:03 /sbin/init
Well, that's a bit weird. On my systemd system, it looks like this.
glaubitz@z6:~> ps -p1 f
PID TTY STAT TIME COMMAND
1 ?S
On 01/21/2015 03:03 PM, Vlad Orlov wrote:
> Well, looking at the description, I see this is the same bug that has been
> found in various situations before [1][2][3].
Just out of curiosity, what init system are you using? Usually, these
weird bugs only occur when using something like systemd-shim
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: http://bugs.debian.org/cgi-bin/bugrep
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 repr
systemd_218-4_amd64.changes uploaded successfully to localhost
along with the files:
systemd_218-4.dsc
systemd_218-4.debian.tar.xz
systemd_218-4_amd64.deb
systemd-sysv_218-4_amd64.deb
libpam-systemd_218-4_amd64.deb
libsystemd0_218-4_amd64.deb
libsystemd-dev_218-4_amd64.deb
libsystem
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
libsystemd-journal
Your message dated Wed, 21 Jan 2015 15:22:03 +
with message-id
and subject line Bug#742048: fixed in systemd 218-4
has caused the Debian Bug report #742048,
regarding [systemd] FAILED to remount /
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Wed, 21 Jan 2015 15:22:02 +
with message-id
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 you claim that the problem has been
Your message dated Wed, 21 Jan 2015 15:22:03 +
with message-id
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 as done.
This means that you claim
Your message dated Wed, 21 Jan 2015 15:22:03 +
with message-id
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 that the problem has been dealt with.
Your message dated Wed, 21 Jan 2015 15:22:03 +
with message-id
and subject line Bug#775889: fixed in systemd 218-4
has caused the Debian Bug report #775889,
regarding breaks init scripts with .sh suffix
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Your message dated Wed, 21 Jan 2015 15:22:03 +
with message-id
and subject line Bug#775903: fixed in systemd 218-4
has caused the Debian Bug report #775903,
regarding sysv-generator: Do not create units for .dpkg-* files
to be marked as done.
This means that you claim that the problem has bee
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 coul
Your message dated Wed, 21 Jan 2015 15:22:03 +
with message-id
and subject line Bug#774335: fixed in systemd 218-4
has caused the Debian Bug report #774335,
regarding Provides: in SysV init scripts are not handled correctly, leading to
wrong orderings
to be marked as done.
This means that yo
Your message dated Wed, 21 Jan 2015 15:22:03 +
with message-id
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 claim that the problem has been dealt
Your message dated Wed, 21 Jan 2015 15:22:03 +
with message-id
and subject line Bug#775404: fixed in systemd 218-4
has caused the Debian Bug report #775404,
regarding [systemd] networking.service does not start
to be marked as done.
This means that you claim that the problem has been dealt wi
Hi Martin, hi Michael,
Martin Pitt 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 regular file
Your message dated Wed, 21 Jan 2015 16:53:13 +0100
with message-id <54bfcb69.2090...@debian.org>
and subject line Re: Bug#772856: Please backport .conf.d configuration
directory support from 218
has caused the Debian Bug report #772856,
regarding Please backport .conf.d configuration directory sup
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 t
Hi Daniel,
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 developer had posted
> a pa
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.
Hi Michael,
On Wed, Jan 21, 2015 at 06:56:50PM +0100, Michael Biebl wrote:
>Am 21.01.2015 um 17:13 schrieb Michael Biebl:
>> Am 15.01.2015 um 18:53 schrieb Daniel Edwards:
>>> It would be great if the package in wheezy could be fixed, as the systemd
>>> version from wheezy-backports (204) is not c
Do either of you know how often systemd-login retries, and how many times it
tries before giving up? What we could do is open the vt on demand, and then
close it after a timeout of non use.
--
Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God.
Phone: 1-613-726-0014 |
Dave Mielke, le Wed 21 Jan 2015 17:08:00 -0500, a écrit :
> Do either of you know how often systemd-login retries, and how many times it
> tries before giving up?
I don't think it retries.
Samuel
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-ma
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
[quoted lines by Samuel Thibault on 2015/01/22 at 00:46 +0100]
>Reading is fine, since it's done through /dev/vcsa, which doesn't count
>in VT_GETSTATE.
Not exactly. The tty device still needs to be opened in order to do things like
fetch the Unicode map.
It's possible, of course, that things l
Dave Mielke, le Wed 21 Jan 2015 18:56:42 -0500, a écrit :
> It's possible, of course, that things like the Unicode map, the screen font
> map, the character translation table, etc are common to all vts,
They are not :/
Samel
___
Pkg-systemd-maintainer
Package: systemd
Version: 215-8
First time reporting a bug to a core package, so I hope I've got everything
write.
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
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 db
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 boo
Didn't spot that dupe on the bug page, thanks for merging.
What exactly does systemd-logind do and why do I get the feeling it isn't
the only thing broken by lack of dbus?
Roll on kdbus I guess,
Michael
On Jan 22, 2015 5:32 PM, "Martin Pitt" wrote:
> Control: forcemerge 769728 -1
>
> Hey Micha
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/nee
>
> 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
64 matches
Mail list logo
