Bug 337311 - Korganizer crashed while moving one apointment from one day to another
Summary: Korganizer crashed while moving one apointment from one day to another
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: general (other bugs)
Version First Reported In: 4.11.5
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2014-07-10 09:52 UTC by Andres Nogueiras
Modified: 2017-01-07 21:50 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andres Nogueiras 2014-07-10 09:52:54 UTC
Application: korganizer (4.11.5)
KDE Platform Version: 4.11.5
Qt Version: 4.8.5
Operating System: Linux 3.11.10-17-desktop x86_64
Distribution: "openSUSE 13.1 (Bottle) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

I was moving one appointment in my agenda to another time in the same day

-- Backtrace:
Application: KOrganizer (korganizer), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6d09231880 (LWP 1741))]

Thread 2 (Thread 0x7f6ce32e7700 (LWP 3138)):
#0  0x00007f6d05847b3d in poll () from /lib64/libc.so.6
#1  0x00007f6cfe100604 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f6cfe10070c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f6d06ea3d76 in QEventDispatcherGlib::processEvents (this=0x7f6cdc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427
#4  0x00007f6d06e75d0f in QEventLoop::processEvents (this=this@entry=0x7f6ce32e6d20, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f6d06e76005 in QEventLoop::exec (this=this@entry=0x7f6ce32e6d20, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f6d06d74fef in QThread::exec (this=this@entry=0x2f35290) at thread/qthread.cpp:536
#7  0x00007f6d06e57513 in QInotifyFileSystemWatcherEngine::run (this=0x2f35290) at io/qfilesystemwatcher_inotify.cpp:256
#8  0x00007f6d06d7768f in QThreadPrivate::start (arg=0x2f35290) at thread/qthread_unix.cpp:338
#9  0x00007f6d0364d0db in start_thread () from /lib64/libpthread.so.0
#10 0x00007f6d0585090d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f6d09231880 (LWP 1741)):
[KCrash Handler]
#6  0x0000000000000000 in ?? ()
#7  0x00007f6d0628a640 in QApplication::x11ProcessEvent (this=0x7fff380cea80, event=event@entry=0x7fff380ce440) at kernel/qapplication_x11.cpp:3431
#8  0x00007f6d062b1882 in x11EventSourceDispatch (s=0xe2dc70, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#9  0x00007f6cfe100316 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#10 0x00007f6cfe100668 in ?? () from /usr/lib64/libglib-2.0.so.0
#11 0x00007f6cfe10070c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#12 0x00007f6d06ea3d55 in QEventDispatcherGlib::processEvents (this=0xde4a90, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#13 0x00007f6d062b1936 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#14 0x00007f6d06e75d0f in QEventLoop::processEvents (this=this@entry=0x7fff380ce820, flags=...) at kernel/qeventloop.cpp:149
#15 0x00007f6d06e76005 in QEventLoop::exec (this=this@entry=0x7fff380ce820, flags=...) at kernel/qeventloop.cpp:204
#16 0x00007f6d06e7b13b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221
#17 0x000000000040863b in ?? ()
#18 0x00007f6d0578abe5 in __libc_start_main () from /lib64/libc.so.6
#19 0x0000000000408965 in _start ()

The reporter indicates this bug may be a duplicate of or related to bug 323345, bug 323397.

Possible duplicates by query: bug 336966, bug 336796, bug 336756, bug 336361, bug 336269.

Reported using DrKonqi
Comment 1 Denis Kurz 2016-09-24 18:47:04 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 21:50:22 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.