[kontact] [Bug 316764] New: Kontact is started twice
https://bugs.kde.org/show_bug.cgi?id=316764 Bug ID: 316764 Summary: Kontact is started twice Classification: Unclassified Product: kontact Version: 4.10.1 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: b_sta...@gmx.at Application: kontact (4.10.1) KDE Platform Version: 4.10.1 Qt Version: 4.8.3 Operating System: Linux 3.5.0-26-generic x86_64 Distribution: Ubuntu 12.10 -- Information about the crash: - What I was doing when the application crashed: After login Kontact is started twice when loading last desktop session. This leads to problems and Kontact crashes after some time. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f57058b17c0 (LWP 3240))] Thread 5 (Thread 0x7f56fe2ad700 (LWP 3243)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f5717120b2d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f5717120c39 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f5712255e9a in start_thread (arg=0x7f56fe2ad700) at pthread_create.c:308 #4 0x7f5717e4bccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 4 (Thread 0x7f56fd994700 (LWP 3245)): #0 0x7f5712257f69 in __pthread_mutex_lock (mutex=0x7f56f8000a60) at pthread_mutex_lock.c:92 #1 0x7f57119cbe21 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f571198e623 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f571198ecab in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f571198eea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f571926dc46 in QEventDispatcherGlib::processEvents (this=0x7f56f80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7f571923e2ef in QEventLoop::processEvents (this=this@entry=0x7f56fd993dc0, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f571923e578 in QEventLoop::exec (this=0x7f56fd993dc0, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f571913fb40 in QThread::exec (this=) at thread/qthread.cpp:501 #9 0x7f5719142b1c in QThreadPrivate::start (arg=0x1b10770) at thread/qthread_unix.cpp:338 #10 0x7f5712255e9a in start_thread (arg=0x7f56fd994700) at pthread_create.c:308 #11 0x7f5717e4bccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #12 0x in ?? () Thread 3 (Thread 0x7f56af120700 (LWP 3459)): #0 0x7f571198ec40 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f571198eea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f571926dc46 in QEventDispatcherGlib::processEvents (this=0x7f56a80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #3 0x7f571923e2ef in QEventLoop::processEvents (this=this@entry=0x7f56af11fd90, flags=...) at kernel/qeventloop.cpp:149 #4 0x7f571923e578 in QEventLoop::exec (this=0x7f56af11fd90, flags=...) at kernel/qeventloop.cpp:204 #5 0x7f571913fb40 in QThread::exec (this=) at thread/qthread.cpp:501 #6 0x7f571921e9df in QInotifyFileSystemWatcherEngine::run (this=0x3ae38c0) at io/qfilesystemwatcher_inotify.cpp:248 #7 0x7f5719142b1c in QThreadPrivate::start (arg=0x3ae38c0) at thread/qthread_unix.cpp:338 #8 0x7f5712255e9a in start_thread (arg=0x7f56af120700) at pthread_create.c:308 #9 0x7f5717e4bccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #10 0x in ?? () Thread 2 (Thread 0x7f5696df5700 (LWP 3543)): #0 QEventDispatcherGlib::processEvents (this=0x7f568c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #1 0x7f571923e2ef in QEventLoop::processEvents (this=this@entry=0x7f5696df4dc0, flags=...) at kernel/qeventloop.cpp:149 #2 0x7f571923e578 in QEventLoop::exec (this=0x7f5696df4dc0, flags=...) at kernel/qeventloop.cpp:204 #3 0x7f571913fb40 in QThread::exec (this=) at thread/qthread.cpp:501 #4 0x7f5719142b1c in QThreadPrivate::start (arg=0x4053490) at thread/qthread_unix.cpp:338 #5 0x7f5712255e9a in start_thread (arg=0x7f5696df5700) at pthread_create.c:308 #6 0x7f5717e4bccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #7 0x in ?? () Thread 1 (Thread 0x7f57058b17c0 (LWP 3240)): [KCrash Handler] #6 value (akey=..., this=0x50) at /usr/include/qt4/QtCore/qmap.h:502 #7 KActionCollection::action (this=0x4d9a4f0, name=...) at ../../kdeui/actions/kactioncollection.cpp:136 #8 0x7f56ad614537 in ?? () from /usr/lib/kde4/akregatorpart.so #9 0x7f56ad614268 in ?? () from /usr/lib/kd
[akregator] [Bug 211999] Syncing with Google Reader
https://bugs.kde.org/show_bug.cgi?id=211999 Boerny changed: What|Removed |Added CC||b_sta...@gmx.at --- Comment #19 from Boerny --- I propose to sync with Owncloud News https://github.com/owncloud/apps/tree/master/news. As the developers themselves (http://algorithmsforthekitchen.com/blog/?p=479) proclaimed: Google Reader is dead. Long live ownCloud News! -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 306731] New: Kontact failed to start after login
https://bugs.kde.org/show_bug.cgi?id=306731 Bug ID: 306731 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact failed to start after login Classification: Unclassified OS: Linux Reporter: b_sta...@gmx.at Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.9) KDE Platform Version: 4.9.00 Qt Version: 4.8.2 Operating System: Linux 3.2.0-29-generic x86_64 Distribution: Ubuntu 12.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: After login Kontact is started and it crashes every time. When restarting it works, but sometimes get same error. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f49930a07c0 (LWP 3329))] Thread 5 (Thread 0x7f4976383700 (LWP 3330)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f498f89edec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f498f89ef19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f498ad4de9a in start_thread (arg=0x7f4976383700) at pthread_create.c:308 #4 0x7f49905d04bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 4 (Thread 0x7f4975a6a700 (LWP 3331)): #0 0x7f49905c4b03 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f498a881036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f498a881164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4990d459e6 in QEventDispatcherGlib::processEvents (this=0x7f4978c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f4990d14f22 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f4990d15177 in QEventLoop::exec (this=0x7f4975a69dc0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f4990c14057 in QThread::exec (this=) at thread/qthread.cpp:501 #7 0x7f4990c1707b in QThreadPrivate::start (arg=0x1259020) at thread/qthread_unix.cpp:307 #8 0x7f498ad4de9a in start_thread (arg=0x7f4975a6a700) at pthread_create.c:308 #9 0x7f49905d04bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #10 0x in ?? () Thread 3 (Thread 0x7f49279a1700 (LWP 3343)): #0 0x7f498ad5105d in __pthread_mutex_unlock_usercnt (mutex=, decr=) at pthread_mutex_unlock.c:52 #1 __pthread_mutex_unlock (mutex=0x7f492a60) at pthread_mutex_unlock.c:290 #2 0x7f498a8bc5d1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f498a880b3d in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f498a880fd6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f498a881164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f4990d459e6 in QEventDispatcherGlib::processEvents (this=0x7f4928c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #7 0x7f4990d14f22 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #8 0x7f4990d15177 in QEventLoop::exec (this=0x7f49279a0d90, flags=...) at kernel/qeventloop.cpp:204 #9 0x7f4990c14057 in QThread::exec (this=) at thread/qthread.cpp:501 #10 0x7f4990cf4c2f in QInotifyFileSystemWatcherEngine::run (this=0x342c500) at io/qfilesystemwatcher_inotify.cpp:248 #11 0x7f4990c1707b in QThreadPrivate::start (arg=0x342c500) at thread/qthread_unix.cpp:307 #12 0x7f498ad4de9a in start_thread (arg=0x7f49279a1700) at pthread_create.c:308 #13 0x7f49905d04bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #14 0x in ?? () Thread 2 (Thread 0x7f4926911700 (LWP 3507)): #0 0x7f498ad5105d in __pthread_mutex_unlock_usercnt (mutex=, decr=) at pthread_mutex_unlock.c:52 #1 __pthread_mutex_unlock (mutex=0x7f4918007560) at pthread_mutex_unlock.c:290 #2 0x7f498a8bc5d1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f498a8807e2 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f498a880f5b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f498a881164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f4990d459e6 in QEventDispatcherGlib::processEvents (this=0x7f4918007620, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #7 0x7f4990d14f22 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #8 0x7f4990d15177 in QEventLoop::exec (this=0x7f4926910dc0, flags=...) at kernel/qeventloop.cpp:204 #9 0x7f4990c14057 in QThread::exec (this=) at
[Bug 295484] filtering removes email's content
https://bugs.kde.org/show_bug.cgi?id=295484 Boerny changed: What|Removed |Added CC||b_sta...@gmx.at --- Comment #13 from Boerny --- +1 After upgrade von Kubuntu 11.10 with KDE SC 4.8.0 to 4.8.1 from kubuntu backports ppa. Lost some content when akonadi was first to check emails. When message was read email content was there. After disabling filter "bogofilter Check" everything seams ok. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 263956] Akonadie crash on startup
https://bugs.kde.org/show_bug.cgi?id=263956 Boerny changed: What|Removed |Added CC||b_sta...@gmx.at -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 263956] Akonadie crash on startup
https://bugs.kde.org/show_bug.cgi?id=263956 --- Comment #10 from Boerny 2011-01-28 16:44:04 --- Created an attachment (id=56580) --> (http://bugs.kde.org/attachment.cgi?id=56580) New crash information added by DrKonqi akonadi_davgroupware_resource (0.1) on KDE Platform 4.6.00 (4.6.0) using Qt 4.7.0 using groupdav with egroupware 1.6. Get error when trying to connect. -- Backtrace (Reduced): #6 0x0041c559 in DavItemsListJob::start (this=0x2009e40) at ../../../../resources/dav/common/davitemslistjob.cpp:38 #7 0x0042de85 in DavGroupwareResource::retrieveItems (this=0x1f7ce10, collection=...) at ../../../../resources/dav/resource/davgroupwareresource.cpp:191 #8 0x7fc7ef8096b5 in Akonadi::ResourceBasePrivate::slotSynchronizeCollection (this=, col=) at ../../akonadi/resourcebase.cpp:572 #9 0x7fc7ef80bd25 in Akonadi::ResourceBase::qt_metacall (this=0x1f7ce10, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff09fcce50) at ./moc_resourcebase.cpp:142 #10 0x004339d5 in DavGroupwareResource::qt_metacall (this=0x0, _c=167562704, _id=0, _a=0x201d3f0) at ./davgroupwareresource.moc:103 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 258635] KDE 4.6 and Google Mail: Unknown Mailbox - Messages
https://bugs.kde.org/show_bug.cgi?id=258635 Boerny changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 --- Comment #7 from Boerny 2011-01-10 18:43:23 --- *** This bug has been confirmed by popular vote. *** -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
