[digiKam-users] Cannot start recent appimage on Manjaro

[Hans-Peter huth]

Hi,

the Appimage from March, 18 does not start on my Manjaro:

[hph@hackbrett4 Temp]$
./digikam-7.0.0-beta3-20200318T054830-x86-64.appimage -- digiKam Linux
AppImage Bundle -- Use 'help' as CLI argument to know all available options
for digiKam application. -- Notes: to integrate this bundle to your
desktop, use AppImageLauncher. --        to enable all debug messages on
the console, use 'export QT_LOGGING_RULES="digikam*=true"'. libudev.so.0
/tmp/.mount_digika7WekU1/AppRun: Zeile 16: arch: Kommando nicht gefunden.
libnss3.so
/tmp/.mount_digika7WekU1/AppRun: Zeile 16: arch: Kommando nicht gefunden.
-- Preloading shared libs: :/tmp/.mount_digika7WekU1/usr/lib/libnss3.so
unknown: qglx_findConfig: Failed to finding matching FBConfig for
QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(),
depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1,
alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior
QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace
QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
unknown: qglx_findConfig: Failed to finding matching FBConfig for
QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(),
depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1,
alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior
QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace
QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
unknown: Could not initialize GLX /tmp/.mount_digika7WekU1/AppRun: Zeile
157: 16475 Abgebrochen (Speicherabzug geschrieben) digikam $@

Any hints?

HP

--
--------- 8< -------------
Why taunt me? Why upbraid me? I am merely a genius, not a god.
(Nero Wolfe)
Meine Bilder: http://jalbum.net/a/1456383
Berge: http://jalbum.net/de/browse/user/album/1823943

[Maik Qualmann]

First of all, the "arch" command does not exist in your system. In my
distribution this command is part of the "coreutils".

Maik

Am Freitag, 20. März 2020, 20:32:51 CET schrieb Hans-Peter Huth:

> Hi,
>
> the Appimage from March, 18 does not start on my Manjaro:
>
> [hph@hackbrett4 Temp]$
> ./digikam-7.0.0-beta3-20200318T054830-x86-64.appimage -- digiKam Linux
> AppImage Bundle -- Use 'help' as CLI argument to know all available options
> for digiKam application. -- Notes: to integrate this bundle to your
> desktop, use AppImageLauncher. --        to enable all debug messages on
> the console, use 'export QT_LOGGING_RULES="digikam*=true"'. libudev.so.0
> /tmp/.mount_digika7WekU1/AppRun: Zeile 16: arch: Kommando nicht gefunden.
> libnss3.so
> /tmp/.mount_digika7WekU1/AppRun: Zeile 16: arch: Kommando nicht gefunden.
> -- Preloading shared libs: :/tmp/.mount_digika7WekU1/usr/lib/libnss3.so
> unknown: qglx_findConfig: Failed to finding matching FBConfig for
> QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(),
> depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1,
> alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior
> QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace
> QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
> unknown: qglx_findConfig: Failed to finding matching FBConfig for
> QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(),
> depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1,
> alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior
> QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace
> QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
> unknown: Could not initialize GLX /tmp/.mount_digika7WekU1/AppRun: Zeile
> 157: 16475 Abgebrochen (Speicherabzug geschrieben) digikam $@
>
> Any hints?
>
> HP

[Hans-Peter huth]

On Sat, 21 Mar 2020 07:12:27 +0100
Maik Qualmann <[hidden email]> wrote:

> First of all, the "arch" command does not exist in your system. In my
> distribution this command is part of the "coreutils".
>
> Maik
>

Thanks, but it is not contained by default. To state
https://www.gnu.org/software/coreutils/manual/html_node/arch-invocation.html#arch-invocation

"arch prints the machine hardware name, and is equivalent to ‘uname -m’.
Synopsis:

arch [option]

The program accepts the Common options only.

arch is not installed by default, so portable scripts should not rely on
its existence.

An exit status of zero indicates success, and a nonzero value indicates
failure."

Could you please use uname instead? BTW: older appimages run fine. Or can
Arch/Manjaro users point me to the correct package?

HP
>
>
>


--
--------- 8< -------------
Why taunt me? Why upbraid me? I am merely a genius, not a god.
(Nero Wolfe)
Meine Bilder: http://jalbum.net/a/1456383
Berge: http://jalbum.net/de/browse/user/album/1823943

[leoutation]

On 3/21/20 11:01 AM, Hans-Peter Huth wrote:

> On Sat, 21 Mar 2020 07:12:27 +0100
> Maik Qualmann <[hidden email]> wrote:
>
>> First of all, the "arch" command does not exist in your system. In my
>> distribution this command is part of the "coreutils".
>>
>> Maik
>>
>
> Thanks, but it is not contained by default. To state
> https://www.gnu.org/software/coreutils/manual/html_node/arch-invocation.html#arch-invocation
>
> "arch prints the machine hardware name, and is equivalent to ‘uname -m’.

In Arch distribution (and Arch derived distro like manjaro), only one
"arch" command: "tla"
https://www.archlinux.org/packages/community/x86_64/arch/

--
Maderios

[Hans-Peter huth]

On Sat, 21 Mar 2020 14:37:45 +0100
[hidden email] wrote:

