[kontact] [Bug 340277] New: Kontact crashed on startup (~CacheLocker)

2014-10-24 Thread Piotr Keplicz 
https://bugs.kde.org/show_bug.cgi?id=340277

Bug ID: 340277
   Summary: Kontact crashed on startup (~CacheLocker)
   Product: kontact
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: mail
  Assignee: kdepim-bugs@kde.org
  Reporter: kepl...@cmc.pl

Application: kontact (4.14.2)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.16.0-23-generic x86_64
Distribution: Ubuntu 14.10

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

Kontact crashed with SIGSEGV on startup (when restoring KDE session).

-- 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 0x7fc5a449f8c0 (LWP 3026))]

Thread 3 (Thread 0x7fc583fda700 (LWP 3079)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc59f19981d in WTF::TCMalloc_PageHeap::scavengerThread() () from
/usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7fc59f199859 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) ()
from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7fc59b8b30a5 in start_thread (arg=0x7fc583fda700) at
pthread_create.c:309
#4  0x7fc5a19c484d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7fc5436d7700 (LWP 3110)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc59eeda20d in JSC::BlockAllocator::blockFreeingThreadMain() () from
/usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7fc59f1c8fd6 in WTF::wtfThreadEntryPoint(void*) () from
/usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7fc59b8b30a5 in start_thread (arg=0x7fc5436d7700) at
pthread_create.c:309
#4  0x7fc5a19c484d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7fc5a449f8c0 (LWP 3026)):
[KCrash Handler]
#6  0x7fc59b8bc838 in _xend () at
../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:33
#7  __lll_unlock_elision (lock=0x7fc5881fb008, private=128) at
../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:29
#8  0x7fc5a26b35b2 in unlock (this=0xc67f80) at
../../kdecore/util/kshareddatacache.cpp:1245
#9  ~CacheLocker (this=synthetic pointer, __in_chrg=optimized out) at
../../kdecore/util/kshareddatacache.cpp:1317
#10 KSharedDataCache::find (this=0xc4b120, key=...,
destination=destination@entry=0x7fff3ac05d90) at
../../kdecore/util/kshareddatacache.cpp:1608
#11 0x7fc5a37fd826 in KIconLoaderPrivate::findCachedPixmapWithPath
(this=0xc4b5d0, key=..., data=..., path=...) at
../../kdeui/icons/kiconloader.cpp:854
#12 0x7fc5a37fdbec in KIconLoader::loadIcon (this=0xc27b80, _name=...,
group=KIconLoader::Small, size=16, state=0, overlays=..., path_store=0x0,
canReturnNull=false) at ../../kdeui/icons/kiconloader.cpp:1149
#13 0x7fc5a37fefff in SmallIcon (name=..., force_size=force_size@entry=0,
state=state@entry=0, overlays=...) at ../../kdeui/icons/kiconloader.cpp:1556
#14 0x7fc53a9df42d in MessageList::Core::Manager::Manager
(this=this@entry=0x1482c40) at ../../messagelist/core/manager.cpp:87
#15 0x7fc53a9e0384 in MessageList::Core::Manager::registerWidget
(pWidget=pWidget@entry=0xd75c50) at ../../messagelist/core/manager.cpp:150
#16 0x7fc53aa1d3fa in MessageList::Core::Widget::Widget (this=0xd75c50,
pParent=optimized out) at ../../messagelist/core/widgetbase.cpp:127
#17 0x7fc53aa3fb6c in MessageList::Widget::Widget (this=0xd75c50,
parent=optimized out) at ../../messagelist/widget.cpp:85
#18 0x7fc53aa36cf9 in MessageList::Pane::createNewTab
(this=this@entry=0x158b0c0) at ../../messagelist/pane.cpp:720
#19 0x7fc53aa393a8 in MessageList::Pane::readConfig
(this=this@entry=0x158b0c0, restoreSession=restoreSession@entry=false) at
../../messagelist/pane.cpp:1087
#20 0x7fc53aa3a0c1 in MessageList::Pane::Pane (this=0x158b0c0,
restoreSession=optimized out, model=optimized out,
selectionModel=optimized out, parent=optimized out) at
../../messagelist/pane.cpp:170
#21 0x7fc53b68604d in CollectionPane::CollectionPane (this=0x158b0c0,
restoreSession=optimized out, model=optimized out,
selectionModel=optimized out, parent=optimized out) at
../../kmail/widgets/collectionpane.cpp:32
#22 0x7fc53b64b079 in KMMainWidget::createWidgets
(this=this@entry=0x144eee0) at ../../kmail/kmmainwidget.cpp:993
#23 0x7fc53b65abf1 in KMMainWidget::KMMainWidget (this=0x144eee0,
parent=optimized out, aGUIClient=0x100ac00, actionCollection=optimized out,
config=...) at ../../kmail/kmmainwidget.cpp:267
#24 0x7fc53b9e3ed1 in KMailPart::KMailPart (this=this@entry=0x100abd0,
parentWidget=parentWidget@entry=0xc8b6b0, parent=parent@entry=0xc8b6b0,
__in_chrg=optimized out, __vtt_parm=optimized out) at

[Akonadi] [Bug 319776] Akonadi crashed, possibly because of sudden lack of network connection, caused by the laptop going into suspend-to-ram

2014-10-24 Thread didi.debian 
https://bugs.kde.org/show_bug.cgi?id=319776

didi.deb...@cknow.org changed:

   What|Removed |Added

 CC||didi.deb...@cknow.org

--- Comment #23 from didi.deb...@cknow.org ---
The problem is still present in 4.14.2.
I'm running Debian Sid (fully up-to-date) on amd64.
I have noticed that with the 4.14 series I get 1-3 times a day that a resource
goes offline, which surprises me since afaik my internet connection is quite
stable (all wired).

And yesterday I got a segmentation fault on one of my IMAP resources.
Backtrace:

Application: m...@email.com of type IMAP E-Mail Server (akonadi_imap_resource),
signal: Segmentation fault
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0x7fd5914b4780 (LWP 2119))]

Thread 2 (Thread 0x7fd577fff700 (LWP 9008)):
#0  __libc_enable_asynccancel () at
../nptl/sysdeps/unix/sysv/linux/x86_64/cancellation.S:65
#1  0x7fd58cce70e2 in poll () at ../sysdeps/unix/syscall-template.S:81
#2  0x7fd58bc74ee4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fd58bc74ffc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fd590abc507 in QEventDispatcherGlib::processEvents
(this=0x7fd56c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7fd590a8bae1 in QEventLoop::processEvents
(this=this@entry=0x7fd577ffee50, flags=...) at kernel/qeventloop.cpp:149
#6  0x7fd590a8be45 in QEventLoop::exec (this=this@entry=0x7fd577ffee50,
flags=...) at kernel/qeventloop.cpp:204
#7  0x7fd590980b89 in QThread::exec (this=optimized out) at
thread/qthread.cpp:538
#8  0x7fd5909833ef in QThreadPrivate::start (arg=0xf92080) at
thread/qthread_unix.cpp:349
#9  0x7fd58c3610a4 in start_thread (arg=0x7fd577fff700) at
pthread_create.c:309
#10 0x7fd58ccefc2d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7fd5914b4780 (LWP 2119)):
[KCrash Handler]
#6  0x7fd590a9f2f8 in QObject::thread (this=this@entry=0xf69020) at
kernel/qobject.cpp:1398
#7  0x7fd590aa74c8 in QObject::QObject (this=0xf6c440, parent=0xf69020) at
kernel/qobject.cpp:752
#8  0x7fd58d88caee in KJob::KJob (this=0xf6c440, parent=optimized out) at
../../kdecore/jobs/kjob.cpp:50
#9  0x7fd58e64e505 in KIMAP::Job::Job (this=0xf6c440, dd=...) at
../../kimap/job.cpp:36
#10 0x7fd58e681f49 in KIMAP::QuotaJobBase::QuotaJobBase (this=0xf6c440,
dd=...) at ../../kimap/quotajobbase.cpp:53
#11 0x7fd58e684a27 in KIMAP::GetQuotaRootJob::GetQuotaRootJob
(this=0xf6c440, session=optimized out) at ../../kimap/getquotarootjob.cpp:47
#12 0x0044083b in RetrieveCollectionMetadataTask::doStart
(this=0xf23e70, session=0xf69020) at
../../../resources/imap/retrievecollectionmetadatatask.cpp:106
#13 0x0043f8b3 in ResourceTask::onSessionRequested (this=0xf23e70,
requestId=optimized out, session=0xf69020, errorCode=0) at
../../../resources/imap/resourcetask.cpp:119
#14 0x0046e01d in ResourceTask::qt_static_metacall (_o=optimized out,
_c=optimized out, _id=optimized out, _a=optimized out) at
moc_resourcetask.cpp:69
#15 0x7fd590aa1f4c in QMetaObject::activate (sender=sender@entry=0xee6bc0,
m=m@entry=0x48f0c0 SessionPool::staticMetaObject,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7fff71d79b50)
at kernel/qobject.cpp:3567
#16 0x0046e192 in SessionPool::sessionRequestDone
(this=this@entry=0xee6bc0, _t1=_t1@entry=834, _t2=_t2@entry=0xf69020,
_t3=_t3@entry=0, _t4=...) at moc_sessionpool.cpp:153
#17 0x0045754a in SessionPool::processPendingRequests (this=0xee6bc0)
at ../../../resources/imap/sessionpool.cpp:257
#18 0x0046e2ed in SessionPool::qt_static_metacall (_o=optimized out,
_c=optimized out, _id=optimized out, _a=optimized out) at
moc_sessionpool.cpp:92
#19 0x7fd590aa6641 in QObject::event (this=0xee6bc0, e=optimized out) at
kernel/qobject.cpp:1222
#20 0x7fd58fde129c in QApplicationPrivate::notify_helper
(this=this@entry=0xd92030, receiver=receiver@entry=0xee6bc0,
e=e@entry=0xf72160) at kernel/qapplication.cpp:4570
#21 0x7fd58fde7da8 in QApplication::notify (this=this@entry=0x7fff71d7a2b0,
receiver=receiver@entry=0xee6bc0, e=e@entry=0xf72160) at
kernel/qapplication.cpp:4356
#22 0x7fd58de8e09a in KApplication::notify (this=0x7fff71d7a2b0,
receiver=0xee6bc0, event=0xf72160) at ../../kdeui/kernel/kapplication.cpp:311
#23 0x7fd590a8cf8d in QCoreApplication::notifyInternal
(this=0x7fff71d7a2b0, receiver=receiver@entry=0xee6bc0,
event=event@entry=0xf72160) at kernel/qcoreapplication.cpp:955
#24 0x7fd590a90821 in sendEvent (event=0xf72160, receiver=0xee6bc0) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#25 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
event_type=event_type@entry=0, data=0xd5b0c0) at

