Bug#895292: Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm

Am 10.04.2018 um 02:15 schrieb Vincent Lefevre: > On 2018-04-09 20:41:55 +0200, Michael Biebl wrote: >> Not reproducible with a default GNOME / systemd as init installation. >> >> Please investigate, if this issue is specific to sysvinit, xfce or some >> other custom

Bug#895292: Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm

Control: severity -1 normal Control: tags -1 moreinfo unreproducible Am 09.04.2018 um 16:22 schrieb Vincent Lefevre: > Control: reassign -1 systemd 238-4 > Control: retitle -1 Restart, Suspend, Hibernate, Shut Down all greyed out in > lightdm > > On 2018-04-09 15:10:47 +0200, Vincent Lefevre

Bug#894605: systemd: System fails to suspend.

Control: tags -1 + moreinfo Am 02.04.2018 um 23:37 schrieb Michael Biebl: > Am 02.04.2018 um 10:20 schrieb Hubert Golembiowski: >> Package: systemd >> Version: 238-3 >> Severity: normal >> >> Dear Maintainer, >> >> Following issue observed: >

Bug#895239: [systemd] suspend works 1st time

Am 08.04.2018 um 19:56 schrieb Ted To: > Package: systemd > Version: 232-25+deb9u3 > Severity: important > > --- Please enter the report below this line. --- > > Suspend only works first time. It worked fine on an ancient Acer Aspire > One. Now on an Acer S7 392, suspend works on its first

Bug#892585: systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2

Am 05.04.2018 um 14:29 schrieb johnw: > Hi Michael, > > I found out, what cause the problem, > I have this line in fstab > "proc /proc proc rw,nosuid,nodev,noexec,relatime,hidepid=2,gid=4    > 0   0" > > I changed it to > "proc /proc proc rw,nosuid,nodev,noexec,relatime,hidepid=2    0  

Bug#894605: systemd: System fails to suspend.

Am 02.04.2018 um 10:20 schrieb Hubert Golembiowski: > Package: systemd > Version: 238-3 > Severity: normal > > Dear Maintainer, > > Following issue observed: > - Select "Suspend" from UI or close laptop lid (closing lid is set to trigger > suspend) > - System doesn't suspend but instead: >

Bug#830230: systemd disable wake-on-lan

On Tue, 19 Jul 2016 17:39:40 +0200 Norbert Schulz wrote: > > > Christian Hofstaedtler schrieb: > > * Norbert Schulz [160718 09:24]: > >> Here are the required and some more information. > > > > Thanks for following up on this. Unfortunately, I

Bug#883877: rsyslog: fails to configure, dpkg --configure exits with error

On Wed, 17 Jan 2018 05:20:49 +0200 =?UTF-8?Q?Martin=2D=C3=89ric_Racine?= <martin-eric.rac...@iki.fi> wrote: > 2018-01-17 4:24 GMT+02:00 Michael Biebl <bi...@debian.org>: > > On Tue, 19 Dec 2017 06:55:34 +0100 Michael Biebl <bi...@debian.org> wrote: > >> Am 19.

Accepted systemd 238-4 (source) into unstable

libsystemd0 libsystemd-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb Architecture: source Version: 238-4 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org> Changed-By: Michael Biebl <bi...@debian.org>

Bug#809069: logind sometimes blocks input to X after VT switch

Control: tags -1 + moreinfo Am 09.03.2017 um 06:40 schrieb Michael Biebl: > Hi Ben > > On Sat, 26 Dec 2015 22:44:45 + Ben Hutchings <b...@decadent.org.uk> > wrote: >> Package: systemd >> Version: 228-2 >> Severity: important >> >> After swi

Accepted systemd 232-25+deb9u3 (source) into proposed-updates->stable-new, proposed-updates

libsystemd-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb Architecture: source Version: 232-25+deb9u3 Distribution: stretch Urgency: medium Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org> Changed-By: Michael Biebl <bi...@debian.org>

Bug#893574: closed by Simon McVittie <s...@debian.org> (Re: Bug#893574: gnome-shell: Suspends after 20 minutes even if there is activity on a seat)

Control: reopen -1 Control: reassign -1 gnome-settings-daemon Control: found -1 3.28.0-1 Am 27.03.2018 um 11:23 schrieb floris: > Debian Bug Tracking System schreef op 2018-03-24 22:42: >> This is an automatic notification regarding your Bug report >> which was filed against the systemd package:

