Give Discoing a go with Kubuntu 19.04 Disco

[NoWorries]

Because this is rc1, I have decided to wait until further release candidates come, and if the problem is not fixed I might take action.

I have previously reported bugs on Libreoffice, but I find it takes a long time before it is fixed. For example, I have been putting up with a white flash before a video is started in Impress for years. This has finally been fixed with the current version that I am keeping, ie 6.1.4.2. Because of this, I will not upgrade to a new version until I am convinced that it performs as well as 6.1.4.2

[NoWorries]

Since my last post on the status of my system, I have had, in the past couple of days, hundreds of updates for KDE Plasma 5.15.3. I was a bit hasty in using my system partway through the days this update took place. So I found applications acting up. For example, I tried Kdenlive to do a render and it was going to take 7 hours!! Anyhow, this reference; https://news.softpedia.com/news/kde-...e-525273.shtml gives the updates that will be make in the coming weeks. I am very pleased with this new update and my impression is that it is slightly faster. So my Info Centre now shows this:



So with the current rate of progress, Disco is going to be some mother of a distribution. While I have the LibreOffice version locked in until they get problems solved, I use Disco as my production system as it performs much much better than my 18.04 LTS on my ASUS Laptop.

Thanks to all those who are making Disco so great.

[acheron]

Because this is rc1, I have decided to wait until further release candidates come, and if the problem is not fixed I might take action.

I have previously reported bugs on Libreoffice, but I find it takes a long time before it is fixed. For example, I have been putting up with a white flash before a video is started in Impress for years. This has finally been fixed with the current version that I am keeping, ie 6.1.4.2. Because of this, I will not upgrade to a new version until I am convinced that it performs as well as 6.1.4.2

Possibly this: https://launchpad.net/bugs/1820062

[NoWorries]

Possibly this: https://launchpad.net/bugs/1820062

Thanks for the reference. Unfortunately none of the solutions given worked on my grandson's Disco system. Maybe some of the changes have yet to be released into Disco. So, once again, I will wait for further updates.

Update:

In my previous post #20, I had installed gstreamer1.0-plugins-* which meant that all the packages in your reference were already installed on this system.

[NoWorries]

I have had LibreOffice updated to the next version on my Grandson's Disco laptop, and it has the same problems with inserted videos. So I have posted a bug report on launchpad with the graphic I used on this site.

[NoWorries]

I found that when I used the launchpad site https://launchpad.net/bugs/1820062 for this bug report, I found that it did not match the gtk3 problems reported there. So I have opened a new bug report on launchpad and this is at https://bugs.launchpad.net/launchpad/+bug/1821849.

At this stage Launchpad has neither confirmed or assigned this bug. So if you have encountered this problem with embedded videos in LibreOffice Impress version 6.2.2.2, ie



I would appreciate extra acknowledgement on this bug site.

I am now happy that this Bug has been Confirmed as it effects multiple users. Hopefully it won't be too long before someone is assigned to solving the problems cited in this bug report.

[acheron]

Qt 5.12.2 landing in disco.

[NoWorries]

Possibly this: https://launchpad.net/bugs/1820062

I have been having a lot of correspondence with a bug report that I started at https://bugs.launchpad.net/ubuntu/+s...e/+bug/1821849.

The final realization was that this bug does not occur with Ubuntu 19.04 as stated in #10. So this is a Kubuntu problem. Is launchpad the best place to get this sorted out or is there somewhere else that I should head? My impression is that some library files are missing for LibreOffice 6.2.2.2 as was the case for version 6.1.4.2.

[JoelParke]

Connector to extensions broken??

I just finished giving Kubuntu 19.04 a spin (daily build)
Operating System: Kubuntu 19.04
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.2
Kernel Version: 5.0.0-8-generic
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz
Memory: 15.6 GiB of RAM

At first, I thought that I had issues with not being able to use extensions and having chrome-gnome-shell fail:
'Unable to locate GNOME Shell settings or version. Make sure it is installed and running.'

After some scratching of my head, I realized that I had to have a gnome driven desktop for this to work and Kubuntu was not it.

So I can now say that Kubuntu is working as expected.

