[digikam] [Bug 363362] New: crash when using configuration

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

[digikam] [Bug 363362] New: crash when using configuration

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

            Bug ID: 363362
           Summary: crash when using configuration
           Product: digikam
           Version: 4.4.0
          Platform: Debian stable
                OS: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: setup
          Assignee: [hidden email]
          Reporter: [hidden email]

After choosing menu "configure digikam" the dialog starts up and looks ok, but
after the first clicks, the entire application freezes.


Reproducible: Always

Steps to Reproduce:
1. start digikam
2. click menu-entry "configure digikam"
3. click something in the dialog-box

Actual Results:  
application freezes, sometimes shows a single reaction after a minute or so,
but never recovers

Expected Results:  
normal operations and ability to use the configuration dialog

standard Debian stable application
64 Bit multi-core Intel system
MariaDB
XFCE Desktop

this happens on the console:

Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QString)
Object::connect: No such signal
org::freedesktop::UPower::DeviceRemoved(QString)
Got bus address:
"unix:abstract=/tmp/dbus-QWhAl5MZWw,guid=b930101fe7404a1657f64adb5730b810"
Connected to accessibility bus at:
"unix:abstract=/tmp/dbus-QWhAl5MZWw,guid=b930101fe7404a1657f64adb5730b810"
Registered DEC:  true
Registered event listener change listener:  true
QSpiAccessible::accessibleEvent not handled:  "8008"  obj:  QObject(0x0)  "
invalid interface!"
QSpiAccessible::accessibleEvent not handled:  "8008"  obj:  QObject(0x0)  "
invalid interface!"
FIXME: handle dialog end.
QSpiAccessible::accessibleEvent not handled:  "6"  obj:  KMenu(0x2b67d40, name
= "settings") "settings"
QSpiAccessible::accessibleEvent not handled:  "7"  obj:  KMenu(0x2b67d40, name
= "settings") "settings"
QLayout: Cannot add null widget to QVBoxLayout/
QSpiAccessible::accessibleEvent not handled:  "8008"  obj:  QObject(0x0)  "
invalid interface!"
QSpiAccessible::accessibleEvent not handled:  "8008"  obj:  QObject(0x0)  "
invalid interface!"
FIXME: handle dialog start.
QSpiAccessible::accessibleEvent not handled:  "8008"  obj:  QObject(0x0)  "
invalid interface!"
QSpiAccessible::accessibleEvent not handled:  "8008"  obj:  QObject(0x0)  "
invalid interface!"
QSpiAccessible::accessibleEvent not handled:  "8008"  obj:  QObject(0x0)  "
invalid interface!"
QSpiAccessible::accessibleEvent not handled:  "8008"  obj:  QObject(0x0)  "
invalid interface!"
QSpiAccessible::accessibleEvent not handled:  "8008"  obj:  QObject(0x0)  "
invalid interface!"

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 363362] crash when using configuration

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

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |BACKTRACE
                 CC|                            |[hidden email]

--- Comment #1 from [hidden email] ---
We need a GDB backtrace to investiguate.

Also use last stable 4.14.0 instead older 4.4.0.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 363362] crash when using configuration

bugzilla_noreply
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=363362

--- Comment #2 from Emil Obermayr <[hidden email]> ---
Can you tell me a Debian Repository where I can get the 4.14?

GDB Backtrace after the dialog hangs:

[Thread 0x7fffab7fc700 (LWP 22106) exited]
[Thread 0x7fff48ff9700 (LWP 22133) exited]
[Thread 0x7fffb8bc9700 (LWP 22104) exited]
[Thread 0x7fff437fe700 (LWP 22134) exited]

^C
Program received signal SIGINT, Interrupt.
0x00007ffff1d86e53 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
(gdb) bt
#0  0x00007ffff1d86e53 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#1  0x00007ffff1d6ec3a in QObjectPrivate::~QObjectPrivate() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2  0x00007ffff1d709e4 in QObject::~QObject() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#3  0x00007ffff1d74a09 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x00007ffff1d6fce3 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5  0x00007ffff277548c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#6  0x00007ffff277bfa8 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#7  0x00007ffff34ed1aa in KApplication::notify(QObject*, QEvent*) () from
/usr/lib/libkdeui.so.5
#8  0x00007ffff1d5671d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x00007ffff1d8838b in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#10 0x00007ffff1d853c1 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#11 0x00007fffe935ec5d in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007fffe935ef48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007fffe935effc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007ffff1d85d1d in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#15 0x00007ffff2819f96 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#16 0x00007ffff1d55271 in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#17 0x00007ffff1d555d5 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#18 0x00007ffff2c4ae7c in QDialog::exec() () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#19 0x00000000004e10c5 in ?? ()
#20 0x00000000005bc326 in ?? ()
#21 0x00007ffff1d6b71c in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#22 0x00007ffff276ece2 in QAction::triggered(bool) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#23 0x00007ffff2770867 in QAction::activate(QAction::ActionEvent) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#24 0x00007ffff2bc569d in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#25 0x00007ffff2bca069 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#26 0x00007ffff35b5013 in KMenu::mouseReleaseEvent(QMouseEvent*) () from
/usr/lib/libkdeui.so.5
#27 0x00007ffff27c8748 in QWidget::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#28 0x00007ffff2bce04b in QMenu::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#29 0x00007ffff277548c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#30 0x00007ffff277c10f in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#31 0x00007ffff34ed1aa in KApplication::notify(QObject*, QEvent*) () from
/usr/lib/libkdeui.so.5
#32 0x00007ffff1d5671d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#33 0x00007ffff277b76f in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#34 0x00007ffff27f27ca in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#35 0x00007ffff27f0e2c in QApplication::x11ProcessEvent(_XEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#36 0x00007ffff2819ed2 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#37 0x00007fffe935ec5d in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#38 0x00007fffe935ef48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#39 0x00007fffe935effc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#40 0x00007ffff1d85d1d in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#41 0x00007ffff2819f96 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#42 0x00007ffff1d55271 in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#43 0x00007ffff1d555d5 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#44 0x00007ffff1d5b059 in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#45 0x0000000000495be6 in ?? ()
#46 0x00007ffff0da7b45 in __libc_start_main (main=0x494aa0, argc=1,
argv=0x7fffffffe348, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7fffffffe338)
    at libc-start.c:287
#47 0x00000000004981df in _start ()
(gdb)

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 363362] crash when using configuration

bugzilla_noreply
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=363362

--- Comment #3 from [hidden email] ---
There is nothing to see in your backtrace.

Did you install debug packages and run digiKam into GDB as ?

https://www.digikam.org/contrib

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 363362] crash when using configuration

bugzilla_noreply
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=363362

--- Comment #4 from Emil Obermayr <[hidden email]> ---
I got 4.14 from the Jessie Backports.

Configuration works now.

Thanks for the hint.

I will use the debug package when I find the next bug ;-)

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 363362] crash when using configuration

bugzilla_noreply
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=363362

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|BACKTRACE                   |INVALID

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel