** Tags removed: disco
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mime-support in Ubuntu.
https://bugs.launchpad.net/bugs/1825420
Title:
package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
install/upgrade:
This is likely a duplicate of
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1828639.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mime-support in Ubuntu.
https://bugs.launchpad.net/bugs/1825420
Title:
package
I tested an upgrade from Ubuntu 18.10 to Ubuntu 19.04 today with some of
the packages from the DuplicateSignature.txt installed e.g.:
Start-Date: 2019-09-25 17:14:37
Commandline: apt-get install bamfdaemon mime-support
Requested-By: bdmurray (1000)
Install: bamfdaemon:amd64
** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mime-support in Ubuntu.
https://bugs.launchpad.net/bugs/1825420
Title:
package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
install/upgrade:
** Changed in: ubuntu-mate
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mime-support in Ubuntu.
https://bugs.launchpad.net/bugs/1825420
Title:
package linux-image-5.0.0-13-generic
So, 4 weeks later, after my previous comments, and now running stably:
Upgraded to 5.0.0-15 today via command line with 'do-release-upgrade'.
The triggers looping error still happens but this gets mopped up by
dpkg --configure -a which the upgrade script autoruns for you.
The 'system error
Upgraded today from 18.10 and encountered same issue:
Could not install 'linux-image-5.0.0-13-generic'
The upgrade will continue but the 'linux-image-5.0.0-13-generic' package
may not be in a working state. Please consider submitting a bug report
about it.
Could not install the upgrades
The
** Changed in: linux (Ubuntu)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mime-support in Ubuntu.
https://bugs.launchpad.net/bugs/1825420
Title:
package
I went back to the 4.18 kernel but am not running VirtualBox (running
bare metal).
Also seeing issues with libglib. gnome-shell won't run due to a trap in
libglib-2.0.so:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826025
--
You received this bug notification because you are a
Update to 2 hours ago:
Started getting segfault problems with libglib. Again re-install fixed
that but then I was getting segfaults elsewhere too.
I have now reverted to a full system backup of 18.10 that I made earlier
&& will probably stay on that for a bit longer.
--
You received this bug
I noticed that the OP had VirtualBox installed, same for me. This taints
the kernel ...
Are people who posted about going back to the old kernel using VBox?
So, re-installing 'VirtualBox' and ubuntu package 'menu' worked for me,
and keeping the new kernel
Suggest "dmesg | grep vbox" (YMMV)
I
On 25/4/19 8:31 am, Troels Petersen wrote:
> I also reverted to Linux kernel 4.18.0-13-generic (The one that ships
> with Ubuntu 18.10) after upgrading to 19.04.
>
> System: HP Spectre 13 v000nf, 8 GB Memory, Dual core Intel i5-6200U CPU
> @ 2.30 GHz, Intel HD Graphics 520 (Skylake GT2)
>
> When
I also reverted to Linux kernel 4.18.0-13-generic (The one that ships
with Ubuntu 18.10) after upgrading to 19.04.
System: HP Spectre 13 v000nf, 8 GB Memory, Dual core Intel i5-6200U CPU
@ 2.30 GHz, Intel HD Graphics 520 (Skylake GT2)
When running 'sudo apt upgrade' it complains about a missing
System: Dell Studio XPS 8300 64bit. memory: 7.8 GiB. CPU: Intel® Core™ i7-2600
CPU @ 3.40GHz × 8.
Graphics AMD® Juniper.
Upgrading from perfectly good 18.10.
Before this bug appeared another error message had stated
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such
file
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mime-support (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mime-support in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bamf (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mime-support in Ubuntu.
More info from post #4
Tried another upgrade from Ubuntu 18.10, which failed once again. I was
unable to upload the errors but at approximately the 60% mark of the
actual installation, a message was generated that the upgrade would
probably fail.
The error messages at this point included a GDK
Upgrading a cloud image, I couldn't reproduce it. I also tried
installing mate-desktop-environment-core + mate-dock-applet (because it
depends on bamfdaemon) before upgrading, and still couldn't reproduce. I
will install a cosmic mate desktop and see if I can reproduce this
problem when upgrading.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a
Faced same problem while upgrading from 18.10 to 19.04
Upgrade completed but showed
" Could not install 'linux-image-5.0.0-13-generic'
The upgrade will continue but the 'linux-image-5.0.0-13-generic' package
may not be in a working state. Please consider submitting a bug report about it.
Faced same problem while upgrading from 18.10 to 19.04
Upgrade completed but showed
" Could not install 'linux-image-5.0.0-13-generic'
The upgrade will continue but the 'linux-image-5.0.0-13-generic' package
may not be in a working state. Please consider submitting a bug report about it.
Confirmed during upgrade of clean fully-updated Ubuntu MATE 18.10 to
Ubuntu MATE 19.04, so I have marked Ubuntu MATE as affected by this bug.
** Also affects: ubuntu-mate
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-firmware (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
Same error message for me. Unable to boot into the 4 kernel backup as
well. Repeatedly boots to the login screen, which shows my name but
refuses to accept my password.
Attempted installation with the beta and now the released version with
same result.
Running standard Ubuntu 18.10 - at least I
Also affected: Ubuntu MATE 18.10 -> 19.04 Upgrade. Normal system (not
VM). 18.10 was a hardly used clean install of Ubuntu MATE, up-to-date
patch status before update. Install appears complete and OK ...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Also affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
27 matches
Mail list logo