[kmail2] [Bug 340260] Kmail composer's template ODATE/ODATESHORT renders incorrect dates.

2014-10-24 Thread Laurent Montel 
https://bugs.kde.org/show_bug.cgi?id=340260

--- Comment #3 from Laurent Montel mon...@kde.org ---
Please paste or attach an exact message here please.

Because ODATE == original date
see code:

} else if ( cmd.startsWith( QLatin1String( ODATE ) ) ) {
kDebug()  Command: ODATE;
i += strlen( ODATE );
if ( mOrigMsg ) {
const QDateTime date =
mOrigMsg-date()-dateTime().dateTime();
const QString str = KGlobal::locale()-formatDate(
date.date(), KLocale::LongDate );
plainBody.append( str );
const QString body = plainToHtml( str );
htmlBody.append( body );
}

= it will take date from original message.

So I need to have a exact message for testing it.
For me code is ok.

I don't understand how it can take another date.
Template uses currentDate = %DATE or original date %ODATE

Regards

-- 
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 340260] Kmail composer's template ODATE/ODATESHORT renders incorrect dates.

2014-10-24 Thread Cezary Statkiewicz 
https://bugs.kde.org/show_bug.cgi?id=340260

--- Comment #4 from Cezary Statkiewicz ce...@thelirium.net ---
I've attached original date in samples already. Here's your last comment:

Return-Path: bugzilla_nore...@kde.org
Delivered-To: ce...@thelirium.net
Received: from bugs.kde.org (bugs.kde.org [5.9.99.188])
(using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
(No client certificate requested)
by ks388619.kimsufi.com (Postfix) with ESMTPS id 64641801F6
for ce...@thelirium.net; Fri, 24 Oct 2014 11:09:04 +0200 (CEST)
Received: from www-data by bugs.kde.org with local (Exim 4.82)
(envelope-from bugzilla_nore...@kde.org)
id 1Xhaqw-0003O3-0E
for ce...@thelirium.net; Fri, 24 Oct 2014 09:08:10 +
From: Laurent Montel mon...@kde.org
Sender: bugzilla_nore...@kde.org
To: ce...@thelirium.net
Subject: [kmail2] [Bug 340260] Kmail composer's template ODATE/ODATESHORT
 renders incorrect dates.
Date: Fri, 24 Oct 2014 09:08:09 +
Reply-To: bug-cont...@bugs.kde.org
X-Bugzilla-Reason: Reporter
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: kmail2
X-Bugzilla-Component: composer
X-Bugzilla-Version: 4.14.1
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mon...@kde.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: NOR
X-Bugzilla-Assigned-To: kdepim-bugs@kde.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: 
Message-ID: bug-340260-188988-w2hmlab...@http.bugs.kde.org/
In-Reply-To: bug-340260-188...@http.bugs.kde.org/
References: bug-340260-188...@http.bugs.kde.org/
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://bugs.kde.org/
Auto-Submitted: auto-generated
MIME-Version: 1.0

https://bugs.kde.org/show_bug.cgi?id=340260

--- Comment #3 from Laurent Montel mon...@kde.org ---
Please paste or attach an exact message here please.

Because ODATE == original date
see code:

} else if ( cmd.startsWith( QLatin1String( ODATE ) ) ) {
kDebug()  Command: ODATE;
i += strlen( ODATE );
if ( mOrigMsg ) {
const QDateTime date =
mOrigMsg-date()-dateTime().dateTime();
const QString str = KGlobal::locale()-formatDate(
date.date(), KLocale::LongDate );
plainBody.append( str );
const QString body = plainToHtml( str );
htmlBody.append( body );
}

= it will take date from original message.

So I need to have a exact message for testing it.
For me code is ok.

I don't understand how it can take another date.
Template uses currentDate = %DATE or original date %ODATE

Regards

-- 
You are receiving this mail because:
You reported the bug.

---

And here's rendered response beginning:

---
On Friday 11 October 2014 11/10/2014 09:08:09 09:08 Laurent Montel wrote:
 https://bugs.kde.org/show_bug.cgi?id=340260
 
 --- Comment #3 from Laurent Montel mon...@kde.org ---
 Please paste or attach an exact message here please.
 


As you probably noticed, Date rendered is incorrect. Should be 24th Oct, and
it's 11th Oct. 

Here's also my template:


%REM=Default reply all template%-
On %ODATE %ODATESHORT %OTIMELONG %OTIME %OFROMNAME wrote:
%QUOTE
%CURSOR


 I don't understand how it can take another date.
 Template uses currentDate = %DATE or original date %ODATE

Maybe date is parsed incorrectly? But from the other hand, Message date is
displayed correctly in message list and in message view. Also, date skew seems
to be constant, 13 days.

-- 
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 340291] New: no Icons for attachments (and no quick search) after folder-import

2014-10-24 Thread Andreas Zeller 
https://bugs.kde.org/show_bug.cgi?id=340291

Bug ID: 340291
   Summary: no Icons for attachments (and no quick search) after
folder-import
   Product: kmail2
   Version: 4.13.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: message list
  Assignee: kdepim-bugs@kde.org
  Reporter: a-zel...@web.de

After file  mail import on new PC the folders, subfolders, messages and
attachments are transferred successfully but unfortunately there are no
attachment-icons (paper clip) so I can't quick search for mails with
attachment.

I use POP3 but I think that doesn't matter here.

Reproducible: Always

Steps to Reproduce:
1. folder  folder archive (on old Kubunt-14.04-PC)
2. file  mail import  (on new Kubunt-14.04-PC)

Actual Results:  
messages and attachments are imported but no attachment-icons so quick search
for mails with attachment doesn't work

Expected Results:  
messages and attachments are imported and attachment-icons are shown in the
message-list so I can quick search for mails with attachment

Please add the flags while folder import. :)

-- 
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 339576] Can't create new top level IMAP folder

2014-10-24 Thread Jean-Baptiste Mardelle 
https://bugs.kde.org/show_bug.cgi?id=339576

--- Comment #5 from Jean-Baptiste Mardelle j...@kdenlive.org ---
Some additionnal infos:
* When I add a new IMAP account in KMail, I can create new top level folders
* However, closing  re-opening KMail disables the top level folder creation.