> On 3/21/20 11:01 AM, Hans-Peter Huth wrote:
> > On Sat, 21 Mar 2020 07:12:27 +0100
> > Maik Qualmann <[hidden email]>
> > wrote:
> >> First of all, the "arch" command does not exist in your system. In my
> >> distribution this command is part of the "coreutils".
> >>
...
>
> In Arch distribution (and Arch derived distro like manjaro), only one
> "arch" command: "tla"
> https://www.archlinux.org/packages/community/x86_64/arch/
>
Yes, i have seen this. But the Appimage script tries to start 'arch'

Sym-linking tla to arch does not help:

[hph@hackbrett4 Temp]$
./digikam-7.0.0-beta3-20200318T054830-x86-64.appimage -- digiKam Linux
AppImage Bundle -- Use 'help' as CLI argument to know all available options
for digiKam application. -- Notes: to integrate this bundle to your
desktop, use AppImageLauncher. --        to enable all debug messages on
the console, use 'export QT_LOGGING_RULES="digikam*=true"'. libudev.so.0
usage: tla command ...
  (try 'tla -h')
libnss3.so
usage: tla command ...
  (try 'tla -h')
...

So maybe tla is really a different command.

When creating a script named 'arch' which simply calls 'uname -m', the error
message goes away, but digikam still does not start:

[hph@hackbrett4 Temp]$
./digikam-7.0.0-beta3-20200318T054830-x86-64.appimage -- digiKam Linux
AppImage Bundle -- Use 'help' as CLI argument to know all available options
for digiKam application. -- Notes: to integrate this bundle to your
desktop, use AppImageLauncher. --        to enable all debug messages on
the console, use 'export QT_LOGGING_RULES="digikam*=true"'. libudev.so.0
libnss3.so
-- Preloading shared libs: :/tmp/.mount_digikal6bNLT/usr/lib64/libnss3.so
unknown: qglx_findConfig: Failed to finding matching FBConfig for
QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(),
depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1,
alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior
QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace
QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
unknown: qglx_findConfig: Failed to finding matching FBConfig for
QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(),
depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1,
alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior
QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace
QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
unknown: Could not initialize GLX /tmp/.mount_digikal6bNLT/AppRun: Zeile
157: 26460 Abgebrochen             (Speicherabzug geschrieben) digikam $@


The older 'digikam-7.0.0-beta1-20191221T113643-x86-64.appimage' does start
and work fine.

HP

--
--------- 8< -------------
Why taunt me? Why upbraid me? I am merely a genius, not a god.
(Nero Wolfe)
Meine Bilder: http://jalbum.net/a/1456383
Berge: http://jalbum.net/de/browse/user/album/1823943

[Gilles Caulier-4]

Le sam. 21 mars 2020 à 11:42, Hans-Peter Huth <[hidden email]> a écrit :

>
> On Sat, 21 Mar 2020 14:37:45 +0100
> [hidden email] wrote:
>
> > On 3/21/20 11:01 AM, Hans-Peter Huth wrote:
> > > On Sat, 21 Mar 2020 07:12:27 +0100
> > > Maik Qualmann <[hidden email]>
> > > wrote:
> > >> First of all, the "arch" command does not exist in your system. In my
> > >> distribution this command is part of the "coreutils".
> > >>
> ...
> >
> > In Arch distribution (and Arch derived distro like manjaro), only one
> > "arch" command: "tla"
> > https://www.archlinux.org/packages/community/x86_64/arch/
> >
> Yes, i have seen this. But the Appimage script tries to start 'arch'

No. Look script code here :

https://invent.kde.org/kde/digikam/-/blob/master/project/bundles/appimage/data/AppRun

Gilles Caulier

[Hans-Peter huth]

On Sat, 21 Mar 2020 11:52:20 -0400
Gilles Caulier <[hidden email]>
wrote:

> Le sam. 21 mars 2020 à 11:42, Hans-Peter Huth
> <[hidden email]> a écrit :
> >
> > On Sat, 21 Mar 2020 14:37:45 +0100
> > [hidden email] wrote:
> >  
> > > On 3/21/20 11:01 AM, Hans-Peter Huth wrote:  
> > > > On Sat, 21 Mar 2020 07:12:27 +0100
> > > > Maik Qualmann <[hidden email]>
> > > > wrote:  
> > > >> First of all, the "arch" command does not exist in your system. In
> > > >> my distribution this command is part of the "coreutils".
> > > >>  
> > ...  
> > >
> > > In Arch distribution (and Arch derived distro like manjaro), only one
> > > "arch" command: "tla"
> > > https://www.archlinux.org/packages/community/x86_64/arch/
> > >  
> > Yes, i have seen this. But the Appimage script tries to start 'arch'  
>
> No. Look script code here :
>
> https://invent.kde.org/kde/digikam/-/blob/master/project/bundles/appimage/data/AppRun
>
> Gilles Caulier
>

Hmm, my script knowledge is a bit old. Line 16: "if [[ "$(arch)" =
"x86_64" ]] ; then"
So it tries to start the command 'arch' in a subshell, correct?

Anyway, even with my replacement script, the appimage doesn't start,
"...
digikam-7.0.0-beta1-20191221T113643-x86-64.appimage
..." (see previous mail).

As said, old appimages do run fine.

