[Stable Update] 2018-02-17 - Kernels, KDE, MATE, Firefox, LibreOffice, Mesa, Systemd

Well, you have not burst my bubble in any way, but perchance my rebuttal may risk that outcome for you :wink: I had hoped that readers would implicitly discern the specific context of my remark, but it seems not. My error possibly was by not using the same full upper case as the Konsole output provides in the sudo spectre-meltdown-checker check, which to remove ambiguity i now partially paste [& hope not to get moderated out for so-doing]:

CVE-2017-5753 [bounds check bypass] aka ‘Spectre Variant 1’

STATUS: NOT VULNERABLE (Mitigation: __user pointer sanitization)

CVE-2017-5715 [branch target injection] aka ‘Spectre Variant 2’

STATUS: NOT VULNERABLE (Mitigation: Full generic retpoline)

CVE-2017-5754 [rogue data cache load] aka ‘Meltdown’ aka ‘Variant 3’

STATUS: NOT VULNERABLE (Mitigation: PTI)

The context of my remark was simply these tests. I do not for a moment naively fantasise that all my online risks are now vanquished… but it is true that i now have somewhat more protection now than previously.

2 Likes

USB optical mouse and synaptics touchpad, which I assume was the cause of the wobble (new libinput and kernel combo) and what the patch fixed.

$ hwinfo --mouse
28: USB 00.0: 10503 USB Mouse
  [Created at usb.122]
  Unique ID: KRJj.XqdzRE1GRIA
  Parent ID: uIhY.2DFUsyrieMD
  SysFS ID: /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0
  SysFS BusID: 3-1:1.0
  Hardware Class: mouse
  Model: "Logitech M105 Optical Mouse"
  Hotplug: USB
  Vendor: usb 0x046d "Logitech, Inc."
  Device: usb 0xc077 "M105 Optical Mouse"
  Revision: "72.00"
  Compatible to: int 0x0210 0x0018
  Driver: "usbhid"
  Driver Modules: "usbhid"
  Device File: /dev/input/mice (/dev/input/mouse0)
  Device Files: /dev/input/mice, /dev/input/mouse0, /dev/input/event5, /dev/input/by-id/usb-Logitech_USB_Optical_Mouse-event-mouse, /dev/input/by-path/pci-0000:00:14.0-usb-0:1:1.0-event-mouse, /dev/input/by-id/usb-Logitech_USB_Optical_Mouse-mouse, /dev/input/by-path/pci-0000:00:14.0-usb-0:1:1.0-mouse
  Device Number: char 13:63 (char 13:32)
  Speed: 1.5 Mbps
  Module Alias: "usb:v046DpC077d7200dc00dsc00dp00ic03isc01ip02in00"
  Driver Info #0:
    Buttons: 8
    Wheels: 1
    XFree86 Protocol: explorerps/2
    GPM Protocol: exps2
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #26 (Hub)

38: PS/2 00.0: 10500 PS/2 Mouse
  [Created at input.249]
  Unique ID: AH6Q.ZHI3OT7LsxA
  Hardware Class: mouse
  Model: "SynPS/2 Synaptics TouchPad"
  Vendor: 0x0002
  Device: 0x0007 "SynPS/2 Synaptics TouchPad"
  Compatible to: int 0x0210 0x0002
  Device File: /dev/input/mice (/dev/input/mouse1)
  Device Files: /dev/input/mice, /dev/input/mouse1, /dev/input/event18, /dev/input/by-path/platform-i8042-serio-1-event-mouse, /dev/input/by-path/platform-i8042-serio-1-mouse
  Device Number: char 13:63 (char 13:33)
  Driver Info #0:
    Buttons: 2
    Wheels: 0
    XFree86 Protocol: explorerps/2
    GPM Protocol: exps2
  Config Status: cfg=new, avail=yes, need=no, active=unknown

Hello friends. After the last update there is a problem in the KDE. After the laptop is restarted, all applications added to Favorites, Recent Documents and Recent Programs disappear. What can be done to solve this problem?

I understand, just making sure most people reading your post don’t misinterpret and assume the results of these checks …

