[Akonadi] [Bug 480563] New: accountwizard crash upon adding my first email account to it

[Steve Cossette]

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

Bug ID: 480563
   Summary: accountwizard crash upon adding my first email account
to it
Classification: Frameworks and Libraries
   Product: Akonadi
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: Account Wizard
  Assignee: kdepim-bugs@kde.org
  Reporter: farch...@gmail.com
CC: c...@carlschwan.eu
  Target Milestone: ---

Application: accountwizard (0.3)

Qt Version: 6.6.1
Frameworks Version: 5.248.0
Operating System: Linux 6.8.0-0.rc0.20240112git70d201a40823.5.fc40.x86_64
x86_64
Windowing System: Wayland
Distribution: "Fedora release 40 (Rawhide)"
DrKonqi: 5.92.0 [CoredumpBackend]

-- Information about the crash:
When starting kmail for the first time, it asks me if I want to import from
Thunderbird (I said no).

Then, I go through the wizard to add my gmail email address. I enter my name,
email and password (I found that odd, figured it'd go through oauth... oh well)
and select the imap server. I then click on Create Account.

Nothing Happens.

So then I try to simply click Continue and/or Create account again, and the
wizard just dies.

The crash can be reproduced every time.

-- Backtrace:
Application: Account Assistant (accountwizard), signal: Segmentation fault


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 50098]
[New LWP 50111]
[New LWP 50115]
[New LWP 50110]
[New LWP 50117]
[New LWP 50118]
[New LWP 50114]
[New LWP 50125]
[New LWP 50127]
[New LWP 50126]
[New LWP 50129]
[New LWP 50138]
[New LWP 50148]
[New LWP 50410]
[New LWP 50113]
[New LWP 50116]
[New LWP 50108]
[New LWP 50145]
[New LWP 50147]
[New LWP 50412]
[New LWP 50151]
[New LWP 50130]
[New LWP 50146]
[New LWP 50413]
[New LWP 50150]
[New LWP 50409]
[New LWP 50128]
[New LWP 50417]
[New LWP 50421]
[New LWP 50420]
[New LWP 50418]
[New LWP 50149]
[New LWP 50408]
[New LWP 50414]
[New LWP 50419]
[New LWP 50415]
[New LWP 50411]
[New LWP 50416]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/accountwizard'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7fc159cab184 in __pthread_kill_implementation () from
/lib64/libc.so.6
[Current thread is 1 (Thread 0x7fc15566f4c0 (LWP 50098))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7fc15566f4c0 (LWP 50098))]

Thread 38 (Thread 0x7fc1098006c0 (LWP 50416)):
#0  0x7fc159ca5959 in __futex_abstimed_wait_common () at /lib64/libc.so.6
#1  0x7fc159ca8692 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libc.so.6
#2  0x7fc15a559661 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/lib64/libQt6Core.so.6
#3  0x7fc15a5561e7 in QThreadPoolThread::run() () at /lib64/libQt6Core.so.6
#4  0x7fc15a550ace in QThreadPrivate::start(void*) () at
/lib64/libQt6Core.so.6
#5  0x7fc159ca91f7 in start_thread () at /lib64/libc.so.6
#6  0x7fc159d2b2dc in clone3 () at /lib64/libc.so.6

Thread 37 (Thread 0x7fc1114006c0 (LWP 50411)):
#0  0x7fc159d1d73d in poll () at /lib64/libc.so.6
#1  0x7fc1596d7244 in g_main_context_iterate_unlocked.isra () at
/lib64/libglib-2.0.so.0
#2  0x7fc15967c227 in g_main_loop_run () at /lib64/libglib-2.0.so.0
#3  0x7fc155ba47d2 in gdbus_shared_thread_func.lto_priv () at
/lib64/libgio-2.0.so.0
#4  0x7fc1596a6453 in g_thread_proxy () at /lib64/libglib-2.0.so.0
#5  0x7fc159ca91f7 in start_thread () at /lib64/libc.so.6
#6  0x7fc159d2b2dc in clone3 () at /lib64/libc.so.6

Thread 36 (Thread 0x7fc10a2006c0 (LWP 50415)):
#0  0x7fc159ca5959 in __futex_abstimed_wait_common () at /lib64/libc.so.6
#1  0x7fc159ca8692 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libc.so.6
#2  0x7fc15a559661 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/lib64/libQt6Core.so.6
#3  0x7fc15a5561e7 in QThreadPoolThread::run() () at /lib64/libQt6Core.so.6
#4  0x7fc15a550ace in QThreadPrivate::start(void*) () at
/lib64/libQt6Core.so.6
#5  0x7fc159ca91f7 in start_thread () at /lib64/libc.so.6
#6  0x7fc159d2b2dc in clone3 () at /lib64/libc.so.6

Thread 35 (Thread 0x7fc1034006c0 (LWP 50419)):
#0  0x7fc159ca5959 in __futex_abstimed_wait_common () at /lib64/libc.so.6
#1  0x7fc159ca8692 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libc.so.6
#2  0x7fc15a559661 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/lib64/libQt6Core.so.6
#3  0x7fc15a5561e7 in QThreadPoolThread::run() () at /lib64/libQt6Core.so.6
#4  0x7fc15a550ace in 

[Akonadi] [Bug 478381] New: [5.27.80] kmail-account-wizard generates a version-less .so file

[Steve Cossette]

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

Bug ID: 478381
   Summary: [5.27.80] kmail-account-wizard generates a
version-less .so file
Classification: Frameworks and Libraries
   Product: Akonadi
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Account Wizard
  Assignee: kdepim-bugs@kde.org
  Reporter: farch...@gmail.com
CC: c...@carlschwan.eu
  Target Milestone: ---

For 5.27.80, the following file is generated:

/usr/lib64/libaccountwizard.so which is very bad for fedora, would it be
possible to version it?

Thank you

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 377399] kontact loses imap connections constantly

[Steve]

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

--- Comment #4 from Steve  ---
I can't reproduce this with the current release. I needed help a long time ago.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Akonadi] [Bug 377982] Kontact sometimes fails to delete an email

[Steve]

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

--- Comment #2 from Steve  ---
No, I can't reproduce it. I needed help many years ago.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Akonadi] [Bug 377979] akonadi_mailfilter_agent is filling up my syslog

[Steve]

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

--- Comment #3 from Steve  ---
No, I can't reproduce it. I needed help many years ago.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 377590] kontact mail is unresponsive

[Steve]

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

--- Comment #2 from Steve  ---
No, I can't reproduce it. I needed help many years ago.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 378172] akonadi keeps losing track of emails

[Steve]

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

--- Comment #3 from Steve  ---
No, I can't reproduce it. I needed help many years ago.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[kontact] [Bug 442550] New: Kontact crashes on setup

[Steve Dietrich]

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

Bug ID: 442550
   Summary: Kontact crashes on setup
   Product: kontact
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: stevenbdietr...@gmail.com
  Target Milestone: ---

Application: kontact (5.18.1 (21.08.1))

Qt Version: 5.15.3
Frameworks Version: 5.86.0
Operating System: Linux 5.11.0-34-generic x86_64
Windowing System: X11
Drkonqi Version: 5.22.5
Distribution: KDE neon User Edition 5.22

-- Information about the crash:
- What I was doing when the application crashed:  Opened Kontact for 1st time.
Screen asked if I wanted to import from Evolution database (Evolution is not
installed. I purged it and did a hard restart before installing Kontact through
Muon). When I clicked 'No' to import that's when Kontact crashed.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault

[New LWP 1694]
[New LWP 1695]
[New LWP 1696]
[New LWP 1697]
[New LWP 1698]
[New LWP 1699]
[New LWP 1712]
[New LWP 1713]
[New LWP 1715]
[New LWP 1721]
[New LWP 1722]
[New LWP 1723]
[New LWP 1724]
[New LWP 1725]
[New LWP 1726]
[New LWP 1732]
[New LWP 1735]
[New LWP 1749]
[New LWP 1754]
[New LWP 1755]
[New LWP 1769]
[New LWP 1812]
[New LWP 1820]
[New LWP 1888]
[New LWP 1891]
[New LWP 1900]
[New LWP 1919]
[New LWP 1922]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7ffa12822aff in __GI___poll (fds=0x7ffe8bff9138, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
[Current thread is 1 (Thread 0x7ff9fdd09200 (LWP 1692))]

Thread 29 (Thread 0x7ff963fff700 (LWP 1922)):
#0  __GI___libc_read (nbytes=16, buf=0x7ff963ffe190, fd=136) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=136, buf=0x7ff963ffe190, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7ffa08b43b2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ffa08afaebe in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7ffa08afb312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7ffa08afb4a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7ffa12df25eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7ffa12d9687b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7ffa12bb0292 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7ffa12bb142c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7ffa0966d609 in start_thread (arg=) at
pthread_create.c:477
#11 0x7ffa1282f293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 28 (Thread 0x7ff969795700 (LWP 1919)):
#0  0x7ffa08b484dd in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7ffa08afaaf5 in g_main_context_query () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ffa08afb2e8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ffa08afb4a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7ffa12df25eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7ffa12d9687b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7ffa12bb0292 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7ffa12bb142c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7ffa0966d609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7ffa1282f293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 27 (Thread 0x7ff968d85700 (LWP 1900)):
#0  __GI___libc_read (nbytes=16, buf=0x7ff968d84190, fd=117) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=117, buf=0x7ff968d84190, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7ffa08b43b2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ffa08afaebe in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7ffa08afb312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7ffa08afb4a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7ffa12df25eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7ffa12d9687b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7ffa12bb0292 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7ffa12bb142c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7ffa0966d609 in start_thread (arg=) at
pthread_create.c:477
#11 0x7ffa1282f293 in clone () 

[akregator] [Bug 202370] closing tab sets focus to search instead of content

[Steve Goodey]

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

Steve Goodey  changed:

   What|Removed |Added

 CC|st...@goodey.org|

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 428184] New: Setting times for events and todo doesn't save defaults to 12:00am

[Steve MacLellan]

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

Bug ID: 428184
   Summary: Setting times for events and todo doesn't save
defaults to 12:00am
   Product: korganizer
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: todoview
  Assignee: kdepim-bugs@kde.org
  Reporter: st...@homebusiness-websites.com
  Target Milestone: ---

Created attachment 132686
  --> https://bugs.kde.org/attachment.cgi?id=132686=edit
Setting times for events and todo doesn't save defaults to 12:00am

SUMMARY
Setting times for events and todo doesn't save. When I click apply, the time
defaults to 12:00am

STEPS TO REPRODUCE
1. Installed this way from Software manager 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT
I would expect it would save the times set for appointments, events and todos.


SOFTWARE/OS VERSIONS 5.13.3 -- Linux mint 20 (x86_64) release 5.4.0-48-generic
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: ?
KDE Frameworks Version: 5.68.0
Qt Version: Qt 5.12.8 (built against 5.12.8)

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 399881] Kontact message list unresponsive

[Steve]

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

--- Comment #5 from Steve  ---
I have upgraded through 4 major versions of kontact since then. Right now my
biggest problem is email I delete suddenly reappears 5 or 10 minutes later. I
suppose its not getting deleted in the imap server and it rediscovers it next
poll. This really isn't fun because I have to delete email 3 or 4 times to
really get it deleted.

So, no. This problem went away with one of the upgrades. I suppose it can be
closed.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 424935] New: Akonadi crashes/loops importing imap mail box

[Steve]

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

Bug ID: 424935
   Summary: Akonadi crashes/loops importing imap mail box
   Product: Akonadi
   Version: 5.13.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: sgr...@redhat.com
  Target Milestone: ---

SUMMARY
There is a problem in one of my folders.
Aug  1 09:28:19 x2 akonadi_imap_resource[3094]: org.kde.pim.imapresource:
Detected inconsistency in local cache, we're missing some messages. Server: 
165935  Local:  9
Aug  1 09:28:19 x2 akonadi_imap_resource[3094]: org.kde.pim.imapresource:
Refetching complete mailbox.

So, it spends a long time fetching 5Gb of email. But before it can finish,

Aug  1 10:05:04 x2 akonadi_mixedmaildir_resource[3108]:
org.kde.pim.mixedmaildirresource: Failed to read item "1442061842.R339.x2" in
Maildir "/home/sgrubb/.kde/share/apps/kmail/mail/Fedora-devel"
Aug  1 10:06:11 x2 akonadi_mixedmaildir_resource[3108]:
org.kde.pim.mixedmaildirresource: Store fetch for new item "" in collection
-124 , "" did not return the expected item. error= 102 , "Error while reading
mails from folder Fedora-devel"
Aug  1 10:06:15 x2 akonadi_mixedmaildir_resource[3108]:
org.kde.pim.mixedmaildirresource: Failed to read item "1442061842.R339.x2" in
Maildir "/home/sgrubb/.kde/share/apps/kmail/mail/Fedora-devel"
Aug  1 10:06:15 x2 akonadi_mixedmaildir_resource[3108]:
org.kde.pim.mixedmaildirresource: Store fetch for new item "" in collection
-124 , "" did not return the expected item. error= 102 , "Error while reading
mails from folder Fedora-devel"
Aug  1 12:09:43 x2 akonadi_indexing_agent[3100]: org.kde.pim.akonadicore:
Failed to open external payload:
"/home/sgrubb/.local/share/akonadi/file_db_data/30/9573130_r0" "No such file or
directory"
Aug  1 12:09:43 x2 akonadi_indexing_agent[3100]: org.kde.pim.akonadicore:
Failed to open external payload:
"/home/sgrubb/.local/share/akonadi/file_db_data/33/9573133_r0" "No such file or
directory"

It does not work any longer. I have to reboot my system. It then repeats the
same cycle. My Fedora-devel folder is a local folder that my imap account gets
filtered into. No amount of refetching imap will fix the local folder. If there
was corruption in the imap cache, sure. But the local folder should just have
the missing entry deleted and life goes on.

How do I fix this? And can akonadi just delete missing entries to fix itself?
I'd rather lose an email than lose all of them.

Linux/KDE Plasma: 5.18.5-2
KDE Plasma Version:
KDE Frameworks Version: 19.12.2
Qt Version: 5.14.2

ADDITIONAL INFORMATION
This is a Fedora 32 x86_64 system.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 399881] Kontact message list unresponsive

[Steve]

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

--- Comment #2 from Steve  ---
The problem that I'm seeing seems to a communication problem between  akonadi
and kontact. I found some other bug reports online about various errors that
I'm seeing which suggested installing akonadiconsole. If I go into the IMAP
Account Agent and do various combinations of Synchronize Collection Tree,
Toggle Offline twice, and Synchronize All. And occassionally akonadictl
restart, I can get it working. Barely. Hope this sheds some light on the
problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 399881] Kontact message list unresponsive

[Steve]

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

--- Comment #1 from Steve  ---
When I run "akonadictl restart", I can briefly see the message list. Then email
pane in lower right corner goes black. And then both message list and email
viewer turn white. This is printed on the command line:

Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadicontrol: Executable "akonadi_knut_resource" for agent
"akonadi_knut_resource" could not be found!
org.kde.pim.calendarview: Agenda::removeIncidence() Failed to remove 
"a0225bad-cb82-4ed0-b177-6a4189b853b1"
org.kde.pim.akonadicontrol: "AgentManager::agentInstanceSynchronizeCollection" 
Agent instance  "akonadi_imap_resource_0"  has no resource interface!
org.kde.pim.akonadiserver: "Cannot connect to agent instance with identifier
'akonadi_imap_resource_0', error message: ''"
"No file selected."
org.kde.pim.maildispatcher: Item 2852642 does not have the required attribute
Address.
org.kde.pim.maildispatcher: Item 2847052 does not have the required attribute
Address.
org.kde.pim.maildispatcher: Item 2846814 does not have the required attribute
Address.

Does this indicate any kind of problem that I can look into for more
information?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 399881] New: Kontact message list unresponsive

[Steve]

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

Bug ID: 399881
   Summary: Kontact message list unresponsive
   Product: kontact
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: sgr...@redhat.com
  Target Milestone: ---

SUMMARY
When starting up kontact, the inbox icon under IMAP Account spins forever. The
message list is empty. No message is displayed. 

STEPS TO REPRODUCE
1. Start kontact


OBSERVED RESULT
Message list is empty.

EXPECTED RESULT
My email message list full of email. I have more than 150k messages in my
inbox.

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.13.5
KDE Frameworks Version: 18.04.3
Qt Version: 5.11.1
Kontact: Version 5.8.3

ADDITIONAL INFORMATION
How do you go about troubleshooting this? It's doing something. I see popup
notifications that I have new emails. But message list is empty. I wished that
it was more verbose so that I could diagnose what is happening.

I see this written to command line:
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadicontrol: Executable "akonadi_knut_resource" for agent
"akonadi_knut_resource" could not be found!
"No file selected."
org.kde.pim.maildispatcher: Item 2852642 does not have the required attribute
Address.
org.kde.pim.maildispatcher: Item 2847052 does not have the required attribute
Address.
org.kde.pim.maildispatcher: Item 2846814 does not have the required attribute
Address.
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)

ProtocolException thrown:Failed to write data to stream
org.kde.pim.akonadiserver: Protocol exception: Failed to write data to stream

Is that related? Something is failing to work and it's not saying something is
wrong. What do I need to look at to see why kontact isn't working? Thanks.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 395312] New: Folders not created

[Steve Cook]

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

Bug ID: 395312
   Summary: Folders not created
   Product: kmail2
   Version: 5.7.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: folders
  Assignee: kdepim-bugs@kde.org
  Reporter: steven.b.c...@me.com
  Target Milestone: ---

Right-click on folder, click Add Folder, enter folder name, nothing happens. No
folder is created.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[akregator] [Bug 377233] Deleting a message should select next message below

[Steve Goodey]

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

Steve Goodey <stevegoo...@spamcop.net> changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #2 from Steve Goodey <stevegoo...@spamcop.net> ---
And also in Kontact 5.5.2 openSUSE Leap 42.3.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[akregator] [Bug 381929] Feeds list gets corrupted when akregator is restored on log in

[Steve]

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

Steve <sweseme...@hotmail.com> changed:

   What|Removed |Added

 CC||sweseme...@hotmail.com

--- Comment #16 from Steve <sweseme...@hotmail.com> ---
Just wanted to add that this also happens on Fedora 26 and 27 (with all updates
applied).

The procedure in Comment 14 also works for me, ie it reproducible destroys the
feeds every time. 

Otherwise, the feed corruption is more hit and miss, ie it doesn't happen every
time I start Akregator but often enough to be annoying.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 383722] New: Can't read calendar list --- too small

[Steve]

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

Bug ID: 383722
   Summary: Can't read calendar list --- too small
   Product: korganizer
   Version: unspecified
  Platform: Mint (Debian based)
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: 1840tra...@gmail.com
  Target Milestone: ---

Created attachment 107371
  --> https://bugs.kde.org/attachment.cgi?id=107371=edit
Screenshot of the calendar (just launched for the first time)...can't read
calendar selection area.

Where you can select the calendars in the bottom left corner...the print is so
small, can't be read.  Can't even click on it without de-selecting or selecting
a calendar.  Have to arrow around and hit spacebar to even guess at which
calendar is showing up and which isn't.  I have three calendars I'm using, but
even just starting the program up...the two default calendars (for the first
time launch) are the same super small font and type.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[akregator] [Bug 377233] Deleting a message should select next message below

[Steve Goodey]

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

Steve Goodey <stevegoo...@spamcop.net> changed:

   What|Removed |Added

 CC||stevegoo...@spamcop.net

--- Comment #1 from Steve Goodey <stevegoo...@spamcop.net> ---
I can confirm this, Kontact 5.3.0 (QtWebEngine), openSUSE Leap 42.2.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 369247] Kontact 5.4.0: settings between Kontact and components (e.g. KMail) are not synchronized

[Steve Goodey]

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

Steve Goodey <stevegoo...@spamcop.net> changed:

   What|Removed |Added

 CC||stevegoo...@spamcop.net

-- 
You are receiving this mail because:
You are the assignee for the bug.

[akregator] [Bug 202370] closing tab sets focus to search instead of content

[Steve Goodey]

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

--- Comment #15 from Steve Goodey <stevegoo...@spamcop.net> ---
Referring to Comment 3, "It does work as expected when using the mouse, but not
when using keyboard shortcut."

I have the same problem even using the mouse. Close tab using mouse, cursor
blinks in search field. Have to click a different article to get cursor out of
search field.

Steve.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[akregator] [Bug 202370] closing tab sets focus to search instead of content

[Steve Goodey]

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

Steve Goodey <stevegoo...@spamcop.net> changed:

   What|Removed |Added

 CC||stevegoo...@spamcop.net

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 377395] Kontact is crashing during start up

[Steve]

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

--- Comment #8 from Steve <sgr...@redhat.com> ---
>From the Qt bug:

Could it be that you use the same QUrlRequestInterceptor multiple times, pass
the Tab/WebEngineView/WebEnginePage to the constructor of the
RequestInterceptor (making it the RequestInterceptors parent) and the crash
happens at the next navigation after you closed the last view you created? That
would mean that the RequestInterceptor is deleted by closing the tab (because
that's its parent) and then the next navigation accesses pointer which is
dangling at this point.

Is this correct? Any comments I should relay to the Qt folks?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 377395] Kontact is crashing during start up

[Steve]

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

--- Comment #7 from Steve <sgr...@redhat.com> ---
OK, just as I predicted, the Qt people are asking me questions I have no idea
how to answer. Can someone from the Kontact team hop on the Qt bug at
https://bugreports.qt.io/browse/QTBUG-59876 and participate in answering
questions? I'll do my part if anything Fedora related comes along. Thanks.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 377395] Kontact is crashing during start up

[Steve]

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

--- Comment #6 from Steve <sgr...@redhat.com> ---
OK. I filed a bz here:
https://bugreports.qt.io/browse/QTBUG-59876

I was kind of hoping someone from KDEpim team would interact with the Qt people
because I have almost no chance of answering their questions about kontact's
code. I guess we'll see what comes up.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 377985] I have 2 emails in outbox that I cannot delete

[Steve]

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

--- Comment #1 from Steve <sgr...@redhat.com> ---
It happened again. 

Mar 30 12:03:15 x2 akonadi_mixedmaildir_resource: "Given item identifier is
empty"
Mar 30 12:03:15 x2 akonadi_mixedmaildir_resource: Item(remoteId= "" , mimeType=
"message/rfc822" , parentCollection= "outbox" )
Mar 30 12:03:15 x2 akonadi_mixedmaildir_resource: log_mixedmaildirresource:
"Given item identifier is empty"

It seems to always be 2 emails. They were both sent yesterday. But today they
show up in my outbox. I can't delete them.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 377656] akonadiserver has an unhandled protocol exception

[Steve]

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

Steve <sgr...@redhat.com> changed:

   What|Removed |Added

Summary|akonadiserver is aborting   |akonadiserver has an
   ||unhandled protocol
   ||exception

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 378240] New: akonadiserver is aborting from the logger

[Steve]

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

Bug ID: 378240
   Summary: akonadiserver is aborting from the logger
   Product: Akonadi
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: libakonadi
  Assignee: kdepim-bugs@kde.org
  Reporter: sgr...@redhat.com
  Target Milestone: ---

Application: akonadi_control (akonadi_control), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
29return SYSCALL_CANCEL (wait4, pid, stat_loc, options, NULL);
[KCrash Handler]
#4  0x7ff31b266765 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#5  0x7ff31b26836a in __GI_abort () at abort.c:89
#6  0x7ff31bf2d4a1 in QMessageLogger::fatal(char const*, ...) const
(context=..., message=) at global/qlogging.cpp:1648
#7  0x7ff31bf2d4a1 in QMessageLogger::fatal(char const*, ...) const
(this=this@entry=0x7ffc76a8d190, msg=msg@entry=0x55dbf42b7d90 "Cannot remove
old log file - running on a readonly filesystem maybe?") at
global/qlogging.cpp:790
#8  0x55dbf42ae481 in akInit(QString const&) (appName=...) at
/usr/src/debug/akonadi-16.12.3/src/shared/akdebug.cpp:197
#9  0x55dbf42ac232 in AkApplicationBase::init() (this=0x7ffc76a8d450) at
/usr/src/debug/akonadi-16.12.3/src/shared/akapplication.cpp:62
#10 0x55dbf4288bfb in main(int, char**) (loggingCategory=...,
argv=0x7ffc76a8d5b8, argc=@0x7ffc76a8d2bc: 1, this=0x7ffc76a8d450) at
/usr/src/debug/akonadi-16.12.3/src/shared/akapplication.h:83
#11 0x55dbf4288bfb in main(int, char**) (argc=,
argv=0x7ffc76a8d5b8) at
/usr/src/debug/akonadi-16.12.3/src/akonadicontrol/main.cpp:56

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 378172] New: akonadi keeps losing track of emails

[Steve]

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

Bug ID: 378172
   Summary: akonadi keeps losing track of emails
   Product: Akonadi
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: IMAP resource
  Assignee: chrig...@fastmail.fm
  Reporter: sgr...@redhat.com
CC: kdepim-bugs@kde.org, vkra...@kde.org
  Target Milestone: ---

Mar 27 09:23:51 x2 akonadi_imap_resource: org.kde.pim.imapresource: Detected
inconsistency in local cache, we're missing some messages. Server:  116243 
Local:  116239
Mar 27 09:23:51 x2 akonadi_imap_resource: org.kde.pim.imapresource: Refetching
complete mailbox.

Mar 27 10:18:33 x2 akonadi_imap_resource: org.kde.pim.imapresource: Detected
inconsistency in local cache, we're missing some messages. Server:  116246 
Local:  116244
Mar 27 10:18:33 x2 akonadi_imap_resource: org.kde.pim.imapresource: Refetching
complete mailbox.


Mar 27 12:35:38 x2 akonadi_imap_resource: org.kde.pim.imapresource: Detected
inconsistency in local cache, we're missing some messages. Server:  116254 
Local:  116244
Mar 27 12:35:38 x2 akonadi_imap_resource: org.kde.pim.imapresource: Refetching
complete mailbox.

Mar 27 13:17:52 x2 akonadi_imap_resource: org.kde.pim.imapresource: Detected
inconsistency in local cache, we're missing some messages. Server:  116311 
Local:  116308
Mar 27 13:17:52 x2 akonadi_imap_resource: org.kde.pim.imapresource: Refetching
complete mailbox.

Mar 27 13:42:56 x2 akonadi_imap_resource: org.kde.pim.imapresource: Detected
inconsistency in local cache, we're missing some messages. Server:  116301 
Local:  116300
Mar 27 13:42:56 x2 akonadi_imap_resource: org.kde.pim.imapresource: Refetching
complete mailbox.

Whenever this happens it takes 20 - 30 minutes to become useful again.
Sometimes after syncing, it filters mail, and suddenly it detects an
inconsistency and refetches the whole mail box again. Could it be a threading
problem where the filter moves mail without updating the count? The reason I
ask is the problem seems to also coincide with:

Mar 27 13:42:56 x2 akonadi_mailfilter_agent: org.kde.pim.akonadicore: Got a
stale notification for an item which was already removed. 2063284 ""
Mar 27 13:42:56 x2 akonadi_archivemail_agent: org.kde.pim.akonadicore: Got a
stale notification for an item which was already removed. 2063284 ""

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Akonadi] [Bug 377985] New: I have 2 emails in outbox that I cannot delete

[Steve]

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

Bug ID: 377985
   Summary: I have 2 emails in outbox that I cannot delete
   Product: Akonadi
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Mixed Maildir resource
  Assignee: kdepim-bugs@kde.org
  Reporter: sgr...@redhat.com
CC: kram...@kde.org
  Target Milestone: ---

I have 2 emails in my outbox that I cannot delete. Trying to delete them causes
these messages in syslog:

Mar 23 13:01:37 x2 akonadi_mixedmaildir_resource: "Given item identifier is
empty"
Mar 23 13:01:38 x2 akonadi_mixedmaildir_resource: Item(remoteId= "" , mimeType=
"message/rfc822" , parentCollection= "outbox" )
Mar 23 13:01:38 x2 akonadi_mixedmaildir_resource: log_mixedmaildirresource:
"Given item identifier is empty"

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 377983] New: Getting a lot of indexer syslog messages

[Steve]

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

Bug ID: 377983
   Summary: Getting a lot of indexer syslog messages
   Product: Akonadi
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Indexer
  Assignee: kdepim-bugs@kde.org
  Reporter: sgr...@redhat.com
CC: chrig...@fastmail.fm, dvra...@kde.org
  Target Milestone: ---

I don't know if this is the right component for this. Please move it to the
correct one if necessary. But I'm getting a lot of these messages:

Mar 23 12:55:55 x2 akonadiserver: org.kde.pim.akonadiplugin_indexer: unknown
term  "attachment"

# grep akonadiplugin_indexer /var/log/messages | wc -l
635

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 377982] New: Kontact sometimes fails to delete an email

[Steve]

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

Bug ID: 377982
   Summary: Kontact sometimes fails to delete an email
   Product: Akonadi
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: IMAP resource
  Assignee: chrig...@fastmail.fm
  Reporter: sgr...@redhat.com
CC: kdepim-bugs@kde.org, vkra...@kde.org
  Target Milestone: ---

Mar 23 12:48:25 x2 akonadi_imap_resource: org.kde.pim.imapresource: Expunge
failed:  "Expunge failed, server replied: A19 NO mailbox selected READ-ONLY
"
Mar 23 12:48:28 x2 akonadi_imap_resource: org.kde.pim.imapresource: Expunge
failed:  "Expunge failed, server replied: A55 NO mailbox selected READ-ONLY
"
Mar 23 12:48:29 x2 akonadi_imap_resource: org.kde.pim.imapresource: Expunge
failed:  "Expunge failed, server replied: A67 NO mailbox selected READ-ONLY
"

When this happens the whole application becomes unresponsive to any email you
click on.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Akonadi] [Bug 377979] New: akonadi_mailfilter_agent is filling up my syslog

[Steve]

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

Bug ID: 377979
   Summary: akonadi_mailfilter_agent is filling up my syslog
   Product: Akonadi
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Mail Filter Agent
  Assignee: kdepim-bugs@kde.org
  Reporter: sgr...@redhat.com
  Target Milestone: ---

Something happened and now my syslog is filling up with this message:

Mar 23 11:52:53 x2 akonadi_mailfilter_agent: org.kde.pim.mailfilteragent:
Cannot find filter object with id "Gobw30QYSPYHD36E"

# grep akonadi_mailfilter_agent /var/log/messages | wc -l
126120

Is it really necessary to log this failure so many times? Can it be rate
limited?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kdepimlibs] [Bug 377946] New: Findings from a code review

[Steve]

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

Bug ID: 377946
   Summary: Findings from a code review
   Product: kdepimlibs
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: sgr...@redhat.com
  Target Milestone: ---

Missing break/return:
kdepimlibs-4.14.10/akonadi/calendar/calendarmodel.cpp:115: unterminated_case:
The case for value "Qt::DisplayRole" is not terminated by a 'break' statement.
kdepimlibs-4.14.10/akonadi/calendar/calendarmodel.cpp:153: fallthrough: The
above case falls through to this one.

Confused code:
kdepimlibs-4.14.10/akonadi/entitylistview.cpp:193: cond_const: Condition
"menuCanceled", taking false branch. Now the value of "menuCanceled" is equal
to 0.
kdepimlibs-4.14.10/akonadi/entitylistview.cpp:195: const: At condition
"menuCanceled", the value of "menuCanceled" must be equal to 0.
kdepimlibs-4.14.10/akonadi/entitylistview.cpp:195: dead_error_condition: The
condition "menuCanceled" cannot be true.
kdepimlibs-4.14.10/akonadi/entitylistview.cpp:196: dead_error_line: Execution
cannot reach this statement: "return;".

Object Passed by Value instead of Reference:
kdepimlibs-4.14.10/kcal/icalformat_p.cpp:2548: pass_by_value: Passing parameter
r of type "icalrecurrencetype" (size 2904 bytes) by value.

Unterminated string possible:
kdepimlibs-4.14.10/kcalcore/versit/vobject.c:1238: buffer_size_warning: strncpy
does not terminate strings if they are equal to or larger than the size passed,
To be safe it needs to be manually terminated: buf1[255] = 0;

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 377939] New: Mail is getting deleted

[Steve]

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

Bug ID: 377939
   Summary: Mail is getting deleted
   Product: kontact
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: mail
  Assignee: kdepim-bugs@kde.org
  Reporter: sgr...@redhat.com
  Target Milestone: ---

Sometimes when I click on an email, instead of showing it in the pane below the
list, the mail gets deleted. Permanently. Without moving it to the trash. I
confirmed this by using a web mail interface to the imap server and see that
mail is gone forever.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 377395] Kontact is crashing during start up

[Steve]

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

--- Comment #4 from Steve <sgr...@redhat.com> ---
Here's the output from the Fedora Retrace Server after analyzing one of my
crashes:

https://retrace.fedoraproject.org/faf/reports/1636854/

I guess this confirms the issue is in Qt. Does anyone here have contacts with
Qt project or know who to direct this to?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 377656] akonadiserver is aborting

[Steve]

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

--- Comment #6 from Steve <sgr...@redhat.com> ---
Some information printed to the console around the time of another abort:

org.kde.pim.akonadicore: Got a stale notification for an item which was already
removed. 2061954 ""
org.kde.pim.akonadicore: Got a stale notification for an item which was already
removed. 2061955 ""
org.kde.pim.akonadicore: "QLocalSocket: Remote closed"
"/tmp/akonadi-sgrubb.jJx32f/akonadiserver-cmd.socket"
org.kde.pim.akonadicore: Socket error occurred: "QLocalSocket: Remote closed"
org.kde.pim.akonadicore: Error on fetching collection statistics:  ""
org.kde.pim.akonadicore: "QLocalSocket: Remote closed"
"/tmp/akonadi-sgrubb.jJx32f/akonadiserver-cmd.socket"
org.kde.pim.akonadicore: Socket error occurred: "QLocalSocket: Remote closed"
org.kde.pim.akonadicore: "QLocalSocket: Remote closed"
"/tmp/akonadi-sgrubb.jJx32f/akonadiserver-ntf.socket"
org.kde.pim.akonadicore: "QLocalSocket: Remote closed"
"/tmp/akonadi-sgrubb.jJx32f/akonadiserver-ntf.socket"
org.kde.pim.akonadicore: "QLocalSocket: Remote closed"
"/tmp/akonadi-sgrubb.jJx32f/akonadiserver-ntf.socket"
org.kde.pim.akonadicore: "QLocalSocket: Remote closed"
"/tmp/akonadi-sgrubb.jJx32f/akonadiserver-ntf.socket"
org.kde.pim.akonadicore: "QLocalSocket: Remote closed"
"/tmp/akonadi-sgrubb.jJx32f/akonadiserver-ntf.socket"
org.kde.pim.akonadicore: "QLocalSocket: Remote closed"
"/tmp/akonadi-sgrubb.jJx32f/akonadiserver-ntf.socket"
org.kde.pim.akonadicore: "QLocalSocket: Remote closed"
"/tmp/akonadi-sgrubb.jJx32f/akonadiserver-ntf.socket"
"Unknown error."
org.kde.pim.akonadicore: Error on fetching collection statistics:  ""
"Unknown error."
org.kde.pim.akonadicore: Error on fetching collection statistics:  ""

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 377897] New: Findings from code review

[Steve]

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

Bug ID: 377897
   Summary: Findings from code review
   Product: Akonadi
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: sgr...@redhat.com
  Target Milestone: ---

Leaked FD:
akonadi-16.12.2/src/rds/bridgeconnection.cpp:96: open_fn: Returning handle
opened by "socket".
akonadi-16.12.2/src/rds/bridgeconnection.cpp:96: var_assign: Assigning: "fd" =
handle returned from "socket(1, SOCK_STREAM, 0)".
akonadi-16.12.2/src/rds/bridgeconnection.cpp:103: noescape: Resource "fd" is
not freed or pointed-to in "connect".
akonadi-16.12.2/src/rds/bridgeconnection.cpp:107: leaked_handle: Handle
variable "fd" going out of scope leaks the handle.

Missing return statements:
akonadi-16.12.2/src/server/handler.cpp:216: unterminated_case: The case for
value "Akonadi::Protocol::Command::SubscriptionChangeNotification" is not
terminated by a 'break' statement.
akonadi-16.12.2/src/server/handler.cpp:219: fallthrough: The above case falls
through to this one.
akonadi-16.12.2/src/server/handler.cpp:222: fallthrough: The above case falls
through to this one.

Identical branches:
akonadi-16.12.2/x86_64-redhat-linux-gnu/src/agentbase/moc_preprocessorbase.cpp:87:
implicit_else: The code from the above if-then branch is identical to the code
after the if statement.
akonadi-16.12.2/x86_64-redhat-linux-gnu/src/agentbase/moc_preprocessorbase.cpp:85:
identical_branches: The same code is executed when the condition "_id < 0" is
true or false, because the code in the if-then branch and after the if
statement is identical.

The identical branches is in other files, too. You can probably grep on it.

Missing Break:
akonadi-16.12.2/src/core/changerecorder_p.cpp:95: unterminated_case: The case
for value "Akonadi::ChangeRecorderPrivate::Collection" is not terminated by a
'break' statement.
akonadi-16.12.2/src/core/changerecorder_p.cpp:97: fallthrough: The above case
falls through to this one.

Double return statements, is the first one supposed to be there?:
akonadi-16.12.2/src/private/protocol.cpp:8019: unreachable: This code cannot be
reached: "return stream;".

Another double return:
akonadi-16.12.2/src/private/protocol.cpp:8025: unreachable: This code cannot be
reached: "return stream;".

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 377395] Kontact is crashing during start up

[Steve]

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

--- Comment #3 from Steve <sgr...@redhat.com> ---
I was able to get a core dump to get a full backtrace. Only including some
lines right before the crash.

#1  0x7ff0688d54fe in KCrash::defaultCrashHandler(int) ()
at /lib64/libKF5Crash.so.5
#2  0x7ff0635157e0 in  () at /usr/lib64/libc-2.23.so
#3  0x7ff05e964b3e in
QtWebEngineCore::NetworkDelegateQt::OnBeforeURLRequest(net::URLRequest*,
base::Callback const&, GURL*) (this=0x7ff03a50,
request=, callback=..., newUrl=0x7ff00069b140)
at
/usr/src/debug/qtwebengine-opensource-src-5.6.2/src/core/network_delegate_qt.cpp:111
requestInfo = {d_ptr = {d = 0x7ff000608710}}
resourceInfo = 0x7ff000560920
resourceType = content::RESOURCE_TYPE_STYLESHEET
navigationType = 0
qUrl = {d = 0x7ff00041cf60}
interceptor = 0x55c3ceecdd50
renderProcessId = -277647872
renderFrameId = 1305607009
params = 
  {url = {d = 0x7ff00041cfc0}, isMainFrameRequest = 2, navigationType =
32752, renderProcessId = 3, renderFrameId = 0}
__FUNCTION__ = "OnBeforeURLRequest"
#4  0x7ff05f258210 in
net::NetworkDelegate::NotifyBeforeURLRequest(net::URLRequest*,
base::Callback const&, GURL*) (this=0x7ff03a50,
request=request@entry=0x7ff00069b030, callback=...,
new_url=new_url@entry=0x7ff00069b140)
at
/usr/src/debug/qtwebengine-opensource-src-5.6.2/src/3rdparty/chromium/net/base/network_delegate.cc:26
tracking_profile = 
  {scoped_profile_ = {birth_ = 0x0, stopwatch_ = {start_time_ =
{ms_ = 0}, wallclock_duration_ms_ = 0, current_thread_data_ = 0x0,
excluded_duration_ms_ = 0, parent_ = 0x0}}}
#5  0x7ff05f21c800 in net::URLRequest::Start() (this=0x7ff00069b030)
at
/usr/src/debug/qtwebengine-opensource-src-5.6.2/src/3rdparty/chromium/net/url_request/url_request.cc:514
tracking_profile25 = 
  {scoped_profile_ = {birth_ = 0x0, stopwatch_ = {start_time_ =
{ms_ = 0}, wallclock_duration_ms_ = 0, current_thread_data_ = 0x0,
excluded_duration_ms_ = 0, parent_ = 0x0}}}
error = 
---Type  to continue, or q  to quit---
tracking_profile = 
  {scoped_profile_ = {birth_ = 0x0, stopwatch_ = {start_time_ =
{ms_ = 0}, wallclock_duration_ms_ = 0, current_thread_data_ = 0x0,
excluded_duration_ms_ = 0, parent_ = 0x0}}}
tracking_profile2 = 
  {scoped_profile_ = {birth_ = 0x0, stopwatch_ = {start_time_ =
{ms_ = 0}, wallclock_duration_ms_ = 0, current_thread_data_ = 0x0,
excluded_duration_ms_ = 0, parent_ = 0x0}}}
#6  0x7ff05f447da0 in content::ResourceLoader::StartRequestInternal()
(this=0x7ff0003b9900)
at
/usr/src/debug/qtwebengine-opensource-src-5.6.2/src/3rdparty/chromium/content/browser/loader/resource_loader.cc:498

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 377656] akonadiserver is aborting

[Steve]

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

--- Comment #4 from Steve <sgr...@redhat.com> ---
In src/server/connection.cpp at line 404, there should probably be a try/catch
around the Protocol::serialize() call:

void Connection::sendResponse(qint64 tag, const Protocol::Command )
{
if (Tracer::self()->currentTracer() != QLatin1String("null")) {
Tracer::self()->connectionOutput(m_identifier, QByteArray::number(tag)
+ ' ' + response.debugString().toUtf8());
}
QDataStream stream(m_socket);
stream << tag;
Protocol::serialize(m_socket, response);
}

because way down at the bottom in src/private/datastream_p_p.h at line 92, we
find:

if (mDev->write((char *), sizeof(T)) != sizeof(T)) {
throw Akonadi::ProtocolException("Failed to write data to stream");
}

Does this help?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 377395] Kontact is crashing during start up

[Steve]

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

--- Comment #2 from Steve <sgr...@redhat.com> ---
I've had about 20 recurrences of this bug today. Sometimes one of the threads
is holding a mutex in the video drivers. The only solution is to reboot the
whole system. I've rebooted my system about 10 times today. I have also spent 5
hours trying to access my email so that I can work. Between akonadi aborting
and kontact crashing on start up, the whole mess is unusable. Not to mention
that when it filters an email it has to resync the whole inbox which has > 150k
emails in it. This alone takes 45 minutes on a good day.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 377656] akonadiserver is aborting

[Steve]

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

--- Comment #2 from Steve <sgr...@redhat.com> ---
I think this is different because its dying via an abort() call. They are
usually placed in code to stop a program when its doing something that violates
some expectation. The idea is to force a coredump to collect a backtrace to get
an idea of what's wrong.

At line 8 the code throws a protocol exception and this probably comes near the
code mentioned in line 9. So, something unexpected in the imap protocol is
probably causing the issue.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 377656] New: akonadiserver is aborting

[Steve]

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

Bug ID: 377656
   Summary: akonadiserver is aborting
   Product: Akonadi
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: sgr...@redhat.com
  Target Milestone: ---

Kontact was in the process of checking my mail box and then akonadiserver
crashed. This is the back trace from the core dump:

#0  0x7fbbd3405765 in __GI_raise (sig=6) at
../sysdeps/unix/sysv/linux/raise.c:54
resultvar = 0
pid = 3597
selftid = 3757
#1  0x7fbbd4aa94fe in KCrash::defaultCrashHandler(int) () at
/lib64/libKF5Crash.so.5
#2  0x7fbbd34057e0 in  () at /usr/lib64/libc-2.23.so
#3  0x7fbbd3405765 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
resultvar = 0
pid = 3597
selftid = 3757
#4  0x7fbbd340736a in __GI_abort () at abort.c:89
save_stage = 2
act = 
  {__sigaction_handler = {sa_handler = 0x0, sa_sigaction = 0x0},
sa_mask = {__val = {0, 0, 140444680092703, 140444683527456, 1, 140444683527587,
0, 18446744073709551615, 140444692594536, 140442175780560, 140442175780560, 1,
140444157013744, 140440800154128, 140444520413392, 140442175780608}}, sa_flags
= -741075808, sa_restorer = 0x7fbaec001918}
sigs = {__val = {32, 0 }}
#5  0x7fbbd3d4452d in __gnu_cxx::__verbose_terminate_handler() () at
../../../../libstdc++-v3/libsupc++/vterminate.cc:95
terminating = true
t = 
#6  0x7fbbd3d422d6 in __cxxabiv1::__terminate(void (*)())
(handler=) at
../../../../libstdc++-v3/libsupc++/eh_terminate.cc:47
#7  0x7fbbd3d42321 in std::terminate() () at
../../../../libstdc++-v3/libsupc++/eh_terminate.cc:57
#8  0x7fbbd3d42539 in __cxxabiv1::__cxa_throw(void*, std::type_info*, void
(*)(void*)) (obj=obj@entry=0x7fbaec015280, tinfo=0x55b315d71bc8 , 
tinfo@entry=0x7fbbd480dc28 ,
dest=dest@entry=0x7fbbd45af7b0
)
at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:87
globals = 
#9  0x7fbbd45cae42 in Akonadi::Protocol::DataStream::operator<< (unsigned char) (this=, val=)
at /usr/src/debug/akonadi-16.12.2/src/private/datastream_p_p.h:92
#10 0x7fbbd45ce57f in
Akonadi::Protocol::FetchItemsResponsePrivate::serialize(Akonadi::Protocol::DataStream&)
const (stream=..., this=0x7fbaec021920)
at /usr/src/debug/akonadi-16.12.2/src/private/protocol.cpp:266
#11 0x7fbbd45ce57f in
Akonadi::Protocol::FetchItemsResponsePrivate::serialize(Akonadi::Protocol::DataStream&)
const (stream=..., this=0x7fbaec021920)
at /usr/src/debug/akonadi-16.12.2/src/private/protocol.cpp:425
#12 0x7fbbd45ce57f in
Akonadi::Protocol::FetchItemsResponsePrivate::serialize(Akonadi::Protocol::DataStream&)
const (this=0x7fbaec021920, stream=...)
at /usr/src/debug/akonadi-16.12.2/src/private/protocol.cpp:3344
#13 0x7fbbd45b5b14 in Akonadi::Protocol::serialize(QIODevice*,
Akonadi::Protocol::Command const&) (command=..., stream=...)
at /usr/src/debug/akonadi-16.12.2/src/private/protocol.cpp:383
stream = {mDev = 0x7fbb140030d0, mWaitTimeout = 3}
#14 0x7fbbd45b5b14 in Akonadi::Protocol::serialize(QIODevice*,
Akonadi::Protocol::Command const&) (device=, command=...)
at /usr/src/debug/akonadi-16.12.2/src/private/protocol.cpp:636
stream = {mDev = 0x7fbb140030d0, mWaitTimeout = 3}
#15 0x55b3159b2f33 in Akonadi::Server::Connection::sendResponse(long long,
Akonadi::Protocol::Command const&) (this=0x55b317374a50, tag=1000,
response=...) at /usr/src/debug/akonadi-16.12.2/src/server/connection.cpp:404
stream = 
  {d = {d = 0x0}, dev = 0x7fbb140030d0, owndev = false, noswap = false,
byteorder = QDataStream::BigEndian, ver = 17, q_status =
QDataStream::WriteFailed}
#16 0x55b3159b7412 in Akonadi::Server::Handler::failureResponse(QString
const&) (response=..., this=0x7fbaec0151d0)
at /usr/src/debug/akonadi-16.12.2/src/server/handler.cpp:268
r = { = {d_ptr = {d = 0x7fbaec021920}}, }
#17 0x55b3159b7412 in Akonadi::Server::Handler::failureResponse(QString
const&) (this=0x7fbaec0151d0, response=...)
at /usr/src/debug/akonadi-16.12.2/src/server/handler.h:152
r = { = {d_ptr = {d = 0x7fbaec021920}}, }
#18 0x55b3159b7412 in Akonadi::Server::Handler::failureResponse(QString
const&) (this=this@entry=0x7fbaec0151d0, failureMessage=...)
at /usr/src/debug/akonadi-16.12.2/src/server/handler.cpp:261
r = { = {d_ptr = {d = 0x7fbaec021920}}, }
#19 0x55b3159b75cf in Akonadi::Server::Handler::failureResponse(char
const*) (this=0x7fbaec0151d0, failureMessage=)
at /usr/src/debug/akonadi-16.12.2/src/server/handler.cpp:252
#20 0x55b3159b4f33 in Akonadi::Server::Connection::slotNewData()
(this=0x55b317374a50) at

[Akonadi] [Bug 377399] kontact loses imap connections constantly

[Steve]

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

--- Comment #1 from Steve <sgr...@redhat.com> ---
This happened another 3 or 4 times today. Is there any troubleshooting
information you might want? Sometimes it segfaults, sometimes the front-end
just cannot communicate at all.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[kontact] [Bug 377590] New: kontact mail is unresponsive

[Steve]

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

Bug ID: 377590
   Summary: kontact mail is unresponsive
   Product: kontact
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: mail
  Assignee: kdepim-bugs@kde.org
  Reporter: sgr...@redhat.com
  Target Milestone: ---

Sometimes I delete emails, it says moved to trash but they are still in my
inbox. Clicking on mail causes it to say its getting the email but it never
does. I restart kontact many, many times to get it to work. Its like the front
end and the back end cannot communicate reliably. And...there is no message on
the front end that gives any message about what might be wrong so that I can
report a proper error to you. Please increase the verbosity of error
information so I can give you information about what's wrong.

kontact-16.12.2-1.fc24
kdepim-16.12.2-3.fc24
kmail-16.12.2-1.fc24

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 377399] kontact loses imap connections constantly

[Steve]

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

Steve <sgr...@redhat.com> changed:

   What|Removed |Added

Summary|kontact loses imap  |kontact loses imap
   |connections constatntly |connections constantly

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Akonadi] [Bug 377399] New: kontact loses imap connections constatntly

[Steve]

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

Bug ID: 377399
   Summary: kontact loses imap connections constatntly
   Product: Akonadi
   Version: 1.13.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: IMAP resource
  Assignee: chrig...@fastmail.fm
  Reporter: sgr...@redhat.com
CC: kdepim-bugs@kde.org, vkra...@kde.org
  Target Milestone: ---

kontact keeps losing connections with the imap server. 

Mar  8 18:46:15 x2 akonadi_imap_resource: org.kde.pim.akonadicore: The item
sync is being rolled-back.
Mar  8 18:46:15 x2 akonadi_imap_resource: org.kde.pim.imapresource: Fetch job
failed  "Connection to server lost."
Mar  8 18:46:15 x2 akonadi_imap_resource: org.kde.pim.imapresource: ""
Mar  8 18:46:47 x2 akonadi_imap_resource: org.kde.pim.kimap: Connection to
server lost  0
Mar  8 18:46:47 x2 akonadi_imap_resource: org.kde.pim.imapresource: Session
login cancelled

I can usually access 1 or 2 emails before it loses the session. It becomes
unresponsive and if I shutdown and restart kontact, it segfaults. Kontact is so
complex the only solution is to reboot the system.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[kontact] [Bug 377395] New: Kontact is crashing during start up

[Steve]

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

Bug ID: 377395
   Summary: Kontact is crashing during start up
   Product: kontact
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: sgr...@redhat.com
  Target Milestone: ---

Application: kontact (5.4.2)

Qt Version: 5.6.2
Frameworks Version: 5.31.0
Operating System: Linux 4.9.13-100.fc24.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
Kontact was not showing mail contents when I clicked on a message. I shut down
kontact. Waited a couple seconds. Then restarted it. The screen flickered and I
have a crash notification.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
185 62: movl(%rsp), %edi
[Current thread is 1 (Thread 0x7fe697b9c940 (LWP 6015))]

Thread 30 (Thread 0x7fe58a648700 (LWP 6582)):
#0  0x7fe6ae7d156d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fe6a5296a06 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7fe6a5296b1c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7fe6af5d780b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fe57c02d2b0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7fe6af58683a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fe58a647c80, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:206
#5  0x7fe6af3e5343 in QThread::exec() (this=) at
thread/qthread.cpp:500
#6  0x7fe6af3e99aa in QThreadPrivate::start(void*) (arg=0x559642a1e650) at
thread/qthread_unix.cpp:365
#7  0x7fe6a6f4c5ca in start_thread (arg=0x7fe58a648700) at
pthread_create.c:333
#8  0x7fe6ae7dd0ed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 29 (Thread 0x7fe56abfd700 (LWP 6100)):
#0  0x7fe6ae7d156d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fe6a5296a06 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7fe6a5296b1c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7fe6af5d780b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fe56940, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7fe6af58683a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fe56abfcc80, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:206
#5  0x7fe6af3e5343 in QThread::exec() (this=) at
thread/qthread.cpp:500
#6  0x7fe6af3e99aa in QThreadPrivate::start(void*) (arg=0x55966473cf60) at
thread/qthread_unix.cpp:365
#7  0x7fe6a6f4c5ca in start_thread (arg=0x7fe56abfd700) at
pthread_create.c:333
#8  0x7fe6ae7dd0ed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 28 (Thread 0x7fe56b3fe700 (LWP 6076)):
#0  0x7fe6a6f51bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fe6ab0cf959 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() at /lib64/libQt5WebEngineCore.so.5
#2  0x7fe6ab0d0020 in base::SequencedWorkerPool::Worker::Run() () at
/lib64/libQt5WebEngineCore.so.5
#3  0x7fe6ab0d01f0 in base::SimpleThread::ThreadMain() () at
/lib64/libQt5WebEngineCore.so.5
#4  0x7fe6ab0ccc2d in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#5  0x7fe6a6f4c5ca in start_thread (arg=0x7fe56b3fe700) at
pthread_create.c:333
#6  0x7fe6ae7dd0ed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 27 (Thread 0x7fe56bbff700 (LWP 6075)):
#0  0x7fe6a6f51bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fe6ab0cf959 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() at /lib64/libQt5WebEngineCore.so.5
#2  0x7fe6ab0d0020 in base::SequencedWorkerPool::Worker::Run() () at
/lib64/libQt5WebEngineCore.so.5
#3  0x7fe6ab0d01f0 in base::SimpleThread::ThreadMain() () at
/lib64/libQt5WebEngineCore.so.5
#4  0x7fe6ab0ccc2d in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#5  0x7fe6a6f4c5ca in start_thread (arg=0x7fe56bbff700) at
pthread_create.c:333
#6  0x7fe6ae7dd0ed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 26 (Thread 0x7fe5737fe700 (LWP 6053)):
#0  0x7fe6ae7cd1cd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fe6a52d9660 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x7fe6a52964d6 in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7fe6a52969a4 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  

[Akonadi] [Bug 377393] /usr/bin/akonadiserver crashes

[Steve]

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

--- Comment #1 from Steve <sgr...@redhat.com> ---
Also scrolling errors like this in syslog:

Mar  8 15:47:33 x2 akonadi_mailfilter_agent: org.kde.pim.akonadicore: Got a
stale notification for an item which was already removed. 949630 ""
Mar  8 15:47:33 x2 akonadi_archivemail_agent: org.kde.pim.akonadicore: Got a
stale notification for an item which was already removed. 949630 ""
Mar  8 15:47:34 x2 /usr/libexec/gdm-x-session: org.kde.pim.akonadicore: Got a
stale notification for an item which was already removed. 949630 ""
Mar  8 15:47:37 x2 akonadi_archivemail_agent: org.kde.pim.akonadicore: Got a
stale notification for an item which was already removed. 949633 ""
Mar  8 15:47:37 x2 akonadi_archivemail_agent: org.kde.pim.akonadicore: Got a
stale notification for an item which was already removed. 949633 ""
Mar  8 15:47:37 x2 akonadi_mailfilter_agent: org.kde.pim.akonadicore: Got a
stale notification for an item which was already removed. 949633 ""
Mar  8 15:47:37 x2 akonadi_mailfilter_agent: org.kde.pim.akonadicore: Got a
stale notification for an item which was already removed. 949633 ""
Mar  8 15:47:52 x2 akonadiserver: org.kde.pim.akonadiplugin_indexer: unknown
term  "attachment"
Mar  8 15:48:04 x2 akonadi_imap_resource: org.kde.pim.kimap: The stream parser
raised an exception: Unable to read more data
Mar  8 15:48:04 x2 akonadi_imap_resource: org.kde.pim.akonadicore: The item
sync is being rolled-back.
Mar  8 15:48:04 x2 akonadi_imap_resource: org.kde.pim.imapresource: Search job
failed:  "Connection to server lost."
Mar  8 15:48:34 x2 akonadi_imap_resource: org.kde.pim.imapresource: Session
login cancelled

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 377393] New: /usr/bin/akonadiserver crashes

[Steve]

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

Bug ID: 377393
   Summary: /usr/bin/akonadiserver crashes
   Product: Akonadi
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: sgr...@redhat.com
  Target Milestone: ---

Application: akonadiserver (5.4.2)

Qt Version: 5.6.2
Frameworks Version: 5.31.0
Operating System: Linux 4.9.13-100.fc24.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
I have been trying to use kontact-16.12.2. Its been causing trouble since I
upgraded to it. It gives an error message about losing contact with the back
end. If I shut down kontact and restart it, it immediately segfaults. Prior to
segfaulting it had the following in syslog:

Mar  8 15:13:56 x2 akonadi_mixedmaildir_resource: org.kde.pim.akonadicore:
Socket error occurred: "QLocalSocket: Remote closed"
Mar  8 15:13:56 x2 akonadi_newmailnotifier_agent: org.kde.pim.akonadicore:
Socket error occurred: "QLocalSocket: Remote closed"
Mar  8 15:13:56 x2 akonadi_newmailnotifier_agent: org.kde.pim.akonadicore:
Socket error occurred: "QLocalSocket: Remote closed"
Mar  8 15:13:56 x2 akonadi_mailfilter_agent: org.kde.pim.akonadicore: Socket
error occurred: "QLocalSocket: Remote closed"
Mar  8 15:13:56 x2 akonadi_akonotes_resource: org.kde.pim.akonadicore: Socket
error occurred: "QLocalSocket: Remote closed"
Mar  8 15:13:56 x2 akonadi_sendlater_agent: org.kde.pim.akonadicore: Socket
error occurred: "QLocalSocket: Remote closed"
Mar  8 15:13:56 x2 akonadi_kalarm_resource: org.kde.pim.akonadicore: Socket
error occurred: "QLocalSocket: Remote closed"
Mar  8 15:13:56 x2 akonadi_akonotes_resource: org.kde.pim.akonadicore:
"QLocalSocket: Remote closed"
"/tmp/akonadi-sgrubb.bv6VxA/akonadiserver-ntf.socket"
Mar  8 15:13:56 x2 akonadi_akonotes_resource: org.kde.pim.akonadicore: Socket
error occurred: "QLocalSocket: Remote closed"
Mar  8 15:13:56 x2 akonadi_vcard_resource: org.kde.pim.akonadicore: Socket
error occurred: "QLocalSocket: Remote closed"
Mar  8 15:13:56 x2 akonadi_ical_resource: org.kde.pim.akonadicore:
"QLocalSocket: Remote closed"
"/tmp/akonadi-sgrubb.bv6VxA/akonadiserver-ntf.socket"
Mar  8 15:13:56 x2 akonadi_akonotes_resource: org.kde.pim.akonadicore:
"QLocalSocket: Remote closed"
"/tmp/akonadi-sgrubb.bv6VxA/akonadiserver-ntf.socket"
Mar  8 15:13:56 x2 korgac: org.kde.pim.akonadicore: "QLocalSocket: Remote
closed" "/tmp/akonadi-sgrubb.bv6VxA/akonadiserver-ntf.socket"
Mar  8 15:13:56 x2 akonadi_akonotes_resource: org.kde.pim.akonadicore:
"QLocalSocket: Remote closed"
"/tmp/akonadi-sgrubb.bv6VxA/akonadiserver-ntf.socket"

-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd8e4c168c0 (LWP 2555))]

Thread 43 (Thread 0x7fd82e7fc700 (LWP 3204)):
#0  0x7fd8eccb7f79 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fd8ef0fa008 in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7fd8ef0f692d in QThreadPoolThread::run() () at /lib64/libQt5Core.so.5
#3  0x7fd8ef0f99aa in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#4  0x7fd8eccb25ca in start_thread () at /lib64/libpthread.so.0
#5  0x7fd8ee4ed0ed in clone () at /lib64/libc.so.6

Thread 42 (Thread 0x7fd86e7fc700 (LWP 3203)):
#0  0x7fd8eccb7f79 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fd8ef0fa008 in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7fd8ef0f692d in QThreadPoolThread::run() () at /lib64/libQt5Core.so.5
#3  0x7fd8ef0f99aa in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#4  0x7fd8eccb25ca in start_thread () at /lib64/libpthread.so.0
#5  0x7fd8ee4ed0ed in clone () at /lib64/libc.so.6

Thread 41 (Thread 0x7fd897fff700 (LWP 3202)):
#0  0x7fd8eccb7f79 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fd8ef0fa008 in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7fd8ef0f692d in QThreadPoolThread::run() () at /lib64/libQt5Core.so.5
#3  0x7fd8ef0f99aa in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#4  0x7fd8eccb25ca in start_thread () at /lib64/libpthread.so.0
#5  0x7fd8ee4ed0ed in clone () at /lib64/libc.so.6

Thread 40 (Thread 0x7fd8b0ff9700 (LWP 3201)):
#0  0x7fd8eccb7f79 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fd8ef0fa008 in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7fd8ef0f692d in QThreadPoolThread::run() () at /lib64/libQt5Core.so.5
#3  0x7fd8ef0f99aa in QThreadPrivate::start(void*) () at

[kontact] [Bug 377359] New: Clicking on File menu item crashes kontact

[Steve]

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

Bug ID: 377359
   Summary: Clicking on File menu item crashes kontact
   Product: kontact
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: sgr...@redhat.com
  Target Milestone: ---

Application: kontact (5.3.3 (QtWebEngine))

Qt Version: 5.6.2
Frameworks Version: 5.31.0
Operating System: Linux 4.9.13-100.fc24.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
I just started kontact. I simply clicked on the File menu item and it crashed.

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

Thread 24 (Thread 0x7ff33cb9f700 (LWP 2875)):
#0  0x7ff457616bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff45b793959 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() at /lib64/libQt5WebEngineCore.so.5
#2  0x7ff45b794020 in base::SequencedWorkerPool::Worker::Run() () at
/lib64/libQt5WebEngineCore.so.5
#3  0x7ff45b7941f0 in base::SimpleThread::ThreadMain() () at
/lib64/libQt5WebEngineCore.so.5
#4  0x7ff45b790c2d in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#5  0x7ff4576115ca in start_thread () at /lib64/libpthread.so.0
#6  0x7ff45eea10ed in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7ff33d3a0700 (LWP 2874)):
#0  0x7ff457616bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff45b793959 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() at /lib64/libQt5WebEngineCore.so.5
#2  0x7ff45b794020 in base::SequencedWorkerPool::Worker::Run() () at
/lib64/libQt5WebEngineCore.so.5
#3  0x7ff45b7941f0 in base::SimpleThread::ThreadMain() () at
/lib64/libQt5WebEngineCore.so.5
#4  0x7ff45b790c2d in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#5  0x7ff4576115ca in start_thread () at /lib64/libpthread.so.0
#6  0x7ff45eea10ed in clone () at /lib64/libc.so.6

