kde juhraya, there's something not right with this one...

#1

installed, it sticks on Started TLP system startup/shutdown for ages...
pamac updates - thought it had hung, took ages
installing new kernel, taking ages...
found this in the journal

mai 13 17:53:07 amd plasmashell[823]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/explorer/AppletDelegate.qml:82:13: QML QQuickItem*: Detected anchors on an item that is managed by a layo>
mai 13 17:53:07 amd plasmashell[823]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/explorer/AppletDelegate.qml:82:13: QML QQuickItem*: Detected anchors on an item that is managed by a layo>
mai 13 17:53:07 amd plasmashell[823]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/explorer/AppletDelegate.qml:82:13: QML QQuickItem*: Detected anchors on an item that is managed by a layo>
mai 13 17:53:07 amd plasmashell[823]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/explorer/AppletDelegate.qml:82:13: QML QQuickItem*: Detected anchors on an item that is managed by a layo>
mai 13 17:53:07 amd plasmashell[823]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/explorer/AppletDelegate.qml:82:13: QML QQuickItem*: Detected anchors on an item that is managed by a layo>
mai 13 17:53:07 amd plasmashell[823]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/explorer/AppletDelegate.qml:82:13: QML QQuickItem*: Detected anchors on an item that is managed by a layo>
mai 13 17:53:07 amd plasmashell[823]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/explorer/AppletDelegate.qml:82:13: QML QQuickItem*: Detected anchors on an item that is managed by a layo>
mai 13 17:53:07 amd plasmashell[823]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/explorer/AppletDelegate.qml:82:13: QML QQuickItem*: Detected anchors on an item that is managed by a layo>
mai 13 17:53:10 amd plasmashell[823]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:343: Unable to assign [undefined] to int
mai 13 17:53:10 amd plasmashell[823]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:371: TypeError: Type error
mai 13 17:53:10 amd plasmashell[823]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 11967, resource id: 62914567, major code: 142 (Unknown), minor code: 3
mai 13 17:53:10 amd plasmashell[823]: qt.qpa.xcb: QXcbConnection: XCB error: 152 (Unknown), sequence: 11968, resource id: 31457568, major code: 143 (Unknown), minor code: 2
mai 13 17:53:10 amd plasmashell[823]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 11974, resource id: 62914567, major code: 142 (Unknown), minor code: 3
mai 13 17:53:10 amd plasmashell[823]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 11975, resource id: 67108880, major code: 142 (Unknown), minor code: 3
mai 13 17:53:10 amd plasmashell[823]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 11979, resource id: 67108880, major code: 142 (Unknown), minor code: 3
mai 13 17:53:10 amd plasmashell[823]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 11983, resource id: 46137350, major code: 142 (Unknown), minor code: 3
mai 13 17:53:10 amd plasmashell[823]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 12073, resource id: 46137350, major code: 142 (Unknown), minor code: 3
mai 13 17:53:10 amd plasmashell[823]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 12074, resource id: 46137677, major code: 142 (Unknown), minor code: 3
mai 13 17:53:12 amd plasmashell[823]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 12128, resource id: 46137350, major code: 142 (Unknown), minor code: 3
mai 13 17:53:12 amd plasmashell[823]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 12129, resource id: 46137677, major code: 142 (Unknown), minor code: 3
mai 13 17:53:13 amd plasmashell[823]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 12160, resource id: 67108880, major code: 142 (Unknown), minor code: 3
mai 13 17:53:13 amd plasmashell[823]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 12161, resource id: 46137350, major code: 142 (Unknown), minor code: 3
mai 13 17:53:13 amd plasmashell[823]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 12162, resource id: 46137677, major code: 142 (Unknown), minor code: 3
mai 13 17:53:13 amd plasmashell[823]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 12163, resource id: 46137350, major code: 142 (Unknown), minor code: 3
mai 13 17:53:13 amd plasmashell[823]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 12164, resource id: 46137677, major code: 142 (Unknown), minor code: 3
mai 13 17:53:16 amd plasmashell[823]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:343: Unable to assign [undefined] to int
mai 13 17:53:16 amd plasmashell[823]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:371: TypeError: Type error
mai 13 17:53:17 amd plasmashell[823]: KActivities: Database connection:  "kactivities_db_resources_140378385840256_readonly" 
                                          query_only:          QVariant(qlonglong, 1) 
                                          journal_mode:        QVariant(QString, "wal") 
                                          wal_autocheckpoint:  QVariant(qlonglong, 100) 
                                          synchronous:         QVariant(qlonglong, 0)
mai 13 17:53:17 amd plasmashell[823]: Nothing to load - the client id is empty
mai 13 17:53:17 amd plasmashell[823]: QObject::connect(KAStatsFavoritesModel, InvalidAppsFilterProxy): invalid null parameter
mai 13 17:53:17 amd plasmashell[823]: Closing SQL connection:  "kactivities_db_resources_140378385840256_readonly"
mai 13 17:53:17 amd plasmashell[823]: KActivities: Database connection:  "kactivities_db_resources_140378385840256_readonly" 
                                          query_only:          QVariant(qlonglong, 1) 
                                          journal_mode:        QVariant(QString, "wal") 
                                          wal_autocheckpoint:  QVariant(qlonglong, 100) 
                                          synchronous:         QVariant(qlonglong, 0)
mai 13 17:53:17 amd plasmashell[823]: Nothing to load - the client id is empty
mai 13 17:53:20 amd plasmashell[823]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:343: Unable to assign [undefined] to int
mai 13 17:53:20 amd plasmashell[823]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:371: TypeError: Type error
mai 13 17:53:37 amd plasmashell[823]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 13151, resource id: 67108880, major code: 142 (Unknown), minor code: 3
mai 13 17:53:37 amd plasmashell[823]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:343: Unable to assign [undefined] to int
mai 13 17:53:37 amd plasmashell[823]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:371: TypeError: Type error
mai 13 17:53:39 amd plasmashell[823]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:343: Unable to assign [undefined] to int
mai 13 17:53:39 amd plasmashell[823]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:371: TypeError: Type error
mai 13 17:53:40 amd plasmashell[823]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:343: Unable to assign [undefined] to int
mai 13 17:53:40 amd plasmashell[823]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:371: TypeError: Type error
mai 13 17:53:42 amd plasmashell[823]: KActivitiesStats( 0x55fee7381370 ) ResultModelPrivate::onResultScoreUpdated  result added: "applications:org.kde.konsole.desktop" score: 1 last: 1557762819 first: 155776

think I might go back to xcfe :crazy_face:

#2

here's my config

           Distro: Manjaro Linux 
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME B350M-A v: Rev X.0x serial: <filter> UEFI: American Megatrends v: 4602 
           date: 03/07/2019 
CPU:       Topology: Dual Core model: AMD A6-9500 RADEON R5 8 COMPUTE CORES 2C+6G bits: 64 type: MCP arch: Excavator rev: 1 
           L2 cache: 1024 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 13979 
           Speed: 1397 MHz min/max: 1400/3500 MHz Core speeds (MHz): 1: 1403 2: 1537 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] vendor: ASUSTeK driver: amdgpu v: kernel 
           bus ID: 00:01.0 
           Display: x11 server: X.Org 1.20.4 driver: amdgpu FAILED: ati unloaded: modesetting resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD CARRIZO (DRM 3.32.0 5.2.0-1-MANJARO LLVM 8.0.0) v: 4.5 Mesa 19.0.3 direct render: Yes 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] Kabini HDMI/DP Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 00:01.1 
           Device-2: Advanced Micro Devices [AMD] Family 15h Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 00:09.2 
           Sound Server: ALSA v: k5.2.0-1-MANJARO 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169 v: kernel port: e000 
           bus ID: 06:00.0 
           IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 335.36 GiB used: 6.74 GiB (2.0%) 
           ID-1: /dev/sda vendor: Lenovo model: SSD SL700 240G size: 223.57 GiB 
           ID-2: /dev/sdb vendor: Integral Memory model: V Series SATA SSD 120GB size: 111.79 GiB 
Partition: ID-1: / size: 109.24 GiB used: 6.74 GiB (6.2%) fs: ext4 dev: /dev/sdb2 
           ID-2: swap-1 size: 8.16 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 31.5 C mobo: N/A gpu: amdgpu temp: 31 C 
           Fan Speeds (RPM): cpu: 0 
Info:      Processes: 187 Uptime: 4m Memory: 7.23 GiB used: 1.28 GiB (17.8%) Init: systemd Compilers: gcc: 8.3.0 Shell: bash 
           v: 5.0.7 inxi: 3.0.34```
#3

Please enclose your outputs with the </> button.

#4

edited...is that better?

#5

No. There's a button on the editor. Select the text and press that button. If this doesn't work enclose all the output with beginning and ending three accents ```

1 Like
#6

whoop de whoop, gotcha :star_struck:

1 Like
#7

