[kdepimlibs] [Bug 312840] Procedure to fix and upload namedays holidays for the Greek language

2014-05-14 Thread auxsvr
https://bugs.kde.org/show_bug.cgi?id=312840

aux...@gmail.com changed:

   What|Removed |Added

 CC||aux...@gmail.com

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


[Akonadi] [Bug 294486] Korganiser crashes on start

2014-05-14 Thread VEC
https://bugs.kde.org/show_bug.cgi?id=294486

VEC hola...@yahoo.es changed:

   What|Removed |Added

 CC||hola...@yahoo.es

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


[Akonadi] [Bug 294486] Korganiser crashes on start

2014-05-14 Thread VEC
https://bugs.kde.org/show_bug.cgi?id=294486

--- Comment #7 from VEC hola...@yahoo.es ---
Created attachment 86624
  -- https://bugs.kde.org/attachment.cgi?id=86624action=edit
New crash information added by DrKonqi

akonadi_kcal_resource (4.12) on KDE Platform 4.12.4 using Qt 4.8.5

- What I was doing when the application crashed: 
Nothing special. It just crashes when periodic update (sync) of remote calendar
 (traditional type calendar) is set.

- Custom settings of the application:

-- Backtrace (Reduced):
#5  0x003268a54524 in KCal::Incidence::removeRelation(KCal::Incidence*) ()
from /usr/lib64/libkcal.so.4
#6  0x003268a54945 in KCal::Incidence::~Incidence() () from
/usr/lib64/libkcal.so.4
#7  0x003268a59da9 in KCal::Event::~Event() () from /usr/lib64/libkcal.so.4
#8  0x00411c39 in Akonadi::Payloadboost::shared_ptrKCal::Incidence
::~Payload() ()
#9  0x00326652a6fe in Akonadi::ItemPrivate::~ItemPrivate() () from
/usr/lib64/libakonadi-kde.so.4

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


[Akonadi] [Bug 295532] Akonadi hogs cpu when updating remote ics feed from google

2014-05-14 Thread Fabian
https://bugs.kde.org/show_bug.cgi?id=295532

Fabian mays...@web.de changed:

   What|Removed |Added

 CC||mays...@web.de

--- Comment #15 from Fabian mays...@web.de ---
I can confirm this issue in KDE 4.13. This periodic restart of the akonadi
source makes korgac eat all my memory (16 gb). After a few hours working my
system starts swapping, which is really annoying. If I restart korgac it
constantly consumes memory and has a CPU usage of a few percent. If I delete my
remote ical calenders this does not appear. 
As a workaround I can use the legacy KDE resource instead of native akonadi
resources. But there I got every now and then annoying error messages because
of a connection break down. 
The calendars are provided by a horde system. They are shared by another user,
so I can't import them using the caldav protocol, since this is not supported
yet. 
Sometimes this problem does not appear immediately after adding the calenders.
And especially on my kubuntu system with the same KDE version and the same
calenders I have never seen korgac eat all my memory. But on this system I got
a message at startup that's telling me there is a pending upload to this
calender. 
I can try to give more and more detailed information about this issue next
week. Any hints about collecting useful information are welcome!

-- 
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 334740] New: kmail doesn't handle failed archiving attempts well.

2014-05-14 Thread qqqqqqqqq9
https://bugs.kde.org/show_bug.cgi?id=334740

Bug ID: 334740
   Summary: kmail doesn't handle failed archiving attempts well.
Classification: Unclassified
   Product: kmail2
   Version: 4.13.0
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: misc
  Assignee: kdepim-bugs@kde.org
  Reporter: qqq...@gmeyer.df-kunde.de

Be the archiving interval 7 days.
When archiving fails the following happens:

1. A corrupted archive is produced.
2. The archiving status is set do done
3. The next archiving will be started in 7 days.
4. What will happen if the maximum number of kept archives is 1? Will kmail
discard the good one and keep the corrupted?

A better handling would be:

1. Delete the corrupted archive
2. Retry after sometime (e.g. 3 h)


Reproducible: Didn't try

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


[kleopatra] [Bug 226630] kwatchgnupg appends invalid options to ~/.gnupg/gpg.conf

2014-05-14 Thread Nick
https://bugs.kde.org/show_bug.cgi?id=226630

Nick nickmdow...@gmail.com changed:

   What|Removed |Added

 CC||nickmdow...@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


[kmail2] [Bug 63780] Auto-render HTML for certain email addresses

2014-05-14 Thread Orion
https://bugs.kde.org/show_bug.cgi?id=63780

--- Comment #40 from Orion orion200...@yahoo.co.uk ---
Great news! It could not be backported to 4.13.2 or something? If I dont keep
an eye on it this can make KMail/Kontact chew up close to 1 Gb RAM

-- 
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 334753] New: Kmail Crashes when using Reply All

2014-05-14 Thread Scott
https://bugs.kde.org/show_bug.cgi?id=334753

Bug ID: 334753
   Summary: Kmail Crashes when using Reply All
Classification: Unclassified
   Product: kmail2
   Version: 4.10.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: scot...@worldsofwar.co.uk

Application: kmail (4.10.5)
KDE Platform Version: 4.10.5 release 1
Qt Version: 4.8.4
Operating System: Linux 3.7.10-1.16-desktop x86_64
Distribution: openSUSE 12.3 (x86_64)

-- Information about the crash:
- Custom settings of the application:

Runing X11 forwaring over ssh.  This makes the crash reproduceable every time,
Kmail crashes when it tries to start

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library /lib64/libthread_db.so.1.
[KCrash Handler]
#6  0x7f79312333d5 in raise () from /lib64/libc.so.6
#7  0x7f7931234858 in abort () from /lib64/libc.so.6
#8  0x7f793127344b in __libc_message () from /lib64/libc.so.6
#9  0x7f7931278fc6 in malloc_printerr () from /lib64/libc.so.6
#10 0x7f7931279d43 in _int_free () from /lib64/libc.so.6
#11 0x7f79323dd095 in free (alignment=8, x=optimized out) at
../../src/corelib/tools/qvector.h:99
#12 free (x=optimized out, this=optimized out) at
../../src/corelib/tools/qvector.h:468
#13 operator= (v=..., this=0x1e501d0) at ../../src/corelib/tools/qvector.h:395
#14 clear (this=0x1e501d0) at ../../src/corelib/tools/qvector.h:348
#15 QTextEngine::clearLineData (this=0x1e501d0) at text/qtextengine.cpp:1483
#16 0x7f7932425c3d in QTextDocumentLayout::documentChanged (this=0x19c1d90,
from=0, oldLength=0, length=6909) at text/qtextdocumentlayout.cpp:2869
#17 0x7f79325e837c in QTextEditPrivate::relayoutDocument
(this=this@entry=0x19c2ff0) at widgets/qtextedit.cpp:1438
#18 0x7f79325e8b89 in QTextEdit::resizeEvent (this=optimized out,
e=0x7fff97e57420) at widgets/qtextedit.cpp:1397
#19 0x7f79321d3315 in QWidget::event (this=0x19c1840, event=0x7fff97e57420)
at kernel/qwidget.cpp:8540
#20 0x7f793257df26 in QFrame::event (this=0x19c1840, e=0x7fff97e57420) at
widgets/qframe.cpp:557
#21 0x7f7931c45ef6 in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
from /usr/lib64/libQtCore.so.4
#22 0x7f793218383c in QApplicationPrivate::notify_helper
(this=this@entry=0x1580730, receiver=receiver@entry=0x19c1630,
e=e@entry=0x7fff97e57420) at kernel/qapplication.cpp:4558
#23 0x7f7932187ceb in QApplication::notify (this=0x7fff97e582d0,
receiver=0x19c1630, e=0x7fff97e57420) at kernel/qapplication.cpp:4423
#24 0x7f79339ad7f6 in KApplication::notify (this=0x7fff97e582d0,
receiver=0x19c1630, event=0x7fff97e57420) at
/usr/src/debug/kdelibs-4.10.5/kdeui/kernel/kapplication.cpp:311
#25 0x7f7931c45d8e in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib64/libQtCore.so.4
#26 0x7f79321cd8e6 in sendEvent (event=0x7fff97e57420, receiver=0x19c1630)
at ../../src/corelib/kernel/qcoreapplication.h:231
#27 QWidgetPrivate::sendPendingMoveAndResizeEvents (this=this@entry=0x19c24f0,
recursive=recursive@entry=false, disableUpdates=optimized out,
disableUpdates@entry=false) at kernel/qwidget.cpp:7445
#28 0x7f79321d5281 in QWidgetPrivate::show_helper
(this=this@entry=0x19c24f0) at kernel/qwidget.cpp:7496
#29 0x7f79321d5682 in QWidget::setVisible (this=0x19c1630,
visible=optimized out) at kernel/qwidget.cpp:
#30 0x7f79321d521e in show (this=0x19c1630) at
../../src/gui/kernel/qwidget.h:494
#31 QWidgetPrivate::showChildren (this=this@entry=0x19c2ff0,
spontaneous=spontaneous@entry=false) at kernel/qwidget.cpp:7865
#32 0x7f79321d529d in QWidgetPrivate::show_helper
(this=this@entry=0x19c2ff0) at kernel/qwidget.cpp:7502
#33 0x7f79321d5682 in QWidget::setVisible (this=0x19c1840,
visible=optimized out) at kernel/qwidget.cpp:
#34 0x7f79321d521e in show (this=0x19c1840) at
../../src/gui/kernel/qwidget.h:494
#35 QWidgetPrivate::showChildren (this=this@entry=0x19bfd60,
spontaneous=spontaneous@entry=false) at kernel/qwidget.cpp:7865
#36 0x7f79321d529d in QWidgetPrivate::show_helper
(this=this@entry=0x19bfd60) at kernel/qwidget.cpp:7502
#37 0x7f79321d5682 in QWidget::setVisible (this=0x198d310,
visible=optimized out) at kernel/qwidget.cpp:
#38 0x7f79321d521e in show (this=0x198d310) at
../../src/gui/kernel/qwidget.h:494
#39 QWidgetPrivate::showChildren (this=this@entry=0x19cb990,
spontaneous=spontaneous@entry=false) at kernel/qwidget.cpp:7865
#40 0x7f79321d529d in QWidgetPrivate::show_helper
(this=this@entry=0x19cb990) at kernel/qwidget.cpp:7502
#41 0x7f79321d5682 in QWidget::setVisible (this=0x191db80,
visible=optimized out) at kernel/qwidget.cpp:
#42 0x7f79321d521e in show (this=0x191db80) at

