digiKam › digikam-devel

[Bug 308827] New: digikam showed error after closing.

Classic

List

Threaded

6 messages Options

Ermides Gonzalez

[Bug 308827] New: digikam showed error after closing.

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

Bug ID: 308827
Severity: crash
Version: 2.8.0
Priority: NOR
Assignee: [hidden email]
Summary: digikam showed error after closing.
Classification: Unclassified
OS: Linux
Reporter: [hidden email]
Hardware: Ubuntu Packages
Status: UNCONFIRMED
Component: general
Product: digikam

Application: digikam (2.8.0)
KDE Platform Version: 4.9.2
Qt Version: 4.8.3
Operating System: Linux 3.5.0-17-generic x86_64
Distribution: Ubuntu 12.10

-- Information about the crash:
I printed a calendar and then I closed digikam, after closing the error
appeared.

-- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9efeac1a00 (LWP 6806))]

Thread 7 (Thread 0x7f9eda38d700 (LWP 6811)):
#0 0x00007f9ef8d5b4c5 in postEventSourcePrepare (s=0x7f9ecc0012d0,
timeout=0x7f9eda38c994) at kernel/qeventdispatcher_glib.cpp:255
#1 0x00007f9ef115b618 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f9ef115bcab in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f9ef115bea4 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007f9ef8d5bc16 in QEventDispatcherGlib::processEvents
(this=0x7f9ecc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#5 0x00007f9ef8d2c2bf in QEventLoop::processEvents
(this=this@entry=0x7f9eda38cb50, flags=...) at kernel/qeventloop.cpp:149
#6 0x00007f9ef8d2c548 in QEventLoop::exec (this=0x7f9eda38cb50, flags=...) at
kernel/qeventloop.cpp:204
#7 0x00007f9ef8c2db10 in QThread::exec (this=<optimized out>) at
thread/qthread.cpp:501
#8 0x00007f9ef8d0c9af in QInotifyFileSystemWatcherEngine::run (this=0x1e960e0)
at io/qfilesystemwatcher_inotify.cpp:248
#9 0x00007f9ef8c30aec in QThreadPrivate::start (arg=0x1e960e0) at
thread/qthread_unix.cpp:338
#10 0x00007f9ef3737e9a in start_thread (arg=0x7f9eda38d700) at
pthread_create.c:308
#11 0x00007f9ef7e59cbd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()

Thread 6 (Thread 0x7f9ed9b8c700 (LWP 6813)):
#0 pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1 0x00007f9ef8c3104b in wait (time=18446744073709551615, this=0x22c4b60) at
thread/qwaitcondition_unix.cpp:86
#2 QWaitCondition::wait (this=<optimized out>, mutex=0x245b658,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3 0x00007f9efc08ea47 in Digikam::ParkingThread::run() () from
/usr/lib/libdigikamcore.so.2
#4 0x00007f9ef8c30aec in QThreadPrivate::start (arg=0x245b640) at
thread/qthread_unix.cpp:338
#5 0x00007f9ef3737e9a in start_thread (arg=0x7f9ed9b8c700) at
pthread_create.c:308
#6 0x00007f9ef7e59cbd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7 0x0000000000000000 in ?? ()

Thread 5 (Thread 0x7f9ed8a53700 (LWP 6814)):
#0 0x00007f9ef7e4c8bd in read () at ../sysdeps/unix/syscall-template.S:82
#1 0x00007f9ef1197f6f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f9ef115b914 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f9ef115bd22 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007f9ef115bea4 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x00007f9ef8d5bc16 in QEventDispatcherGlib::processEvents
(this=0x7f9ec40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6 0x00007f9ef8d2c2bf in QEventLoop::processEvents
(this=this@entry=0x7f9ed8a52b50, flags=...) at kernel/qeventloop.cpp:149
#7 0x00007f9ef8d2c548 in QEventLoop::exec (this=0x7f9ed8a52b50, flags=...) at
kernel/qeventloop.cpp:204
#8 0x00007f9ef8c2db10 in QThread::exec (this=<optimized out>) at
thread/qthread.cpp:501
#9 0x00007f9ef8d0c9af in QInotifyFileSystemWatcherEngine::run (this=0x246a010)
at io/qfilesystemwatcher_inotify.cpp:248
#10 0x00007f9ef8c30aec in QThreadPrivate::start (arg=0x246a010) at
thread/qthread_unix.cpp:338
#11 0x00007f9ef3737e9a in start_thread (arg=0x7f9ed8a53700) at
pthread_create.c:308
#12 0x00007f9ef7e59cbd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#13 0x0000000000000000 in ?? ()

Thread 4 (Thread 0x7f9eab7fe700 (LWP 6860)):
#0 0x00007f9ef40c3fb6 in ?? () from /usr/lib/x86_64-linux-gnu/libgomp.so.1
#1 0x00007f9ef40c282e in ?? () from /usr/lib/x86_64-linux-gnu/libgomp.so.1
#2 0x00007f9ef3737e9a in start_thread (arg=0x7f9eab7fe700) at
pthread_create.c:308
#3 0x00007f9ef7e59cbd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#4 0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f9eaa331700 (LWP 6861)):
#0 0x00007f9ef40c3fb6 in ?? () from /usr/lib/x86_64-linux-gnu/libgomp.so.1
#1 0x00007f9ef40c282e in ?? () from /usr/lib/x86_64-linux-gnu/libgomp.so.1
#2 0x00007f9ef3737e9a in start_thread (arg=0x7f9eaa331700) at
pthread_create.c:308
#3 0x00007f9ef7e59cbd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#4 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f9ea94e6700 (LWP 6862)):
#0 0x00007f9ef40c3fb6 in ?? () from /usr/lib/x86_64-linux-gnu/libgomp.so.1
#1 0x00007f9ef40c282e in ?? () from /usr/lib/x86_64-linux-gnu/libgomp.so.1
#2 0x00007f9ef3737e9a in start_thread (arg=0x7f9ea94e6700) at
pthread_create.c:308
#3 0x00007f9ef7e59cbd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#4 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f9efeac1a00 (LWP 6806)):
[KCrash Handler]
#6 0x00007f9ef0e8e0ff in FT_Done_Face () from
/usr/lib/x86_64-linux-gnu/libfreetype.so.6
#7 0x00007f9ef99ff941 in QFreetypeFace::release (this=0x1ee6470, face_id=...)
at text/qfontengine_ft.cpp:326
#8 0x00007f9ef9a0053f in QFontEngineFT::~QFontEngineFT (this=0x219a220,
__in_chrg=<optimized out>) at text/qfontengine_ft.cpp:652
#9 0x00007f9ef99f72e9 in QFontEngineX11FT::~QFontEngineX11FT (this=0x219a220,
__in_chrg=<optimized out>) at text/qfontengine_x11.cpp:1128
#10 0x00007f9ef99304d6 in QFontCache::clear (this=this@entry=0x1ed91a0) at
text/qfont.cpp:2883
#11 0x00007f9ef993059a in QFontCache::~QFontCache (this=0x1ed91a0,
__in_chrg=<optimized out>) at text/qfont.cpp:2815
#12 0x00007f9ef99306d9 in QFontCache::~QFontCache (this=0x1ed91a0,
__in_chrg=<optimized out>) at text/qfont.cpp:2846
#13 0x00007f9ef8c2e8a0 in QThreadStorageData::set (this=<optimized out>, p=0x0)
at thread/qthreadstorage.cpp:165
#14 0x00007f9ef978b11a in qt_cleanup () at kernel/qapplication_x11.cpp:2721
#15 0x00007f9ef971812e in QApplication::~QApplication (this=0x7fffb6f654e0,
__in_chrg=<optimized out>) at kernel/qapplication.cpp:1192
#16 0x00000000006cbdcc in main ()

