Bug#823577: marked as done (systemd: Systemd-215 does not setup per-session cgroups for each resource type)

Your message dated Tue, 2 Jan 2018 00:38:17 +0100 with message-id <106b4109-64f0-e8d8-ae2a-efa975df8...@debian.org> and subject line Re: Bug#823577: Patches has caused the Debian Bug report #823577, regarding systemd: Systemd-215 does not setup per-session cgroups for each resource type to be

Processed: tagging 884506

Processing commands for cont...@bugs.debian.org: > tags 884506 + pending Bug #884506 [systemd] systemd: "systemd-analyze plot" fails for root Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 884506:

Processed: tagging 869354

Processing commands for cont...@bugs.debian.org: > tags 869354 + pending Bug #869354 [systemd] systemd: Overwrites local config without warning Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 869354:

Bug#807041: 807041

On Sun, 13 Dec 2015 15:48:20 + "George B." wrote: > tags 807041 - moreinfo This was closed upstream as being fixed. Can you please retry if you still run into this issue with a recent version of systemd. Thanks, Michael -- Why is it that all of the instruments seeking

Processed: tagging 885061

Processing commands for cont...@bugs.debian.org: > tags 885061 + pending Bug #885061 [systemd] systemd-timesyncd.service fails to start if static user is removed, but group is retained Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 885061:

Bug#884258: marked as done (machinectl shell should use bash as a default)

Your message dated Tue, 2 Jan 2018 00:05:48 +0100 with message-id <5349098c-c2d2-ca72-01ee-202de78df...@debian.org> and subject line Re: machinectl shell should use bash as a default has caused the Debian Bug report #884258, regarding machinectl shell should use bash as a default to be marked as

Bug#886053: override: libudev1:libs/optional

Package: ftp.debian.org Severity: normal With the recent changes in debian policy, libudev1 is now flagged as https://lintian.debian.org/tags/excessive-priority-for-library-package.html Please downgrade libudev1 to optional. I'll make the corresponding change in debian/control in the next

Bug#885325: Similar issue: Mount points not found by apache2 and another services

Michael, thanks for working on this and reporting to upstream. Meanwhile I've mounted the mount points over tty1 and they are indeed propagated to all services. But I think you already figured it out as you tried to reproduce the bug. For someone who doesn't have access to tty, the nsenter

Bug#884788: systemd-ask-password echos password as stars (*) while decrypting LUKS partition

Am 20.12.2017 um 10:41 schrieb root kea: > On Wed, Dec 20, 2017 at 4:46 AM, Michael Biebl wrote: > >> I think this is intentional behaviour, so you'll easily spot that your >> input system works > > The current implementation is that the password gets echoed to > terminal as

Processed: tagging 885325

Processing commands for cont...@bugs.debian.org: > tags 885325 - moreinfo Bug #885325 [systemd] systemd: Daemon start with systemctl start daemon can not find mount point not mounted by boot Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#885325: Similar issue: Mount points not found by apache2 and another services

Am 29.12.2017 um 13:03 schrieb Sumit Madan: > I'll try that tomorrow evening and inform you; I'm not at home > currently. But what I can tell is that the behavior over SSH has been > changed. In the past I often created mounts over SSH. My guess is that this is related to this upstream change

Processed: bug 885325 is forwarded to https://github.com/systemd/systemd/issues/7761

Processing commands for cont...@bugs.debian.org: > forwarded 885325 https://github.com/systemd/systemd/issues/7761 Bug #885325 [systemd] systemd: Daemon start with systemctl start daemon can not find mount point not mounted by boot Set Bug forwarded-to-address to

Bug#885325: Similar issue: Mount points not found by apache2 and another services

I'll try that tomorrow evening and inform you; I'm not at home currently. But what I can tell is that the behavior over SSH has been changed. In the past I often created mounts over SSH. On December 29, 2017 10:32:06 AM GMT+01:00, Michael Biebl wrote: >Am 29.12.2017 um 01:28

Bug#885325: Similar issue: Mount points not found by apache2 and another services

Am 29.12.2017 um 01:28 schrieb Sumit Madan: > Do you have an idea how to propagate the mount points created in an ssh > session to other namespaces? Just to clarify: This issue only happens if you login via SSH? If you login locally, e.g. on tty1, the manually mounted mount points are visible

