[kmail2] [Bug 393421] No ability to hide the HTML Message Status Bar

2019-02-05 Thread PK
https://bugs.kde.org/show_bug.cgi?id=393421

--- Comment #54 from PK  ---
What starts to puzzle me about this whole discussion is that no one ever took
the trouble of explaining why this bar had to be fixed. Why so many faithful
users had to be "kicked against the sore leg" as we say in my country.
It seems to me that there must be a really simple and good explanation to take
a measure that harsh that also ruins the looks of your application.
What is this reason? Please explain.

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

[Akonadi] [Bug 403982] EWS gets stuck in "Retrieving collection tree"

2019-02-05 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=403982

--- Comment #1 from Aaron Williams  ---
I stopped Akonadi and started it from the Alonadi console. The job tracker says
Akonadi::CollectionFetchJob failed at CollectionRemoteId INBOX. The resource
scheduler shows it waiting on SyncTags.

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

[Akonadi] [Bug 403982] New: EWS gets stuck in "Retrieving collection tree"

2019-02-05 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=403982

Bug ID: 403982
   Summary: EWS gets stuck in "Retrieving collection tree"
   Product: Akonadi
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: EWS Resource
  Assignee: kdepim-bugs@kde.org
  Reporter: aar...@doofus.org
CC: kri...@op.pl
  Target Milestone: ---

SUMMARY
I have run into an issue where every time I try and retrieve email from an
Office 365 email account using EWS it hangs at "Retrieving collection tree".

I have restarted the EWS resource, akonadi and kontact multiple times to no
avail.

In the logging I see it is able to fetch all of the emails, but none get
displayed, presumably because it is stuck retrieving the collection tree.

STEPS TO REPRODUCE
1. Configure an EWS account with a lot of email in it
2. Try and synchronize to that account
3. Watch it get stuck at "Retrieving collection tree"

OBSERVED RESULT
It gets stuck retrieving the collection tree. I do not see any messages in
the log indicating why it is stuck (or where for that matter).

EXPECTED RESULT
I expect it to complete

SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: OpenSUSE 15.0 with latest KDE (18.12.1)
(available in About System)
KDE Plasma Version: 5.14.90
KDE Frameworks Version: 5.54.0
Qt Version: 5.12.0

ADDITIONAL INFORMATION
I tried to abort but abort doesn't seem to work either.

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

[Akonadi] [Bug 403903] org.kde.pim.ews.client: a:ErrorServerBusy: The server cannot service this request right now. Try again later.

2019-02-05 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=403903

--- Comment #1 from Aaron Williams  ---
When the server responds with this error it also specifies how long the client
should wait in milliseconds. It would be nice if Akonadi would respect that.