Based on my previous comment, I think there is a flag issue with the MERGE
command implementation, but debugging it is beyond my skills.

I can provide test IMAP accounts if a developer needs to reproduce the bug.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
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 335090] Akonadi Dav Resource: Broken State / Unexpected Error 401

2014-10-24 Thread Wolf Drechsel 
https://bugs.kde.org/show_bug.cgi?id=335090

Wolf Drechsel drech...@verkehrsplanung.com changed:

   What|Removed |Added

 CC||drech...@verkehrsplanung.co
   ||m

--- Comment #32 from Wolf Drechsel drech...@verkehrsplanung.com ---
Me too. 
Is there already a possibility to obtain the 4.14 with trusty?

-- 
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 340298] New: kontact gets confused when opened after an Libreoffice is being sent as mail attachment

2014-10-24 Thread Martin Tlustos 
https://bugs.kde.org/show_bug.cgi?id=340298

Bug ID: 340298
   Summary: kontact gets confused when opened after an Libreoffice
is being sent as mail attachment
   Product: kontact
   Version: 4.13.2
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: martin.tlus...@gmail.com

when opening kontact while a document is being sent as email attachment and the
email window is still open, kmail gets opened in a separate window.

Reproducible: Always

Steps to Reproduce:
1. Open Libreoffice, create document, use file - send - send as email
attachment
2. Email windows opens
3. now open kontact

Actual Results:  
kontact opens, but a separate kmail window is opened as well. When selecting
any other component (korganizer, kaddressbook, etc.), kontact behaves normally,
but when selecting kmail, the other window gets activated.

Expected Results:  
kmail should be opened within kontact.

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

[akregator] [Bug 340308] New: akregator (4.14.1) crashes overnight without any particular user action

2014-10-24 Thread gev000 
https://bugs.kde.org/show_bug.cgi?id=340308

Bug ID: 340308
   Summary: akregator (4.14.1) crashes overnight without any
particular user action
   Product: akregator
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: gev...@gmail.com

The whole KDE session, including Akregator was left running overnight. No load
on the machine. Just powered with a few programs on the screen. This morn
ing, I found the Sorry there was a crash for Akregator. All the other
programs and the KDE session itself are fine. This is very typical

The crash can be reproduced every time.



Reproducible: Always

Steps to Reproduce:
1. Start Akregator, read a bit, leave it alone
2.  Go away for some time
3. Come back and find it crashed


Expected Results:  
Akregator should not crash, especially without any user interaction

Application: akregator (4.14.1)
KDE Platform Version: 4.14.1
Qt Version: 4.8.6
Operating System: Linux 3.16.6-200.fc20.x86_64 x86_64
Distribution: Fedora release 20 (Heisenbug)

-- Information about the crash:
- What I was doing when the application crashed:
The whole KDE session, including Akregator was left running overnight. No load
on the machine. Just powered with a few programs on the screen. This morn
ing, I found the Sorry there was a crash for Akregator. All the other
programs and the KDE session itself are fine. This is very typical

The crash can be reproduced every time.

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library /lib64/libthread_db.so.1.
[Current thread is 1 (Thread 0x7f1e245fe940 (LWP 6845))]

