Manjaro KDE 17.0 (Beta3)

development
release

#1

Manjaro Fringilla was a great release, however we are already working on our next release, called “Gellivara”.

With this we also change some things in our release cycle:

In the past we have used numbered versions. Currently we are using versions based on the release target month which, on a rolling release, might point to a monthly based versioning of our install media. However, they only reflect the status of our tools and installer. Also this creates the impression of some of our community releases being newer than the core releases, when in fact they are using the same base and were simply published on a later date.

Depending on the development we might release three major sets of install media with new features. If we find some issues in the original install media, we may update them for fixing bugs, which will then be a point release of the same series. Also we will discuss if we change the code name of the releases this year, or keep one for the whole year.

So what will be the features of the new release series:

  • We updated the stock kernel to linux49 4.9 LTS - Done with Alpha1
  • We will update the Xorg-Stack to v1.19 series - Done with Beta1
  • We will enhance and improve Luks and LVM support in CAL - Partly done with CAL v3.0
  • We will enhance and improve our Manjaro Tools & Profiles - Ongoing within v0.14 branch
  • We will enhance and improve our MHWD and MSM - Almost completed for Xorg 1.19
  • We will update our themes - Done with Beta3

Changes since Beta2 release:

  • Plasma 5.9.1
  • KDE Apps 16.12.2
  • VLC Nightly added
  • Manjaro Hello 0.4.10
  • Fixed some crashing issues with Xorg-Server
  • [CAL] partition: use always double click to activate a partition tree view item
  • [CAL] netinstall: moved module to a tree based UI
  • [CAL] welcome: Add fallback check for internet connection
  • [CAL] partition: Don’t hardcode /dev/sd* as device path.
  • [CAL] packages: Make try_{install,remove} more robust.

Changes since Beta1 release:

  • Plasma 5.9.0
  • Mesa 13.0.4
  • Manjaro Settings-Manager 0.5.0
  • Network Manager 1.6.0
  • Octopi 0.8.7
  • QT 5.8.0
  • [CAL] fix for an issue in the users module, which could break login if the chosen password had non-Latin1 characters
  • [CAL] proper exception handling in the networkcfg module
  • [CAL] improved autologin configuration handling for sddm.

Changes since Alpha releases:

  • fixes for EFI installation
  • gcc updated to v6.3.1
  • xorg-stack v1.19
  • KDE Apps v16.12.1
  • KDE Framework v5.30
  • Calamares 3.0 includes countless fixes and improvements to the core application and to the modules, as well as an all new PythonQt-based module interface. The PythonQt interface is optional, and allows module developers to create view modules in Python with Qt.

For those, who already want to test our latest install media, you can find them here.


Another black screen
#2

Thanks Phil for yet another release. Unfortunately KDE system-settings keeps crashing, like it also did in previous versions.
This is what I saw about it in the log file:

12-02-17 14:04	plasmashell	KActivitiesStats( 0x4d026c0 ) ResultModelPrivate::onResultScoreUpdated  result added: "applications:systemsettings.desktop" score: 1 last: 1486904682 first: 1486904575
12-02-17 14:04	systemsettings5	org.kde.kcoreaddons: Error loading plugin "kcm_lookandfeel" "The shared library was not found." 
Plugin search paths are ("/usr/lib/qt/plugins", "/usr/bin") 
The environment variable QT_PLUGIN_PATH might be not correctly set
12-02-17 14:04	systemsettings5	Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion
12-02-17 14:04	systemsettings5	invalid theme "Breeze_Snow"
12-02-17 14:04	systemsettings5	invalid theme "default"
12-02-17 14:04	systemsettings5	invalid theme "breeze_cursors"
12-02-17 14:04	systemsettings5	couldn't include  "widgets/default"
12-02-17 14:04	systemsettings5	couldn't include  "widgets/buttons"
12-02-17 14:04	systemsettings5	couldn't include  "widgets/menu"
12-02-17 14:04	systemsettings5	couldn't include  "widgets/entry"
12-02-17 14:04	systemsettings5	couldn't include  "widgets/notebook"
12-02-17 14:04	systemsettings5	couldn't include  "widgets/range"
12-02-17 14:04	systemsettings5	couldn't include  "widgets/scrollbar"
12-02-17 14:04	systemsettings5	couldn't include  "widgets/toolbar"
12-02-17 14:04	systemsettings5	couldn't include  "widgets/progressbar"
12-02-17 14:04	systemsettings5	couldn't include  "widgets/misc"
12-02-17 14:04	systemsettings5	couldn't include  "widgets/styles"
12-02-17 14:04	systemsettings5	unknown field "gtk-color-scheme"
12-02-17 14:04	systemsettings5	could not find icon "start-here"
12-02-17 14:04	systemsettings5	Plugin changed to:  "org.kde.breeze"
12-02-17 14:04	systemsettings5	Calling KPluginInfo::property("X-KDE-PluginInfo-Name") is deprecated, use KPluginInfo::pluginName() in "/usr/lib/qt/plugins/org.kde.kdecoration2/breezedecoration.so" instead.
12-02-17 14:04	systemsettings5	Factory:  true
12-02-17 14:04	systemsettings5	Setting  active : false
12-02-17 14:04	systemsettings5	Setting  providesContextHelp : true
12-02-17 14:04	systemsettings5	Setting  active : false
12-02-17 14:04	systemsettings5	Setting  providesContextHelp : true
12-02-17 14:04	systemsettings5	Setting  active : false
12-02-17 14:04	systemsettings5	Setting  providesContextHelp : true
12-02-17 14:04	systemsettings5	Setting  active : false
12-02-17 14:04	systemsettings5	Setting  providesContextHelp : true
12-02-17 14:04	systemsettings5	file:///usr/share/kwin/kcm_kwindecoration/Buttons.qml:42:16: Unable to assign [undefined] to QColor
12-02-17 14:04	systemsettings5	file:///usr/share/kwin/kcm_kwindecoration/Buttons.qml:54:24: Unable to assign [undefined] to QColor
12-02-17 14:04	systemsettings5	file:///usr/share/kwin/kcm_kwindecoration/Buttons.qml:149: ReferenceError: iconLabel is not defined
12-02-17 14:04	systemsettings5	file:///usr/share/kwin/kcm_kwindecoration/Buttons.qml:197:24: Unable to assign [undefined] to QColor
12-02-17 14:04	systemsettings5	kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/kwin-decoration.desktop, tried ("/home/jan/.local/share", "/usr/share", "/usr/local/share")
12-02-17 14:04	systemsettings5	Plugin changed to:  "org.kde.kwin.aurorae"
12-02-17 14:04	systemsettings5	Calling KPluginInfo::property("X-KDE-PluginInfo-Name") is deprecated, use KPluginInfo::pluginName() in "/usr/lib/qt/plugins/org.kde.kdecoration2/breezedecoration.so" instead.
12-02-17 14:04	systemsettings5	Factory:  true
12-02-17 14:04	systemsettings5	Module 'org.kde.kwin.decoration' does not contain a module identifier directive - it cannot be protected from external registrations.
12-02-17 14:04	systemsettings5	kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/kwin-decoration.desktop, tried ("/home/jan/.local/share", "/usr/share", "/usr/local/share")
12-02-17 14:04	systemsettings5	Setting  width : -8
12-02-17 14:04	systemsettings5	Setting  height : -32
12-02-17 14:04	systemsettings5	Setting  width : -8
12-02-17 14:04	systemsettings5	Setting  height : -32
12-02-17 14:04	systemsettings5	Setting  width : 352
12-02-17 14:04	systemsettings5	Setting  height : 193
12-02-17 14:04	systemsettings5	Setting  width : 352
12-02-17 14:04	systemsettings5	Setting  height : 193
12-02-17 14:04	systemsettings5	Setting  caption : "Plastik"
12-02-17 14:04	systemsettings5	Setting  width : 342
12-02-17 14:04	systemsettings5	Setting  width : 302
12-02-17 14:04	systemsettings5	Setting  height : 153
12-02-17 14:04	systemsettings5	Setting  height : 143
12-02-17 14:04	systemsettings5	Setting  caption : "Plastik"
12-02-17 14:04	systemsettings5	Setting  active : false
12-02-17 14:04	systemsettings5	Setting  width : 312
12-02-17 14:04	systemsettings5	Setting  width : 302
12-02-17 14:04	systemsettings5	Setting  height : 183
12-02-17 14:04	systemsettings5	Setting  height : 143
12-02-17 14:04	systemsettings5	Plugin changed to:  "org.kde.breeze"
12-02-17 14:04	systemsettings5	Calling KPluginInfo::property("X-KDE-PluginInfo-Name") is deprecated, use KPluginInfo::pluginName() in "/usr/lib/qt/plugins/org.kde.kdecoration2/breezedecoration.so" instead.
12-02-17 14:04	systemsettings5	Factory:  true
12-02-17 14:04	systemsettings5	Setting  width : -8
12-02-17 14:04	systemsettings5	Setting  height : -33
12-02-17 14:04	systemsettings5	Setting  width : -28
12-02-17 14:04	systemsettings5	Setting  height : -53
12-02-17 14:04	systemsettings5	Setting  width : -8
12-02-17 14:04	systemsettings5	Setting  height : -33
12-02-17 14:04	systemsettings5	Setting  width : -28
12-02-17 14:04	systemsettings5	Setting  height : -53
12-02-17 14:04	systemsettings5	Setting  width : 332
12-02-17 14:04	systemsettings5	Setting  height : 172
12-02-17 14:04	systemsettings5	Setting  width : 332
12-02-17 14:04	systemsettings5	Setting  height : 172
12-02-17 14:04	systemsettings5	Setting  caption : "Breeze"
12-02-17 14:04	systemsettings5	Setting  width : 329
12-02-17 14:04	systemsettings5	Setting  width : 302
12-02-17 14:04	systemsettings5	Setting  height : 139
12-02-17 14:04	systemsettings5	Setting  height : 142
12-02-17 14:04	systemsettings5	Setting  caption : "Breeze"
12-02-17 14:04	systemsettings5	Setting  active : false
12-02-17 14:04	systemsettings5	Setting  width : 299
12-02-17 14:04	systemsettings5	Setting  width : 302
12-02-17 14:04	systemsettings5	Setting  height : 169
12-02-17 14:04	systemsettings5	Setting  height : 142
12-02-17 14:04	systemsettings5	Setting  active : false
12-02-17 14:04	systemsettings5	Setting  providesContextHelp : true
12-02-17 14:04	systemsettings5	Setting  active : false
12-02-17 14:04	systemsettings5	Setting  providesContextHelp : true
12-02-17 14:04	systemsettings5	Setting  active : false
12-02-17 14:04	systemsettings5	Setting  providesContextHelp : true
12-02-17 14:04	systemsettings5	Setting  active : false
12-02-17 14:04	systemsettings5	Setting  providesContextHelp : true
12-02-17 14:04	systemsettings5	Setting  active : false
12-02-17 14:04	systemsettings5	Setting  providesContextHelp : true
12-02-17 14:04	systemsettings5	Setting  active : false
12-02-17 14:04	systemsettings5	Setting  providesContextHelp : true
12-02-17 14:05	systemsettings5	Setting  active : false
12-02-17 14:05	systemsettings5	Setting  providesContextHelp : true
12-02-17 14:05	systemsettings5	Setting  active : false
12-02-17 14:05	systemsettings5	Setting  providesContextHelp : true
12-02-17 14:05	systemsettings5	Setting  active : false
12-02-17 14:05	systemsettings5	Setting  providesContextHelp : true
12-02-17 14:05	systemsettings5	Setting  active : false
12-02-17 14:05	systemsettings5	Setting  providesContextHelp : true
12-02-17 14:05	systemsettings5	Setting  active : false
12-02-17 14:05	systemsettings5	Setting  providesContextHelp : true
12-02-17 14:05	systemsettings5	Setting  active : false
12-02-17 14:05	systemsettings5	Setting  providesContextHelp : true
12-02-17 14:05	kernel	systemsettings5[5668]: segfault at 121ffffffff ip 00007fd59065f8ae sp 00007ffec567b6b0 error 4 in libQt5Core.so.5.8.0[7fd5903a4000+4cc000]
12-02-17 14:05	systemd	Started Process Core Dump (PID 5694/UID 0).

I know it is KDE stuff so it should be fixed upstream.
I use the beta3 in a virtualbox VM.


#3

@DeMus: please boot up the ISO on real hardware. If the issue is only with VirtualBox you may try the VESA driver by adding xdriver=vesa during live-session boot-up to check if it is a virtualbox graphic driver issue.


#4

When booting with the free drivers does also crash the system-settings.
Booting with non-free drivers does the same.
Only when I used the option xdriver=vesa the program does not crash, but the screen looks terrible (4:3) instead of 16:9 with a maximum of 1024x768 dots.
Tried it on my laptop, which is a different computer than the one with the VM.

Closing the lid and opening it again, then pushing the on-button gave a half a screen filled with dots and very short lines. Computer did not recover from it. Had to use the power-button for 5 seconds to switch off.


#5

This file name I found was manjaro-kde-17.0-beta3-testing-x86_64.iso
I know the beta1 I downloaded was named unstable.
Is it normal to progress betas from unstable to testing on the way to releases on stable?

Edit: On one machine the panel on the live image is pretty much unreadable. It was the same T61 that was a little glitchy before I broke down and switched from nouveau to nvidia 340xx,

Edit: Successful install onto an HP Elitebook. It seemed as if the Oxygen cursor themes are removed. The (probably upstream) bug of System Settings > Desktop Behavior > Turn off Screen Locking > Return to All Settings that crashes System Settings remains.


#6

Hello, someone has this wifi adapter and can test if it works with any version of this distro KDE? Does not work with Beta 1, Beta 2, Beta 3 or the previous stable. 16.10. The drivers are loaded in /lib/firmware but it is as if you do not read or communicate them.

This is the adapter.

03: 00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
Subsystem: Intel Corporation Dual Band Wireless-AC 7265
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

[sergi@sergi-kde ~]$ dmesg | grep firmware
[ 8.119607] [drm] GuC firmware load skipped
[ 9.980793] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7265D-26.ucode failed with error -2
[ 9.980856] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7265D-25.ucode failed with error -2
[ 9.980905] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7265D-24.ucode failed with error -2
[ 9.980954] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7265D-23.ucode failed with error -2
[ 10.637184] iwlwifi 0000:03:00.0: loaded firmware version 22.361476.0 op_mode iwlmvm
[ 43.141704] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 43.455844] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
[ 697.240760] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 697.558906] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
[sergi@sergi-kde ~]$

[sergi@sergi-kde ~]$ dmesg | grep iwlwifi
[ 9.980793] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7265D-26.ucode failed with error -2
[ 9.980856] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7265D-25.ucode failed with error -2
[ 9.980905] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7265D-24.ucode failed with error -2
[ 9.980954] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7265D-23.ucode failed with error -2
[ 10.637184] iwlwifi 0000:03:00.0: loaded firmware version 22.361476.0 op_mode iwlmvm
[ 10.723854] iwlwifi 0000:03:00.0: Detected Intel® Dual Band Wireless AC 7265, REV=0x210
[ 10.725949] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[ 10.726263] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[ 10.948971] iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0
[ 18.298198] iwlwifi 0000:03:00.0: RF_KILL bit toggled to disable radio.
[ 19.852495] iwlwifi 0000:03:00.0: RF_KILL bit toggled to enable radio.
[ 696.703920] iwlwifi 0000:03:00.0: RF_KILL bit toggled to disable radio.
[ 702.850517] iwlwifi 0000:03:00.0: RF_KILL bit toggled to enable radio.

http://www.subirimagenes.com/imagen-screenshot2017020514-9682695.html

http://www.subirimagenes.com/imagen-screenshot2017020514-9682696.html

I would like to know if someone has that adapter working since I can not find any way possible.

Thank you very much sorry for my english.


#7

The beta ISOs are built using a minimal package profile to keep the size down.

If you install using manjaro-architect you get the choice of selecting the full or minimal package profile.

For these beta installs I install oxygen and oxygen-icons post install.


#8

Note from networkmanager update in KDE beta 3 :