Thanks,
Joel Parke

[Flavio R. Cavalcanti]

"Kernel Panic, not syncing, Attempted to kill init"

Kernel 5.0.0.11 doesn't boot properly ─ It boots only in Recovery mode

Kernel 5.0.0.8 boots properly ─ no problem.

But maybe there is another reason, that not Kernel 5.0.0.11 ─ Don't want to do many different tests, now.

Operating System: Kubuntu 19.04
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.2
Kernel Version: 5.0.0-8-generic
OS Type: 64-bit
Processors: 2 × Intel® Core™2 Duo CPU E7300 @ 2.66GHz
Memory: 3,8 GiB of RAM

[NoWorries]

Sorry that you are having trouble with Kernel 5.0.0.11 as initially my system was only only booting 5.0.0.8 even though Kernel 5.0.0.11 had been installed.

I tracked down my problem by using grub-customizer that I have installed on Bionic which is in a separate partition on the same disk with Disco installed. I had to rearranged the boot order and after that it worked without a problem.

If you do not have this option, it looks like you will have to edit grub and I am not an expert on doing this. There are others on this forum who would be able to help with this.

[Flavio R. Cavalcanti]

I was not sure the problem was caused by Kernel 5.0.0.11 ─ so, did you confirm?Well, I am not using Grub-Customizer, but it is easy to repeatedly boot to 5.0.0.8, since my Grub is set to remember and auto select last used distro / option.

[NoWorries]

I was not sure the problem was caused by Kernel 5.0.0.11 ─ so, did you confirm?

I have been using the Kernel 5.0.0-11 for some days now and have not had any trouble with it.

Muon packages that I have are:

[Flavio R. Cavalcanti]

These were the updates Saturday ─ also, removed previous Kernel 5.0.0.7 ─ and boot failed since Sunday morning.

Commit Log for Sat Apr 13 09:22:36 2019

Completely removed the following packages:
linux-headers-5.0.0-7
linux-headers-5.0.0-7-generic
linux-image-5.0.0-7-generic
linux-modules-5.0.0-7-generic
linux-modules-extra-5.0.0-7-generic

