Re: Upgrade from 14.04 to 16.04 went bad

2016-03-29 Thread EdLesMann
On 03/29/2016 12:50 PM, Alberto Salvia Novella wrote:
> EdLesMann:
>> Most of the guides I see online for submitting bug reports
>> kinda require the system to be in a mostly working state.
> 
> You can do this!:
> (https://help.ubuntu.com/community/ReportingBugs#Filing_bugs_at_Launchpad.net)

Thanks!

I did some digging around and chris hermansen also helped by sending me
a few links. It seems that a lot of the error messages that turned up in
my log are reported already. I added a 'me too' to a few of them. I am
planning on rebuilding the laptop from scratch later.

I guess my 14.04 systems will just have to stay 14.04 for a while until
I can rebuild them to 16.04.




-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality


Re: Upgrade from 14.04 to 16.04 went bad

2016-03-29 Thread Alberto Salvia Novella

EdLesMann:
> Most of the guides I see online for submitting bug reports
> kinda require the system to be in a mostly working state.

You can do this!:
(https://help.ubuntu.com/community/ReportingBugs#Filing_bugs_at_Launchpad.net)


-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality


Upgrade from 14.04 to 16.04 went bad

2016-03-27 Thread EdLesMann
Greetings,

Every system I have is Lubuntu. Just getting that out there at the
beginning. :-)

I have been tinkering with and using the 16.04 daily builds for a while
on a few I-really-don't-care-what-happens-dev-boxes. Things have been
pretty solid so far. The few bugs I found I reported, but no major
issues. I have many 14.04 systems that I am planning on updating to
16.04. I thought I would test a few of the systems I don't care so much
for and see how an update goes.

The first was a VM. It threw a bunch of weird messages about systemd and
init packages, but completed and seems to be functioning...but it isn't
really anything more then a default install (I roll back my test changes
to a base install + updates).

I decided to test something a bit more real (but expecting it to have
issues). The laptop I occasionally play steam games on but mostly just
watch movies in bed with.

Oh no...it did not go so well.

First, A LOT of messages about systemd and init packages conflicting or
missing.

Second, I got an error saying that there were too many errors. That was
slightly terrifying and my first sinking feeling that this wasn't going
to end well...But it sent me on to a dpkg recovery process so that made
me feel a bit better until...

Third, I got errors about the dpkg repair process (something about not
being able to write apport errors because they already existed)...uh oh;
no more warm fuzzies for me...

Fourth, at this point I have just been clicking 'OK' letting the
installer do its thing through all of these error messages and as it was
doing something about those dpkg repair messages, it got to the point
where it was rebuilding the DKMS kernel modules...then the screen went
blank...but I could still tell the laptop was doing /something/. At the
very least the caps light still turned on and off but I couldn't see any
other sign of life. After about 30 minutes of just sitting there, I
checked again and it was just dead. No light changes with caps/num lock,
no virtual terminal switching, nothing at all. I couldn't even ssh into
the laptop any more. So I hard rebooted. Insta-kernel-panic. As soon as
I start to boot, it just dies. None of the kernels (pre or post update)
work. I tried a few tricks and it just flat out panics.

The good thing is that there really isn't anything on this laptop I care
about. I can easily wipe and start over. I can also liveCD boot and
check out the disk contents too.

However, before I do a re-install to 16.04 I thought it was worth asking
if there is interest in me attempting to salvage logs or do any kind of
post-mortum. Most of the guides I see online for submitting bug reports
kinda require the system to be in a mostly working state. This one
ain't. Not even close. A liveCD is the best I can do for this guy right now.

What logs should I get? How much should I provide?

I really want smooth updates for my other 14.04 boxes which is why I
wanted to test and give feedback now. I expected issues, but I didn't
quite expect a complete insta-panic. :-{

Anyway, if there is anyone interested in trying to figure out what went
wrong, let me know. I will gladly pull whatever information you want.
Anything I can do to help make this smoother later on. :-)

Thanks!


-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality