Bugzilla – Bug 360274
Language information disappears (hidden dialog)
Last modified: 2008-04-23 08:56:31 UTC
I just started openSUSE 11.0 alpha2 installation (GNOME-Live-CD) and noticed that in the first screen (Languages) there is a design flaw. I selected Language: Svenska and clicked Next. A dialog appeared "Translation of the primary language is not complete. Some texts may be displayed in English. [Continue] [Cancel]". Try to click outside that dialog in the green area. Dialog disappears and user (me) expected to click Next (in the lower right area) again. Nothing happened. I figured out that ALT+Tab would bring back the dialog. Problem is that dialog is hidden, there is no sign at all that it is behind the green installer.
It seems to be wrong translation.
I do not understand exactly what is going on there. There seems to be a problem with focus setting and window management. I think it cannot depend on the translation because the Live-CD does not come with any translation at all. Or is this different with 11.0 now? I'm just burning a CD and will run a test on my own.
I cannot reproduce it. That's what I did: 1/ Boot the GNOME Live-CD (11.0 Alpha2) 2/ Gnome starts. Double-click "Install". xmessage appears: YaST got signal 11 at YCP file Wixard.ycp: 385 ...
Troubles with hidden dialogs are described in a lot of other bugs. It is known problem of new installation. IMO interesting part of description is: I selected Language: Svenska and clicked Next. A dialog appeared "Translation of the primary language is not complete. Some texts may be displayed in English. [Continue] [Cancel]". comment #3 - this is other bug :( Could you create a new bug for it please? There are missing YaST logs and I don't know write what is wrong. Could you attach YaST logs please (in a new bug)?
I created bug 368199; I think you now can close this as a dupe...
see comment 5 : I created bug 368199; I think you now can close this as a dupe...
It si duplicated/similar of bug# 378773 troubles with localization is desribed in bug 368199 *** This bug has been marked as a duplicate of bug 378773 ***