Thread 22 (Thread 0x7ff3ec953700 (LWP 2870)):
#0  0x7ff457616bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff44a3661a4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQt5Script.so.5
#2  0x7ff44a3661e9 in  () at /lib64/libQt5Script.so.5
#3  0x7ff4576115ca in start_thread () at /lib64/libpthread.so.0
#4  0x7ff45eea10ed in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7ff3ed8ec700 (LWP 2863)):
#0  0x7ff457616bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff45b6a37c0 in mojo::system::Waiter::Wait(unsigned long, unsigned
int*) () at /lib64/libQt5WebEngineCore.so.5
#2  0x7ff45b68f39c in mojo::system::Core::WaitManyInternal(unsigned int
const*, unsigned int const*, unsigned int, unsigned long, unsigned int*,
mojo::system::HandleSignalsState*) () at /lib64/libQt5WebEngineCore.so.5
#3  0x7ff45b68f89c in
mojo::system::Core::WaitMany(mojo::system::UserPointer,
mojo::system::UserPointer, unsigned int, unsigned long,
mojo::system::UserPointer,
mojo::system::UserPointer) () at
/lib64/libQt5WebEngineCore.so.5
#4  0x7ff45b68bcf5 in MojoWaitMany () at /lib64/libQt5WebEngineCore.so.5
#5  0x7ff45cd02c47 in
mojo::common::MessagePumpMojo::DoInternalWork(mojo::common::MessagePumpMojo::RunState
const&, bool) () at /lib64/libQt5WebEngineCore.so.5
#6  0x7ff45cd02e7e in
mojo::common::MessagePumpMojo::DoRunLoop(mojo::common::MessagePumpMojo::RunState*,
base::MessagePump::Delegate*) () at /lib64/libQt5WebEngineCore.so.5
#7  0x7ff45cd02fb9 in
mojo::common::MessagePumpMojo::Run(base::MessagePump::Delegate*) () at
/lib64/libQt5WebEngineCore.so.5
#8  0x7ff45b77bca4 in base::RunLoop::Run() () at
/lib64/libQt5WebEngineCore.so.5
#9  0x7ff45b766ae5 in base::MessageLoop::Run() () at
/lib64/libQt5WebEngineCore.so.5
#10 0x7ff45b7946e6 in base::Thread::ThreadMain() () at
/lib64/libQt5WebEngineCore.so.5
#11 0x7ff45b790c2d in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#12 0x7ff4576115ca in start_thread () at /lib64/libpthread.so.0
#13 0x7ff45eea10ed in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7ff3ee0ed700 (LWP 2862)):
#0  0x7ff457616bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff45b793959 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() at /lib64/libQt5WebEngineCore.so.5
#2  0x7ff45b794020 in base::SequencedWorkerPool::Worker::Run() () at

[kdepim] [Bug 309963] Deleting any mail causes heavy system load

[Steve]

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

--- Comment #5 from Steve <sgr...@redhat.com> ---
This problem still exists. Its takes about 45 minutes from start up until
kontact is usable. kontact-16.08.3-2.fc24.x86_64, kdepim-16.08.3-2.fc24.x86_64.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 363390] New: Akonadi randomly crashes

[Steve via KDE Bugzilla]

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

Bug ID: 363390
   Summary: Akonadi randomly crashes
   Product: Akonadi
   Version: unspecified
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: IMAP resource
  Assignee: chrig...@fastmail.fm
  Reporter: steve...@gmail.com
CC: kdepim-bugs@kde.org, vkra...@kde.org

Application: akonadi_imap_resource (4.14)
KDE Platform Version: 4.14.5
Qt Version: 4.8.6
Operating System: Linux 4.1.15-server-2.mga5 i686
Distribution: "Mageia 5"

-- Information about the crash:
- What I was doing when the application crashed:
nothing particular, now I am using libreoffice and crashes, it crashes with or
without kmail open, or when no application other than KDE are open.

The crash can be reproduced every time.

-- Backtrace:
Application: Google Mail (steverav) di tipo Server di posta IMAP
(akonadi_imap_resource), signal: Segmentation fault
Using host libthread_db library "/lib/i686/libthread_db.so.1".
[Current thread is 1 (Thread 0xb4387740 (LWP 6992))]

Thread 3 (Thread 0xb15c6b40 (LWP 7023)):
#0  0x in __kernel_vsyscall ()
#1  0x in poll () at /lib/i686/libc.so.6
#2  0x in g_poll () at /lib/libglib-2.0.so.0
#3  0x in g_main_context_iterate.isra () at /lib/libglib-2.0.so.0
#4  0x in g_main_context_iteration () at /lib/libglib-2.0.so.0
#5  0x in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/libQtCore.so.4
#6  0x in
QEventLoop::processEvents(QFlags) () at
/lib/libQtCore.so.4
#7  0x in QEventLoop::exec(QFlags) () at
/lib/libQtCore.so.4
#8  0x in QThread::exec() () at /lib/libQtCore.so.4
#9  0x in QThread::run() () at /lib/libQtCore.so.4
#10 0x in QThreadPrivate::start(void*) () at /lib/libQtCore.so.4
#11 0x in start_thread () at /lib/i686/libpthread.so.0
#12 0x in clone () at /lib/i686/libc.so.6

Thread 2 (Thread 0xafdffb40 (LWP 7025)):
#0  0x in __kernel_vsyscall ()
#1  0x in poll () at /lib/i686/libc.so.6
#2  0x in g_poll () at /lib/libglib-2.0.so.0
#3  0x in g_main_context_iterate.isra () at /lib/libglib-2.0.so.0
#4  0x in g_main_context_iteration () at /lib/libglib-2.0.so.0
#5  0x in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/libQtCore.so.4
#6  0x in
QEventLoop::processEvents(QFlags) () at
/lib/libQtCore.so.4
#7  0x in QEventLoop::exec(QFlags) () at
/lib/libQtCore.so.4
#8  0x in QThread::exec() () at /lib/libQtCore.so.4
#9  0x in QThread::run() () at /lib/libQtCore.so.4
#10 0x in QThreadPrivate::start(void*) () at /lib/libQtCore.so.4
#11 0x in start_thread () at /lib/i686/libpthread.so.0
#12 0x in clone () at /lib/i686/libc.so.6

Thread 1 (Thread 0xb4387740 (LWP 6992)):
[KCrash Handler]
#6  0x in KIMAP::SearchJob::handleResponse(KIMAP::Message const&) () at
/lib/libkimap.so.4
#7  0x in KIMAP::SessionPrivate::responseReceived(KIMAP::Message
const&) () at /lib/libkimap.so.4
#8  0x in KIMAP::SessionPrivate::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) [clone .part.41] () at /lib/libkimap.so.4
#9  0x in QMetaCallEvent::placeMetaCall(QObject*) () at
/lib/libQtCore.so.4
#10 0x in QObject::event(QEvent*) () at /lib/libQtCore.so.4
#11 0x in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at
/lib/libQtGui.so.4
#12 0x in QApplication::notify(QObject*, QEvent*) () at
/lib/libQtGui.so.4
#13 0x in KApplication::notify(QObject*, QEvent*) () at
/lib/libkdeui.so.5
#14 0x in QCoreApplication::notifyInternal(QObject*, QEvent*) () at
/lib/libQtCore.so.4
#15 0x in QCoreApplicationPrivate::sendPostedEvents(QObject*, int,
QThreadData*) () at /lib/libQtCore.so.4
#16 0x in QCoreApplication::sendPostedEvents(QObject*, int) () at
/lib/libQtCore.so.4
#17 0x in postEventSourceDispatch(_GSource*, int (*)(void*), void*) ()
at /lib/libQtCore.so.4
#18 0x in g_main_context_dispatch () at /lib/libglib-2.0.so.0
#19 0x in g_main_context_iterate.isra () at /lib/libglib-2.0.so.0
#20 0x in g_main_context_iteration () at /lib/libglib-2.0.so.0
#21 0x in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/libQtCore.so.4
#22 0x in
QGuiEventDispatcherGlib::processEvents(QFlags)
() at /lib/libQtGui.so.4
#23 0x in
QEventLoop::processEvents(QFlags) () at
/lib/libQtCore.so.4
#24 0x in QEventLoop::exec(QFlags) () at
/lib/libQtCore.so.4
#25 0x in QCoreApplication::exec() () at /lib/libQtCore.so.4
#26 0x in QApplication::exec() () at /lib/libQtGui.so.4
#27 0x in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () at
/lib/libakonadi-kde.so.4
#28 0x0805b7c3 in int Akonadi::

[Akonadi] [Bug 360792] akonadi_davgroupware_resource crashes constandly

[Steve Youngs via KDE Bugzilla]

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

Steve Youngs <st...@steveyoungs.com> changed:

   What|Removed |Added

 CC||st...@steveyoungs.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 331826] Emails based on template go to local sent folder instead of that configured

[Steve via KDE Bugzilla]

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

Steve <das.sha...@gmail.com> changed:

   What|Removed |Added

 CC||das.sha...@gmail.com

--- Comment #12 from Steve <das.sha...@gmail.com> ---
It's still happening in Kmail 5.0.2, it just started not saving the email for
me, which is not cool as I do need a record of email I've sent.

It used to save in my local save-mail folder instead of on IMAP, but something
changed last week and it just stopped saving template messages altogether.

-- 
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 358538] New: kmail crash when clicking Tools|Find Messages

[Steve via KDE Bugzilla]

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

Bug ID: 358538
   Summary: kmail crash when clicking Tools|Find Messages
   Product: kontact
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: sgr...@redhat.com

Application: kontact (4.14.10)
KDE Platform Version: 4.14.16
Qt Version: 4.8.7
Operating System: Linux 4.2.3-203.fc22.x86_64 x86_64
Distribution: "Fedora release 23 (Twenty Three)"

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

I was trying to seach for a compound word on the search bar just above the mail
list. But was not getting the results I wanted. I decided to look in the tools
menu to see if there was an advanced search. I saw 'Find Messages' and clicked
on it. The dialog box never came up, the program crashed.

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

Thread 6 (Thread 0x7f6e6ebc0700 (LWP 9345)):
#0  0x7f6eda4c1fdd in poll () at /lib64/libc.so.6
#1  0x7f6ed74ab16c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f6ed74ab27c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f6ed74ab2b9 in glib_worker_main () at /lib64/libglib-2.0.so.0
#4  0x7f6ed74d1835 in g_thread_proxy () at /lib64/libglib-2.0.so.0
#5  0x7f6edb7bc60a in start_thread () at /lib64/libpthread.so.0
#6  0x7f6eda4cda4d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f6e6e3bf700 (LWP 9346)):
#0  0x7f6eda4c1fdd in poll () at /lib64/libc.so.6
#1  0x7f6ed74ab16c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f6ed74ab4f2 in g_main_loop_run () at /lib64/libglib-2.0.so.0
#3  0x7f6ed895e336 in gdbus_shared_thread_func () at /lib64/libgio-2.0.so.0
#4  0x7f6ed74d1835 in g_thread_proxy () at /lib64/libglib-2.0.so.0
#5  0x7f6edb7bc60a in start_thread () at /lib64/libpthread.so.0
#6  0x7f6eda4cda4d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f6e6d991700 (LWP 9347)):
#0  0x7f6edb7c1b10 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f6ee01fc071 in JSC::BlockAllocator::blockFreeingThreadMain() () at
/lib64/libQtWebKit.so.4
#2  0x7f6ee05004c6 in WTF::wtfThreadEntryPoint(void*) () at
/lib64/libQtWebKit.so.4
#3  0x7f6edb7bc60a in start_thread () at /lib64/libpthread.so.0
#4  0x7f6eda4cda4d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f6e518e5700 (LWP 9401)):
#0  0x7f6eda4c1fdd in poll () at /lib64/libc.so.6
#1  0x7f6ed74ab16c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f6ed74ab27c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f6edb1f2eae in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#4  0x7f6edb1c1151 in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#5  0x7f6edb1c14c5 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#6  0x7f6edb0b0a89 in QThread::exec() () at /lib64/libQtCore.so.4
#7  0x7f6edb0b337c in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#8  0x7f6edb7bc60a in start_thread () at /lib64/libpthread.so.0
#9  0x7f6eda4cda4d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f6e442ff700 (LWP 22042)):
#0  0x7f6eda4c1fdd in poll () at /lib64/libc.so.6
#1  0x7f6ed74ab16c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f6ed74ab27c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f6edb1f2eae in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#4  0x7f6edb1c1151 in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#5  0x7f6edb1c14c5 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#6  0x7f6edb0b0a89 in QThread::exec() () at /lib64/libQtCore.so.4
#7  0x7f6edb1a1223 in QInotifyFileSystemWatcherEngine::run() () at
/lib64/libQtCore.so.4
#8  0x7f6edb0b337c in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#9  0x7f6edb7bc60a in start_thread () at /lib64/libpthread.so.0
#10 0x7f6eda4cda4d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f6ee1053940 (LWP 9341)):
[KCrash Handler]
#6  0x7f6e5c76c98e in MailCommon::SearchPattern::purify(bool) () at
/lib64/libmailcommon.so.4
#7  0x7f6e539ce076 in
KMail::SearchWindow::addRulesToSearchPattern(MailCommon::SearchPattern const&)
() at /lib64/libkmailprivate.so.4
#8  0x7f6e5392ba73 in KMMainWidget::slotRequestFullSearchFromQuickSearch()
() at /lib64/libkmailprivate.so.4
#9  0x7f6e53a3b27c in KMMainWidget::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () at /lib64/libkmailprivate.so.4
#10 

[kmail2] [Bug 354443] New: KMail crash on loading

[Steve Adams via KDE Bugzilla]

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

Bug ID: 354443
   Summary: KMail crash on loading
   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: st...@saktaala.info

Application: kmail (4.14.10)
KDE Platform Version: 4.14.10
Qt Version: 4.8.7
Operating System: Linux 4.2.1-1-desktop x86_64
Distribution: "openSUSE Tumbleweed (20151002) (x86_64)"

-- Information about the crash:
KMail crash on start of day loading into kde

The crash can be reproduced every time.

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

Thread 4 (Thread 0x7f0a83fff700 (LWP 1897)):
#0  0x7f0aa66a107f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f0aa2a79de6 in WTF::TCMalloc_PageHeap::scavengerThread() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7f0aa2a79e19 in  () at /usr/lib64/libQtWebKit.so.4
#3  0x7f0aa669b4a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f0aadc1480d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f0a82e6e700 (LWP 1898)):
#0  0x7f0aa66a107f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f0aa27e35e9 in JSC::BlockAllocator::blockFreeingThreadMain() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7f0aa2aa18f6 in WTF::wtfThreadEntryPoint(void*) () at
/usr/lib64/libQtWebKit.so.4
#3  0x7f0aa669b4a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f0aadc1480d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f0a81fb1700 (LWP 1899)):
#0  0x7f0aadc0be7d in poll () at /lib64/libc.so.6
#1  0x7f0aa587be94 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f0aa587bf9c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f0aaf2e926e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7f0aaf2b93e1 in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7f0aaf2b96f5 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7f0aaf1b2a59 in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7f0aaf1b523c in  () at /usr/lib64/libQtCore.so.4
#8  0x7f0aa669b4a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f0aadc1480d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f0ab09bf940 (LWP 1812)):
[KCrash Handler]
#6  0x7f0aadb5f7a8 in raise () at /lib64/libc.so.6
#7  0x7f0aadb60bfa in abort () at /lib64/libc.so.6
#8  0x7f0a9cc218e4 in  () at /lib64/libdbus-1.so.3
#9  0x7f0a9cc184a1 in  () at /lib64/libdbus-1.so.3
#10 0x7f0a9cc09bd3 in dbus_message_new_method_call () at
/lib64/libdbus-1.so.3
#11 0x7f0aa8211238 in  () at /usr/lib64/libQtDBus.so.4
#12 0x7f0aa820c982 in  () at /usr/lib64/libQtDBus.so.4
#13 0x7f0aa820eb3b in  () at /usr/lib64/libQtDBus.so.4
#14 0x7f0aa821b6c3 in  () at /usr/lib64/libQtDBus.so.4
#15 0x7f0aa821b805 in QDBusInterface::QDBusInterface(QString const&,
QString const&, QString const&, QDBusConnection const&, QObject*) () at
/usr/lib64/libQtDBus.so.4
#16 0x7f0aaafff763 in
PimCommon::ImapResourceCapabilitiesManager::searchCapabilities(QString const&)
() at /usr/lib64/libpimcommon.so.4
#17 0x7f0aab0c in
PimCommon::ImapResourceCapabilitiesManager::slotInstanceAdded(Akonadi::AgentInstance
const&) () at /usr/lib64/libpimcommon.so.4
#18 0x7f0aaf2cdf60 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#19 0x7f0aa9eb7705 in
Akonadi::AgentManager::instanceAdded(Akonadi::AgentInstance const&) () at
/usr/lib64/libakonadi-kde.so.4
#20 0x7f0aa9ebbb16 in  () at /usr/lib64/libakonadi-kde.so.4
#21 0x7f0aa9ebbf84 in  () at /usr/lib64/libakonadi-kde.so.4
#22 0x7f0aaf2cdf60 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#23 0x7f0aa824532f in QDBusServiceWatcher::serviceOwnerChanged(QString
const&, QString const&, QString const&) () at /usr/lib64/libQtDBus.so.4
#24 0x7f0aa824535f in  () at /usr/lib64/libQtDBus.so.4
#25 0x7f0aa82460e7 in QDBusServiceWatcher::qt_metacall(QMetaObject::Call,
int, void**) () at /usr/lib64/libQtDBus.so.4
#26 0x7f0aa82071d5 in  () at /usr/lib64/libQtDBus.so.4
#27 0x7f0aaf2d3aa1 in QObject::event(QEvent*) () at
/usr/lib64/libQtCore.so.4
#28 0x7f0aae640f1c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQtGui.so.4
#29 0x7f0aae6479ec in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQtGui.so.4
#30 0x7f0aafd3e63a in KApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libkdeui.so.5
#31 0x7f0aaf2baa1d in QCoreApplication::notifyInternal(QObject*, 

[kmail2] [Bug 353887] New: kmail crash on loading

[Steve Adams]

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

Bug ID: 353887
   Summary: kmail crash on loading
   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: st...@saktaala.info

Application: kmail (4.14.10)
KDE Platform Version: 4.14.10
Qt Version: 4.8.7
Operating System: Linux 4.2.1-1-desktop x86_64
Distribution: "openSUSE Tumbleweed (20151002) (x86_64)"

-- Information about the crash:
Starting kmail as part of kde autostart. Aside from kde deskto pstart no other
user based action happening

The crash can be reproduced every time.

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

Thread 4 (Thread 0x7f6c41988700 (LWP 1951)):
#0  0x7f6c5ff4e07f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f6c5c326de6 in WTF::TCMalloc_PageHeap::scavengerThread() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7f6c5c326e19 in  () at /usr/lib64/libQtWebKit.so.4
#3  0x7f6c5ff484a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f6c674c180d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f6c3bfff700 (LWP 1981)):
#0  0x7f6c5ff4e07f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f6c5c0905e9 in JSC::BlockAllocator::blockFreeingThreadMain() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7f6c5c34e8f6 in WTF::wtfThreadEntryPoint(void*) () at
/usr/lib64/libQtWebKit.so.4
#3  0x7f6c5ff484a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f6c674c180d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f6c3b7fe700 (LWP 2013)):
#0  0x7f6c5f16cb54 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f6c5f1284b0 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f6c5f128dc3 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f6c5f128f9c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f6c68b9626e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#5  0x7f6c68b663e1 in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7f6c68b666f5 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#7  0x7f6c68a5fa59 in QThread::exec() () at /usr/lib64/libQtCore.so.4
#8  0x7f6c68a6223c in  () at /usr/lib64/libQtCore.so.4
#9  0x7f6c5ff484a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f6c674c180d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f6c6a26c940 (LWP 1847)):
[KCrash Handler]
#6  0x7f6c6740c7a8 in raise () at /lib64/libc.so.6
#7  0x7f6c6740dbfa in abort () at /lib64/libc.so.6
#8  0x7f6c564ce8e4 in  () at /lib64/libdbus-1.so.3
#9  0x7f6c564c54a1 in  () at /lib64/libdbus-1.so.3
#10 0x7f6c564b6bd3 in dbus_message_new_method_call () at
/lib64/libdbus-1.so.3
#11 0x7f6c61abe238 in  () at /usr/lib64/libQtDBus.so.4
#12 0x7f6c61ab9982 in  () at /usr/lib64/libQtDBus.so.4
#13 0x7f6c61abbb3b in  () at /usr/lib64/libQtDBus.so.4
#14 0x7f6c61ac86c3 in  () at /usr/lib64/libQtDBus.so.4
#15 0x7f6c61ac8805 in QDBusInterface::QDBusInterface(QString const&,
QString const&, QString const&, QDBusConnection const&, QObject*) () at
/usr/lib64/libQtDBus.so.4
#16 0x7f6c648ac763 in
PimCommon::ImapResourceCapabilitiesManager::searchCapabilities(QString const&)
() at /usr/lib64/libpimcommon.so.4
#17 0x7f6c648ad00c in
PimCommon::ImapResourceCapabilitiesManager::slotInstanceAdded(Akonadi::AgentInstance
const&) () at /usr/lib64/libpimcommon.so.4
#18 0x7f6c68b7af60 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#19 0x7f6c63764705 in
Akonadi::AgentManager::instanceAdded(Akonadi::AgentInstance const&) () at
/usr/lib64/libakonadi-kde.so.4
#20 0x7f6c63768b16 in  () at /usr/lib64/libakonadi-kde.so.4
#21 0x7f6c63768f84 in  () at /usr/lib64/libakonadi-kde.so.4
#22 0x7f6c68b7af60 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#23 0x7f6c61af232f in QDBusServiceWatcher::serviceOwnerChanged(QString
const&, QString const&, QString const&) () at /usr/lib64/libQtDBus.so.4
#24 0x7f6c61af235f in  () at /usr/lib64/libQtDBus.so.4
#25 0x7f6c61af30e7 in QDBusServiceWatcher::qt_metacall(QMetaObject::Call,
int, void**) () at /usr/lib64/libQtDBus.so.4
#26 0x7f6c61ab41d5 in  () at /usr/lib64/libQtDBus.so.4
#27 0x7f6c68b80aa1 in QObject::event(QEvent*) () at
/usr/lib64/libQtCore.so.4
#28 0x7f6c67eedf1c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQtGui.so.4
#29 0x7f6c67ef49ec in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQtGui.so.4
#30 