[kmail2] [Bug 223034] cannot send mail to distribution list

2014-05-14 Thread Alex Ball
https://bugs.kde.org/show_bug.cgi?id=223034

Alex Ball a.b...@ukoln.ac.uk changed:

   What|Removed |Added

 CC||a.b...@ukoln.ac.uk

-- 
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 333611] error on decoding PGP-encoded messages

2014-05-14 Thread Andrew Gaydenko
https://bugs.kde.org/show_bug.cgi?id=333611

--- Comment #3 from Andrew Gaydenko a...@gaydenko.com ---
I'm still ready to send PGP-signed (encoded, but not encrypted) message example
directly to KMail team member. Or - must I supply any additional information?

BTW, KMail1 has dealt with this use case perfectly.

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


[knotes] [Bug 334554] Suggestion: Showing Knotes service users on a LAN

2014-05-14 Thread Rafael
https://bugs.kde.org/show_bug.cgi?id=334554

Rafael rmr...@gmail.com changed:

   What|Removed |Added

 CC||rmr...@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


[knotes] [Bug 334554] Suggestion: Showing Knotes service users on a LAN

2014-05-14 Thread Rafael
https://bugs.kde.org/show_bug.cgi?id=334554

--- Comment #1 from Rafael rmr...@gmail.com ---
Kepas (discountinued) let do my suggestions, and even use KNotes to send
notes. It's a pity do not try to make these applications to continue working
togheter.

-- 
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 63780] Auto-render HTML for certain email addresses

2014-05-14 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=63780

--- Comment #41 from Laurent Montel mon...@kde.org ---
(In reply to comment #40)
 Great news! It could not be backported to 4.13.2 or something? If I dont
 keep an eye on it this can make KMail/Kontact chew up close to 1 Gb RAM

no I can't it added some new i18n and big changes in code.
For next version :)

-- 
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 334740] kmail doesn't handle failed archiving attempts well.

2014-05-14 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=334740

Laurent Montel mon...@kde.org changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #1 from Laurent Montel mon...@kde.org ---
When archiving fails the following happens: why ? How do you produce it ?

-- 
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 334778] New: Kontact crashed after modifying KNotes Settings

2014-05-14 Thread twtroughton
https://bugs.kde.org/show_bug.cgi?id=334778

Bug ID: 334778
   Summary: Kontact crashed after modifying KNotes Settings
Classification: Unclassified
   Product: kontact
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: twtrough...@gmail.com

Application: kontact (4.13.1)
KDE Platform Version: 4.13.1
Qt Version: 4.8.6
Operating System: Linux 3.13.0-24-generic i686
Distribution: Ubuntu 14.04 LTS

-- Information about the crash:
- What I was doing when the application crashed: I was trying to get the KNotes
alarm to work. I went to Popup Notes in the sidebar, selected Settings 
Preferences Knotes  Collections, and right-clicked on one of teh collections
to delete (couldn't), then deselected it and chose the other collection. Then I
clicked on another preference on the sidebar and the software crashed. Happens
sometimes.

Other possibly irrelevant notes: The alarm function of KNotes doesn't work - no
popup note appears. I cannot get a popup not to appear on my desktop. I had
installed KJots, but uninstalled it. It let me create and delete collections,
while I could not figure out how to do that in KNotes.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0xb145c740 (LWP 2679))]

