Red Hat Bugzilla – Bug 974736
Anaconda Fedora 19 TC3 Live Crash on Custom Partitioning Using es_ES language
Last modified: 2013-06-20 02:55:32 EDT
Created attachment 761512 [details]
Anaconda Crash trying delete a pre-existent partition using Spanish Language, if en_US is used no happen
Description of problem:
Using es_ES language for installation, Anaconda crash when a custom partitioning is selected, in the moment that I select (-) for remove a pre-existent partition, all turn grey and crash with a message about unicode.
The backtrace and reporting from the live medium is reported here:
The conditions for reproduce it are 2:
1.- That the HDD must be a previous primary partition / ext and swap
2.- Select Spanish for language in installation, and only repeat step by step commented in "Steps to Reproduce" item here.
NOTE: If en_US is used for the installation, the bug no happen.
Version-Release number of selected component (if applicable):
Fedora 19 TC3 Live KDE
Steps to Reproduce:
0.Create a primary partition in a disk, / ext4 and swap using any live distro
1.Boot a Live CD with Fedora 19 TC3 KDE Spin or other spin
2.Start anaconda, select Spanish as language for installing
3.Select destination, select custom partitioning (The hdd must be a previous partition of another installation, / ext4 and swap, point 0), select / partition, press "-" symbol for delete it, Anaconda crash and a message of error is displayed.
If a previous partition is in the HDD for installation of Fedora 19 TC3, and language selected is Spanish, custom partitioning crash always when you try to delete a previous / partition.
No crash Anaconda.
Attach a screenshot and the bug report auto-generated by anaconda and reported in bugzilla for me
Is a regression instroduced in Anaconda 19.30.3-1, i can confirm it
No need to report it twice...
*** This bug has been marked as a duplicate of bug 973019 ***
(In reply to Adam Williamson from comment #2)
> No need to report it twice...
> *** This bug has been marked as a duplicate of bug 973019 ***
Sorry Adam, i repliqued the bug because i don't see any change in the other bug, so, I opened this bug.