Bug#892585: systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2

> Mar 12 08:43:37 kvm102 slim[703]: pam_unix(slim:session): session opened for > user kaka by (uid=0) > Mar 12 08:43:37 kvm102 slim[703]: pam_systemd(slim:session): Failed to create > session: No such process Is see that the autopkgtest for logind fails as well: > autopkgtest [12:38:29]: test

Bug#810247: RE: Bug#810247: Hyper-V network adapters are mapped to a different interface (ethN) on every boot

On Sat, 9 Jan 2016 17:20:26 + Fernando Soto wrote: > Hi Martin, > > Udevadm output is attached. > > Thank you, > Fernando > > > -Original Message- > > From: Martin Pitt [mailto:mp...@debian.org] > > Sent: Saturday, January 09, 2016 10:45 AM > > To:

Bug#893054: systemd: System failed to boot after upgrade/install systemd from systemd:i386

Control: tags -1 + moreinfo On Mon, 19 Mar 2018 09:46:04 -0600 Jeff Ketchum wrote: > Second issue, I have trouble getting my system to boot reliably after the > changes. > It is using systemd:amd64 Ok, so what exactly is the failure then? Please describe it in more detail.

Bug#875557: Info received (Bug#875557: systemd: service mark as enabled but not in reality)

hm, the email address bounces here: > >The mail system > > : host mx.cblue.be[193.104.37.23] said: 550 Unrouteable > address (in reply to RCPT TO command) > > > > Reporting-MTA: dns; dd17218.kasserver.com > X-Postfix-Queue-ID: A90216801856 >

Bug#875557: systemd: service mark as enabled but not in reality

Control: tags -1 + moreinfo On Tue, 12 Sep 2017 10:08:49 +0200 Michael Biebl <bi...@debian.org> wrote: > Am 12.09.2017 um 09:45 schrieb sthiry: > > Package: systemd > > Version: 232-25+deb9u1 > > Severity: normal > > > > Hello, > > > > I use mu

Bug#803524: journalctl too slow

Control: tags -1 + moreinfo On Sat, 31 Oct 2015 01:46:59 +0100 Christoph Egger wrote: > Package: systemd > Version: 215-17+deb8u2 > Severity: normal > File: /bin/journalctl > > Hi! > > `journalctl -u nsd.service` just takes 10 minutes (!) cpu time to > scrol to the newest

Bug#892585: systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2

