[Unstable Update] 2018-11-16 - Kernels, Systemd, Gnome, Deepin, Palemoon

unstable
update

#1

Hi community,

Welcome to another unstable update. So what do we have with this one?

  • We updated most of our kernels
  • Fixes added to Deepin and Gnome packages
  • Palemoon got an update
  • Systemd got some fixes for resume issues
  • A lot of rebuilds in regard of BUILDINFO

We hope with all these changes Manjaro to be more efficient for you all.


The Iconic Spitfire: Now Quad-Core!

jpg%3Alarge

Visit StationX now!


Manjaro v18.0.1 Preview2 released!

If you are curious about the latest Manjaro-Illyria 18.0.1 release, you now have the opportunity to download XFCE Edition with the latest 4.13 packages, aswell as our most recent styling efforts. Our KDE fans may try our KDE Edition with the latest KDE v5.14 instead. And our GNOME fans may try our Gnome Edition with the latest GNOME v3.30.


Current supported Kernels

  • linux316 3.16.59
  • linux318 3.18.125 [EOL]
  • linux44 4.4.163
  • linux49 4.9.137
  • linux414 4.14.81
  • linux417 4.17.19 [EOL]
  • linux418 4.18.19
  • linux419 4.19.2
  • linux414-rt 4.14.78_rt47
  • linux416-rt 4.16.18_rt11
  • linux418-rt 4.18.16_rt9

Sync Package Updates (Fri Nov 16 07:35:45 CET 2018)

A detailed list of all package changes can be found here.

  • No issue, 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

Check if your mirror has already synced:


#2

Just upgraded and installed systemsetting5.

Output:
QCoreApplication::arguments: Please instantiate the QApplication object first


#3

In which context?


I updated mostly Haskell, Mesa, Systemd, Nvidia Drivers and some python updates. Stefano added some more Budgie Wallpapers.


#4

I have upgraded all packages then I installed KDE settings, am not running KDE so a package migth be missing, that systemsettings5 is not pulling as it was working fine last time I install it.

I also installed KDElive and openshot they are crashing when adding a video.


#5

AANNNDDD after another reboot and removing /etc/modprobe.d/mhwd-gpu.conf (to rely on the manual blacklisting for PRIME) it works again.

I don’t know. :woman_shrugging:


NVIDIA driver appears to be broken or have introduced a bug with PRIME.

Weirdly LightDM starts fine, but X crashes on login.

-- Subject: Unit lightdm.service has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit lightdm.service has finished starting up.
-- 
-- The start-up result is done.
Nov 16 10:47:46 box acpid[1221]: client 6386[0:0] has disconnected
Nov 16 10:47:46 box acpid[1221]: client connected from 6445[0:0]
Nov 16 10:47:46 box acpid[1221]: 1 client rule loaded
Nov 16 10:47:47 box acpid[1221]: client connected from 6445[0:0]
Nov 16 10:47:47 box acpid[1221]: 1 client rule loaded
Nov 16 10:47:47 box systemd-coredump[6416]: Process 6386 (Xorg) of user 0 dumped core.
                                            
                                            Stack trace of thread 6386:
                                            #0  0x00007f24e498d32d _Unwind_IteratePhdrCallback (libgcc_s.so.1)
                                            #1  0x00007f24e75f4fdf dl_iterate_phdr (libc.so.6)
                                            #2  0x00007f24e498e476 _Unwind_Find_FDE (libgcc_s.so.1)
                                            #3  0x00007f24e498a9d4 uw_frame_state_for (libgcc_s.so.1)
                                            #4  0x00007f24e498bbd0 uw_init_context_1 (libgcc_s.so.1)
                                            #5  0x00007f24e498ca2c _Unwind_Backtrace (libgcc_s.so.1)
                                            #6  0x00007f24e75c7cc6 __backtrace (libc.so.6)
                                            #7  0x000056246a6f91fd xorg_backtrace (Xorg)
                                            #8  0x000056246a6f9339 n/a (Xorg)
                                            #9  0x00007f24e74f5e00 __restore_rt (libc.so.6)
                                            #10 0x00007f24e76dbd56 _dl_fixup (ld-linux-x86-64.so.2)
                                            #11 0x00007f24e76e26ee _dl_runtime_resolve_xsave (ld-linux-x86-64.so.2)
                                            #12 0x00007f24e0fef24c n/a (libglamoregl.so)
                                            #13 0x000056246a77544e n/a (Xorg)
                                            #14 0x000056246a745aa5 n/a (Xorg)
                                            #15 0x000056246a78a2df RRCrtcSet (Xorg)
                                            #16 0x000056246a78ab21 ProcRRSetCrtcConfig (Xorg)
                                            #17 0x00007f24e1641e4d n/a (nvidia_drv.so)
-- Subject: Process 6386 (Xorg) dumped core
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
-- 
-- Process 6386 (Xorg) crashed and dumped core.
-- 
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.
Nov 16 10:47:47 box audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@27-6414-0 comm="systemd" exe="/usr/lib/systemd/systemd">
Nov 16 10:47:48 box audit[6445]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 pid=6445 comm="Xorg" exe="/usr/lib/Xorg" sig=11 res=1
Nov 16 10:47:48 box kernel: [drm:nv_drm_fence_context_create_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to allocate fence signaling event
Nov 16 10:47:48 box kernel: [drm:nv_drm_fence_context_create_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to allocate fence signaling event
Nov 16 10:47:48 box kernel: BUG: scheduling while atomic: Xorg/6445/0x00000003
Nov 16 10:47:48 box kernel: Modules linked in: overlay fuse tun bnep cachefiles fscache xfs iTCO_wdt iTCO_vendor_support gpio_ich msi_wmi mxm_wmi uinput sparse_keymap i>
Nov 16 10:47:48 box kernel:  icp(POE) lpc_ich memstick
Nov 16 10:47:48 box kernel: kauditd_printk_skb: 4 callbacks suppressed
Nov 16 10:47:48 box kernel:  rfkill
Nov 16 10:47:48 box kernel: audit: type=1701 audit(1542365268.311:297): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=6445 comm="Xorg" exe="/usr/lib/Xorg" sig=11 res=1
Nov 16 10:47:48 box kernel:  mdio mei soundcore fscrypto int3403_thermal nvidia_drm(OE) battery ac nvidia_modeset(POE) wmi int3402_thermal int340x_thermal_zone int3400_>
Nov 16 10:47:48 box kernel: Preemption disabled at:
Nov 16 10:47:48 box kernel: [<0000000000000000>]           (null)
Nov 16 10:47:48 box kernel: CPU: 1 PID: 6445 Comm: Xorg Tainted: P        W  OE     4.19.2-1-MANJARO #1
Nov 16 10:47:48 box kernel: Hardware name: MEDION X781X/X782X/X781X/X782X, BIOS E1762IM7.50M 01/04/2013
Nov 16 10:47:48 box kernel: Call Trace:
Nov 16 10:47:48 box kernel:  dump_stack+0x5c/0x80
Nov 16 10:47:48 box kernel:  __schedule_bug.cold.14+0x38/0x51
Nov 16 10:47:48 box kernel:  __schedule+0x6fd/0x8b0
Nov 16 10:47:48 box kernel:  schedule+0x32/0x90
Nov 16 10:47:48 box kernel:  schedule_timeout+0x311/0x4a0
Nov 16 10:47:48 box kernel:  ? resched_curr+0x23/0xd0
Nov 16 10:47:48 box kernel:  ? check_preempt_curr+0x7a/0x90
Nov 16 10:47:48 box kernel:  wait_for_common+0x15f/0x190
Nov 16 10:47:48 box kernel:  ? wake_up_q+0x70/0x70
Nov 16 10:47:48 box kernel:  do_coredump+0x35d/0xe98
Nov 16 10:47:48 box kernel:  ? _raw_spin_lock_irqsave+0x25/0x50
Nov 16 10:47:48 box kernel:  ? _raw_spin_unlock_irqrestore+0x20/0x40
Nov 16 10:47:48 box kernel:  get_signal+0x29b/0x5d0
Nov 16 10:47:48 box kernel:  ? page_fault+0x8/0x30
Nov 16 10:47:48 box kernel:  do_signal+0x36/0x700
Nov 16 10:47:48 box kernel:  ? page_fault+0x8/0x30
Nov 16 10:47:48 box kernel:  exit_to_usermode_loop+0xbf/0xe0
Nov 16 10:47:48 box kernel:  prepare_exit_to_usermode+0x64/0x90
Nov 16 10:47:48 box kernel:  retint_user+0x8/0x8
Nov 16 10:47:48 box kernel: RIP: 0033:0x7f2c56e6c32d
Nov 16 10:47:48 box kernel: Code: 58 b8 ff ff ff ff 5b 5d 41 5c 41 5d 41 5e 41 5f c3 0f 1f 40 00 48 8b 4f 20 48 3b 0d fd 6c 00 00 4c 8b 47 28 0f 84 9b 00 00 00 <48> 89 >
Nov 16 10:47:48 box kernel: RSP: 002b:00007ffd79ac5c70 EFLAGS: 00013216
Nov 16 10:47:48 box kernel: RAX: 00005579670d4040 RBX: 00007ffd79ac5d20 RCX: 0000000000000057
Nov 16 10:47:48 box kernel: RDX: 00007ffd79ac5db0 RSI: 0000000000000040 RDI: 00007ffd79ac5d20
Nov 16 10:47:48 box kernel: RBP: 0000000000000057 R08: 0000000000000000 R09: 0000000000000000
Nov 16 10:47:48 box kernel: R10: 00005579670d4000 R11: 0000000000000000 R12: 00007f2c59bd5000
Nov 16 10:47:48 box kernel: R13: 00007ffd79ac6050 R14: 0000000000000000 R15: 00007f2c59bd6120
Nov 16 10:47:48 box systemd[1]: Started Process Core Dump (PID 6463/UID 0).
$ pacman -Qs nvidia
local/lib32-libvdpau 1.1.1-3
    Nvidia VDPAU library
local/lib32-nvidia-utils 1:410.78-1
    NVIDIA drivers utilities (32-bit)
local/lib32-opencl-nvidia 1:410.78-1
    OpenCL implemention for NVIDIA (32-bit)
local/libvdpau 1.1.1+3+ga21bf7a-1
    Nvidia VDPAU library
local/libxnvctrl 410.73-1
    NVIDIA NV-CONTROL X extension
local/linux414-nvidia 1:410.78-1 (linux414-extramodules)
    NVIDIA drivers for linux.
local/linux419-nvidia 1:410.78-1 (linux419-extramodules)
    NVIDIA drivers for linux.
local/mhwd-nvidia 1:410.78-1
    MHWD module-ids for nvidia 410.78
local/mhwd-nvidia-340xx 340.107-1
    MHWD module-ids for nvidia 340.107
local/mhwd-nvidia-390xx 390.87-1
    MHWD module-ids for nvidia 390.87
local/nvidia-utils 1:410.78-1
    NVIDIA drivers utilities
local/opencl-nvidia 1:410.78-1
    OpenCL implemention for NVIDIA

Curiouser and curiouser:

[    52.526] (II) modeset(G0): [DRI2] Setup complete
[    52.526] (II) modeset(G0): [DRI2]   DRI driver: i965
[    52.526] (II) modeset(G0): [DRI2]   VDPAU driver: i965
[    52.527] (II) NVIDIA: Using 6144.00 MB of virtual memory for indirect memory
[    52.527] (II) NVIDIA:     access.
[    52.533] (EE) NVIDIA(0): Failed to allocate primary buffer: out of memory.
[    52.533] (EE) NVIDIA(0):  *** Aborting ***
[    52.556] (EE) 
Fatal server error:
[    52.556] (EE) AddScreen/ScreenInit failed for driver 0

#6

I have several amdgpu related issues with kernel 4.19:

  • My monitor, connected thru displayport, switched itself off whenever the system goes to sleep and it takes several seconds for it to turn itself on when I move the mouse or press a key on the keyboard.

  • The system won’t shut itself down or reboot by software, I have to use the power/reboot button.

  • When gaming, I experience quite a lot more stuttering and random freezes. In between freezes, the monitor seems to lose the displayport signal as it reports a “No connection” error.

  • Booting the system is several times slower.

I’ve had these issues with every iternation of the 4.19 kernel so far. dmesg has these errors at boot:

nov 05 16:14:15 kernel: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed testing IB on ring 14 (-110).
nov 05 16:14:15 kernel: [drm:uvd_v6_0_enc_ring_test_ib [amdgpu]] *ERROR* amdgpu: IB test timed out.
nov 05 16:14:14 kernel: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed testing IB on ring 13 (-110).
nov 05 16:14:14 kernel: [drm:uvd_v6_0_enc_ring_test_ib [amdgpu]] *ERROR* amdgpu: IB test timed out.
nov 05 16:14:13 kernel: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed testing IB on ring 12 (-110).
nov 05 16:14:13 kernel: [drm:amdgpu_uvd_ring_test_ib [amdgpu]] *ERROR* amdgpu: (0)IB test timed out.
nov 05 16:14:11 kernel: amdgpu: [powerplay] Failed to retrieve minimum clocks.

I don’t have this problem and never had it with kernel versions 4.18 or earlier.


[Testing Update] 2018-11-24 - Kernels, Nvidia
AMDGPU errors "failed testing IB on ring"
#7

Hmm. I don’t see any PRIME changes … Can you test with several kernels?


#8

It’s working again now. It may have been because mhwd had blacklisted drm, or it was the laptop itself playing up.


#9

Good to know. I’ve to look at PRIME at some point. Maybe we may find a way to set it up automatically. Might be needed for one of the projects I’ve in mind for 2019 based on a Lenovo Notebook.


#10

On one of my installs, not PRIME, is just a desktop, i had to create a new file /etc/modprobe.d/blacklist.conf with this lines:

blacklist nouveau
blacklist ttm
blacklist drm_kms_helper
blacklist drm
blacklist nvidiafb

because the mhwd-gpu.conf with the same content was ignored and i couldn’t log in.


#11

I’ve been looking on-and-off at reimplementing Ubuntu’s prime-switch as that should be a bit more reliable than bumblebee for the most recent Optimus laptops.

It needs a fair bit of work, though, as the Ubuntu solution relies on a lot of Ubuntu-specific setup.


#12

TuxnVape gave me some to look at. Also there is nvidia-prime.


#13

Ah, yes, that’s what I was thinking of:


#14

Whats your hardware?


#15

I need to ask this, as it seems I am always out of context with everyone else, what am I looking for when submitting branch issues, hardware related stuff only? @philm @jonathon


#16

A Radeon RX580 8 GB.


#17

I run the unstable branch. If there is a recent unstable announcement thread it means something “major” has changed, so if I spot something around the same day as the announcement I report here. Otherwise it goes into #manjaro-development:unstable-branch.


#18

On the GNOME side of things this update is a huge improvement for nvidia systems. I’m not sure if it is the combination of updated driver + Mutter or just Mutter, but it makes the mutter-781835-workaround from AUR mostly obsolete in my case because the performance improved really a lot.
I have to test it a bit more but it looks very promising.


#19

yes, seems faster.


#20

Update today with only one package (first):

core/archlinux-keyring  20181122-1    20181126-1             0,00 MiB             0,62 MiB
[...]
==> Aktualisiere Trust-Datenbank...
gpg: nächste "Trust-DB"-Pflichtüberprüfung am 2019-03-29
:: Starte post-transaction hooks...
(1/2) Initialize and populate keyring ...
Konnte execv nicht aufrufen (Datei oder Verzeichnis nicht gefunden)
Fehler: Befehl konnte nicht korrekt ausgeführt werden
(2/2) Arming ConditionNeedsUpdate...

The kernel update work nonethelesse.