Bug 1057614

Summary: somethng resets my usb mouse every night
Product: [Fedora] Fedora Reporter: Tom Horsley <horsley1953>
Component: xorg-x11-drv-evdevAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: johannbg, lnykryn, lpoetter, msekleta, peter.hutterer, plautrba, systemd-maint, vpavlin, xgl-maint, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 14:44:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
/var/log/Xorg.0.log showing evdev resets
none
Here's my xinput script in case that is relevant none

Description Tom Horsley 2014-01-24 13:25:15 UTC 
Created attachment 854973 [details]
/var/log/Xorg.0.log showing evdev resets

Description of problem:

I apply several xinput settings to make my trackball work the way I want it to work and every morning I find it has been reset and I have to re-run my script to apply the settings again. Whatever is doing this may also be creating the nologin file from bug 1043212. It may also be related to bug 1048003 where plugging in a new device causes everything on the same hub to be reset.

My system is up 24/7 with all screen savers and power management disabled. I'm logged in all the time.


Version-Release number of selected component (if applicable):
systemd-208-9.fc20.x86_64

How reproducible:
Happens every night

Steps to Reproduce:
1. use xinput to apply setting to mouse
2. find the settings have disappeared over night
3.

Actual results:
xinput settings disappear

Expected results:
as long as I stay logged in and don't unplug the mouse, the settings should stay active.

Additional info:

I'll attach the X log that shows evdev resets long after X started.
Comment 1 Tom Horsley 2014-01-24 13:26:32 UTC 
Created attachment 854974 [details]
Here's my xinput script in case that is relevant
Comment 2 Lennart Poettering 2014-01-28 00:37:26 UTC 
Not sure what I am supposed to do with this. systemd does not touch input devices. Reassigning.
Comment 3 Tom Horsley 2014-01-28 00:47:34 UTC 
Actually, it does touch input devices. Like seemingly everything else in linux, udev has been assimilated by the systemd fungus and the same thing that screws up everything else on my system also re-initializes udev, so all the devices look like they were plugged in again, which resets all the evdev settings back to ground zero.
Comment 4 Peter Hutterer 2014-01-28 04:16:53 UTC 
Tom: your choice of words won't help the discussion along, so please stay respectful and polite.

Lennart: have a look at the log. something resets at time 35286.401, because I haven't seen the "Video Bus" device and other virtual devices disappear before. Is this a side-effect of some power feature in the kernel or is this udev re-initialising something?
Comment 5 Tom Horsley 2014-02-08 00:23:19 UTC 
I'm almost completely convinced this is from the same fundamental cause as bug 1043212, just a different symptom cropping up.
Comment 6 Fedora End Of Life 2015-05-29 10:39:44 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 7 Fedora End Of Life 2015-06-29 14:44:02 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 8 Red Hat Bugzilla 2023-09-14 01:57:49 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days