Thread 8 (Thread 0x7f1dd3efb700 (LWP 6846)):
#0  0x003197448bf0 in g_main_context_prepare () from
/lib64/libglib-2.0.so.0
#1  0x0031974494bb in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x0031974496dc in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x00319f9b543e in
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) ()
from /lib64/libQtCore.so.4
#4  0x00319f98538f in
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from
/lib64/libQtCore.so.4
#5  0x00319f9856dd in
QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from
/lib64/libQtCore.so.4
#6  0x00319f879e5f in QThread::exec() () from /lib64/libQtCore.so.4
#7  0x00319f87c69f in QThreadPrivate::start(void*) () from
/lib64/libQtCore.so.4
#8  0x003194407ee5 in start_thread () from /lib64/libpthread.so.0
#9  0x0031938f4b8d in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7f1dd1ca4700 (LWP 6896)):
#0  0x00319440bca0 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x0035598bc1bd in JSC::BlockAllocator::blockFreeingThreadMain() () from
/lib64/libQtWebKit.so.4
#2  0x003559baea86 in WTF::wtfThreadEntryPoint(void*) () from
/lib64/libQtWebKit.so.4
#3  0x003194407ee5 in start_thread () from /lib64/libpthread.so.0
#4  0x0031938f4b8d in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f1db9dc9700 (LWP 6915)):
#0  0x00319440bca0 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f1db9e30e39 in PluginRequestProcessor::queueProcessorThread() ()
from /usr/lib64/IcedTeaPlugin.so
#2  0x7f1db9e318d9 in queue_processor(void*) () from
/usr/lib64/IcedTeaPlugin.so
#3  0x003194407ee5 in start_thread () from /lib64/libpthread.so.0
#4  0x0031938f4b8d in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f1db95c8700 (LWP 6916)):
#0  0x00319440bca0 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f1db9e30e39 in PluginRequestProcessor::queueProcessorThread() ()
from /usr/lib64/IcedTeaPlugin.so
#2  0x7f1db9e318d9 in queue_processor(void*) () from
/usr/lib64/IcedTeaPlugin.so
#3  0x003194407ee5 in start_thread () from /lib64/libpthread.so.0
#4  0x0031938f4b8d in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f1db8dc7700 (LWP 6917)):
#0  0x00319440bca0 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f1db9e30e39 in PluginRequestProcessor::queueProcessorThread() ()
from /usr/lib64/IcedTeaPlugin.so
#2  0x7f1db9e318d9 in queue_processor(void*) () from
/usr/lib64/IcedTeaPlugin.so
#3  0x003194407ee5 in start_thread () from /lib64/libpthread.so.0
#4  0x0031938f4b8d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f1da50ff700 (LWP 6974)):
#0  0x0031938ea71d in poll () from /lib64/libc.so.6
#1  0x0031974495b4 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x003197449a3a in g_main_loop_run () from /lib64/libglib-2.0.so.0
#3  0x00319fed0376 in gdbus_shared_thread_func () from
/lib64/libgio-2.0.so.0
#4  0x00319746ea45 in g_thread_proxy ()

[kmail2] [Bug 340312] New: Attachments are not encrypted when automatic encryption is selected

2014-10-24 Thread Mike Schneider 
https://bugs.kde.org/show_bug.cgi?id=340312

Bug ID: 340312
   Summary: Attachments are not encrypted when automatic
encryption is selected
   Product: kmail2
   Version: 4.11.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: crypto
  Assignee: kdepim-bugs@kde.org
  Reporter: mike2.schnei...@gmail.com

When composing a new message, selecting encrypt message will cause
attachments to be also encrypted. This is the correct, expected behavior.

However, if encryption is not manually selected and a message comprising
attachments is sent AND the option automatic encryption (Nachrichten
möglichst automatisch verschlüsseln)is selected and the key of the receiver is
known, a pop-up is displayed, asking whether you want to encrypt the mail. This
is also correct.

HOWEVER: if you select yes, kmail will only encrypt the message body, not the
attachments and will send out the unencrypted attachment without asking further
questions.

Expected behaviour: attachments are also encrypted

Reproducible: Always

Steps to Reproduce:
1. In the settings, under security, select automatic encryption (Nachrichten
möglichst automatisch verschlüsseln)
2. Compose a mail to a sender having a known gpg key
3. Attach a file to the message
4. send the massage, when asked whether you want to encrypt the message, select
yes

Actual Results:  
Message body will be encrypted, attachment will be sent in clear , defeating
the purpose of sending encrypted mails

Expected Results:  
Message body ant attachments are encrypted

-- 
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 340315] New: kmail quicksearch buttons take too much horizontal space

2014-10-24 Thread Martin Steigerwald 
https://bugs.kde.org/show_bug.cgi?id=340315

Bug ID: 340315
   Summary: kmail quicksearch buttons take too much horizontal
space
   Product: kmail2
   Version: 4.14.1
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: message list
  Assignee: kdepim-bugs@kde.org
  Reporter: mar...@lichtvoll.de

Version is 4.14.2 (not yet available in version selector)

Just as demonstrated with screenshots I attach. With active quicksearch in wide
view the kmail quicksearch buttons take too much horizontal space leaving not
enough space for the mailview pane to read some mails without wordwrapping.

Reproducible: Always