[kontact] [Bug 332056] New: Crash while closing kontact

[Steve]

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

Bug ID: 332056
   Summary: Crash while closing kontact
Classification: Unclassified
   Product: kontact
   Version: 4.12.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: sgr...@redhat.com

Application: kontact (4.12.3)
KDE Platform Version: 4.12.3
Qt Version: 4.8.5
Operating System: Linux 3.13.6-200.fc20.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
I had started kontact. After a while, I saw a cinnomon notification that I had
60 new emails. For some reason, it forgot the last email I was looking at
yesterday and it resorted all of my email and left me at one from 2004. I
scrolled to the bottom and only saw new 15-20 emails. I also saw that none of
the filters had moved mail to folders (like trash for example). So, I had a
feeling kontact had deadlocked displaying something and decided to close it. As
soon as I did, it crashed.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library /lib64/libthread_db.so.1.
81T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f0e474ba8c0 (LWP 3075))]

Thread 4 (Thread 0x7f0dd1d8f700 (LWP 3078)):
#0  0x7f0e4028b9dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f0e3d0a95b4 in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7f0dcc0010c0, timeout=-1, context=0x168d300) at gmain.c:4007
#2  g_main_context_iterate (context=0x168d300, block=block@entry=1,
dispatch=dispatch@entry=1, self=optimized out) at gmain.c:3708
#3  0x7f0e3d0a9a3a in g_main_loop_run (loop=0x1642c70) at gmain.c:3907
#4  0x7f0e3e850376 in gdbus_shared_thread_func (user_data=0x168f880) at
gdbusprivate.c:278
#5  0x7f0e3d0cea45 in g_thread_proxy (data=0x1556190) at gthread.c:798
#6  0x7f0e4100af33 in start_thread (arg=0x7f0dd1d8f700) at
pthread_create.c:309
#7  0x7f0e40295ded in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7f0dd1385700 (LWP 3079)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0e45f0746d in JSC::BlockAllocator::blockFreeingThreadMain
(this=0x1771e98) at
/usr/src/debug/webkit-qtwebkit-23/Source/JavaScriptCore/heap/BlockAllocator.cpp:128
#2  0x7f0e461f9d36 in WTF::wtfThreadEntryPoint (param=0x176b9c0) at
/usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/ThreadingPthreads.cpp:196
#3  0x7f0e4100af33 in start_thread (arg=0x7f0dd1385700) at
pthread_create.c:309
#4  0x7f0e40295ded in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f0db96a3700 (LWP 3111)):
#0  0x7f0e3d0ea2ea in g_mutex_get_impl (mutex=0x7f0dac0009a0) at
gthread-posix.c:124
#1  0x7f0e3d0ea5c9 in g_mutex_unlock (mutex=mutex@entry=0x7f0dac0009a0) at
gthread-posix.c:232
#2  0x7f0e3d0a8c78 in g_main_context_prepare
(context=context@entry=0x7f0dac0009a0, priority=priority@entry=0x7f0db96a2bd0)
at gmain.c:3405
#3  0x7f0e3d0a94bb in g_main_context_iterate
(context=context@entry=0x7f0dac0009a0, block=block@entry=1,
dispatch=dispatch@entry=1, self=optimized out) at gmain.c:3693
#4  0x7f0e3d0a96dc in g_main_context_iteration (context=0x7f0dac0009a0,
may_block=1) at gmain.c:3774
#5  0x7f0e413d2ec6 in QEventDispatcherGlib::processEvents
(this=0x7f0dac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427
#6  0x7f0e413a2edf in QEventLoop::processEvents
(this=this@entry=0x7f0db96a2d10, flags=...) at kernel/qeventloop.cpp:149
#7  0x7f0e413a322d in QEventLoop::exec (this=this@entry=0x7f0db96a2d10,
flags=...) at kernel/qeventloop.cpp:204
#8  0x7f0e41299baf in QThread::exec (this=optimized out) at
thread/qthread.cpp:536
#9  0x7f0e4129c3af in QThreadPrivate::start (arg=0x13ae960) at
thread/qthread_unix.cpp:338
#10 0x7f0e4100af33 in start_thread (arg=0x7f0db96a3700) at
pthread_create.c:309
#11 0x7f0e40295ded in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f0e474ba8c0 (LWP 3075)):
[KCrash Handler]
#6  Akonadi::StandardMailActionManager::action (this=0x0,
type=type@entry=Akonadi::StandardMailActionManager::MarkAllMailAsRead) at
/usr/src/debug/kdepimlibs-4.12.3/akonadi/kmime/standardmailactionmanager.cpp:905
#7  0x7f0dbe8d3688 in KMMainWidget::updateMoveAction
(this=this@entry=0x1cc8a10, hasUnreadMails=hasUnreadMails@entry=false,
hasMails=hasMails@entry=false) at
/usr/src/debug/kdepim-4.12.3/kmail/kmmainwidget.cpp:1157
#8  0x7f0dbe8e16c0 in KMMainWidget::updateMessageActionsDelayed
(this=0x1cc8a10) at /usr/src/debug/kdepim-4.12.3/kmail/kmmainwidget.cpp:3986
#9  0x7f0dbe8f9c9a in KMMainWidget::qt_static_metacall 

[kontact] [Bug 329734] New: Crash on cancel entering passphrase

[Steve]

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

Bug ID: 329734
   Summary: Crash on cancel entering passphrase
Classification: Unclassified
   Product: kontact
   Version: 4.11.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: sgr...@redhat.com

Application: kontact (4.11.4)
KDE Platform Version: 4.11.4
Qt Version: 4.8.5
Operating System: Linux 3.12.6-300.fc20.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
I received an encrypted email to myself and 2 other people. It selected someone
else's email address and asked to enter their passphrase. I clicked cancel like
I normally do so that it advances to my email address. This time it says I
entered an invalid passphrase. I can retry or cancel. Since I don't know their
passphrase I clicked cancel and it crashed.

It seems like kmail could scan the email to see who can unlock it and only
prompt for my passphrase. Why does it ask for everyone else's passphrase?

The crash can be reproduced every time.

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

Thread 4 (Thread 0x7fe281017700 (LWP 17213)):
#0  0x003c0e00e87d in read () from /lib64/libpthread.so.0
#1  0x003c0fc897b0 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0
#2  0x003c0fc4909c in g_main_context_check () from /lib64/libglib-2.0.so.0
#3  0x003c0fc49533 in g_main_context_iterate.isra.24 () from
/lib64/libglib-2.0.so.0
#4  0x003c0fc49a3a in g_main_loop_run () from /lib64/libglib-2.0.so.0
#5  0x0035d6ed0376 in gdbus_shared_thread_func () from
/lib64/libgio-2.0.so.0
#6  0x003c0fc6ea45 in g_thread_proxy () from /lib64/libglib-2.0.so.0
#7  0x003c0e007f33 in start_thread () from /lib64/libpthread.so.0
#8  0x003c0d8f4ead in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fe27bfff700 (LWP 17214)):
#0  0x003c0e00bd20 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x0030ef2bc46d in JSC::BlockAllocator::blockFreeingThreadMain() () from
/lib64/libQtWebKit.so.4
#2  0x0030ef5aed36 in WTF::wtfThreadEntryPoint(void*) () from
/lib64/libQtWebKit.so.4
#3  0x003c0e007f33 in start_thread () from /lib64/libpthread.so.0
#4  0x003c0d8f4ead in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fe2728a9700 (LWP 17217)):
#0  0x003c0d8eaa8d in poll () from /lib64/libc.so.6
#1  0x003c0fc495b4 in g_main_context_iterate.isra.24 () from
/lib64/libglib-2.0.so.0
#2  0x003c0fc496dc in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x0035d97b31a6 in
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) ()
from /lib64/libQtCore.so.4
#4  0x0035d978312f in
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from
/lib64/libQtCore.so.4
#5  0x0035d978347d in
QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from
/lib64/libQtCore.so.4
#6  0x0035d9679bdf in QThread::exec() () from /lib64/libQtCore.so.4
#7  0x0035d967c3df in QThreadPrivate::start(void*) () from
/lib64/libQtCore.so.4
#8  0x003c0e007f33 in start_thread () from /lib64/libpthread.so.0
#9  0x003c0d8f4ead in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fe2d78ca8c0 (LWP 17212)):
[KCrash Handler]
#5  0x0030ebc48d51 in KMime::Content::contents() const () from
/lib64/libkmime.so.4
#6  0x0030f7a3b4ee in MessageCore::NodeHelper::nextSibling(KMime::Content
const*) () from /lib64/libmessagecore.so.4
#7  0x0030f76a5de7 in
MessageViewer::ObjectTreeParser::parseObjectTreeInternal(KMime::Content*) ()
from /lib64/libmessageviewer.so.4
#8  0x0030f76d5b4b in
MessageViewer::ViewerPrivate::parseContent(KMime::Content*) () from
/lib64/libmessageviewer.so.4
#9  0x0030f76d62d4 in MessageViewer::ViewerPrivate::displayMessage() ()
from /lib64/libmessageviewer.so.4
#10 0x0030f76d6f3e in MessageViewer::ViewerPrivate::updateReaderWin() ()
from /lib64/libmessageviewer.so.4
#11 0x0030f76dec1d in
MessageViewer::ViewerPrivate::qt_static_metacall(QObject*, QMetaObject::Call,
int, void**) () from /lib64/libmessageviewer.so.4
#12 0x0035d9798fa8 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /lib64/libQtCore.so.4
#13 0x0035d979d361 in QObject::event(QEvent*) () from /lib64/libQtCore.so.4
#14 0x0035dd1c9dfc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQtGui.so.4
#15 0x0035dd1d0795 in QApplication::notify(QObject*, QEvent*) () from
/lib64/libQtGui.so.4
#16 0x0030e784a9ca in KApplication::notify(QObject*, QEvent*) () from
/lib64/libkdeui.so.5
#17 0x0035d97845ed in QCoreApplication::notifyInternal(QObject*, 

[kontact] [Bug 327499] New: kmail crashes when canceling entering gpg passphrase

[Steve]

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

Bug ID: 327499
   Summary: kmail crashes when canceling entering gpg passphrase
Classification: Unclassified
   Product: kontact
   Version: 4.11.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: sgr...@redhat.com

Application: kontact (4.11.3)
KDE Platform Version: 4.11.3
Qt Version: 4.8.5
Operating System: Linux 3.11.7-200.fc19.x86_64 x86_64
Distribution (Platform): Fedora RPMs

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

kmail displayed the user name of another recipient cc'ed on the encrypted
email. I clicked on cancel. It said that I had enetered an invalid passphrase.
I knew I hadn't because it was not asking for my passphrase. I clicked cancel
again thinking it would move to asking for my passphrase, but instead it
segfaulted. Btw, kmail _knows_ my email address, why does it show me other
users and ask me to provide _their_ passphrase? I hate clicking through 3-4
people just to enter mine.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library /lib64/libthread_db.so.1.
81T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7fe87f1008c0 (LWP 5810))]

Thread 5 (Thread 0x7fe86ee2c700 (LWP 5811)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00ecde2d in WTF::TCMalloc_PageHeap::scavengerThread
(this=optimized out) at
/usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/FastMalloc.cpp:2571
#2  0x00ecde69 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=optimized out) at
/usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/FastMalloc.cpp:1767
#3  0x003ad5c07c53 in start_thread (arg=0x7fe86ee2c700) at
pthread_create.c:308
#4  0x003ad50f5dbd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 4 (Thread 0x7fe8276c8700 (LWP 5812)):
#0  0x003ad5c0aa6c in __pthread_mutex_unlock_usercnt (decr=1,
mutex=0x242bda0) at pthread_mutex_unlock.c:52
#1  __GI___pthread_mutex_unlock (mutex=0x242bda0) at pthread_mutex_unlock.c:297
#2  0x003ad7487281 in g_mutex_unlock (mutex=mutex@entry=0x242bce0) at
gthread-posix.c:229
#3  0x003ad7448006 in g_main_context_iterate (context=0x242bce0,
block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at
gmain.c:3679
#4  0x003ad744855a in g_main_loop_run (loop=0x242bc70) at gmain.c:3895
#5  0x003ae00c6d66 in gdbus_shared_thread_func (user_data=0x242bcb0) at
gdbusprivate.c:278
#6  0x003ad746c185 in g_thread_proxy (data=0x248b0f0) at gthread.c:798
#7  0x003ad5c07c53 in start_thread (arg=0x7fe8276c8700) at
pthread_create.c:308
#8  0x003ad50f5dbd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 3 (Thread 0x7fe826cbe700 (LWP 5813)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00c0e5bd in JSC::BlockAllocator::blockFreeingThreadMain
(this=0x7fe86e596398) at
/usr/src/debug/webkit-qtwebkit-23/Source/JavaScriptCore/heap/BlockAllocator.cpp:128
#2  0x00efd686 in WTF::wtfThreadEntryPoint (param=0x2563040) at
/usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/ThreadingPthreads.cpp:196
#3  0x003ad5c07c53 in start_thread (arg=0x7fe826cbe700) at
pthread_create.c:308
#4  0x003ad50f5dbd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 2 (Thread 0x7fe8157f8700 (LWP 5845)):
#0  0x003ad7447f9b in g_main_context_iterate
(context=context@entry=0x7fe819a0, block=block@entry=1,
dispatch=dispatch@entry=1, self=optimized out) at gmain.c:3638
#1  0x003ad74481fc in g_main_context_iteration (context=0x7fe819a0,
may_block=1) at gmain.c:3762
#2  0x003ae15a7166 in QEventDispatcherGlib::processEvents
(this=0x7fe818c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427
#3  0x003ae1578ecf in QEventLoop::processEvents
(this=this@entry=0x7fe8157f7d20, flags=...) at kernel/qeventloop.cpp:149
#4  0x003ae15791c5 in QEventLoop::exec (this=this@entry=0x7fe8157f7d20,
flags=...) at kernel/qeventloop.cpp:204
#5  0x003ae147866f in QThread::exec (this=optimized out) at
thread/qthread.cpp:536
#6  0x003ae147ad0f in QThreadPrivate::start (arg=0x220bed0) at
thread/qthread_unix.cpp:338
#7  0x003ad5c07c53 in start_thread (arg=0x7fe8157f8700) at
pthread_create.c:308
#8  0x003ad50f5dbd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 1 (Thread 0x7fe87f1008c0 (LWP 5810)):
[KCrash Handler]
#6  0x00326ea43184 in KMime::Content::parent (this=this@entry=0x1955f2e0)
at /usr/src/debug/kdepimlibs-4.11.3/kmime/kmime_content.cpp:953
#7  0x003276a3aa07 in 

[kmail2] [Bug 303531] Kmail crash after akonadi pop server delete

[Steve Wray]

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

Steve Wray dialtwenty...@gmail.com changed:

   What|Removed |Added

 CC||dialtwenty...@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 303531] Kmail crash after akonadi pop server delete

[Steve Wray]

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

--- Comment #3 from Steve Wray dialtwenty...@gmail.com ---
Created attachment 82978
  -- https://bugs.kde.org/attachment.cgi?id=82978action=edit
New crash information added by DrKonqi

kmail (4.11.2) on KDE Platform 4.11.2 using Qt 4.8.4

Added a new user and changed the directory from inbox folder to example.com
folder and the KMail program crased. Dialog box comes up saying changing the
name of the folder I just made back to the original folder. I could not rename
to the folder I wanted it to be. Has to be inbox.

-- Backtrace (Reduced):
#8  0xb5e4baff in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#9  0xb5e4f083 in __GI_abort () at abort.c:90
[...]
#13 0xb75f3ffc in operator- (this=optimized out) at
../../kdeui/widgets/kmainwindow.cpp:214
#14 operator* (this=optimized out) at ../../kdeui/widgets/kmainwindow.cpp:214
#15 KMainWindow::memberList () at ../../kdeui/widgets/kmainwindow.cpp:1176

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail] [Bug 266666] KMail cannot see a folder it created

[steve]

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

st...@bawue.de changed:

   What|Removed |Added

 CC||st...@bawue.de

--- Comment #1 from st...@bawue.de ---
This bug is still present in KDE 4.11.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

[Akonadi] [Bug 325224] New: CalDav doesn't read server items

[steve]

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

Bug ID: 325224
   Summary: CalDav doesn't read server items
Classification: Unclassified
   Product: Akonadi
   Version: 4.11
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: DAV Resource
  Assignee: kdepim-bugs@kde.org
  Reporter: st...@bawue.de

CalDav is treating the server as a write-only resource.  It is not reading any
items already on the server, and not seeing changes to the items it placed onto
the server (including deletion).

Items written with Kontact generate files on the server, but are not viewable
using Kontact on another machine.  The behaviour is the same in the other
direction (starting with Kontact on the 2nd machine).

Thunderbird (with Lightning calendar add-on) can see the items.

Reproducible: Always

Steps to Reproduce:
1. Write a calendar entry to a server from elsewhere
2. Refresh calendar in Kontact

Actual Results:  
New items and changes are not visible in Kontact.

Expected Results:  
New items and changes should be visible in Kontact.

Using 4.11.1 64-bit on OpenSUSE 12.3 from the normal KDE: repository.  System
patches are up to date.  Two systems are exhibiting the same behaviour.

The server is a Synology Diskstation (DSM 4.3 - the current software release).

The problem persists over reboots.  Changing the calendar folder settings to
automatically sync after 1min makes no difference.

CalDav is effectively not usable.  I have not tested GroupDav or CardDav.

-- 
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 325226] New: Kolab resources disappeared, can't be re-added

[steve]

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

Bug ID: 325226
   Summary: Kolab resources disappeared, can't be re-added
Classification: Unclassified
   Product: Akonadi
   Version: 4.11
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: Kolab Resource
  Assignee: kdepim-bugs@kde.org
  Reporter: st...@bawue.de
CC: kdepim-bugs@kde.org

Since the last update (4.11.1), my Kolab resources have disappeared.  That's
already a bug that happens sometimes.

Normally, they can be retrieved by some combination 're-creating' the folders
in the Kolab config, restarting Kontact and/or restarting Akonadi.

This now doesn't work.  Completely removing the Kolab resource and adding a new
one doesn't work either.  The Kolab resource itself appears in the list, but
the address book and calendar components don't see any resources via Kolab.

Reproducible: Always

Steps to Reproduce:
1. Set up a Kolab resource for calendar and address book.
Actual Results:  
Calendar and address book not usable via Kolab (ie: the relevant components
don't list them as available).

Expected Results:  
The Kolab calendar and address book should be usable as normal.

Using 4.11.1 64-bit on OpenSUSE 12.3 from the normal KDE: repository.  System
patches are up to date.  Two systems are exhibiting the same behaviour.

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

[knotes] [Bug 247612] KNotes has (send) To Desktop greyed out

[Steve Wickert]

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

Steve Wickert steve.wick...@gmail.com changed:

   What|Removed |Added

 CC||steve.wick...@gmail.com

--- Comment #10 from Steve Wickert steve.wick...@gmail.com ---
Bug still present as of 2013-07-20 in knotes-4.10.5. I was able to find this
bug description fairly quickly on Google and the workaround (Show note in
taskbar and right click and move from there) works fine, but having the To
deskop main menu option greyed out is clearly a bug. Hope this gets fixed
sometime soon :-)

-- 
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 316840] imap resource starts crazy connect / disconnect cycle to mail server

[Steve Evans]

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

Steve Evans ste...@gorbag.com changed:

   What|Removed |Added

 CC||ste...@gorbag.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 321875] New: kmail segfaulted while idling

[Steve]

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

Bug ID: 321875
   Summary: kmail segfaulted while idling
Classification: Unclassified
   Product: Akonadi
   Version: 4.10
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: IMAP resource
  Assignee: er...@kde.org
  Reporter: sgr...@redhat.com
CC: kdepim-bugs@kde.org, vkra...@kde.org

Application: akonadi_imap_resource (4.10)
KDE Platform Version: 4.10.4
Qt Version: 4.8.4
Operating System: Linux 3.9.6-200.fc18.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
The program was idling. I was not doing anything. I suppose it may have been
checking for email as it periodically does.

-- Backtrace:
Application: IMAP Account of type IMAP E-Mail Server (akonadi_imap_resource),
signal: Segmentation fault
Using host libthread_db library /lib64/libthread_db.so.1.
81T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f564b866880 (LWP 3104))]

