[digiKam-users] DK 7.1.0 not starting anymore

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

[digiKam-users] DK 7.1.0 not starting anymore

digikam-2
DK 7.1.0 appimage on Manjaro and DK doesn't start anymore.

Yesterday, I did a Manjaro update and today...

I get:

> $ ~/downloads/appimages/digikam-7.1.0-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
libnssutil3.so
libxcb-dri3.so.0
-- Preloading shared libs: :/tmp/.mount_digikaK1RWuf/usr/lib64/libnss3.so:/tmp/.mount_digikaK1RWuf/usr/lib64/libnssutil3.so:/tmp/.mount_digikaK1RWuf/usr/lib64/libxcb-dri3.so.0
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_digikaK1RWuf/AppRun: line 163:  1509 Aborted                 (core dumped) digikam $@

I have the feeling that it's to do with Qt.

> $qmake --version
> QMake version 3.1
> Using Qt version 5.15.1 in /usr/lib

Any suggested work around?

Thank you

--
sknahT

vyS
Reply | Threaded
Open this post in threaded view
|

Re: DK 7.1.0 not starting anymore

Hans-Peter huth
On Fri, 6 Nov 2020 07:54:36 -0800
[hidden email] wrote:

> DK 7.1.0 appimage on Manjaro and DK doesn't start anymore.
>
> Yesterday, I did a Manjaro update and today...
>

why not use the native Manjaro digikam package? Runs fine 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


Reply | Threaded
Open this post in threaded view
|

Re: DK 7.1.0 not starting anymore

digikam-2
On Fri, 6 Nov 2020 17:53:32 +0100
Hans-Peter Huth <[hidden email]> wrote:

> On Fri, 6 Nov 2020 07:54:36 -0800
> [hidden email] wrote:
>
> > DK 7.1.0 appimage on Manjaro and DK doesn't start anymore.
> >
> > Yesterday, I did a Manjaro update and today...
> >  
>
> why not use the native Manjaro digikam package? Runs fine here.

I'm not using the native because it also requires akonadi

--
sknahT

vyS
Reply | Threaded
Open this post in threaded view
|

Re: DK 7.1.0 not starting anymore

Hans-Peter huth
On Fri, 6 Nov 2020 09:14:22 -0800
[hidden email] wrote:

> On Fri, 6 Nov 2020 17:53:32 +0100
> Hans-Peter Huth <[hidden email]> wrote:
>
> > On Fri, 6 Nov 2020 07:54:36 -0800
> > [hidden email] wrote:
> >  
> > > DK 7.1.0 appimage on Manjaro and DK doesn't start anymore.
> > >
> > > Yesterday, I did a Manjaro update and today...
> > >    
> >
> > why not use the native Manjaro digikam package? Runs fine here.  
>
> I'm not using the native because it also requires akonadi
>

I just tested: you can remove akonadi, but not libakonadi and
akonadi-contacts. So why is this a problem? I never used any KDE progs
apart from digikam, which runs fine under XFCE.

HP
> --
> sknahT
>
> vyS
>


--
--------- 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


Reply | Threaded
Open this post in threaded view
|

Re: DK 7.1.0 not starting anymore

Hans-Peter huth
In reply to this post by digikam-2
On Fri, 6 Nov 2020 07:54:36 -0800
[hidden email] wrote:

...
I had this problem a while ago, maybe the old thread helps:
http://digikam.1695700.n4.nabble.com/digiKam-users-Cannot-start-recent-appimage-on-Manjaro-td4711983.html

I did not quite understood what went wrong, but it seems we have to wait for
new appimage builds.

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


Reply | Threaded
Open this post in threaded view
|

Re: DK 7.1.0 not starting anymore

digikam-2
On Fri, 6 Nov 2020 19:13:46 +0100
Hans-Peter Huth <[hidden email]> wrote:

> On Fri, 6 Nov 2020 07:54:36 -0800
> [hidden email] wrote:
>
> ...
> I had this problem a while ago, maybe the old thread helps:
> http://digikam.1695700.n4.nabble.com/digiKam-users-Cannot-start-recent-appimage-on-Manjaro-td4711983.html

I've read it and it doesn't look like it's applying to me. I use
amdgpu and kde.

$ inxi -Gaz
Graphics:  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
           vendor: Micro-Star MSI driver: amdgpu v: kernel bus ID: 01:00.0  chip ID: 1002:67df
           Display: x11 server: X.Org 1.20.9 compositor: kwin_x11 driver: amdgpu
           FAILED: ati unloaded: modesetting,radeon alternate: fbdev,vesa display ID: :0
           screens: 1
           Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x285mm (40.0x11.2")  s-diag: 1055mm (41.5")
           Monitor-1: DisplayPort-1 res: 1920x1080 hz: 60 dpi: 96 size: 510x290mm (20.1x11.4") diag: 587mm (23.1")
           Monitor-2: DisplayPort-2 res: 1920x1080 dpi: 96 size: 509x286mm (20.0x11.3") diag: 584mm (23")
           OpenGL: renderer: Radeon RX 570 Series (POLARIS10 DRM 3.35.0 5.4.74-1-MANJARO LLVM 10.0.1)  v: 4.6 Mesa 20.2.1 direct render: Yes


>
> I did not quite understood what went wrong, but it seems we have to
> wait for new appimage builds.


--
sknahT

vyS