[Unstable Update] 2016-09-02 - Xorg-Stack, Plasma5, Apps, Pamac, Manjaro-Tools

Hi community,

Since we managed to put out our second final review of Manjaro Ellada, we are already working on our next release we codenamed Fringilla. With this update we try to fix the known networkmanager issues, updated some kernels, Plasma to 5.7.4 Apps to 16.08, added some Haskell packages and reworked all our settings for Manjaro-Tools 0.13.5. Additionally we switched to Xorg-Server 1.18 series and re-introduced matching packages for Catalyst drivers, so they are still working.

Archlinux upstream fixes are now from: Thu Sep 1 23:59 CEST 2016.

Please report any issues you may have with this update. Also read our troubleshoots to avoid known issues. A detailed list can be found here.

Kind regards,
Philip Müller and the Manjaro Development Team


Troubleshoots

Issues with updating MATE

Some users have mate-menu installed from AUR. Please remove this package if you use the GTK2 version of MATE before trying to update. If you have a different issue with updating, please post.

LibreOffice and GTK3

LibreOffice might be broken on gtk-based Desktop Environments. Workaround would be to force a look to Libreoffice by editing /etc/profile.d/libreoffice*sh. We recommend to uncomment SAL_USE_VCLPLUGIN=gtk. Our KDE edition isn’t affected by this issue.

GTK3

With this we updated Gnome and GTK to 3.20. This will break most of the themes, which will be fixed if and when their developers decide to update them. Some GTK 3.20-compliant themes are ready now - see further down this post.

The new default Manjaro GTK theme, which is GTK 3.20 compatible, is Vertex-Maia

You can install it with:

sudo pacman -Sy vertex-maia-themes vertex-maia-icon-theme xcursor-maia

KDE users should default to Maia theme:

sudo pacman -Sy maia-icon-theme gtk-theme-maia plasma5-themes-maia xcursor-maia

QT apps style with GTK - only needed for non-KDE desktop environments!

With QT 5.7 you need to install qt5-styleplugins and qt5ct and configure your system to have an unified look again.

ufw

If you have issues with ufw not working anymore, you have to copy your custom rules to a different folder. Do it like this:

sudo cp -v /usr/lib/ufw/user.rules.pacsave /etc/ufw/user.rules
sudo cp -v /usr/lib/ufw/user6.rules.pacsave /etc/ufw/user6.rules

steam

Steam might not work due incompatiblity of libgpg. You my try followed command to “fix” it:

find ~/.steam/root/ \( -name "libgcc_s.so*" -o -name "libstdc++.so*" -o -name "libxcb.so*" -o -name "libgpg-error.so*" \) -print -delete
find ~/.local/share/Steam/ \( -name "libgcc_s.so*" -o -name "libstdc++.so*" -o -name "libxcb.so*" -o -name "libgpg-error.so*" \) -print -delete

Reference: Archlinux wiki


Did you experience any issue with this update?

  • No issues, everything went smoothly
  • Yes there was an issue. I was able to resolve it myself. (Please post your solution)
  • Yes I am currently experiencing an issue due to the update. (Please post about it)

0 voters


Current supported kernels

  • Linux310 3.10.103
  • Linux312 3.12.62
  • Linux314 3.14.77
  • Linux316 3.16.37
  • Linux318 3.18.40
  • Linux41 4.1.31
  • Linux44 4.4.19
  • Linux46 4.6.7 [EOL]
  • Linux47 4.7.2
  • Linux-RT-LTS 4.4.19_rt27
  • Linux-RT 4.6.7_rt11
1 Like

I’m running xorg 1.18 without issues here! :grinning:

1 Like

wow finally, but I wonder how is catalyst still working if Xorg != 1.17.

2 Likes

[quote=“philm, post:1, topic:8532”]
Additionally we switched to Xorg-Server 1.18 series and re-introduced matching packages for Catalyst drivers, so they are still working.
[/quote]let me be original by commending how?

Well I’m a little confused now… How is catalyst going to replace my video-intel driver?

looking for conflicting packages...
warning: removing 'xf86-video-intel' from target list because it conflicts with 'catalyst-video'
warning: removing 'xorg-server-common' from target list because it conflicts with 'catalyst-server'
warning: removing 'xorg-server-devel' from target list because it conflicts with 'catalyst-server'
warning: removing 'xorg-server-xvfb' from target list because it conflicts with 'catalyst-server'
warning: removing 'xorg-server' from target list because it conflicts with 'catalyst-server'
warning: removing 'xf86-input-synaptics' from target list because it conflicts with 'catalyst-input'
warning: removing 'xf86-input-acecad' from target list because it conflicts with 'catalyst-input'
warning: removing 'xf86-input-elographics' from target list because it conflicts with 'catalyst-input'
warning: removing 'xf86-input-evdev' from target list because it conflicts with 'catalyst-input'
warning: removing 'xf86-input-joystick' from target list because it conflicts with 'catalyst-input'
warning: removing 'xf86-input-keyboard' from target list because it conflicts with 'catalyst-input'
warning: removing 'xf86-input-mouse' from target list because it conflicts with 'catalyst-input'
warning: removing 'xf86-input-void' from target list because it conflicts with 'catalyst-input'
warning: removing 'xf86-input-wacom' from target list because it conflicts with 'catalyst-input'
:: catalyst-video and xf86-video-intel are in conflict. Remove xf86-video-intel? [y/N]

Really??

3 Likes

Maybe Catalyst is now using its own xorg version included in the package catalyst-server? And all other drivers will use the updated xorg-server. Goodbye catalyst, we’re going 1.18 :smile:

4 Likes

Thanks. Xorg just make my wallpaper default :slight_smile: Every thinkg is fine Xorg :slight_smile:
X.Org X Server 1.18.4
Release Date: 2016-07-19
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.5.4-1-ARCH x86_64
Current Operating System: Linux onem-pc 4.7.2-1-MANJARO #1 SMP PREEMPT Sun Aug 21 15:04:37 UTC 2016 x86_64

I’m getting this message. I assume it’s safe to proceed?

yes we all got this message

2 Likes

But this surely will ■■■■ up many systems on testing and stable.

@philm
What about “replace” the current catalyst with video-ati and provide the new catalyst system as “new” package, so that no system tries to upgrade to it? sure this will make some users angry or something but this way you make sure that no intel user gets the upgrade to catalyst.

3 Likes

no issue on plasma with nouveau drivers

This is really weird on my machine. I have

Graphics:  Card: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display
           Display Server: X.Org 1.17.4 driver: intel Resolution: 1366x768@60.06hz
           GLX Renderer: Mesa DRI Intel Bay Trail GLX Version: 3.0 Mesa 12.0.1

Now while on my main partition pacman wants to replace video-intel and a long list of others with the new catalyst packages, on my other partition on the same machine I get this, including an upgrade of video-intel

looking for conflicting packages...
:: xorg-server and xf86-input-aiptek are in conflict (X-ABI-XINPUT_VERSION). Remove xf86-input-aiptek? [y/N] y

