[akregator] [Bug 336417] New: Akregator crashes when being closed
https://bugs.kde.org/show_bug.cgi?id=336417 Bug ID: 336417 Summary: Akregator crashes when being closed Classification: Unclassified Product: akregator Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: tittiatc...@gmail.com Application: akregator (4.14 pre) KDE Platform Version: 4.13.60 Qt Version: 4.8.6 Operating System: Linux 3.15.0-3.gcc07b60-desktop x86_64 Distribution: "openSUSE 13.2 Milestone 0 (Harlequin) (x86_64)" -- Information about the crash: Closing akregator causes akregator to crash. Akregator functions normally without any issues until I close the window. The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". To enable execution of this file add add-auto-load-safe-path /usr/lib64/libstdc++.so.6.0.19-gdb.py line to your configuration file "/home/hq06/.gdbinit". To completely disable this security protection add set auto-load safe-path / line to your configuration file "/home/hq06/.gdbinit". For more information about this security protection see the "Auto-loading safe path" section in the GDB manual. E.g., run from the shell: info "(gdb)Auto-loading safe path" [KCrash Handler] #5 0x7f8c57bd3dd7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4 #6 0x7f8c58ca1a62 in Akregator::Frame::signalCompleted(Akregator::Frame*) () from /usr/lib64/libakregatorprivate.so.4 #7 0x7f8c58c988c8 in Akregator::Frame::slotSetState(Akregator::Frame::State) () from /usr/lib64/libakregatorprivate.so.4 #8 0x7f8c40c08e47 in Akregator::MainWidget::slotFetchingStopped() () from /usr/lib64/kde4/akregatorpart.so #9 0x7f8c57bd404a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4 #10 0x7f8c58c98349 in Akregator::FetchQueue::slotAbort() () from /usr/lib64/libakregatorprivate.so.4 #11 0x7f8c58c983ba in Akregator::FetchQueue::~FetchQueue() () from /usr/lib64/libakregatorprivate.so.4 #12 0x7f8c58c98429 in Akregator::FetchQueue::~FetchQueue() () from /usr/lib64/libakregatorprivate.so.4 #13 0x7f8c58c973ef in Akregator::Kernel::~Kernel() () from /usr/lib64/libakregatorprivate.so.4 #14 0x7f8c5626ff99 in __run_exit_handlers () from /lib64/libc.so.6 #15 0x7f8c5626ffe5 in exit () from /lib64/libc.so.6 #16 0x7f8c56259b0c in __libc_start_main () from /lib64/libc.so.6 #17 0x0040872b in _start () Possible duplicates by query: bug 318038. Reported using DrKonqi -- 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
[kontact] [Bug 309981] Kontact crashed after returning from sleep
https://bugs.kde.org/show_bug.cgi?id=309981 Giuseppe Vinci changed: What|Removed |Added CC|giuseppe.vi...@gmx.net | --- Comment #25 from Giuseppe Vinci --- I removed my name from the CC list because I haven't yet any experience about Kontact crashing after returning from sleep with my current version 4.13.1 -- 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
[kmail] [Bug 203251] column size kmail list
https://bugs.kde.org/show_bug.cgi?id=203251 Matt Stevens changed: What|Removed |Added CC||mattdaw...@gmail.com --- Comment #17 from Matt Stevens --- Can confirm this is still an issue using 4.13.1 under ubuntu trusty LTS -- 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
[kmail2] [Bug 316153] can't move or delete messages in imap inbox
https://bugs.kde.org/show_bug.cgi?id=316153 --- Comment #15 from Maciej Mrozowski --- Let me guess - you have 'disconnected IMAP' enabled. ? -- 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
[Akonadi] [Bug 334929] imap resource has a pending task and crashes repetitively
https://bugs.kde.org/show_bug.cgi?id=334929 --- Comment #3 from Feth Arezki --- (In reply to comment #2) > Do you still have this issue? Could you try to update to KDE 4.13 ? Now running 4.13.1. I believe I still have akonadi issues, but certainly this one vanished. Thanks ! -- 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
[kleopatra] [Bug 336392] New: Kleopatra crashed when searching "Gael"
https://bugs.kde.org/show_bug.cgi?id=336392 Bug ID: 336392 Summary: Kleopatra crashed when searching "Gael" Classification: Unclassified Product: kleopatra Version: 2.2.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: j...@ms63.hinet.net CC: m...@kde.org Application: kleopatra (2.2.0) KDE Platform Version: 4.12.5 Qt Version: 4.8.6 Operating System: Linux 3.14.7-200.fc20.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I clicked "Lookup Certificates on Server", searching "Gael", and then it crashed. However it worked when I searched with other strings, such as "jdh8" and "Jitse". The crash can be reproduced every time. -- Backtrace: Application: Kleopatra (kleopatra), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 81T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f53ea49d8c0 (LWP 6460))] Thread 5 (Thread 0x7f53de601700 (LWP 6463)): #0 0x0036d508a2ea in g_mutex_get_impl () from /lib64/libglib-2.0.so.0 #1 0x0036d508a599 in g_mutex_lock () from /lib64/libglib-2.0.so.0 #2 0x0036d504948d in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x0036d50496dc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x00356a1b5a7e in QEventDispatcherGlib::processEvents (this=0x7f53d80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #5 0x00356a18595f in QEventLoop::processEvents (this=this@entry=0x7f53de600cc0, flags=...) at kernel/qeventloop.cpp:149 #6 0x00356a185cad in QEventLoop::exec (this=this@entry=0x7f53de600cc0, flags=...) at kernel/qeventloop.cpp:204 #7 0x00356a079e8f in QThread::exec (this=this@entry=0x164a6f0) at thread/qthread.cpp:538 #8 0x00356a1662e3 in QInotifyFileSystemWatcherEngine::run (this=0x164a6f0) at io/qfilesystemwatcher_inotify.cpp:265 #9 0x00356a07c6bf in QThreadPrivate::start (arg=0x164a6f0) at thread/qthread_unix.cpp:349 #10 0x0036d3007f33 in start_thread (arg=0x7f53de601700) at pthread_create.c:309 #11 0x0036d28f4ded in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 4 (Thread 0x7f53dde00700 (LWP 6505)): #0 0x00356a1b7333 in constBegin (this=0x7f53d0001220) at ../../src/corelib/tools/qlist.h:269 #1 QTimerInfoList::timerWait (this=0x7f53d0001220, tm=...) at kernel/qeventdispatcher_unix.cpp:465 #2 0x00356a1b590c in timerSourcePrepareHelper (src=, timeout=0x7f53dddffaf4) at kernel/qeventdispatcher_glib.cpp:143 #3 0x00356a1b59d5 in timerSourcePrepare (source=, timeout=) at kernel/qeventdispatcher_glib.cpp:176 #4 0x0036d5048bed in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #5 0x0036d50494bb in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #6 0x0036d50496dc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #7 0x00356a1b5a7e in QEventDispatcherGlib::processEvents (this=0x7f53d0002bd0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #8 0x00356a18595f in QEventLoop::processEvents (this=this@entry=0x7f53dddffcc0, flags=...) at kernel/qeventloop.cpp:149 #9 0x00356a185cad in QEventLoop::exec (this=this@entry=0x7f53dddffcc0, flags=...) at kernel/qeventloop.cpp:204 #10 0x00356a079e8f in QThread::exec (this=this@entry=0x1693570) at thread/qthread.cpp:538 #11 0x00356a1662e3 in QInotifyFileSystemWatcherEngine::run (this=0x1693570) at io/qfilesystemwatcher_inotify.cpp:265 #12 0x00356a07c6bf in QThreadPrivate::start (arg=0x1693570) at thread/qthread_unix.cpp:349 #13 0x0036d3007f33 in start_thread (arg=0x7f53dde00700) at pthread_create.c:309 #14 0x0036d28f4ded in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7f53dc8e6700 (LWP 6506)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238 #1 0x00356a07cbd4 in wait (time=2000, this=0x1631da0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=this@entry=0x164e238, mutex=mutex@entry=0x164e230, time=time@entry=2000) at thread/qwaitcondition_unix.cpp:158 #3 0x005c7400 in (anonymous namespace)::ReaderStatusThread::run (this=0x164e220) at /usr/src/debug/kdepim-4.12.5/kleopatra/smartcard/readerstatus.cpp:560 #4 0x00356a07c6bf in QThreadPrivate::start (arg=0x164e220) at thread/qthread_unix.cpp:349 #5 0x0036d3007f33 in start_thread (arg=0x7f53dc8e6700) at pthread_create.c:309 #6 0x0036d28f4ded in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7f53ceca8700 (LWP 6535)): [KCrash Handler] #6 gpg_keylist_preprocess (line=, r_line=0x7f53ceca77e0) at engine-gpg.c:2108
[kontact] [Bug 336389] New: It allways crashed after attached a document, since last KDE Update i can not attached a document
https://bugs.kde.org/show_bug.cgi?id=336389 Bug ID: 336389 Summary: It allways crashed after attached a document, since last KDE Update i can not attached a document Classification: Unclassified Product: kontact Version: 4.13.1 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: stefan.mueller...@gmx.de Application: kontact (4.13.1) KDE Platform Version: 4.13.1 Qt Version: 4.8.6 Operating System: Linux 3.13.0-29-generic x86_64 Distribution: Ubuntu 14.04 LTS -- Information about the crash: - What I was doing when the application crashed: Start Kmail, then press "New E-Mail", then "Attachement", pick a PDF document, then pushed the Button "attach" and here Kmail crashed 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 0x7fc2ebd0c800 (LWP 4683))] Thread 7 (Thread 0x7fc2cb888700 (LWP 4684)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc2e6aaf81d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fc2e6aaf859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fc2e31d1182 in start_thread (arg=0x7fc2cb888700) at pthread_create.c:312 #4 0x7fc2e928330d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 6 (Thread 0x7fc28af85700 (LWP 4685)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc2e67f020d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fc2e6adefd6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fc2e31d1182 in start_thread (arg=0x7fc28af85700) at pthread_create.c:312 #4 0x7fc2e928330d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 5 (Thread 0x7fc27b55b700 (LWP 4688)): #0 0x7fff85b58a1f in ?? () #1 0x7fc27b55ab70 in ?? () #2 0x in ?? () Thread 4 (Thread 0x7fc27944c700 (LWP 4689)): #0 __GI___pthread_mutex_lock (mutex=0x7fc26c000a60) at ../nptl/pthread_mutex_lock.c:161 #1 0x7fc2e2d33991 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc2e2cf11f8 in g_main_context_release () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc2e2cf1f91 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc2e2cf20ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc2e99fc7be in QEventDispatcherGlib::processEvents (this=0x7fc26c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #6 0x7fc2e99ce0af in QEventLoop::processEvents (this=this@entry=0x7fc27944bda0, flags=...) at kernel/qeventloop.cpp:149 #7 0x7fc2e99ce3a5 in QEventLoop::exec (this=this@entry=0x7fc27944bda0, flags=...) at kernel/qeventloop.cpp:204 #8 0x7fc2e98cac5f in QThread::exec (this=this@entry=0x281bdd0) at thread/qthread.cpp:537 #9 0x7fc2e99af823 in QInotifyFileSystemWatcherEngine::run (this=0x281bdd0) at io/qfilesystemwatcher_inotify.cpp:265 #10 0x7fc2e98cd32f in QThreadPrivate::start (arg=0x281bdd0) at thread/qthread_unix.cpp:349 #11 0x7fc2e31d1182 in start_thread (arg=0x7fc27944c700) at pthread_create.c:312 #12 0x7fc2e928330d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7fc26bfff700 (LWP 4701)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc281c5bffb in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x7fc281c5c039 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x7fc2e31d1182 in start_thread (arg=0x7fc26bfff700) at pthread_create.c:312 #4 0x7fc2e928330d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7fc1ea750700 (LWP 4704)): #0 0x7fc2e2cf1694 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fc2e2cf1f03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc2e2cf20ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc2e99fc7be in QEventDispatcherGlib::processEvents (this=0x7fc1dc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #4 0x7fc2e99ce0af in QEventLoop::processEvents (this=this@entry=0x7fc1ea74fda0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fc2e99ce3a5 in QEventLoop::exec (this=this@entry=0x7fc1ea74fda0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fc2e98cac5f in QThread::exec (this=this@entry=0x4c0bd10) at thread/qthread.cpp:537 #7 0x7fc2e99af823 in QInotifyFileSystemWatcherEngine::run (this=0x4c0bd10) at io/qf
[kmail2] [Bug 316153] can't move or delete messages in imap inbox
https://bugs.kde.org/show_bug.cgi?id=316153 --- Comment #14 from zucco.h...@gmail.com --- The deleted message reapears in Akonadi console after akonadictl restart. With the new Id and same Remote ID. -- 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
[kmail2] [Bug 316153] can't move or delete messages in imap inbox
https://bugs.kde.org/show_bug.cgi?id=316153 zucco.h...@gmail.com changed: What|Removed |Added CC||zucco.h...@gmail.com --- Comment #13 from zucco.h...@gmail.com --- Kmail 4.13.0 (Kubuntu back port). Delete or move message from IMAP Inbox folder removes message temporarly (cca 2 s) then it appears again as gray/shadow. Message is not in Inbox in Akonadi (Akonadi Console -> Browser -> Inbox : I can see preview and next messages only, not the delete one). The move message between non-Inbox (e.g. Archive to Thrash on IMAP) folder works well. -- 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
[kdepimlibs] [Bug 336386] New: Support for freebusy FBTYPE
https://bugs.kde.org/show_bug.cgi?id=336386
Bug ID: 336386
Summary: Support for freebusy FBTYPE
Classification: Unclassified
Product: kdepimlibs
Version: GIT (master)
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: kcalcore
Assignee: kdepim-bugs@kde.org
Reporter: kna...@kolabsys.com
Free Busy support different types in a freebusy file. With the additional
fbtype you can deside, if a attendee is tentative or busy.
Reproducible: Always
[copied form RFC 5545]
Parameter Name: FBTYPE
Purpose: To specify the free or busy time type.
Format Definition: This property parameter is defined by the
following notation:
fbtypeparam= "FBTYPE" "=" ("FREE" / "BUSY"
/ "BUSY-UNAVAILABLE" / "BUSY-TENTATIVE"
/ x-name
; Some experimental iCalendar free/busy type.
/ iana-token)
; Some other IANA-registered iCalendar free/busy type.
Description: This parameter specifies the free or busy time type.
The value FREE indicates that the time interval is free for
scheduling. The value BUSY indicates that the time interval is
busy because one or more events have been scheduled for that
interval. The value BUSY-UNAVAILABLE indicates that the time
interval is busy and that the interval can not be scheduled. The
value BUSY-TENTATIVE indicates that the time interval is busy
because one or more events have been tentatively scheduled for
that interval. If not specified on a property that allows this
parameter, the default is BUSY. Applications MUST treat x-name
and iana-token values they don't recognize the same way as they
would the BUSY value.
Example: The following is an example of this parameter on a
"FREEBUSY" property.
FREEBUSY;FBTYPE=BUSY:19980415T133000Z/19980415T17Z
--
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
