Bug 254774 - kontact crashed after clicking a ical file in chrome while the calendar import file browser was already open
Summary: kontact crashed after clicking a ical file in chrome while the calendar impor...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-20 16:49 UTC by Craig Magina
Modified: 2017-01-07 21:54 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Craig Magina 2010-10-20 16:49:00 UTC
Application: kontact (4.4.6)
KDE Platform Version: 4.5.2 (KDE 4.5.2)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-22-generic x86_64
Distribution: Ubuntu 10.10

-- Information about the crash:
I downloaded an ical file, but it was named .ical, so kontact's calendar import file browser didn't see it.  I went back to chrome without closing the file browser and clicked the file (opening it).  It switched me back to kontact and switched kontact to the to-do list plugin and then crashed.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0x7fa2ee96b780 (LWP 23994))]

Thread 2 (Thread 0x7fa2c3fff710 (LWP 24006)):
#0  0x00007fa2eb99d1d3 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007fa2e470b009 in g_main_context_poll (context=0x10b7390, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at /build/buildd/glib2.0-2.26.0/glib/gmain.c:3093
#2  g_main_context_iterate (context=0x10b7390, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2775
#3  0x00007fa2e470b45c in g_main_context_iteration (context=0x10b7390, may_block=1) at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2843
#4  0x00007fa2ec0e11e6 in QEventDispatcherGlib::processEvents (this=0xeadf80, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:417
#5  0x00007fa2ec0b3a02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#6  0x00007fa2ec0b3dec in QEventLoop::exec (this=0x7fa2c3ffed90, flags=) at kernel/qeventloop.cpp:201
#7  0x00007fa2ebfbe2fd in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490
#8  0x00007fa2ec0935f8 in QInotifyFileSystemWatcherEngine::run (this=0xfd63a0) at io/qfilesystemwatcher_inotify.cpp:248
#9  0x00007fa2ebfc127e in QThreadPrivate::start (arg=0xfd63a0) at thread/qthread_unix.cpp:266
#10 0x00007fa2e6a9a971 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#11 0x00007fa2eb9a991d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fa2ee96b780 (LWP 23994)):
[KCrash Handler]
#6  0x00007fa2ecaf3051 in QETWidget::translateMouseEvent (this=0x1106a50, event=0x7fffd0883600) at kernel/qapplication_x11.cpp:4354
#7  0x00007fa2ecaf1c5c in QApplication::x11ProcessEvent (this=<value optimized out>, event=0x7fffd0883ec0) at kernel/qapplication_x11.cpp:3536
#8  0x00007fa2ecb1e0e2 in x11EventSourceDispatch (s=0x725360, callback=<value optimized out>, user_data=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:146
#9  0x00007fa2e4707342 in g_main_dispatch (context=0x724520) at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2149
#10 g_main_context_dispatch (context=0x724520) at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2702
#11 0x00007fa2e470b2a8 in g_main_context_iterate (context=0x724520, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2780
#12 0x00007fa2e470b45c in g_main_context_iteration (context=0x724520, may_block=1) at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2843
#13 0x00007fa2ec0e1193 in QEventDispatcherGlib::processEvents (this=0x6e9e90, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:415
#14 0x00007fa2ecb1da4e in QGuiEventDispatcherGlib::processEvents (this=0x7fffd08835a0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#15 0x00007fa2ec0b3a02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#16 0x00007fa2ec0b3dec in QEventLoop::exec (this=0x7fffd08841f0, flags=) at kernel/qeventloop.cpp:201
#17 0x00007fa2ec0b7ebb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#18 0x0000000000403b4e in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../kontact/src/main.cpp:224

Possible duplicates by query: bug 254762, bug 254748, bug 254608, bug 254554, bug 254409.

Reported using DrKonqi
Comment 1 Denis Kurz 2016-09-24 19:26:20 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 kontact (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:54:11 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.