Description of problem: clicked "-" and then i did something weird. It is something i do not believe that will normally happen. The following was filed automatically by anaconda: anaconda 18.37.2 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/keyboard.py", line 526, in remove_layout variant)) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/keyboard.py", line 358, in _removeLayout self._xkl_wrapper.remove_layout(store[itr][0]) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/keyboard.py", line 394, in on_add_clicked self._removeLayout(self._store, itr) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/utils.py", line 30, in wrap func(*args) XklWrapperError: Failed to remove layout 'us ()' Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2018-TC2\x20x86_64 quiet gpt BOOT_IMAGE=vmlinuz executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.6.10-4.fc18.x86_64 other involved packages: package: anaconda-18.37.2 product: Fedora release: Cannot get release name. type: libreport version: 18-TC2
Created attachment 663770 [details] File: anaconda.log
Created attachment 663771 [details] File: environ
Created attachment 663772 [details] File: ifcfg.log
Created attachment 663773 [details] File: packaging.log
Created attachment 663774 [details] File: program.log
Created attachment 663775 [details] File: storage.log
Created attachment 663776 [details] File: syslog
Created attachment 663777 [details] File: anaconda-tb
Can you remember what "something weird" you did that caused this? Without it, I don't think we'll be able to reproduce and fix this problem.
I could not replicate it. I was some junk imput, so i don't think it will happen very often. If i can reproduce it i will update this bug-report.
Well, i believe i speaker too quickly... I was able to reproduce it. 0. Boot, enter KEYBOARD 1. Click '-' key 2. Type: spaX 3. Double click the now empty keyboard layout are (the center of the widget) 4. The 'input' is accepted and the 'unknown error' appears. Partially unrelated: in recent times i noticed that there is now a delay for the unknown error to show up. Previously they were almost instantaneous. There is at least one case in which there is an anaconda-tb-XXX file but no unknown error has been ever displayed.
(In reply to comment #11) > Well, i believe i speaker too quickly... I was able to reproduce it. > > 0. Boot, enter KEYBOARD > 1. Click '-' key > 2. Type: spaX > 3. Double click the now empty keyboard layout are (the center of the widget) > 4. The 'input' is accepted and the 'unknown error' appears. Thanks for the reproducer. I'm sending an easy fix for this issue to anaconda-patches. > > > Partially unrelated: in recent times i noticed that there is now a delay for > the unknown error to show up. Previously they were almost instantaneous. I have seen this too some time ago and it was caused by dumping some big data that should have been skipped (yum instance). In the anaconda-tb file you have provided I can see some unimportant rubbish that could be skipped. I'll look at this too. > There is at least one case in which there is an anaconda-tb-XXX file but no > unknown error has been ever displayed. Whenever this happens, please switch to tty1 because there will likely be a traceback from python-meh (our exception handling). You can use tmux capabilities [1] to copy-paste these and file a bug against python-meh. Thanks! [1] http://awhan.wordpress.com/2010/06/20/copy-paste-in-tmux/
It still happens with TC4 (18.37.8)
(In reply to comment #13) > It still happens with TC4 (18.37.8) That's expected. This bug was not marked as blocker nor NTH and thus the patch was pushed only for Rawhide, not F18.
Tested with F19, cannot reproduce; the fix worked.