[Akonadi] [Bug 351850] Random crash when having a gmail account setup in kmail

[Lars Hilgenstock via KDE Bugzilla]

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

Lars Hilgenstock  changed:

   What|Removed |Added

 CC|lars.hilgenstock@tu-dortmun |
   |d.de|

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

[kmail2] [Bug 361196] crash when one add new mail account because KDE wallet is off

[Laurent Montel via KDE Bugzilla]

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
""This only happen when "Enable the KDE wallet subsystem" checkbox is off. "
where do you do 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 361213] New: Mint would'nt shut down

[J Coombs via KDE Bugzilla]

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

Bug ID: 361213
   Summary: Mint would'nt shut down
   Product: Akonadi
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: IMAP resource
  Assignee: chrig...@fastmail.fm
  Reporter: gribn...@hotmail.com
CC: kdepim-bugs@kde.org, vkra...@kde.org

Application: akonadi_imap_resource (4.14)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.16.0-38-generic x86_64
Distribution: Linux Mint 17.2 Rafaela

-- Information about the crash:
- What I was doing when the application crashed:Closed all applications
shutdown computer. I noticed it was not shutting down after 10 minutes I forced
shutdown.

-- Backtrace:
Application: Google Mail (bigdaddymobaddie) 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 0x7f8d4bf257c0 (LWP 2442))]

Thread 3 (Thread 0x7f8d37810700 (LWP 2558)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x7f8d4b4277f4 in wait (time=3, this=0x7f8d30014b80) at
thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=this@entry=0x7f8d300149a0,
mutex=mutex@entry=0x7f8d300147d8, time=3) at
thread/qwaitcondition_unix.cpp:158
#3  0x7f8d4b41b0fa in QThreadPoolThread::run (this=0x7f8d30014990) at
concurrent/qthreadpool.cpp:142
#4  0x7f8d4b42732f in QThreadPrivate::start (arg=0x7f8d30014990) at
thread/qthread_unix.cpp:349
#5  0x7f8d46f22182 in start_thread (arg=0x7f8d37810700) at
pthread_create.c:312
#6  0x7f8d478c547d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f8d38011700 (LWP 2674)):
#0  __pthread_mutex_unlock_usercnt (decr=1, mutex=0x7f8d30005240) at
pthread_mutex_unlock.c:63
#1  __GI___pthread_mutex_unlock (mutex=0x7f8d30005240) at
pthread_mutex_unlock.c:310
#2  0x7f8d4687f9b1 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f8d4683e0f6 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f8d4b5567be in QEventDispatcherGlib::processEvents
(this=0x7f8d30004db0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#5  0x7f8d4b5280af in QEventLoop::processEvents
(this=this@entry=0x7f8d38010e20, flags=...) at kernel/qeventloop.cpp:149
#6  0x7f8d4b5283a5 in QEventLoop::exec (this=this@entry=0x7f8d38010e20,
flags=...) at kernel/qeventloop.cpp:204
#7  0x7f8d4b424c5f in QThread::exec (this=) at
thread/qthread.cpp:537
#8  0x7f8d4b42732f in QThreadPrivate::start (arg=0x247e720) at
thread/qthread_unix.cpp:349
#9  0x7f8d46f22182 in start_thread (arg=0x7f8d38011700) at
pthread_create.c:312
#10 0x7f8d478c547d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f8d4bf257c0 (LWP 2442)):
[KCrash Handler]
#5  0x0d31 in ?? ()
#6  0x7f8d4b53c999 in QObject::disconnect (sender=0x249f920,
signal=0x23e3c09 "stateChanged(KIMAP::Session::State,KIMAP::Session::State)",
signal@entry=0x47b588
"2stateChanged(KIMAP::Session::State,KIMAP::Session::State)",
receiver=receiver@entry=0x2460450, method=0x242aef9
"onSessionStateChanged(KIMAP::Session::State,KIMAP::Session::State)",
method@entry=0x47b540
"1onSessionStateChanged(KIMAP::Session::State,KIMAP::Session::State)") at
kernel/qobject.cpp:2883
#7  0x0044fbb5 in SessionPool::killSession (this=this@entry=0x2460450,
session=0x249f920, termination=termination@entry=SessionPool::LogoutSession) at
../../../resources/imap/sessionpool.cpp:182
#8  0x0044ff55 in SessionPool::disconnect (this=0x2460450,
termination=termination@entry=SessionPool::LogoutSession) at
../../../resources/imap/sessionpool.cpp:115
#9  0x004285fb in ImapResourceBase::startConnect (this=0x241f020) at
../../../resources/imap/imapresourcebase.cpp:246
#10 0x00464511 in ImapResourceBase::qt_static_metacall (_o=0x249f920,
_o@entry=0x241f020, _c=685514976, _c@entry=QMetaObject::InvokeMetaMethod,
_id=1, _id@entry=14, _a=0x0, _a@entry=0x7ffe28dc23d0) at
moc_imapresourcebase.cpp:122
#11 0x7f8d4b531908 in QMetaMethod::invoke (this=this@entry=0x7ffe28dc25c0,
object=object@entry=0x241f020, connectionType=Qt::DirectConnection,
connectionType@entry=Qt::AutoConnection, returnValue=..., val0=..., val1=...,
val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...)
at kernel/qmetaobject.cpp:1664
#12 0x7f8d4b533dc2 in QMetaObject::invokeMethod (obj=0x241f020,
member=, type=Qt::AutoConnection, ret=..., val0=..., val1=...,
val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...)
at kernel/qmetaobject.cpp:1179
#13 0x7f8d4ba1ad7f in ?? () from 

