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, I've tried everything again now: removed udev rules, placed network units, updated initramfs, rebooted. It works now, system no longer tries to rename the first interface it comes across into the first configured name it comes across. Either unupdated initramfs caused this, or something was fixed during the last year. How could the lack of rules in initramfs trigger spontaneous rename ignoring match filters anyway? ___ 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#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. ___ 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#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 systemd: Systemd tries to rename ppp interface when .link files present for existing NICs to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 816384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816384 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 228-6 Severity: important Dear Maintainer, when .link files are in place in /etc/systemd/network to rename NICs based on MAC addresses, systemd tries to rename ppp0 link which is being created by NetworkManager. This results in failure to establish PPTP connection. $ cat /etc/systemd/network/10-eth0.link [Match] MACAddress="xx:xx:xx:xx:xx:xx" [Link] Name=eth0 $ cat /etc/systemd/network/10-wlan0.link [Match] MACAddress="yy:yy:yy:yy:yy:yy" [Link] Name=wlan0 Nothing here can possibly be related to any ppp iface. But here is the journal while trying to establish PPTP via NetworkManager. "ppp0" is being renamed to "rename13" when these files are in place. It does not happen when they are not. Mar 01 15:26:22 hostname NetworkManager[797]: op="connection-activate" uuid="16be4658-71fd-4027-aa6d-ce3e2de2a189" name="pptp-connection-profile" pid=4763 uid=1000 result="success" Mar 01 15:26:22 hostname NetworkManager[797]: vpn-connection[0x19f2490,16be4658-71fd-4027-aa6d-ce3e2de2a189,"pptp-connection-profile",0]: Started the VPN service, PID 4770 Mar 01 15:26:22 hostname NetworkManager[797]: vpn-connection[0x19f2490,16be4658-71fd-4027-aa6d-ce3e2de2a189,"pptp-connection-profile",0]: Saw the service appear; activating connection Mar 01 15:26:22 hostname NetworkManager[797]: vpn-connection[0x19f2490,16be4658-71fd-4027-aa6d-ce3e2de2a189,"pptp-connection-profile",0]: VPN plugin: state changed: init (1) Mar 01 15:26:22 hostname NetworkManager[797]: vpn-connection[0x19f2490,16be4658-71fd-4027-aa6d-ce3e2de2a189,"pptp-connection-profile",0]: VPN connection: (ConnectInteractive) reply received Mar 01 15:26:22 hostname NetworkManager[797]: vpn-connection[0x19f2490,16be4658-71fd-4027-aa6d-ce3e2de2a189,"pptp-connection-profile",0]: VPN plugin: state changed: starting (3) Mar 01 15:26:22 hostname NetworkManager[797]: ** Message: pppd started with pid 4776 Mar 01 15:26:22 hostname pppd[4776]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Mar 01 15:26:22 hostname NetworkManager[797]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Mar 01 15:26:22 hostname NetworkManager[797]: ** Message: nm-pptp-ppp-plugin: (plugin_init): initializing Mar 01 15:26:22 hostname pppd[4776]: pppd 2.4.7 started by root, uid 0 Mar 01 15:26:22 hostname NetworkManager[797]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 3 / phase 'serial connection' Mar 01 15:26:22 hostname dbus[722]: [system] Rejected send message, 8 matched rules; type="method_return", sender=":1.60854" (uid=0 pid=4770 comm="/usr/lib/NetworkManager/nm-pptp-service ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.60855" (uid=0 pid=4776 comm="/usr/sbin/pppd pty /usr/sbin/pptp [pptp_gateway_address] -") Mar 01 15:26:22 hostname pppd[4776]: Using interface ppp0 Mar 01 15:26:22 hostname pppd[4776]: Connect: ppp0 <--> /dev/pts/4 Mar 01 15:26:22 hostname NetworkManager[797]: Using interface ppp0 Mar 01 15:26:22 hostname NetworkManager[797]: Connect: ppp0 <--> /dev/pts/4 Mar 01 15:26:22 hostname NetworkManager[797]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 5 / phase 'establish' Mar 01 15:26:22 hostname NetworkManager[797]: (ppp0): new Generic device (/org/freedesktop/NetworkManager/Devices/12) Mar 01 15:26:22 hostname dbus[722]: [system] Rejected send message, 8 matched rules; type="method_return", sender=":1.60854" (uid=0 pid=4770 comm="/usr/lib/NetworkManager/nm-pptp-service ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.60855" (uid=0 pid=4776 comm="/usr/sbin/pppd pty /usr/sbin/pptp [pptp_gateway_address] -") Mar 01 15:26:22 hostname pptp[4781]: nm-pptp-service-4770 log[main:pptp.c:350]: The synchronous pptp option is NOT activated Mar 01 15:26:22 hostname kernel: rename13: renamed from ppp0 Mar 01 15:26:22 hostname pptp[4791]: nm-pptp-service-4770 log[ctrlp_rep:pptp_ctrl.c:259]: Sent control packet type is 1 'Start-Contr
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 it. Maybe there is another person on this world that tries to run debian on a QNAP TS-419P II, encouters these issues and maybe finds this bugreport. Merry Christmas :) Tino signature.asc Description: OpenPGP digital signature ___ 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#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. -- Nick ___ 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#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.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
787473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787473
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 215-17
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
systemd doesn't survive two days on my bare minimal headless NAS
installation. I already purged all unused packages, reinstalled systemd
and reverted all config files to factory default, reconfiguring
everything i need. I upgraded from wheezy some time ago.
This time it segfaulted while adding a job that should restart journald.
Unfortunately, this message did not make it to the logfiles. I only saw
systemd mentioning a job that should restart the journal in dmesg right
before the sefgault. This job never finished.
Here is a callstack of the coredump. I'll post more logs and dumps at
the next crashes. Shouldn't take too long..
#0 0xb6e3b198 in raise (sig=11) at
../nptl/sysdeps/unix/sysv/linux/pt-raise.c:37
_sys_result = 0
pid = 4345
#1 0xb6e9a8f0 in crash.lto_priv.245 (sig=11) at ../src/core/main.c:158
rl = {rlim_cur = 18446744073709551615, rlim_max =
18446744073709551615}
sa = {__sigaction_handler = {sa_handler = 0x0, sa_sigaction =
0x0}, sa_mask = {__val = {0 }}, sa_flags = 0,
sa_restorer = 0x0}
pid = 0
__func__ = "crash"
__PRETTY_FUNCTION__ = "crash"
#2
No locals.
#3 hashmap_iterate (h=0xb6b76cb4, i=i@entry=0xbe91027c,
key=key@entry=0x0) at ../src/shared/hashmap.c:704
e = 0xba83a02d
__PRETTY_FUNCTION__ = "hashmap_iterate"
#4 0xb6ef94b4 in set_iterate (s=, i=i@entry=0xbe91027c)
at ../src/shared/set.c:91
No locals.
#5 0xb6f3ac6c in transaction_add_job_and_dependencies
(tr=tr@entry=0xb7914c18, type=type@entry=JOB_START, unit=, by=by@entry=0xb79429d0, matters=matters@entry=true,
override=override@entry=false, conflicts=conflicts@entry=false,
ignore_requirements=ignore_requirements@entry=false,
ignore_order=ignore_order@entry=false, e=e@entry=0xbe910458)
at ../src/core/transaction.c:982
following = 0x0
i = 0x0
dep = 0x0
r =
is_new =
__PRETTY_FUNCTION__ = "transaction_add_job_and_dependencies"
__func__ = "transaction_add_job_and_dependencies"
#6 0xb6f3a8e0 in transaction_add_job_and_dependencies
(tr=tr@entry=0xb7914c18, type=type@entry=JOB_START, unit=, by=by@entry=0xb79424b0, matters=matters@entry=true,
override=override@entry=false, conflicts=conflicts@entry=false,
ignore_requirements=ignore_requirements@entry=false,
ignore_order=ignore_order@entry=false, e=e@entry=0xbe910458)
at ../src/core/transaction.c:949
following = 0x0
i = 0x
dep =
r =
is_new =
__PRETTY_FUNCTION__ = "transaction_add_job_and_dependencies"
__func__ = "transaction_add_job_and_dependencies"
#7 0xb6f3a8e0 in transaction_add_job_and_dependencies
(tr=tr@entry=0xb7914c18, type=JOB_START, unit=unit@entry=0x0,
by=by@entry=0x0, matters=matters@entry=true,
override=override@entry=false, conflicts=conflicts@entry=false,
ignore_requirements=ignore_requirements@entry=false,
ignore_order=ignore_order@entry=false, e=e@entry=0xbe910458)
at ../src/core/transaction.c:949
following = 0x0
i = 0x
dep =
r =
is_new =
__PRETTY_FUNCTION__ = "transaction_add_job_and_dependencies"
__func__ = "transaction_add_job_and_dependencies"
#8 0xb6f51d2c in manager_add_job (m=0xb7893c08, type=-1215690256,
type@entry=JOB_RESTART, unit=0x0, unit@entry=0xb78a2328,
mode=mode@entry=JOB_FAIL, override=override@entry=false,
e=e@entry=0xbe910458, _ret=_ret@entry=0x0) at ../src/core/manager.c:1209
r =
j =
i = 0x
__PRETTY_FUNCTION__ = "manager_add_job"
__func__ = "manager_add_job"
#9 0xb6f1f348 in service_enter_restart (s=0xb78a2328) at
../src/core/service.c:1448
error = {name = 0x0, message = 0x0, _need_free = 0}
r =
#10 service_dispatch_timer.lto_priv.908 (source=,
usec=, userdata=0xb78a2328) at ../src/core/service.c:2541
__PRETTY_FUNCTION__ = "service_dispatch_timer"
__func__ = "service_dispatch_timer"
#11 0xb6ea8d38 in source_dispatch (s=0xb793d81
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 joystick device for MS mouse'. > reassign 884595 udev Bug #884595 [powermanga] udev: consider blacklisting fake joystick devices Bug reassigned from package 'powermanga' to 'udev'. Ignoring request to alter found versions of bug #884595 to the same values previously set Ignoring request to alter fixed versions of bug #884595 to the same values previously set > clone 884595 -1 Bug #884595 [udev] udev: consider blacklisting fake joystick devices Bug 884595 cloned as bug 884718 > reassign -1 src:linux Bug #884718 [udev] udev: consider blacklisting fake joystick devices Bug reassigned from package 'udev' to 'src:linux'. Ignoring request to alter found versions of bug #884718 to the same values previously set Ignoring request to alter fixed versions of bug #884718 to the same values previously set > retitle -1 kernel recognizes keyboards and mice as joysticks Bug #884718 [src:linux] udev: consider blacklisting fake joystick devices Changed Bug title to 'kernel recognizes keyboards and mice as joysticks' from 'udev: consider blacklisting fake joystick devices'. > thanks Stopping processing here. Please contact me if you need assistance. -- 884595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884595 884718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
[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 in "configuring", leading to degraded system # * https://github.com/systemd/systemd/issues/6961 # * remote status changed: open -> closed # * closed upstream tags 878811 + fixed-upstream usertags 878811 - status-open usertags 878811 + status-closed thanks ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
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-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). > # remote status report for #878811 (http://bugs.debian.org/878811) > # Bug title: dummy interface in bridge sticks in "configuring", leading to > degraded system > # * https://github.com/systemd/systemd/issues/6961 > # * remote status changed: open -> closed > # * closed upstream > tags 878811 + fixed-upstream Bug #878811 [systemd] dummy interface in bridge sticks in "configuring", leading to degraded system Added tag(s) fixed-upstream. > usertags 878811 - status-open Usertags were: status-open. Usertags are now: . > usertags 878811 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 878811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878811 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ 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#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 marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 884595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: powermanga Version: 0.93.1-2 Severity: important Dear Maintainer, The game didn't work at all. After loading the game the selected option is 'Quit'. 'Up arrow' key didn't work on main menu, so I only can change menu option by pressing 'down arrow'. Once 'Play' option is selected the game starts and the ship goes to up-left corner and I can't move it from there. Regards, -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages powermanga depends on: ii libc62.25-4 ii libpng16-16 1.6.34-1 ii libsdl-mixer1.2 1.2.12-14 ii libsdl1.2debian 1.2.15+dfsg2-0.1 ii powermanga-data 0.93.1-2 powermanga recommends no packages. powermanga suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- 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 > thanks > > Am 18.12.2017 um 00:33 schrieb Michael Biebl: >> Control: reassign -1 powermanga >> >> Am 17.12.2017 um 23:24 schrieb Markus Koschany: >>> 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 device >>> manager is responsible for creating or handling device nodes. This could >>> also be a bug in the kernel. We have received similar bug reports [1] >>> [2] for games in the past. >>> >>> In #714399 [3] Peter De Wachter pointed out that it might be a >>> longstanding kernel bug, reported as: >>> >>> https://bugzilla.kernel.org/show_bug.cgi?id=28912 >>> https://bugzilla.kernel.org/show_bug.cgi?id=37982 >>> >>> But there is also a way to work around this issue by blacklisting such >>> devices with udev rules: >>> >>> https://github.com/denilsonsa/udev-joystick-blacklist >>> >>> I'm not sure if someone ever intends to fix these kernel bugs. If udev >>> is not responsible for creating those fake joystick devices for >>> keyboards and mice, then please consider to blacklist the affected >>> devices, so that they will not be confused with joysticks. >> >> I'm reassigning this back to powermanga. the udev package is not a >> proper place for such a blacklist. I'll let you decide if you want to >> reassign this bug to the kernel or if you want to provide such a >> blacklist on your own. > > Michael what point does it serve to reassign this bug back to > powermanga? I explained to you that keyboards and mice are recognized as > joysticks and powermanga is surely not responsible for creating device > nodes. All games and applications with joystick support are affected. > > I am going to clone this bug report and reassign it to src:linux and > reassign 884595 back to udev. > > Reasoning for reassignment: > > The kernel is responsible for creating device nodes. Various keyboard > and mouse models are detected as joysticks though. This makes several > games hard or even impossible to control because the application code > assumes a joystick is a joystick and not a keyboard or a mouse. > > There are two longstanding kernel bugs which describe the same issue for > two devices: > > https://bugzilla.kernel.org/show_bug.cgi?id=28912 > https://bugzilla.kernel.org/show_bug.cgi?id=37982 > > Here are two more Debian bug reports which describe the same issue > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711350 > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714401 > > The issue is still reproducible with the latest kernel in Sid. > > If this bug cannot be
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: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884595
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
___
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#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 >> thanks >> >> Am 18.12.2017 um 00:33 schrieb Michael Biebl: >>> Control: reassign -1 powermanga >>> >>> Am 17.12.2017 um 23:24 schrieb Markus Koschany: 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 device manager is responsible for creating or handling device nodes. This could also be a bug in the kernel. We have received similar bug reports [1] [2] for games in the past. In #714399 [3] Peter De Wachter pointed out that it might be a longstanding kernel bug, reported as: https://bugzilla.kernel.org/show_bug.cgi?id=28912 https://bugzilla.kernel.org/show_bug.cgi?id=37982 But there is also a way to work around this issue by blacklisting such devices with udev rules: https://github.com/denilsonsa/udev-joystick-blacklist I'm not sure if someone ever intends to fix these kernel bugs. If udev is not responsible for creating those fake joystick devices for keyboards and mice, then please consider to blacklist the affected devices, so that they will not be confused with joysticks. >>> >>> I'm reassigning this back to powermanga. the udev package is not a >>> proper place for such a blacklist. I'll let you decide if you want to >>> reassign this bug to the kernel or if you want to provide such a >>> blacklist on your own. >> >> Michael what point does it serve to reassign this bug back to >> powermanga? I explained to you that keyboards and mice are recognized as >> joysticks and powermanga is surely not responsible for creating device >> nodes. All games and applications with joystick support are affected. >> >> I am going to clone this bug report and reassign it to src:linux and >> reassign 884595 back to udev. >> >> Reasoning for reassignment: >> >> The kernel is responsible for creating device nodes. Various keyboard >> and mouse models are detected as joysticks though. This makes several >> games hard or even impossible to control because the application code >> assumes a joystick is a joystick and not a keyboard or a mouse. >> >> There are two longstanding kernel bugs which describe the same issue for >> two devices: >> >> https://bugzilla.kernel.org/show_bug.cgi?id=28912 >> https://bugzilla.kernel.org/show_bug.cgi?id=37982 >> >> Here are two more Debian bug reports which describe the same issue >> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711350 >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714401 >> >> The issue is still reproducible with the latest kernel in Sid. >> >> If this bug cannot be fixed in time for the next stable release aka >> Buster then I would like to see that the udev maintainers create a >> blacklist for such keyboards and mice. >> >> 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 "wontfix" accordingly. >> Please don't reassign it back to affected games and applications. >> Whether I or someone else wants to provide a patch should not be the >> criterion for bug assignment. >> > > And you reassigned it back even though I explained that udev is not the > proper place to maintain such a blacklist. > > I'm thus going to close this bug report This is extremely unhelpful. I wonder what you consider a "proper place" for a udev blacklist if not udev itself. Just closing a valid bug report is a poor decision. Then please also close https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711350 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714401 signature.asc Description: OpenPGP digital signature ___ 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#884595: closed by Michael Biebl (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 devices > > It has been closed by Michael Biebl . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Michael Biebl > by > replying to this email. > > > -- > 884595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884595 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > Date: Mon, 18 Dec 2017 18:28:40 +0100 > From: Michael Biebl > To: Markus Koschany > Cc: 884595-d...@bugs.debian.org, Antoni Villalonga , > cont...@bugs.debian.org > Subject: Re: kernel recognizes keyboards and mice as joysticks > > 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 > > thanks > > > > Am 18.12.2017 um 00:33 schrieb Michael Biebl: > >> Control: reassign -1 powermanga > >> > >> Am 17.12.2017 um 23:24 schrieb Markus Koschany: > >>> 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 device > >>> manager is responsible for creating or handling device nodes. This could > >>> also be a bug in the kernel. We have received similar bug reports [1] > >>> [2] for games in the past. > >>> > >>> In #714399 [3] Peter De Wachter pointed out that it might be a > >>> longstanding kernel bug, reported as: > >>> > >>> https://bugzilla.kernel.org/show_bug.cgi?id=28912 > >>> https://bugzilla.kernel.org/show_bug.cgi?id=37982 > >>> > >>> But there is also a way to work around this issue by blacklisting such > >>> devices with udev rules: > >>> > >>> https://github.com/denilsonsa/udev-joystick-blacklist > >>> > >>> I'm not sure if someone ever intends to fix these kernel bugs. If udev > >>> is not responsible for creating those fake joystick devices for > >>> keyboards and mice, then please consider to blacklist the affected > >>> devices, so that they will not be confused with joysticks. > >> > >> I'm reassigning this back to powermanga. the udev package is not a > >> proper place for such a blacklist. I'll let you decide if you want to > >> reassign this bug to the kernel or if you want to provide such a > >> blacklist on your own. > > > > Michael what point does it serve to reassign this bug back to > > powermanga? I explained to you that keyboards and mice are recognized as > > joysticks and powermanga is surely not responsible for creating device > > nodes. All games and applications with joystick support are affected. > > > > I am going to clone this bug report and reassign it to src:linux and > > reassign 884595 back to udev. > > > > Reasoning for reassignment: > > > > The kernel is responsible for creating device nodes. Various keyboard > > and mouse models are detected as joysticks though. This makes several > > games hard or even impossible to control because the application code > > assumes a joystick is a joystick and not a keyboard or a mouse. > > > > There are two longstanding kernel bugs which describe the same issue for > > two devices: > > > > https://bugzilla.kernel.org/show_bug.cgi?id=28912 > > https://bugzilla.kernel.org/show_bug.cgi?id=37982 > > > > Here are two more Debian bug reports which describe the same issue > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711350 > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714401 > > > > The issue is still reproducible with the latest kernel in Sid. > > > > If this bug cannot be fixed in time for the next stable release aka > > Buster then I would like to see that the udev maintainers create a > > blacklist for such keyboards and mice. > > > > 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 "wontfix" accordingly. > > Please don't reassign it back to affected games and applications. > > Whether I or someone else wants to provide a patch should not be the > > criterion for bug assignment. > > > > And you reassigned it back even though I explained that udev is not the > proper place to maintain such a blacklist. > > I'm thus going to close this bug report > > > -- > Why is it that all of the instruments seeking intelligent life in the > uni
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 > upstream bug report. But let's first wait for your results with 236-1 The issue is not fixed. Something fails at communicating with dbus, and it messes up everything else. Googling up the issue, I found this: https://answers.launchpad.net/ubuntu/+source/systemd/+question/287454 As to whether this is the exact issue we're seeing, I wouldn't know. However, there's one interesting problem: purging all dbus-related packages (dpkg -P --force-all) fails because dbus's maintainer scripts call dbus... whose socket cannot be reached for some damn reason. Thus, my attempt at reainstaling it also fails. Martin-Éric ___ 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#884595: closed by Michael Biebl (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.- Linux 'joydev' module creates /dev/input/js0 device for de MS usb mouse 045e:075c 4.- udev isn't involved (or should be somehow transparent) Some questions I can't reply by myself: - Should Linux create a js device for 045e:075c? - Should SDL accept this js device? - Should powermanga accept a js without axes? FTR: As a hotfix for powermanga: # modprobe -r joydev Regards, On Mon, Dec 18, 2017 at 06:21:59PM +, Antoni Villalonga wrote: > 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 devices > > > > It has been closed by Michael Biebl . > > > > Their explanation is attached below along with your original report. > > If this explanation is unsatisfactory and you have not received a > > better one in a separate message then please contact Michael Biebl > > by > > replying to this email. > > > > > > -- > > 884595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884595 > > Debian Bug Tracking System > > Contact ow...@bugs.debian.org with problems > > > Date: Mon, 18 Dec 2017 18:28:40 +0100 > > From: Michael Biebl > > To: Markus Koschany > > Cc: 884595-d...@bugs.debian.org, Antoni Villalonga , > > cont...@bugs.debian.org > > Subject: Re: kernel recognizes keyboards and mice as joysticks > > > > 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 > > > thanks > > > > > > Am 18.12.2017 um 00:33 schrieb Michael Biebl: > > >> Control: reassign -1 powermanga > > >> > > >> Am 17.12.2017 um 23:24 schrieb Markus Koschany: > > >>> 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 device > > >>> manager is responsible for creating or handling device nodes. This could > > >>> also be a bug in the kernel. We have received similar bug reports [1] > > >>> [2] for games in the past. > > >>> > > >>> In #714399 [3] Peter De Wachter pointed out that it might be a > > >>> longstanding kernel bug, reported as: > > >>> > > >>> https://bugzilla.kernel.org/show_bug.cgi?id=28912 > > >>> https://bugzilla.kernel.org/show_bug.cgi?id=37982 > > >>> > > >>> But there is also a way to work around this issue by blacklisting such > > >>> devices with udev rules: > > >>> > > >>> https://github.com/denilsonsa/udev-joystick-blacklist > > >>> > > >>> I'm not sure if someone ever intends to fix these kernel bugs. If udev > > >>> is not responsible for creating those fake joystick devices for > > >>> keyboards and mice, then please consider to blacklist the affected > > >>> devices, so that they will not be confused with joysticks. > > >> > > >> I'm reassigning this back to powermanga. the udev package is not a > > >> proper place for such a blacklist. I'll let you decide if you want to > > >> reassign this bug to the kernel or if you want to provide such a > > >> blacklist on your own. > > > > > > Michael what point does it serve to reassign this bug back to > > > powermanga? I explained to you that keyboards and mice are recognized as > > > joysticks and powermanga is surely not responsible for creating device > > > nodes. All games and applications with joystick support are affected. > > > > > > I am going to clone this bug report and reassign it to src:linux and > > > reassign 884595 back to udev. > > > > > > Reasoning for reassignment: > > > > > > The kernel is responsible for creating device nodes. Various keyboard > > > and mouse models are detected as joysticks though. This makes several > > > games hard or even impossible to control because the application code > > > assumes a joystick is a joystick and not a keyboard or a mouse. > > > > > > There are two longstanding kernel bugs which describe the same issue for > > > two devices: > > > > > > https://bugzilla.kernel.org/show_bug.cgi?id=28912 > > > https://bugzilla.kernel.org/show_bug.cgi?id=37982 > > > > > > Here are two more Debian bug reports which describe the same issue > > > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711350 > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714401 > > > > >
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 "wontfix" accordingly. > Please don't reassign it back to affected games and applications. > Whether I or someone else wants to provide a patch should not be the > criterion for bug assignment. ... and the joystick package includes the blacklist linked above. Installing that should fix many of this issues. Regards, Stephen pgp4kQrhzk_zr.pgp Description: OpenPGP digital signature ___ 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#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 a >> blacklist, then please mark this bug report as "wontfix" accordingly. >> Please don't reassign it back to affected games and applications. >> Whether I or someone else wants to provide a patch should not be the >> criterion for bug assignment. > > ... and the joystick package includes the blacklist linked above. Installing > that should fix many of this issues. > > Regards, > > Stephen Alas the joystick package is only optional while udev is priority important. It is rather unlikely that someone will have it installed already. The issue is that those people would not even think about a joystick, they just assume the game/application is broken. It's rather strange to recommend the installation of joystick when you want to play a game without one. This issue should be solved in packages which are guaranteed to be installed on a default desktop computer like udev. signature.asc Description: OpenPGP digital signature ___ 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#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, we'll have to involve upstream at some point by filing an >> upstream bug report. But let's first wait for your results with 236-1 > > The issue is not fixed. Something fails at communicating with dbus, > and it messes up everything else. Just to be sure, have you rebooted your system after upgrading to 236-1? -- 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 ___ 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#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 this version a try. Maybe your issue is >>> already fixed. >>> If not, we'll have to involve upstream at some point by filing an >>> upstream bug report. But let's first wait for your results with 236-1 >> >> The issue is not fixed. Something fails at communicating with dbus, >> and it messes up everything else. > > Just to be sure, have you rebooted your system after upgrading to 236-1? Yes I have, but this required issuing "exec reboot -f" to bypass init entirely, otherwise it fails due to the lack of dbus connection. Martin-Éric ___ 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#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, we'll have to involve upstream at some point by filing an >> upstream bug report. But let's first wait for your results with 236-1 > > The issue is not fixed. Something fails at communicating with dbus, > and it messes up everything else. > > Googling up the issue, I found this: > > https://answers.launchpad.net/ubuntu/+source/systemd/+question/287454 > > As to whether this is the exact issue we're seeing, I wouldn't know. > I don't think this is related. The issue above talks above the systemd --user instance. Your issue seems to be about systemd PID 1 crashing. -- 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 ___ 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#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 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 upstream bug report. But let's first wait for your results with 236-1 >>> >>> The issue is not fixed. Something fails at communicating with dbus, >>> and it messes up everything else. >> >> Just to be sure, have you rebooted your system after upgrading to 236-1? > > Yes I have, but this required issuing "exec reboot -f" to bypass init > entirely, otherwise it fails due to the lack of dbus connection. Sure, if PID 1 has crashed, it will freeze itself and no longer respond to any (D-Bus) requests. When exactly does systemd crash? Is it immediately during boot or after you've been using the system for a while? I assume it works at least for a while, otherwise no other services would be started and you would not be able to log in. When systemd crashes, you should get an entry in the kernel log (dmesg) respectively the journal. It would be great if you can follow the instructions at [1] to boot with debug logging enabled and then provide a journal log which shows such a crash. Michael [1] https://freedesktop.org/wiki/Software/systemd/Debugging/ -- 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 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
