Dual boot install using Trisquel 7 Live DVD and Windows XP or Windows 8 fails to boot when selecting Windows partition.

Projekt:Trisquel
Version:7.0
Komponente:Installer
Kategorie:Fehlerbericht
Priorität:critical
Zugewiesen:nicht zugewiesen
Status:closed
Beschreibung

I have tried installing trisquel 7 doing dual boot with windows XP or windows 8 and in both cases on two different computers if fails.

I never had this problem with previous trisquel version installs. Using Trisquel 7 Live DVD and letting the live DVD do the dual boot install alongside the windows partition when I reboot the system I only get a dark screen that shows a prompt for a username and a password.

Even after entering these details booting into the windows partition is impossible. Booting is only possible with Trisquel.

The only way I could boot again into Windows was to use a recovery disc and fix the master boot record but then booting into Trisquel was not possible anymore.

Can anyone explain what is happening? Has anyone else experienced this problem?

I think this is a serious problem that will discourage new users from giving Trisquel a try.

Thanks for any feedback.

Fr, 11/21/2014 - 16:53

Here's workaround https://trisquel.info/en/forum/strange-grub-behaviour-trisquel-7#comment-57413

(It doesn't want your Trisquel password and username but grub password and username.)

Sa, 12/20/2014 - 07:50
Status:active» patch (ready)

Fixed in this commit

https://devel.trisquel.info/trisquel/package-helpers/commit/b75364070c802cf9033a4576011c1487701b3bee

Which is now in the repo. Please report if it has been successful

Sa, 12/20/2014 - 13:57

Should that be +sed 's/class osx/class osx --unrestricted/; s/class windows/class windows --unrestricted/;' -i ./util/grub.d/30_os-prober.in

?

Mi, 01/07/2015 - 16:39
Status:patch (ready)» needs more info

Well spotted, but it's just a 'class' for grouping/display properties of menu entries in the boot display.

Patch now in Belenos repo. Please comment if you dissent from fixed status.

Di, 01/13/2015 - 19:14
Status:needs more info» fixed
Di, 01/27/2015 - 19:15
Status:fixed» closed

Automatically closed -- issue fixed for 2 weeks with no activity.