digiKam › digikam-devel

[digikam] [Bug 368167] New: crash on startup in geoiface QMutex::lock [cause: digikamrc]

Classic

List

Threaded

7 messages Options

bugzilla_noreply

[digikam] [Bug 368167] New: crash on startup in geoiface QMutex::lock [cause: digikamrc]

https://bugs.kde.org/show_bug.cgi?id=368167

Bug ID: 368167
Summary: crash on startup in geoiface QMutex::lock [cause:
digikamrc]
Product: digikam
Version: 5.1.0
Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: Geolocation-Editor
Assignee: [hidden email]
Reporter: [hidden email]

Digikam crashes right on startup after the console messages as follows:

(... lots of kipi.plugins loading ...)
kipi.library: Loaded plugin "Smug"
kipi.plugins: Reading data from kipirc file..
Could not resolve property : XMLID_8_
Could not resolve property : XMLID_12_
Could not resolve property : XMLID_13_
Could not resolve property : XMLID_14_
Could not resolve property : XMLID_8_
Could not resolve property : XMLID_12_
Could not resolve property : XMLID_13_
Could not resolve property : XMLID_14_
Could not resolve property : XMLID_8_
Could not resolve property : XMLID_12_
Could not resolve property : XMLID_13_
Could not resolve property : XMLID_14_
digikam.geoiface: ----
Speicherzugriffsfehler (Speicherabzug geschrieben)

This happens exactly when in digikamrc, the following section is present:
[Digikam Right Sidebar]

Removing this section allows Digikam to start again. After closing it, the
section changes as follows:

[Digikam Right Sidebar]
-ActiveTab=3
+ActiveTab=0
DigikamProperties Expanded=true
FileProperties Expanded=true
ItemProperties Expanded=true
-Minimized=false
+Minimized=true
PhotographProperties Expanded=true
-RestoreSize=-1
+RestoreSize=209
VideoProperties Expanded=true

and subsequent starts are successful again.
This file was written by Digikam upon exit, I did not modify it by myself.

Partial backtrace:
Thread 1 (Thread 0x7f3822ac7b80 (LWP 7551)):
#0 0x00007f384f7d81d1 in QCoreApplication::postEvent(QObject*, QEvent*, int)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1 0x00007f384a64c397 in ?? () from
/usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.23
#2 0x00007f384a64cd30 in ?? () from
/usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.23
#3 0x00007f384f805ea1 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5

StacktraceTop:
QCoreApplication::postEvent(QObject*, QEvent*, int) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
?? () from /usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.23
?? () from /usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.23
QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
QApplicationPrivate::notify_helper(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5

Reproducible: Always

--
You are receiving this mail because:
You are the assignee for the bug.

bugzilla_noreply

[digikam] [Bug 368167] crash on startup in geoiface QMutex::lock [cause: digikamrc]

https://bugs.kde.org/show_bug.cgi?id=368167

[hidden email] changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[hidden email]
Component|Geolocation-Editor |Geolocation

--- Comment #1 from [hidden email] ---
Sound like a Marble Widget problem when sidebar is set to show maps view at
startup.
Remember that Marble has plenty of plugins. The problem can be located in a 3rd
party component

Also, this will be interesting to see if stand alone marble application has
same problem on your computer...

Note : please specify which maps view is expected to see : GoogleMaps, OSM, or
local ?

--
You are receiving this mail because:
You are the assignee for the bug.

bugzilla_noreply