Thread 6 (Thread 0xae839b40 (LWP 2680)):
#0  0xb778c424 in __kernel_vsyscall ()
#1  0xb320fd4b in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187
#2  0xb611a8ec in __pthread_cond_wait (cond=0xb5869cb0, mutex=0xb5869c98) at
forward.c:149
#3  0xb4ff19ac in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#4  0xb4ff19ff in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#5  0xb320bf70 in start_thread (arg=0xae839b40) at pthread_create.c:312
#6  0xb610d70e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129

Thread 5 (Thread 0xadf18b40 (LWP 2681)):
#0  0xb778c424 in __kernel_vsyscall ()
#1  0xb320fd4b in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187
#2  0xb611a8ec in __pthread_cond_wait (cond=0xadf867dc, mutex=0xadf867c4) at
forward.c:149
#3  0xb50209f3 in WTF::ThreadCondition::wait(WTF::Mutex) () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#4  0xb4cfc574 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#5  0xb50077c6 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#6  0xb5020369 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#7  0xb320bf70 in start_thread (arg=0xadf18b40) at pthread_create.c:312
#8  0xb610d70e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129

Thread 4 (Thread 0xab375b40 (LWP 2689)):
#0  0xb778c424 in __kernel_vsyscall ()
#1  0xb60fe7ab in poll () at ../sysdeps/unix/syscall-template.S:81
#2  0xb313520b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb31263e8 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb3126528 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb646295f in QEventDispatcherGlib::processEvents (this=0xaa900468,
flags=...) at kernel/qeventdispatcher_glib.cpp:436
#6  0xb6431823 in QEventLoop::processEvents (this=this@entry=0xab375288,
flags=...) at kernel/qeventloop.cpp:149
#7  0xb6431b49 in QEventLoop::exec (this=this@entry=0xab375288, flags=...) at
kernel/qeventloop.cpp:204
#8  0xb631e23d in QThread::exec (this=this@entry=0x9bc6b00) at
thread/qthread.cpp:537
#9  0xb631e38b in QThread::run (this=0x9bc6b00) at thread/qthread.cpp:604
#10 0xb6320b6f in QThreadPrivate::start (arg=0x9bc6b00) at
thread/qthread_unix.cpp:349
#11 0xb320bf70 in start_thread (arg=0xab375b40) at pthread_create.c:312
#12 0xb610d70e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129

Thread 3 (Thread 0xaa28bb40 (LWP 2696)):
#0  0xb320f12e in __pthread_mutex_unlock_usercnt (mutex=0xa9900558, decr=1) at
pthread_mutex_unlock.c:57
#1  0xb611ab34 in pthread_mutex_unlock (mutex=0xa9900558) at forward.c:194
#2  0xb316b140 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb3126532 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb646295f in QEventDispatcherGlib::processEvents (this=0xa9900468,
flags=...) at kernel/qeventdispatcher_glib.cpp:436
#5  0xb6431823 in QEventLoop::processEvents (this=this@entry=0xaa28b258,
flags=...) at kernel/qeventloop.cpp:149
#6  0xb6431b49 in QEventLoop::exec (this=this@entry=0xaa28b258, flags=...) at
kernel/qeventloop.cpp:204
#7  0xb631e23d in QThread::exec (this=this@entry=0xa111568) at
thread/qthread.cpp:537
#8  0xb6411c44 in QInotifyFileSystemWatcherEngine::run (this=0xa111568) at

[kontact] [Bug 334779] New: KNotes crashes Kontact

2014-05-14 Thread twtroughton
https://bugs.kde.org/show_bug.cgi?id=334779

Bug ID: 334779
   Summary: KNotes crashes Kontact
Classification: Unclassified
   Product: kontact
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: twtrough...@gmail.com

Application: kontact (4.13.1)
KDE Platform Version: 4.13.1
Qt Version: 4.8.6
Operating System: Linux 3.13.0-24-generic i686
Distribution: Ubuntu 14.04 LTS

-- Information about the crash:
I had two collections selected in KNotes. One was supposed to be the default
collections. I created a note, which appeared twice. Edited one note - entered
message. When I edited the second note with a different message, I got a
dialogue box asking me to compare and choose one. I selected one, then deleted
the other. Went to KNotes Settings, collections, and unselected the not default
collection. Kontact crashed.

Other notes - There is nothing in my .kde/share/apps/knotes directory except a
print folder.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0xb13f0740 (LWP 3197))]

Thread 6 (Thread 0xae7cdb40 (LWP 3198)):
#0  0xb7720424 in __kernel_vsyscall ()
#1  0xb31a3d4b in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187
#2  0xb60ae8ec in __pthread_cond_wait (cond=0xb57fdcb0, mutex=0xb57fdc98) at
forward.c:149
#3  0xb4f859ac in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#4  0xb4f859ff in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#5  0xb319ff70 in start_thread (arg=0xae7cdb40) at pthread_create.c:312
#6  0xb60a170e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129

Thread 5 (Thread 0xadeacb40 (LWP 3199)):
#0  0xb7720424 in __kernel_vsyscall ()
#1  0xb31a3d4b in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187
#2  0xb60ae8ec in __pthread_cond_wait (cond=0xadf1a7dc, mutex=0xadf1a7c4) at
forward.c:149
#3  0xb4fb49f3 in WTF::ThreadCondition::wait(WTF::Mutex) () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#4  0xb4c90574 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#5  0xb4f9b7c6 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#6  0xb4fb4369 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#7  0xb319ff70 in start_thread (arg=0xadeacb40) at pthread_create.c:312
#8  0xb60a170e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129

Thread 4 (Thread 0xab30db40 (LWP 3203)):
#0  0xb63f6def in testAndSetOrdered (newValue=0, expectedValue=1,
this=0x92d0a28) at
../../include/QtCore/../../src/corelib/arch/qatomic_i386.h:144
#1  testAndSetRelease (newValue=0, expectedValue=1, this=0x92d0a28) at
../../include/QtCore/../../src/corelib/arch/qatomic_i386.h:271
#2  unlockInline (this=0x8d0f494) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:171
#3  unlock (this=synthetic pointer) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:121
#4  ~QMutexLocker (this=synthetic pointer, __in_chrg=optimized out) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:115
#5  canWaitLocked (this=optimized out) at
../../include/QtCore/private/../../../src/corelib/thread/qthread_p.h:229
#6  postEventSourcePrepare (s=0xaaa02800, timeout=0xab30d11c) at
kernel/qeventdispatcher_glib.cpp:270
#7  0xb30b99b3 in g_main_context_prepare () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#8  0xb30ba2df in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#9  0xb30ba528 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#10 0xb63f695f in QEventDispatcherGlib::processEvents (this=0xaaa00468,
flags=...) at kernel/qeventdispatcher_glib.cpp:436
#11 0xb63c5823 in QEventLoop::processEvents (this=this@entry=0xab30d288,
flags=...) at kernel/qeventloop.cpp:149
#12 0xb63c5b49 in QEventLoop::exec (this=this@entry=0xab30d288, flags=...) at
kernel/qeventloop.cpp:204
#13 0xb62b223d in QThread::exec (this=this@entry=0x8d1d0f0) at
thread/qthread.cpp:537
#14 0xb62b238b in QThread::run (this=0x8d1d0f0) at thread/qthread.cpp:604
#15 0xb62b4b6f in QThreadPrivate::start (arg=0x8d1d0f0) at
thread/qthread_unix.cpp:349
#16 0xb319ff70 in start_thread (arg=0xab30db40) at pthread_create.c:312
#17 0xb60a170e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129

Thread 3 (Thread 0xaa222b40 (LWP 3208)):
#0  0xb7720424 in __kernel_vsyscall ()
#1  0xb60927ab in poll () at ../sysdeps/unix/syscall-template.S:81
#2  0xb30c920b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb30ba3e8 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb30ba528 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb63f695f in 

[Akonadi] [Bug 334014] akonadiserver start problem after 4.12 to 4.13 update

2014-05-14 Thread jajaX
https://bugs.kde.org/show_bug.cgi?id=334014

--- Comment #9 from jajaX jaja...@gmail.com ---
Hi ! (sorry for my bad english !)

always same problem after upgrade to kubuntu 14.04 :

jajax@portable:~/.local/share/akonadi/db_data$ mysql
--socket=/tmp/akonadi-jajax.BSQudX/mysql.socket
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 25
Server version: 5.5.35-1ubuntu1 (Ubuntu)

Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql SELECT TABLE_NAME,ENGINE FROM information_schema.TABLES WHERE
TABLE_SCHEMA='akonadi';
+--++
| TABLE_NAME   | ENGINE |
+--++
| collectionattributetable | InnoDB |
| collectionmimetyperelation   | InnoDB |
| collectionpimitemrelation| InnoDB |
| collectiontable  | InnoDB |
| flagtable| InnoDB |
| mimetypetable| InnoDB |
| parttable| InnoDB |
| parttypetable| InnoDB |
| pimitemflagrelation  | InnoDB |
| pimitemtable | InnoDB |
| pimitemtagrelation   | InnoDB |
| resourcetable| InnoDB |
| schemaversiontable   | InnoDB |
| tagattributetable| InnoDB |
| tagremoteidresourcerelationtable | InnoDB |
| tagtable | InnoDB |
+--++
16 rows in set (0.00 sec)