HP
--
--------- 8< -------------
Why taunt me? Why upbraid me? I am merely a genius, not a god.
(Nero Wolfe)
Meine Bilder: http://jalbum.net/a/1456383
Berge: http://jalbum.net/de/browse/user/album/1823943

[Gilles Caulier-4]

No $(arch) is a system variable used to share the current architecture
: 32 or 64 bits for ex...

https://superuser.com/questions/471645/issue-with-arch-variable

Gilles Caulier

Le sam. 21 mars 2020 à 12:23, Hans-Peter Huth <[hidden email]> a écrit :

>
> On Sat, 21 Mar 2020 11:52:20 -0400
> Gilles Caulier <[hidden email]>
> wrote:
>
> > Le sam. 21 mars 2020 à 11:42, Hans-Peter Huth
> > <[hidden email]> a écrit :
> > >
> > > On Sat, 21 Mar 2020 14:37:45 +0100
> > > [hidden email] wrote:
> > >
> > > > On 3/21/20 11:01 AM, Hans-Peter Huth wrote:
> > > > > On Sat, 21 Mar 2020 07:12:27 +0100
> > > > > Maik Qualmann <[hidden email]>
> > > > > wrote:
> > > > >> First of all, the "arch" command does not exist in your system. In
> > > > >> my distribution this command is part of the "coreutils".
> > > > >>
> > > ...
> > > >
> > > > In Arch distribution (and Arch derived distro like manjaro), only one
> > > > "arch" command: "tla"
> > > > https://www.archlinux.org/packages/community/x86_64/arch/
> > > >
> > > Yes, i have seen this. But the Appimage script tries to start 'arch'
> >
> > No. Look script code here :
> >
> > https://invent.kde.org/kde/digikam/-/blob/master/project/bundles/appimage/data/AppRun
> >
> > Gilles Caulier
> >
>
> Hmm, my script knowledge is a bit old. Line 16: "if [[ "$(arch)" =
> "x86_64" ]] ; then"
> So it tries to start the command 'arch' in a subshell, correct?
>
> Anyway, even with my replacement script, the appimage doesn't start,
> "...
> digikam-7.0.0-beta1-20191221T113643-x86-64.appimage
> ..." (see previous mail).
>
> As said, old appimages do run fine.
>
> HP
> --
> --------- 8< -------------
> Why taunt me? Why upbraid me? I am merely a genius, not a god.
> (Nero Wolfe)
> Meine Bilder: http://jalbum.net/a/1456383
> Berge: http://jalbum.net/de/browse/user/album/1823943
>
>

[Hans-Peter huth]

On Sat, 21 Mar 2020 12:33:24 -0400
Gilles Caulier <[hidden email]>
wrote:

> No $(arch) is a system variable used to share the current architecture
> : 32 or 64 bits for ex...
>
> https://superuser.com/questions/471645/issue-with-arch-variable
>

Thanks, didn't know that. It is not set on my system. Doing a "export
ARCH=$(uname -m)" before the start however makes no difference.

And could the "unknown: qglx_findConfig..." be the real reason why Digikam
doesn't start? Maybe Qt version problems (Qt 5.14.1 here)?

HP

--
--------- 8< -------------
Why taunt me? Why upbraid me? I am merely a genius, not a god.
(Nero Wolfe)
Meine Bilder: http://jalbum.net/a/1456383
Berge: http://jalbum.net/de/browse/user/album/1823943

[Maik Qualmann]

https://invent.kde.org/kde/digikam/-/commit/
8e2673d01fae0525c94b4e02db5c2e10ec00ea0c

Maik

Am Samstag, 21. März 2020, 17:58:44 CET schrieb Hans-Peter Huth:

> On Sat, 21 Mar 2020 12:33:24 -0400
> Gilles Caulier <[hidden email]>
>
> wrote:
> > No $(arch) is a system variable used to share the current architecture
> >
> > : 32 or 64 bits for ex...
> >
> > https://superuser.com/questions/471645/issue-with-arch-variable
>
> Thanks, didn't know that. It is not set on my system. Doing a "export
> ARCH=$(uname -m)" before the start however makes no difference.
>
> And could the "unknown: qglx_findConfig..." be the real reason why Digikam
> doesn't start? Maybe Qt version problems (Qt 5.14.1 here)?
>
> HP

[Gilles Caulier-4]

I will start to rebuild AppImage when the Internet connection will
better here in France. Currently the Git repository access to KDE
server is limited to 30Kb/s. It's certainly a COV-19 side-effect
(:=)))...

So please be patient.

Best regards

Gilles Caulier

Gilles

Le sam. 21 mars 2020 à 13:42, Maik Qualmann <[hidden email]> a écrit :

>
> https://invent.kde.org/kde/digikam/-/commit/
> 8e2673d01fae0525c94b4e02db5c2e10ec00ea0c
>
> Maik
>
> Am Samstag, 21. März 2020, 17:58:44 CET schrieb Hans-Peter Huth:
> > On Sat, 21 Mar 2020 12:33:24 -0400
> > Gilles Caulier <[hidden email]>
> >
> > wrote:
> > > No $(arch) is a system variable used to share the current architecture
> > >
> > > : 32 or 64 bits for ex...
> > >
> > > https://superuser.com/questions/471645/issue-with-arch-variable
> >
> > Thanks, didn't know that. It is not set on my system. Doing a "export
> > ARCH=$(uname -m)" before the start however makes no difference.
> >
> > And could the "unknown: qglx_findConfig..." be the real reason why Digikam
> > doesn't start? Maybe Qt version problems (Qt 5.14.1 here)?
> >
> > HP
>
>
>
>