Reported using DrKonqi

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

Gilles Caulier-4

[Bug 308827] digikam showed error after closing.

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

Gilles Caulier <[hidden email]> changed:

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

--- Comment #1 from Gilles Caulier <[hidden email]> ---
There is no digiKam code relevant in your backtrace. Sound like a crash from
Qt/X11 about fonts.

Check your system...

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

Gilles Caulier-4

[digikam] [Bug 308827] digikam showed error after closing.

In reply to this post by Ermides Gonzalez

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

--- Comment #2 from Gilles Caulier <[hidden email]> ---
New digiKam 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?

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

Gilles Caulier-4

[digikam] [Bug 308827] digikam showed error after closing.

In reply to this post by Ermides Gonzalez

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

--- Comment #3 from Gilles Caulier <[hidden email]> ---
digiKam 4.12.0 is out :

https://www.digikam.org/node/741

We need a fresh feedback using this release please...
Thanks in advance.

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

bugzilla_noreply

[digikam] [Bug 308827] digikam showed error after closing.

In reply to this post by Ermides Gonzalez

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

[hidden email] changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |FIXED
Version Fixed In| |5.1.0

--- Comment #4 from [hidden email] ---
This problem is not reproducible with last 5.0.0.
I close this file now. Don't hesitate to re-open it if necessary.
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

bugzilla_noreply

[digikam] [Bug 308827] digikam showed error after closing.

In reply to this post by Ermides Gonzalez