$ vul
/sys/devices/system/cpu/vulnerabilities/meltdown:Mitigation: PTI
/sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: __user pointer sanitization
/sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full generic retpoline

… mean that the very serious security flaw is now resolved and we are all safe and sound again.

We are basically on the same page.

1 Like

1st - KDE Plasma / Intel CPU & onboard GPU: update worked very well

2nd - KDE Plasma / AMD CPU / NVIDIA GPU: update stucked due to deprecated kernel 4.13. … Update then went mad because of nvidia graphic driver dependency issues. Solved by deinstalling deprecated kernel. Afterwards it worked like a charme.

Same here - DE (Xfce) doesn’t appear until I change to another tty and back to the xorg session (tty1).

In /etc/X11/mhwd.d/nvidia.conf this line

Option         "metamodes" "DVI-D-0: nvidia-auto-select +0+0 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}, HDMI-0: nvidia-auto-select +1920+0 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}"

is the culprit.

If I remove it, the DE (Xfce) appears, but screen tearing is now an issue.

To turn on and off the 2nd Screen I use two simple commands in bash scripts:
On: xrandr --output HDMI-0 --auto --right-of DVI-D-0
Off: xrandr --output HDMI-0 --off
I start Xfce using only one screen. Whenever I need the second screen I run script “On”. Still works flawlessly. But using script “Off” afterwards, to turn off the 2nd screen again results in a still picture of the xorg session. Changing to another tty and then back to the xorg session fixes the issue (same as right after the login).

For now I have to deal with Ctrl+Alt+F7 and Ctrl+Alt+F1 , cause screen tearing drives me nuts…

2 Likes

Sounds like this:

1 Like

After this update my laptop log out randomly and take me to login screen. It happened twice and then the system freezed. After restart it is working fine.

Edit: It’s happening again.
These are most recent entries in journalctl. This part was in red so maybe it has to do with the log out.

Feb 18 17:32:32 rishab-pc systemd[746]: bamfdaemon.service: Main process exited, code=exited, status=1/FAILURE
Feb 18 17:32:32 rishab-pc systemd[746]: bamfdaemon.service: Failed with result 'exit-code'.
Feb 18 17:32:32 rishab-pc systemd[746]: Failed to start BAMF Application Matcher Framework.
Feb 18 17:32:33 rishab-pc systemd-coredump[2513]: Process 727 (Xorg) of user 0 dumped core.
                                                  
                                                  Stack trace of thread 740:
                                                  #0  0x00007f328b8527e4 n/a (intel_drv.so)
                                                  #1  0x00007f328b7d6068 n/a (intel_drv.so)
                                                  #2  0x000055e55b0d0d79 n/a (Xorg)
                                                  #3  0x00007f328f873dd0 __restore_rt (libpthread.so.0)
                                                  #4  0x00007f328f4df860 raise (libc.so.6)
                                                  #5  0x00007f328f4e0ec9 abort (libc.so.6)
                                                  #6  0x00007f328f4d80bc __assert_fail_base (libc.so.6)
                                                  #7  0x00007f328f4d8133 __assert_fail (libc.so.6)
                                                  #8  0x00007f3288dad62e n/a (libinput.so.10)
                                                  #9  0x00007f3288dae298 n/a (libinput.so.10)
                                                  #10 0x00007f3288d9a188 n/a (libinput.so.10)
                                                  #11 0x00007f3288d99a6f libinput_dispatch (libinput.so.10)
                                                  #12 0x00007f3289000c19 n/a (libinput_drv.so)
                                                  #13 0x000055e55b0cf163 n/a (Xorg)
                                                  #14 0x000055e55b0d1861 n/a (Xorg)
                                                  #15 0x000055e55b0cefae n/a (Xorg)
                                                  #16 0x00007f328f86908c start_thread (libpthread.so.0)
                                                  #17 0x00007f328f5a0e7f __clone (libc.so.6)
                                                  
                                                  Stack trace of thread 727:
                                                  #0  0x00007f328f5a0fe6 epoll_pwait (libc.so.6)
                                                  #1  0x000055e55b0d1817 n/a (Xorg)
                                                  #2  0x000055e55b0ca70b WaitForSomething (Xorg)
                                                  #3  0x000055e55af6afc3 n/a (Xorg)
                                                  #4  0x000055e55af6f260 n/a (Xorg)
                                                  #5  0x00007f328f4cbf4a __libc_start_main (libc.so.6)
                                                  #6  0x000055e55af58f0a _start (Xorg)
                                                  
                                                  Stack trace of thread 737:
                                                  #0  0x00007f328f86f3bd pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                                                  #1  0x00007f328b8524a0 n/a (intel_drv.so)
                                                  #2  0x00007f328f86908c start_thread (libpthread.so.0)
                                                  #3  0x00007f328f5a0e7f __clone (libc.so.6)