[Maik Qualmann]

This is probably the main cause. We now use QWebEngine to display the HTML
content. QWebEngine requires stable OpenGL support. Does your problem look
like you're using an Intel graphics card and driver?

Maik

Am Samstag, 21. März 2020, 17:58:44 CET schrieb Hans-Peter Huth:
> And could the "unknown: qglx_findConfig..." be the real reason why Digikam
> doesn't start? Maybe Qt version problems (Qt 5.14.1 here)?

[Hans-Peter huth]

On Sat, 21 Mar 2020 20:19:07 +0100
Maik Qualmann <[hidden email]> wrote:

> This is probably the main cause. We now use QWebEngine to display the
> HTML content. QWebEngine requires stable OpenGL support. Does your
> problem look like you're using an Intel graphics card and driver?
>
> Maik
>
> Am Samstag, 21. März 2020, 17:58:44 CET schrieb Hans-Peter Huth:
> > And could the "unknown: qglx_findConfig..." be the real reason why
> > Digikam doesn't start? Maybe Qt version problems (Qt 5.14.1 here)?  
>
>
>
>
>

Yes, Intel driver:
Graphics:  Device-1: Intel HD Graphics 530 driver: i915 v: kernel
           Display: x11 server: X.Org 1.20.7 driver: intel resolution:
1920x1200~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 530 (Skylake
GT2) v: 4.6 Mesa 19.3.5

HP


--
--------- 8< -------------
Why taunt me? Why upbraid me? I am merely a genius, not a god.
(Nero Wolfe)
Meine Bilder: http://jalbum.net/a/1456383
Berge: http://jalbum.net/de/browse/user/album/1823943

[samuelkn]

Hi,

I'm having the same GLX issue as described here. However, the arch error
does not appear. I have tried version 7 beta 3 (24-Apr-2020 09:23). My setup
is Manjaro (Kernel 5.6.7), on Intel graphics.

I found that it could be due to some glxinfo. glxinfo and glxgears is
available on my system through the mesa-demos package.

Is there any update on this issue?

Best regards,
Samuel

---- output-----
-- Preloading shared libs: :/tmp/.mount_digikadOPlJ1/usr/lib64/libnss3.so

unknown: qglx_findConfig: Failed to finding matching FBConfig for
QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(),
depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1,
alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior
QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace
QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)

unknown: qglx_findConfig: Failed to finding matching FBConfig for
QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(),
depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1,
alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior
QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace
QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)

unknown: Could not initialize GLX

/tmp/.mount_digikadOPlJ1/AppRun: line 157: 115423 Aborted                
(core dumped) digikam $@




--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

[samuelkn]

Update on the GLX issue:

Sorry for not having tested and included this in my earlier post.

I tested the appimages of beta 1 and beta 2. While beta 1 is running
fine, beta 2 has gives the same error as beta 3. So, this problem might
have come in the transition to beta 3.

BTW: I'm running Xfce. Might this this be due to some Gtk vs Qt issue?

Probably this thread could be related:
https://github.com/NixOS/nixpkgs/issues/66755

Best,

Samuel

On 28.04.20 09:53, samuelkn wrote:

> Hi,
>
> I'm having the same GLX issue as described here. However, the arch error
> does not appear. I have tried version 7 beta 3 (24-Apr-2020 09:23). My setup
> is Manjaro (Kernel 5.6.7), on Intel graphics.
>
> I found that it could be due to some glxinfo. glxinfo and glxgears is
> available on my system through the mesa-demos package.
>
> Is there any update on this issue?
>
> Best regards,
> Samuel
>
> ---- output-----
> -- Preloading shared libs: :/tmp/.mount_digikadOPlJ1/usr/lib64/libnss3.so
>
> unknown: qglx_findConfig: Failed to finding matching FBConfig for
> QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(),
> depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1,
> alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior
> QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace
> QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
>
> unknown: qglx_findConfig: Failed to finding matching FBConfig for
> QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(),
> depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1,
> alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior
> QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace
> QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
>
> unknown: Could not initialize GLX
>
> /tmp/.mount_digikadOPlJ1/AppRun: line 157: 115423 Aborted
> (core dumped) digikam $@
>
>
>
>
> --
> Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

[Gilles Caulier-4]

Hi,

For security reasons, we switch from QtWebKit to QtWebEngine to render
HTML contents. Webkit qt framework is no supported officially by Qt
company since a while. We need to use WebEngine (Chromium) framework
instead.

The Chromium stuff require OpenGL this is why you seen this kind of
error on your system, even if we disable openGL support everywhere in
QtWebEngine. I suspect that some part still try to use OpenGL even if
it's disabled.

This is not a simple issue, not dependant of digiKam. QtWebEngine is a
monster, take few hours to be compiled here, and complex to tune in
client application.

Best

Gilles Caulier

Le mar. 28 avr. 2020 à 10:59, Samuel Knapp <[hidden email]> a écrit :

