Comment #11 is addressed in bug 1506169 for which I've created a fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508157
Title:
Kernel not upgraded during Vivid -> Wily upgrade
To manage notific
Just checked the forums this AM and four other people report the same
issue:
http://ubuntuforums.org/showthread.php?t=2299964
And more Wily kernel + nVidia woes:
http://ubuntuforums.org/showthread.php?t=2300068&p=13377864&posted=1#post13377864
--
You received this bug notification because you
@brian-murray
Done. New possibly duplicate report is here:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/1509305
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508157
Title:
That other bug that Bryan posted about made me do some digging in an
install that had been affected by unrelated bug #1489147.
I was using the same hardware as in this bug and had to use the boot
parameter nomodeset to even get casper/ubiquity to run w/o a black
screen - this resulted in a complet
If you're installing a proprietary driver using the GUI it might be this
bug instead - Bug 1506169 instead
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508157
Title:
Kernel not upgraded during Vi
@zob your logs were not added, could you please open a new bug report
(using ubuntu-bug ubuntu-release-upgrader-core) and I'll mark it as a
duplicate if it is one. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Happened to me too after final release. I too have propietary nvidia
drivers on the machine in question. I added my logs with ubuntu-bug (I
think).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508157
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508
Bug 1470577 is another case of the upgraded kernel being considered an
"Unused dependency", however in that upgrade there were a plethora of
issues contacting the mirror. This is something we don't see in this
bug.
Bug 1315978 is another case of the upgraded kernel being considered an
"Unused depe
We can also see that the 4.2 kernel is actually installed during the
upgrade:
4612 Setting up linux-image-4.2.0-16-generic (4.2.0-16.19) ...^M
4613 Running depmod.^M
4614 update-initramfs: deferring update (hook will be called later)^M
4615 Examining /etc/kernel/postinst.d.^M
4616 run-parts: execu
>From VarLogDistUpgradeMain.log we can see the following decisions being
made:
2015-10-20 12:03:36,420 DEBUG Foreign:
2015-10-20 12:03:36,420 DEBUG identifyObsoleteKernels()
2015-10-20 12:03:44,628 DEBUG identifyObsoleteKernels found 'set()'
2015-10-20 12:03:44,628 DEBUG forced_obsoletes: ['deskt
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1508157
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
In retrospect I probably should have selected that this posed a
potential security risk because the Vivid kernel may fail to upgrade
properly, and even if it does Vivid will go EOL in about 3 months, so
this probably should be flagged for security. Sadly I'm not sure how to
do that, sorry.
--
You
13 matches
Mail list logo
