Focal Testing of Kubuntu 20.04 LTS

[rec9140]

Python2 is dead (https://www.python.org/doc/sunset-python-2/). So the process of removing it is sort of a forced process that is going on in basically every distro (*buntu/debian/fedora/arch etc.). It is quite likely to cause some issues (it you still use software that is python2 only), but it has to be removed, especially since it's an LTS release (with years of support). Python2 will not receive even security updates, so it has to be phased out (and there has been plenty of time for projects to migrate to python3).

Thanks for the reply... .. I will end here as I do not agree with that

Gwenview is available as a regular deb in the focal repos, you are not forced to install a snap version if you do not want to.

Well its in the install I just did, and not seeing any of that loop crap for snaps... I am making sure...

That will be on tomorrows agenda to lock out that stupid crap...

[rec9140]

Audio Notifications Slider - Can't unmute??

So after getting 20.04.02.04.20 and installed and then updated to anything that it offered...

So right now the only glitch I am finding is notification sounds... I can't unmute it!?

If I click the speaker it goes up and IMMEDIATELY GOES BACK to mute...

Slide it.. same thing.. slider drops back and mute icon...

Ummmm?

And where are the sounds for the notifications at now?? I've looked in the places I am familar with and not finding them...

I attached a grab of the menu I am talking about..

I get it its early daily... any hints

[NoWorries]

All in now fixed and glmark2 works without error on both 19.10 and 20.04

For several weeks now I have not been able to run glmark2 without error. I do not consider this problem to be because I use the pre-released option. I believe this is a Focal problem as glmark2 runs without error on my I also have a Kubuntu 19.10 system in a separate partition on my Laptop and after updates this morning, it also gave the same glmark2 problem.

The error that I get is:

:~$ glmark2
** GLX does not support GLX_EXT_swap_control or GLX_MESA_swap_control!
** Failed to set swap interval. Results may be bounded above by refresh rate.
=======================================================
glmark2 2014.03+git20150611.fa71af2d
=======================================================
OpenGL Information
GL_VENDOR:     VMware, Inc.
GL_RENDERER:   llvmpipe (LLVM 9.0.1, 256 bits)
GL_VERSION:    3.1 Mesa 20.1.0-devel (git-2799676 2020-02-05 focal-oibaf-ppa)
=======================================================
** GLX does not support GLX_EXT_swap_control or GLX_MESA_swap_control!
** Failed to set swap interval. Results may be bounded above by refresh rate.
[build] use-vbo=false: FPS: 916 FrameTime: 1.092 ms
** GLX does not support GLX_EXT_swap_control or GLX_MESA_swap_control!
** Failed to set swap interval. Results may be bounded above by refresh rate.
[build] use-vbo=true: FPS: 927 FrameTime: 1.079 ms
=======================================================
                          glmark2 Score: 921 
=======================================================

This error has been reported several years ago and the solutions I found did not work.

So I hope the solution is simple and I look forward to having glmark2 working again to keep monitoring improvements provided by gpu updates from oibaf.

[kubicle]

Care to elaborate on this? Please... As thats a problem.. if you are telling me the 3.x branch is now the only one... Houston we got a problem.

Python2 is dead (https://www.python.org/doc/sunset-python-2/). So the process of removing it is sort of a forced process that is going on in basically every distro (*buntu/debian/fedora/arch etc.). It is quite likely to cause some issues (it you still use software that is python2 only), but it has to be removed, especially since it's an LTS release (with years of support). Python2 will not receive even security updates, so it has to be phased out (and there has been plenty of time for projects to migrate to python3).

What URRGGHGH! Gwenview is something I rely on and based on other posts I plant to purge snapd as I don't want them... so as long as this can be neutered fine...

Gwenview is available as a regular deb in the focal repos, you are not forced to install a snap version if you do not want to.

[rec9140]

Rrrort Rhaggyy?

Python2 is no longer available..

Care to elaborate on this? Please... As thats a problem.. if you are telling me the 3.x branch is now the only one... Houston we got a problem.

Before removing Discovery this would lead to a (probable) snap link but this time I'm sure I run a .deb version of Gwenview.

What URRGGHGH! Gwenview is something I rely on and based on other posts I plant to purge snapd as I don't want them... so as long as this can be neutered fine...

I've got a brand new laptop coming in the AM thats going to be my test for 20.04 before hitting the new build...first time in 10 years I will be that/this current.

[kubicle]

And to help clarify, -proposed is the pre-release updates option in the Software Sources configuration tool

I'm starting to wonder if it is possibly a bit too easy to enable proposed in software sources (maybe there could be a clear warning dialog) and/or if the wording of "pre-release updates" is somehat confusing (I can easily see that people could thnk they need to enable that since they are running a "pre-release" version of kubuntu).

[NoWorries]

When using the proposed repositories, I find it better to, not get my knickers in a twist, when I get abnormal updates. Thanks for the insight into the problem and the developers have certainly fixed the problem very quickly.

I have just had a few updates and initramfs-tools is now at version 0.133ubuntu14.

When I used the word ubuntu in the previous line, it reminded me that yesterday I checked the download iso file size for Focal and found that the ubuntu version is 200MB larger than the kubuntu file.

[Snowhog]

Confirmed.

[MeMyself]

It appears the fix has uploaded already. Installed fine.

[MeMyself]

I'm taking to the uploader. They are going to try to fix it soon.

Thank you for the great information in your posts. Would it be better to keep the proposed active until this issue clears and then make it inactive, or if we uncheck proposed will the fix generate when ready?

[claydoh]

Again, this is the version of initramfs-tools in PROPOSED pocket.

NO-ONE SHOULD BE USING PACKAGES FROM PROPOSED :P :P

Packages in proposed are IN PROPOSED until they can be confirmed that they don't break things.

As you can see from the proposed migration excuses page, the proposed version is thoroughly borked.

[ATTACH=CONFIG]8646[/ATTACH]

And to help clarify, -proposed is the pre-release updates option in the Software Sources configuration tool

[acheron]

I'm taking to the uploader. They are going to try to fix it soon.

[Snowhog]

Thank you.

I'm running 20.04 on my laptop; not my production rig; so I wasn't worried.

Muon Package Manager wouldn't let me get into Configure Software Sources; as soon as I typed in my password it updated the package list and returned me to that list. Launched Discover and went to Settings. I scrolled down and see that I have Focal proposed (multiverse universe restricted main) marked.

This is the first issue I've had with Focal since I installed it (and had that repository marked). Like I said; not my production rig.

I'll just leave it on; won't reboot; and run apt update && apt full-upgrade periodically until the issue resolves.

I do thank you for the precise explanation of the issue.

[acheron]

This morning:

Setting up initramfs-tools (0.133ubuntu13) ...

Again, this is the version of initramfs-tools in PROPOSED pocket.

NO-ONE SHOULD BE USING PACKAGES FROM PROPOSED :P :P

Packages in proposed are IN PROPOSED until they can be confirmed that they don't break things.

As you can see from the proposed migration excuses page, the proposed version is thoroughly borked.

[Snowhog]

The usual. In a Konsole issue

sudo apt -f install
sudo dpkg --configure -a


Repeat them until no error msgs are reported.

Neither works in this case.

Added:
I wonder if this is a regression issue. I found a Debian bug report on the exact same problem (earlier kernel of course, but still the exact same issue):

Debian Bug report logs - #898720
E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1 (btrfs-zero-log no longer present)