| Summary: | 7.3.0 AppImage Randomly Crashes | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | shaav |
| Component: | Bundle-AppImage | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 7.3.0 | ||
| Target Milestone: | --- | ||
| Platform: | Appimage | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 7.4.0 | |
| Sentry Crash Report: | |||
|
Description
shaav
2021-11-08 02:28:04 UTC
Can you test the 7.4.0 AppImage pre-release build available here : https://files.kde.org/digikam/ To see if problem still here. If yes, use AppImage bundle with "debug" suffix and run it from the console with "debug" option from command line. This will run digikam in gdb. When it crash, enter "bt" to get the backtrace. Post the output here... all is explained in this page : https://www.digikam.org/contribute/ Best Gilles Caulier On 7.4.0 I'm getting: digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found Was actually in the process of trying to figure out how to install glibc_2.29... Same crash happens on 7.2.0 and 7.0.0 although in 7.0.0 the line number is 157. If it is helpful, I did find that it reliably crashes when switching to the "People" or "Map" tabs and just before the segmentation fault it reliably gives me: Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Which I guess is pointing at a driver issue? I'm using the latest proprietary release for my card: nvidia-driver-470 The line number is 157 --> it come from startup internal bash script in AppImage. It's not the line of code from binary program. `GLIBC_2.29' not found from 7.4.0 want mean that you linux host is to older to run 7.4.0. This last one is compiled with CentOS 7 like system, where 7.3.0 is compiled with CentOS 6 like. We upgrade binary compatibility to compile AppImage bundle for security reasons. About 7.3.0 crash, yes OpenGL issues is possible. We already seen this kind of problem in the past. OpenGL compatibility is a hell under Linux, especially with Qt/Chromium API used internally in digiKam to render Maps. Gilles Caulier Do you use a MariaDB database, if so in which MariaDB version? Maik > Do you use a MariaDB database, if so in which MariaDB version?
I don't no—just the sqllite db.
> About 7.3.0 crash, yes OpenGL issues is possible. We already seen this kind
> of problem in the past. OpenGL compatibility is a hell under Linux,
> especially with Qt/Chromium API used internally in digiKam to render Maps.
Hrm. So it looks like I might have had two issues happening and resolved one. I started watching my syslog when opening digikam and there was an API mismatch error with my graphics driver—that was resolved with a reboot and now it doesn't crash on switching to the people tab anymore.
The crash still happens though and it my syslog it's reporting:
ThreadPoolForeg[8491]: segfault at 1 ip 00007f74b7f51018 sp 00007f745db4a930 error 4 in libudev.so.0.13.0[7f74b7f4d000+c000]
I upgraded to Linux Mint 20 and the problem went away. Also 7.4 (unsurprisingly) works as well. |