Bug 465106

Summary:	Unable to select entry in yast bootloader settings
Product:	[openSUSE] openSUSE 11.2	Reporter:	Forgotten User vXTZVacoSi <forgotten_vXTZVacoSi>
Component:	YaST2	Assignee:	E-mail List <bnc-team-screening>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Enhancement
Priority:	P5 - None	CC:	jreidinger
Version:	unspecified
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Forgotten User vXTZVacoSi 2009-01-10 11:17:56 UTC

Whenever I click an entry in the bootloader main menu it opens the corresponding configuration, not even right click is working to just select it.

Thus it is annoying to delete an entry, you need to use the keyboard to move to the entry and then click delete...


I hope this is not intended way to delete entries =)
Thanks for you work

Comment 1 Josef Reidinger 2009-01-13 15:17:41 UTC

Please, can you specify what frontend you use? I try it in gtk and qt frontend and one click select item and double click edit it.

Comment 2 Forgotten User vXTZVacoSi 2009-01-13 23:18:42 UTC

Sorry, forgot that!

I am using the qt frontend, BUT with the kde4.2beta packages which provide their own qt build, the issue has been confirmed by another person on the #opensuse-kde irc channel using kde4.2 beta as well.

Same happens for any list in yast where I can usually select items, for example "partition harddisk"

The relevant package versions: (hope I got them all)
yast 2.17 (plus individual build numbers)
yast-control-center
yast-control-center-qt
yast-qt

libqt4 4.4.3

libqt4 is the same as repo-oss, just different build number, reverting to release ones didn't help.


So propably INVALID due to beta stuff, maybe ask kde team for any possible reasons?

Comment 3 Josef Reidinger 2009-01-19 09:28:03 UTC

stefan - JFYI, maybe in future some duplicates appear

Comment 4 Forgotten User vXTZVacoSi 2009-02-04 10:48:42 UTC

duplicate

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