Upgraded the following packages:
apport (2.20.10-0ubuntu26) to 2.20.10-0ubuntu27
apport-kde (2.20.10-0ubuntu26) to 2.20.10-0ubuntu27
ca-certificates-java (20180516ubuntu1) to 20190405ubuntu1
console-setup (1.178ubuntu11) to 1.178ubuntu12
console-setup-linux (1.178ubuntu11) to 1.178ubuntu12
cups-browsed (1.22.4-1) to 1.22.5-1
cups-filters (1.22.4-1) to 1.22.5-1
cups-filters-core-drivers (1.22.4-1) to 1.22.5-1
firefox (66.0.2+build1-0ubuntu1) to 66.0.3+build1-0ubuntu1
firefox-locale-en (66.0.2+build1-0ubuntu1) to 66.0.3+build1-0ubuntu1
firefox-locale-pt (66.0.2+build1-0ubuntu1) to 66.0.3+build1-0ubuntu1
fwupd (1.2.5-1) to 1.2.5-1ubuntu1
fwupd-signed (1.5+1.2.5-1) to 1.6+1.2.5-1ubuntu1
gir1.2-freedesktop (1.60.0-1) to 1.60.1-1
gir1.2-glib-2.0 (1.60.0-1) to 1.60.1-1
gir1.2-gtk-3.0 (3.24.7-1ubuntu1) to 3.24.8-1ubuntu1
gtk-update-icon-cache (3.24.7-1ubuntu1) to 3.24.8-1ubuntu1
initramfs-tools (0.131ubuntu18) to 0.131ubuntu19
initramfs-tools-bin (0.131ubuntu18) to 0.131ubuntu19
initramfs-tools-core (0.131ubuntu18) to 0.131ubuntu19
intel-media-va-driver (18.4.0+dfsg1-1) to 18.4.1+dfsg1-2ubuntu1
keyboard-configuration (1.178ubuntu11) to 1.178ubuntu12
kmod (25-1ubuntu3) to 25-1ubuntu4
language-pack-en (1:19.04+20190408) to 1:19.04+20190412
language-pack-en-base (1:19.04+20190304) to 1:19.04+20190412
language-pack-pt (1:19.04+20190408) to 1:19.04+20190412
language-pack-pt-base (1:19.04+20190304) to 1:19.04+20190412
libc-bin (2.29-0ubuntu1) to 2.29-0ubuntu2
libc-dev-bin (2.29-0ubuntu1) to 2.29-0ubuntu2
libc6 (2.29-0ubuntu1) to 2.29-0ubuntu2
libc6-dbg (2.29-0ubuntu1) to 2.29-0ubuntu2
libc6-dev (2.29-0ubuntu1) to 2.29-0ubuntu2
libc6:i386 (2.29-0ubuntu1) to 2.29-0ubuntu2
libcupsfilters1 (1.22.4-1) to 1.22.5-1
libegl-mesa0 (19.0.1-1ubuntu2) to 19.0.2-1ubuntu1
libegl1-mesa (19.0.1-1ubuntu2) to 19.0.2-1ubuntu1
libfontembed1 (1.22.4-1) to 1.22.5-1
libfwupd2 (1.2.5-1) to 1.2.5-1ubuntu1
libgbm1 (19.0.1-1ubuntu2) to 19.0.2-1ubuntu1
libgirepository-1.0-1 (1.60.0-1) to 1.60.1-1
libgl1-mesa-dri (19.0.1-1ubuntu2) to 19.0.2-1ubuntu1
libgl1-mesa-dri:i386 (19.0.1-1ubuntu2) to 19.0.2-1ubuntu1
libgl1-mesa-glx (19.0.1-1ubuntu2) to 19.0.2-1ubuntu1
libglapi-mesa (19.0.1-1ubuntu2) to 19.0.2-1ubuntu1
libglapi-mesa:i386 (19.0.1-1ubuntu2) to 19.0.2-1ubuntu1
libglx-mesa0 (19.0.1-1ubuntu2) to 19.0.2-1ubuntu1
libglx-mesa0:i386 (19.0.1-1ubuntu2) to 19.0.2-1ubuntu1
libgraphicsmagick++-q16-12 (1.4~hg15916-1) to 1.4~hg15916-2
libgraphicsmagick-q16-3 (1.4~hg15916-1) to 1.4~hg15916-2
libgtk-3-0 (3.24.7-1ubuntu1) to 3.24.8-1ubuntu1
libgtk-3-bin (3.24.7-1ubuntu1) to 3.24.8-1ubuntu1
libgtk-3-common (3.24.7-1ubuntu1) to 3.24.8-1ubuntu1
libkmod2 (25-1ubuntu3) to 25-1ubuntu4
libkpmcore7 (3.3.0-4) to 3.3.0-5
libnss-systemd (240-6ubuntu4) to 240-6ubuntu5
libopenexr23 (2.2.1-4build1) to 2.2.1-4.1
libosmesa6:i386 (19.0.1-1ubuntu2) to 19.0.2-1ubuntu1
libpam-systemd (240-6ubuntu4) to 240-6ubuntu5
libqt5concurrent5 (5.12.2+dfsg-4) to 5.12.2+dfsg-4ubuntu1
libqt5core5a (5.12.2+dfsg-4) to 5.12.2+dfsg-4ubuntu1
libqt5dbus5 (5.12.2+dfsg-4) to 5.12.2+dfsg-4ubuntu1
libqt5gui5 (5.12.2+dfsg-4) to 5.12.2+dfsg-4ubuntu1
libqt5network5 (5.12.2+dfsg-4) to 5.12.2+dfsg-4ubuntu1
libqt5opengl5 (5.12.2+dfsg-4) to 5.12.2+dfsg-4ubuntu1
libqt5printsupport5 (5.12.2+dfsg-4) to 5.12.2+dfsg-4ubuntu1
libqt5sql5 (5.12.2+dfsg-4) to 5.12.2+dfsg-4ubuntu1
libqt5sql5-mysql (5.12.2+dfsg-4) to 5.12.2+dfsg-4ubuntu1
libqt5sql5-sqlite (5.12.2+dfsg-4) to 5.12.2+dfsg-4ubuntu1
libqt5test5 (5.12.2+dfsg-4) to 5.12.2+dfsg-4ubuntu1
libqt5widgets5 (5.12.2+dfsg-4) to 5.12.2+dfsg-4ubuntu1
libqt5xml5 (5.12.2+dfsg-4) to 5.12.2+dfsg-4ubuntu1
librsvg2-2 (2.44.10-1) to 2.44.10-2
librsvg2-common (2.44.10-1) to 2.44.10-2
libsoup-gnome2.4-1 (2.66.0-1) to 2.66.1-1
libsoup2.4-1 (2.66.0-1) to 2.66.1-1
libsystemd0 (240-6ubuntu4) to 240-6ubuntu5
libsystemd0:i386 (240-6ubuntu4) to 240-6ubuntu5
libudev1 (240-6ubuntu4) to 240-6ubuntu5
libudev1:i386 (240-6ubuntu4) to 240-6ubuntu5
libvte-2.91-0 (0.56.0-1ubuntu1) to 0.56.1-1ubuntu1
libvte-2.91-common (0.56.0-1ubuntu1) to 0.56.1-1ubuntu1
libxatracker2 (19.0.1-1ubuntu2) to 19.0.2-1ubuntu1
libxmmsclient6 (0.8+dfsg-18.1build7) to 0.8+dfsg-18.2
linux-generic (5.0.0.8.9) to 5.0.0.11.12
linux-headers-generic (5.0.0.8.9) to 5.0.0.11.12
linux-image-generic (5.0.0.8.9) to 5.0.0.11.12
linux-libc-dev (5.0.0-8.9) to 5.0.0-11.12
locales (2.29-0ubuntu1) to 2.29-0ubuntu2
mesa-va-drivers (19.0.1-1ubuntu2) to 19.0.2-1ubuntu1
mesa-vdpau-drivers (19.0.1-1ubuntu2) to 19.0.2-1ubuntu1
mesa-vulkan-drivers (19.0.1-1ubuntu2) to 19.0.2-1ubuntu1
multiarch-support (2.29-0ubuntu1) to 2.29-0ubuntu2
python3-apport (2.20.10-0ubuntu26) to 2.20.10-0ubuntu27
python3-distupgrade (1:19.04.15) to 1:19.04.16
python3-problem-report (2.20.10-0ubuntu26) to 2.20.10-0ubuntu27
python3-renderpm (3.5.13-1) to 3.5.18-1
python3-reportlab (3.5.13-1) to 3.5.18-1
python3-reportlab-accel (3.5.13-1) to 3.5.18-1
python3-software-properties (0.97.9) to 0.97.11
qt5-gtk-platformtheme (5.12.2+dfsg-4) to 5.12.2+dfsg-4ubuntu1
software-properties-common (0.97.9) to 0.97.11
software-properties-qt (0.97.9) to 0.97.11
systemd (240-6ubuntu4) to 240-6ubuntu5
systemd-sysv (240-6ubuntu4) to 240-6ubuntu5
ubuntu-advantage-tools (18) to 19.4
ubuntu-release-upgrader-core (1:19.04.15) to 1:19.04.16
udev (240-6ubuntu4) to 240-6ubuntu5
wpasupplicant (2:2.6-21ubuntu2) to 2:2.6-21ubuntu3
xml-core (0.18) to 0.18+nmu1
xserver-xorg-input-libinput (0.28.2-1) to 0.28.2-2
xserver-xorg-input-wacom (1:0.36.1-0ubuntu1) to 1:0.36.1-0ubuntu2

