Latest status of the testing repository [08 Jan 2018 - 16 Jan 2018]


(Neofytos Kolokotronis) #1

Hi testers,

As of now you’ll find available in testing kernel updates to linux 4.14.2 and linux-lts 4.4.110 which tackle the recently discovered Meltdown and Spectre vulnerabilities regarding Intel’s CPUs.

The nvidia graphics drivers were also updated to 387.34.

Hopefully this makes you feel a bit more secure. :slight_smile:


(tom) #3

i cant start qupzilla

[tom@frija ~]$ LC_ALL=C qupzilla
[0109/095816.620254:WARNING:stack_trace_posix.cc(648)] Failed to open file: /home/tom/#53705 (deleted)
  Error: No such file or directory
[1141:1163:0109/095816.675640:ERROR:gl_implementation.cc(246)] Failed to load /usr/bin/libGLESv2.so: /usr/bin/libGLESv2.so: cannot open shared object file: No such file or directory
propsReply "Method \"GetAll\" with signature \"s\" on interface \"org.freedesktop.DBus.Properties\" doesn't exist\n"
nmReply "Method \"GetDevices\" with signature \"\" on interface \"org.freedesktop.NetworkManager\" doesn't exist\n"
"Object path cannot be empty"
[1141:1163:0109/095817.039475:ERROR:gl_surface_qt.cpp(701)] Requested OpenGL implementation is not supported. Implementation: 0
Received signal 11 SEGV_MAPERR 000000000000
#0 0x7f81ad8d58c6 <unknown>
#1 0x7f81ac5f14c1 <unknown>
#2 0x7f81ad8d5c6d <unknown>
#3 0x7f81b30f5a90 <unknown>
#4 0x7f81ac6347d4 <unknown>
#5 0x7f81ac635838 <unknown>
#6 0x7f81ae362404 <unknown>
#7 0x7f81ae36f6d4 <unknown>
#8 0x7f81ae37221b <unknown>
#9 0x7f81ae37341f <unknown>
#10 0x7f81ae36cf4c <unknown>
#11 0x7f81ae36d47c <unknown>
#12 0x7f81ae36c5b0 <unknown>
#13 0x7f81ae36e9a5 <unknown>
#14 0x7f81ad9587a9 <unknown>
#15 0x7f81ad8f1e48 <unknown>
#16 0x7f81ad8f353f <unknown>
#17 0x7f81ad8f3a8b <unknown>
#18 0x7f81ad8f4939 <unknown>
#19 0x7f81ad9122fa <unknown>
#20 0x7f81ad92d3b7 <unknown>
#21 0x7f81ad928a82 <unknown>
#22 0x7f81ab1802e7 start_thread
#23 0x7f81b31ae54f __GI___clone
  r8: 0000000000000003  r9: 0000000000000050 r10: 0000000000012c40 r11: 0000000000000000
 r12: 0000000000000000 r13: 00007f8156ffbee0 r14: 00007f8156ffbe90 r15: 00007f812800e140
  di: 0000000000000000  si: 0000000000000000  bp: 00007f8156ffbc90  bx: 00007f812800e140
  dx: 0000000000000000  ax: 00007f81b2922c68  cx: 00007f8156ffbab0  sp: 00007f8156ffbab0
  ip: 00007f81ac6347d4 efl: 0000000000010246 cgf: 002b000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
Calling _exit(1). Core file will not be generated.

from my Xorg.0.log