>
> Update on the GLX issue:
>
> Sorry for not having tested and included this in my earlier post.
>
> I tested the appimages of beta 1 and beta 2. While beta 1 is running
> fine, beta 2 has gives the same error as beta 3. So, this problem might
> have come in the transition to beta 3.
>
> BTW: I'm running Xfce. Might this this be due to some Gtk vs Qt issue?
>
> Probably this thread could be related:
> https://github.com/NixOS/nixpkgs/issues/66755
>
> Best,
>
> Samuel
>
> On 28.04.20 09:53, samuelkn wrote:
> > Hi,
> >
> > I'm having the same GLX issue as described here. However, the arch error
> > does not appear. I have tried version 7 beta 3 (24-Apr-2020 09:23). My setup
> > is Manjaro (Kernel 5.6.7), on Intel graphics.
> >
> > I found that it could be due to some glxinfo. glxinfo and glxgears is
> > available on my system through the mesa-demos package.
> >
> > Is there any update on this issue?
> >
> > Best regards,
> > Samuel
> >
> > ---- output-----
> > -- Preloading shared libs: :/tmp/.mount_digikadOPlJ1/usr/lib64/libnss3.so
> >
> > unknown: qglx_findConfig: Failed to finding matching FBConfig for
> > QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(),
> > depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1,
> > alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior
> > QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace
> > QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
> >
> > unknown: qglx_findConfig: Failed to finding matching FBConfig for
> > QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(),
> > depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1,
> > alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior
> > QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace
> > QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
> >
> > unknown: Could not initialize GLX
> >
> > /tmp/.mount_digikadOPlJ1/AppRun: line 157: 115423 Aborted
> > (core dumped) digikam $@
> >
> >
> >
> >
> > --
> > Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

[Kai Blauberg]

Hei,

Just for the record, the same error message also with Fedora 31:

Regards, Kai

[[hidden email] Downloads]$ ./digikam-7.0.0-beta3-20200422T062854-x86-64.appimage 

-- digiKam Linux AppImage Bundle

-- Use 'help' as CLI argument to know all available options for digiKam application.

-- Notes: to integrate this bundle to your desktop, use AppImageLauncher.

--        to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'.

libudev.so.0 

libnss3.so 

-- Preloading shared libs: :/tmp/.mount_digikaf7BThc/usr/lib64/libnss3.so

unknown: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)

unknown: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)

unknown: Could not initialize GLX

/tmp/.mount_digikaf7BThc/AppRun: rivi 157:11610 Keskeytetty             (luotiin core-tiedosto)digikam $@

[[hidden email] Downloads]$ 

-----Alkuperäinen viesti-----

Aihe: Re: [digiKam-users] Cannot start recent appimage on Manjaro

Lähettäjä: Gilles Caulier <[hidden email]>

Päiväys: Tue, 28 Apr 2020 11:21:56 +0200

Hi,

For security reasons, we switch from QtWebKit to QtWebEngine to render

HTML contents. Webkit qt framework is no supported officially by Qt

company since a while. We need to use WebEngine (Chromium) framework

instead.

The Chromium stuff require OpenGL this is why you seen this kind of

error on your system, even if we disable openGL support everywhere in

QtWebEngine. I suspect that some part still try to use OpenGL even if

it's disabled.

This is not a simple issue, not dependant of digiKam. QtWebEngine is a

monster, take few hours to be compiled here, and complex to tune in

client application.

Best

Gilles Caulier

Le mar. 28 avr. 2020 à 10:59, Samuel Knapp <

[hidden email]

> a écrit :

Update on the GLX issue:

Sorry for not having tested and included this in my earlier post.

I tested the appimages of beta 1 and beta 2. While beta 1 is running

fine, beta 2 has gives the same error as beta 3. So, this problem might

have come in the transition to beta 3.

BTW: I'm running Xfce. Might this this be due to some Gtk vs Qt issue?

Probably this thread could be related:

https://github.com/NixOS/nixpkgs/issues/66755

Best,

Samuel

On 28.04.20 09:53, samuelkn wrote:

Hi,

I'm having the same GLX issue as described here. However, the arch error

does not appear. I have tried version 7 beta 3 (24-Apr-2020 09:23). My setup

is Manjaro (Kernel 5.6.7), on Intel graphics.

I found that it could be due to some glxinfo. glxinfo and glxgears is

available on my system through the mesa-demos package.

Is there any update on this issue?

Best regards,

Samuel

---- output-----

-- Preloading shared libs: :/tmp/.mount_digikadOPlJ1/usr/lib64/libnss3.so

unknown: qglx_findConfig: Failed to finding matching FBConfig for

QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(),

depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1,

alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior

QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace

QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)

unknown: qglx_findConfig: Failed to finding matching FBConfig for

QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(),

depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1,

alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior

QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace

QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)

unknown: Could not initialize GLX

/tmp/.mount_digikadOPlJ1/AppRun: line 157: 115423 Aborted

(core dumped) digikam $@

--

Sent from: 

http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

-- 

Kai Blauberg

Oskelantie 10 as. 3 | 00320 Helsinki

puh. 040-730 7241 | s.posti [hidden email]

[Gilles Caulier-4]

Similar problem with flatpak and another Qt application probably using
QtWebEngine :

https://github.com/moonlight-stream/moonlight-qt/issues/49

Gilles Caulier

Le mar. 28 avr. 2020 à 13:13, Kai Blauberg <[hidden email]> a écrit :

