As mentioned today at the 2017 openSUSE Conference, openSUSE Leap 42.3 entered the Beta Test Phase last week.
<https://software.opensuse.org/developer/en?release=developer>
This thread is for discussion.
[HR][/HR]I’ll mention the lack of a 42.3 Forums prefix at tomorrow’s conference.
… that link says 42.3 Alpha ???:?
This Thread will be either moved or (waste-) binned once the 42.3 prefix has been set-up for this Forum.
[HR][/HR]The Leap 42.3 testing has no Alpha/Beta/Release Candidate (RC) phases.
One can view the testing process as being similar to a “rolling release”.
Please, always mention the Build Number when adding comments and experiences to this thread or, raising Bug Reports.
I upgraded from 42.2 to 42.3 beta yesterday.
Starting K3b now (using GNOME Shell 3.20.4), the following problem pop-up (pasted from a terminal):
kernel version: "4.4.68-2-default"
(K3b::Core) System problems:
WARNING
PROBLEM: "MP3 Audio Decoder plugin not found."
DETAILS: "K3b could not load or find the MP3 decoder plugin. This means that you will not be able to create Audio CDs from MP3 files. Many Linux distributions do not include MP3 support for legal reasons."
SOLUTION: "To enable MP3 support, please install the MAD MP3 decoding library as well as the K3b MAD MP3 decoder plugin (the latter may already be installed but not functional due to the missing libmad). Some distributions allow installation of MP3 support via an online update tool."
zypper se -is K3b MAD MP3 libmad
Warning: Repository 'openSUSE:Leap:42.3:Update' appears to be outdated. Consider using a different mirror or server.
S | Name | Type | Version | Arch | Repository
---+----------------------------+-------------+---------------+--------+--------------------------
i+ | K3b | application | | noarch | (System Packages)
i+ | gnump3d | package | 3.0-108.3 | noarch | Hovedpakkebrønn (OSS)
i+ | gstreamer-0_10-fluendo-mp3 | package | 21-2.8 | x86_64 | Hovedpakkebrønn (NON-OSS)
i+ | gstreamer-fluendo-mp3 | package | 21-2.8 | x86_64 | Hovedpakkebrønn (NON-OSS)
i+ | k3b | package | 17.04.1-2.1 | x86_64 | Hovedpakkebrønn (OSS)
i+ | k3b-lang | package | 17.04.1-2.1 | noarch | Hovedpakkebrønn (OSS)
i+ | libmad0 | package | 0.15.1b-1.5 | x86_64 | (System Packages)
i+ | libmp3lame0 | package | 3.99.5-1016.1 | x86_64 | (System Packages)
i+ | libsnmp30 | package | 5.7.3-6.6 | x86_64 | Hovedpakkebrønn (OSS)
I’ve tried to add ‘mad’ 1:2.3-1.1 (force install, solution 2) from ‘home:Ledest:erlang:20’
zypper in mad
Problem: nothing provides erlang_beam(mad_bundle) needed by mad-1:2.3-1.1.noarch
Solution 1: do not install mad-1:2.3-1.1.noarch
Solution 2: break mad-1:2.3-1.1.noarch by ignoring some of its dependencies
i+ | mad | package | 1:2.3-1.1 | noarch | home:Ledest:erlang:20
but that doesn’t seem to help regarding the K3b missing MP3 decoder problem.
Any help to solve this will be appreciated.
Terje J. H
Am installing the new Kubic image (Kubernetes on openSUSE),
And am surprised…
Is an SMT(Server Management Tool) Server now going to be a part of openSUSE installs?
Obviously, SMT has a place in SUSE installs, but why should it appear in openSUSE?
There is no mistake, the Kubic image so far consistently displays openSUSE, not SUSE branding.
Have mixed opinions about the new window which asks for the SMT URL and includes numerous other setup options… It’s a big and significant change from what has existed through many versions of openSUSE, but it also omits numerous standard settings. On the one hand, set up now requires far fewer clicks (good) but also might deprecate settings because after clicking to proceed I’m never asked questions about all the other options ultimately ending in an Installation Summary verification before actual install.
Unless, my musings are specific to this Kubic image…
I guess I should get my hands on a regular 42.3 to see if the experience is the same…
TSU
After viewing the video from SUSECON 2017,
It seems that Kubic is based on TW, not LEAP 42.3.
It also uniquely has the weird, different installer I described which is what threw me (never saw that in TW).
So, cool.
The Kubic TW distro appears to be a stripped down TW with its own essential components (Docker, Kubernetes).
People should know if there are are any Q about Kubic, it’s a unique distro based on TW but not a normal TW.
TSU
I did find a workaround myself:
downgraded to and added the following Packman repo for Leap 42.2 packages:
k3b-2.9.90+git20170220.0453-8.15.x86_64
k3b-codecs-2.9.90+git20170220.0453-8.15.x86_64
k3b-lang-2.9.90+git20170220.0453-8.15.noarch
Terje J. H
I have been a more than satisfied user of openSUSE distros for over ten years now, and want to stick to openSUSE.
So I have downloaded Leap 42.3 Beta on May 25 and I am installing/using it on two laptops and two towers (being mainly used as servers).
No particular inconvenience so far, but for a problem I will detail in a following post.
I have however some useful suggestions for the installation process that shouldn’t be too hard to fix.
I mistakenly created a /boot partition of only 256 MB: the installation went fine till the very end (when the mask for restarting the system in some 10 seconds would appear), and then an unspecified error was reported. It would be useful that the lack of space be detected at the very beginning, not at the end (I also wonder where it did copy the boot software so far !!).
It would be very useful that the name / domain for the system be asked during installation, instead of modifying hostname in /etc at first boot or later; this may screw up some routers (when they find that two different names are being assigned to the same physical device before the lease period has expired).
At the end of the installation of the required software packages the system, before executing scripts, is very busy for about one minute or more doing something no one knows: except for the laptops where one may see the disk led blinking and deduce that some disk operation is in progress, one may mistakenly assume that the system has screwed up. It would be very useful that a message be output, saying something as “Be patient for some time, I am doing some housekeeping”.
In addition to this, there is also a minor point with laptops being Wi-Fi connected. Everything is fine if one sticks to the Network Manager. If trying the wicked service (after configuring, disabling Network Manager and rebooting), there is no way out: it does not connect.
If one goes back to the Network Manager, then everything works again perfectly at first trial (even without rebooting the system).
On both towers the installation went fine and they are then usable without I could detect a defect, if any.
One of the towers (the one I am using now) has - as reported by Hardware Info - a NVIDIA MCP 61 Card (mcpi61-86) and a Philips PHL 203 V5 monitor, using a resolution of 1600x900@60Hz (the same that the monitor itself suggests as the best one).
No problem till I remain with the distro I downloaded on May 25, with kernel 4.4.68-2.
If however I apply the software updates (which leads to kernel 4.4.71-1) then - after rebooting - everything goes fine till I complete the login; then - upon launching plasma - the screen either screws up (with a plenty of transversal lines typical of synchronization problems), or remains full black. In some cases the whole system is screwed up and does not even respond to <Alt><Ctrl><F2>, nor the power switch off button (I have to unplug it from the main).
The problem remains identical even if I try to launch from Grub the previous built that had been working fine so far (i.e., 4.4.68-2).
From what I could somehow see in the Xorg log, it seems that nouveau does no longer find a configuration file it needs for managing the NVIDIA card.
Hope this will be fixed in a future built, but would like to know when.
One more minor problem I have noticed on all my four installations. In the bottom bar it appears a loudspeaker with a red line on the right. If I click on it, a fully blank window appears, as if there were no audio system in place.
It is not so, because both audio and video work perfectly. But I do not have a direct mean to adjust volume, as it was in older distros. The only way to do this is going through YaST and audio card configuration.
Did you maybe disable PulseAudio?
That volume applet is just a frontent to PA, like pavucontrol, and doesn’t work without it.
You can install and run kmix, that’s still included and works with plain ALSA too.
And if you want to, you can disable the Plasma volume applet in the “System Tray Settings” (reachable by right-clicking on an empty space or the small up arrow in the system tray).
That’s how it always was in openSUSE.
MP3 support is disabled for legal reasons (except for the gstreamer-fluendo-mp3 plugin, but that only helps with applications using gstreamer, k3b is not one of them).
You need to install k3b from Packman (as you found out already), if you need that.
This will hopefully change in Leap 15, as most MP3 patents have already expired, and the rest will at the end of this year AFAIK.
Packman offers a repo for 42.3 already as well since a few days, better use this.
http://lists.links2linux.de/pipermail/packman/2017-June/015262.html
And 2.9.90 is outdated (and just an unstable development version), the current version is 17.04.2, that’s what’s in the Packman repo for 42.2 too since about two weeks, and in the 42.3 repo of course.
PS: I just noticed that I’m replying in an old thread here.
@bangcube:
the current one about the 42.3 development is here:
https://forums.opensuse.org/showthread.php/525288-Discussion-thread-for-42-3-Release-Candidate
Please continue there…
Thanks.
This one is closed now.