Installed the following packages:
linux-headers-5.0.0-11 (5.0.0-11.12)
linux-headers-5.0.0-11-generic (5.0.0-11.12)
linux-image-5.0.0-11-generic (5.0.0-11.12)
linux-modules-5.0.0-11-generic (5.0.0-11.12)
linux-modules-extra-5.0.0-11-generic (5.0.0-11.12)
python3-cffi-backend (1.12.2-1)
python3-nacl (1.3.0-2)
python3-pymacaroons (0.13.0-2)

[Flavio R. Cavalcanti]

Well, now I think there was no problem with Kubuntu 19.04 nor with Kernel 5.0.0.11 ─ because I have tried later, again, and... it booted Ok once, twice... and so on, yesterday ─ and today, again.

The only event I could think to be the reason of the "fix", was a little update, at Sunday evening:

Commit Log for Sun Apr 14 17:12:12 2019

Upgraded the following packages:
fuse (2.9.8-1ubuntu1) to 2.9.9-1ubuntu1
libfuse2 (2.9.8-1ubuntu1) to 2.9.9-1ubuntu1
update-notifier-common (3.192.15) to 3.192.18

Also, I did run a dpkg-reconfigure grub-pc in order to set Grub not to write a bootloader at external USB-SSD, anymore.

It was an attempt to stop the "failed boot detection" message while booting.