[Akonadi] [Bug 353957] Akonadi IMAP resource crashed when checked maildir

[Daniel Vrátil via KDE Bugzilla]

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

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org

--- Comment #15 from Daniel Vrátil  ---
Hi,

this should be fixed since KDE Applications 15.12. Can you please confirm
whether you can still reproduce in 15.12 or newer?

-- 
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 351850] Random crash when having a gmail account setup in kmail

[Daniel Vrátil via KDE Bugzilla]

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

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org

--- Comment #25 from Daniel Vrátil  ---
The bug has been fixed in KDE Applications 15.08 release, the fixed has been
cherry-picked to KDE/4.14 branch after its last release. Please ask your
distribution to include the patch in their packaging, or upgrade to latest KDE
PIM from KDE Applications 16.04.

-- 
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 357541] akonadi_baloo_indexer crashes on akonadi start

[Daniel Vrátil via KDE Bugzilla]

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

--- Comment #2 from Daniel Vrátil  ---
Looks like there's either some problem with your DBus, or that somehow
something is already occupying the
org.freedesktop.Akonadi.Agent.akonadi_baloo_indexer service on the bus -
possibly another instance running (which should NOT be possible).

Can you check if this is still happening in KDE PIM 15.12 or 16.04? The agent
there is called akonadi_indexing_agent (we removed "Baloo" from the name).

-- 
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 357541] akonadi_baloo_indexer crashes on akonadi start

[Daniel Vrátil via KDE Bugzilla]

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

Daniel Vrátil  changed:

   What|Removed |Added

 CC||v...@pelcak.org

--- Comment #1 from Daniel Vrátil  ---
*** Bug 358314 has been marked as a duplicate of this bug. ***

-- 
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 358314] akonadi_baloo_indexer crashes

[Daniel Vrátil via KDE Bugzilla]

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

Daniel Vrátil  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Daniel Vrátil  ---


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

-- 
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 352014] Regression: Akonadi 15.08.0 iCal Resource does not accept https-URLs as calendar source any more

[Daniel Vrátil via KDE Bugzilla]

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

Daniel Vrátil  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
 CC||dvra...@kde.org

--- Comment #11 from Daniel Vrátil  ---
Thanks for testing, marking as FIXED. Please reopen if necessary.

-- 
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 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"

[Daniel Vrátil via KDE Bugzilla]

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