On Wed, 21 Mar 2018 16:16:40 +0800 johnw wrote: > After upgrade systemd to 238-3, I still have this problem :( > Any one? > Help, please. Does it work if you switch to a different display manager, like say lightdm (which IIRC is the preferred one of xfce). Might be a

Bug#893866: stretch-pu: package systemd/232-25+deb9u3

892794) + + -- Michael Biebl <bi...@debian.org> Fri, 23 Mar 2018 13:55:43 +0100 + systemd (232-25+deb9u2) stretch; urgency=medium * networkd: Handle MTU field in IPv6 RA (Closes: #878162) diff --git a/debian/patches/networkd-ndisc-handle-missing-mtu-gracefully-4913.patch b/debian/patches/ne

Bug#893605: warning: #warning "Consider adding the right mmap() syscall definitions here!" [-Wcpp]

Am 22.03.2018 um 12:31 schrieb James Cowgill: > I sent a patch upstream (see above). Thanks! -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature

Bug#893369: systemd-udevd is killed at startup

Am 22.03.2018 um 10:24 schrieb LEDUQUE Mickaël: > Ah yes. > I'm not sure you'll get much more from my system and logs now, can I > install systemd:amd64 back now ? Please go ahead and install systemd:amd64 again. -- Why is it that all of the instruments seeking intelligent life in the universe

Bug#893369: systemd-udevd is killed at startup

Am 19.03.2018 um 16:36 schrieb LEDUQUE Mickaël: > Start-Date: 2018-03-15 09:28:21 > Commandline: apt dist-upgrade [..] > Remove: bundler:amd64 (1.15.1-1), systemd:amd64 (237-4), > ruby-bundler:amd64 (1.15.1-1) > End-Date: 2018-03-15  09:28:29 > > Also it seems at some point I had systemd:amd64

Bug#893369: 893369

Am 21.03.2018 um 14:47 schrieb Michael Biebl: > Am 21.03.2018 um 13:18 schrieb Felix Defrance: > >> Start-Date: 2018-03-20  14:02:40 >> Commandline: apt full-upgrade >> Requested-By: fdef (1000) >> Install: libpam0g:i386 (1.1.8-3.7, automatic), libdevmapper

Bug#893369: 893369

Am 21.03.2018 um 13:18 schrieb Felix Defrance: > Start-Date: 2018-03-20  14:02:40 > Commandline: apt full-upgrade > Requested-By: fdef (1000) > Install: libpam0g:i386 (1.1.8-3.7, automatic), libdevmapper1.02.1:i386 > (2:1.02.145-4.1, automatic), libseccomp2:i386 (2.3.1-2.1, automatic), >

Accepted systemd 238-3 (source) into unstable

libsystemd0 libsystemd-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb Architecture: source Version: 238-3 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org> Changed-By: Michael Biebl <bi...@debian.org>

Bug#893602: macro.h:423:18: error: expected ')' before '__attribute__'

Control: forcemerge 893426 -1 On Tue, 20 Mar 2018 11:32:52 +0100 Mathieu Malaterre wrote: > ../src/basic/macro.h:423:18: error: expected ')' before '__attribute__' > #define noreturn __attribute__((noreturn)) ^ Duplicate of #893426 -- Why is it that all

Bug#883690: Buck-passing

Control: tags -1 moreinfo On Wed, 20 Dec 2017 11:10:18 +0100 (CET) Jan Fuchs wrote: > Hello Michael, > > After recompile systemd with patch in attachement then every boot is success I've forwarded this issue upstream, see https://github.com/systemd/systemd/issues/8483 It was

Bug#893369: systemd-udevd is killed at startup

Am 19.03.2018 um 09:51 schrieb LEDUQUE Mickaël: > You're right, but honestly, I have no idea how this happened : > > $ dpkg -l systemd > Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder > | >

Bug#883569: libpam-systemd: Prefer systemd-sysv over systemd-shim

On Thu, 8 Mar 2018 12:47:22 +0100 Martin Pitt <mp...@debian.org> wrote: > Hello Michael, > > Michael Biebl [2018-03-08 12:16 +0100]: > > Am 08.03.2018 um 09:22 schrieb Martin Pitt: > > There is one case: someone installs a minimal system without > > libpam-system

Bug#893054: systemd: System failed to boot after upgrade/install systemd from systemd:i386

Am 15.03.2018 um 23:31 schrieb Jeff Ketchum: > I upgraded systemd, and after a failure to boot, realized it was on > systemd:i386. > I went into a recovery environment and removed systemd:i386 and > installed systemd. > After that It failed to boot at a different location. > I was able to get it

Bug#893426: Processed: Re: Processed: Re: Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN

Control: tags -1 fixed-upstream patch Control: forwarded -1 https://github.com/systemd/systemd/pull/8456 Fixed upstream by https://github.com/systemd/systemd/commit/848e863acc51ecfb0f3955c498874588201d9130 -- Why is it that all of the instruments seeking intelligent life in the universe are

Bug#893369: systemd-udevd is killed at startup

Am 18.03.2018 um 22:41 schrieb LEDUQUE Mickaël: > No I don't think I have one > dpkg -l udev only shows udev and64 what about systemd? i386 or amd64 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description:

Bug#893369: systemd-udevd is killed at startup

Am 18.03.2018 um 22:33 schrieb LEDUQUE Mickaël: > Looks like commenting out > > SystemCallArchitectures=native > > fixes  the issue. Does that mean you have a udev:i386 installed on a amd64 system? If so, that would basically be a duplicate of #869719 -- Why is it that all of the

Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN

Control: reassign -1 libgpg-error-dev Control: found -1 1.28-1 Control: affects -1 + systemd Am 18.03.2018 um 19:54 schrieb Helmut Grohne: > Package: systemd > Version: 238-2 > Severity: serious > User: helm...@debian.org > Usertags: rebootstrap > > systemd fails to build from source on amd64.

Bug#893369: systemd-udevd is killed at startup

Am 18.03.2018 um 20:38 schrieb Mickaël Leduque: > Package: systemd > Version: 238-2 > Followup-For: Bug #893369 > > It didn't work so I just added the options in /etc/default/grub. > Here are the journal and the systemctl list-jobs output (which is just "no > jobs"). > Ok, thanks. Once you are

Bug#893369: systemd-udevd is killed at startup

Am 18.03.2018 um 18:50 schrieb LEDUQUE Mickaël: > I'll do all that, thanks. Do you know how I can set a correct keymap in > the grub "e" text editor ? I don't. But this is literally the first google hit regarding that question

Bug#893369: systemd-udevd is killed at startup

On Sun, 18 Mar 2018 12:14:41 +0100 =?utf-8?q?Micka=C3=ABl_Leduque?= wrote: > Package: systemd > Version: 238-2 > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > > After an update and a restart of the system, boot fails. It enters a loop, >

Bug#893282: systemd: SuccessAction=reboot in wrong stanza in /lib/systemd/system/system-update-cleanup.service

Am 17.03.2018 um 18:37 schrieb Michael Grant: > Package: systemd > Version: 238-2 > Severity: normal > > I noticed the following in the log file: > Mar 17 07:12:41 example systemd[1]: > /lib/systemd/system/system-update-cleanup.service:35: Unknown lvalue > 'SuccessAction' in section 'Service' >

Bug#886914: systemd: Kernel Panic on systemctl daemon-relaod, unit enable/disable when libvirt vms are running

On Thu, 11 Jan 2018 11:01:03 +0200 "Plamen K. Kosseff" wrote: > Package: systemd > Version: 236-2 > Severity: normal > > Dear Maintainer, > > > This is new debian buster install on HP z600 workstation (for hardware spec > see below). > The issue has manifested first during

Bug#870301: systemd: Touchpad fix Dell Inspiron Mini 1012

On Tue, 30 Jan 2018 04:30:58 -0500 (EST) bw wrote: > I'll go back and read your earlier posts, and see what I need to do. I > guess you are recommending that I upgrade systemd and use upstream bug > reporting instead of debian bugtracker? Yes, please upgrade to v238, try

Bug#884784: systemd-network segfaults

On Tue, 19 Dec 2017 19:50:49 +0200 =?utf-8?q?R=C3=A9mi_Denis-Courmont?= wrote: > Package: systemd > Version: 235-3 > Severity: critical > Justification: breaks unrelated software > > Dear Maintainer, > > systemd-networkd from version 236-1 systematically segfaults at

Bug#892321: attempts to suspend failing after crash

On Thu, 8 Mar 2018 10:02:32 + Daniel Pocock wrote: > Package: systemd > Version: 232-25+deb9u1 > Severity: important > > > Laptop was connected to a Thunderbolt dock, lid closed, using desktop > monitor and keyboard, everything connected through the dock.  It is a >

Bug#892989: weird chars found in dpkg output

Am 16.03.2018 um 08:45 schrieb Harald Dunkel: > On 03/15/18 18:46, Michael Biebl wrote: >> >> With a UTF-8 locale (which you really should enable), systemctl will use >> '→', for a non-UTF8 locale, systemctl will fall back to '->' >> >> > > Sorry to sa

Bug#893054: systemd: System failed to boot after upgrade/install systemd from systemd:i386

Am 15.03.2018 um 23:31 schrieb Jeff Ketchum: > Package: systemd > Version: 238-2 > Severity: normal > > > > -- Package-specific info: > > -- System Information: > Debian Release: buster/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > Foreign

Bug#892989: weird chars found in dpkg output

Am 15.03.2018 um 18:11 schrieb Michael Biebl: > Am 15.03.2018 um 14:38 schrieb Guillem Jover: > >> AFAIR, this is coming from systemd, and the character should be an >> arrow (→), but I assume there's some kind of locale/encoding problem >> somewhere. Perhaps even a

Bug#892989: weird chars found in dpkg output

Am 15.03.2018 um 14:38 schrieb Guillem Jover: > AFAIR, this is coming from systemd, and the character should be an > arrow (→), but I assume there's some kind of locale/encoding problem > somewhere. Perhaps even a misconfiguration in your system, but I'll > leave that up to the systemd

Re: Bug#767016: fixed in cron 3.0pl1-129

[systemd maintainer speaking here] Hi Javier On Sun, 11 Mar 2018 23:04:21 + =?utf-8?q?Javier_Fern=C3=A1ndez-Sanguino_Pe=C3=B1a?= wrote: >* debian/cron.init, debian/cron.service: Make sure cron is started last and > stopped first, with patch provided by Harald

Re: Bug#892730: nslcd: Please add systemd .service file

Am 12.03.2018 um 11:26 schrieb Laurent Bigonville: > Package: nslcd > Version: 0.9.9-1 > Severity: normal > User: pkg-systemd-maintainers@lists.alioth.debian.org > Usertags: systemd-units > > Hi, > > nslcd currently doesn't provides a systemd .service file. > > This is a problem as nslcd should

Bug#892585: systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2

Control: tags -1 moreinfo Am 11.03.2018 um 03:34 schrieb johnw: > Package: systemd > Version: 238-2 > Severity: important > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > I noticed, my system(xfce4, slim) can not create

Re: Starting powertop --auto-tune from systemd

Am 10.03.2018 um 18:55 schrieb Rainer Dorsch: > [Please follow-up to debian-user] > > Hello, > > I run > > /usr/bin/powertop --auto-tune > > to optimize the power consumption of my system. Running it manually works > nicely. When I try to run from systemd, I see no effect :-/ > > I followed

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

Am 11.03.2018 um 19:12 schrieb Francesco Poli: > My ~/.bash_logout is attached, but it's nothing special: it should be > identical to the one provided by the bash package in /etc/skel/ Can you comment out / remove the following three lines: if [ "$SHLVL" = 1 ]; then [ -x

Bug#888955: open-vm-tools.service 10.2.0 does not start on boot on jessie/stretch/etc

Am 10.03.2018 um 01:39 schrieb Bernd Zeimetz: > Hi, > > because it needs to run before cloud-init. Why does it need to run before cloud-init i.e. why does cloud-init need open-vm-tools? Feel free to point me to the relevant parts of the bug report which explain that. -- Why is it that all of

Accepted systemd 238-2 (source) into unstable

libsystemd0 libsystemd-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb Architecture: source Version: 238-2 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org> Changed-By: Michael Biebl <bi...@debian.org>

Bug#888955: open-vm-tools.service 10.2.0 does not start on boot on jessie/stretch/etc

On Fri, 2 Feb 2018 09:31:28 +0100 =?UTF-8?Q?Patrick_Matth=c3=a4i?= > for the public: > systemd does not start open-vm-tools at all in this scenario. If you > configure open-vm-tools.service to use DefaultDependencies=yes instead > of =no, it works as a workaround. Why does open-vm-tools.service

Bug#888955: open-vm-tools.service 10.2.0 does not start on boot on jessie/stretch/etc

On Wed, 31 Jan 2018 16:06:16 +0100 =?UTF-8?Q?Patrick_Matth=c3=a4i?= wrote: > Package: open-vm-tools > Version: 2:10.2.0-2 > Severity: important > > Dear Maintainer, > > here all systems on vSphere 6.0/6.5 fail to start open-vm-tools.service > on boot. > The only thing I

Bug#892360: systemd: Breaks also all my tested amd64 machines

Am 08.03.2018 um 18:31 schrieb Elimar Riesebieter: > * Michael Biebl <bi...@debian.org> [2018-03-08 17:09 +0100]: > >> Am 08.03.2018 um 17:05 schrieb Michael Biebl: >>> Control: tags -1 moreinfo >>> >>> Am 08.03.2018 um 16:23 schrieb valette:

Bug#892360: systemd pid 1 freezes at startup on x86 systems

Am 08.03.2018 um 18:27 schrieb Elimar Riesebieter: > * Michael Biebl <em...@michaelbiebl.de> [2018-03-08 17:05 +0100]: > >> Control: tags -1 moreinfo >> >> Am 08.03.2018 um 16:23 schrieb valette: >> >>> Kernel: Linux 4.14.23 (SMP w/2 CPU cores; PREEMP

Bug#892360: systemd: Breaks also all my tested amd64 machines

Am 08.03.2018 um 17:09 schrieb Michael Biebl: > Could you check if > https://github.com/systemd/systemd/issues/8387 > looks related > > I.e. if booting with systemd.unified_cgroup_hierarchy avoids the problem. If not, follow the instructions at https://freedesktop.org/wiki/S

Bug#892360: systemd: Breaks also all my tested amd64 machines

Am 08.03.2018 um 17:05 schrieb Michael Biebl: > Control: tags -1 moreinfo > > Am 08.03.2018 um 16:23 schrieb valette: > >> Kernel: Linux 4.14.23 (SMP w/2 CPU cores; PREEMPT) > > Is this also happening with a Debian provided kernel? > I see both you

Bug#892360: systemd: Breaks also all my tested amd64 machines

Control: tags -1 moreinfo Am 08.03.2018 um 16:23 schrieb valette: > Kernel: Linux 4.14.23 (SMP w/2 CPU cores; PREEMPT) Is this also happening with a Debian provided kernel? I see both you and Elimar use a custom one. Is this a virtualized environment or read hardware? Do you get a coredump? If

Bug#883569: libpam-systemd: Prefer systemd-sysv over systemd-shim

Am 08.03.2018 um 09:22 schrieb Martin Pitt: > Hello, > > Julian Andres Klode [2017-12-05 11:43 +0100]: >> libpam-systemd depending on systemd-shim first causes severe trouble with >> resolving dependencies, as APT picks systemd-shim but then later sees a >> package which needs systemd-sysv and

Bug#846377: discovered likely cause of this issue

Thanks Trent for further investigating this. Dirk, can you confirm that adding pam_keyinit.so to /etc/pam.d/systemd-user solves the problem for you as well? Am 08.03.2018 um 09:47 schrieb Trent Lloyd: > I believe I know the cause for this issue.  I ran into the same issue > when trying to use

Bug#892302: libpam-systemd: Does not recgonize serial consoles as part of a seat

On Wed, 07 Mar 2018 19:05:13 -0500 Matthew Gabeler-Lee wrote: > Package: libpam-systemd > Version: 232-25+deb9u1 > Severity: normal > > Various policykit actions that flag as for "active" or even "inactive", but > not "any", do not work from serial console sessions. After

Accepted systemd 238-1 (source) into unstable

libsystemd0 libsystemd-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb Architecture: source Version: 238-1 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org> Changed-By: Michael Biebl <bi...@debian.org>

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

Am 25.11.2015 um 22:20 schrieb Francesco Poli (wintermute): > Package: libpam-systemd > Version: 228-2 > Severity: normal > > Hello, > I noticed a weird bug that is possibly caused by libpam-systemd. > > Steps to reproduce (on a box with systemd as PID 1 process): > > 0) login on TTY1

Bug#891836: systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors

Control: reassign -1 postgresql Am 03.03.2018 um 11:16 schrieb Christoph Berg: > Re: To Michael Biebl 2018-03-03 <20180303085701.ga9...@msg.df7cb.de> >> In that case the error is in a config file, and marking the service as >> faulty makes sense. In the unit@instancetypo

Bug#891836: systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors

Am 02.03.2018 um 20:48 schrieb Christoph Berg: > "systemctl start foo.service" throws an error, but does not mark > foo.service as failed. > > If "systemctl start postgresql@foo.service" would not have > ConditionFileExists, it would permanently be marked as failed (until > "systemctl

Bug#891836: systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors

Am 02.03.2018 um 17:23 schrieb Christoph Berg: > Re: Michael Biebl 2018-03-02 <4c3431e8-36e3-d86b-4bb8-1f99eaa38...@debian.org> >> Am 02.03.2018 um 13:45 schrieb Christoph Berg: >> >>> I agree that it is not helpful that it doesn't raise an error here, >>>

Bug#891836: systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors

Am 02.03.2018 um 13:45 schrieb Christoph Berg: > I agree that it is not helpful that it doesn't raise an error here, > but I think it is working as intended by systemd. Or should we rather > be using AssertFileExists here? But starting the non-existing "foo" > service doesn't put "foo" into a

Bug#891836: systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors

Am 01.03.2018 um 20:35 schrieb Felipe Sateler: > On Thu, Mar 1, 2018 at 2:46 PM, Michael Biebl <bi...@debian.org> wrote: >> Control: tags -1 moreinfo unreproducible >> >> Am 01.03.2018 um 16:00 schrieb Martin von Wittich: >>> Hi Michael, >>> >>&g

Bug#891836: systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors

Control: tags -1 moreinfo unreproducible Am 01.03.2018 um 16:00 schrieb Martin von Wittich: > Hi Michael, > > On Thu, 1 Mar 2018 15:10:26 +0100 Michael Biebl <bi...@debian.org> wrote: >> I can't reproduce this, neither on v237 nor on v232: >> >> # systemc

Bug#891836: systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors

Control: tags -1 + moreinfo unreproducible Am 01.03.2018 um 13:24 schrieb Martin von Wittich: > Package: systemd > Version: 232-25+deb9u1 > Severity: normal > Tags: upstream > > Dear Maintainer, > > the following commands unexpectedly do not print any error messages or > return non-zero exit

Accepted systemd 237-4 (source) into unstable

libsystemd0 libsystemd-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb Architecture: source Version: 237-4 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org> Changed-By: Michael Biebl <bi...@debian.org>

Bug#891477: udev: MemoryDenyWriteExecute breaks gzip on i386

Control: reassign -1 gzip Control: forcemerge 890279 -1 Am 25.02.2018 um 23:22 schrieb Pascal Hambourg: > Error message: > > error while loading shared libraries: cannot restore segment prot after > reloc: Operation not permitted .. > Actually I am not sure whether this bug should be filed

Bug#891477: udev: MemoryDenyWriteExecute breaks gzip on i386

Am 25.02.2018 um 23:22 schrieb Pascal Hambourg: > Package: udev > Version: 232-25+deb9u1 > > This a follow-up to bug #855798 "udev: MemoryDenyWriteExecute=yes should > not be applied to udev plugins" which was closed because the affected > program was not part of Debian. Now it seems that gzip is

Accepted systemd 237-3~bpo9+1 (source) into stretch-backports

libsystemd0 libsystemd-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb Architecture: source Version: 237-3~bpo9+1 Distribution: stretch-backports Urgency: medium Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org> Changed-By: Michael Bie

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

On Tue, 20 Feb 2018 19:38:08 +0100 Gert Wollny <gw.foss...@gmail.com> wrote: > Am Dienstag, den 20.02.2018, 15:31 +0100 schrieb Michael Biebl: > > > > > Kernel: Linux 4.15.1-cm-fx6-my (SMP w/4 CPU cores; PREEMPT) > > > > > > Does this also happen w

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

Am 20.02.2018 um 12:40 schrieb Gert Wollny: > on an 32 bit arm system when the RTC is set to a wrong time booting the > system might > fail because systemd gets stuck in a loop printing "systemd[1]: Time has been > changed". > > The problem is known upstream and claimed to be a problem of the

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

Am 20.02.2018 um 13:57 schrieb Gert Wollny: > Am Dienstag, den 20.02.2018, 13:33 +0100 schrieb Michael Biebl: >> Am >> >>> make it lock up in this loop, but if someone can spoof this kind of >>> message and the system locks up because of this, wouldn't this be a

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

Am 20.02.2018 um 13:19 schrieb Gert Wollny: > Am Dienstag, den 20.02.2018, 12:56 +0100 schrieb Michael Biebl: >> Am 20.02.2018 um 12:40 schrieb Gert Wollny: >>> However, while upstream is certainly correct that a kernel bug is >>> the trigger of the lock

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

Am 20.02.2018 um 12:40 schrieb Gert Wollny: > However, while upstream is certainly correct that a kernel bug is the trigger > of > the lockup, systemd should not hang on this, because if sending messages to > systemd > can lock up the system then this is actually an attack vector for a DoS >

Bug#890824: Container: unsets cgroup memory limit on user login

Am 19.02.2018 um 13:09 schrieb Maximilian Philipps: > Package: systemd > Version: 232-25+deb9u1 > Severity: important > > Hi > > I have an issue with Systemd unsetting the memory limit for my container, > whereupon programs like free and htop report having access to 8 exabyte > of memory. > >

Bug#890095: systemd: Failed to start network time synchronization

Control: tags -1 + moreinfo On Sun, 11 Feb 2018 03:38:51 -0200 Carlos Donizete Froes wrote: > Package: systemd > Version: 236-3 > Severity: normal > > Dear Maintainer, > > At startup, the following failures appear: > > [FAILED] Failed to start network time

Bug#890265: systemd: journalctl compiled without pattern matching support

Am 12.02.2018 um 18:02 schrieb Calum Mackay: > Package: systemd > Version: 237-2 > Severity: normal > > Dear Maintainer, > > The -g/--grep option was recently added to the man page, but: > > $ journalctl --grep=blah > Compiled without pattern matching support > > this could be a

Bug#890659: systemd segfault in libsystemd-shared-232.so

See #890470 > Am 16.02.2018 um 20:09 schrieb Lukas Hejtmanek : > > Package: systemd > Version: 232-25+deb9u1 > Severity: important > Tags: patch > > > > -- Package-specific info: > > -- System Information: > Debian Release: 9.3 > APT prefers stable-updates > APT

Bug#890470: stretch-pu: package systemd/232-25+deb9u1

Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu Hi, I'd like to make a stable upload for systemd fixing a couple of issues. An annotated changelog follows. Full debdiff is attached. systemd (232-25+deb9u2) stretch;

Accepted systemd 237-3 (source) into unstable

libsystemd0 libsystemd-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb Architecture: source Version: 237-3 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org> Changed-By: Michael Biebl <bi...@debian.org>

Bug#873613: systemd gets confused at shutdown time

On Fri, 1 Dec 2017 10:39:33 +0100 Harald Dunkel wrote: > Hi Felipe, > > sorry for the delay. > > On 9/5/17 10:09 PM, Felipe Sateler wrote: > > > > > > On Mon, Sep 4, 2017 at 3:26 AM, Harald Dunkel > > wrote:

Bug#890436: systemd-sysv-install uses ROOT variable from environment for chrooting

Am 14.02.2018 um 18:32 schrieb Lars Michelsen: > Package: systemd > Version: 232-25+deb9u1 > Severity: normal > > systemd-sysv-install uses `ROOT` variable from environment when not set > via `-r` and tries to execute update-rc.d chrooted to the content of > this variable. Both CHROOT and ROOT

Accepted systemd 237-2 (source) into unstable

libsystemd0 libsystemd-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb Architecture: source Version: 237-2 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org> Changed-By: Michael Biebl <bi...@debian.org>

Bug#889144: systemd 237-1: problem starting dnsmasq

Am 07.02.2018 um 22:12 schrieb Jonathan de Boyne Pollard: > Michael Biebl: > >> If other services depend on dnsmasq, please keep >> https://www.lucas-nussbaum.net/blog/?p=877 in mind >> > Please do not.  It is an erroneous conclusion based upon a faulty > analysi

Re: Openvswitch must started before networking servise

On Mon, 16 Oct 2017 20:28:26 +0700 Fedor Goncharov wrote: > Package: openvswitch-switch > Version: 2.6.2~pre+git20161223-3 > Priority: critical > > The Openvswitch daemon must be started before the network.service. > Because when the initiation of the network started

Bug#889110: udev: extremely high cpu usage (overheats notebook after a minute of use)

Am 02.02.2018 um 04:50 schrieb Alex Henry: > Here's the "bluez" issue report > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889111 > > Hopefully the maintainers for both packages can communicate to identify > responsibilities and solve the issue. Thank you! Looks like neither a udev nor

Bug#886342: systemd-networkd: Unknown section 'Tap'. Ignoring.

Am 30.01.2018 um 15:15 schrieb Ritesh Raj Sarraf: > Hello Michael, > > On Tue, 2018-01-30 at 15:07 +0100, Michael Biebl wrote: >> Am 30.01.2018 um 15:01 schrieb Ritesh Raj Sarraf: >> >>> /etc/systemd/network/tap.netdev:5: Unknown section 'Tap'. Ignoring. >> >

Bug#888892: No permission on U2F security key

Am 30.01.2018 um 23:47 schrieb Kurt Roeckx: > There is no such package, but I do have u2f-host instaled, and so > libu2f-host0 and libhidapi-hidraw0. I also have libykpers-1-1 > installed that ships /lib/udev/rules.d/69-yubikey.rules Seems the package was named libu2f-udev, not libu2f-common.

Bug#888850: systemd-timesyncd fails to start

Control: forcemerge 887343 -1 Am 30.01.2018 um 17:12 schrieb John Williams: > Package: systemd > Version: 236-6 There is no such version in the archive? Please consider using reportbug next time, which will include correct version information and lots of diagnostic info which helps to triage

Bug#886342: systemd-networkd: Unknown section 'Tap'. Ignoring.

Am 30.01.2018 um 15:01 schrieb Ritesh Raj Sarraf: > /etc/systemd/network/tap.netdev:5: Unknown section 'Tap'. Ignoring. Please always share your full config files you use. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?

Bug#870301: systemd: Touchpad fix Dell Inspiron Mini 1012

On Tue, 10 Oct 2017 16:04:46 +0200 Michael Biebl <bi...@debian.org> wrote: > On Mon, 31 Jul 2017 20:44:17 -0400 (EDT) bw <bwtn...@yahoo.com> wrote: > > On Tue, 1 Aug 2017, Michael Biebl wrote: > > > It would be great if you can file this issue upstream at > >

Accepted systemd 237-1 (source) into unstable

libsystemd0 libsystemd-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb Architecture: source Version: 237-1 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org> Changed-By: Michael Biebl <bi...@debian.org>

  1   2   3   4   5   6   7   8   9   10   >