>
> Hei,
>
> Just for the record, the same error message also with Fedora 31:
>
> Regards, Kai
>
>
> [digikam7@localhost Downloads]$ ./digikam-7.0.0-beta3-20200422T062854-x86-64.appimage
> -- digiKam Linux AppImage Bundle
> -- Use 'help' as CLI argument to know all available options for digiKam application.
> -- Notes: to integrate this bundle to your desktop, use AppImageLauncher.
> --        to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'.
> libudev.so.0
> libnss3.so
> -- Preloading shared libs: :/tmp/.mount_digikaf7BThc/usr/lib64/libnss3.so
> unknown: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
> unknown: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
> unknown: Could not initialize GLX
> /tmp/.mount_digikaf7BThc/AppRun: rivi 157:11610 Keskeytetty             (luotiin core-tiedosto)digikam $@
> [digikam7@localhost Downloads]$
>
>
> -----Alkuperäinen viesti-----
> Aihe: Re: [digiKam-users] Cannot start recent appimage on Manjaro
> Lähettäjä: Gilles Caulier <[hidden email]>
> Päiväys: Tue, 28 Apr 2020 11:21:56 +0200
>
> Hi,
>
>
> For security reasons, we switch from QtWebKit to QtWebEngine to render
>
> HTML contents. Webkit qt framework is no supported officially by Qt
>
> company since a while. We need to use WebEngine (Chromium) framework
>
> instead.
>
>
> The Chromium stuff require OpenGL this is why you seen this kind of
>
> error on your system, even if we disable openGL support everywhere in
>
> QtWebEngine. I suspect that some part still try to use OpenGL even if
>
> it's disabled.
>
>
> This is not a simple issue, not dependant of digiKam. QtWebEngine is a
>
> monster, take few hours to be compiled here, and complex to tune in
>
> client application.
>
>
> Best
>
>
> Gilles Caulier
>
>
> Le mar. 28 avr. 2020 à 10:59, Samuel Knapp <
>
> [hidden email]
>
> > a écrit :
>
>
> Update on the GLX issue:
>
>
> Sorry for not having tested and included this in my earlier post.
>
>
> I tested the appimages of beta 1 and beta 2. While beta 1 is running
>
> fine, beta 2 has gives the same error as beta 3. So, this problem might
>
> have come in the transition to beta 3.
>
>
> BTW: I'm running Xfce. Might this this be due to some Gtk vs Qt issue?
>
>
> Probably this thread could be related:
>
> https://github.com/NixOS/nixpkgs/issues/66755
>
>
>
> Best,
>
>
> Samuel
>
>
> On 28.04.20 09:53, samuelkn wrote:
>
> Hi,
>
>
> I'm having the same GLX issue as described here. However, the arch error
>
> does not appear. I have tried version 7 beta 3 (24-Apr-2020 09:23). My setup
>
> is Manjaro (Kernel 5.6.7), on Intel graphics.
>
>
> I found that it could be due to some glxinfo. glxinfo and glxgears is
>
> available on my system through the mesa-demos package.
>
>
> Is there any update on this issue?
>
>
> Best regards,
>
> Samuel
>
>
> ---- output-----
>
> -- Preloading shared libs: :/tmp/.mount_digikadOPlJ1/usr/lib64/libnss3.so
>
>
> unknown: qglx_findConfig: Failed to finding matching FBConfig for
>
> QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(),
>
> depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1,
>
> alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior
>
> QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace
>
> QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
>
>
> unknown: qglx_findConfig: Failed to finding matching FBConfig for
>
> QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(),
>
> depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1,
>
> alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior
>
> QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace
>
> QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
>
>
> unknown: Could not initialize GLX
>
>
> /tmp/.mount_digikadOPlJ1/AppRun: line 157: 115423 Aborted
>
> (core dumped) digikam $@
>
>
>
>
>
> --
>
> Sent from:
>
> http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html
>
>
> --
>
> Kai Blauberg
>
> Oskelantie 10 as. 3 | 00320 Helsinki
> puh. 040-730 7241 | s.posti [hidden email]

[Gilles Caulier-4]

For this one, after an update, problem is gone :

https://bbs.archlinux.org/viewtopic.php?id=228433

Note : the problem appear mostly with NVIDIA video card. The comon
tips is to use the NVIDIA video driver as well, not the open source
one.

Here i use Mageia 6 and 7, Centos 7 and 8 with NVIDIA video cards and
official driver : no GLX problem with the AppImage.

Gilles Caulier


Le mar. 28 avr. 2020 à 13:25, Gilles Caulier
<[hidden email]> a écrit :

>
> Similar problem with flatpak and another Qt application probably using
> QtWebEngine :
>
> https://github.com/moonlight-stream/moonlight-qt/issues/49
>
> Gilles Caulier
>
> Le mar. 28 avr. 2020 à 13:13, Kai Blauberg <[hidden email]> a écrit :
> >
> > Hei,
> >
> > Just for the record, the same error message also with Fedora 31:
> >
> > Regards, Kai
> >
> >
> > [digikam7@localhost Downloads]$ ./digikam-7.0.0-beta3-20200422T062854-x86-64.appimage
> > -- digiKam Linux AppImage Bundle
> > -- Use 'help' as CLI argument to know all available options for digiKam application.
> > -- Notes: to integrate this bundle to your desktop, use AppImageLauncher.
> > --        to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'.
> > libudev.so.0
> > libnss3.so
> > -- Preloading shared libs: :/tmp/.mount_digikaf7BThc/usr/lib64/libnss3.so
> > unknown: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
> > unknown: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
> > unknown: Could not initialize GLX
> > /tmp/.mount_digikaf7BThc/AppRun: rivi 157:11610 Keskeytetty             (luotiin core-tiedosto)digikam $@
> > [digikam7@localhost Downloads]$
> >
> >
> > -----Alkuperäinen viesti-----
> > Aihe: Re: [digiKam-users] Cannot start recent appimage on Manjaro
> > Lähettäjä: Gilles Caulier <[hidden email]>
> > Päiväys: Tue, 28 Apr 2020 11:21:56 +0200
> >
> > Hi,
> >
> >
> > For security reasons, we switch from QtWebKit to QtWebEngine to render
> >
> > HTML contents. Webkit qt framework is no supported officially by Qt
> >
> > company since a while. We need to use WebEngine (Chromium) framework
> >
> > instead.
> >
> >
> > The Chromium stuff require OpenGL this is why you seen this kind of
> >
> > error on your system, even if we disable openGL support everywhere in
> >
> > QtWebEngine. I suspect that some part still try to use OpenGL even if
> >
> > it's disabled.
> >
> >
> > This is not a simple issue, not dependant of digiKam. QtWebEngine is a
> >
> > monster, take few hours to be compiled here, and complex to tune in
> >
> > client application.
> >
> >
> > Best
> >
> >
> > Gilles Caulier
> >
> >
> > Le mar. 28 avr. 2020 à 10:59, Samuel Knapp <
> >
> > [hidden email]
> >
> > > a écrit :
> >
> >
> > Update on the GLX issue:
> >
> >
> > Sorry for not having tested and included this in my earlier post.
> >
> >
> > I tested the appimages of beta 1 and beta 2. While beta 1 is running
> >
> > fine, beta 2 has gives the same error as beta 3. So, this problem might
> >
> > have come in the transition to beta 3.
> >
> >
> > BTW: I'm running Xfce. Might this this be due to some Gtk vs Qt issue?
> >
> >
> > Probably this thread could be related:
> >
> > https://github.com/NixOS/nixpkgs/issues/66755
> >
> >
> >
> > Best,
> >
> >
> > Samuel
> >
> >
> > On 28.04.20 09:53, samuelkn wrote:
> >
> > Hi,
> >
> >
> > I'm having the same GLX issue as described here. However, the arch error
> >
> > does not appear. I have tried version 7 beta 3 (24-Apr-2020 09:23). My setup
> >
> > is Manjaro (Kernel 5.6.7), on Intel graphics.
> >
> >
> > I found that it could be due to some glxinfo. glxinfo and glxgears is
> >
> > available on my system through the mesa-demos package.
> >
> >
> > Is there any update on this issue?
> >
> >
> > Best regards,
> >
> > Samuel
> >
> >
> > ---- output-----
> >
> > -- Preloading shared libs: :/tmp/.mount_digikadOPlJ1/usr/lib64/libnss3.so
> >
> >
> > unknown: qglx_findConfig: Failed to finding matching FBConfig for
> >
> > QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(),
> >
> > depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1,
> >
> > alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior
> >
> > QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace
> >
> > QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
> >
> >
> > unknown: qglx_findConfig: Failed to finding matching FBConfig for
> >
> > QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(),
> >
> > depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1,
> >
> > alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior
> >
> > QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace
> >
> > QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
> >
> >
> > unknown: Could not initialize GLX
> >
> >
> > /tmp/.mount_digikadOPlJ1/AppRun: line 157: 115423 Aborted
> >
> > (core dumped) digikam $@
> >
> >
> >
> >
> >
> > --
> >
> > Sent from:
> >
> > http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html
> >
> >
> > --
> >
> > Kai Blauberg
> >
> > Oskelantie 10 as. 3 | 00320 Helsinki
> > puh. 040-730 7241 | s.posti [hidden email]

[samuelkn]

To test, if it could be related to QtWebKit or QtWebEngine, I installed
and tested the KDE falkon browser, which uses QtWebEngine, and also
found other programs, which use QtWebEngine (e.g. seafile). They all run
fine.

Also the tested the daily built now, with same error as with beta 2 and 3.