--- Comment #50 from Daniel Vrátil  ---
The only fix for the "Multiple merge candidates" error is to run Akonadi
Console, go to "Browser" tab, right-click the broken folder and select "Clear
Akonadi cache". Then restart Akonadi and it will re-fetch content of the broken
folder from the IMAP server.

-- 
You are receiving this mail because:
You are the assignee for the bug.
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 355743] akonadiconsole shows no enties in the 'Browser' tab

[Daniel Vrátil via KDE Bugzilla]

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

Daniel Vrátil  changed:

   What|Removed |Added

Summary|akonadiconsole shows now|akonadiconsole shows no
   |enties in the 'Browser' tab |enties in the 'Browser' tab

--- Comment #5 from Daniel Vrátil  ---
This is a known regression in KDEPIM5, looks like something is going wrong in
one of the many layers of proxy models, you can try investigating with
GammaRay.

Akonadi Console is a developer tool, so this has a very low priority, probably
until I need it working again :)

-- 
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 329779] crash without kontakt open (while background email check on POP3 runs on the default account and a mailinglist filter is used)

[Albert Astals Cid via KDE Bugzilla]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED

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

[kmail2] [Bug 361196] crash when one add new mail account because KDE wallet is off

[RJ via KDE Bugzilla]

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

RJ  changed:

   What|Removed |Added

Summary|crash when one add new mail |crash when one add new mail
   |account |account because KDE wallet
   ||is off

-- 
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 361196] New: crash when one add new mail account

[RJ via KDE Bugzilla]

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

Bug ID: 361196
   Summary: crash when one add new mail account
   Product: kmail2
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: ogldel...@mail.ru

Application: kmail (5.1.3)

Qt Version: 5.5.1
Operating System: Linux 4.5.0-1-pae i686
Distribution: "openSUSE Tumbleweed (20160326) (i586)"

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

Start KMail and try to add new mail account. This only happen when "Enable the
KDE wallet subsystem" checkbox is off. With "Enable the KDE wallet subsystem"
active all goes fine!

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0xae321ac0 (LWP 13820))]

Thread 18 (Thread 0xac7aeb40 (LWP 13821)):
#0  0xb77b9f3d in __kernel_vsyscall ()
#1  0xb5eae17b in poll () from /lib/libc.so.6
#2  0xb303b99d in poll (__timeout=-1, __nfds=1, __fds=0xac7ae0dc) at
/usr/include/bits/poll2.h:46
#3  _xcb_conn_wait (c=0x9f296b0, cond=0x9f296d4, vector=0x0, count=0x0) at
xcb_conn.c:459
#4  0xb303da9b in xcb_wait_for_event (c=0x9f296b0) at xcb_in.c:693
#5  0xac8d3483 in QXcbEventReader::run (this=0x9f39718) at
qxcbconnection.cpp:1229
#6  0xb61afc00 in QThreadPrivate::start (arg=0x9f39718) at
thread/qthread_unix.cpp:331
#7  0xb3ba12f5 in start_thread () from /lib/libpthread.so.0
#8  0xb5eb855e in clone () from /lib/libc.so.6

Thread 17 (Thread 0xab36fb40 (LWP 13822)):
#0  0xb77b9f3d in __kernel_vsyscall ()
#1  0xb5eae17b in poll () from /lib/libc.so.6
#2  0xb3a6d7f0 in poll (__timeout=8513, __nfds=1, __fds=0xaaa00de0) at
/usr/include/bits/poll2.h:46
#3  g_poll (fds=0xaaa00de0, nfds=1, timeout=8513) at gpoll.c:124
#4  0xb3a5ef5c in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0xaaa00de0, timeout=, context=0xaaa004d8) at gmain.c:4135
#5  g_main_context_iterate (context=context@entry=0xaaa004d8,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3835
#6  0xb3a5f094 in g_main_context_iteration (context=0xaaa004d8, may_block=1) at
gmain.c:3901
#7  0xb63cea84 in QEventDispatcherGlib::processEvents (this=0xaaa00468,
flags=...) at kernel/qeventdispatcher_glib.cpp:420
#8  0xb63764c3 in QEventLoop::processEvents (this=0xab36f198, flags=...) at
kernel/qeventloop.cpp:128
#9  0xb63768fa in QEventLoop::exec (this=0xab36f198, flags=...) at
kernel/qeventloop.cpp:204
#10 0xb61aa855 in QThread::exec (this=0x9ffc150) at thread/qthread.cpp:503
#11 0xb61aa928 in QThread::run (this=0x9ffc150) at thread/qthread.cpp:570
#12 0xb61afc00 in QThreadPrivate::start (arg=0x9ffc150) at
thread/qthread_unix.cpp:331
#13 0xb3ba12f5 in start_thread () from /lib/libpthread.so.0
#14 0xb5eb855e in clone () from /lib/libc.so.6