org.kde.pim.ews.client.proto: data KIO::TransferJob(0x55602c039970) "http://schemas.xmlsoap.org/soap/envelope/\;>http://schemas.microsoft.com/exchange/services/2006/types\;>a:ErrorServerBusyThe server cannot service this request right now. Try again
later.http://schemas.microsoft.com/exchange/services/2006/errors\;>ErrorServerBusyhttp://schemas.microsoft.com/exchange/services/2006/errors\;>The
server cannot service this request right now. Try again
later.http://schemas.microsoft.com/exchange/services/2006/types\;>213631"
org.kde.pim.ews.client.proto: data KIO::TransferJob(0x55602c039970) ""
org.kde.pim.ews.client.proto: response dumped to
"/tmp/akonadi-ews-RLygWvy/ews_xmldump_ppzpkKi.xml"
org.kde.pim.ews.client: a:ErrorServerBusy: The server cannot service this
request right now. Try again later.
org.kde.pim.ews.client: request  dumped to
"/tmp/akonadi-ews-RLygWvy/ews_xmlreqdump_EgwgskN.xml"
org.kde.pim.ews.client: response dumped to
"/tmp/akonadi-ews-RLygWvy/ews_xmlresdump_PtFspvg.xml"
org.kde.pim.ews.client.request: Starting GetStreamingEvents request (subId:
1melsjw, timeout: 30)
org.kde.pim.ews.client.proto: "http://schemas.xmlsoap.org/soap/envelope/\;
xmlns:m=\"http://schemas.microsoft.com/exchange/services/2006/messages\;
xmlns:t=\"http://schemas.microsoft.com/exchange/services/2006/types\;>JwBieWFwcjE4bWIyNDQwLm5hbXByZDE4LnByb2Qub3V0bG9vay5jb20Q/PV94Xu0Dk6xhatkt3i44Q3WO9vei9YIEKStBHVI/VtOowPZCRt0Buc=30\n"
org.kde.pim.ews.client.proto: data KIO::TransferJob(0x556024f3d4a0) "http://schemas.xmlsoap.org/soap/envelope/\;>http://schemas.microsoft.com/exchange/services/2006/types\;>a:ErrorServerBusyThe server cannot service this request right now. Try again
later.http://schemas.microsoft.com/exchange/services/2006/errors\;>ErrorServerBusyhttp://schemas.microsoft.com/exchange/services/2006/errors\;>The
server cannot service this request right now. Try again
later.http://schemas.microsoft.com/exchange/services/2006/types\;>213564"
org.kde.pim.ews.client.proto: data KIO::TransferJob(0x556024f3d4a0) ""
org.kde.pim.ews.client.proto: response dumped to
"/tmp/akonadi-ews-RLygWvy/ews_xmldump_fCPJiiC.xml"
org.kde.pim.ews.client: a:ErrorServerBusy: The server cannot service this
request right now. Try again later.
org.kde.pim.ews.client: request  dumped to
"/tmp/akonadi-ews-RLygWvy/ews_xmlreqdump_wRuZnVK.xml"
org.kde.pim.ews.client: response dumped to
"/tmp/akonadi-ews-RLygWvy/ews_xmlresdump_jBIqQPU.xml"
org.kde.pim.ews.client.request: Starting GetStreamingEvents request (subId:
1melsjw, timeout: 30)
org.kde.pim.ews.client.proto: "http://schemas.xmlsoap.org/soap/envelope/\;
xmlns:m=\"http://schemas.microsoft.com/exchange/services/2006/messages\;
xmlns:t=\"http://schemas.microsoft.com/exchange/services/2006/types\;>

[Akonadi] [Bug 403981] New: EWS resource needs to be able to specify identity to use

2019-02-05 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=403981

Bug ID: 403981
   Summary: EWS resource needs to be able to specify identity to
use
   Product: Akonadi
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: EWS Resource
  Assignee: kdepim-bugs@kde.org
  Reporter: aar...@doofus.org
CC: kri...@op.pl
  Target Milestone: ---

SUMMARY
I have several email accounts, one for home (IMAP) and one for work (EWS).
While I can specify which identity to use for IMAP, I am unable to specify
which identity to use for EWS so it uses the default. This requires that I
set my default identity to my work identity.

STEPS TO REPRODUCE
1. Open Microsoft Exchange Configuration
2. Look through the tabs
3. Notice that there is no way to specify which identity to use

OBSERVED RESULT


EXPECTED RESULT
In the IMAP configuration in the advanced tab I am able to specify
which identity should be used.  EWS needs this same configuration.

SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: 5.14.90
(available in About System)
KDE Plasma Version: 5.14.90
KDE Frameworks Version: 18.12.1
Qt Version: 5.12.1

ADDITIONAL INFORMATION

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

[kmail2] [Bug 403976] New: Message viewer: Lines starting with | (pipe symbol) incorrectly shown as quoted lines

2019-02-05 Thread David Hurka
https://bugs.kde.org/show_bug.cgi?id=403976

Bug ID: 403976
   Summary: Message viewer: Lines starting with | (pipe symbol)
incorrectly shown as quoted lines
   Product: kmail2
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: UI
  Assignee: kdepim-bugs@kde.org
  Reporter: david.hu...@mailbox.org
  Target Milestone: ---

Created attachment 117849
  --> https://bugs.kde.org/attachment.cgi?id=117849=edit
Example for a messed up table in kmail2

SUMMARY
Lines starting with | after much whitespace are displayed as quote, although
they should not be. This messes up tables.

STEPS TO REPRODUCE
1. Take a typical Bugzilla CC added message, or create a message like:
   What|Removed |Added

 CC||some...@kde.org
   ||someone.e...@kde.org

2. Open it in message viewer

OBSERVED RESULT
Because the last line starts with | (after some whitespace), it is shown as
quote:
   What|Removed |Added

 CC||some...@kde.org
||someone.e...@kde.org

EXPECTED RESULT
To avoid this, do not recognize quoting signs after more than, say, 5 spaces;
or do not remove whitespace from quotes.

It is not a big problem for me if the whitespace is removed when replying to
the message. (Might be a problem for the recipient, though.)

SOFTWARE/OS VERSIONS
KMail Version: 5.10.1
KDE Neon 5.14
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.2

ADDITIONAL QUESTION
I thought I could change which symbols are recognized as quote. Where?

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

[kmail2] [Bug 403976] Message viewer: Lines starting with | (pipe symbol) incorrectly shown as quoted lines

2019-02-05 Thread David Hurka
https://bugs.kde.org/show_bug.cgi?id=403976

David Hurka  changed:

   What|Removed |Added

 CC||david.hu...@mailbox.org

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

[korganizer] [Bug 403968] New: Deleting one of a repeating event from Google Calendar deletes all Korganiser events in that series.

2019-02-05 Thread John Carrick Smith
https://bugs.kde.org/show_bug.cgi?id=403968

Bug ID: 403968
   Summary: Deleting one of a repeating event from Google Calendar
deletes all Korganiser events in that series.
   Product: korganizer
   Version: 5.7.3
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: recurrence
  Assignee: kdepim-bugs@kde.org
  Reporter: jcarricksm...@gmail.com
  Target Milestone: ---

SUMMARY

I have Korganizer synchronised with my Android 'phone using the Google Calendar
app.

If I create an event in Korganizer with recurrences and then delete one event
(in the middle of the series) from Google Calendar on my Android 'phone the
whole series in deleted from Korganizer.

STEPS TO REPRODUCE
1. Synchronise Korganizer with a Google Calendar using the standard KDE
feature.
2. Create a weekly repeating series with 11 entries using the Korganizer Add
Event option and adding the repeating information.
3. Delete an arbitrary entry from the series using Google Calendar on an
Android 'phone, using the delete this entry only option.

OBSERVED RESULT
All events in the series created in step 1. are removed from Korganizer.

EXPECTED RESULT
only the event deleted via the Google Calendar app should be deleted.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSuse 15.0 
(available in About System)
KDE Plasma Version: 5.12.6
KDE PIM: 17.12.3
KDE Frameworks Version: 5.45.0
Qt Version: 5.9.4

Android: 6.0.1

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

[kmail2] [Bug 403963] New: KMail SIGSEGV when opening one of my folders

2019-02-05 Thread Allen Winter
https://bugs.kde.org/show_bug.cgi?id=403963

Bug ID: 403963
   Summary: KMail SIGSEGV when opening one of my folders
   Product: kmail2
   Version: Git (master)
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: folders
  Assignee: kdepim-bugs@kde.org
  Reporter: win...@kde.org
  Target Milestone: ---

This is version 5.10.2 (or the current stable branch)

SUMMARY
I get a SIGSEGV whenever I enter one of my subfolders.

STEPS TO REPRODUCE
1. select the subfolder
2. 
3. 

OBSERVED RESULT
crash

EXPECTED RESULT
no crash



SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[kmail2] [Bug 403963] KMail SIGSEGV when opening one of my folders

2019-02-05 Thread Allen Winter
https://bugs.kde.org/show_bug.cgi?id=403963

Allen Winter  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |LATER

--- Comment #1 from Allen Winter  ---
nevermind.
this is an infinite recursion that I ran into and tried to fix myself.  I found
a hack but not the real problem.  I don't think it happens in master, or if it
did , I never noticed it.


#3  0x7fd942a3ed58 in
QList::append(MessageList::Core::MessageItem*
const&) (this=0x7ffdbfc784a0, t=@0x7ffdbf47a0d0: 0x114a17b0) at
/usr/include/qt5/QtCore/qlist.h:581
#4  0x7fd942a3c151 in
MessageList::Core::MessageItem::subTreeToList(QList&)
(this=0x114a17b0, list=...) at
/data/kde/src/5/kde/pim/messagelib/messagelist/src/core/messageitem.cpp:587
#5  0x7fd942a3c208 in
MessageList::Core::MessageItem::subTreeToList(QList&)
(this=0x114adaa0, list=...) at
/data/kde/src/5/kde/pim/messagelib/messagelist/src/core/messageitem.cpp:594
#6  0x7fd942a3c208 in
MessageList::Core::MessageItem::subTreeToList(QList&)
(this=0x114a17b0, list=...) at
/data/kde/src/5/kde/pim/messagelib/messagelist/src/core/messageitem.cpp:594
#7  0x7fd942a3c208 in
MessageList::Core::MessageItem::subTreeToList(QList&)
(this=0x114adaa0, list=...) at
/data/kde/src/5/kde/pim/messagelib/messagelist/src/core/messageitem.cpp:594
#8  0x7fd942a3c208 in
MessageList::Core::MessageItem::subTreeToList(QList&)
(this=0x114a17b0, list=...) at
/data/kde/src/5/kde/pim/messagelib/messagelist/src/core/messageitem.cpp:594
#9  0x7fd942a3c208 in
MessageList::Core::MessageItem::subTreeToList(QList&)
(this=0x114adaa0, list=...) at
/data/kde/src/5/kde/pim/messagelib/messagelist/src/core/messageitem.cpp:594
#10 0x7fd942a3c208 in
MessageList::Core::MessageItem::subTreeToList(QList&)
(this=0x114a17b0, list=...) at
/data/kde/src/5/kde/pim/messagelib/messagelist/src/core/messageitem.cpp:594
#11 0x7fd942a3c208 in
MessageList::Core::MessageItem::subTreeToList(QList&)
(this=0x114adaa0, list=...) at
/data/kde/src/5/kde/pim/messagelib/messagelist/src/core/messageitem.cpp:594
#12 0x7fd942a3c208 in
MessageList::Core::MessageItem::subTreeToList(QList&)
(this=0x114a17b0, list=...) at
/data/kde/src/5/kde/pim/messagelib/messagelist/src/core/messageitem.cpp:594
#13 0x7fd942a3c208 in
MessageList::Core::MessageItem::subTreeToList(QList&)
(this=0x114adaa0, list=...) at
/data/kde/src/5/kde/pim/messagelib/messagelist/src/core/messageitem.cpp:594

forever

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

[Akonadi] [Bug 402229] Sqlite backend error with schema update 36 & 37 (5.10.0)

2019-02-05 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=402229

--- Comment #4 from Christophe Giboudeaux  ---
Please submit your patch using phabricator.kde.org.

You can find information here:
https://community.kde.org/Infrastructure/Phabricator

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

[kmail2] [Bug 403958] New: Add Reminders to Invitations without Reminders

2019-02-05 Thread Allen Winter
https://bugs.kde.org/show_bug.cgi?id=403958

Bug ID: 403958
   Summary: Add Reminders to Invitations without Reminders
   Product: kmail2
   Version: Git (master)
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: misc
  Assignee: kdepim-bugs@kde.org
  Reporter: win...@kde.org
  Target Milestone: ---

SUMMARY
Sometimes I receive an invitation that doesn't have a reminder.  So even if I
accept the invitation I might not remember.  I have KOrganizer configured to
add reminders to all new events.  

This wish is to follow the KOrganizer configuration for adding a reminder to
accepted invitations

STEPS TO REPRODUCE
1. receive invitation without a reminder
2. accept invitation
3. 

OBSERVED RESULT
notice that the corresponding event in KOrganizer does not have a reminder

EXPECTED RESULT
the corresponding event should follow the KOrganizer configuration for adding a
reminder to all new events

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 28
(available in About System)
KDE Plasma Version: 5.13.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3

ADDITIONAL INFORMATION

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

[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"

2019-02-05 Thread Matthias Kretz
https://bugs.kde.org/show_bug.cgi?id=338658

--- Comment #127 from Matthias Kretz  ---
The fact that I can have an inconsistent state stored in my Akonadi DB is
telling. Apparently, while clients interact with Akonadi, the DB goes through
inconsistent states. Those appear to be open to races, and unfortunate
interrupts (crash, system hang, power loss).

What I'd do (and I'm guessing from a far away distance in the hopes it helps
inspire a real fix, hoping not to step on any toes):

1. Update the DB schema to enforce consistent state. In particular all foreign
keys need to be defined so that it's impossible to DELETE FROM parttable while
something in pimitemtable still holds a key to it.

2. Presumably this will break clients which rely on the DB to allow
inconsistent intermediate states. DB updates therefore need to be fixed to
atomically go from one consistent state to the next. E.g. use DELETE together
with INNER JOIN.

3. Races like "unread -> read -> unread" need to be guarded against via
compare-exchange atomic operations using some modification counter. E.g.
mailcheck create id=X, state=unread
kmail read id=X, state=unread
kmail write state=read WHERE id=X
mailcheck update id=X, state=unread (why would this happen anyway, can the IMAP
server indicate some update of metadata?)

If we add a version the UPDATE could be predicated on the version column still
storing the same value as when it was SELECTED before. E.g. the mail client
does
`UPDATE foo SET state=read WHERE id=X AND version=1` instead of `UPDATE foo SET
state=read WHERE id=X`. I actually expect Akonadi already has such a facility
and Allans guess is incorrect.

I have another guess from looking at my logs. I have lots of:

org.kde.pim.akonadiserver:   DB error:  "Lock wait timeout exceeded; try
restarting transaction"
org.kde.pim.akonadiserver:   Error text: "Lock wait timeout exceeded; try
restarting transaction QMYSQL3: Unable to execute statement"

I.e. KMail updates the UI to read state, tries to reflect the state change with
Akonadi, but the DB is locked up. The UPDATE fails, and the KMail UI reverts to
the state stored in Akonadi.

These locks might also be the reason why inconsistent entries in tables remain.
A first DELETE goes through, the second (to make it consistent again) times
out.

I have no clue where the locks come from though. One data point: After my
DELETE FROM statement above I've not seen a single DB error message about lock
timeouts again. Before I had lots.

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

[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"

2019-02-05 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=338658

--- Comment #126 from Boudewijn Rempt  ---
That sounds very likely -- I see the read-unread flip all the time as well.

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

[Akonadi] [Bug 402229] Sqlite backend error with schema update 36 & 37 (5.10.0)

2019-02-05 Thread Konrad Rzepecki
https://bugs.kde.org/show_bug.cgi?id=402229

--- Comment #3 from Konrad Rzepecki  ---
Created attachment 117837
  --> https://bugs.kde.org/attachment.cgi?id=117837=edit
Patch witch PRAGMA changes suggested by Maël

I've attached patch with PRAGMA changes suggested by Maël. "PRAGMA
foreign_key_check=OFF" is definitely wrong syntax according SQLite
documentation. I have no idea if "PRAGMA defer_foreign_keys=ON" is a correct
replacement, but as Maël wrote, it works.

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

[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"

2019-02-05 Thread Allan Sandfeld
https://bugs.kde.org/show_bug.cgi?id=338658

--- Comment #125 from Allan Sandfeld  ---
Btw. I believe the underlying cause is the same that causes emails you are
currently reading to be marked unread again while you are reading it. A sync is
often started in parallel with other actions, so for instance you click on a
folder it starts syncing, and you are reading an email and it is marked read.
You mark it read, but the sync then marks it unread (race condition). 

The same can happen when moving emails, it might be moved, only to be recreated
by the parallel sync, and then moved again, causing two exact copies to exist
in the target folder.

The transactional atomicy of Akonadi is somewhat questionable with several jobs
that consists of multiple database transactions, or is combined with syncing
remote servers.

I tried looking at the move job, but it is pretty messy.

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

[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"

2019-02-05 Thread Allan Sandfeld
https://bugs.kde.org/show_bug.cgi?id=338658

--- Comment #124 from Allan Sandfeld  ---
(In reply to Matthias Kretz from comment #123)
> (In reply to Allan Sandfeld from comment #122)
> > With my patch in place the duplicates can be removed by simply calling
> > "remove duplicates" from KMail.
> 
> "Folder -> Remove Duplicates"? If that removes stales in the pimitemtable
> it's somewhat misleadingly named. I was expecting it to search for copies of
> the same mail (i.e. different local & remote ID but equal payload data).

It is not what it is supposed to do, but those exact copies of a single remote
entry also match as if they are just normal copies of the same email.

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

[kmail2] [Bug 393421] No ability to hide the HTML Message Status Bar

2019-02-05 Thread Konrad Rzepecki
https://bugs.kde.org/show_bug.cgi?id=393421

Konrad Rzepecki  changed:

   What|Removed |Added

 CC||hanni...@astral.lodz.pl

--- Comment #53 from Konrad Rzepecki  ---
I just begin to test KDE5/Plasma, and I definitely want to have option to
remove this crappy bar!!!

I have problem with enable message structure which you also want to remove. In
bug 387931 you restore that functionality in expert plugin. Option to hide this
THING can be also put there - since message structure also can be used to
change html/text parts.

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

[kmail2] [Bug 399245] Restore UI functionality related to "Show HTML side bar"

2019-02-05 Thread Konrad Rzepecki
https://bugs.kde.org/show_bug.cgi?id=399245

Konrad Rzepecki  changed:

   What|Removed |Added

 CC||hanni...@astral.lodz.pl

--- Comment #10 from Konrad Rzepecki  ---
I just begin to test KDE5/Plasma, and I definitely want to have option to
remove this crappy bar!!!

I have problem with enable message structure which you also want to remove. In
bug 387931 you restore that functionality in expert plugin. Option to hide this
THING can be also put there - since message structure also can be used to
change html/text parts.

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

[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"

2019-02-05 Thread Matthias Kretz
https://bugs.kde.org/show_bug.cgi?id=338658

--- Comment #123 from Matthias Kretz  ---
(In reply to Allan Sandfeld from comment #122)
> With my patch in place the duplicates can be removed by simply calling
> "remove duplicates" from KMail.

"Folder -> Remove Duplicates"? If that removes stales in the pimitemtable it's
somewhat misleadingly named. I was expecting it to search for copies of the
same mail (i.e. different local & remote ID but equal payload data).

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

[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"

2019-02-05 Thread Allan Sandfeld
https://bugs.kde.org/show_bug.cgi?id=338658

--- Comment #122 from Allan Sandfeld  ---
With my patch in place the duplicates can be removed by simply calling "remove
duplicates" from KMail.

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

[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"

2019-02-05 Thread Matthias Kretz
https://bugs.kde.org/show_bug.cgi?id=338658

Matthias Kretz  changed:

   What|Removed |Added

 CC||kr...@kde.org

--- Comment #121 from Matthias Kretz  ---
I'm fed up with wiping my Akonadi data every other month so I'm trying to once
again to understand the cause or find a workaround.

Anyway, I was following the SQL hints on debugging the state of my Akonadi data
and found three instances of duplicated (well, rather "multiplicated")
pimitemtable.remoteIds, on the order of hundreds of different pimitemtable.ids.
I then tried to find the corresponding data in parttable via INNER JOIN
parttable ON pimitemtable.id = parttable.pimItemId. Interestingly enough
there's a single pimitemtable.id per pimitemtable.remoteId left (with three
different parttable.id per pimitemtable.id, which seems to be correct for
normal entries). So it seems there are stale entries in pimitemtable. The query

SELECT pimitemtable.*, collectiontable.name FROM pimitemtable
INNER JOIN collectiontable ON pimitemtable.collectionId = collectiontable.id
LEFT JOIN parttable ON pimitemtable.id = parttable.pimItemId
WHERE parttable.id IS NULL

lists the same remoteIds that the query looking for dups found, minus the ones
that have a match in parttable. Useful information: there are no additional
stale entries in pimitemtable than the dups.

Next step, I tried to remove the stale entries in pimitemtable with the
following query:

DELETE pimitemtable FROM pimitemtable
LEFT JOIN parttable ON pimitemtable.id = parttable.pimItemId
WHERE parttable.id IS NULL

However, the query hangs akonadiconsole for ~1 minute and then returns "Lock
wait timeout exceeded; try restarting transaction QMYSQL: Unable to execute
query". An `akonadictl restart` in this case did the trick and the query then
got through. All dups gone. In any case the hangs on reading mails in KMail
that I experienced since yesterday are gone. Let's see whether it helps.

Maybe the DELETE query is a useful addition to `akonadictl fsck` until the root
cause can be fixed?

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