Bug#885318: systemd kills X or freezes it when logging out from last opened tty

Control: reassign -1 xserver-xorg-core Control: forcemerge 810660 -1 Am 29.12.2017 um 09:30 schrieb Awtul: > Changingif [ "$SHLVL" = 1 ] in .bash_logout to if [ "$SHLVL" = 2 ] > > solves my problem; now X doesn't crash and I can switch between my openbox > session (on tty1) > and other

Processed: Re: Bug#885318: systemd kills X or freezes it when logging out from last opened tty

Processing control commands: > reassign -1 xserver-xorg-core Bug #885318 [systemd] systemd kills X or freezes it when logging out from last opened tty Bug reassigned from package 'systemd' to 'xserver-xorg-core'. No longer marked as found in versions systemd/236-1. Ignoring request to alter

Processed: tagging 885318

Processing commands for cont...@bugs.debian.org: > tags 885318 = Bug #885318 [systemd] systemd kills X or freezes it when logging out from last opened tty Removed tag(s) unreproducible and moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 885318:

Bug#885318: systemd kills X or freezes it when logging out from last opened tty

Am 29.12.2017 um 08:55 schrieb Michael Biebl: > Which shell do you use as user shell. If it is bash, how does > ~/.bash_logout look like? > > Is the problem gone if you edit ~/.bash_logout as suggested in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858073#10 Fwiw, my ~/.bash_logout

Bug#885318: systemd kills X or freezes it when logging out from last opened tty

Package: systemd Version: 236-1 Followup-For: Bug #885318 - my user shell is bash (echo $SHELL > /bin/bash) - .bash_logout: if [ "$SHLVL" = 1 ]; then [ -x /usr/bin/clear_console ] && /usr/bin/clear_console -q fi -- Changingif [

Bug#885318: (no subject)

Subject: Re: systemd kills X or freezes it when logging out from last opened tty Followup-For: Bug #885318 Package: systemd Version: 236-1 The Xorg.0.log.old (of my debian Sid vm) I joined is a fresh one; logged just after X "crash". ___

Bug#885318: systemd kills X or freezes it when logging out from last opened tty

Am 29.12.2017 um 08:43 schrieb Awtul: > Package: systemd > Followup-For: Bug #885318 > > Hi, > > I may have reported this bug against the wrong package (systemd); I apologize > if that is the case (?). > I wonder if this bug should be merged with #858073 & #791342. > I tried to reproduce with

Bug#885318: systemd kills X or freezes it when logging out from last opened tty

Package: systemd Followup-For: Bug #885318 Hi, I may have reported this bug against the wrong package (systemd); I apologize if that is the case (?). I wonder if this bug should be merged with #858073 & #791342. I tried to reproduce with fvwm and jwm but I wasn't able to do so; the issue I

Bug#885325: systemd: Daemon start with systemctl start daemon can not find mount point not mounted by boot