Packages (52) chromium-53.0.2785.89-1  cups-filters-1.11.2-1  dbus-1.10.10-3  downgrade-5.3.0-2  gnome-online-accounts-3.20.3+5+gc098f5d-1
              gsettings-desktop-schemas-3.21.4-1  hplip-3.16.8-2  imagemagick-6.9.5.8-1  lib32-elfutils-0.167-1  lib32-libdbus-1.10.10-3
              lib32-sqlite-3.14.1-1  libdbus-1.10.8-1 [removal]  libinput-1.4.2-1  libmediainfo-0.7.88-1  libnautilus-extension-3.20.3-1
              libnm-glib-1.4.1dev+15+g0d23ffd-0  libwbclient-4.4.5-2  libxfont-1.5.2-1  libxml2-2.9.4+4+g3169602-1  manjaro-base-skel-20160827-1
              mediainfo-0.7.88-1  mhwd-db-0.5.8-3  mhwd-nvidia-1:370.23-1  nautilus-3.20.3-1  network-manager-applet-1.4.0-1
              networkmanager-1.4.1dev+15+g0d23ffd-0  nm-connection-editor-1.4.0-1  orc-0.4.26-1  pamac-4.1.4-1  python-requests-2.11.1-1
              python2-lxml-3.6.4-1  python2-ply-3.9-1  python2-requests-2.11.1-1  python2-setuptools-1:26.1.1-1  smbclient-4.4.5-2  sudo-1.8.17.p1-1.1
              unrar-1:5.4.5-1  webkit2gtk-2.12.4-1  xf86-input-acecad-1.5.0-9  xf86-input-aiptek-1.4.1-8 [removal]  xf86-input-elographics-1.4.1-6
              xf86-input-evdev-2.10.3-1  xf86-input-joystick-1.6.2-6  xf86-input-keyboard-1.8.1-2  xf86-input-libinput-0.19.0-1
              xf86-input-mouse-1.9.1-2  xf86-input-synaptics-1.8.99.1-1  xf86-input-void-1.4.1-2  xf86-input-wacom-0.33.0-1
              xf86-video-intel-1:2.99.917+697+g12c14de-1  xorg-server-1.18.4-1  xorg-server-common-1.18.4-1

Why’s that?

1 Like

I don’t know why it wants to install catalyst-video on one partition of my machine and not on the other.
Also I don’t understand how catalyst

Provides        : xf86-video-fbdev=0.4.4-4
                  xf86-video-intel=1_2.99.917+697+g12c14de-0.1
                  xf86-video-vesa=2.3.4-1  xf86-video-intel-uxa
                  xf86-video-intel-sna

I always thought
AMD > Catalyst
Intel > Intel
no?

Aaaah. Now I finally got it :laughing:
Because I have been building kernel extramodules I have catalyst-utils installed. They now depend on catalyst-video.
Solved by removing catalyst-utils
Still I don’t understand the ‘provides’ array of catalyst-video, @philm I doubt that my GPU would work with catalyst, right?

2 Likes

Yeah, I also just uninstalled catalyst-utils last night or it won’t install because of the /usr/lib/libgl and LICENCE file exists in the file system error. I was really confused about why I got that package in my system until I read your post. :smile:

Ok, some conclusions on the new style how Catalyst works now:

  • Catalyst-Utils needs now three new packages: catalyst-video, catalyst-input and catalyst-server.
  • Catalyst-Video provides some needed drivers like Intel and Vesa, since we have some hybrid systems too
  • Catalyst-Input provides the needed input drivers
  • Catalyst-Server provides the compatible Xorg-Server

Without these packages it would be not possible to still provide Catalyst at all. So it is logical to remove conflicting packages on these AMD systems. Ping me if some issues are still there and not working as expected. It can be tested with a new dev-build.

2 Likes

this

also it doesnt boot
https://scontent.fath1-2.fna.fbcdn.net/v/t34.0-12/14218457_10209941985244248_2110990405_n.jpg?oh=9b0d9e95c10b656cae3d6219562acd9a&oe=57CCE9F5
https://scontent.fath1-2.fna.fbcdn.net/v/t34.0-12/14256492_10209941991484404_590827670_n.jpg?oh=608deb1cb408931718037126b354188b&oe=57CD0CE2

Cool, works good here.
Could you add lib32-libva between conflicts of lib32-catalyst-utils then?
It’s true I had myself manually installed the former, though it was quite bad having to figure out alone which package was keeping usr/lib32/dri/ populated.

Thanks.

Ok, never mind: it seems I can’t get back to video-ati anymore.
When I install it from mhwd, something is complaining there’s no “/usr/lib/xorg/modules/extensions/libglx.xorg

EDIT: ok, it seems this something is x.org. I can’t understand what’s even the point though.
EDIT2: ok ok ok, I think I understood the problem now: you aren’t switched back to newer x.org once you reinstall video-ati
EDIT3: Once I installed xorg-server and xorg-server-common indeed everything was fine.
EDIT4: except trackpad because I still lack any xf86-input package, but hey at least now I have display

Forum kindly sponsored by Bytemark