Thread 16 (Thread 0xaa9b5b40 (LWP 13823)):
#0  0xb3a5e92e in g_main_context_check (context=0xaa0004d8,
max_priority=2147483647, fds=0xaa003730, n_fds=1) at gmain.c:3750
#1  0xb3a5eef1 in g_main_context_iterate (context=context@entry=0xaa0004d8,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3837
#2  0xb3a5f094 in g_main_context_iteration (context=0xaa0004d8, may_block=1) at
gmain.c:3901
#3  0xb63cea84 in QEventDispatcherGlib::processEvents (this=0xaa000468,
flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0xb63764c3 in QEventLoop::processEvents (this=0xaa9b5198, flags=...) at
kernel/qeventloop.cpp:128
#5  0xb63768fa in QEventLoop::exec (this=0xaa9b5198, flags=...) at
kernel/qeventloop.cpp:204
#6  0xb61aa855 in QThread::exec (this=0x9fca3c0) at thread/qthread.cpp:503
#7  0xb61aa928 in QThread::run (this=0x9fca3c0) at thread/qthread.cpp:570
#8  0xb61afc00 in QThreadPrivate::start (arg=0x9fca3c0) at
thread/qthread_unix.cpp:331
#9  0xb3ba12f5 in start_thread () from /lib/libpthread.so.0
#10 0xb5eb855e in clone () from /lib/libc.so.6

Thread 15 (Thread 0xa9fffb40 (LWP 13825)):
#0  0xb5ec5914 in __libc_disable_asynccancel () from /lib/libc.so.6
#1  0xb5ea8524 in read () from /lib/libc.so.6
#2  0xb3aa2de5 in read (__nbytes=16, __buf=0xa9ffefac, __fd=) at
/usr/include/bits/unistd.h:44
#3  g_wakeup_acknowledge (wakeup=0xaa001dc8) at gwakeup.c:210
#4  0xb3a5ea36 in g_main_context_check (context=0xa01c5c8,
max_priority=2147483647, fds=0xa021d40, n_fds=1) at gmain.c:3632
#5  0xb3a5eef1 in g_main_context_iterate (context=context@entry=0xa01c5c8,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3837
#6  0xb3a5f094 in g_main_context_iteration (context=0xa01c5c8, may_block=1) at
gmain.c:3901
#7  0xb63cea84 in QEventDispatcherGlib::processEvents (this=0xa01a558,
flags=...) at kernel/qeventdispatcher_glib.cpp:420
#8  0xb63764c3 in QEventLoop::processEvents (this=0xa9fff198, flags=...) at
kernel/qeventloop.cpp:128
#9  

[kdepimlibs] [Bug 341877] "circular dependency" between kdepimlibs and new split PIM kmailtransport

[James Richard Tyrer via KDE Bugzilla]

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