I have no NVIDIA card (ThinPad Yoga12 with original intel graphics (HD
5500). So, I don't think it's related to any NVIDIA driver.

However, as the error message is mentioning QSurfaceFormat, I found this
thread which could probably point towards the problem:

https://stackoverflow.com/questions/53768408/qt3d-qt-glx-qglx-findconfig-failed-to-finding-matching-fbconfig-warning

Best,

Samuel


On 28.04.20 13:28, Gilles Caulier wrote:

> For this one, after an update, problem is gone :
>
> https://bbs.archlinux.org/viewtopic.php?id=228433
>
> Note : the problem appear mostly with NVIDIA video card. The comon
> tips is to use the NVIDIA video driver as well, not the open source
> one.
>
> Here i use Mageia 6 and 7, Centos 7 and 8 with NVIDIA video cards and
> official driver : no GLX problem with the AppImage.
>
> Gilles Caulier
>
>
> Le mar. 28 avr. 2020 à 13:25, Gilles Caulier
> <[hidden email]> a écrit :
>> Similar problem with flatpak and another Qt application probably using
>> QtWebEngine :
>>
>> https://github.com/moonlight-stream/moonlight-qt/issues/49
>>
>> Gilles Caulier
>>
>> Le mar. 28 avr. 2020 à 13:13, Kai Blauberg <[hidden email]> a écrit :
>>> Hei,
>>>
>>> Just for the record, the same error message also with Fedora 31:
>>>
>>> Regards, Kai
>>>
>>>
>>> [digikam7@localhost Downloads]$ ./digikam-7.0.0-beta3-20200422T062854-x86-64.appimage
>>> -- digiKam Linux AppImage Bundle
>>> -- Use 'help' as CLI argument to know all available options for digiKam application.
>>> -- Notes: to integrate this bundle to your desktop, use AppImageLauncher.
>>> --        to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'.
>>> libudev.so.0
>>> libnss3.so
>>> -- Preloading shared libs: :/tmp/.mount_digikaf7BThc/usr/lib64/libnss3.so
>>> unknown: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
>>> unknown: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
>>> unknown: Could not initialize GLX
>>> /tmp/.mount_digikaf7BThc/AppRun: rivi 157:11610 Keskeytetty             (luotiin core-tiedosto)digikam $@
>>> [digikam7@localhost Downloads]$
>>>
>>>
>>> -----Alkuperäinen viesti-----
>>> Aihe: Re: [digiKam-users] Cannot start recent appimage on Manjaro
>>> Lähettäjä: Gilles Caulier <[hidden email]>
>>> Päiväys: Tue, 28 Apr 2020 11:21:56 +0200
>>>
>>> Hi,
>>>
>>>
>>> For security reasons, we switch from QtWebKit to QtWebEngine to render
>>>
>>> HTML contents. Webkit qt framework is no supported officially by Qt
>>>
>>> company since a while. We need to use WebEngine (Chromium) framework
>>>
>>> instead.
>>>
>>>
>>> The Chromium stuff require OpenGL this is why you seen this kind of
>>>
>>> error on your system, even if we disable openGL support everywhere in
>>>
>>> QtWebEngine. I suspect that some part still try to use OpenGL even if
>>>
>>> it's disabled.
>>>
>>>
>>> This is not a simple issue, not dependant of digiKam. QtWebEngine is a
>>>
>>> monster, take few hours to be compiled here, and complex to tune in
>>>
>>> client application.
>>>
>>>
>>> Best
>>>
>>>
>>> Gilles Caulier
>>>
>>>
>>> Le mar. 28 avr. 2020 à 10:59, Samuel Knapp <
>>>
>>> [hidden email]
>>>
>>>> a écrit :
>>>
>>> Update on the GLX issue:
>>>
>>>
>>> Sorry for not having tested and included this in my earlier post.
>>>
>>>
>>> I tested the appimages of beta 1 and beta 2. While beta 1 is running
>>>
>>> fine, beta 2 has gives the same error as beta 3. So, this problem might
>>>
>>> have come in the transition to beta 3.
>>>
>>>
>>> BTW: I'm running Xfce. Might this this be due to some Gtk vs Qt issue?
>>>
>>>
>>> Probably this thread could be related:
>>>
>>> https://github.com/NixOS/nixpkgs/issues/66755
>>>
>>>
>>>
>>> Best,
>>>
>>>
>>> Samuel
>>>
>>>
>>> On 28.04.20 09:53, samuelkn wrote:
>>>
>>> Hi,
>>>
>>>
>>> I'm having the same GLX issue as described here. However, the arch error
>>>
>>> does not appear. I have tried version 7 beta 3 (24-Apr-2020 09:23). My setup
>>>
>>> is Manjaro (Kernel 5.6.7), on Intel graphics.
>>>
>>>
>>> I found that it could be due to some glxinfo. glxinfo and glxgears is
>>>
>>> available on my system through the mesa-demos package.
>>>
>>>
>>> Is there any update on this issue?
>>>
>>>
>>> Best regards,
>>>
>>> Samuel
>>>
>>>
>>> ---- output-----
>>>
>>> -- Preloading shared libs: :/tmp/.mount_digikadOPlJ1/usr/lib64/libnss3.so
>>>
>>>
>>> unknown: qglx_findConfig: Failed to finding matching FBConfig for
>>>
>>> QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(),
>>>
>>> depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1,
>>>
>>> alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior
>>>
>>> QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace
>>>
>>> QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
>>>
>>>
>>> unknown: qglx_findConfig: Failed to finding matching FBConfig for
>>>
>>> QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(),
>>>
>>> depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1,
>>>
>>> alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior
>>>
>>> QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace
>>>
>>> QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
>>>
>>>
>>> unknown: Could not initialize GLX
>>>
>>>
>>> /tmp/.mount_digikadOPlJ1/AppRun: line 157: 115423 Aborted
>>>
>>> (core dumped) digikam $@
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Sent from:
>>>
>>> http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html
>>>
>>>
>>> --
>>>
>>> Kai Blauberg
>>>
>>> Oskelantie 10 as. 3 | 00320 Helsinki
>>> puh. 040-730 7241 | s.posti [hidden email]