[spiff]

yes and yes.

[spiff]

sorry i cannot really install stuff on the box i develop on. so i build everything myself. i'll try to install debs stuff on my laptop once i have it and recall this and yes, i have tested with the very latest, it works fine. i do get the same noise in the log, i haven't tried to fix that yet, but it works fine.

[User 29008]

Hey @spiff , so I guess projectm is still working for you with current Leia nightlies? Just tried again today, with a complete fresh install of Kodi on Lubuntu 18.04.1. Still getting the same errors in log. Kodi seems to try to go fullscreen for vis on playing music, but hangs for a while and then restarts itself can post a link to log later, but pretty much looking similiar to what I posted above.

[3dfx]

I have the same issue on Ubuntu 18.04 with Leia beta 2.
Also the errors that you posted end of July. Screen stays black an Kodi crashes.
I tried to compile it myself but with no luck

[User 29008]

Weird that it works for you @wsnipex  .... I set up my own build env a couple of days ago and am following the kodi build guide exactly:

https://github.com/xbmc/xbmc/blob/master...E.Linux.md

It does build projectm, I can select it in kodi, but either nothing happens -> black screen, or kodi crashes with latest leia nightlies. Only vis I can get to work right now is spectrum.

[wsnipex]

nothing changed, it doesn't work for me either. No viz showing up

[spiff]

an educated guess; it works with the old GL profile, but does not work the >= 3.2 profile. so it will depend on your gl drivers etc etc.

[User 29008]

an educated guess; it works with the old GL profile, but does not work the >= 3.2 profile. so it will depend on your gl drivers etc etc.

Any plans on making the visualizations compatible with the newer profiles and thus Leie on a current Ubuntu system? ;-)

[spiff]

it would big surgery on a upstream library - not something i really have on my todo, no.

[User 29008]

So basically you are saying ... no vis in an Ubuntu 18.04.1 environment, which comes with opengl profile >=3.2:

$ glxinfo | grep -i opengl
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel® HD Graphics (Coffeelake 3x8 GT2)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.0.5
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 18.0.5
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.0.5
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

[spiff]

yes, that's basically what i'm saying.. you can test if it behaves better if you launch kodi with old gl, by setting MESA_GL_VERSION_OVERRIDE=3.0

[User 29008]

thx @spiff , it actually works with the 3.0 profile. I can't seem to lock presets by pressing the "L" key though. Log shows keypress recognized as "lock preset" but it doesn't seem to have any effect.

boba

[3dfx]

thx @spiff , it actually works with the 3.0 profile. I can't seem to lock presets by pressing the "L" key though. Log shows keypress recognized as "lock preset" but it doesn't seem to have any effect.

boba

 How did you set it?
In the openbox autostart config?

I still didn't got it runing :/
In the openbox autostart I have now:

MESA_GL_VERSION_OVERRIDE=3.0
/usr/bin/kodi --standalone

But with this Kodi just crashes and in System info I still see the profile 4.5

[spiff]

export the variable.

[User 29008]

Correct, add "export" in front of that line...