I think it does. after reflashing my last backup was loaded (that i made before i reflashed but after Mer was installed), so it's possible, that it is some wierd user setting that got reinstalled with the backup. And as i said: it worked all very nice before i installed Mer, and i didn't install anything else but Mer. so unless bad weather or full moon aren't counted in, i dont see what else could have done this.
i will reflash later without installing the backup and see how that works out,
then install the backup and see if i it screws up again. after that i will reflash, install Mer and see what happens. Then we will know, whether it is Mer (or the bootmanager) or not
and btw. just saying "no, it cant be the stuff we made, because it worked fine on different model" is not a good way to find possible bugs
I think it does. after reflashing my last backup was loaded (that i made before i reflashed but after Mer was installed), so it's possible, that it is some wierd user setting that got reinstalled with the backup. And as i said: it worked all very nice before i installed Mer, and i didn't install anything else but Mer. so unless bad weather or full moon aren't counted in, i dont see what else could have done this.
i will reflash later without installing the backup and see how that works out,
then install the backup and see if i it screws up again. after that i will reflash, install Mer and see what happens. Then we will know, whether it is Mer (or the bootmanager) or not
and btw. just saying "no, it cant be the stuff we made, because it worked fine on different model" is not a good way to find possible bugs
First off I didn't make Mer I'm just trying to help you troubleshoot, but the backup should only reinstall Mer installer not Mer. When you process your backup you can tell it what programs to install and what not to install so just leave Mer installer off. I would suggest reporting it as a bug so the developers can see and and see about fixing it.
I think it does. after reflashing my last backup was loaded (that i made before i reflashed but after Mer was installed), so it's possible, that it is some wierd user setting that got reinstalled with the backup. And as i said: it worked all very nice before i installed Mer, and i didn't install anything else but Mer. so unless bad weather or full moon aren't counted in, i dont see what else could have done this.
i will reflash later without installing the backup and see how that works out,
then install the backup and see if i it screws up again. after that i will reflash, install Mer and see what happens. Then we will know, whether it is Mer (or the bootmanager) or not
and btw. just saying "no, it cant be the stuff we made, because it worked fine on different model" is not a good way to find possible bugs
Mer installer .install file gives you extras-devel repo. It might be that bad weather or full moon installed something else from extras-devel too, that killed you keyboard.
First off I didn't make Mer I'm just trying to help you troubleshoot, but the backup should only reinstall Mer installer not Mer. When you process your backup you can tell it what programs to install and what not to install so just leave Mer installer off. I would suggest reporting it as a bug so the developers can see and and see about fixing it.
Well actually it was more of a general statement and not specifically meant for you, andrew I just remembered some comment about Mer not screwing up keyboards with finnish layouts
I left the Mer installer and the bootmanager out when i reinstalled the backup, but i still got that wierd behaviour, thus my comment about the user settings. I will test it first (as laid out in my last post) before i file a bug to make sure it's not something else. thanks for your input though.