When it is stuck at the TLP message, what happens if you press CTRL+ALT+F3. If it changes to a text login screen, then login as root and try to reupdate:
pacman-mirrors -f5 && pacman -Syyu

#8

it boots up fast on my old intel rig......so some more software that doesn't like AMD
mind you saying it's fast, pamac is stuck for ages on checking inter conflicts
here's my intel config

System:
  Host: g4560 Kernel: 5.0.15-1-MANJARO x86_64 bits: 64 compiler: gcc 
  v: 8.3.0 Desktop: KDE Plasma 5.15.5 Distro: Manjaro Linux 
Machine:
  Type: Desktop System: MSI product: MS-7994 v: 1.0 serial: <filter> 
  Mobo: MSI model: B150M ECO (MS-7994) v: 1.0 serial: <filter> 
  UEFI: American Megatrends v: 1.C0 date: 07/12/2018 
Battery:
  Device-1: hid-00:02:76:2d:b1:d2-battery model: Motorola Bluetooth Mouse 
  charge: N/A status: Discharging 
CPU:
  Topology: Dual Core model: Intel Pentium G4560 bits: 64 type: MT MCP 
  arch: Kaby Lake rev: 9 L2 cache: 3072 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28040 
  Speed: 800 MHz min/max: 800/3500 MHz Core speeds (MHz): 1: 800 2: 800 
  3: 800 4: 800 
Graphics:
  Device-1: Intel HD Graphics 610 vendor: Micro-Star MSI driver: i915 
  v: kernel bus ID: 00:02.0 
  Display: x11 server: X.Org 1.20.4 driver: intel unloaded: modesetting 
  resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 610 (Kaby Lake GT1) 
  v: 4.5 Mesa 19.0.3 direct render: Yes 
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio 
  vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
  Sound Server: ALSA v: k5.0.15-1-MANJARO 
Network:
  Device-1: Intel Ethernet I219-V vendor: Micro-Star MSI driver: e1000e 
  v: 3.2.6-k port: f040 bus ID: 00:1f.6 
  IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 111.79 GiB used: 6.43 GiB (5.8%) 
  ID-1: /dev/sda model: SATA SSD size: 111.79 GiB 
Partition:
  ID-1: / size: 109.24 GiB used: 6.43 GiB (5.9%) fs: ext4 dev: /dev/sda2 
Sensors:
  System Temperatures: cpu: 29.8 C mobo: 28.5 C 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 182 Uptime: 5m Memory: 3.75 GiB used: 1.26 GiB (33.6%) 
  Init: systemd Compilers: gcc: 8.3.0 Shell: bash v: 5.0.7 inxi: 3.0.34 

#9

kill -9 on that update :stuck_out_tongue_closed_eyes:
updated using terminal.....it's actually quite fast on this 'old pc' :crazy_face:
Edit: and a reboot was fast too!

#10

the 'Applications' button is missing from the 'Manjaro Hello' window
I know it's an extra app but I think it should be installed by default......more professional, helps newbies :+1:

#11

You're confusing me, @confused!! I can't help you if we don't follow one line of thought to the end. Please stick with one computer and answer mu questions clearly.

Do you still need help? Can change terminal and login on the first machine? If yes, did you try to update?

Lastly, is the second machine working properly? If yes, please don't bring it to this topic.

#12

sorry I have 'low concentration' issues sometimes......
Anyway this is not just a juhraya problem, I experience the same with a new illyria build too
10 second boot on old 3 year Intel hardware, compared to about a minute boot with 'new' AMD hardware....
what's your hardware/software and boot times?

#13

Although it's not exactly the same problem, you could try this:


Instead of removing, it's probably safer to rename the folder.

#14

I deleted those 3 database files, no difference
@mbb, when I dish out a CTRL+ATRL+F3 it makes it boot much quicker!

#15

Besides the Intel machine having 4 cores compared to a 2 core AMD CPU, this could be the issue. Maybe it takes longer because Xorg is trying to load the ati driver and then fails and ends up loading the amdgpu driver. One way to circumvent this is by writing a Xorg config file to load specifically the amdgpu driver. Another way is to use kernel parameters.

Well, on this laptop I have an i5-3427U CPU and an Intel HD4000. My hardware is always outdated and middle-ground in what concerns performance.

[mbb@mbb-laptop buildtest]$ systemd-analyze
Startup finished in 2.577s (firmware) + 893ms (loader) + 4.692s (kernel) + 22.993s (userspace) = 31.156s 
graphical.target reached after 22.825s in userspace

Boot times vary by many factors, such as trim operations and file system mounts, for example. I don't care about boot times that much, but one minute I can understand is a bit too much. You can issue systemd-analyze blame to see whats taking longer.

[mbb@mbb-laptop buildtest]$ systemd-analyze blame
         35.934s systemd-fsck@dev-disk-by\x2duuid-aa222f36\x2db6e7\x2d41f5\x2d8f1d\x2db4a5bb25a044.service
         23.562s fstrim.service
         20.478s nmb.service
          1.779s man-db.service
           898ms lvm2-monitor.service
           861ms dev-sda1.device
           776ms systemd-logind.service
           549ms systemd-timesyncd.service
           469ms ModemManager.service
           425ms org.cups.cupsd.service
           419ms upower.service
           413ms systemd-journald.service
           407ms systemd-udevd.service
           390ms swapfile.swap
           341ms ldconfig.service
           314ms nbfc.service
           241ms mnt-Windows.mount
           215ms smb.service
           214ms avahi-daemon.service
           214ms polkit.service
           191ms nilfs2-autoclean_mnt-Data.service
           187ms bluetooth.service
           179ms NetworkManager.service
           173ms wakeup-events.service
           167ms tlp.service
           147ms mnt-Data.mount
           111ms systemd-udev-trigger.service
           111ms logrotate.service
            99ms systemd-journal-flush.service
            90ms user@1000.service
            87ms systemd-modules-load.service
            75ms udisks2.service
            45ms systemd-sysusers.service
            44ms boot-efi.mount
            37ms colord.service
            33ms systemd-binfmt.service
            32ms systemd-tmpfiles-setup.service
            31ms systemd-tmpfiles-setup-dev.service
            30ms grub-boot-indeterminate.service
            27ms wpa_supplicant.service
            27ms systemd-journal-catalog-update.service
            26ms systemd-tmpfiles-clean.service
            25ms systemd-random-seed.service
            23ms systemd-update-utmp.service
            23ms alsa-restore.service
            21ms dev-mqueue.mount
            21ms systemd-sysctl.service
            17ms systemd-backlight@backlight:intel_backlight.service
            16ms dev-hugepages.mount
            16ms user-runtime-dir@1000.service
            16ms kmod-static-nodes.service
            14ms systemd-remount-fs.service
            13ms systemd-update-done.service
            13ms sys-kernel-debug.mount
            12ms tmp.mount
            10ms systemd-user-sessions.service
             8ms systemd-rfkill.service
             5ms rtkit-daemon.service
             4ms proc-sys-fs-binfmt_misc.mount
             3ms sys-fs-fuse-connections.mount
             3ms sys-kernel-config.mount

As you can see, in my case nmb.service is the main culprit, but fstrim and fsck also take a lot.

1 Like
#16

I'm having a similar problem in my Wife's computer but haven't dug on it yet. Sometimes it gets stuck on the output screen (I mean the status, which you probably don't see because you have the quiet boot parameter) and SDDM only shows when I try to change tty :thinking:

#17

@mbb thanks for the feedback, yes the Pentium range is stunning value for money, think that one is Kaby lake...
I've got a Ryzen 3 sitting in a box but all these 'MAD' AMD issues make me think I will just dump this rig and go back to Intel :sob:

systemd-analyze blame
           987ms lvm2-monitor.service
           765ms dev-sdb2.device
           677ms systemd-logind.service
           328ms systemd-udevd.service
           293ms ModemManager.service
           286ms systemd-journald.service
           279ms tlp.service
           160ms polkit.service
           152ms dev-disk-by\x2duuid-9fa4fa21\x2d7049\x2d4f52\x2d93e2\x2d62251538bb89.swap
           148ms upower.service
           126ms NetworkManager.service
           120ms systemd-udev-trigger.service
           116ms systemd-journal-flush.service
           106ms udisks2.service
            89ms avahi-daemon.service
            76ms user@1000.service
            58ms systemd-binfmt.service
            58ms systemd-remount-fs.service
            48ms boot-efi.mount
            48ms systemd-fsck@dev-disk-by\x2duuid-64BA\x2dE3B0.service
            48ms org.cups.cupsd.service
            44ms grub-boot-indeterminate.service
            43ms systemd-modules-load.service
            34ms systemd-sysctl.service
            29ms systemd-tmpfiles-setup.service
            27ms dev-mqueue.mount
            27ms sys-kernel-config.mount
            26ms dev-hugepages.mount
            24ms systemd-tmpfiles-setup-dev.service
            24ms sys-kernel-debug.mount
            22ms kmod-static-nodes.service
            20ms proc-sys-fs-binfmt_misc.mount
            19ms sys-fs-fuse-connections.mount
            17ms user-runtime-dir@1000.service
            15ms systemd-random-seed.service
            12ms systemd-update-utmp.service
             9ms systemd-user-sessions.service
             7ms systemd-backlight@backlight:acpi_video0.service
             7ms rtkit-daemon.service
             5ms tmp.mount

#18
systemd-analyze
Startup finished in 8.423s (firmware) + 2.166s (loader) + 8.122s (kernel) + 2.388s (userspace) = 21.101s 
graphical.target reached after 2.107s in userspace

#19

is there a 'quick fix' way of trying either of these?

#20

so now I'm even more bleeding edge; had a bios update too!
and the boot on this build still sucks :stuck_out_tongue_closed_eyes:

System:    Host: amd Kernel: 5.2.0-1-MANJARO x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: KDE Plasma 5.15.5 
           Distro: Manjaro Linux 
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME B350M-A v: Rev X.0x serial: <filter> UEFI: American Megatrends v: 4801 
           date: 04/25/2019 
CPU:       Topology: Dual Core model: AMD A6-9500 RADEON R5 8 COMPUTE CORES 2C+6G bits: 64 type: MCP arch: Excavator rev: 1 
           L2 cache: 1024 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 13981 
           Speed: 1396 MHz min/max: 1400/3500 MHz Core speeds (MHz): 1: 1468 2: 1543 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] vendor: ASUSTeK driver: amdgpu v: kernel 
           bus ID: 00:01.0 
           Display: x11 server: X.Org 1.20.4 driver: amdgpu FAILED: ati unloaded: modesetting resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD CARRIZO (DRM 3.32.0 5.2.0-1-MANJARO LLVM 8.0.0) v: 4.5 Mesa 19.0.3 direct render: Yes 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] Kabini HDMI/DP Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 00:01.1 
           Device-2: Advanced Micro Devices [AMD] Family 15h Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 00:09.2 
           Sound Server: ALSA v: k5.2.0-1-MANJARO 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169 v: kernel port: e000 
           bus ID: 06:00.0 
           IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 335.36 GiB used: 10.45 GiB (3.1%) 
           ID-1: /dev/sda vendor: Lenovo model: SSD SL700 240G size: 223.57 GiB 
           ID-2: /dev/sdc vendor: Integral Memory model: V Series SATA SSD 120GB size: 111.79 GiB 
Partition: ID-1: / size: 109.24 GiB used: 10.45 GiB (9.6%) fs: ext4 dev: /dev/sdc2 
           ID-2: swap-1 size: 8.16 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 29.8 C mobo: N/A gpu: amdgpu temp: 29 C 
           Fan Speeds (RPM): cpu: 0 
Info:      Processes: 160 Uptime: 7m Memory: 7.23 GiB used: 1.13 GiB (15.6%) Init: systemd Compilers: gcc: 8.3.0 Shell: bash 
           v: 5.0.7 inxi: 3.0.34 

Any devs/uber geeks/experts got a clue what's going down?
I'm thinking this is a video/graphics issue

mai 14 15:14:22 amd systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:acpi_video0...
mai 14 15:14:22 amd systemd-backlight[430]: Failed to get backlight or LED device 'backlight:acpi_video0': No such device
mai 14 15:14:22 amd systemd[1]: systemd-backlight@backlight:acpi_video0.service: Main process exited, code=exited, status=1/FAILURE
mai 14 15:14:22 amd systemd[1]: systemd-backlight@backlight:acpi_video0.service: Failed with result 'exit-code'.
mai 14 15:14:22 amd systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
mai 14 15:14:22 amd audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-backlight@backlight:acpi_video0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mai 14 15:14:22 amd kernel: audit: type=1130 audit(1557839662.284:11): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-backlight@backlight:acpi_video0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mai 14 15:19:52 amd systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:acpi_video0...
mai 14 15:19:52 amd systemd-backlight[446]: Failed to get backlight or LED device 'backlight:acpi_video0': No such device
mai 14 15:19:52 amd systemd[1]: systemd-backlight@backlight:acpi_video0.service: Main process exited, code=exited, status=1/FAILURE
mai 14 15:19:52 amd systemd[1]: systemd-backlight@backlight:acpi_video0.service: Failed with result 'exit-code'.
mai 14 15:19:52 amd systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
mai 14 15:19:52 amd audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-backlight@backlight:acpi_video0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'