mysql ALTER TABLE akonadi.tableName ENGINE = InnoDB;
ERROR 1146 (42S02): Table 'akonadi.tablename' doesn't exist
mysql USE akonadi;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql DELETE FROM CollectionTable WHERE parentId NOT IN (SELECT id FROM
CollectionTable) AND parentId IS NOT NULL;
ERROR 1093 (HY000): You can't specify target table 'CollectionTable' for update
in FROM clause
mysql DELETE FROM CollectionTable WHERE parentId NOT IN (SELECT * FROM (SELECT
id FROM CollectionTable)) AND parentId IS NOT NULL;
ERROR 1248 (42000): Every derived table must have its own alias
mysql DELETE FROM CollectionTable WHERE parentId NOT IN (SELECT * FROM (SELECT
id FROM CollectionTable) AS tableA) AND parentId IS NOT NULL;
Query OK, 6 rows affected (0.17 sec)

mysql mysqladmin --socket=/tmp/akonadi-jajax.BSQudX/mysql.socket shutdown
- quit
- 
- 
- 
- 
- quit
- exit
- ^CCtrl-C -- exit!
Aborted
jajax@portable:~/.local/share/akonadi/db_data$ mysqladmin
--socket=/tmp/akonadi-jajax.BSQudX/mysql.socket shutdown
jajax@portable:~/.local/share/akonadi/db_data$ akonadictl start
Starting Akonadi Server... 
   done. 
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
jajax@portable:~/.local/share/akonadi/db_data$ search paths: 
(/usr/local/sbin, /usr/local/bin, /usr/sbin, /usr/bin, /sbin, /bin,
/usr/games, /usr/local/games, /usr/sbin, /usr/local/sbin,
/usr/local/libexec, /usr/libexec, /opt/mysql/libexec,
/opt/local/lib/mysql5/bin, /opt/mysql/sbin) 
Found mysql_install_db:  /usr/bin/mysql_install_db 
Found mysqlcheck:  /usr/bin/mysqlcheck 
akonadi.collectionattributetable   OK
akonadi.collectionmimetyperelation OK
akonadi.collectionpimitemrelation  OK
akonadi.collectiontableOK
akonadi.flagtable  OK
akonadi.mimetypetable  OK
akonadi.parttable  OK
akonadi.parttypetable  OK
akonadi.pimitemflagrelationOK
akonadi.pimitemtable   OK
akonadi.pimitemtagrelation OK
akonadi.resourcetable  OK
akonadi.schemaversiontable OK
akonadi.tagattributetable  OK
akonadi.tagremoteidresourcerelationtable   OK
akonadi.tagtable   OK
mysql.columns_priv OK
mysql.db   OK
mysql.eventOK
mysql.func OK
mysql.general_log  OK
mysql.help_categoryOK
mysql.help_keyword OK
mysql.help_relationOK
mysql.help_topic   OK
mysql.host OK
mysql.ndb_binlog_index OK
mysql.plugin   OK

[kontact] [Bug 334730] Kontact crash on logout

2014-05-14 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=334730

Laurent Montel mon...@kde.org changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||4.13.2
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kdep
   ||im/990d6c87eb243d03f7c067d6
   ||61278cf3aff22fed

--- Comment #1 from Laurent Montel mon...@kde.org ---
Git commit 990d6c87eb243d03f7c067d661278cf3aff22fed by Montel Laurent.
Committed on 14/05/2014 at 19:31.
Pushed by mlaurent into branch 'KDE/4.13'.

Fix Bug 334730 - Kontact crash on logout
FIXED-IN: 4.13.2

M  +1-1kmail/kmmainwidget.cpp

http://commits.kde.org/kdepim/990d6c87eb243d03f7c067d661278cf3aff22fed

-- 
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 330727] Kmail/Kontact crashes when attaching document via external program

2014-05-14 Thread Reinhard Biegel
https://bugs.kde.org/show_bug.cgi?id=330727

Reinhard Biegel r.bie...@gmx.at changed:

   What|Removed |Added

 CC||r.bie...@gmx.at

--- Comment #2 from Reinhard Biegel r.bie...@gmx.at ---
Kontact crashed for me when adding an attachment via drag  drop from dolphin.
Backtrace below is from application start, not the first crash when adding the
attachment.

