Bug 752657

Summary: GPointing Middle button Scroll Does not survive Reboot
Product: [Fedora] Fedora Reporter: Vincent passaro <vincent.passaro>
Component: gpointing-device-settingsAssignee: Thomas Spura <tomspur>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: jlbouras, psimerda, rstp, tomspur
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 23:45:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Vincent passaro 2011-11-10 03:37:39 UTC
Description of problem:

Configuring gpointing-devices via GUI to use middle scroll function on Lenovo W520 laptop configures properly, but does not survive a reboot.  


Version-Release number of selected component (if applicable):

gpointing-device-settings-1.5.1-5.fc16.x86_6

How reproducible: Always


Steps to Reproduce:
1. Installe gpointing-device-settings
2. Configure with your prefrences
3. Restart systems
4. Pointing device (middle scroll button) settings do not survive reboot
  
Actual results:

Settings are persistent. 

Expected results:

Settings are not persistent.


Additional info:

Comment 1 Vincent passaro 2011-11-14 06:14:01 UTC
Server re installs of F16 and still settings do not survive reboot. Have tried multiple 'tactics' to try and configure with gpointing, still always gets destroyed after a reboot.

Comment 2 Pavel Šimerda (pavlix) 2012-03-21 00:41:08 UTC
This bug is still present in Fedora 17:

gpointing-device-settings-1.5.1-7.fc17.x86_64

Comment 3 rstp 2013-01-12 22:59:09 UTC
Related to: https://bugzilla.redhat.com/show_bug.cgi?id=710053 (still unresolved)

Comment 4 Fedora End Of Life 2013-01-16 20:19:33 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 
'version' of '16'.

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 prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 John Bouras 2013-01-17 05:59:51 UTC
This has been plaguing me since I began using Fedora 9. Back then, I was using an IBM ThinkPad R40. With every iteration of Fedora, this problem never fails. Now I'm on Fedora 18 with a Lenovo T61p, and the same thing occurs.

gpointing does not work after reboot.

I will post at the above mentioned link as well.

Comment 6 Fedora Admin XMLRPC Client 2013-01-25 11:03:24 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 7 Fedora End Of Life 2013-02-13 23:45:10 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

Thank you for reporting this bug and we are sorry it could not be fixed.