Description of problem: Go to select keyboard layout, choose to add keyboard '+' and selected ALL keyboards. All keyboards layout get added ok, even if it took a bit for it. Then started to remove one by one and got this. Version-Release number of selected component: anaconda-18.14 Additional info: libreport version: 2.0.14 cmdline: /usr/bin/python /sbin/anaconda kernel: 3.6.1-1.fc18.x86_64 description: :The following was filed automatically by anaconda: :anaconda 18.14 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/pyanaconda/keyboard.py", line 379, in remove_layout : raise XklWrapperError(msg) : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/keyboard.py", line 258, in _removeLayout : self._xkl_wrapper.remove_layout(store[itr][0]) : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/keyboard.py", line 323, in on_remove_clicked : self._removeLayout(store, itr) :XklWrapperError: 'ph ()' not in the list of added layouts
Created attachment 626075 [details] File: anaconda-tb
Created attachment 626076 [details] File: product
Created attachment 626077 [details] File: type
Created attachment 626078 [details] File: ifcfg.log
Created attachment 626079 [details] File: storage.log
Created attachment 626080 [details] File: version
Created attachment 626081 [details] File: environ
Created attachment 626082 [details] File: anaconda.log
Created attachment 626083 [details] File: syslog
Created attachment 626084 [details] File: hashmarkername
Created attachment 626085 [details] File: packaging.log
Created attachment 626086 [details] File: cmdline_file
Created attachment 626087 [details] File: release
Created attachment 626088 [details] File: program.log
Sorry, but this is not a reasonable use case. Moreover we just call libxklavier (chaning X runtime configuration) and it probably cannot handle so many layouts correctly.
I do agree that it is not a reasonable usage case. (who will have so many keyboards? :-) ) Should anaconda prevent the user from doing know things that crashes the installer? At least there might be max number of keyboards that anaconda (for whatever reason) supports.
(In reply to comment #16) > I do agree that it is not a reasonable usage case. (who will have so many > keyboards? :-) ) > > Should anaconda prevent the user from doing know things that crashes the > installer? > > At least there might be max number of keyboards that anaconda (for whatever > reason) supports. Well, this might be a problem, because it depends on X server itself and I'm affraid it may be arch-dependend.