[     6.274] (--) RandR disabled
[     6.284] (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/i965_dri.so failed (/usr/lib/xorg/modules/dri/i965_dri.so: cannot open shared object file: No such file or directory)
[     6.284] (EE) AIGLX: reverting to software rendering
[     6.284] (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/swrast_dri.so failed (/usr/lib/xorg/modules/dri/swrast_dri.so: cannot open shared object file: No such file or directory)
[     6.284] (EE) GLX: could not load software renderer
[     6.284] (II) GLX: no usable GL providers found for screen 0

from my Xorg.1.log

[     2.811] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
...
[     5.032] (EE) intel(0): [drm] failed to set drm interface version: Permission denied [13].
…
[     5.032] (EE) intel(0): Failed to claim DRM device.
[     5.032] (II) UnloadModule: "intel"
[     5.032] (EE) Screen(s) found, but none have a usable configuration.
[     5.032] (EE) 
Fatal server error:
[     5.032] (EE) no screens found(EE) 
[     5.032] (EE) 
Please consult the The X.Org Foundation support 
     at http://wiki.x.org
 for help. 
[     5.032] (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information.
[     5.032] (EE) 
[     5.053] (EE) Server terminated with error (1). Closing log file.

my 20-intel.conf

Section "Device"
   Identifier  "Intel Graphics"
   Driver      "intel"
   Option      "DRI"          "3"
   Option      "DRI"          "true"
   Option      "TearFree"     "true"
   Option      "AccelMethod"  "sna"
EndSection

edit: the cause for the problem is mesa


Kwin fails to initialize, black screen with cursor
(Neofytos Kolokotronis) #4

I can replicate this error.

KMail also fails for me, with similar output:

tetris4@lappy ~]$ kmail 
Error loading text-to-speech plug-in "flite"
[0109/142244.995851:WARNING:stack_trace_posix.cc(648)] Failed to open file: /home/tetris4/#1598777 (deleted)
  Error: No such file or directory
[18494:18523:0109/142245.087051:ERROR:gl_implementation.cc(246)] Failed to load /usr/bin/libGLESv2.so: /usr/bin/libGLESv2.so: cannot open shared object file: No such file or directory
[18494:18523:0109/142245.850649:ERROR:gl_surface_qt.cpp(701)] Requested OpenGL implementation is not supported. Implementation: 0
Received signal 11 SEGV_MAPERR 000000000000
#0 0x7f1e72e938c6 <unknown>
#1 0x7f1e71baf4c1 <unknown>
#2 0x7f1e72e93c6d <unknown>
#3 0x7f1e88e5da90 <unknown>
#4 0x7f1e71bf27d4 <unknown>
#5 0x7f1e71bf3838 <unknown>
#6 0x7f1e73920404 <unknown>
#7 0x7f1e7392d6d4 <unknown>
#8 0x7f1e7393021b <unknown>
#9 0x7f1e7393141f <unknown>
#10 0x7f1e7392af4c <unknown>
#11 0x7f1e7392b47c <unknown>
#12 0x7f1e7392a5b0 <unknown>
#13 0x7f1e7392c9a5 <unknown>
#14 0x7f1e72f167a9 <unknown>
#15 0x7f1e72eafe48 <unknown>
#16 0x7f1e72eb153f <unknown>
#17 0x7f1e72eb1a8b <unknown>
#18 0x7f1e72eb2939 <unknown>
#19 0x7f1e72ed02fa <unknown>
#20 0x7f1e72eeb3b7 <unknown>
#21 0x7f1e72ee6a82 <unknown>
#22 0x7f1e7f2e42e7 start_thread
#23 0x7f1e88f1654f __GI___clone
  r8: 0000000000000003  r9: 0000000000000050 r10: 0000000000012e90 r11: 0000000000000000
 r12: 0000000000000000 r13: 00007f1e057f8ea0 r14: 00007f1e057f8e50 r15: 00007f1dec00def0
  di: 0000000000000000  si: 0000000000000000  bp: 00007f1e057f8c50  bx: 00007f1dec00def0
  dx: 0000000000000000  ax: 00007f1e77ee0c68  cx: 00007f1e057f8a70  sp: 00007f1e057f8a70
  ip: 00007f1e71bf27d4 efl: 0000000000010246 cgf: 002b000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
Calling _exit(1). Core file will not be generated.

Update of mesa from 17.1.5-1 to 17.3.1-1 and of xorg from 1.19.5-1 to 1.19.5-2 leaves me without login screen
(tom) #5

i discovered a other problem

[tom@frija ~]$ journalctl -p err | grep sddm
[    6.375317] frija sddm-greeter[357]: Could not connect to any X display.
[tom@frija ~]$ journalctl | grep sddm-greeter
[    6.286433] frija sddm-helper[313]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
[    6.341211] frija sddm-greeter[357]: High-DPI autoscaling not Enabled
[    6.375239] frija sddm-greeter[357]: QXcbConnection: Could not connect to display
[    6.375317] frija sddm-greeter[357]: Could not connect to any X display.
[    6.797964] frija sddm-helper[380]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
[    6.883237] frija sddm-greeter[389]: High-DPI autoscaling not Enabled
[    6.904314] frija sddm-greeter[389]: Loading theme configuration from "/usr/share/sddm/themes/heritage/theme.conf"
[    6.904616] frija sddm-greeter[389]: Reading from "/usr/share/xsessions/plasma.desktop"
[    6.904936] frija sddm-greeter[389]: Reading from "/usr/share/xsessions/systemd.desktop"
[    6.905495] frija sddm-greeter[389]: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop"
[    6.906920] frija sddm-greeter[389]: Connected to the daemon.
[    6.961824] frija sddm-greeter[389]: Loading file:///usr/share/sddm/themes/heritage/Main.qml...
[    7.097915] frija sddm-greeter[389]: QObject: Cannot create children for a parent that is in a different thread.
[    7.098047] frija sddm-greeter[389]: QObject: Cannot create children for a parent that is in a different thread.
[    7.098177] frija sddm-greeter[389]: QObject: Cannot create children for a parent that is in a different thread.
[    7.100957] frija sddm-greeter[389]: QObject: Cannot create children for a parent that is in a different thread.
[    7.101007] frija sddm-greeter[389]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
[    7.102418] frija sddm-greeter[389]: QObject: Cannot create children for a parent that is in a different thread.
[    7.324090] frija sddm-greeter[389]: QObject: Cannot create children for a parent that is in a different thread.
[    7.324208] frija sddm-greeter[389]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
[    7.390839] frija sddm-greeter[389]: Cannot watch QRC-like path ":/icons/hicolor/index.theme"
[    7.487953] frija sddm-greeter[389]: QObject::connect: No such signal QDBusAbstractInterface::DeviceAdded(QString)
[    7.488007] frija sddm-greeter[389]: QObject::connect: No such signal QDBusAbstractInterface::DeviceRemoved(QString)
[    7.506153] frija sddm-greeter[389]: virtual QStringList Solid::Backends::UPower::UPowerManager::allDevices()  error:  "org.freedesktop.systemd1.UnitMasked"
[    7.770321] frija sddm-greeter[389]: file:///usr/share/sddm/themes/heritage/components/Battery.qml:39:18: Unable to assign [undefined] to int
[    7.770461] frija sddm-greeter[389]: Adding view for "LVDS1" QRect(0,0 1366x768)
[    7.785381] frija sddm-greeter[389]: Message received from daemon: Capabilities
[    7.785483] frija sddm-greeter[389]: Message received from daemon: HostName
[   11.835559] frija sddm-greeter[389]: UdevQt: unhandled device action "bind"
[   11.837217] frija sddm-greeter[389]: UdevQt: unhandled device action "bind"
[   18.256690] frija sddm-greeter[389]: Reading from "/usr/share/xsessions/plasma.desktop"
[   18.274138] frija sddm-greeter[389]: Message received from daemon: LoginSucceeded
[   18.390558] frija sddm-helper[380]: pam_unix(sddm-greeter:session): session closed for user sddm

edit: to days upgrade solves this problem

[2018-01-10 08:55] [ALPM] upgraded mesa (17.1.5-1 -> 17.3.1-1)
[2018-01-10 08:55] [ALPM] upgraded xorg-server-common (1.19.5-1 -> 1.19.5-2)
[2018-01-10 08:55] [ALPM] upgraded xorg-server (1.19.5-1 -> 1.19.5-2)
[2018-01-10 08:55] [ALPM] upgraded xorg-server-xwayland (1.19.5-1 -> 1.19.5-2)

(Neofytos Kolokotronis) #6

There was an ugly issue with xorg-server, it had to be rebuilt against mesa.
I can confirm both kmail and qupzilla issues are fixed for me.


(Knut Hildebrandt) #7

@tetris4 Does that mean that after updating xorg etc. I can update mesa etc. too without running again into the problems with kmail, kontact etc.?


(Neofytos Kolokotronis) #8

Exactly, it should be safe to upgrade now.


(Knut Hildebrandt) #9

is it not. First I only updated xorg and ran into the problems with kontact and kmail again. Then I updated the mesa packages too which rendered me with a black screen. Even though the curser was visible the login screen did not show up. Now I’m back to the old versions.

Any suggestions? And is it possible that the failure is due to the fact, that I did not update the nvidia drivers too? BTW, do you need more information from my side?


(serafean) #11

21:35 CET, kmail fails.

missing /usr/bin/libGLESv2.so
Why it’s looking into /usr/bin instead of /usr/lib (where the file exists) is beyond me…
Also why can’t I link to paste.kde.org from the new post form? (https://paste.kde.org/prdxhfaif)


(tom) #12

upgrade booth package at once?

65bits are very difficult to handle… :stuck_out_tongue:
on my i have an old core2 and in the sometimes the same problem and up to now i was not able to discover why it freezes.
a view weeks ago i installed chakra again on a ssd and i don’t noticed this problem perhaps it will occur again by more use …
i am using the 20-intel.conf from my main machine.

 [tom@frija ~]$ cat /etc/X11/xorg.conf.d/20-intel.conf 
Section "Device"
   Identifier  "Intel Graphics"
   Driver      "intel"
   Option      "DRI"          "3"
   Option      "DRI"          "true"
   Option      "TearFree"     "true"
   Option      "AccelMethod"  "sna"
EndSection

https://wiki.archlinux.org/index.php/I915#OpenGL_2.1_with_i915_driver


(Knut Hildebrandt) #13

first I updated mesa and ran into the problem with kontact and thus downgraded again. Then I updated (only) the xorg stuff and ran into the same problem. After that I updated the mesa stuff again and ended up with the black login screen. Then I downgraded all five packages in the rescue mode and now I’m back to the old versions.

I have a quad core i5, of course 64 bits. Would be interesting to see how 65 works :joy:

Anyhow, was this part of your post meant as an answer to my question in the other thread? Is that the route I have to take to solve my freezing problem without compromising the graphics system?


(dinolib) #14

I just updated and reboot.
Now I’m not able to start vbox machine anymore.

Trying #dkms autoinstall to fix it as usual I get:

Error! Could not locate dkms.conf file.
File:  does not exist.

Reinstalling virtualbox-host-dkms package brings at the same error.

EDIT: fixed this error manually removing the old modules

$ for i in /var/lib/dkms/*/[^k]*/source; do [ -e "$i" ] || echo "$i";done
/var/lib/dkms/vboxhost/5.2.0_OSE/source

$ sudo rm /var/lib/dkms/vboxhost/5.2.0_OSE/source

# dkms autoinstall 
# vboxreload

Failed to Load Kernel Modules + Failed to Mount /boot/efi
(Neofytos Kolokotronis) #15

@king.knut
In Chakra partial updates are not supported. To properly test this you should perform a full system upgrade (sudo pacman -Syu) and then reboot. If your system still fails, then we need to further troubleshoot this.
If it fails, please provide the package versions you had installed that cause the issue and the ones that work for you.

@serafean
Can you please also share the mesa and xorg versions you have installed?

The latest available versions are:

core/mesa 17.3.1-1
core/xorg-server 1.19.5-2

(tom) #16

my answer was dedicated to the other thread and perhaps is are my hint helpful.
a other thought: disable graphical effect because openGL could be difficult to older graphical units… the effects on my notebook are disabled


(Knut Hildebrandt) #17

My system is up-to-date, except for firefox (56.0.2-1) all mesa stuff (17.1.5-1) and the xorg stuff (1.19.5-1). The versions I tried are the ones you mentioned in your reply. Furthermore I updated mesa and xorg again to the new versions after updating the kernel to 4.14.12 and all packages that depend on it. Same result, instead of a login screen a black screen with mouse curser. If I’m not mistaken I had had the same problem when first making that big update in October. It had to do with the nvidia graphics driver, but I don’t remember how I solved it.

thanks again for the hint, but I solved the problem without changing my graphics settings. An update to kernel 4.14.12 brought the solution. Have a look at the other thread:

Anyhow, it seems that the complexity of dependencies between kernel, xorg, mesa and custom graphics drivers are a source for a lot of frustration. I thought the times that one has to change a bunch of conf files with every update are over. At least they were over for me for years. And all of a sudden, with the arrival of kernel 4.1x and the changes in graphics system they seem to be back. What a pity.


(tom) #18

have you the same behaviour with a other plasma distro like debian/kubunt or suse?

how to delete a wrong and misleading post?


(Knut Hildebrandt) #19

no clue what happens in other distros. I’ve only got Chakra on my laptop. And until this big update in October everything worked out fine for me. Sometimes there were minor problems with bluetooth for instance, but hardware recognition and support generally worked great and got even better over the years. BTW, who is responsible for that? Does the kernel recognize the hardware and selects the correct modules or is that something that has to be done by the packager?


(tom) #20

udev load the kernel modules with default configuration.
you can influence this system by using kcmd options and .conf files in /etc.

please change to a tty and run “lsmod” ot check if all modules are properly loaded when this happen next time

systemctl --failed
journalctl -p err
lsmod

(Knut Hildebrandt) #21

Once again I tries to update all xorg and mesa stuff to the latest version. And the update left me with an unusable windows system again. After the update I could neither logout nor shutdown from within Plasma. I had to change to another TTY (CTRL-ALT-F2) and invoke shutdown now. But it came worse. After reboot there was no login screen any more, only the mouse curser on a black screen. I changed to another TTY again and downgraded the graphics stuff. But before I ran the commands @brikler recommended. How shall I post the output? As hidden details?

These are the packages in question:

lib32/lib32-mesa 17.1.5-1 -> 17.3.1-1
core/mesa 17.1.5-1 -> 17.3.1-1
core/xorg-server 1.19.5-1 -> 1.19.5-2
core/xorg-server-common 1.19.5-1 -> 1.19.5-2
core/xorg-server-xwayland 1.19.5-1 -> 1.19.5-2

The old versions work, with the new ones the window system is broken.


Update of mesa from 17.1.5-1 to 17.3.1-1 and of xorg from 1.19.5-1 to 1.19.5-2 leaves me without login screen
(tom) #22

make the output persistent and then can you downgrade if you want

systemctl --failed > failedServices
journalctl -p err > errorsJournal

a idea to get a workable state: blacklist the nvidia module and reboot

#/etc/modprobe.de/blacklist.conf
blacklist <modulName>

open a new thread please