Forget to CC bug(#885325) tracker :) Michael Biebl 於 2017-12-29 04:33 寫到: Can you please break that down into a minimal test case which would allow to reproduce the problem. OK, create mount point /disk, in my case is encrypted by luks, and not mount on boot. After the system boot up, ssh

Bug#885325: Similar issue: Mount points not found by apache2 and another services

Dear Maintainer, I've got a similar issue with mount points that are mounted manually after the boot process is completed. As John reports these mount points are not reachable anymore from other services. In his case smbd and in my case apache2 is affected. I think the issue here is with

Bug#885318: systemd kills X or freezes it when logging out from last opened tty

control: tags -1 + unreproducible Am 28.12.2017 um 21:35 schrieb Michael Biebl: >> Please, let me know if you need more info/details. > > Why do you suspect it is systemd which kills your X session? > Can you provide logs or error messages which would confirm such a guess? I tried to reproduce

Processed: Re: Bug#885318: systemd kills X or freezes it when logging out from last opened tty

Processing control commands: > tags -1 + unreproducible Bug #885318 [systemd] systemd kills X or freezes it when logging out from last opened tty Added tag(s) unreproducible. -- 885318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885318 Debian Bug Tracking System Contact

Bug#885318: systemd kills X or freezes it when logging out from last opened tty

Control: tags -1 + moreinfo Am 26.12.2017 um 07:56 schrieb Nekki Nekki: > Package: systemd > Version: 236-1 > Severity: critical > > Dear maintainers, > > When using startx (no DM enabled) I suspect that systemd logs me out > from my X session > if it doesn't freezes it. I try to explain: I

Processed: Re: Bug#885318: systemd kills X or freezes it when logging out from last opened tty

Processing control commands: > tags -1 + moreinfo Bug #885318 [systemd] systemd kills X or freezes it when logging out from last opened tty Added tag(s) moreinfo. -- 885318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885318 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#885325: systemd: Daemon start with systemctl start daemon can not find mount point not mounted by boot

Control: tags -1 + moreinfo Am 26.12.2017 um 09:30 schrieb John Wong: > Package: systemd > Version: 236-1 > Severity: important > > Dear Maintainer, > > After upgrade systemd* to 236-1, I noticed nfsd/smbd can not share some > mount point, > which is not mounted on boot (eg: luks

Processed: Re: Bug#885325: systemd: Daemon start with systemctl start daemon can not find mount point not mounted by boot

Processing control commands: > tags -1 + moreinfo Bug #885325 [systemd] systemd: Daemon start with systemctl start daemon can not find mount point not mounted by boot Added tag(s) moreinfo. -- 885325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885325 Debian Bug Tracking System Contact

Bug#885446: marked as done (systemd: user processes remain after logout)

Your message dated Wed, 27 Dec 2017 09:28:41 +0100 with message-id and subject line Re: Bug#885446: systemd: user processes remain after logout has caused the Debian Bug report #885446, regarding systemd: user processes remain after logout to be

Bug#885446: systemd: user processes remain after logout

Package: systemd Version: 236-1 Severity: important Is there any legitimate reason why after logging out of an XFCE session, all these desktop processes should remain alive? # ps axfu | grep ^ian ian 1687 0.0 0.0 80544 8384 ?Ss 19:35 0:00 /lib/systemd/systemd --user ian

Processed: severity of 883680 is normal

Processing commands for cont...@bugs.debian.org: > severity 883680 normal Bug #883680 {Done: Michael Biebl } [systemd] systemd: Compiling systemd-232.25 debian rules override_dh_auto_test fails Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please

Processed: severity of 885318 is normal

Processing commands for cont...@bugs.debian.org: > severity 885318 normal Bug #885318 [systemd] systemd kills X or freezes it when logging out from last opened tty Severity set to 'normal' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 885318:

Bug#885318: systemd kills X or freezes it when logging out from last opened tty

Package: systemd Version: 236-1 Severity: critical Dear maintainers, When using startx (no DM enabled) I suspect that systemd logs me out from my X session if it doesn't freezes it. I try to explain: I login in my openbox session on tty1 using startx, and in tty2 I run some program, say 'moc'.

Processed: Re: Bug#885201: systemd-cryptsetup-generator: incorrectly reports “Out of memory”

Processing control commands: > forwarded -1 https://github.com/systemd/systemd/pull/7688 Bug #885201 [systemd] systemd-cryptsetup-generator: incorrectly reports “Out of memory” Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/pull/7688'. -- 885201:

Bug#885201: systemd-cryptsetup-generator: incorrectly reports “Out of memory”

Control: forwarded -1 https://github.com/systemd/systemd/pull/7688 Would be great if you can try the upstream patch and verify that it fixes the issue. Am 26.12.2017 um 00:04 schrieb Ben Finney: > There is a patch suggested for the bug in SystemD Please write "systemd" in the future:

Processed: Re: Bug#885201: systemd-cryptsetup-generator: incorrectly reports “Out of memory”

Processing control commands: > tags -1 + patch Bug #885201 [systemd] systemd-cryptsetup-generator: incorrectly reports “Out of memory” Added tag(s) patch. -- 885201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#885201: systemd-cryptsetup-generator: incorrectly reports “Out of memory”

Control: tags -1 + patch The Arch Linux forums have a report for this bug also . As discussed there, once the system fails to boot, at the emergency shell the ‘/usr/lib/systemd/systemd-cryptsetup attach’ command runs without any problem. There is a

Bug#885201: systemd-cryptsetup-generator: incorrectly reports “Out of memory”

Package: systemd Version: 236-1 Severity: important The host fails to start up because encrypted volumes depend on cryptsetup. When ‘systemd-cryptsetup-generator’ runs during boot, the following error appears: systemd-cryptsetup-generator[320]: Out of memory and all dependencies that

Bug#885061: systemd-timesyncd.service fails to start if static user is removed, but group is retained

On Sat, Dec 23, 2017 at 11:35:44AM +0100, Michael Biebl wrote: > Am 23.12.2017 um 09:26 schrieb Martin Dickopp: > > Following the instructions in /usr/share/doc/systemd/NEWS.Debian.gz > > > > DynamicUser=yes has been enabled for systemd-journal-upload.service, > >

柠市重娦巳觉掎 来吧 332418点C0M邀您注冊嶺⑤8赢5⒏0提+K服Q295019338嶺

___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#885061: systemd-timesyncd.service fails to start if static user is removed, but group is retained

Am 23.12.2017 um 09:26 schrieb Martin Dickopp: > Package: systemd > Version: 236-1 > Severity: normal > > Hi, > > Following the instructions in /usr/share/doc/systemd/NEWS.Debian.gz > > DynamicUser=yes has been enabled for systemd-journal-upload.service, > systemd-journal-gatewayd.service

Bug#885061: systemd-timesyncd.service fails to start if static user is removed, but group is retained

Package: systemd Version: 236-1 Severity: normal Hi, Following the instructions in /usr/share/doc/systemd/NEWS.Debian.gz DynamicUser=yes has been enabled for systemd-journal-upload.service, systemd-journal-gatewayd.service and systemd-timesyncd.service. This means we no longer need to

systemd 236-1 MIGRATED to testing

FYI: The status of the systemd source package in Debian's testing distribution has changed. Previous version: 235-3 Current version: 236-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive

Processed: Re: Bug#884994: systemd: shutdown does not send its warning messages when time is more than ten minutes

Processing control commands: > tags -1 moreinfo Bug #884994 [systemd] systemd: shutdown does not send its warning messages when time is more than ten minutes Added tag(s) moreinfo. > severity -1 normal Bug #884994 [systemd] systemd: shutdown does not send its warning messages when time is more

Bug#884994: systemd: shutdown does not send its warning messages when time is more than ten minutes

Control: tags -1 moreinfo Control: severity -1 normal Am 22.12.2017 um 17:00 schrieb Christoph Pleger: > Package: systemd > Version: 215-17+deb8u7 > Severity: important > > Dear maintainers, > > The command 'shutdown -h +$time" does not send its repeated warning > messages to logged in users

Bug#884994: systemd: shutdown does not send its warning messages when time is more than ten minutes

Package: systemd Version: 215-17+deb8u7 Severity: important Dear maintainers, The command 'shutdown -h +$time" does not send its repeated warning messages to logged in users when $time is greater than 10, but sends it only once - directly after entering the shutdown command. That is a

Processed: [bts-link] source package systemd

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package systemd > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to

[bts-link] source package systemd

# # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #884506 (http://bugs.debian.org/884506) # Bug title: systemd: "systemd-analyze plot"

Bug#884784: systemd-network segfaults

Am 20.12.2017 um 17:35 schrieb Rémi Denis-Courmont: > Le keskiviikkona 20. joulukuuta 2017, 0.05.02 EET Michael Biebl a écrit : >> Please try to provide a backtrace of the crash. > > eth0: Gained IPv6LL > > Program received signal SIGSEGV, Segmentation fault. ... >> That kernel is not provided

Bug#884258: machinectl shell should use bash as a default

On Wed, 13 Dec 2017 01:26:00 +0100 Michael Biebl wrote: > Am 13.12.2017 um 00:30 schrieb Marco d'Itri: > > Package: systemd-container > > Version: 235-3 > > Severity: normal > > > > Until https://github.com/systemd/systemd/issues/1395 will be fixed, > > machinectl should be

Processed: your mail

Processing commands for cont...@bugs.debian.org: > tags 884784 - moreinfo Bug #884784 [systemd] systemd-network segfaults Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 884784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884784

Bug#883690: Buck-passing

Hello Michael, After recompile systemd with patch in attachement then every boot is success and systemd is alive. Best Regards Jan -- http://www.fuky.org*** orig/systemd-234/src/core/manager.c Wed Jul 12 16:01:10 2017 --- src/core/manager.c Wed Dec 20 10:49:11 2017 *** ***

Bug#884788: systemd-ask-password echos password as stars (*) while decrypting LUKS partition

On Wed, Dec 20, 2017 at 4:46 AM, Michael Biebl wrote: > I think this is intentional behaviour, so you'll easily spot that your > input system works The current implementation is that the password gets echoed to terminal as star(*) characters by default and one needs to press

Bug#884788: systemd-ask-password echos password as stars (*) while decrypting LUKS partition

Am 19.12.2017 um 19:33 schrieb Avinash Sonawane: > Package: systemd > Version: 232-25+deb9u1 > Severity: normal > > Dear Maintainer, > > I have encrypted swap and /home. When the system starts it asks password to > decrypt swap. The password doesn't get echoed at all. Totally expected >

Processed: Re: Bug#884784: systemd-network segfaults

Processing control commands: > severity -1 important Bug #884784 [systemd] systemd-network segfaults Severity set to 'important' from 'critical' > tags -1 moreinfo Bug #884784 [systemd] systemd-network segfaults Added tag(s) moreinfo. > found -1 236-1 Bug #884784 [systemd] systemd-network

Bug#884595: kernel recognizes keyboards and mice as joysticks

Am 19.12.2017 um 20:26 schrieb Stephen Kitt: > On Mon, 18 Dec 2017 23:15:02 +0100, Markus Koschany wrote: >> Am 18.12.2017 um 22:59 schrieb Stephen Kitt: >>> On Mon, 18 Dec 2017 17:55:21 +0100, Markus Koschany >>> wrote: Preliminary work is already

Bug#884784: systemd-network segfaults

Control: severity -1 important Control: tags -1 moreinfo Control: found -1 236-1 Control: notfound -1 235-3 Am 19.12.2017 um 18:50 schrieb Rémi Denis-Courmont: > Package: systemd > Version: 235-3 > Severity: critical > Justification: breaks unrelated software > > Dear Maintainer, > >

Bug#884595: kernel recognizes keyboards and mice as joysticks

On Mon, 18 Dec 2017 23:15:02 +0100, Markus Koschany wrote: > Am 18.12.2017 um 22:59 schrieb Stephen Kitt: > > On Mon, 18 Dec 2017 17:55:21 +0100, Markus Koschany > > wrote: > >> Preliminary work is already available at: > >> > >>

Aw: Guten Morgen

Aw: Guten Morgen Ich bin Barrister Jeff Edwards und ich möchte, dass du als Erbe meines verstorbenen Klienten stehst, der die Summe von $ 5,2 Millionen mit einer Bank hier in Togo hinterlegt hat. Er starb im Juli 2012 mit seinen Familienmitgliedern ohne registrierte Angehörige und die Gelder

Bug#883690: Next information: Bug#883690: systemd Caught

Hello Michael, This bug arise after boot my diskless system. Not always, three boot is bad, one boot is success. I don't know why function __readonly_area() return -1. Format is not writable: asprintf(, "U\002%c%s%n", My idea is: - fopen("/proc/self/maps", "rce") from

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

Am 19.12.2017 um 02:18 schrieb Martin-Éric Racine: > 2017-12-19 2:02 GMT+02:00 Michael Biebl : >> Am 18.12.2017 um 20:07 schrieb Martin-Éric Racine: >>> 2017-12-18 2:08 GMT+02:00 Michael Biebl : Hi, I just uploaded v236 today. Before we try to

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

Am 18.12.2017 um 20:07 schrieb Martin-Éric Racine: > 2017-12-18 2:08 GMT+02:00 Michael Biebl : >> Hi, >> >> I just uploaded v236 today. Before we try to debug this further, it >> would be great if you can give this version a try. Maybe your issue is >> already fixed. >> If not,

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

2017-12-19 2:02 GMT+02:00 Michael Biebl : > Am 18.12.2017 um 20:07 schrieb Martin-Éric Racine: >> 2017-12-18 2:08 GMT+02:00 Michael Biebl : >>> Hi, >>> >>> I just uploaded v236 today. Before we try to debug this further, it >>> would be great if you can give

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

Am 18.12.2017 um 20:07 schrieb Martin-Éric Racine: > 2017-12-18 2:08 GMT+02:00 Michael Biebl : >> Hi, >> >> I just uploaded v236 today. Before we try to debug this further, it >> would be great if you can give this version a try. Maybe your issue is >> already fixed. >> If not,

Bug#884595: kernel recognizes keyboards and mice as joysticks

Am 18.12.2017 um 22:59 schrieb Stephen Kitt: > On Mon, 18 Dec 2017 17:55:21 +0100, Markus Koschany wrote: >> Preliminary work is already available at: >> >> https://github.com/denilsonsa/udev-joystick-blacklist >> >> If the udev maintainers don't want to create and maintain such

Bug#884595: kernel recognizes keyboards and mice as joysticks

On Mon, 18 Dec 2017 17:55:21 +0100, Markus Koschany wrote: > Preliminary work is already available at: > > https://github.com/denilsonsa/udev-joystick-blacklist > > If the udev maintainers don't want to create and maintain such a > blacklist, then please mark this bug report as

Bug#884595: closed by Michael Biebl <bi...@debian.org> (Re: kernel recognizes keyboards and mice as joysticks)

Hi, I'll try to sumarize my findings about this topic: 1.- powermanga accepts all joysticks from SDL 2.- Reading SDL: SDL_SYS_JoystickInit function for Linux seems to look for /dev/input/event*, /dev/input/js*, /dev/js* devices. Some extra checks are done at this function EV_IsJoystick. 3.-

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

2017-12-18 2:08 GMT+02:00 Michael Biebl : > Hi, > > I just uploaded v236 today. Before we try to debug this further, it > would be great if you can give this version a try. Maybe your issue is > already fixed. > If not, we'll have to involve upstream at some point by filing an >

Bug#884595: closed by Michael Biebl <bi...@debian.org> (Re: kernel recognizes keyboards and mice as joysticks)

Hi, My problem trying to play powermanga remains :-/ On Mon, Dec 18, 2017 at 05:33:04PM +, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the udev package: > > #884595: udev: consider blacklisting fake joystick

Bug#884595: kernel recognizes keyboards and mice as joysticks

Am 18.12.2017 um 18:28 schrieb Michael Biebl: > Am 18.12.2017 um 17:55 schrieb Markus Koschany: >> retitle 884595 udev: consider blacklisting fake joystick devices >> reassign 884595 udev >> clone 884595 -1 >> reassign -1 src:linux >> retitle -1 kernel recognizes keyboards and mice as joysticks >>

Processed: tagging 884595

Processing commands for cont...@bugs.debian.org: > tags 884595 + wontfix Bug #884595 {Done: Michael Biebl } [udev] udev: consider blacklisting fake joystick devices Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 884595:

Bug#884595: marked as done (udev: consider blacklisting fake joystick devices)

Your message dated Mon, 18 Dec 2017 18:28:40 +0100 with message-id and subject line Re: kernel recognizes keyboards and mice as joysticks has caused the Debian Bug report #884595, regarding udev: consider blacklisting fake joystick devices to be

Processed: [bts-link] source package systemd

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package systemd > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to

[bts-link] source package systemd

# # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #878811 (http://bugs.debian.org/878811) # Bug title: dummy interface in bridge sticks

Processed: kernel recognizes keyboards and mice as joysticks

Processing commands for cont...@bugs.debian.org: > retitle 884595 udev: consider blacklisting fake joystick devices Bug #884595 [powermanga] udev creates a fake joystick device for MS mouse Changed Bug title to 'udev: consider blacklisting fake joystick devices' from 'udev creates a fake

Bug#787473: marked as done (systemd: Segfault while adding a new job)

Your message dated Mon, 18 Dec 2017 13:24:21 +0100 with message-id <20ba83f6-cf85-673a-4813-ef6fdcceb...@debian.org> and subject line Re: systemd: Segfault while adding a new job has caused the Debian Bug report #787473, regarding systemd: Segfault while adding a new job to be marked as done.

Bug#869354: systemd: Overwrites local config without warning

On 2017-12-17 21:58 GMT, Michael Biebl wrote: > In all these years, we didn't have a service file where the [Install] > section changed. So this code does more harm then good apparently. I'm > thus inclined to just drop it. > > Thoughts/comments? No objection from me. Thanks for looking into it.

Bug#787473: systemd: Segfault while adding a new job

Hi Michael, nice to read you again. Quite some time has passed. About a year ago I was so fed up with this NAS and these bugs that I sold it. I built my own server running debian again and since then I had no issues at all. Rock solid. I suggest to close this bug for now until somebody reopens

Bug#816384: marked as done (systemd: Systemd tries to rename ppp interface when .link files present for existing NICs)

Your message dated Mon, 18 Dec 2017 12:06:34 +0100 with message-id <43449fc7-fd0e-5cc3-a119-67ca33ac4...@debian.org> and subject line Re: Bug#816384: systemd: Systemd tries to rename ppp interface when .link files present for existing NICs has caused the Debian Bug report #816384, regarding

Bug#816384: systemd: Systemd tries to rename ppp interface when .link files present for existing NICs

The thing is, as far as I remember when network units were in place, even before reboot, the system tried to apply them to any newly appeared interface, i.e. created by tinc or pptp, despite MAC filter. Anyway, now it does not, so it fixed. ___

Bug#816384: systemd: Systemd tries to rename ppp interface when .link files present for existing NICs

> Please make sure to update your initramfs (via update-initramfs -u). > Those link and udev rules files are embedded in the initramfs, so you > need to ensure it is rebuilt. > > Can you please report back what happens if you do that? I do not remember for certain if I did that earlier. Anyway,

Bug#843256: systemd: Follow-up to previous post

Package: systemd Version: 235-3 Followup-For: Bug #843256 Dear Maintainer, After comparing every man page in systemd package, I found that my previous diff would introduce errors in many places. The following diff singles out the particular problem man page and fixes the error in it. Unless

Bug#884258: machinectl shell should use bash as a default

On Wed, 13 Dec 2017 01:26:00 +0100 Michael Biebl wrote: > Am 13.12.2017 um 00:30 schrieb Marco d'Itri: > > Package: systemd-container > > Version: 235-3 > > Severity: normal > > > > Until https://github.com/systemd/systemd/issues/1395 will be fixed, > > machinectl should be

Bug#862992: systemd: avoid attempt to re-create /etc/mtab by systemd-tmpfiles-setup.service

Control: clone -1 -2 Control: reassign -2 finish-install 2.90 Control: retitle -2 Stop using/creating /etc/mtab Control: block -1 by -2 On Mon, 29 May 2017 21:23:28 +0200 Cyril Brulebois wrote: > Michael Biebl (2017-05-29): > > I think if you use

Processed: retitle 883877 to systemd segfaults in manager_unref_uid_internal

Processing commands for cont...@bugs.debian.org: > retitle 883877 systemd segfaults in manager_unref_uid_internal Bug #883877 [systemd] rsyslog: fails to configure, dpkg --configure exits with error Changed Bug title to 'systemd segfaults in manager_unref_uid_internal' from 'rsyslog: fails to

Bug#883605: marked as done (stale obsolete /var/lib/systemd/clock left present on upgrade)

Your message dated Sun, 17 Dec 2017 23:07:16 + with message-id and subject line Bug#883605: fixed in systemd 236-1 has caused the Debian Bug report #883605, regarding stale obsolete /var/lib/systemd/clock left present on upgrade to be marked as done. This

Bug#881823: marked as done (systemd-networkd: Fails to start with 'Could not enumerate rules: Operation not supported')

Your message dated Sun, 17 Dec 2017 23:07:15 + with message-id and subject line Bug#881823: fixed in systemd 236-1 has caused the Debian Bug report #881823, regarding systemd-networkd: Fails to start with 'Could not enumerate rules: Operation not

Bug#882270: marked as done (systemd-logind crashes when closing lid after "systemctl mask sleep.target")

Your message dated Sun, 17 Dec 2017 23:07:16 + with message-id and subject line Bug#882270: fixed in systemd 236-1 has caused the Debian Bug report #882270, regarding systemd-logind crashes when closing lid after "systemctl mask sleep.target" to be marked

Bug#879603: marked as done (systemd: network service enters failed state when client goes away too fast)

Your message dated Sun, 17 Dec 2017 23:07:15 + with message-id and subject line Bug#879603: fixed in systemd 236-1 has caused the Debian Bug report #879603, regarding systemd: network service enters failed state when client goes away too fast to be marked

Bug#882245: marked as done (systemd-sysv: shutdown does not parse correctly -t option)

Your message dated Sun, 17 Dec 2017 23:07:15 + with message-id and subject line Bug#882245: fixed in systemd 236-1 has caused the Debian Bug report #882245, regarding systemd-sysv: shutdown does not parse correctly -t option to be marked as done. This

Bug#878965: marked as done (systemd spam syslog with Detaching egress BPF program from cgroup failed: Invalid argument)

Your message dated Sun, 17 Dec 2017 23:07:15 + with message-id and subject line Bug#878965: fixed in systemd 236-1 has caused the Debian Bug report #878965, regarding systemd spam syslog with Detaching egress BPF program from cgroup failed: Invalid

Bug#883380: marked as done (systemd 235 segfaults when using BindPaths or BindReadOnlyPaths)

Your message dated Sun, 17 Dec 2017 23:07:16 + with message-id and subject line Bug#883380: fixed in systemd 236-1 has caused the Debian Bug report #883380, regarding systemd 235 segfaults when using BindPaths or BindReadOnlyPaths to be marked as done.

Bug#883407: marked as done (libnss-systemd: _nss_systemd_getpwnam_r leaks memory)

Your message dated Sun, 17 Dec 2017 23:07:16 + with message-id and subject line Bug#883407: fixed in systemd 236-1 has caused the Debian Bug report #883407, regarding libnss-systemd: _nss_systemd_getpwnam_r leaks memory to be marked as done. This means

systemd_236-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 17 Dec 2017 21:45:51 +0100 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump systemd-tests libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve

Processing of systemd_236-1_source.changes

systemd_236-1_source.changes uploaded successfully to localhost along with the files: systemd_236-1.dsc systemd_236.orig.tar.gz systemd_236-1.debian.tar.xz systemd_236-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

张哥：邀您住冊嶺⑶⒏瀛38O缇-擙鍆威尼斯人官网336418。C0M加客服扣:2813339771领荭鉋天天抢每周拿共资月月赚俸禄、入窾优惠2%首拵可获最高3888元

1991019554软件风险 您好，<程序段表>我是澳<网络luo拓tuo扑>门<逆平行四边形机构>威尼斯人邀请拄冊<品系>拿<对准网络luo>3⒏<相等，恒等>，<组合>网址 <文件控制块>3<向左>3<群聚>64<对话>78<动态扭斜>。<层次分析处理>C0<制造商>M 只要您<交友以义，不慕势利。>投注红<不要志气高大，倒要俯就卑微的人。不要自以为聪明。>包天天<脏水罐子掉到茅坑里越闹越臭

Bug#884595: powermanga: Controls didn't work

Am 17.12.2017 um 23:02 schrieb Michael Biebl: [...] > I don't have access to such a device, but it looks like this device node > /dev/input/js0 is created by the kernel. > Please elaborate why this is supposed to be a bug in udev. I'm not familiar with udev and I would have expected that the

Bug#884595: powermanga: Controls didn't work

Control: tags -1 + moreinfo On Sun, 17 Dec 2017 22:24:15 +0100 Markus Koschany wrote: > Control: reassign -1 udev > Control: retitle -1 udev creates a fake joystick device for MS mouse > Control: found -1 175-7.2 > Control: found -1 235-3 > > Am 17.12.2017 um 22:05 schrieb

<    2   3   4   5   6   7   8   9   10   11   >