(62/98) upgrading networkmanager [######################] 100%
warning: directory permissions differ on /etc/NetworkManager/system-connections/
filesystem: 755 package: 700

#9

#10

I used the testing branch for this build. The previous released had unstable. I hope to have a RC release soon, based on our stable branch. I hope this one is almost ready so far …


#11

Downloading now. I will try it tonight.


#12

I have a btrfs partition which contains my Arch /home in a subvolume. If I install 17.0-beta3 to that partition without formatting, will it keep my @arch-home subvolume?


#13

Yes, it will keep the subvolume if you tell Calamares to keep it in manual partitioning. Calamares will fail if there are already subvolumes @ and @home, otherwise it will not touch other subvolumes.


#14

System Settings crashing bugs were resolved or me with Plasma 5.9.2 update, now in both unstable and testing.

An update after installing this ISO (installs Plasma 5.9.1) should fix these issues.


#15

OK, been busy finally got some time to test this.

Have an installation testing VB VM, installed on an old USB drive, currently with 10 partitions that I use to test manjaro-archtitect and Calmares.

I want to re-install Manjaro KDE into sda10, so I chose to replace an existing partition, and here are the resulting Calmares generated actions.

The sda10 is partition being deleted and recreated? Why not just reformat it with mkfs, instead of deleting and recreating a partition of exactly the same size? Some users may have gone to a great deal of trouble to create their partitions via GParted, ensuring correct alignment and spacing between partitions, and this will be undone.

If Manjaro devs are adamant to retain this functionality then it would be more informative to the user to change the terminology used in the text from Replace Partition to Re-Create Partition.

I didn’t like that option so I went back a few steps to the Partition tab and selected Manual Editing of partions instead.

Selected sda10, set / mount point, chose to Format it, clicked Ok.

Click Edit again, and the Content radio button is back to Keep.

This behaviour was reported back in September 2016, but still occurs. The problem is that it looks like the selection is not persisting, so users repeat the same action by re-selecting Format. I did this three times, and Calmares generates 3 partition format actions.

This is not right, users should make their selection once, have it persist, and thus one format action results (if the final choice is to actually format).

What happens if format is accidently chosen? Currently the format action will always be generated and cannot be undone. Users would have to go back a couple of steps and start their manual partitioning again. Again, not ideal.

Testing the actually installation now… I like the new slide show feature, nice.


#16

Installation completed, system boots successfully, kind of.

My current efi partition is sda1, but my customized grub.cfg (ie defines the grub menu) is on sda2. Testing 17.0 XFCE Beta 2 Calmares install previously on sda8 the bootloader in sda1 was replaced, and grub.cfb on sda8 became the default.

In order to remedy this I had to fix manually.

It happened again, this time grub.cfg on sda10 is now the machine default. Update-grub worked though, and all system partitions were found and correct in grub.cfg.

Is there no way to install a system using Calmares without the bootloader in /boot/efi/EFI/boot getting clobbered and changing the default grub.cfg boot partition?

Not mounting an efi partition generated an error, so not an option.

So, during the installation process in Calmares I mounted sda1 to /boot/efi and select to Keep Content, not Format the partition.

This then generates the following Calmares action

Set up fat32 partition on /dev/sda1 with mount point /boot/efi

Will this action always make this new install the default boot partition?

In manjaro-architect setting a new install to become the default bootloader is not the default, it is an action that has to be explicitly chosen. There should be a setting (ie checkbox) somewhere in Calmares with the same function. Fine to leave this existing functionality as default, but there needs to be a way to disable it.

Here you can see that the bootloader, bootx64.efi, was replaced during Calmares install. I kept a copy of the original sda2 grub bootloader file handy in case this happened again.

$ pwd
/boot/efi/EFI/boot                                                                             
[manjaro@gellivara-kbeta3 boot]$ ll                                                            
total 368                                                                                          
drwxr-xr-x 2 root root   4096 Feb 13 15:34 .                                                       
drwxr-xr-x 5 root root   4096 Feb 13 00:08 ..                                                      
-rwxr-xr-x 1 root root 122368 Feb 17  2017 bootx64.efi                                               
-rwxr-xr-x 1 root root 122368 Feb 13 15:34 grubx64.efi.sda2   

I kept a copy of my orginal sda2 grub bootloader efi file just in case it happened again.

Calmares is a fantastic installer if you know all its little quirks, but for new users some of these quirks can be quite confusing, and in some cases lead to unexpected installation results.

Having said all that I think the Manjaro devs are doing a fantastic job, and all up Calmares has enormous potential.

EDIT : Same hibernation device resume UUID error on boot, in the Beta 2 thread multiple users reported it OOTB also.

ERROR: resume: no device specified for hibernation

From the Beta 2 thread…


#17

I can’t restore the grub bootloader of a previous installed manjaro with this beta 3 version, as it’s described in the WIKI. I can start (within console) sudo mhwd-chroot, but after this the grub-install /dev/sda fails with the error message, the directory of efi configuration isn’t found.

And the boot menue of ISO doesn’t allow to change (keyboard) language and screen resolution. There are only four entries (start free ISO, start nonfree ISO and two UEFI related entries). But there is no start menue to change the start parameters.


#18

This command saved my butt couple of times. Give it a try.

sudo grub-mkconfig -o /boot/grub/grub.cfg


#19

That’s been my impression as well. (I don’t use Calmares that often, because I haven’t had to reinstall).

I always use the manual partitioning mode, and i expect it to do exactly as I say.
I think I first ran into this because Calmares didn’t offer the choice of a separate partition for /home (which I believe should be a standard). Maybe that’s fixed now.


#20

Same, my exposure to Calmares has been through testing these Beta ISO releases. Its been interesting contrasting Calmares with the new manjaro-architect cli installer.

Same, even more so after experimenting with the automatic partitioning modes.

It is.