Steps to Reproduce:
1. Switch kmail to wide view
2. Access a folder
3. Make message list narrow enough so you see the complete mail in the mail
view pane
4. Do a quick search

Actual Results:  
Message list gets wider and does not leave enough space for message view pane.

Expected Results:  
Message list stays on the same width. Buttons after Nachricht filtern nach
(filter message by) become wordwrapped.

This is with 1920x1080 resolution. If you have some big display with Ultra HD
you may not care :). But IMHO Full HD is also quite a resolution already.

X.org is set to 143 dpi due to display dimensions I measured. Machine is a 15
inch ThinkPad T520 with said Full HD display.

-- 
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 340315] kmail quicksearch buttons take too much horizontal space

2014-10-24 Thread Martin Steigerwald 
https://bugs.kde.org/show_bug.cgi?id=340315

--- Comment #2 from Martin Steigerwald mar...@lichtvoll.de ---
Created attachment 89307
  -- https://bugs.kde.org/attachment.cgi?id=89307action=edit
folder with active quicksearch

-- 
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 340315] kmail quicksearch buttons take too much horizontal space

2014-10-24 Thread Martin Steigerwald 
https://bugs.kde.org/show_bug.cgi?id=340315

--- Comment #1 from Martin Steigerwald mar...@lichtvoll.de ---
Created attachment 89306
  -- https://bugs.kde.org/attachment.cgi?id=89306action=edit
folder without active quicksearch

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

[kaddressbook] [Bug 340316] New: Custom field titles and field types not saved with vCard

2014-10-24 Thread icepacks 
https://bugs.kde.org/show_bug.cgi?id=340316

Bug ID: 340316
   Summary: Custom field titles and field types not saved with
vCard
   Product: kaddressbook
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: icepa...@gmx.com
CC: to...@kde.org

Only the UUID key and value is saved with the vCard, so when imported back in
you lose the title and field type.

For example...
Favorite Color: Blue (text)
Likes Carrots: [x] (boolean)
...imports back as...
c2547fb3-b58a-4290-bb4e-6cbc32ff2a33: Blue (text)
1d01a796-d646-4359-9094-ac448aaa4c80: true (text)

Reproducible: Always

Steps to Reproduce:
1. Create custom fields for a contact, using various types
2. Export vCard
3. Import vCard

Actual Results:  
Imported contact has custom fields with just the UUID as its title instead of
the custom title, and type information is lost and the value always treated as
text.

Expected Results:  
Custom field titles and type information retained on import because they get
exported with the vCard.

Global custom field titles are retained because their titles are stored outside
of the vCard. However, these also are lost if imported into a different
KAddressBook install, etc.

Right now custom fields are stored like this...
X-KADDRESSBOOK-c2547fb3-b58a-4290-bb4e-6cbc32ff2a33:Blue
X-KADDRESSBOOK-1d01a796-d646-4359-9094-ac448aaa4c80:true

Maybe change it to something like this?...
X-KADDRESSBOOK-CF:text:c2547fb3-b58a-4290-bb4e-6cbc32ff2a33:Favorite Color:Blue
X-KADDRESSBOOK-CF:bool:1d01a796-d646-4359-9094-ac448aaa4c80:Likes Carrots:true

-- 
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 299224] kontact crash on quit

2014-10-24 Thread RJVB 
https://bugs.kde.org/show_bug.cgi?id=299224

--- Comment #9 from RJVB rjvber...@gmail.com ---
Created attachment 89309
  -- https://bugs.kde.org/attachment.cgi?id=89309action=edit
New crash information added by DrKonqi

kontact (4.13.3) on KDE Platform 4.14.2 using Qt 4.8.6

- What I was doing when the application crashed:

I quit Kontact through the relevant menu item, in hope of getting rid of the
Retrieving folder content catatonic state

- Unusual behaviour I noticed:

After waking my computer from sleep, mail was being checked for normally and
Kontact showed the progress normally. The message view pane remained frozen on
Retrieving folder contents however, and I don't think new mail actually
showed up in the message list.