Feb 18 17:32:33 rishab-pc systemd[746]: bamfdaemon.service: Service hold-off time over, scheduling restart.
Feb 18 17:32:33 rishab-pc systemd[746]: bamfdaemon.service: Scheduled restart job, restart counter is at 2.
Feb 18 17:32:33 rishab-pc systemd[746]: Stopped BAMF Application Matcher Framework.
Feb 18 17:32:33 rishab-pc systemd[746]: Starting BAMF Application Matcher Framework...
Feb 18 17:32:33 rishab-pc lightdm[589]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Feb 18 17:32:33 rishab-pc unknown[2531]: cannot open display: :0
Feb 18 17:32:33 rishab-pc bamfdaemon[2531]: Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused
Feb 18 17:32:33 rishab-pc systemd[746]: bamfdaemon.service: Main process exited, code=exited, status=1/FAILURE
Feb 18 17:32:33 rishab-pc systemd[746]: bamfdaemon.service: Failed with result 'exit-code'.
Feb 18 17:32:33 rishab-pc systemd[746]: Failed to start BAMF Application Matcher Framework.

v4.14.20-2 continues to work for me. Also, I don’t appear to be using the synaptics driver:

$  hwinfo --mouse
35: PS/2 00.0: 10500 PS/2 Mouse                                 
  [Created at input.249]
  Unique ID: AH6Q.5+smWHVjPI3
  Hardware Class: mouse
  Model: "AlpsPS/2 ALPS DualPoint Stick"
  Vendor: 0x0002 
  Device: 0x0008 "AlpsPS/2 ALPS DualPoint Stick"
  Compatible to: int 0x0210 0x0003
  Device File: /dev/input/mice (/dev/input/mouse0)
  Device Files: /dev/input/mice, /dev/input/mouse0, /dev/input/event9, /dev/input/by-path/platform-i8042-serio-1-event-mouse, /dev/input/by-path/platform-i8042-serio-1-mouse
  Device Number: char 13:63 (char 13:32)
  Driver Info #0:
    Buttons: 3
    Wheels: 0
    XFree86 Protocol: explorerps/2
    GPM Protocol: exps2
  Config Status: cfg=new, avail=yes, need=no, active=unknown

36: PS/2 00.0: 10500 PS/2 Mouse
  [Created at input.249]
  Unique ID: AH6Q.5+smWHVjPI3
  Hardware Class: mouse
  Model: "AlpsPS/2 ALPS DualPoint TouchPad"
  Vendor: 0x0002 
  Device: 0x0008 "AlpsPS/2 ALPS DualPoint TouchPad"
  Compatible to: int 0x0210 0x0003
  Device File: /dev/input/mice (/dev/input/mouse1)
  Device Files: /dev/input/mice, /dev/input/mouse1, /dev/input/event10, /dev/input/by-path/platform-i8042-serio-1-event-mouse, /dev/input/by-path/platform-i8042-serio-1-mouse
  Device Number: char 13:63 (char 13:33)
  Driver Info #0:
    Buttons: 3
    Wheels: 0
    XFree86 Protocol: explorerps/2
    GPM Protocol: exps2
  Config Status: cfg=new, avail=yes, need=no, active=unknown

I also had random session restarts. I changed the kernel to 4.15, maybe it is related to that. I tried with 4.15.3 and 4.15.4 (because I have a cursor jittering problem solved with 4.15.4). Next time it crashes I go on the 4.14 branch again and will update about it, the problem is that crashes are sometimes happening after five minutes, sometimes after one hour.