--- Comment #8 from James Richard Tyrer  ---
(In reply to James Richard Tyrer from comment #5)
> 16.03.80 behaves as follows:
> 
> configure of KDEpimligs asks for:
> 
> KF5CalendarCoreConfig.cmake
> 
Yes, that is provided by: kcalcore.  Which I might note that you don't find if
you look for "calendar".

Should I revise the Bug to state the problem as being that there are CAM
(Content Addressable Memory) references that indicate which dependencies are
required rather than the actual name of the package.  Not to mention the fact
that they are all very similar.  That is if you have the package, you can look
to see what it provides but how do you do the reverse?  Is there a reason why
the dependencies don't state the name of the package which is needed rather
than a file which that package would supply AFTER it is installed?

-- 
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 361180] New: kontact crashes when selecting associated google contacts

[wallace . maxted]

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

Bug ID: 361180
   Summary: kontact crashes when selecting associated google
contacts
   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: wallace.max...@gmail.com

Application: kontact (5.0.2)

Qt Version: 5.4.2
Operating System: Linux 4.2.0-34-generic i686
Distribution: Ubuntu 15.10

-- Information about the crash:
- What I was doing when the application crashed:
I connected a google account and associated it with the contacts section. On
attempting to view the contacts kontact crashes.
- Custom settings of the application:
Connection to a gmail account - calendar section is working OK.

I did find some similar reports but clicking on 'select this report as similar'
or whaterver the text was did nothing  ?

The crash can be reproduced every time.

-- 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 0xad8f77c0 (LWP 13137))]

Thread 5 (Thread 0xac0e7b40 (LWP 13139)):
#0  0xb778ebe8 in __kernel_vsyscall ()
#1  0xb2a0825c in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187
#2  0xb605cd46 in __pthread_cond_wait (cond=0xb5df2d34, mutex=0xb5df2d1c) at
forward.c:149
#3  0xb515611a in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5
#4  0xb515616c in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5
#5  0xb2a031aa in start_thread (arg=0xac0e7b40) at pthread_create.c:333
#6  0xb605002e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122

Thread 4 (Thread 0xab13ab40 (LWP 13140)):
#0  0xb6337fcb in QMutex::lock() () from
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#1  0xb656ed30 in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#2  0xb27433db in g_main_context_prepare () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb2743e24 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb2744054 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb656f7e4 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#6  0xb65122b3 in
QEventLoop::processEvents(QFlags) () from
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#7  0xb6512702 in QEventLoop::exec(QFlags) ()
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#8  0xb633b23d in QThread::exec() () from
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#9  0xb633b318 in QThread::run() () from
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#10 0xb634065b in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#11 0xb2a031aa in start_thread (arg=0xab13ab40) at pthread_create.c:333
#12 0xb605002e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122

Thread 3 (Thread 0xa9f7cb40 (LWP 13141)):
#0  0xb778ebe8 in __kernel_vsyscall ()
#1  0xb2a0825c in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187
#2  0xb605cd46 in __pthread_cond_wait (cond=0xab820138, mutex=0xab820120) at
forward.c:149
#3  0xb5184cec in WTF::ThreadCondition::wait(WTF::Mutex&) () from
/usr/lib/i386-linux-gnu/libQt5WebKit.so.5
#4  0xb4e434c6 in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5
#5  0xb516d2e2 in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5
#6  0xb51846f1 in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5
#7  0xb2a031aa in start_thread (arg=0xa9f7cb40) at pthread_create.c:333
#8  0xb605002e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122

Thread 2 (Thread 0xa95ffb40 (LWP 13142)):
#0  0xb778ebe8 in __kernel_vsyscall ()
#1  0xb2a0825c in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187
#2  0xb605cd46 in __pthread_cond_wait (cond=0xab824734, mutex=0xab82471c) at
forward.c:149
#3  0xb5184cec in WTF::ThreadCondition::wait(WTF::Mutex&) () from
/usr/lib/i386-linux-gnu/libQt5WebKit.so.5
#4  0xb4e445f5 in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5
#5  0xb516d2e2 in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5
#6  0xb51846f1 in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5
#7  0xb2a031aa in start_thread (arg=0xa95ffb40) at pthread_create.c:333
#8  0xb605002e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122