Thread 3 (Thread 0x7f563e9ac700 (LWP 3156)):
#0  0x0037b080aacf in __pthread_mutex_unlock_usercnt (mutex=0x7f5638000a60,
decr=decr@entry=1) at pthread_mutex_unlock.c:52
#1  0x0037b080ab2a in __GI___pthread_mutex_unlock (mutex=optimized out)
at pthread_mutex_unlock.c:297
#2  0x0037b2c84dd1 in g_mutex_unlock (mutex=mutex@entry=0x7f56380009a0) at
gthread-posix.c:229
#3  0x0037b2c47046 in g_main_context_acquire (context=0x7f56380009a0) at
gmain.c:2790
#4  0x0037b2c47c04 in g_main_context_iterate
(context=context@entry=0x7f56380009a0, block=block@entry=1,
dispatch=dispatch@entry=1, self=optimized out) at gmain.c:3240
#5  0x0037b2c47e44 in g_main_context_iteration (context=0x7f56380009a0,
may_block=1) at gmain.c:3351
#6  0x0037bcda5fa6 in QEventDispatcherGlib::processEvents
(this=0x7f56380008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#7  0x0037bcd765ef in QEventLoop::processEvents
(this=this@entry=0x7f563e9abce0, flags=...) at kernel/qeventloop.cpp:149
#8  0x0037bcd76878 in QEventLoop::exec (this=0x7f563e9abce0, flags=...) at
kernel/qeventloop.cpp:204
#9  0x0037bcc78980 in QThread::exec (this=optimized out) at
thread/qthread.cpp:542
#10 0x0030e5e4017a in KIMAP::SessionThread::run (this=0xd72ec0) at
/usr/src/debug/kdepimlibs-4.10.4/kimap/sessionthread.cpp:188
#11 0x0037bcc7b95c in QThreadPrivate::start (arg=0xd72ec0) at
thread/qthread_unix.cpp:338
#12 0x0037b0807d15 in start_thread (arg=0x7f563e9ac700) at
pthread_create.c:308
#13 0x0037b04f248d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:114

Thread 2 (Thread 0x7f563d18f700 (LWP 3166)):
#0  0x7fffac9d79c9 in clock_gettime ()
#1  0x0037b140413d in __GI_clock_gettime (clock_id=optimized out,
tp=optimized out) at ../sysdeps/unix/clock_gettime.c:115
#2  0x0037bccd18d4 in do_gettime (frac=0x7f563d18ea38, sec=0x7f563d18ea30)
at tools/qelapsedtimer_unix.cpp:123
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#4  0x0037bcda68ad in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7f5634002860) at kernel/qeventdispatcher_unix.cpp:354
#5  0x0037bcda6bf3 in QTimerInfoList::timerWait (this=0x7f5634002860,
tm=...) at kernel/qeventdispatcher_unix.cpp:461
#6  0x0037bcda565c in timerSourcePrepareHelper (src=optimized out,
timeout=0x7f563d18eb24) at kernel/qeventdispatcher_glib.cpp:136
#7  0x0037bcda5705 in timerSourcePrepare (source=optimized out,
timeout=timeout@entry=0x7f563d18eb24) at kernel/qeventdispatcher_glib.cpp:169
#8  0x0037b2c475b8 in g_main_context_prepare
(context=context@entry=0x7f56340009a0, priority=priority@entry=0x7f563d18eb88)
at gmain.c:2986
#9  0x0037b2c47c4b in g_main_context_iterate
(context=context@entry=0x7f56340009a0, block=block@entry=1,
dispatch=dispatch@entry=1, self=optimized out) at gmain.c:3270
#10 0x0037b2c47e44 in g_main_context_iteration (context=0x7f56340009a0,
may_block=1) at gmain.c:3351
#11 0x0037bcda5fa6 in QEventDispatcherGlib::processEvents
(this=0x7f56340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#12 0x0037bcd765ef in QEventLoop::processEvents
(this=this@entry=0x7f563d18ece0, flags=...) at kernel/qeventloop.cpp:149
#13 0x0037bcd76878 in QEventLoop::exec (this=0x7f563d18ece0, flags=...) at
kernel/qeventloop.cpp:204
#14 0x0037bcc78980 in QThread::exec (this=optimized out) at
thread/qthread.cpp:542
#15 0x0030e5e4017a in KIMAP::SessionThread::run (this=0xc24e60) at
/usr/src/debug/kdepimlibs-4.10.4/kimap/sessionthread.cpp:188
#16 0x0037bcc7b95c in QThreadPrivate::start (arg=0xc24e60) at
thread/qthread_unix.cpp:338
#17 0x0037b0807d15 in start_thread (arg=0x7f563d18f700) at
pthread_create.c:308
#18 0x0037b04f248d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:114

Thread 1 (Thread 0x7f564b866880 (LWP 3104)):
[KCrash Handler]
#6  

[kmail2] [Bug 321116] DIMAP mail loss on deleting folder after all messages were moved elsewhere.

[steve]

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

st...@bawue.de changed:

   What|Removed |Added

   Platform|OpenBSD Packages|openSUSE RPMs

-- 
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 321116] New: DIMAP mail loss on deleting folder after all messages were moved elsewhere.

[steve]

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

Bug ID: 321116
   Summary: DIMAP mail loss on deleting folder after all messages
were moved elsewhere.
Classification: Unclassified
   Product: kmail2
   Version: 4.10.4
  Platform: OpenBSD Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: st...@bawue.de

After moving all the messages (several hundred) out of a folder appeared to
have completed, the folder was deleted.  The messages were already visible at
the new location, but when the old (empty) folder was deleted a lot of those
messages disappeared completely.

Reproducible: Sometimes

Steps to Reproduce:
1. Move all messages from one DIMAP folder to another.
2. Delete the (now empty) folder.

Actual Results:  
Some of the moved messages disappeared.

Expected Results:  
All of the moved messages should be in the second folder.

The folder deletion appears to be executed immediately, even though other
related actions may still be pending.

I could see no indication that the moving of messages was still going on.

-- 
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 316541] akonadi_imap_resource uses 50% of one core even while KMail is shut down

[Steve Evans]

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

Steve Evans ste...@gorbag.com changed:

   What|Removed |Added

 CC||ste...@gorbag.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 312830] New: Kmail crashed while viewing email

[Steve]

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

Bug ID: 312830
   Summary: Kmail crashed while viewing email
Classification: Unclassified
   Product: kontact
   Version: 4.9.4
  Hardware: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: sgr...@redhat.com

Application: kontact (4.9.4)
KDE Platform Version: 4.9.4
Qt Version: 4.8.4
Operating System: Linux 3.6.10-4.fc18.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
When kmail crashed, I had clicked on an email I wanted to see. The interface
froze up and I decided to browse some web sites. Then the crash handler popped
up. About 5 minutes had ellapsed from the time I clicked on an email until the
crash occurred. I do have filters that send email to the trash. So, I don't
know if that had anything to do with a crash.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library /lib64/libthread_db.so.1.
81T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7fe50840c880 (LWP 6188))]

Thread 4 (Thread 0x7fe4f875d700 (LWP 6189)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:165
#1  0x003e6ce1672d in WTF::TCMalloc_PageHeap::scavengerThread
(this=0x3e6d800ce0 WTF::pageheap_memory) at wtf/FastMalloc.cpp:2495
#2  0x003e6ce16839 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=optimized out) at wtf/FastMalloc.cpp:1618
#3  0x003e41407d15 in start_thread (arg=0x7fe4f875d700) at
pthread_create.c:308
#4  0x003e410f22cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:114

Thread 3 (Thread 0x7fe4f7e5c700 (LWP 6190)):
#0  0x003e410e97ed in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x003e40c47d44 in g_main_context_poll (n_fds=1, fds=0x7fe4f00029c0,
timeout=4390, context=0x7fe4f9a0, priority=optimized out) at gmain.c:3584
#2  g_main_context_iterate (context=context@entry=0x7fe4f9a0,
block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at
gmain.c:3285
#3  0x003e40c47e64 in g_main_context_iteration (context=0x7fe4f9a0,
may_block=1) at gmain.c:3351
#4  0x003e4d1a60f6 in QEventDispatcherGlib::processEvents
(this=0x7fe4f8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#5  0x003e4d1767df in QEventLoop::processEvents
(this=this@entry=0x7fe4f7e5bd00, flags=...) at kernel/qeventloop.cpp:149
#6  0x003e4d176a68 in QEventLoop::exec (this=0x7fe4f7e5bd00, flags=...) at
kernel/qeventloop.cpp:204
#7  0x003e4d078950 in QThread::exec (this=optimized out) at
thread/qthread.cpp:542
#8  0x003e4d07b92c in QThreadPrivate::start (arg=0xb545e0) at
thread/qthread_unix.cpp:338
#9  0x003e41407d15 in start_thread (arg=0x7fe4f7e5c700) at
pthread_create.c:308
#10 0x003e410f22cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:114

Thread 2 (Thread 0x7fe4f6707700 (LWP 6191)):
#0  0x003e410e97ed in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x003e40c47d44 in g_main_context_poll (n_fds=3, fds=0x7fe4e00010c0,
timeout=-1, context=0xe46410, priority=optimized out) at gmain.c:3584
#2  g_main_context_iterate (context=0xe46410, block=block@entry=1,
dispatch=dispatch@entry=1, self=optimized out) at gmain.c:3285
#3  0x003e40c481a2 in g_main_loop_run (loop=0xe463a0) at gmain.c:3484
#4  0x003e49ccc546 in gdbus_shared_thread_func (user_data=0xe463e0) at
gdbusprivate.c:277
#5  0x003e40c6b5f5 in g_thread_proxy (data=0xe4c990) at gthread.c:797
#6  0x003e41407d15 in start_thread (arg=0x7fe4f6707700) at
pthread_create.c:308
#7  0x003e410f22cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:114

Thread 1 (Thread 0x7fe50840c880 (LWP 6188)):
[KCrash Handler]
#6  operator QItemSelectionModel* (this=error reading variable: Cannot access
memory at address 0x322d414b) at ../../src/corelib/kernel/qpointer.h:78
#7  QAbstractItemView::selectionModel (this=0x322d4143) at
itemviews/qabstractitemview.cpp:766
#8  0x003f1fec6676 in MailCommon::FolderTreeWidget::selectedCollections
(this=optimized out) at
/usr/src/debug/kdepim-4.9.4/mailcommon/foldertreewidget.cpp:244
#9  0x003f20f2206a in KMMainWidget::updateFolderMenu
(this=this@entry=0x135c090) at
/usr/src/debug/kdepim-4.9.4/kmail/kmmainwidget.cpp:4167
#10 0x003f20f32eb8 in KMMainWidget::slotEndCheckFetchCollectionsDone
(this=0x135c090, job=optimized out) at
/usr/src/debug/kdepim-4.9.4/kmail/kmmainwidget.cpp:469
#11 0x003f20f386e6 in KMMainWidget::qt_static_metacall (_o=0x135c090,
_c=optimized out, _id=optimized out, _a=0x79c5a950) at
/usr/src/debug/kdepim-4.9.4/x86_64-redhat-linux-gnu/kmail/kmmainwidget.moc:370
#12 0x003e4d18cebf in QMetaObject::activate (sender=0x11e41930,
m=optimized out, local_signal_index=optimized 

[Bug 309963] Deleting any mail causes heavy system load

[Steve]

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

--- Comment #1 from Steve sgr...@redhat.com ---
Is there anything I can provide to help diagnose the problem? This is a
horrible user experience as it stands. I find that if I close kontact and
restart it, only the New Message button shows up. When I close its again, a
Mail - Kontact is not responding. dialogue shows up. Killing it again and
again eventually causes something to get freed up and Kontact sort of works as
you would expect. So, to me this sounds a lot like a synchronization issue.

I also have some Coverity scan reports that show lots of different problems. If
someone from KDE wants to see them, email me. Would be happy to share if it
helps.

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

[Bug 305454] Crash on Update address book folder (kolabproxy/akonadi)

[steve]

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

--- Comment #6 from st...@bawue.de ---
Hi,

Now using KDE 4.9.4.  I'm not able to reproduce this bug - the picture handling
seems to be working fine.  As far as I am concerned, this can be closed.

Many thanks,

Steve

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

[Bug 311492] New: Kontact crashs on closing

[Steve]

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

Bug ID: 311492
  Severity: crash
   Version: 4.9.3
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: Kontact crashs on closing
Classification: Unclassified
OS: Linux
  Reporter: sgr...@redhat.com
  Hardware: Fedora RPMs
Status: UNCONFIRMED
 Component: general
   Product: kontact

Application: kontact (4.9.3)
KDE Platform Version: 4.9.3
Qt Version: 4.8.3
Operating System: Linux 3.6.9-2.fc17.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
I was reading email, virtuoso is using about 150% of the CPU and everything is
taking forever. I had been waiting for 3 minutes for 1 email to delete and
decided to just shutdown kontact and turn the computer off. After I closed
kontact, a little later the crash handler popped up.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library /lib64/libthread_db.so.1.
82T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f6affbd6880 (LWP 3192))]

Thread 3 (Thread 0x7f6af0940700 (LWP 3193)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:166
#1  0x003955c1677d in WTF::TCMalloc_PageHeap::scavengerThread
(this=0x3956600980) at wtf/FastMalloc.cpp:2495
#2  0x003955c16889 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=optimized out) at wtf/FastMalloc.cpp:1618
#3  0x0033db407d14 in start_thread (arg=0x7f6af0940700) at
pthread_create.c:309
#4  0x0033db0f168d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 2 (Thread 0x7f6af003f700 (LWP 3194)):
#0  0x0033db0e8bdf in __GI___poll (fds=optimized out, nfds=optimized
out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x0033dd447af4 in g_main_context_poll (n_fds=1, fds=0x7f6ae80029c0,
timeout=6367, context=0x7f6ae80009a0, priority=optimized out) at gmain.c:3440
#2  g_main_context_iterate (context=context@entry=0x7f6ae80009a0,
block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at
gmain.c:3141
#3  0x0033dd447c14 in g_main_context_iteration (context=0x7f6ae80009a0,
may_block=1) at gmain.c:3207
#4  0x0033e69a5ff6 in QEventDispatcherGlib::processEvents
(this=0x7f6ae80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#5  0x0033e6976cbf in QEventLoop::processEvents
(this=this@entry=0x7f6af003ed00, flags=...) at kernel/qeventloop.cpp:149
#6  0x0033e6976f48 in QEventLoop::exec (this=0x7f6af003ed00, flags=...) at
kernel/qeventloop.cpp:204
#7  0x0033e68787e0 in QThread::exec (this=optimized out) at
thread/qthread.cpp:501
#8  0x0033e687b7bc in QThreadPrivate::start (arg=0x841e50) at
thread/qthread_unix.cpp:338
#9  0x0033db407d14 in start_thread (arg=0x7f6af003f700) at
pthread_create.c:309
#10 0x0033db0f168d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 1 (Thread 0x7f6affbd6880 (LWP 3192)):
[KCrash Handler]
#6  0x00394d7fdb96 in at (this=0x3361aa36b0, i=1223592264) at
../../src/corelib/tools/qlist.h:100
#7  at (i=1223592264, this=0x3361aa36b0) at ../../src/corelib/tools/qlist.h:470
#8  QStackedLayout::currentWidget (this=0x3361e4be30) at
kernel/qstackedlayout.cpp:378
#9  0x00336cc95578 in MessageList::Pane::markMessageItemsAsAboutToBeRemoved
(this=optimized out, ref=2, bMark=false) at
/usr/src/debug/kdepim-4.9.3/messagelist/pane.cpp:832
#10 0x00336c7190ae in KMMainWidget::slotTrashMessagesCompleted
(this=0xfff200, command=0x9edf950) at
/usr/src/debug/kdepim-4.9.3/kmail/kmmainwidget.cpp:2168
#11 0x00336c7394b1 in KMMainWidget::qt_static_metacall (_o=0xfff200,
_c=optimized out, _id=optimized out, _a=0x7fffd9bfe5d0) at
/usr/src/debug/kdepim-4.9.3/x86_64-redhat-linux-gnu/kmail/kmmainwidget.moc:483
#12 0x0033e698e71f in QMetaObject::activate (sender=0x9edf950, m=optimized
out, local_signal_index=optimized out, argv=0x7fffd9bfe5d0) at
kernel/qobject.cpp:3547
#13 0x00336c703bef in KMMoveCommand::moveDone (this=this@entry=0x9edf950,
_t1=_t1@entry=0x9edf950) at
/usr/src/debug/kdepim-4.9.3/x86_64-redhat-linux-gnu/kmail/kmcommands.moc:1630
#14 0x00336c703c37 in KMMoveCommand::completeMove (this=0x9edf950,
result=KMCommand::OK) at /usr/src/debug/kdepim-4.9.3/kmail/kmcommands.cpp:1474
#15 0x0033e698e71f in QMetaObject::activate (sender=0x13578fb0,
m=optimized out, local_signal_index=optimized out, argv=0x7fffd9bfe740) at
kernel/qobject.cpp:3547
#16 0x003361333e42 in KJob::result (this=this@entry=0x13578fb0,
_t1=_t1@entry=0x13578fb0) at
/usr/src/debug/kdelibs-4.9.3/x86_64-redhat-linux-gnu/kdecore/kjob.moc:207
#17 0x003361333e80 in KJob::emitResult (this=0x13578fb0) at
/usr/src/debug/kdelibs-4.9.3/kdecore/jobs/kjob.cpp:318
#18 0x0033e698c86e in QObject::event (this=0x13578fb0, e=optimized out)
at kernel/qobject.cpp:1195
#19 

[Bug 310409] New: Kontact crashed when moving folders imported from Thunderbird

[Steve]

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

Bug ID: 310409
  Severity: crash
   Version: unspecified
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: Kontact crashed when moving folders imported from
Thunderbird
Classification: Unclassified
OS: Linux
  Reporter: stev...@sprynet.com
  Hardware: Ubuntu Packages
Status: UNCONFIRMED
 Component: general
   Product: kontact

Application: kontact (4.8.5)
KDE Platform Version: 4.8.5 (4.8.5)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-33-generic x86_64
Distribution: Ubuntu 12.04.1 LTS

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

I had imported mail from Thunderbird, about 40,000 messages or so in many
folders with subfolders. This went fine. Then I got mail from my POP3 servers.
I waited overnight for everything to settle down, since virtuoso-t (I think)
was using 100% of one of my CPU cores. In the morning, the system was quiet.

Then I moved the imported mail from the imported inbox to the KMail inbox, from
the imported sent folder to KMail sent folder, from imported trash to KMail
trash, and from imported drafts to KMail drafts. I deleted all the imported
folders that I had just emptied. All that went fine.

Then I selected the rest of the imported folders that hadn't been emptied and
dragged them to Local Folders and selected move. The CPU went crazy again,
which I thought was normal with KMail, and KMail didn't respond, so I went away
and ate breakfast. When I came back, Kontact had crashed.

This seems closest to bug 304324, which has been closed and marked as fixed,
but the other bug I listed seems like a close match, too.

-- 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 0x7f3e93f3e7c0 (LWP 2054))]