And, no, it didn't stop this messages, as I can see at today's /var/log/boot.log:

------------ Tue Apr 16 11:51:35 -03 2019 ------------
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password R…s to Plymouth Directory Watch.
[  OK  ] Reached target Local Encrypted Volumes.
[  OK  ] Listening on Load/Save RF …itch Status /dev/rfkill Watch.
[  OK  ] Started Flush Journal to Persistent Storage.
[*     ] (1 of 2) A start job is running for /dev/disk/by-uuid/085e6ca1-963b-47bd-9aac-fd71e8760150 (14s / 1min 30s)
M
[**    ] (1 of 2) A start job is running for /dev/disk/by-uuid/085e6ca1-963b-47bd-9aac-fd71e8760150 (14s / 1min 30s)
M
[***   ] (1 of 2) A start job is running for /dev/disk/by-uuid/085e6ca1-963b-47bd-9aac-fd71e8760150 (15s / 1min 30s)
M
[ ***  ] (2 of 2) A start job is running for /dev/disk/by-uuid/4224469c-9ad0-41d7-8e64-4b8d862ed636 (15s / 1min 30s)
M
[  OK  ] Found device S2_Portable Swap11.
         Activating swap /dev/disk/by-uuid/085e6ca1-963b-47bd-9aac-fd71e8760150...
[  OK  ] Found device S2_Portable Home11.
     Starting File System Check on /dev/disk/by-uuid/4224469c-9ad0-41d7-8e64-4b8d862ed636...
[  OK  ] Activated swap /dev/disk/by-uuid/085e6ca1-963b-47bd-9aac-fd71e8760150.
[  OK  ] Started File System Check Daemon to report status.
[  OK  ] Reached target Swap.
[  OK  ] Started File System Check on /dev/disk/by-uuid/4224469c-9ad0-41d7-8e64-4b8d862ed636.
     Mounting /home...
[  OK  ] Mounted /home.
[  OK  ] Reached target Local File Systems.
     Starting GRUB failed boot detection...
     Starting Load AppArmor profiles...
     Starting Set console font and keymap...
     Starting Create Volatile Files and Directories...
     Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Set console font and keymap.
[  OK  ] Started GRUB failed boot detection.
[  OK  ] Started Create Volatile Files and Directories.
     Starting Network Name Resolution...
     Starting Network Time Synchronization...

Just to note another message (since January, at least) when installing new / removing old Kernels:

The link /vmlinuz is a damaged link
Removing symbolic link vmlinuz 
you may need to re-run your boot loader[grub]
The link /initrd.img is a damaged link
Removing symbolic link initrd.img 
you may need to re-run your boot loader[grub]

But it didn't cause any problem, until last weekend. So, I don't know if it is a real problem.

Also, I have installed lm_sensors since November 2018, but had never runned sensors-detect, until last Sunday ─ after Boot problem.

It usually introduces 2 modules ─ and one of them is not found in all distros ─ so I had to edit /etc/modules to disable one of them:

[#]# Generated by sensors-detect on Sun Apr 14 14:03:36 2019
# Chip drivers
coretemp
# w83627ehf[/#]

But, these last things were done after the problem, and cannot explain its origin.

So, there are many variables to consider, and I am not able to try to understand what happened.

What matters is that there is no more any problem to boot with Kernel 5.0.0.11.