Thread 1 (Thread 0xad8f77c0 (LWP 13137)):
[KCrash Handler]
#7  0xb2f1a29a in Akonadi::Tag::operator=(Akonadi::Tag const&) () from
/usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5
#8  0xb2f1a3ff in Akonadi::Tag::Tag(Akonadi::Tag const&) () from
/usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5
#9  0xb2fb9537 in ?? () from /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5
#10 0xb2fb832c in 

[Akonadi] [Bug 255388] Kmail filters dont work in incoming mail

[Metko via KDE Bugzilla]

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

Metko  changed:

   What|Removed |Added

 CC||metkome...@gmail.com

--- Comment #109 from Metko  ---
When kmail (5.1.2) is started after login (Leap 42.1), no filter is applied and
all new emails remain in the inbox folder (very annoying). Even manual
filtering and Ctrl+J don't work. My standard procedure then is to just open the
filter settings dialog (Einstellungen|Filter einrichten...) and close it
immediately with Ok, i.e. without changing anything. From then on filtering
works as expected. It seems like the whole filtering mechanism is only started
upon firing up the configuration dialog. Couldn't find this in the previous
comments, so maybe it's a clue for the developers.

-- 
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 361177] New: LDAP server settings not being displayed after saving when a username has been provided

[via KDE Bugzilla]

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

Bug ID: 361177
   Summary: LDAP server settings not being displayed after saving
when a username has been provided
   Product: kleopatra
   Version: 2.2.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aheine...@intevation.de
  Reporter: kde-b...@papillonpictures.co.uk
CC: kdepim-bugs@kde.org, m...@kde.org

Adding an LDAP server with username details saves in the config file but isn't
displayed when you re-open the keyserver window.


Reproducible: Always

Steps to Reproduce:
Go to add a new directory server. Change the scheme to LDAPS. Change the server
name to something (e.g. keys.example.com). Enter a base DN (e.g.
dc=example,dc=com). Select "Show user and password information" and enter
"uid=fred.bloggs,ou=accounts,dc=example,dc=com" in the username field.

Click Apply/OK.




Actual Results:  
If you re-open the directory services window, the server name and base DN are
blank and, if you re-select "show user and password information", the user
information is missing from there as well.


Expected Results:  
All of the fields should show the values that were provided when the server was
added to the configuration.

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

[kmail2] [Bug 358116] messageviewer leaks temporary files with mail parts in it

[Simon Andric via KDE Bugzilla]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@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 361174] New: Kmail crash while viewing

[Ian via KDE Bugzilla]

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

Bug ID: 361174
   Summary: Kmail crash while viewing
   Product: kmail2
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: ianse...@yahoo.co.uk

Application: kmail (5.1.3)

Qt Version: 5.5.1
Frameworks Version: 5.20.0
Operating System: Linux 4.5.0-1-default x86_64
Distribution: "openSUSE Tumbleweed (20160117) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: i had opened kmail, most of
teh emails had been filtered off to other folders. i deleted the couple of spam
emails left in the inbox and viewed the remaining "boucing emails" message. i
then viewed some emails and marked threads as read in two of the other folders.
i was just about to read the emails in the third folder when kmail crashed.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff4722e1940 (LWP 1893))]

Thread 19 (Thread 0x7ff44d088700 (LWP 1894)):
#0  0x7ff46f31b43d in poll () from /lib64/libc.so.6
#1  0x7ff462348432 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7ff46234a007 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7ff44edb0dd9 in QXcbEventReader::run (this=0x23a6440) at
qxcbconnection.cpp:1229
#4  0x7ff46fc2190f in QThreadPrivate::start (arg=0x23a6440) at
thread/qthread_unix.cpp:331
#5  0x7ff4656aa454 in start_thread () from /lib64/libpthread.so.0
#6  0x7ff46f323d8d in clone () from /lib64/libc.so.6

Thread 18 (Thread 0x7ff446ae3700 (LWP 1899)):
#0  0x7ff46f31741d in read () from /lib64/libc.so.6
#1  0x7ff4651cf290 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7ff46518cdc4 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7ff46518d238 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7ff46518d39c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7ff46fe464db in QEventDispatcherGlib::processEvents
(this=0x7ff448c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#6  0x7ff46fdf05ca in QEventLoop::exec (this=this@entry=0x7ff446ae2c90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7ff46fc1cadc in QThread::exec (this=) at
thread/qthread.cpp:503
#8  0x7ff46fc2190f in QThreadPrivate::start (arg=0x246f230) at
thread/qthread_unix.cpp:331
#9  0x7ff4656aa454 in start_thread () from /lib64/libpthread.so.0
#10 0x7ff46f323d8d in clone () from /lib64/libc.so.6

Thread 17 (Thread 0x7ff445c5e700 (LWP 1900)):
#0  0x7ff46f31b43d in poll () from /lib64/libc.so.6
#1  0x7ff46518d294 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7ff46518d39c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7ff46fe464db in QEventDispatcherGlib::processEvents
(this=0x7ff4380008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7ff46fdf05ca in QEventLoop::exec (this=this@entry=0x7ff445c5dc90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7ff46fc1cadc in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7ff46fc2190f in QThreadPrivate::start (arg=0x2507690) at
thread/qthread_unix.cpp:331
#7  0x7ff4656aa454 in start_thread () from /lib64/libpthread.so.0
#8  0x7ff46f323d8d in clone () from /lib64/libc.so.6

Thread 16 (Thread 0x7ff44545d700 (LWP 1901)):
#0  0x7ff4651d0554 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7ff46518d15d in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7ff46518d39c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7ff46fe464db in QEventDispatcherGlib::processEvents
(this=0x7ff43c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7ff46fdf05ca in QEventLoop::exec (this=this@entry=0x7ff44545cc90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7ff46fc1cadc in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7ff46fc2190f in QThreadPrivate::start (arg=0x2405c30) at
thread/qthread_unix.cpp:331
#7  0x7ff4656aa454 in start_thread () from /lib64/libpthread.so.0
#8  0x7ff46f323d8d in clone () from /lib64/libc.so.6

Thread 15 (Thread 0x7ff444c5c700 (LWP 1904)):
#0  0x7ff46f31741d in read () from /lib64/libc.so.6
#1  0x7ff4651cf290 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7ff46518cdc4 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7ff46518d238 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7ff46518d39c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7ff46fe464db in QEventDispatcherGlib::processEvents
(this=0x7ff438c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#6  0x7ff46fdf05ca in 

[kmail2] [Bug 361173] New: Disposition-Notification-To not correctly escaped in message viewer

[Gunter Ohrner via KDE Bugzilla]

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

Bug ID: 361173
   Summary: Disposition-Notification-To not correctly escaped in
message viewer
   Product: kmail2
   Version: 5.1
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: UI
  Assignee: kdepim-bugs@kde.org
  Reporter: kdeb...@customcdrom.de

The following header:

Disposition-Notification-To: "Mr. Smith" 

is displayed as

Empfangsbestätigung an: "Mr. Smith"

(with quotation marks and without notification target mail address) in the
message viewer and looks as follows in the viewers HTML source:



   Empfangsbestätigung an: 


  "Mr. Smith" 



At least, the "sm...@example.com"-tag has been closed properly... ;)

Reproducible: Always

-- 
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 354948] Akonadi crashes when checking Gmail Inbox in Kmail

[Gerhard Lehnhoff via KDE Bugzilla]

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

Gerhard Lehnhoff  changed:

   What|Removed |Added

 CC||pub...@glehnhoff.de

--- Comment #2 from Gerhard Lehnhoff  ---
It also crashes with Google Calender.

Rückverfolgung des Absturzes:

Application: Akonadi-Ressource (akonadi_googlecalendar_resource), signal:
Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc26b5e1840 (LWP 1801))]

Thread 3 (Thread 0x7fc26939d700 (LWP 1829)):
#0  0x7fc2814d988d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fc279686bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fc27968874f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fc26b0c37e9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7fc281de6a6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fc27905a6aa in start_thread (arg=0x7fc26939d700) at
pthread_create.c:333
#6  0x7fc2814e4e9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fc262db5700 (LWP 1927)):
#0  0x7fc278b3a758 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fc278b3b11b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc278b3b2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc28201e50b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fc281fc550a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fc281de1ac4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fc281de6a6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fc27905a6aa in start_thread (arg=0x7fc262db5700) at
pthread_create.c:333
#8  0x7fc2814e4e9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fc26b5e1840 (LWP 1801)):
[KCrash Handler]
#6  QString::QString (other=..., this=this@entry=0x7ffc805a12f0) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:811
#7  Akonadi::Entity::remoteRevision (this=this@entry=0x7fc28209b3d8
) at ../../../../akonadi/src/core/entity.cpp:92
#8  0x0041d980 in CalendarResource::retrieveItems
(this=this@entry=0x1959390, collection=...) at
../../../../resources/google/calendar/calendarresource.cpp:123
#9  0x7fc28511732d in
Akonadi::ResourceBasePrivate::slotItemRetrievalCollectionFetchDone
(this=, job=0x1aa57b0) at
../../../../akonadi/src/agentbase/resourcebase.cpp:954
#10 0x7fc285119200 in Akonadi::ResourceBase::qt_static_metacall
(_o=, _c=, _id=, _a=) at ./moc_resourcebase.cpp:294
#11 0x7fc281ff68ea in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7fc2832d7752 in KJob::result (this=this@entry=0x1aa57b0,
_t1=_t1@entry=0x1aa57b0) at ./moc_kjob.cpp:555
#13 0x7fc2832d8311 in KJob::finishJob (this=0x1aa57b0,
emitResult=) at ../../../src/lib/jobs/kjob.cpp:109
#14 0x7fc2832d832a in KJob::emitResult (this=) at
../../../src/lib/jobs/kjob.cpp:295
#15 0x7fc2846ee3b3 in Akonadi::JobPrivate::delayedEmitResult
(this=) at ../../../../akonadi/src/core/jobs/job.cpp:153
#16 Akonadi::Job::qt_static_metacall (_o=, _c=,
_id=, _a=) at ./moc_job.cpp:107
#17 0x7fc281ff77b1 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x7fc2828bc9dc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x7fc2828c1ea6 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x7fc281fc7d7b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x7fc281fca176 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x7fc28201e0e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x7fc278b3aff7 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7fc278b3b250 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7fc278b3b2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x7fc28201e4ef in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x7fc281fc550a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x7fc281fcd5ec in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#29 0x7fc28511321a in Akonadi::ResourceBase::init (r=r@entry=0x1959390) at

[Akonadi] [Bug 355743] akonadiconsole shows now enties in the 'Browser' tab

[Stephan Diestelhorst via KDE Bugzilla]

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

--- Comment #4 from Stephan Diestelhorst  ---
This is a regression, by the way.

-- 
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 355743] akonadiconsole shows now enties in the 'Browser' tab

[Stephan Diestelhorst via KDE Bugzilla]

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

Stephan Diestelhorst  changed:

   What|Removed |Added

 CC||stephan.diestelhorst@gmail.
   ||com

--- Comment #3 from Stephan Diestelhorst  ---
Could you please fix the bug title?  It should read "akonadiconsole shows no
entries in 'Browser' tab".  Thanks!  Also.. same here.

akonadiconsole Version 0.99
Using:
  KDE Frameworks 5.15.0
  Qt 5.4.2 (built against 5.4.2)
  The xcb windowing system

$ apt-cache policy akonadiconsole
akonadiconsole:
  Installed: 4:15.08.2-0ubuntu1
  Candidate: 4:15.08.2-0ubuntu1
  Version table:
 *** 4:15.08.2-0ubuntu1 0
500 http://mirror.sov.uk.goscomb.net/ubuntu/ wily/universe amd64
Packages
100 /var/lib/dpkg/status

$ cat /etc/*-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=15.10
DISTRIB_CODENAME=wily
DISTRIB_DESCRIPTION="Ubuntu 15.10"

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