Bug 3976 - mouse pointer disappears when Universal Access Settings Zoom is used
Summary: mouse pointer disappears when Universal Access Settings Zoom is used
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 4974
  Show dependency treegraph
 
Reported: 2012-01-01 00:57 CET by Peter D
Modified: 2012-07-15 09:47 CEST (History)
4 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Peter D 2012-01-01 00:57:26 CET
Description of problem:


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

Mageia 2 Alpha 2 i586 Gnome live iso

[root@unknown001fd0b96f13 ~]# lspci -s 1:
01:00.0 VGA compatible controller: ATI Technologies Inc RV370 [Radeon X550]
01:00.1 Display controller: ATI Technologies Inc RV370 secondary [Sapphire X550 Silent]
[root@unknown001fd0b96f13 ~]# 

How reproducible:

Always - on this machine.  I guess that it is ati video driver related.  
(It is worse on my nVidia machine, no "Universal Access Settings" at all.  
Separate bug report to follow.)  


Steps to Reproduce:
1.  Boot live CD
2.  Click on "Universal Access Settings" (top right of screen)
3.  Click on "Zoom"
Comment 1 Marja Van Waes 2012-02-12 17:17:15 CET
(In reply to comment #0)

> 
> Always - on this machine.  I guess that it is ati video driver related.  
> (It is worse on my nVidia machine, no "Universal Access Settings" at all.  
> Separate bug report to follow.)  
> 
> 

I searched for that separate bug report, but I couldn't find it
https://bugs.mageia.org/buglist.cgi?email1=0123peter%40gmail.com&emailreporter1=1&emailtype1=substring&query_format=advanced&order=bug_id%20DESC&query_based_on=

nor do I find a bug of someone else about universal access settings
https://bugs.mageia.org/buglist.cgi?quicksearch=ALL+universal+access+settings

CC: (none) => doktor5000, mageia, marja11, olav, tmb

Peter D 2012-03-16 04:59:56 CET

Blocks: (none) => 4974

Florian Hubold 2012-03-16 15:11:19 CET

CC: doktor5000 => (none)

Comment 2 Marja Van Waes 2012-05-26 13:06:09 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 3 Marja Van Waes 2012-07-01 15:55:24 CEST
It is very important for us to know whether this bug is still valid for Mageia 2 or for *current* cauldron.

Please tell us. If you don't reply, we'll have to close this bug as old.
Comment 4 Peter D 2012-07-14 08:15:33 CEST
Are there any cauldron live isos to test against?  

For the Mageia 2 release live CD:  

It mis-behaved on two machines (an old nVidia and an ATI X550) BUT both had to be run with the VESA driver which caused Gnome to run in legacy mode.  There was no universal access icon to click on.  

It behaved on a machine with an nVidia 8400 GS.  

It also behaved on full install (not live CD) on an ATI X550.  

So, I can't really test this until the first alpha live CDs of Mageia 3, but the problem has _probably_ gone away.
Comment 5 Marja Van Waes 2012-07-15 09:47:28 CEST
Thx for the feedback, Peter

I understand for two of the machines you had this issue with, you could not test whether the issue was still there with a live CD, because the universal access icon was missing, due to running legacy mode.

For another machine with a Live CD, the issue wasn't there, nor was it on a full install for one of the machines you couldn't test this for with the LiveCD.

So 2x fixed, 2x can't tell

Since no one else seems to suffer from this bug, I'll close as fixed.

Please reopen if you find this problem again. The Mageia 3 alpha 1 LiveCD is expected to be released on September 4th

https://wiki.mageia.org/en/Mageia_3_development

Resolution: (none) => FIXED
Status: NEW => RESOLVED

Marja Van Waes 2012-07-15 09:47:49 CEST

Keywords: NEEDINFO => (none)


Note You need to log in before you can comment on or make changes to this bug.