Bug 17486

Summary:	cauldron network install - no mouse pointer at installer screens
Product:	Mageia	Reporter:	Jüri Ivask <jyri2000>
Component:	Installer	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Normal	CC:	ftg, maurice77
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	drakx-installer-stage2	CVE:
Status comment:

Description Jüri Ivask 2016-01-13 09:38:34 CET

Description of problem: attempted a cauldron network install - no mouse pointer at installer screen


Version-Release number of selected component (if applicable):
boot-nonfree.iso 2016-01-11 07:32   50M
mdkinst.sqfs 2016-01-13 07:21   72M  


At the network installer first screen (language selection) there was no visible X mouse pointer. However - the pointer exists, but is invisible - if you succeed to click on some button by trial/error - the cursor appears and you can use it afterwards.

See also comments 16 and 17 of bug 16726:
https://bugs.mageia.org/show_bug.cgi?id=16726#c16

Reproducible: 

Steps to Reproduce:

Comment 1 Maurice Batey 2016-01-13 10:35:24 CET

Thank you, JÃ¼ri!

Will raise one on the clobbered MBR...

CC: (none) => maurice

Comment 2 Frank Griffin 2016-01-13 13:04:37 CET

Dup of bug#17470 ?

CC: (none) => ftg

Comment 3 Maurice Batey 2016-01-13 13:35:55 CET

Yes, indeed - though that doesn't mention 'network installer', though I guess it boils down to the same installer...

Comment 4 Samuel Verschelde 2016-01-18 10:44:02 CET

Closing as duplicate as per comment #2

*** This bug has been marked as a duplicate of bug 17470 ***

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

Comment 5 Rémi Verschelde 2016-01-18 11:00:12 CET

Not sure it's actually a duplicate as bug 17470 seemed to be about non-working (touchpad) pointer, while this one is about working but invisible mouse pointer. Hence the former seemed to be a kernel issue (apparently with a fix already) while the latter might be a gtk theme regression or similar.

But we can also continue working on the general symptom in the other bug IMO, there is no big risk to add confusion even if the two issues were different; both end up in non-usable mouse pointer in current stage2 and need to be fixed soon :)