KDE 4.13.1, Gentoo


Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library /lib64/libthread_db.so.1.
[Current thread is 1 (Thread 0x7f1ea956d780 (LWP 2533))]

Thread 3 (Thread 0x7f1e94721700 (LWP 2534)):
#0  0x7f1ea142144c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f1ea445542b in ?? () from /usr/lib64/qt4/libQtWebKit.so.4
#2  0x7f1ea4455529 in ?? () from /usr/lib64/qt4/libQtWebKit.so.4
#3  0x7f1ea141d1f3 in start_thread () from /lib64/libpthread.so.0
#4  0x7f1ea6b2648d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f1e93f20700 (LWP 2535)):
#0  0x7f1ea6b1808d in read () from /lib64/libc.so.6
#1  0x7f1ea0848eb0 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f1ea080978c in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f1ea0809bfb in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f1ea0809d74 in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f1ea7f0a59e in
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) ()
from /usr/lib64/qt4/libQtCore.so.4
#6  0x7f1ea7edbd8f in
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from
/usr/lib64/qt4/libQtCore.so.4
#7  0x7f1ea7edc07d in
QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from
/usr/lib64/qt4/libQtCore.so.4
#8  0x7f1ea7dd9c50 in QThread::exec() () from /usr/lib64/qt4/libQtCore.so.4
#9  0x7f1ea7ddc4ef in ?? () from /usr/lib64/qt4/libQtCore.so.4
#10 0x7f1ea141d1f3 in start_thread () from /lib64/libpthread.so.0
#11 0x7f1ea6b2648d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f1ea956d780 (LWP 2533)):
[KCrash Handler]
#5  0x7f1ea7eee868 in QObject::killTimer(int) () from
/usr/lib64/qt4/libQtCore.so.4
#6  0x7f1ea7efa471 in QTimer::stop() () from /usr/lib64/qt4/libQtCore.so.4
#7  0x7f1ea7efa50f in QTimer::start() () from /usr/lib64/qt4/libQtCore.so.4
#8  0x7f1e90788a35 in ?? () from /usr/lib64/libkmailprivate.so.4
#9  0x7f1ea7ef11c8 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /usr/lib64/qt4/libQtCore.so.4
#10 0x7f1ea7ef11c8 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /usr/lib64/qt4/libQtCore.so.4
#11 0x7f1e4bd415be in
MessageComposer::AttachmentControllerBase::addAttachment(boost::shared_ptrMessageCore::AttachmentPart)
() from /usr/lib64/libmessagecomposer.so.4
#12 0x7f1e4bd62552 in
MessageComposer::ComposerViewBase::addAttachmentPart(KMime::Content*) () from
/usr/lib64/libmessagecomposer.so.4
#13 0x7f1e4bd721d3 in
MessageComposer::ComposerViewBase::setMessage(boost::shared_ptrKMime::Message
const) () from /usr/lib64/libmessagecomposer.so.4
#14 0x7f1e9075e5f8 in ?? () from /usr/lib64/libkmailprivate.so.4
#15 0x7f1e90687b05 in KMKernel::recoverDeadLetters() () from
/usr/lib64/libkmailprivate.so.4
#16 0x7f1e90a3138b in ?? () from /usr/lib64/kde4/kmailpart.so
#17 0x7f1e90a32a4f in ?? () from /usr/lib64/kde4/kmailpart.so
#18 0x7f1ea844c852 in KPluginFactory::create(char const*, QWidget*,
QObject*, QListQVariant const, QString const) () from
/usr/lib64/libkdecore.so.5
#19 0x7f1ea91c2010 in KontactInterface::Core::createPart(char const*) ()
from /usr/lib64/libkontactinterface.so.4
#20 0x7f1e91272f20 in ?? () from /usr/lib64/kde4/kontact_kmailplugin.so
#21 0x7f1ea91c44e9 in KontactInterface::Plugin::part() () from
/usr/lib64/libkontactinterface.so.4
#22 0x7f1ea8d8a9ec in
Kontact::MainWindow::selectPlugin(KontactInterface::Plugin*) () from
/usr/lib64/libkontactprivate.so.4
#23 0x7f1ea8d886ac in Kontact::MainWindow::loadSettings() () from
/usr/lib64/libkontactprivate.so.4
#24 0x7f1ea8d8dca2 in Kontact::MainWindow::initObject() () from
/usr/lib64/libkontactprivate.so.4
#25 0x7f1ea8d8e3a8 in Kontact::MainWindow::MainWindow() () from
/usr/lib64/libkontactprivate.so.4
#26 0x00404164 in _start ()

-- 
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 328224] Kontact has crashed when fetching e-mail via IMAP

2014-05-14 Thread Martin
https://bugs.kde.org/show_bug.cgi?id=328224

Martin martin.ruess...@mailbox.org changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||martin.ruess...@mailbox.org
Version|4.11.3  |4.13
 Ever confirmed|0   |1

--- Comment #2 from Martin martin.ruess...@mailbox.org ---
I also experienced the bug. It is the first time but right now KMail crashes
every time I start it.

-- 
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 294517] Moving emails from a local folder to another duplicates mails

2014-05-14 Thread Sandro Knauß
https://bugs.kde.org/show_bug.cgi?id=294517

Sandro Knauß m...@sandroknauss.de changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||m...@sandroknauss.de
Version|unspecified |1.12.1
 Ever confirmed|0   |1

--- Comment #2 from Sandro Knauß m...@sandroknauss.de ---
I can confirm this with Akonadi 1.12.1 (shipped via debian) and kmail 4.12.2.

Unfortunatelly this bug only occourse sometimes. I think, that this bug is
related, that akonadi cheks for new mails at the same time, when moving mails.

-- 
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 294517] Moving emails from a local folder to another duplicates mails

2014-05-14 Thread Christian Boltz
https://bugs.kde.org/show_bug.cgi?id=294517

Christian Boltz kde-b...@cboltz.de changed:

   What|Removed |Added

 CC||kde-b...@cboltz.de
   Severity|normal  |major

--- Comment #3 from Christian Boltz kde-b...@cboltz.de ---
Same bug here with KDE 4.13.0 and KDE 4.13 on openSUSE Factory.

This happens (nearly?) always when
a) I move around multiple mails at once (moving a single mail seems to be
boomerang-free)
b) the folder has a high throughput (like the inbox, where the mails arrive and
later get moved or filtered away)
c) the folder contains lots of mails (1000 seem to be a good reproducer)

I also verified that moving the mails one by one is boomerang-free - but that's
a very annoying and time-consuming workaround when moving 50 mails :-/

hefee_ on #kontact has the same problem with KDE 4.12 / kmail 4.12.2 - he
confirmed a) and is not sure about b). c) seems not to be necessary - hefee_
also had this bug when moving nearly all mails in a folder with about 20 mails.

-- 
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 303946] Kontact started twice and chrashed when closen one instance

2014-05-14 Thread Andreas Roth
https://bugs.kde.org/show_bug.cgi?id=303946

Andreas Roth ar...@arsoft-online.com changed:

   What|Removed |Added

 CC||ar...@arsoft-online.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


[kontact] [Bug 303946] Kontact started twice and chrashed when closen one instance

2014-05-14 Thread Andreas Roth
https://bugs.kde.org/show_bug.cgi?id=303946

--- Comment #6 from Andreas Roth ar...@arsoft-online.com ---
Created attachment 86639
  -- https://bugs.kde.org/attachment.cgi?id=86639action=edit
New crash information added by DrKonqi

kontact (4.13.1) on KDE Platform 4.13.1 using Qt 4.8.6

- What I was doing when the application crashed:
Two instances of Kontact was started. Both instances asked me to migrate my
KNotes configuration. 
When i've seen that two instances/windows are open i closed one and it crashed.

-- Backtrace (Reduced):
#6  0x7f30ae201b66 in MailCommon::Kernel::folderIsTemplates
(this=optimized out, col=...) at ../../mailcommon/kernel/mailkernel.cpp:277
#7  0x7f30ae60f250 in KMail::MessageActions::updateActions (this=0x1cdccc0)
at ../../kmail/messageactions.cpp:271
#8  0x7f30ae611319 in KMail::MessageActions::setCurrentMessage
(this=optimized out, msg=..., items=...) at
../../kmail/messageactions.cpp:236
#9  0x7f30ae5e1d45 in KMMainWidget::updateMessageActions
(this=this@entry=0x1a30550, fast=fast@entry=true) at
../../kmail/kmmainwidget.cpp:3803
#10 0x7f30ae5e24be in KMMainWidget::startUpdateMessageActionsTimer
(this=0x1a30550) at ../../kmail/kmmainwidget.cpp:3788

-- 
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 333689] Kontact 4.4.11 segfaults after upgrading KDE to 4.13.0

2014-05-14 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=333689

Laurent Montel mon...@kde.org changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #2 from Laurent Montel mon...@kde.org ---
kontact (4.12.5) on KDE Platform 4.13.1 using Qt 4.8.5
why don't use kontact 4.13.1 on kde 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