-- Backtrace (Reduced):
#5  0x000103dce3c7 in QItemSelectionModel::selectedIndexes
(this=0xc000121a5) at itemviews/qitemselectionmodel.cpp:1432
#6  0x0001206b498e in MailCommon::FolderTreeWidget::selectedCollections
(this=value temporarily unavailable, due to optimizations)
at
/Volumes/Debian/MP6/var/macports/build/_Volumes_Debian_MP6_site-ports_kde_kdepim4/kdepim4/work/kdepim-4.13.3/mailcommon/folder/foldertreewidget.cpp:244
#7  0x00012035d670 in KMMainWidget::updateFolderMenu (this=0x121a38b70)
at
/Volumes/Debian/MP6/var/macports/build/_Volumes_Debian_MP6_site-ports_kde_kdepim4/kdepim4/work/kdepim-4.13.3/kmail/kmmainwidget.cpp:4115
#8  0x00012043fbf2 in KMMainWidget::qt_static_metacall (_o=value
temporarily unavailable, due to optimizations, _c=value temporarily
unavailable, due to optimizations, 
_id=value temporarily unavailable, due to optimizations, _a=value
temporarily unavailable, due to optimizations) at moc_kmmainwidget.cpp:525
[...]
#10 0x000104e67280 in QObject::event (this=0x121a38dc8, e=value
temporarily unavailable, due to optimizations) at kernel/qobject.cpp:1184

-- 
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 299224] kontact crash on quit

2014-10-24 Thread RJVB 
https://bugs.kde.org/show_bug.cgi?id=299224

RJVB rjvber...@gmail.com changed:

   What|Removed |Added

 CC||rjvber...@gmail.com

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

[akregator] [Bug 340308] akregator (4.14.1) crashes overnight without any particular user action

2014-10-24 Thread Christoph Feck 
https://bugs.kde.org/show_bug.cgi?id=340308

Christoph Feck christ...@maxiom.de changed:

   What|Removed |Added

   Severity|normal  |crash
 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Christoph Feck christ...@maxiom.de ---
Crash is caused by QtWebKit. You can avoid it by using KHTML backend instead of
WebKit backend in the web browser.

*** This bug has been marked as a duplicate of bug 317475 ***

-- 
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 340321] New: openPGP/MIME Signatures are invalid

2014-10-24 Thread gigadoc2 
https://bugs.kde.org/show_bug.cgi?id=340321

Bug ID: 340321
   Summary: openPGP/MIME Signatures are invalid
   Product: kmail2
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: crypto
  Assignee: kdepim-bugs@kde.org
  Reporter: gigad...@revreso.de

First I should mention I'm actually using kmail 4.14.2, but the bugtracker
isn't yet aware of this version.

I am signing my mails with openPGP/MIME for some time now, but since recently,
both Enigmail and Sylpheed complain about invalid signatures when recieving
mails. I first thought the fault to be with Enigmail, but after testing with
numerous other Mailcients, only Horde webmail and KMail itself show my
signatures as valid.

After finding a blogpost explaining to me how to verify PGP/MIME with the gpg
cli tool (http://emergent.unpythonic.net/01393247437), I did test some of my
mails with the provided python script and by manually splitting up the mail
into mailpart and signature, and indeed all my mails fail to verify.

Apologies for not providing more information/logs, but I do not know where to
look for it.

Reproducible: Always

Steps to Reproduce:
1. Compose Mail with openPGP/MIME signature
2. Save mail in mbox format
3. Split mail at boundaries
4. Verify with gpg --verify

Actual Results:  
gpg: Signature made Fri Oct 24 23:26:11 2014 CEST using RSA key ID 422DE3FA
gpg: BAD signature from Fabian Bernhard Pack gigad...@revreso.de [ultimate]

Expected Results:  
gpg: Signature made Fri Oct 24 23:26:11 2014 CEST using RSA key ID 422DE3FA
gpg: GOOD signature from Fabian Bernhard Pack gigad...@revreso.de
[ultimate]

$ gpg --version
gpg (GnuPG) 2.0.26
libgcrypt 1.6.2
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, RSA, RSA, ELG, DSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

$ kmail --version
Qt: 4.8.6
KDE: 4.14.2
KMail: 4.14.2

-- 
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 340321] openPGP/MIME Signatures are invalid

2014-10-24 Thread gigadoc2 
https://bugs.kde.org/show_bug.cgi?id=340321

--- Comment #1 from gigad...@revreso.de ---
Created attachment 89310
  -- https://bugs.kde.org/attachment.cgi?id=89310action=edit
example of a PGP/MIME signed mail by kmail

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