[Stable Update] 2018-04-28 - Kernels, Cinnamon, Browsers, Mesa, KDE Apps, KDE Framework, Virtualbox

Hi,

Can be a poltergeist? :scream:

1 Like

The proprietary drivers doesn't stay in a working condition

I install video-hybrid-intel-nvidia-bumblebee from system settings - Hardware Configuration
I reboot and the driver is there and working.

I shutdown and boot the driver is, well not really gone, but not working.
I have to uninstall the driver, shutdown, boot, install, shutdown and boot to make them work one more time.
Shutdown is needed it seems. A reboot seems not to install the driver in a working condition.
I have to do this on two laptops. The error is there with kernel 4.14 and 4.16.
I don't know if the error was the before this update.

Anyone else have this problem?

Driver installed and working
inxi without primusrun:
Graphics: Card-1:
Intel HD Graphics 620 driver: i915 v: kernel
Card-2: NVIDIA GM108M [GeForce 940MX] driver: N/A
Display: x11 server: X.Org 1.19.6 driver: intel resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 620 (Kaby Lake GT2) v: 4.5 Mesa 18.0.1

inxi with primusrun:
Graphics:
Card-1: Intel HD Graphics 620 driver: i915 v: kernel
Card-2: NVIDIA GM108M [GeForce 940MX] driver: N/A
Display: x11 server: X.Org 1.19.6 driver: intel resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce 940MX/PCIe/SSE2 v: 4.6.0 NVIDIA 390.48

Driver not working
inxi without primusrun:
Graphics:
Card-1: Intel HD Graphics 620 driver: i915 v: kernel
Card-2: NVIDIA GM108M [GeForce 940MX] driver: nvidia v: 390.48
Display: x11 server: X.Org 1.19.6 driver: intel resolution: 1920x1080~60Hz
OpenGL: renderer: N/A v: N/A

inxi with primusrun:
sh: line 1: 2582 Segmentation fault (core dumped) /sbin/glxinfo 2> /dev/null
Graphics:
Card-1: Intel HD Graphics 620 driver: i915 v: kernel
Card-2: NVIDIA GM108M [GeForce 940MX] driver: nvidia v: 390.48
Display: x11 server: X.Org 1.19.6 driver: intel resolution: 1920x1080~60Hz
Message: No advanced graphics data found on this system.

From konsole when starting steam:
optirun /usr/bin/flatpak run --branch=stable --arch=x86_64 --command=/app/bin/steam-wrapper --file-forwarding com.valvesoftware.Steam @@u %U @@
Couldn't find dpkg, please update steamdeps for your distribution.
Running Steam on org.freedesktop.platform 1.6 64-bit
STEAM_RUNTIME is enabled automatically
Pins up-to-date!
Installing breakpad exception handler for appid(steam)/version(1522709999)
Installing breakpad exception handler for appid(steam)/version(1522709999)
Installing breakpad exception handler for appid(steam)/version(1522709999)
OpenGL GLX extension not supported by displayMain.cpp (323) : Assertion Failed: Fatal Error: OpenGL GLX extension not supported by display
Assert( Assertion Failed: Fatal Error: OpenGL GLX extension not supported by display ):Main.cpp:323

Installing breakpad exception handler for appid(steam)/version(1522709999)
assert_20180506103129_5.dmp[130]: Uploading dump (out-of-process)
/tmp/dumps/assert_20180506103129_5.dmp
assert_20180506103129_5.dmp[130]: Finished uploading minidump (out-of-process): success = no
assert_20180506103129_5.dmp[130]: error: Couldn't connect to server
assert_20180506103129_5.dmp[130]: file ''/tmp/dumps/assert_20180506103129_5.dmp'', upload no: ''Couldn't connect to server''

I think I was able to fix the slick-greeter background issues by patching both lightdm-settings and lightdm-slick-greeter packages. The updated versions will arrive with next stable update.

For now, try adding this line in your /etc/lightdm/slick-greeter.conf:

draw-user-backgrounds=false

Does that help to display your configured background?

1 Like

JFYI: KDE:
Update went fine with kernel 4.9.

kernel 4.14.36-1 is now working on my T60 Intel T5500, (which did previously not ).
There was only a long boot delay at black boot screen on the first reboot after kernel upgrade from 4.9 to 4.14.
Thanks.

Machine:   Type: Laptop System: LENOVO product: 1952VA4 v: ThinkPad T60 serial: N/A 
           Mobo: LENOVO model: 1952VA4 serial: N/A BIOS: LENOVO v: 79ETE6WW (2.26 ) date: 04/01/2010 
Battery:   ID-1: BAT0 charge: 36.5 Wh condition: 36.5/47.5 Wh (77%) model: SANYO 93P5030 status: Unknown 
CPU:       Topology: Dual Core model: Intel Core2 T5500 bits: 64 type: MCP arch: Conroe rev: 6 
           L2 cache: 2048 KiB 
           flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 6652 
           Speed: 1045 MHz min/max: 1000/1667 MHz Core speeds (MHz): 1: 1057 2: 1015 
Graphics:  Card-1: Intel Mobile 945GM/GMS 943/940GML Express Integrated Graphics driver: i915 v: kernel 
           bus ID: 00:02.0 
           Display: x11 server: X.Org 1.19.6 driver: intel unloaded: fbdev,modesetting,vesa tty: N/A 
           OpenGL: renderer: Mesa DRI Intel 945GM v: 1.4 Mesa 18.0.1 direct render: Yes 
. . . 
Info:      Processes: 150 Uptime: 1m Memory: 1.94 GiB used: 1006.9 MiB (50.6%) Init: systemd Compilers: 
           gcc: 7.3.1 Shell: bash v: 4.4.19 inxi: 3.0.07 
[yankee@T60small64bit ~]$ uname -a
Linux T60small64bit 4.14.36-1-MANJARO #1 SMP PREEMPT Tue Apr 24 19:16:26 UTC 2018 x86_64 GNU/Linux



Fixed with today's stable update. Thanks.

1 Like