Here are some entries of my journalctl:

févr. 18 12:40:57 valentin-pc systemd[1]: Started Process Core Dump (PID 6440/UID 0).
févr. 18 12:40:58 valentin-pc xfce4-notifyd[6017]: xfce4-notifyd: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.
févr. 18 12:40:58 valentin-pc systemd[800]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE
févr. 18 12:40:58 valentin-pc systemd[800]: xfce4-notifyd.service: Failed with result 'exit-code'.
févr. 18 12:40:58 valentin-pc at-spi-bus-launcher[884]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
févr. 18 12:40:58 valentin-pc at-spi-bus-launcher[884]:       after 865 requests (865 known processed) with 0 events remaining.
févr. 18 12:40:58 valentin-pc pulseaudio[5872]: XIO:  fatal IO error 11 (Ressource temporairement non disponible) on X server ":0.0"
févr. 18 12:40:58 valentin-pc pulseaudio[5872]:       after 12 requests (6 known processed) with 0 events remaining.
févr. 18 12:40:58 valentin-pc systemd[800]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE
févr. 18 12:40:58 valentin-pc systemd[800]: pulseaudio.service: Failed with result 'exit-code'.
févr. 18 12:40:59 valentin-pc systemd-coredump[6441]: Process 5880 (Xorg) of user 0 dumped core.
                                                       
                                                       Stack trace of thread 5902:
                                                       #0  0x00007f518fadf7ef n/a (libpixman-1.so.0)
                                                       #1  0x00007f518fac473b n/a (libpixman-1.so.0)
                                                       #2  0x00007f518fa7edf9 pixman_fill (libpixman-1.so.0)
                                                       #3  0x00007f518a686159 fbFill (libfb.so)
                                                       #4  0x00007f518a686994 fbPolyFillRect (libfb.so)
                                                       #5  0x00007f518a4596a7 n/a (libglamoregl.so)
                                                       #6  0x0000557b15445173 n/a (Xorg)
                                                       #7  0x00007f518aaef0be n/a (radeon_drv.so)
                                                       #8  0x00007f518aaec5ee n/a (radeon_drv.so)
                                                       #9  0x0000557b153b3fc6 n/a (Xorg)
                                                       #10 0x00007f518bc35d4d n/a (libglx.so)
                                                       #11 0x0000557b153a1705 AbortDDX (Xorg)
                                                       #12 0x0000557b154cb7e2 n/a (Xorg)
                                                       #13 0x0000557b154cc625 FatalError (Xorg)
                                                       #14 0x0000557b154c2dde n/a (Xorg)
                                                       #15 0x00007f518ea4edd0 __restore_rt (libpthread.so.0)
                                                       #16 0x00007f518e6ba860 raise (libc.so.6)
                                                       #17 0x00007f518e6bbec9 abort (libc.so.6)
                                                       #18 0x00007f518e6b30bc __assert_fail_base (libc.so.6)
                                                       #19 0x00007f518e6b3133 __assert_fail (libc.so.6)
                                                       #20 0x00007f51810c562e n/a (libinput.so.10)
                                                       #21 0x00007f51810c6298 n/a (libinput.so.10)
                                                       #22 0x00007f51810b2188 n/a (libinput.so.10)
                                                       #23 0x00007f51810b1a6f libinput_dispatch (libinput.so.10)
                                                       #24 0x00007f518131cc19 n/a (libinput_drv.so)
                                                       #25 0x0000557b154c1163 n/a (Xorg)
                                                       #26 0x0000557b154c3861 n/a (Xorg)
                                                       #27 0x0000557b154c0fae n/a (Xorg)
                                                       #28 0x00007f518ea4408c start_thread (libpthread.so.0)
                                                       #29 0x00007f518e77be7f __clone (libc.so.6)
                                                       
                                                       Stack trace of thread 5898:
                                                       #0  0x00007f518ea4a3bd pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                                                       #1  0x00007f5188acffbc n/a (r600_dri.so)
                                                       #2  0x00007f5188acfec8 n/a (r600_dri.so)
                                                       #3  0x00007f518ea4408c start_thread (libpthread.so.0)
                                                       #4  0x00007f518e77be7f __clone (libc.so.6)
                                                       
                                                       Stack trace of thread 5899:
                                                       #0  0x00007f518ea4a3bd pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                                                       #1  0x00007f5188acffbc n/a (r600_dri.so)
                                                       #2  0x00007f5188acfec8 n/a (r600_dri.so)
                                                       #3  0x00007f518ea4408c start_thread (libpthread.so.0)
                                                       #4  0x00007f518e77be7f __clone (libc.so.6)
                                                       
                                                       Stack trace of thread 5880:
                                                       #0  0x00007f518e77bfe6 epoll_pwait (libc.so.6)
                                                       #1  0x0000557b154c3817 n/a (Xorg)
                                                       #2  0x0000557b154bc70b WaitForSomething (Xorg)
                                                       #3  0x0000557b1535cfc3 n/a (Xorg)
                                                       #4  0x0000557b15361260 n/a (Xorg)
                                                       #5  0x00007f518e6a6f4a __libc_start_main (libc.so.6)
                                                       #6  0x0000557b1534af0a _start (Xorg)

Edit: It crashed again on kernel 4.14.19, I try downgrading libinput to 1.9.4, I hope it is not linked to xorgproto which seemed to change a lot of packages. Also, the cursor jitter was solved with kernel 4.15.4, or by downgrading libinput to 1.9.4, good to know :wink:

2 Likes

sudo pacman -Qs libvpx
local/libvpx 1.7.0-1
VP8 and VP9 codec

with those commands my problem is gonne.

1 Like

Thank you very much, friend. My problem is solved thanks to you.

Update went fine. Then I tried (I was very curious) the new “stable” KDE Wayland integration, started the Plasma Wayland session and I have the mouse cursor with different sizes depending on the application.
If I’m using a Gtk application the size is ok, if I move over the window border or the title bar of a window the size is ok, but if I move the mouse over the plasma components or I open a Qt/KDE application the mouse size doubles, but only when I stay over the window content.
If the mouse hovers the desktop background the mouse pointer is double sized… really don’t know how to fix this…

EDIT:
I found a fix: in System Settings go to “Workspace theme” (don’t know if it’s the right naming, I’m using my system in Italian language), then “Pointer theme”, at the lower right corner there’s a combo in which you can enter the mouse size: change from “Resolution dependent” to the size you want.

1 Like

When I turn on the pc everything goes normal until logon screen, the first time I write my password and hit enter the logon box dissapears but nothing happens, I need to press ctrl+alt+del (don’t know if its good as I’m still a newbie ) for the screen go black, then reappears the logon screen and I can login normally.

When using Opera (last version) the mouse have lag sometimes, when opening tabs (just 2-3) or watching youtube with maximized browser.

terminal

I’m using the Nvidia drivers (latest)

update OK. xps9550, KDE, kernel 44

I had the unmounting issue, but the udiskie workaround did not worked… not a big deal, but i’d like to solve without manually intervention.

Error message:

Error response from daemon: container "<CONTAINERID>": already exists

If you encounter this error with Docker (v 18.02) not bringing up your container, you can fix it by this command:

sudo docker-containerd-ctr --address /run/docker/containerd/docker-containerd.sock --namespace moby c rm <CONTAINERID>

For more info, consult this thread: https://github.com/docker/for-linux/issues/211

cpuguy83 commented 6 days ago

Closing since this issue will be resolved in 18.03. 18.02 is the only affected version as far as I can tell.
Sorry we didn’t track this down in time for the 18.02 GA :cry: .

Kernel 4.15 and 4.14 keep eating my cpu.
Running this guys = cpu usage 90-100% all the time. Even right after boot
kernel 4.9 runs ok

Cpu: Intel core 2 duo 2.1GHz T6500

Hi,
I tried the update in testing (VBox) and the update fails on libre office, something on a corrupted package.
Mirors have been updated several times already.
There is quite some “proto” being replaced, is that normal?
Thanks
Melissa
Edit - the unstable does take all the packages in…
Edit 2 - I did a dry-run in the real system, all packages are ready to be fetched, only the test system fails at fetching Libre…I’ll look into that, something new to learn! Woohoo! :smile_cat: