[kontact] [Bug 330652] New: Kontact crashed long after closing its window

2014-02-01 Thread Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=330652

Bug ID: 330652
   Summary: Kontact crashed long after closing its window
Classification: Unclassified
   Product: kontact
   Version: 4.12.1
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: k...@kaishome.de

Application: kontact (4.12.1)
KDE Platform Version: 4.12.1
Qt Version: 4.8.5
Operating System: Linux 3.13.1-gentoo x86_64
Distribution: "Gentoo Base System release 2.2"

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

I used Kontact to browser kmail and knode. Many minutes after closing Kontact,
this crash showed up.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7de6f36780 (LWP 5154))]

Thread 4 (Thread 0x7f7de24e1700 (LWP 5155)):
#0  pthread_cond_wait () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00325395590d in WTF::TCMalloc_PageHeap::scavengerThread() () from
/usr/lib64/qt4/libQtWebKit.so.4
#2  0x003253955a19 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) ()
from /usr/lib64/qt4/libQtWebKit.so.4
#3  0x003c4a208f3a in start_thread (arg=0x7f7de24e1700) at
pthread_create.c:308
#4  0x003c49aee2ed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 3 (Thread 0x7f7de1bc8700 (LWP 5157)):
#0  0x003c49ae466d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x003c4e24a33c in g_main_context_poll (n_fds=1, fds=0x7f7ddc0029c0,
timeout=-1, context=0x7f7ddc0009a0, priority=) at
/var/tmp/portage/dev-libs/glib-2.36.4-r1/work/glib-2.36.4/glib/gmain.c:3995
#2  g_main_context_iterate (context=context@entry=0x7f7ddc0009a0,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.36.4-r1/work/glib-2.36.4/glib/gmain.c:3696
#3  0x003c4e24a464 in g_main_context_iteration (context=0x7f7ddc0009a0,
may_block=1) at
/var/tmp/portage/dev-libs/glib-2.36.4-r1/work/glib-2.36.4/glib/gmain.c:3762
#4  0x0035b37abca6 in QEventDispatcherGlib::processEvents
(this=0x7f7ddc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427
#5  0x0035b377c60f in QEventLoop::processEvents
(this=this@entry=0x7f7de1bc7e70, flags=...) at kernel/qeventloop.cpp:149
#6  0x0035b377c898 in QEventLoop::exec (this=0x7f7de1bc7e70, flags=...) at
kernel/qeventloop.cpp:204
#7  0x0035b367f350 in QThread::exec (this=) at
thread/qthread.cpp:536
#8  0x0035b3681acc in QThreadPrivate::start (arg=0x2155ec0) at
thread/qthread_unix.cpp:338
#9  0x003c4a208f3a in start_thread (arg=0x7f7de1bc8700) at
pthread_create.c:308
#10 0x003c49aee2ed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 2 (Thread 0x7f7d8398e700 (LWP 5445)):
#0  pthread_cond_wait () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x0035bcf86d27 in QTWTF::TCMalloc_PageHeap::scavengerThread
(this=0x35bd293640 ) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x0035bcf86d59 in QTWTF::TCMalloc_PageHeap::runScavengerThread
(context=) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x003c4a208f3a in start_thread (arg=0x7f7d8398e700) at
pthread_create.c:308
#4  0x003c49aee2ed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 1 (Thread 0x7f7de6f36780 (LWP 5154)):
[KCrash Handler]
#6  parent (this=0x334b4a0) at
../../include/QtCore/../../src/corelib/kernel/qobject.h:273
#7  parentWidget (this=0x334b4a0) at
../../include/QtGui/../../src/gui/kernel/qwidget.h:1036
#8  QWidget::window (this=0x334b4a0) at kernel/qwidget.cpp:4345
#9  0x7f7ce5ff4e80 in topLevelWidget (this=0x334b4a0) at
/usr/include/qt4/QtGui/qwidget.h:328
#10 KNMainWidget::setStatusMsg (this=0x334b4a0, text=..., id=405) at
/var/tmp/portage/kde-base/knode-4.12.1-r1/work/knode-4.12.1/knode/knmainwidget.cpp:263
#11 0x7f7ce5f83bcc in KNGroup::scoreArticles (this=0x36c1780,
onlynew=) at
/var/tmp/portage/kde-base/knode-4.12.1-r1/work/knode-4.12.1/knode/kngroup.cpp:923
#12 0x7f7ce5f78bbf in KNGroupManager::processJob (this=0x1102b190,
j=0x135c9cd0) at
/var/tmp/portage/kde-base/knode-4.12.1-r1/work/knode-4.12.1/knode/kngroupmanager.cpp:630
#13 0x7f7ce5f68002 in KNJobConsumer::jobDone (this=0x1102b1a0,
j=0x7fff005d9400) at
/var/tmp/portage/kde-base/knode-4.12.1-r1/work/knode-4.12.1/knode/knjobdata.cpp:54
#14 0x7f7ce5f65f1a in KNode::Scheduler::slotJobFinished (this=0x62fc990,
job=0x7fff005d9400) at
/var/tmp/portage/kde-base/knode-4.12.1-r1/work/knode-4.12.1/knode/scheduler.cpp:202
#15 0x0035b3793054 in QMetaObject::activate (sender=0x135c9cd0,
m=, local_signal_index=, argv=0x7fff005d9950)

[kontact] [Bug 330646] New: Kontact crash clicking feeds icon

2014-02-01 Thread guyl
https://bugs.kde.org/show_bug.cgi?id=330646

Bug ID: 330646
   Summary: Kontact crash clicking feeds icon
Classification: Unclassified
   Product: kontact
   Version: 4.11.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: g...@crowhealingnetwork.net

Application: kontact (4.11.3)
KDE Platform Version: 4.11.3
Qt Version: 4.8.4
Operating System: Linux 3.11.0-15-generic x86_64
Distribution: Ubuntu 13.10

-- Information about the crash:
- What I was doing when the application crashed:
After clicking the feeds icon Kontact will crash every 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 0x7f6554be9800 (LWP 6150))]

Thread 5 (Thread 0x7f6534c0d700 (LWP 6151)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f654f9d71cd in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f654f9d7209 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f654c101f6e in start_thread (arg=0x7f6534c0d700) at
pthread_create.c:311
#4  0x7f65521679cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 4 (Thread 0x7f64f430a700 (LWP 6152)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f654f717bbd in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f654fa06a76 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f654c101f6e in start_thread (arg=0x7f64f430a700) at
pthread_create.c:311
#4  0x7f65521679cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 3 (Thread 0x7f64e4b66700 (LWP 6159)):
#0  0x7f654c105043 in __pthread_mutex_unlock_usercnt (mutex=0x7f64d8000a60,
decr=1) at pthread_mutex_unlock.c:41
#1  0x7f654bc693d1 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f654bc295b6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f654bc297ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f65528e0a76 in QEventDispatcherGlib::processEvents
(this=0x7f64d80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#5  0x7f65528b25ef in QEventLoop::processEvents
(this=this@entry=0x7f64e4b65d30, flags=...) at kernel/qeventloop.cpp:149
#6  0x7f65528b28e5 in QEventLoop::exec (this=this@entry=0x7f64e4b65d30,
flags=...) at kernel/qeventloop.cpp:204
#7  0x7f65527b188f in QThread::exec (this=this@entry=0x2385a60) at
thread/qthread.cpp:542
#8  0x7f6552893d13 in QInotifyFileSystemWatcherEngine::run (this=0x2385a60)
at io/qfilesystemwatcher_inotify.cpp:265
#9  0x7f65527b3f2f in QThreadPrivate::start (arg=0x2385a60) at
thread/qthread_unix.cpp:338
#10 0x7f654c101f6e in start_thread (arg=0x7f64e4b66700) at
pthread_create.c:311
#11 0x7f65521679cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 2 (Thread 0x7f64df197700 (LWP 6161)):
#0  0x7f654bc690ed in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f654bc69399 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f654bc28c17 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f654bc295c3 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f654bc297ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f65528e0a76 in QEventDispatcherGlib::processEvents
(this=0x7f64cc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x7f65528b25ef in QEventLoop::processEvents
(this=this@entry=0x7f64df196d70, flags=...) at kernel/qeventloop.cpp:149
#7  0x7f65528b28e5 in QEventLoop::exec (this=this@entry=0x7f64df196d70,
flags=...) at kernel/qeventloop.cpp:204
#8  0x7f65527b188f in QThread::exec (this=) at
thread/qthread.cpp:542
#9  0x7f65527b3f2f in QThreadPrivate::start (arg=0x1c747f0) at
thread/qthread_unix.cpp:338
#10 0x7f654c101f6e in start_thread (arg=0x7f64df197700) at
pthread_create.c:311
#11 0x7f65521679cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 1 (Thread 0x7f6554be9800 (LWP 6150)):
[KCrash Handler]
#6  __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:2495
#7  0x7f64c89bb5d6 in memcpy (__len=, __src=,
__dest=) at /usr/include/x86_64-linux-gnu/bits/string3.h:51
#8  c4_Bytes::_MakeCopy (this=0x7fffd8b792c0) at
../../../../akregator/plugins/mk4storage/metakit/src/table.cpp:138
#9  0x7f64c89b1b53 in c4_FormatB::SetOne (this=0xd59a9b0, index_=0,
xbuf_=..., ignoreMemos_=ignoreMemos_@entry=false) at
../../../../akregator/plugins/mk4storage/

[kleopatra] [Bug 330638] New: Kleopatra only displays short Key-IDs.

2014-02-01 Thread Samir Nassar
https://bugs.kde.org/show_bug.cgi?id=330638

Bug ID: 330638
   Summary: Kleopatra only displays short Key-IDs.
Classification: Unclassified
   Product: kleopatra
   Version: 2.2.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: sa...@samirnassar.com
CC: m...@kde.org

Kleopatra only displays short Key-IDs.

Reproducible: Always

Steps to Reproduce:
1. Open Kleopatra
2. Look at Key-ID column
Actual Results:  
Key-IDs in Key-ID column are short (8-bit).

Expected Results:  
Kleoptra should have a facility to toggle different Key-ID displays such as
'0xlong' or 'long'. This is a settig that can be read from gpg.conf

-- 
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 330637] New: Imap resource crashes after moving messages

2014-02-01 Thread Luis Silva
https://bugs.kde.org/show_bug.cgi?id=330637

Bug ID: 330637
   Summary: Imap resource crashes after moving messages
Classification: Unclassified
   Product: Akonadi
   Version: 4.12
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: IMAP resource
  Assignee: chrig...@fastmail.fm
  Reporter: lacsi...@gmail.com
CC: kdepim-bugs@kde.org, vkra...@kde.org

Application: akonadi_imap_resource (4.12)
KDE Platform Version: 4.12.0 (Compiled from sources)
Qt Version: 4.8.4
Operating System: Linux 3.11.0-15-generic i686
Distribution: Ubuntu 13.10

-- Information about the crash:
- What I was doing when the application crashed:
I moved a few e-mail between two imap accounts. The resource responsible for
the receiving account started crashing after that. Note that the receiving
account is an Outlook web access account mimicing imap.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Glasgow Uni of type IMAP E-Mail Server (akonadi_imap_resource),
signal: Aborted
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb4938740 (LWP 14901))]

Thread 2 (Thread 0xb1fd5b40 (LWP 14987)):
#0  0xb7701424 in __kernel_vsyscall ()
#1  0xb56e64d2 in clock_gettime (clock_id=1, tp=0xb1fd4ff8) at
../sysdeps/unix/clock_gettime.c:115
#2  0xb718d3ec in do_gettime (frac=0xb1fd4ff0, sec=0xb1fd4fe8) at
tools/qelapsedtimer_unix.cpp:123
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#4  0xb7272fd2 in updateCurrentTime (this=0xb1602074) at
kernel/qeventdispatcher_unix.cpp:354
#5  QTimerInfoList::timerWait (this=0xb1602074, tm=...) at
kernel/qeventdispatcher_unix.cpp:461
#6  0xb727167b in timerSourcePrepareHelper (src=,
timeout=0xb1fd50ec) at kernel/qeventdispatcher_glib.cpp:136
#7  0xb727170d in timerSourcePrepare (source=0xb1602040, timeout=0xb1fd50ec) at
kernel/qeventdispatcher_glib.cpp:169
#8  0xb53d8143 in g_main_context_prepare () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#9  0xb53d8a5f in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#10 0xb53d8ca8 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#11 0xb72718df in QEventDispatcherGlib::processEvents (this=0xb1600468,
flags=...) at kernel/qeventdispatcher_glib.cpp:426
#12 0xb72409f3 in QEventLoop::processEvents (this=this@entry=0xb1fd5258,
flags=...) at kernel/qeventloop.cpp:149
#13 0xb7240d19 in QEventLoop::exec (this=this@entry=0xb1fd5258, flags=...) at
kernel/qeventloop.cpp:204
#14 0xb712fe3d in QThread::exec (this=this@entry=0x8bbc818) at
thread/qthread.cpp:542
#15 0xb712ff8b in QThread::run (this=0x8bbc818) at thread/qthread.cpp:609
#16 0xb713272f in QThreadPrivate::start (arg=0x8bbc818) at
thread/qthread_unix.cpp:338
#17 0xb5507d78 in start_thread (arg=0xb1fd5b40) at pthread_create.c:311
#18 0xb56d301e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131

Thread 1 (Thread 0xb4938740 (LWP 14901)):
[KCrash Handler]
#7  0xb7701424 in __kernel_vsyscall ()
#8  0xb560faff in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#9  0xb5613083 in __GI_abort () at abort.c:90
#10 0xb7127993 in qt_message_output (msgType=QtFatalMsg, buf=0x8cb7048 "ASSERT:
\"!isEmpty()\" in file /usr/include/qt4/QtCore/qlist.h, line 284") at
global/qglobal.cpp:2347
#11 0xb7127d47 in qt_message (msgType=msgType@entry=QtFatalMsg,
msg=msg@entry=0xb72a9aec "ASSERT: \"%s\" in file %s, line %d",
ap=ap@entry=0xbfccc6e4 "db\v\b$b\v\b\034\001") at global/qglobal.cpp:2393
#12 0xb7128278 in qFatal (msg=msg@entry=0xb72a9aec "ASSERT: \"%s\" in file %s,
line %d") at global/qglobal.cpp:2576
#13 0xb71282f5 in qt_assert (assertion=0x80b6264 "!isEmpty()", file=0x80b6224
"/usr/include/qt4/QtCore/qlist.h", line=284) at global/qglobal.cpp:2021
#14 0x0808d8c5 in QList::last (this=0x8c869a0) at
/usr/include/qt4/QtCore/qlist.h:284
#15 0x0808d17a in MoveItemsTask::recordNewUid (this=0x8c86978) at
/home/lacsilva/Development/kdepim.d/kdepim-runtime/resources/imap/moveitemstask.cpp:290
#16 0x0808cdc4 in MoveItemsTask::onSearchDone (this=0x8c86978, job=0x8cb2620)
at
/home/lacsilva/Development/kdepim.d/kdepim-runtime/resources/imap/moveitemstask.cpp:242
#17 0x080a6784 in MoveItemsTask::qt_static_metacall (_o=_o@entry=0x8c86978,
_c=_c@entry=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfccc8e8) at
/home/lacsilva/Development/kdepim.d/kdepim-runtime/BUILD-DEBUG/resources/imap/moc_moveitemstask.cpp:60
#18 0xb7256fc7 in QMetaObject::activate (sender=sender@entry=0x8cb2620,
m=m@entry=0xb5b464cc ,
local_signal_index=local_signal_index@entry=3, argv=argv@entry=0xbfccc8e8) at
kernel/qobject.cpp:3539
#19 0xb59a21e5 in KJob::result (this=this@entry=0x8cb2620,
_t1=_t1@entry=0x8cb2620) at ./kjob.moc:208
#20 0xb59a2232 in KJob::emitResult (this=0x8cb2620) at
../../kdecore/jobs/kjob.cpp:318
#21 0xb6475c55 in KIMAP::Job::handl

[kdepim] [Bug 279749] Kontact crashed when trying to open gpg encripted email

2014-02-01 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=279749

--- Comment #38 from Albert Astals Cid  ---
I can try giving it a try next week.

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


[kdepim] [Bug 279749] Kontact crashed when trying to open gpg encripted email

2014-02-01 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=279749

--- Comment #37 from Laurent Montel  ---
Another guy can confirm that this patch fixes problem ?

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


[kdepim] [Bug 326530] can't add owncloud resources if shared calendars exist on owncloud server

2014-02-01 Thread Martin Koller
https://bugs.kde.org/show_bug.cgi?id=326530

Martin Koller  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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


[kdepim] [Bug 326530] can't add owncloud resources if shared calendars exist on owncloud server

2014-02-01 Thread Johannes Rohr
https://bugs.kde.org/show_bug.cgi?id=326530

--- Comment #2 from Johannes Rohr  ---
(In reply to comment #1)
> Is this probably the same issue with duplicate names of addressbooks or
> calendars ?
> see bug #284783

Well, I don't know. Meanwhile it seems to be working. I have upgraded Owncloud
to version 6.0.1 now. So I suppose this can be closed, but I don't know that
the appropriate status would be..

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