Oh nooooooooooo, it happened again overnight - identical symptoms. 100% certain that Tower was Suspended late last night, but this morning it was already running again... Not Good [apart from just being plain wrong in principle for Suspend to fail, it's dangerous... i cover Tower each night with a dust cloth, thus it cannot properly draw cooling air if it runs like that].

Today i will be applying the 20180507 Stable Update to it, so i really hope that solves this.

Which kernel are you using? Which hardware?
In any case. Try a different kernel if possible.

Currently:

$ inxi -Fxz
System:    Host: GA-Z97-HD3-Tower Kernel: 4.16.4-1-MANJARO x86_64 bits: 64 compiler: gcc v: 7.3.1 
           Desktop: KDE Plasma 5.12.4 tk: Qt 5.10.1 Distro: Manjaro Linux 17.1.9 Hakoila 
Machine:   Type: Desktop Mobo: Gigabyte model: Z97-HD3 v: x.x serial: N/A UEFI: American Megatrends v: F7 
           date: 12/08/2014 
CPU:       Topology: Quad Core model: Intel Core i7-4790 bits: 64 type: MT MCP arch: Haswell rev: 3 
           L2 cache: 8192 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 57606 
           Speed: 3514 MHz min/max: 800/4000 MHz Core speeds (MHz): 1: 3514 2: 3223 3: 3388 4: 3319 5: 3273 
           6: 3285 7: 3169 8: 3683 
Graphics:  Card-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel 
           bus ID: 00:02.0 
           Display: x11 server: X.Org 1.19.6 driver: intel unloaded: fbdev,modesetting,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 18.0.1 direct render: Yes 
Audio:     Card-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel v: kernel 
           bus ID: 00:03.0 
           Card-2: Intel 9 Series Family HD Audio driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
           Sound Server: ALSA v: k4.16.4-1-MANJARO 
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8168 v: 8.045.08-NAPI 
           port: e000 bus ID: 02:00.0 
           IF: enp2s0 state: up speed: 100 Mbps duplex: half mac: <filter> 
           IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
Drives:    HDD Total Size: 2.05 TiB used: 1.10 TiB (54.0%) 
           ID-1: /dev/sda model: Samsung_SSD_850 size: 232.89 GiB 
           ID-2: /dev/sdb model: ST2000DM001-1ER1 size: 1.82 TiB 
Partition: ID-1: / size: 58.81 GiB used: 23.13 GiB (39.3%) fs: ext4 dev: /dev/sda2 
           ID-2: /home size: 158.46 GiB used: 31.17 GiB (19.7%) fs: ext4 dev: /dev/dm-1 
           ID-3: swap-1 size: 2.01 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-0 
Sensors:   System Temperatures: cpu: 29.8 C mobo: 27.8 C 
           Fan Speeds (RPM): cpu: 670 fan-1: 1027 fan-3: 0 fan-4: 0 fan-5: 0 
Info:      Processes: 444 Uptime: 1d 11h 45m Memory: 30.85 GiB used: 11.61 GiB (37.6%) Init: systemd Compilers: 
           gcc: 7.3.1 Shell: bash v: 4.4.19 inxi: 3.0.07 

...but the 20180507 Stable Update is in the late download phase right now, so pretty soon after rebooting it will be Plasma 5.12.5 & Kernel 4.16.7, etc.

...Aha, it's just finished, will be rebooting after posting this, so once i go to bed later tonight my Tower will be suspended in this new state. I shall be interested to see Tower's power status tomorrow morning... hopefully it will still be asleep.

Just don't wrap it up ... :wink:
If you still have issues with suspend try the latest LTS kernel linux414 instead.

My issue seems to be gone with 05/07/2018 update. The issue was this error when update-grub ran:

Failure to communicate with kernel device-mapper driver.
Check that device-mapper is available in the kernel.
Incompatible libdevmapper 1.02.146 (2017-12-18) and kernel driver (unknown version).
Command failed
/dev/mapper/control: open failed: No such device

in spite of the error message I noticed no loss of system functionality. And now the error message it self is gone so many thanks to Manjaro Team.

Tower was still sound asleep this morning when i dragged it out of bed & threw it into a cold shower to wake up.

Obviously that's nice, but is far from conclusive, given that there were only two instances of The Poltergeist when Tower still wore Stable 20180428 Clothes. I want to see many more consecutive days in its new Stable 20180507 Clothes sans poltergeist, before i'll feel comfortable that the bug has gone.

1 Like

Things go bump in the night if I'm to understand correctly?... Yikes! :laughing:

Ha yes, apparently so.

Two more mornings with Tower still asleep, but this morning's one probably does not count; last night for reasons unrelated* to The Poltergeist, i decided to reboot Tower from kernel 4.16.x back down to 4.9.x.

* It's off-topic for matters poltergeisty, but fyi as to why i downgraded my kernel last night:

  1. For a long time [several months] Tower has randomly, infrequently, irregularly misbehaved wrt running programs suddenly malfunctioning, & closed programs refusing to launch. The common link is that i run lots of my programs in Firejail, & each time these wobblies occurred though i could generally [but not always] close the defective programs' UIs, they refused to close in Firejail too [FireTools continues to list them], hence could not be killed in KSysGuard either [zombies frequently occur]. Each time a reboot is needed, & sometimes actually a REISUB.

  2. i have a growing suspicion that the culprit for my random Tower wobblies might be that Firejail is incompatible with contemporary kernels [over the past few months i was using 4.15.x & then 4.16.x]. FJ Stable [mine = 0.9.52-1] has not been updated by its Dev for a quite long time [Thu, 7 Dec 2017], so it seems plausible to me that it might not have been able to be tested by its Dev on the later kernels, & there might thus be a mismatch. When i have done extended tests [1 - 2 weeks] running my programs "naked" [no FJ], no wobblies occurred, but i do prefer to use FJ. Hence my decision to downgrade to the older 4.9.x LTS kernel, which i assume should have been proven compatible with current FJ version [???]. If Tower runs for a couple of weeks like this, sans wobblies, then i might cautiously try kernel 4.14.x LTS, but otherwise i guess i'd have to stay on 4.9.x at least until a new FJ is released.

  3. Who knows, maybe the older kernel might also possess potent anti-poltergeist magic?

1 Like

I think your tower is possessed, or you could possibly have a Microsoft Ciippy Gremlin infestation. Either way you might have to seek professional help on this one. Hopefully it's only a M$ Clippy Gremlin, as exterminators are way easier to come by than an exorcist. :smile:

4 Likes

You know, you might well be onto something here. I had been wondering why sometimes when i walked into my Study i saw the Tower levitating above the desk, & sometimes it turned green & warty, its head rotated, & on especially bad days it projectile vomited. Am just going online now to look up Max von Sydow's phone number...

Hey, want me to attach a pic? Muhahahaha teehee.

1 Like

If your home folders permissions switched to 666, definitely go the exorcist route. That's a dead giveaway. Of course the other stuff you listed is pretty symptomatic too.

1 Like

Cor blimey yeah, that's a dead cert ain't it? Checking it out right now...

1 Like

In these extreme cases some visual evidence would definitely go a long ways in narrowing down the cause.

1 Like

OK, i hereby make you this solemn promise. The very instant i next catch my Tower levitating, i shall snap a pic & upload it here. After all, if i merely described it simply in words alone, who would believe me? Some might even think me bonkers!

2 Likes

These manifestations are definitely un-earthly and, to quote, tbg, very similair to a "Microsoft Ciippy Gremlin Infestation"...! :laughing:

I'd similair manifestations i.e my Windows 10 PC-tower waking up in the middle of the night and doing its thing(amongst other things!)... :wink: Then, one day, enough was enough: I booted out PC-tower, got hold of a purpsose-built PC installed a Linux distro(my very first) which was the end of all that poltergeist thingy... And, all that without calling in The Ghostbusters and wrecking my place. :grin:

2 Likes

Forum kindly sponsored by