Thread 4 (Thread 0x7f3e77ae5700 (LWP 2057)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x7f3e90726dec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f3e90726f19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f3e8bbe8e9a in start_thread (arg=0x7f3e77ae5700) at
pthread_create.c:308
#4  0x7f3e91459cbd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x in ?? ()

Thread 3 (Thread 0x7f3e772e4700 (LWP 2058)):
#0  0x7f3e9144e303 in __GI___poll (fds=optimized out, nfds=optimized
out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x7f3e8b71c036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f3e8b71c164 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3e91bcf426 in QEventDispatcherGlib::processEvents
(this=0x7f3e78c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x7f3e91b9ec82 in QEventLoop::processEvents (this=optimized out,
flags=...) at kernel/qeventloop.cpp:149
#5  0x7f3e91b9eed7 in QEventLoop::exec (this=0x7f3e772e3dc0, flags=...) at
kernel/qeventloop.cpp:204
#6  0x7f3e91a9dfa7 in QThread::exec (this=optimized out) at
thread/qthread.cpp:501
#7  0x7f3e91aa0fcb in QThreadPrivate::start (arg=0xf78560) at
thread/qthread_unix.cpp:298
#8  0x7f3e8bbe8e9a in start_thread (arg=0x7f3e772e4700) at
pthread_create.c:308
#9  0x7f3e91459cbd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#10 0x in ?? ()

Thread 2 (Thread 0x7f3e1bfff700 (LWP 2167)):
#0  __pthread_mutex_lock (mutex=0x7f3e1a60) at pthread_mutex_lock.c:64
#1  0x7f3e8b7575a1 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f3e8b71bb4e in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3e8b71bfd6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f3e8b71c164 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f3e91bcf426 in QEventDispatcherGlib::processEvents
(this=0x7f3e18c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x7f3e91b9ec82 in QEventLoop::processEvents (this=optimized out,
flags=...) at kernel/qeventloop.cpp:149
#7  0x7f3e91b9eed7 in QEventLoop::exec (this=0x7f3e1bffed90, flags=...) at
kernel/qeventloop.cpp:204
#8  0x7f3e91a9dfa7 in QThread::exec (this=optimized out) at
thread/qthread.cpp:501
#9  0x7f3e91b7e9ff in QInotifyFileSystemWatcherEngine::run (this=0x2906050)
at io/qfilesystemwatcher_inotify.cpp:248
#10 0x7f3e91aa0fcb in QThreadPrivate::start (arg=0x2906050) at
thread/qthread_unix.cpp:298
#11 0x7f3e8bbe8e9a in start_thread (arg=0x7f3e1bfff700) at
pthread_create.c:308
#12 0x7f3e91459cbd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#13 0x in ?? ()

Thread 1 (Thread 0x7f3e93f3e7c0 (LWP 2054)):
[KCrash Handler]
#6  

[Bug 310409] Kontact crashed when moving folders imported from Thunderbird

[Steve]

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

--- Comment #1 from Steve stev...@sprynet.com ---
When I reopened Kontact, all the folders have apparently been moved
successfully as I requested. Perhaps it just needs a better notification that
the job is done than crashing the application? (Just kidding, a little
developer humor there.)

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

[Bug 310409] Kontact crashed when moving folders imported from Thunderbird

[Steve]

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

--- Comment #2 from Steve stev...@sprynet.com ---
When I click on one of the many folders I imported and then moved all at once,
I get a notification pop-up that says something like:

Local Folders
Local Folders: Maildir
'/home/userid/.local/share/local-mail/.Import.directory/.Thunderbird-Import.directory/Car'
for collection 'Car' is invalid.

Import is the directory I created to import the mail from Thunderbird into.
This import was done from Import Messages in the File menu. All the e-mails
are displayed correctly, and when I click on them, I see their contents in the
preview pane, but I also sometimes get this notification pop-up:

Local Folders
Local Folders: Error opening
/home/userid/.local/share/local-mail/.Import.directory/.Thunderbird-Import.directory/Car;
this folder is missing.

However, when I click on most of the messages in the sent-mail folder, which I
imported from Thunderbird, I don't get a notification pop-up, but I don't see
the contents of the message in the preview pane or when I double-click to open
the message, either. I see the From, To, and Date headers, but not the body of
the message.

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

[Bug 310409] Kontact crashed when moving folders imported from Thunderbird

[Steve]

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

--- Comment #3 from Steve stev...@sprynet.com ---
Every time I get mail from my POP3 accounts, I get what seems like hundreds of
notification pop-ups saying:

Local Folders
Local Folders: Maildir
'/home/userid/.local/share/local-mail/.Import.directory/.Thunderbird-Import.directory/Travel'
for collection 'Travel' is invalid.

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

[Bug 309963] New: Deleting any mail causes heavy system load

[Steve]

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

Bug ID: 309963
  Severity: major
   Version: 4.9
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: Deleting any mail causes heavy system load
Classification: Unclassified
OS: Linux
  Reporter: sgr...@redhat.com
  Hardware: Fedora RPMs
Status: UNCONFIRMED
 Component: libkdepim
   Product: kdepim

Deleting any email takes forever and causes heavy system load. Kmail 3 was
light and fast, kmail4 consumes lots of resources.

  PID   USER  PR  NI  VIRT RESSHR S %CPU %MEMTIME+  COMMAND 
 2068 sgrubb39  19 1372m 371m 6920 S 158.2  6.3  19:14.60 virtuoso-t
 2074 sgrubb20   0 2919m 503m  59m S  2.3  8.5   0:43.96 kontact  
 2063 sgrubb39  19 1755m  47m  24m S  6.3  0.8   1:09.00 nepomukservices

Reproducible: Always

Steps to Reproduce:
1. Delete an email
2. wait 5 minutes for it to delete
Actual Results:  
It takes minutes to delete an email which took a second or two under kmail3.

Expected Results:  
Gone in a second or two

Even after deleting email, kmail causes heavy load for 10's of minutes to an
hour later. This really eats laptop battery.

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

[Bug 309968] New: Encrypting email malfunctions

[Steve]

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

Bug ID: 309968
  Severity: major
   Version: 4.9
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: Encrypting email malfunctions
Classification: Unclassified
OS: Linux
  Reporter: sgr...@redhat.com
  Hardware: Fedora RPMs
Status: UNCONFIRMED
 Component: messagecore
   Product: kdepim

On kmail3, sending encrypted email works fine. After migrating to kmail4 (4.9.3
specifically), I can no longer exchange encrypted emails with anyone. I get a
generic error that seems meaningless:  Could not compose message: general
failure.  That doesn't give me a clue as to how to solve the problem. Reading
encrypted emails works fine, its just the sending that is broken.

Reproducible: Always

Steps to Reproduce:
1. Receive encrypted email
2. Reply such that it will be encrypted
3. Click send
Actual Results:  
vague error message

Expected Results:  
mail sent 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

[Bug 309968] Encrypting email malfunctions

[Steve]

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

--- Comment #2 from Steve sgr...@redhat.com ---
Its configured to use OpenPgp/Mime via gpg. Looking around, there are next to
no settings to configure. What would you need to see? I haven't changed
anything from kmail3 and it migrated via the migration tool.

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

[Bug 271000] Bring smart rewrapping from KNode to KMail ;-)

[Steve Riley]

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

Steve Riley st...@rileyz.net changed:

   What|Removed |Added

 CC||st...@rileyz.net

--- Comment #7 from Steve Riley st...@rileyz.net ---
Agreed with #6. I do believe I saw proper behavior for a few days right after
4.9.2 hit Ubuntu's Universe repository; but now, the old behavior is back.
Should we re-open another of those bugs?

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

[Bug 294489] imap resource crashed after changing(?) account settings

[Steve]

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

Steve sgr...@redhat.com changed:

   What|Removed |Added

 CC||sgr...@redhat.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

[Bug 294489] imap resource crashed after changing(?) account settings

[Steve]

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

--- Comment #4 from Steve sgr...@redhat.com ---
Created attachment 74571
  -- https://bugs.kde.org/attachment.cgi?id=74571action=edit
New crash information added by DrKonqi

akonadi_imap_resource (4.9) on KDE Platform 4.9.2 using Qt 4.8.2

- What I was doing when the application crashed:

I was asked to update the imap password. When I did so, kmail crashed
immediately.

-- Backtrace (Reduced):
#6  0x7f22a57d349f in QObject::disconnect (sender=0xae82b0, signal=0xe578e9
stateChanged(KIMAP::Session::State,KIMAP::Session::State), receiver=0xaecb10,
method=0xb1bd59
onSessionStateChanged(KIMAP::Session::State,KIMAP::Session::State)) at
kernel/qobject.cpp:2891
#7  0x00453915 in SessionPool::killSession (this=this@entry=0xaecb10,
session=session@entry=0xae82b0,
termination=termination@entry=SessionPool::LogoutSession) at
/usr/src/debug/kdepim-runtime-4.9.2/resources/imap/sessionpool.cpp:176
#8  0x00454341 in SessionPool::cancelSessionCreation
(this=this@entry=0xaecb10, session=0xae82b0, errorCode=errorCode@entry=2,
errorMessage=...) at
/usr/src/debug/kdepim-runtime-4.9.2/resources/imap/sessionpool.cpp:233
#9  0x00455629 in SessionPool::onPasswordRequestDone (this=0xaecb10,
resultType=optimized out, password=...) at
/usr/src/debug/kdepim-runtime-4.9.2/resources/imap/sessionpool.cpp:295
#10 0x004561a7 in SessionPool::qt_static_metacall (_o=optimized out,
_c=optimized out, _id=optimized out, _a=optimized out) at
/usr/src/debug/kdepim-runtime-4.9.2/x86_64-redhat-linux-gnu/resources/imap/sessionpool.moc:93

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

[Bug 308420] New: kmail4 crashed opening encrypted email

[Steve]

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

Bug ID: 308420
  Severity: crash
   Version: 4.9.2
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: kmail4 crashed opening encrypted email
Classification: Unclassified
OS: Linux
  Reporter: sgr...@redhat.com
  Hardware: Fedora RPMs
Status: UNCONFIRMED
 Component: general
   Product: kontact

Application: kontact (4.9.2)
KDE Platform Version: 4.9.2
Qt Version: 4.8.2
Operating System: Linux 3.6.1-1.fc17.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
Opening email. First attempt I forgot to enter my password. It failed and asked
If I want to try again. I did and typed the password and it crashed.
immediately.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library /lib64/libthread_db.so.1.
82T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f8f56fed880 (LWP 2209))]

Thread 3 (Thread 0x7f8f44b71700 (LWP 2210)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:166
#1  0x7f8f6db8877d in WTF::TCMalloc_PageHeap::scavengerThread
(this=0x7f8f6e572980) at wtf/FastMalloc.cpp:2495
#2  0x7f8f6db9 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=optimized out) at wtf/FastMalloc.cpp:1618
#3  0x7f8f68972d14 in start_thread (arg=0x7f8f44b71700) at
pthread_create.c:309
#4  0x7f8f67c1767d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 2 (Thread 0x7f8f44370700 (LWP 2211)):
#0  0x7f8f657409b1 in g_mutex_unlock (mutex=mutex@entry=0x7f8f3c0009a0) at
gthread-posix.c:227
#1  0x7f8f65704a0e in g_main_context_iterate
(context=context@entry=0x7f8f3c0009a0, block=block@entry=1,
dispatch=dispatch@entry=1, self=optimized out) at gmain.c:3124
#2  0x7f8f65704c14 in g_main_context_iteration (context=0x7f8f3c0009a0,
may_block=1) at gmain.c:3207
#3  0x7f8f68d2b4e6 in QEventDispatcherGlib::processEvents
(this=0x7f8f3c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x7f8f68cfc10f in QEventLoop::processEvents
(this=this@entry=0x7f8f4436fd20, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f8f68cfc398 in QEventLoop::exec (this=0x7f8f4436fd20, flags=...) at
kernel/qeventloop.cpp:204
#6  0x7f8f68bff650 in QThread::exec (this=optimized out) at
thread/qthread.cpp:501
#7  0x7f8f68c025eb in QThreadPrivate::start (arg=0x14d7e10) at
thread/qthread_unix.cpp:307
#8  0x7f8f68972d14 in start_thread (arg=0x7f8f44370700) at
pthread_create.c:309
#9  0x7f8f67c1767d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 1 (Thread 0x7f8f56fed880 (LWP 2209)):
[KCrash Handler]
#6  0x7f8f62d9de84 in KMime::Content::parent (this=0x53b0aa0) at
/usr/src/debug/kdepimlibs-4.9.2/kmime/kmime_content.cpp:949
#7  0x7f8eead42336 in MessageCore::NodeHelper::nextSibling (node=0x53b0aa0)
at /usr/src/debug/kdepim-4.9.2/messagecore/nodehelper.cpp:32
#8  0x7f8ee8d54b64 in
MessageViewer::ObjectTreeParser::parseObjectTreeInternal (this=0x7fffaef8e870,
node=0x53b0aa0) at
/usr/src/debug/kdepim-4.9.2/messageviewer/objecttreeparser.cpp:296
#9  0x7f8ee8d8a3d0 in MessageViewer::ViewerPrivate::parseContent
(this=this@entry=0x1cbbe90, content=0x53b0aa0) at
/usr/src/debug/kdepim-4.9.2/messageviewer/viewer_p.cpp:1022
#10 0x7f8ee8d8bc9c in MessageViewer::ViewerPrivate::displayMessage
(this=this@entry=0x1cbbe90) at
/usr/src/debug/kdepim-4.9.2/messageviewer/viewer_p.cpp:894
#11 0x7f8ee8d8c1b6 in MessageViewer::ViewerPrivate::updateReaderWin
(this=0x1cbbe90) at /usr/src/debug/kdepim-4.9.2/messageviewer/viewer_p.cpp:2251
#12 0x7f8ee8d8eefa in MessageViewer::ViewerPrivate::qt_static_metacall
(_o=0x1cbbe90, _c=optimized out, _id=optimized out, _a=optimized out) at
/usr/src/debug/kdepim-4.9.2/x86_64-redhat-linux-gnu/messageviewer/viewer_p.moc:229
#13 0x7f8f68d13b6f in QMetaObject::activate (sender=0x1cbbf20, m=optimized
out, local_signal_index=optimized out, argv=0x0) at kernel/qobject.cpp:3547
#14 0x7f8f68d11aec in QObject::event (this=0x1cbbf20, e=optimized out) at
kernel/qobject.cpp:1157
#15 0x7f8f6994437c in QApplicationPrivate::notify_helper
(this=this@entry=0x14c9aa0, receiver=receiver@entry=0x1cbbf20,
e=e@entry=0x7fffaef8f2a0) at kernel/qapplication.cpp:4551
#16 0x7f8f699487fa in QApplication::notify (this=0x7fffaef8f6a0,
receiver=0x1cbbf20, e=0x7fffaef8f2a0) at kernel/qapplication.cpp:4412
#17 0x7f8f6a6618a6 in KApplication::notify (this=0x7fffaef8f6a0,
receiver=0x1cbbf20, event=0x7fffaef8f2a0) at
/usr/src/debug/kdelibs-4.9.2/kdeui/kernel/kapplication.cpp:311
#18 0x7f8f68cfd3be in QCoreApplication::notifyInternal
(this=0x7fffaef8f6a0, receiver=0x1cbbf20, event=0x7fffaef8f2a0) at
kernel/qcoreapplication.cpp:915
#19 0x7f8f68d2dd32 in 

[Bug 305454] New: Crash on Update address book folder (kolabproxy/akonadi)

[steve]

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

Bug ID: 305454
  Severity: crash
   Version: 4.9
  Priority: NOR
CC: kdepim-bugs@kde.org
  Assignee: kdepim-bugs@kde.org
   Summary: Crash on Update address book folder
(kolabproxy/akonadi)
Classification: Unclassified
OS: Linux
  Reporter: st...@bawue.de
  Hardware: openSUSE RPMs
Status: UNCONFIRMED
 Component: Kolab Resource
   Product: Akonadi

Application: akonadi_kolabproxy_resource (4.9)
KDE Platform Version: 4.9.00 release 559
Qt Version: 4.8.2
Operating System: Linux 3.1.10-1.16-desktop x86_64
Distribution: openSUSE 12.1 (x86_64)

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

Right clicked on 'Contacts' address book folder, and selected Update address
book folder (F5).

- Other notes:

This bug did not occur in KDE 4.8.x.  It's new in 4.9.0.

As apparent from the stack trace, it's related to the contact's photograph. 
One workaround is to remove the photos - I tried this and the refresh
completed... but now my phone doesn't show me anybody's picture when a call is
made. :-(

The crash can be reproduced every time.

-- Backtrace:
Application: Kolab of type Kolab Groupware Server
(akonadi_kolabproxy_resource), signal: Segmentation fault
[KCrash Handler]
#6  headerKMime::Headers::ContentTransferEncoding (create=optimized out,
this=optimized out) at
/usr/src/debug/kdepimlibs-4.9.0/kmime/kmime_content.h:833
#7  KMime::Content::contentTransferEncoding (this=0x0, create=true) at
/usr/src/debug/kdepimlibs-4.9.0/kmime/kmime_content.cpp:999
#8  0x7f4b4cbd988b in KMime::Content::decodedContent (this=0x0) at
/usr/src/debug/kdepimlibs-4.9.0/kmime/kmime_content.cpp:374
#9  0x7f4b4f65c03d in Kolab::getPicture (pictureAttachmentName=...,
data=optimized out, type=...) at
/usr/src/debug/libkolab-0.3.1/kolabformat/v2helpers.h:81
#10 0x7f4b4f65c70b in Kolab::addresseeFromKolab (xmlData=..., data=...) at
/usr/src/debug/libkolab-0.3.1/kolabformat/v2helpers.h:121
#11 0x7f4b4f663fa8 in Kolab::KolabObjectReader::Private::readKolabV2
(this=0xbf9410, msg=..., objectType=Kolab::ContactObject) at
/usr/src/debug/libkolab-0.3.1/kolabformat/kolabobject.cpp:246
#12 0x7f4b4f664fde in Kolab::KolabObjectReader::parseMimeMessage
(this=0x7fffc66e30c0, msg=...) at
/usr/src/debug/libkolab-0.3.1/kolabformat/kolabobject.cpp:391
#13 0x7f4b4f66540d in Kolab::KolabObjectReader::KolabObjectReader
(this=0x7fffc66e30c0, msg=...) at
/usr/src/debug/libkolab-0.3.1/kolabformat/kolabobject.cpp:104
#14 0x00427217 in ?? ()
#15 0x00417ff5 in _start ()

Possible duplicates by query: bug 300141.

Reported using DrKonqi

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

[Bug 288340] Kolab address book disappears

[steve]

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

st...@bawue.de changed:

   What|Removed |Added

 CC||st...@bawue.de

--- Comment #2 from st...@bawue.de ---
I've been having this problem sporadically since KDE 4.7.x.  Now, with 4.9.0,
the Kolab address book is gone almost every time I log in, although the D-IMAP
'Contacts' folder is not made visible again.

I can unhide the folder by un- and re- subscribing (server side).  To get the
calendar back I then have to re-setup the Kolab configuration (including
restarting akonadi and kontact at least once each).

This is with RPMs from the OpenSuse 12.1 x86_64 repository.

Oddly enough, it used to be that my calendar disappeared at the same time. 
Since 4.9.0 that's stayed right where it is!  Perhaps the solution to this
problem can be copied from the calendar code.

Steve

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

[Bug 281227] KMail2 4.7's Find messages ... reproducibly fails to search: Unknown error. (Unable to create persistent search)

[steve]

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

st...@bawue.de changed:

   What|Removed |Added

 CC||st...@bawue.de

--- Comment #39 from st...@bawue.de ---
I'm still getting this error, even on the first search.  I can't get any search
results at all using the Find Messages dialog, although the quick search
(inside the current folder) seems to work fine.

I'm using the 4.9.0 RPMs from the OpenSuse 12.1 repository (x86_64).  FWIW, I'm
have both local folders (Maildir) and disconnected IMAP.

Steve

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

[Bug 303842] New: Kontact crashes on the clicking of Feeds

[Steve]

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

Bug ID: 303842
  Severity: crash
   Version: 4.8.4
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: Kontact crashes on the clicking of Feeds
Classification: Unclassified
OS: Linux
  Reporter: sbra...@gmail.com
  Hardware: Other
Status: UNCONFIRMED
 Component: general
   Product: kontact

Application: kontact (4.8.4)
KDE Platform Version: 4.8.4 (4.8.4)
Qt Version: 4.8.2
Operating System: Linux 3.4.5-2.fc17.i686 i686

-- Information about the crash:
Open Kontact clicked on Feeds and the application crashed...I've had this
problem before in Kororaa/Fedora 16 but it seems the bug has reappeared in
Kororaa/Fedora 17

The crash can be reproduced every time.

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

Thread 3 (Thread 0xb3fabb40 (LWP 12899)):
#0  0xb77bb424 in __kernel_vsyscall ()
#1  0x47dc512c in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:172
#2  0x4ba97db9 in WTF::TCMalloc_PageHeap::scavengerThread
(this=this@entry=0x4c20cc80) at wtf/FastMalloc.cpp:2495
#3  0x4ba97eb0 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=0x4c20cc80) at wtf/FastMalloc.cpp:1618
#4  0x47dc1adf in start_thread (arg=0xb3fabb40) at pthread_create.c:309
#5  0x47cf554e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133

Thread 2 (Thread 0xb3682b40 (LWP 12900)):
#0  0x47e07dcd in __GI_clock_gettime (clock_id=1, tp=0xb3681f78) at
../sysdeps/unix/clock_gettime.c:116
#1  0x48a29966 in do_gettime (frac=0xb3681f70, sec=0xb3681f68) at
tools/qelapsedtimer_unix.cpp:123
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#3  0x48b116af in QTimerInfoList::updateCurrentTime (this=0xb3681ff8) at
kernel/qeventdispatcher_unix.cpp:343
#4  0xb2d004e0 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 1 (Thread 0xb63e07c0 (LWP 12898)):
[KCrash Handler]
#7  elf_machine_rela_relative (reloc_addr_arg=0x62fa9fd5, l_addr=1636012032,
reloc=optimized out) at ../sysdeps/i386/dl-machine.h:644
#8  elf_dynamic_do_Rela (skip_ifunc=0, nrelative=558769, relsize=6794148,
reladdr=optimized out, map=0x9e3d4f0, lazy=optimized out) at do-rel.h:121
#9  _dl_relocate_object (scope=0x9e3d6a8, reloc_mode=reloc_mode@entry=1,
consider_profiling=optimized out, consider_profiling@entry=13) at
dl-reloc.c:295
#10 0x47bf08b2 in dl_open_worker (a=a@entry=0xbfad3e7c) at dl-open.c:416
#11 0x47bec48e in _dl_catch_error (objname=objname@entry=0xbfad3e74,
errstring=errstring@entry=0xbfad3e78, mallocedp=mallocedp@entry=0xbfad3e70,
operate=operate@entry=0x47bf0450 dl_open_worker, args=args@entry=0xbfad3e7c)
at dl-error.c:178
#12 0x47bf00b4 in _dl_open (file=0x9e3b170
/usr/lib/kde4/akregator_sharemicroblog_plugin.so, mode=-2147483647,
caller_dlopen=caller_dlopen@entry=0x48acf212, nsid=-2, argc=argc@entry=1,
argv=argv@entry=0xbfad5db4, env=0x9486570) at dl-open.c:652
#13 0x47db4cbe in dlopen_doit (a=a@entry=0xbfad4030) at dlopen.c:67
#14 0x47bec48e in _dl_catch_error (objname=0x938c2b4, errstring=0x938c2b8,
mallocedp=0x938c2b0, operate=0x47db4c20 dlopen_doit, args=0xbfad4030) at
dl-error.c:178
#15 0x47db5472 in _dlerror_run (operate=optimized out, args=0xbfad4030) at
dlerror.c:164
#16 0x09e398e8 in ?? ()

Possible duplicates by query: bug 302570, bug 301727, bug 301619, bug 301160,
bug 300274.

Reported using DrKonqi

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 303319] New: crash on closing kontact

[Steve]

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

Bug ID: 303319
  Severity: crash
   Version: 4.8.4
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: crash on closing kontact
Classification: Unclassified
OS: Linux
  Reporter: sgr...@redhat.com
  Hardware: Fedora RPMs
Status: UNCONFIRMED
 Component: general
   Product: kontact

Application: kontact (4.8.4)
KDE Platform Version: 4.8.4 (4.8.4)
Qt Version: 4.8.2
Operating System: Linux 3.4.4-5.fc17.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
I had been using kontact for a while. The crash occurred when I was closing
kontact.

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

Thread 3 (Thread 0x7f2bb73ac700 (LWP 5901)):
#0  0x7f2bdb18a595 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f2be039977d in WTF::TCMalloc_PageHeap::scavengerThread
(this=0x7f2be0d83980) at wtf/FastMalloc.cpp:2495
#2  0x7f2be0399889 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=optimized out) at wtf/FastMalloc.cpp:1618
#3  0x7f2bdb186d14 in start_thread () from /lib64/libpthread.so.0
#4  0x7f2bda42b99d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f2bb6bab700 (LWP 5902)):
#0  0x7f2bdb188bc2 in pthread_mutex_lock () from /lib64/libpthread.so.0
#1  0x7f2bd7f576f1 in g_mutex_lock (mutex=mutex@entry=0x7f2bb9a0) at
gthread-posix.c:208
#2  0x7f2bd7f1bac0 in g_main_context_iteration (context=0x7f2bb9a0,
may_block=1) at gmain.c:3206
#3  0x7f2bdb53f506 in QEventDispatcherGlib::processEvents
(this=0x7f2bb8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x7f2bdb51013f in QEventLoop::processEvents
(this=this@entry=0x7f2bb6baad20, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f2bdb5103c8 in QEventLoop::exec (this=0x7f2bb6baad20, flags=...) at
kernel/qeventloop.cpp:204
#6  0x7f2bdb413650 in QThread::exec (this=optimized out) at
thread/qthread.cpp:501
#7  0x7f2bdb4165eb in QThreadPrivate::start (arg=0x1450880) at
thread/qthread_unix.cpp:307
#8  0x7f2bdb186d14 in start_thread () from /lib64/libpthread.so.0
#9  0x7f2bda42b99d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f2bc9824880 (LWP 5900)):
[KCrash Handler]
#6  QStackedWidget::currentWidget (this=0x6c69614d6c6d7468) at
widgets/qstackedwidget.cpp:273
#7  0x7f2b61bcc298 in MessageList::Pane::markMessageItemsAsAboutToBeRemoved
(this=optimized out, ref=3, bMark=false) at
/usr/src/debug/kdepim-4.8.4/messagelist/pane.cpp:779
#8  0x7f2b62992b8e in KMMainWidget::slotTrashMessagesCompleted
(this=0x1bd6fb0, command=0x30ad5a0) at
/usr/src/debug/kdepim-4.8.4/kmail/kmmainwidget.cpp:2198
#9  0x7f2b629b10b6 in KMMainWidget::qt_static_metacall (_o=0x1bd6fb0,
_c=optimized out, _id=optimized out, _a=0x76550530) at
/usr/src/debug/kdepim-4.8.4/x86_64-redhat-linux-gnu/kmail/kmmainwidget.moc:475
#10 0x7f2bdb527b9f in QMetaObject::activate (sender=0x30ad5a0, m=optimized
out, local_signal_index=optimized out, argv=0x76550530) at
kernel/qobject.cpp:3547
#11 0x7f2b6297dabf in KMMoveCommand::moveDone (this=this@entry=0x30ad5a0,
_t1=_t1@entry=0x30ad5a0) at
/usr/src/debug/kdepim-4.8.4/x86_64-redhat-linux-gnu/kmail/kmcommands.moc:1691
#12 0x7f2b6297db07 in KMMoveCommand::completeMove (this=0x30ad5a0,
result=KMCommand::OK) at /usr/src/debug/kdepim-4.8.4/kmail/kmcommands.cpp:1410
#13 0x7f2bdb527b9f in QMetaObject::activate (sender=0x1d9bf820,
m=optimized out, local_signal_index=optimized out, argv=0x765506a0) at
kernel/qobject.cpp:3547
#14 0x7f2bdb99bba2 in KJob::result (this=this@entry=0x1d9bf820,
_t1=_t1@entry=0x1d9bf820) at
/usr/src/debug/kdelibs-4.8.4/x86_64-redhat-linux-gnu/kdecore/kjob.moc:207
#15 0x7f2bdb99bbe0 in KJob::emitResult (this=0x1d9bf820) at
/usr/src/debug/kdelibs-4.8.4/kdecore/jobs/kjob.cpp:318
#16 0x7f2bdb525cee in QObject::event (this=0x1d9bf820, e=optimized out)
at kernel/qobject.cpp:1195
#17 0x7f2bdc15837c in QApplicationPrivate::notify_helper
(this=this@entry=0x1448ab0, receiver=receiver@entry=0x1d9bf820,
e=e@entry=0x1d3e430) at kernel/qapplication.cpp:4551
#18 0x7f2bdc15c7fa in QApplication::notify (this=0x76551ef0,
receiver=0x1d9bf820, e=0x1d3e430) at kernel/qapplication.cpp:4412
#19 0x7f2bdce75756 in KApplication::notify (this=0x76551ef0,
receiver=0x1d9bf820, event=0x1d3e430) at
/usr/src/debug/kdelibs-4.8.4/kdeui/kernel/kapplication.cpp:311
#20 0x7f2bdb5113ee in QCoreApplication::notifyInternal
(this=0x76551ef0, receiver=receiver@entry=0x1d9bf820,
event=event@entry=0x1d3e430) at kernel/qcoreapplication.cpp:915
#21 0x7f2bdb514ea1 in sendEvent (event=0x1d3e430, receiver=0x1d9bf820) at

[Bug 303086] UI formatting problems in KMail Quick Search Bar

[Steve Riley]

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

Steve Riley st...@rileyz.net changed:

   What|Removed |Added

 CC||st...@rileyz.net

--- Comment #8 from Steve Riley st...@rileyz.net ---
Regarding the first issue... yes, in fact, I do have a very long item in this
list. When I imported a calendar file from Google calendar, all items included
a long category string containing some pointer to a Google schema. I deleted
that category in KOrganizer, but this category appears to have also made its
way into KMail. Need to find out how to delete it from there, too.

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

[Bug 303086] UI formatting problems in KMail Quick Search Bar

[Steve Riley]

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

--- Comment #9 from Steve Riley st...@rileyz.net ---
Found it. When I deleted that long-string category and restarted KMail, the
search field became much wider and the button shrank.

Thanks for the tip, and for fixing the bug in the second issue.

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

[Bug 303086] New: UI formatting problems in KMail Quick Search Bar

[Steve Riley]

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

Bug ID: 303086
  Severity: normal
   Version: 4.9 pre
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: UI formatting problems in KMail Quick Search Bar
Classification: Unclassified
OS: Linux
  Reporter: st...@rileyz.net
  Hardware: Ubuntu Packages
Status: UNCONFIRMED
 Component: UI
   Product: kmail2

When the Quick Search Bar is enabled, the sizes of its elements are suboptimal.
The search field is very small, while the category drop-down bar is very long:

http://imgur.com/xsWW6

When the Quick Search Bar is turned off (Ctrl+H), the message list column gains
wide margins on either side:

http://imgur.com/DE09c


Reproducible: Always

Steps to Reproduce:
1. Observer the Quick Search Bar.
2. Press Ctrl+H to show/hide the bar, and observe the large margins.


Expected Results:  
The search field should occupy most of the width, while the dropdown should be
small. When the Quick Search Bar is hidden, the message list should not gain
margins.

steve@x1:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu quantal (development branch)
Release:12.10
Codename:   quantal

steve@x1:~$ uname -a
Linux x1 3.5.0-2-generic #2-Ubuntu SMP Tue Jun 26 14:11:06 UTC 2012 x86_64
x86_64 x86_64 GNU/Linux


steve@x1:~$ kde4-config -v
Qt: 4.8.2
KDE Development Platform: 4.8.90 (4.8.90)
kde4-config: 1.0

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

[Bug 300274] New: KDE desktop crash...

[Steve]

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

Bug ID: 300274
  Severity: crash
   Version: 4.8.3
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: KDE desktop crash...
Classification: Unclassified
OS: Linux
  Reporter: sbra...@gmail.com
  Hardware: Other
Status: UNCONFIRMED
 Component: general
   Product: akregator

Application: akregator (4.8.3)
KDE Platform Version: 4.8.3 (4.8.3)
Qt Version: 4.8.1
Operating System: Linux 3.3.5-2.fc16.i686 i686
Distribution: Kororaa release 16 (Chum)

-- Information about the crash:
Had just installed the nvidia driver 295 and now KDe desktop doesn't work and
all PIM applications crash on startup...

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library /lib/libthread_db.so.1.
[KCrash Handler]
#7  elf_machine_rela_relative (reloc_addr_arg=0xb78d4d95, l_addr=3054915584,
reloc=optimized out) at ../sysdeps/i386/dl-machine.h:644
#8  elf_dynamic_do_Rela (skip_ifunc=0, nrelative=558710, relsize=6793428,
reladdr=optimized out, map=0x917b358, lazy=optimized out) at do-rel.h:121
#9  _dl_relocate_object (scope=0x917b510, reloc_mode=1, consider_profiling=0)
at dl-reloc.c:265
#10 0x43acb3ab in dl_open_worker (a=0xbfa2b730) at dl-open.c:338
#11 0x43ac6d0f in _dl_catch_error (objname=0xbfa2b754, errstring=0xbfa2b758,
mallocedp=0xbfa2b75f, operate=0x43acb100 dl_open_worker, args=0xbfa2b730) at
dl-error.c:178
#12 0x43acad06 in _dl_open (file=0x9175098
/usr/lib/kde4/akregator_sharemicroblog_plugin.so, mode=-2147483647,
caller_dlopen=0x44978623, nsid=-2, argc=3, argv=0xbfa2ce04, env=0x8fc33e0) at
dl-open.c:575
#13 0x43c8cc09 in dlopen_doit (a=0xbfa2b900) at dlopen.c:67
#14 0x43ac6d0f in _dl_catch_error (objname=0x8ed46b4, errstring=0x8ed46b8,
mallocedp=0x8ed46b0, operate=0x43c8cb70 dlopen_doit, args=0xbfa2b900) at
dl-error.c:178
#15 0x43c8d3ba in _dlerror_run (operate=0x43c8cb70 dlopen_doit,
args=0xbfa2b900) at dlerror.c:164
#16 0x43c8ccb7 in __dlopen (file=0x9175098
/usr/lib/kde4/akregator_sharemicroblog_plugin.so, mode=1) at dlopen.c:88
#17 0x44978623 in QLibraryPrivate::load_sys (this=0x9174160) at
plugin/qlibrary_unix.cpp:209
#18 0x44974a94 in load (this=0x9174160) at plugin/qlibrary.cpp:466
#19 QLibraryPrivate::load (this=0x9174160) at plugin/qlibrary.cpp:458
#20 0x44974e5e in QLibraryPrivate::loadPlugin (this=0x9174160) at
plugin/qlibrary.cpp:516
#21 0x449695f3 in QPluginLoader::load (this=0xbfa2bc10) at
plugin/qpluginloader.cpp:227
#22 0x4ac12f98 in KPluginLoader::load (this=0xbfa2bc10) at
/usr/src/debug/kdelibs-4.8.3/kdecore/util/kpluginloader.cpp:224
#23 0x4ac132d3 in KPluginLoader::factory (this=0xbfa2bc10) at
/usr/src/debug/kdelibs-4.8.3/kdecore/util/kpluginloader.cpp:189
#24 0x006f333b in Akregator::PluginManager::createFromService (service=...,
parent=0x9025500) at
/usr/src/debug/kdepim-4.8.3/akregator/src/pluginmanager.cpp:87
#25 0x0073155d in Akregator::Part::loadPlugins (this=0x9025500, type=...) at
/usr/src/debug/kdepim-4.8.3/akregator/src/akregator_part.cpp:285
#26 0x00731ef3 in Akregator::Part::Part (this=0x9025500,
parentWidget=0x8ecbf18, parent=0x21cd2d8, __in_chrg=optimized out,
__vtt_parm=optimized out) at
/usr/src/debug/kdepim-4.8.3/akregator/src/akregator_part.cpp:274
#27 0x007349b5 in KPluginFactory::createPartInstanceAkregator::Part
(parentWidget=0x8ecbf18, parent=0x8ecbf18, args=...) at
/usr/include/kde4/kpluginfactory.h:483
#28 0x4ac11850 in KPluginFactory::create (this=0x9025110, iface=0x472e6840
KParts::ReadOnlyPart, parentWidget=0x8ecbf18, parent=0x8ecbf18, args=...,
keyword=...) at
/usr/src/debug/kdelibs-4.8.3/kdecore/util/kpluginfactory.cpp:203
#29 0x080502fd in createKParts::ReadOnlyPart (args=optimized out,
parent=optimized out, this=optimized out) at
/usr/include/kde4/kpluginfactory.h:507
#30 Akregator::MainWindow::loadPart (this=0x8ecbf18) at
/usr/src/debug/kdepim-4.8.3/akregator/src/mainwindow.cpp:108
#31 0x0804ebf6 in Akregator::Application::newInstance (this=0xbfa2ccbc) at
/usr/src/debug/kdepim-4.8.3/akregator/src/main.cpp:59
#32 0x4bce8d78 in KUniqueApplicationAdaptor::newInstance (this=0x8fcc410,
asn_id=..., args=...) at
/usr/src/debug/kdelibs-4.8.3/kdeui/kernel/kuniqueapplication.cpp:442
#33 0x4bce8e28 in qt_static_metacall (_a=0xbfa2c2ac, _id=0, _o=0x8fcc410,
_c=optimized out) at
/usr/src/debug/kdelibs-4.8.3/i686-redhat-linux-gnu/kdeui/kuniqueapplication_p.moc:57
#34 KUniqueApplicationAdaptor::qt_static_metacall (_o=0x8fcc410,
_c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfa2c2ac) at
/usr/src/debug/kdelibs-4.8.3/i686-redhat-linux-gnu/kdeui/kuniqueapplication_p.moc:51
#35 0x4bce8f9c in KUniqueApplicationAdaptor::qt_metacall (this=0x8fcc410,
_c=QMetaObject::InvokeMetaMethod, _id=optimized out, _a=0xbfa2c2ac) at
/usr/src/debug/kdelibs-4.8.3/i686-redhat-linux-gnu/kdeui/kuniqueapplication_p.moc:101
#36 0x44b5f618 in QDBusConnectionPrivate::deliverCall (this=0x8ed1c10,

[Bug 295957] New: Kontact crashes...

[Steve]

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

Bug ID: 295957
  Severity: crash
   Version: unspecified
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: Kontact crashes...
Classification: Unclassified
OS: Linux
  Reporter: sbra...@gmail.com
  Hardware: Fedora RPMs
Status: UNCONFIRMED
 Component: general
   Product: kontact

Application: kontact (4.8.0)
KDE Platform Version: 4.8.1 (4.8.1)
Qt Version: 4.8.0
Operating System: Linux 3.2.9-1.fc16.i686 i686
Distribution: Kororaa release 16 (Chum)

-- Information about the crash:
- What I was doing when the application crashed: When opening app it instantly
crashes...click I icon...crash...just recently updated to KDE 4.8.1

The crash can be reproduced every time.

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

Thread 4 (Thread 0xb6b86b40 (LWP 5044)):
#0  0x00d6a416 in __kernel_vsyscall ()
#1  0x42cec85c in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:172
#2  0x482bd9a3 in WTF::TCMalloc_PageHeap::scavengerThread (this=0x489e2fe0) at
../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495
#3  0x482bdac0 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=0x489e2fe0) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618
#4  0x42ce8cd3 in start_thread (arg=0xb6b86b40) at pthread_create.c:309
#5  0x42f59a2e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133

Thread 3 (Thread 0xb625db40 (LWP 5045)):
#0  0x42d4f001 in __GI_clock_gettime (clock_id=1, tp=0xb625cff8) at
../sysdeps/unix/clock_gettime.c:116
#1  0x43aa4e06 in do_gettime (frac=0xb625cff0, sec=0xb625cfe8) at
tools/qelapsedtimer_unix.cpp:123
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#3  0x43b8ebf7 in QTimerInfoList::updateCurrentTime (this=0xb5901abc) at
kernel/qeventdispatcher_unix.cpp:343
#4  0x43b8e84e in timerSourceCheckHelper (src=0xb5901a88) at
kernel/qeventdispatcher_glib.cpp:150
#5  timerSourceCheckHelper (src=0xb5901a88) at
kernel/qeventdispatcher_glib.cpp:144
#6  0x432842ec in g_main_context_check (context=0xb59004e0,
max_priority=2147483647, fds=0xb5900de8, n_fds=1) at gmain.c:2959
#7  0x43284cd0 in g_main_context_iterate (context=0xb59004e0, block=1126774800,
dispatch=1, self=0xb5900d70) at gmain.c:3086
#8  0x4328501f in g_main_context_iteration (context=0xb59004e0, may_block=1) at
gmain.c:3152
#9  0x43b8e317 in QEventDispatcherGlib::processEvents (this=0xb5900468,
flags=...) at kernel/qeventdispatcher_glib.cpp:426
#10 0x43b5a4ee in QEventLoop::processEvents (this=0xb625d230, flags=...) at
kernel/qeventloop.cpp:149
#11 0x43b5a799 in QEventLoop::exec (this=0xb625d230, flags=...) at
kernel/qeventloop.cpp:204
#12 0x43a42b2c in QThread::exec (this=0x93e22f8) at thread/qthread.cpp:501
#13 0x43a42c1c in QThread::run (this=0x93e22f8) at thread/qthread.cpp:568
#14 0x43a460b1 in QThreadPrivate::start (arg=0x93e22f8) at
thread/qthread_unix.cpp:298
#15 0x42ce8cd3 in start_thread (arg=0xb625db40) at pthread_create.c:309
#16 0x42f59a2e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133

Thread 2 (Thread 0xb5203b40 (LWP 5049)):
#0  0x00d6a416 in __kernel_vsyscall ()
#1  0x42cecc04 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_timedwait.S:238
#2  0x43a465b0 in wait (time=3, this=0x9873e70) at
thread/qwaitcondition_unix.cpp:84
#3  QWaitCondition::wait (this=0x9873e18, mutex=0x9873e14, time=3) at
thread/qwaitcondition_unix.cpp:158
#4  0x43a3884c in QThreadPoolThread::run (this=0x987ea70) at
concurrent/qthreadpool.cpp:141
#5  0x43a460b1 in QThreadPrivate::start (arg=0x987ea70) at
thread/qthread_unix.cpp:298
#6  0x42ce8cd3 in start_thread (arg=0xb5203b40) at pthread_create.c:309
#7  0x42f59a2e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133

Thread 1 (Thread 0xb77bb9c0 (LWP 5043)):
[KCrash Handler]
#7  elf_machine_rela_relative (reloc_addr_arg=0x6709a315, l_addr=1704349696,
reloc=optimized out) at ../sysdeps/i386/dl-machine.h:644
#8  elf_dynamic_do_Rela (skip_ifunc=0, nrelative=558093, relsize=6782952,
reladdr=optimized out, map=0x9a337d0, lazy=optimized out) at do-rel.h:121
#9  _dl_relocate_object (scope=0x9a33988, reloc_mode=1, consider_profiling=0)
at dl-reloc.c:265
#10 0x42cca3ab in dl_open_worker (a=0xbfa93590) at dl-open.c:338
#11 0x42cc5d0f in _dl_catch_error (objname=0xbfa935b4, errstring=0xbfa935b8,
mallocedp=0xbfa935bf, operate=0x42cca100 dl_open_worker, args=0xbfa93590) at
dl-error.c:178
#12 0x42cc9d06 in _dl_open (file=0x9a31710
/usr/lib/kde4/akregator_sharemicroblog_plugin.so, mode=-2147483647,
caller_dlopen=0x43b4c913, nsid=-2, argc=1, argv=0xbfa95094, env=0x93af508) at
dl-open.c:575
#13 0x42cdbc09 in dlopen_doit (a=0xbfa93760) at dlopen.c:67
#14 0x42cc5d0f in _dl_catch_error 

[Bug 259949] Kmail does not use all addressbooks for autocompletion

[steve]

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





--- Comment #78 from steve steve kinescope tv  2012-03-02 14:10:11 ---
The bug is severe enough for me to be greatly hindered in using Kmail for my
business, which I've been doing for years now. It is too much to hand select
emails from 1500 clients. So yesterday I wiped my drive and installed Kubuntu
11.10 fresh. I went ahead and let it perform the first set of updates suggested
by the system. I believe this updated from 4.7.3 to 4.7.4. I created a new
personal contact book using akonadi, and populated it with Vcard import in
Kontact. Autocomplete works flawlessly now.

It seems something breaks in either Nepomuk feeder or Akonadi when upgrading to
a new 'decade' of KDE. I am witholding implementing anymore system updates for
now because this is a feature of Kmail I must have. I spent quite a while
searching around for clues and found many people experiencing this bug who have
yet to report it. I consider it a major bug.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- 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

[Bug 259949] Kmail does not use all addressbooks for autocompletion

[steve]

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


steve st...@kinescope.tv changed:

   What|Removed |Added

 CC||st...@kinescope.tv




--- Comment #74 from steve steve kinescope tv  2012-03-01 22:28:59 ---
Same problem here. I've tried everything and I can't make it happen.

Kubuntu 11.10 KDE 4.8

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- 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