[neon] [Bug 366285] System is unable to boot after installing a new copy of KDE neon on UEFI enabled systems

[Jonathan Riddell via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366285

Jonathan Riddell  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #13 from Jonathan Riddell  ---
Fixed on today's images

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 366285] System is unable to boot after installing a new copy of KDE neon on UEFI enabled systems

[Lucas Finsterbusch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366285

--- Comment #12 from Lucas Finsterbusch  ---
Well, i've tried it with an automatic repair on a new neon live session, but
nothing... with this little boot-repair thingy... maybe fixing it manually will
do something.

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 366285] System is unable to boot after installing a new copy of KDE neon on UEFI enabled systems

[Juan Pablo Berdejo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366285

--- Comment #11 from Juan Pablo Berdejo  ---
¿There is a way to manually fix the grub.cfg after the fresh install?

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 366285] System is unable to boot after installing a new copy of KDE neon on UEFI enabled systems

[Juan Pablo Berdejo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366285

Juan Pablo Berdejo  changed:

   What|Removed |Added

 CC||jpberd...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 366285] System is unable to boot after installing a new copy of KDE neon on UEFI enabled systems

[Lucas Finsterbusch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366285

Lucas Finsterbusch  changed:

   What|Removed |Added

Summary|System is unable to boot|System is unable to boot
   |after installing a new copy |after installing a new copy
   |of KDE neon in UEFI enabled |of KDE neon on UEFI enabled
   |systems |systems

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 366285] System is unable to boot after installing a new copy of KDE neon in UEFI enabled systems

[Lucas Finsterbusch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366285

--- Comment #10 from Lucas Finsterbusch  ---
Unfortunately, yes... I've tried it two days ago...

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 366285] System is unable to boot after installing a new copy of KDE neon in UEFI enabled systems

[J Janz via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366285

--- Comment #9 from J Janz  ---
(In reply to Liam Murphy from comment #6)
> Janz, any possibility of us getting that image?
Sorry for taking this long:
https://www.dropbox.com/s/dqi98lvj8sy655u/neon-useredition-20160713-1223-amd64.iso?dl=0
(I didn't test downloading it to see if everything went well so let us know
here if this file is not working so I can re-upload it and people coming for a
workaround can use it.)

(In reply to ZrL from comment #8)
> Same problem on a fresh install !
Was it with thursday's new iso (neon-useredition-20160804-1018-amd64.iso), yet?

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 366285] System is unable to boot after installing a new copy of KDE neon in UEFI enabled systems

[Marcus via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366285

Marcus  changed:

   What|Removed |Added

 CC||bio...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 366285] System is unable to boot after installing a new copy of KDE neon in UEFI enabled systems

[ZrL via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366285

ZrL  changed:

   What|Removed |Added

 CC||k.bre...@outlook.com

--- Comment #8 from ZrL  ---
Hi there !
Same problem on a fresh install !

I had to use this image + update OS to get something up to date:
neon-useredition-20160705-0929-amd64.iso.

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 366285] System is unable to boot after installing a new copy of KDE neon in UEFI enabled systems

[J Janz via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366285

--- Comment #7 from J Janz  ---
(In reply to Liam Murphy from comment #6)
> Janz, any possibility of us getting that image? I would really like getting
> Neon on my machine. That does make me think, Neon did indeed use to work a
> month or two ago on this same machine.

I thought it could happen when I wrote that. =)  It is in my GDrive currently
and I even thought of sharing the link but, as I was afraid of, it is almost
full and I'll need to remove it. Right now I'm trying to send it to my dropbox,
which I never use so it would be ok to keep it there until we get this fixed.
The only issue is that I'm at work right now, where both Dropbox and GDrive are
blocked, so I'm trying that from my phone, which might demand a little patience
(specially from me). =O

Unless that, and I'm not enough into KDE Bugs rules to know but, this could
qualify as a workaround and then I could attach it here (file was indeed found
in my work's PC)...

Any of the experienced ones among you could tell me?

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 366285] System is unable to boot after installing a new copy of KDE neon in UEFI enabled systems

[Liam Murphy via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366285

--- Comment #6 from Liam Murphy  ---
(In reply to J Janz from comment #4)
> Thank God I happened to have an image of a few weeks ago
> (neon-useredition-20160713-1223-amd64.iso) and that one installed with no
> erros, same as current one, but installed system boots and works ok! Updated
> (even got plasma 5.7.3 last night) and still alright (well, just that sound
> never came up with onboard HDMI and AMD R9 270, also through HDMI, only goes
> from boot splash to dead black screen but I guess those are separate bugs).
> 
> Well, now I'm hoping that having a closer date to where things were still on
> track might help to find a related change from then to current version and
> it can be fixed or reverted.

Janz, any possibility of us getting that image? I would really like getting
Neon on my machine. That does make me think, Neon did indeed use to work a
month or two ago on this same machine.

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 366285] System is unable to boot after installing a new copy of KDE neon in UEFI enabled systems

[Jonathan Riddell via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366285

--- Comment #5 from Jonathan Riddell  ---
Harald: what did you predict would happen?

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 366285] System is unable to boot after installing a new copy of KDE neon in UEFI enabled systems

[J Janz via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366285

--- Comment #4 from J Janz  ---
Thank God I happened to have an image of a few weeks ago
(neon-useredition-20160713-1223-amd64.iso) and that one installed with no
erros, same as current one, but installed system boots and works ok! Updated
(even got plasma 5.7.3 last night) and still alright (well, just that sound
never came up with onboard HDMI and AMD R9 270, also through HDMI, only goes
from boot splash to dead black screen but I guess those are separate bugs).

Well, now I'm hoping that having a closer date to where things were still on
track might help to find a related change from then to current version and it
can be fixed or reverted.

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 366285] System is unable to boot after installing a new copy of KDE neon in UEFI enabled systems

[Liam Murphy via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366285

Liam Murphy  changed:

   What|Removed |Added

 CC||l...@lpmdesigns.com

--- Comment #3 from Liam Murphy  ---
I am also having this issue. 

I have a dual boot with Windows, but separate SSD's for Windows and Linux. I've
attempted manual partition editing, and the default "erase disk" and let Neon
do the work. 

Getting same GRUB Minimal screen after rebooting when the install is complete. 

I get no errors during the install.

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 366285] System is unable to boot after installing a new copy of KDE neon in UEFI enabled systems

[J Janz via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366285

J Janz  changed:

   What|Removed |Added

 CC||k...@juniorjanz.net

--- Comment #2 from J Janz  ---
I can confirm this: not only for VMs, I went for a refresh at my mediacenter
(just regular PC next to TV) and gave it a clean KDE Neon User install and got
to the same unformatunate situation. Either with Secure Boot on or off. The
thing is that it used to work well.*

I didn't try to disable UEFI and try it with Legacy but, by the description of
this bug, it seems it'll work. I'll try and either way and post here what it
gives.

* I first tried Developer edition until User came out and both, freshly
installed, didn't have this boot issue. Then I went back to Kubuntu 15.10 to
use fglrx until I got better news from open AMD drivers (all 3, KDE Neon Dev
and User, and Kubuntu, with UEFI and Secure Boot both on) and now hit this.

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 366285] System is unable to boot after installing a new copy of KDE neon in UEFI enabled systems

[Harald Sitter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366285

Harald Sitter  changed:

   What|Removed |Added

   Assignee|neon-b...@kde.org   |j...@jriddell.org

--- Comment #1 from Harald Sitter  ---
Jonathan. I do so very much hope this isn't what I predicted would happen.

-- 
You are receiving this mail because:
You are watching all bug changes.