[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails

2018-01-29 Thread Kamil Dudka
https://bugs.kde.org/show_bug.cgi?id=377521

--- Comment #18 from Kamil Dudka  ---
(In reply to Christoph Feck from comment #17)
> but the systray number display had
> several issues, including, but not limited to, color readability and HiDPI
> scaling.

See comment #10.  Attachment #109488 works perfectly for me.  If somebody has
issues with that feature, nobody forces him/her to have it enabled.  AFAIK it
has always been optional.

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

2018-01-29 Thread Andrius Štikonas
https://bugs.kde.org/show_bug.cgi?id=381929

--- Comment #19 from Andrius Štikonas  ---
(In reply to Christoph Feck from comment #18)
> Did anyone else see feedlist corruption with the 17.12.x release (Akregator
> version 5.7.x)?

Yes, I have it too on 17.12.1 with Qt 5.9.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

2018-01-29 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=381929

--- Comment #18 from Christoph Feck  ---
Did anyone else see feedlist corruption with the 17.12.x release (Akregator
version 5.7.x)?

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

[korganizer] [Bug 388302] Non-recurring all-day to-dos show up on wrong due date in agenda view

2018-01-29 Thread Boian Berberov
https://bugs.kde.org/show_bug.cgi?id=388302

Boian Berberov  changed:

   What|Removed |Added

Version|5.7.0   |5.7.1

--- Comment #2 from Boian Berberov  ---
Update for 5.7.1

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

[akregator] [Bug 377485] regression: system tray icon no longer shows number of unread articles

2018-01-29 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=377485

Christoph Feck  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=377521

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

[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails

2018-01-29 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=377521

Christoph Feck  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=377485

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

[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails

2018-01-29 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=377521

--- Comment #17 from Christoph Feck  ---
According to https://phabricator.kde.org/D9841 Plasma developers contributed a
'unread email count' to the KMail launcher icon when pinned to taskbar. This
isn't a complete replacement, but the systray number display had several
issues, including, but not limited to, color readability and HiDPI scaling.

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

[Akonadi] [Bug 388029] Checking "Show week numbers in Calander" made Plasma crash

2018-01-29 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=388029

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #2 from Christoph Feck  ---


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

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

[Akonadi] [Bug 376220] Crash in Akonadi::Monitor::mimeTypesMonitored

2018-01-29 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=376220

Christoph Feck  changed:

   What|Removed |Added

 CC||ole.reier.ull...@gmail.com

--- Comment #25 from Christoph Feck  ---
*** Bug 388029 has been marked as a duplicate of this bug. ***

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

[Akonadi] [Bug 389609] akonadictl fsck: optional show metadata for affected items to aid user to fix up things manually

2018-01-29 Thread Martin Steigerwald
https://bugs.kde.org/show_bug.cgi?id=389609

Martin Steigerwald  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Martin Steigerwald  ---
Okay, Dan. Considering your comment I think it is not beneficial to keep this
bug report open. akonadictl fsck appears to be a developer tool and maybe users
should not even use it. That leaves that Akonadi shall be able to fix up
inconsistencies by itself, or avoid creating inconsistencies in the first place
by using atomic operations and roll-back but that is for other bug reports.

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

[Akonadi] [Bug 389608] akonadictl fsck: offer to fix duplicate items

2018-01-29 Thread Martin Steigerwald
https://bugs.kde.org/show_bug.cgi?id=389608

--- Comment #4 from Martin Steigerwald  ---
Ok, so I completely misunderstood your explanation on the mailing list.
However, akonadictl fsck reports an issue, it cannot do anything about it, the
user can´t either. So what is the point? How how do these duplicates happen? I
do think there is something to fix here as the current situation is not
suitable to make the ordinary user. In the end for the user it is still just a
mail program, a calender application or an address book. And it has an fsck… I
am pretty sure I could not really explain this to my father easily.

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

[Akonadi] [Bug 389607] akonadictl fsck: Show more helpful messages

2018-01-29 Thread Martin Steigerwald
https://bugs.kde.org/show_bug.cgi?id=389607

--- Comment #3 from Martin Steigerwald  ---
Thank you Dan, for your prompt responses. So I still misunderstood some of the
error messages despite your explainations. I think this hints and the
underlying issue: there is an akonadictl fsck, it often does not really fix the
issue the user sees, yet it reports some kind of probable inconsistencies and
leaves the user without anything sensible to do about… So I wonder about the
purpose of it? Aside from the migration work it does, is it a developer tool?
Whatever, no need to discuss it here. I reported what I think I understood from
your answer on the mailing list. If there are different actions to be taken
than the ones I suggest, feel free to close some of the reports I made. I just
wanted to help to move this forward.

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

[Akonadi] [Bug 389609] akonadictl fsck: optional show metadata for affected items to aid user to fix up things manually

2018-01-29 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=389609

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org

--- Comment #2 from Daniel Vrátil  ---
This would be a major effort and something that's not easily achievable with
the current architecture.

"akonadictl fsck" is a service inside the akonadiserver and therefore it has no
knowledge about the payload format - IOW it does not understand "MIME" or
"iCal" or "vCard" formats, it simply sees the payload as a binary blob.

At the same time, this tool cannot be easily re-implemented outside of the
akonadiserver (so that it would be able to understand payload formats)  because
it directly interacts with the SQL database, which cannot be safely done from
outside of the akonadiserver process.

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

[Akonadi] [Bug 389608] akonadictl fsck: offer to fix duplicate items

2018-01-29 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=389608

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org

--- Comment #3 from Daniel Vrátil  ---
See my comment on bug 389607. The "duplicates" refer to Remote IDs in the
database (which in case of maildir happen to be filenames), not to actual
messages in the backend.

If the situation happens that there are two records in the Akonadi database
that have identical RID, the only case when we could automatically delete one
or the other would be if we could be sure that both records are absolutely
identical (not just in the metadata but also in the payload). In most
situations I've seen there actually was a difference between the items with the
same RID and in that case, which one to keep?

I'll keep this opened for the "Should fix it" part, but note that most of what
you describe below is wrong (based on wrong assumption of what the message
implies - which goes back to bug 389607 of course :-)

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

[Akonadi] [Bug 389607] akonadictl fsck: Show more helpful messages

2018-01-29 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=389607

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org

--- Comment #2 from Daniel Vrátil  ---
> Of course, even better would be if akonadictl fsck could fix the issues it 
> finds.

Yes, but not everything is an issue.

> Some suggestions to improve the situation:
> Item "1289323" has no RID. =>
>
> Item "1289323" only stored in database, not locally in XYZ resource.
>
> XYZ should be the name of the affected resource.

There are two problems:
1) The item can be owned by an online Resource (e.g. IMAP) and the Item may
have no RID simply because the Resource wasn't online yet. In such case the
situation above is not an error.

2) Your message is not precise. "locally in XYZ resource" is wrong, again in
case of online resource. I don't want fsck to contain misguiding messages. In
its own way, the current message (Item has no RID) is perfect, because
describes the situation perfectly. I think the best way would be to just add a
link to Wiki where the issue is described in detail.

> Item "1360766" has RID and is dirty. =>
> 
> Item "1360766" has changes that are only stored in the database, not locally 
> in XYZ resource

Again, the case can simply be because the change couldn't be replayed by an
online Resource yet because it's offline. Same solution as above would apply.

> => Exactly tell which files are identically to give the user the chance to 
> remove duplicate files. It is not obvious from the above:

The "duplicate" refers to duplicate RID, meaning there are multiple Items
stored in the database that belong to the same Collection and have the same
RID. That in no way implies there's a duplicate in the backing storage (maildir
or IMAP) and in most cases there's not even any actual file to refer to (e.g.
IMAP).

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

[Akonadi] [Bug 389606] akonadictl fsck: do not show missing RID warning for search and invitation folders

2018-01-29 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=389606

Daniel Vrátil  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||dvra...@kde.org
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Daniel Vrátil  ---
To generalize, this check should simply ignore all collections belonging to a
virtual resource as those don't have RID by definition.

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

[Akonadi] [Bug 389609] akonadictl fsck: optional show metadata for affected items to aid user to fix up things manually

2018-01-29 Thread Martin Steigerwald
https://bugs.kde.org/show_bug.cgi?id=389609

--- Comment #1 from Martin Steigerwald  ---
This should be optional for privacy reasons. (i.e. when sharing with other
users or in a bug report for help).

Metadata for mail probably should include Message-Id.

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

[Akonadi] [Bug 389609] New: akonadictl fsck: optional show metadata for affected items to aid user to fix up things manually

2018-01-29 Thread Martin Steigerwald
https://bugs.kde.org/show_bug.cgi?id=389609

Bug ID: 389609
   Summary: akonadictl fsck: optional show metadata for affected
items to aid user to fix up things manually
   Product: Akonadi
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: mar...@lichtvoll.de
  Target Milestone: ---

Akonadi 17.08.3

Ideally akonadictl fsck would fix up:

Bug 309474 - akonadictl fsck : item has no RID

Bug 389608 - akonadictl fsck: offer to fix duplicate items 

and other issues with Akonadi cache automatically.

Even better would be that Akonadi would avoid most of these issues the best it
can.

But until getting there, in addition to have more helpful error messages (Bug
389607 - akonadictl fsck: Show more helpful messages) it would be good if
akonadictl fsck would optionally show some metadata about the affected items.

Like in

akonadictl fsck --show-meta-data

and then displaying:

>From / Subject / local maildir file (if known) for mails and so on.

Similar for other types.

Of course it would be better to automatically or at least interactively (by
asking the user) fix up things so if you intend to go that route, feel free to
close this one as WONTFIX. Or to avoid these issues from happening.

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

[Akonadi] [Bug 360834] no mechanism to reattempt to store items without rid (just in db) into the resource

2018-01-29 Thread Martin Steigerwald
https://bugs.kde.org/show_bug.cgi?id=360834

--- Comment #9 from Martin Steigerwald  ---
Also see:

akonadictl fsck: What messages indicate real issues and what to do about them?
https://marc.info/?l=kdepim-users&m=149426877926602&w=2

(I am about to reply to this thread with a further message with references to
further bug reports and further information.)

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

[Akonadi] [Bug 309474] akonadictl fsck : item has no RID

2018-01-29 Thread Martin Steigerwald
https://bugs.kde.org/show_bug.cgi?id=309474

Martin Steigerwald  changed:

   What|Removed |Added

 CC||mar...@lichtvoll.de

--- Comment #4 from Martin Steigerwald  ---
Confirmed with Akonadi 17.08.3.

Please see

Bug 360834 - no mechanism to reattempt to store items without rid (just in db)
into the resource

and the thread

akonadictl fsck: What messages indicate real issues and what to do about them?
https://marc.info/?l=kdepim-users&m=149426877926602&w=2

(I am about to reply to this thread with a mail with more findings and more
references to bugs report about akonadictl fsck I newly created.)

for the best information on these messages I got so far.

So far I am not aware of any fix, so you could only attempt to fix it up
manually. Which for me is no viable option considering that I have >3000 of
these messages with a local maildir resource.

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

[Akonadi] [Bug 389608] akonadictl fsck: offer to fix duplicate items

2018-01-29 Thread Martin Steigerwald
https://bugs.kde.org/show_bug.cgi?id=389608

--- Comment #2 from Martin Steigerwald  ---
Some test with the other files showed that files with the same SHA512 sum
appear only once in the folder

~/.local/share/local-mail/.Lichtvoll.directory/.Debian.directory/qt-kde-ml>
sha512sum */* | grep
7eb122521a7e154bfc7752f3487c965926471c51f22bb76932ff0177976acf89d78e4e91e06ad30db99f248cf56937c168c266b8b7ec9880c32c7d10572abfa3
7eb122521a7e154bfc7752f3487c965926471c51f22bb76932ff0177976acf89d78e4e91e06ad30db99f248cf56937c168c266b8b7ec9880c32c7d10572abfa3
 new/1435499291.R292.merkaba

~/.local/share/local-mail/.Lichtvoll.directory/.Debian.directory/qt-kde-ml>
sha512sum */* | grep
f48518033c959d7a17eb6ef452b93f226a2f9409ae3300d0826cda6ac33116ad9524c43d8b8a59a16d35f89d7a2981eb440f8ddcb8be9ef50b0ba91d45281bc1
f48518033c959d7a17eb6ef452b93f226a2f9409ae3300d0826cda6ac33116ad9524c43d8b8a59a16d35f89d7a2981eb440f8ddcb8be9ef50b0ba91d45281bc1
 new/1435497488.R146.merkaba

But also by Message-Id the appear only once:

~/.local/share/local-mail/.Lichtvoll.directory/.Debian.directory/qt-kde-ml>
fgrep "" */*
new/1435497488.R146.merkaba:Message-Id: 

Its for sure that an ordinary user would usually not go as far in order to fix
up issues, but now I give up as well. I honestly have no idea what to do about
these "duplicates" messages.

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

[Akonadi] [Bug 389608] akonadictl fsck: offer to fix duplicate items

2018-01-29 Thread Martin Steigerwald
https://bugs.kde.org/show_bug.cgi?id=389608

--- Comment #1 from Martin Steigerwald  ---
Nope: BTRFS is fine. It just appears that Akonadi sees the same file mutiple
times:

~/.local/share/local-mail/.Lichtvoll.directory/.Debian.directory/qt-kde-ml/new>
ls -l 1424455081.R806.merkaba*
-rw-r--r-- 1 martin martin 4175 Feb 20  2015 1424455081.R806.merkaba


~/.local/share/local-mail/.Lichtvoll.directory/.Debian.directory/qt-kde-ml/new#130>
sha512sum * | grep
bcd41316ed95949d8c211c38df21f818687d568c408db53bcaee9d70798c09c0408bb64bdd0286bad2bf798efe7af15568ada43b3dcf8ab2907a9d19feb7bb3d

bcd41316ed95949d8c211c38df21f818687d568c408db53bcaee9d70798c09c0408bb64bdd0286bad2bf798efe7af15568ada43b3dcf8ab2907a9d19feb7bb3d
 1424455081.R806.merkaba

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

[Akonadi] [Bug 389608] New: akonadictl fsck: offer to fix duplicate items

2018-01-29 Thread Martin Steigerwald
https://bugs.kde.org/show_bug.cgi?id=389608

Bug ID: 389608
   Summary: akonadictl fsck: offer to fix duplicate items
   Product: Akonadi
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: mar...@lichtvoll.de
  Target Milestone: ---

Offer to fix up duplicate items.

For example:

Checking qt-kde-ml
Found duplicates 1424447870.R861.merkaba
Found duplicates 1424453278.R177.merkaba
Found duplicates 1424453279.R44.merkaba
Found duplicates 1424455081.R806.merkaba
Found duplicates 1424455081.R860.merkaba
Found duplicates 1435497488.R146.merkaba
Found duplicates 1435497488.R303.merkaba:2,S
Found duplicates 1435499290.R326.merkaba:2,S
Found duplicates 1435499291.R292.merkaba
Found duplicates 1435499291.R683.merkaba
Found duplicates 1435499291.R865.merkaba
Found duplicates 1435499291.R886.merkaba:2,S


Currently user has to figure it out by herself. And from a simple ls -l it does
not appear to be obvious what to do:

~/.local/share/local-mail/[…]/.Debian.directory/qt-kde-ml/new> ls -l 
1424447870.R861.merkaba 1424453278.R177.merkaba 1424453279.R44.merkaba
1424455081.R806.merkaba 1424455081.R806.merkaba 1424455081.R806.merkaba
1424455081.R860.merkaba 1435497488.R146.merkaba 1435497488.R303.merkaba:2,S
1435499290.R326.merkaba:2,S 1435499291.R292.merkaba 1435499291.R683.merkaba
1435499291.R865.merkaba 1435499291.R886.merkaba:2,S
-rw-r--r-- 1 martin martin 6560 Feb 20  2015 1424447870.R861.merkaba
-rw-r--r-- 1 martin martin 6085 Feb 20  2015 1424453278.R177.merkaba
-rw-r--r-- 1 martin martin 4232 Feb 20  2015 1424453279.R44.merkaba
-rw-r--r-- 1 martin martin 4175 Feb 20  2015 1424455081.R806.merkaba
-rw-r--r-- 1 martin martin 4175 Feb 20  2015 1424455081.R806.merkaba
-rw-r--r-- 1 martin martin 4175 Feb 20  2015 1424455081.R806.merkaba
-rw-r--r-- 1 martin martin 4348 Feb 20  2015 1424455081.R860.merkaba
-rw-r--r-- 1 martin martin 4309 Jun 28  2015 1435497488.R146.merkaba
-rw-r--r-- 1 martin martin 4327 Jun 28  2015 1435497488.R303.merkaba:2,S
-rw-r--r-- 1 martin martin 4351 Jun 28  2015 1435499290.R326.merkaba:2,S
-rw-r--r-- 1 martin martin 4314 Jun 28  2015 1435499291.R292.merkaba
-rw-r--r-- 1 martin martin 8027 Jun 28  2015 1435499291.R683.merkaba
-rw-r--r-- 1 martin martin 4349 Jun 28  2015 1435499291.R865.merkaba
-rw-r--r-- 1 martin martin 7910 Jun 28  2015 1435499291.R886.merkaba:2,S


Currently only three files are obvious:

~/.local/share/local-mail/.Lichtvoll.directory/.Debian.directory/qt-kde-ml/new>
sha512sum  1424447870.R861.merkaba 1424453278.R177.merkaba
1424453279.R44.merkaba 1424455081.R806.merkaba 1424455081.R806.merkaba
1424455081.R806.merkaba 1424455081.R860.merkaba 1435497488.R146.merkaba
1435497488.R303.merkaba:2,S 1435499290.R326.merkaba:2,S 1435499291.R292.merkaba
1435499291.R683.merkaba 1435499291.R865.merkaba 1435499291.R886.merkaba:2,S |
sort
[…]
bcd41316ed95949d8c211c38df21f818687d568c408db53bcaee9d70798c09c0408bb64bdd0286bad2bf798efe7af15568ada43b3dcf8ab2907a9d19feb7bb3d
 1424455081.R806.merkaba
bcd41316ed95949d8c211c38df21f818687d568c408db53bcaee9d70798c09c0408bb64bdd0286bad2bf798efe7af15568ada43b3dcf8ab2907a9d19feb7bb3d
 1424455081.R806.merkaba
bcd41316ed95949d8c211c38df21f818687d568c408db53bcaee9d70798c09c0408bb64bdd0286bad2bf798efe7af15568ada43b3dcf8ab2907a9d19feb7bb3d
 1424455081.R806.merkaba

and appear to show a consistency issue on my BTRFS filesystem as they have the
same name.


Also related:

Bug 389607 - akonadictl fsck: Show more helpful messages

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

[Akonadi] [Bug 389607] akonadictl fsck: Show more helpful messages

2018-01-29 Thread Martin Steigerwald
https://bugs.kde.org/show_bug.cgi?id=389607

--- Comment #1 from Martin Steigerwald  ---
That is with Akonadi 17.08.3

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

[Akonadi] [Bug 389607] New: akonadictl fsck: Show more helpful messages

2018-01-29 Thread Martin Steigerwald
https://bugs.kde.org/show_bug.cgi?id=389607

Bug ID: 389607
   Summary: akonadictl fsck: Show more helpful messages
   Product: Akonadi
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: mar...@lichtvoll.de
  Target Milestone: ---

Currently the error messages of akonadictl fsck do not really indicate the
issue at hand to a user who does not understand the internals of Akonadi.

In addition to optionally show some metadata about the affected items so the
user can get an idea on how important they are to her, I think its also
important to reword them so he can understand them more easily.

Of course, even better would be if akonadictl fsck could fix the issues it
finds.



Some suggestions to improve the situation:

Item "1289323" has no RID. =>

Item "1289323" only stored in database, not locally in XYZ resource.

XYZ should be the name of the affected resource.


Item "1360766" has RID and is dirty. =>

Item "1360766" has changes that are only stored in the database, not locally in
XYZ resource



Checking qt-kde-ml
Found duplicates 1424447870.R861.merkaba
Found duplicates 1424453278.R177.merkaba
Found duplicates 1424453279.R44.merkaba
Found duplicates 1424455081.R806.merkaba
Found duplicates 1424455081.R860.merkaba
Found duplicates 1435497488.R146.merkaba
Found duplicates 1435497488.R303.merkaba:2,S
Found duplicates 1435499290.R326.merkaba:2,S
Found duplicates 1435499291.R292.merkaba
Found duplicates 1435499291.R683.merkaba
Found duplicates 1435499291.R865.merkaba
Found duplicates 1435499291.R886.merkaba:2,S

=> Exactly tell which files are identically to give the user the chance to
remove duplicate files. It is not obvious from the above:

~/.local/share/local-mail/[…]/.Debian.directory/qt-kde-ml/new> ls -l 
1424447870.R861.merkaba 1424453278.R177.merkaba 1424453279.R44.merkaba
1424455081.R806.merkaba 1424455081.R806.merkaba 1424455081.R806.merkaba
1424455081.R860.merkaba 1435497488.R146.merkaba 1435497488.R303.merkaba:2,S
1435499290.R326.merkaba:2,S 1435499291.R292.merkaba 1435499291.R683.merkaba
1435499291.R865.merkaba 1435499291.R886.merkaba:2,S
-rw-r--r-- 1 martin martin 6560 Feb 20  2015 1424447870.R861.merkaba
-rw-r--r-- 1 martin martin 6085 Feb 20  2015 1424453278.R177.merkaba
-rw-r--r-- 1 martin martin 4232 Feb 20  2015 1424453279.R44.merkaba
-rw-r--r-- 1 martin martin 4175 Feb 20  2015 1424455081.R806.merkaba
-rw-r--r-- 1 martin martin 4175 Feb 20  2015 1424455081.R806.merkaba
-rw-r--r-- 1 martin martin 4175 Feb 20  2015 1424455081.R806.merkaba
-rw-r--r-- 1 martin martin 4348 Feb 20  2015 1424455081.R860.merkaba
-rw-r--r-- 1 martin martin 4309 Jun 28  2015 1435497488.R146.merkaba
-rw-r--r-- 1 martin martin 4327 Jun 28  2015 1435497488.R303.merkaba:2,S
-rw-r--r-- 1 martin martin 4351 Jun 28  2015 1435499290.R326.merkaba:2,S
-rw-r--r-- 1 martin martin 4314 Jun 28  2015 1435499291.R292.merkaba
-rw-r--r-- 1 martin martin 8027 Jun 28  2015 1435499291.R683.merkaba
-rw-r--r-- 1 martin martin 4349 Jun 28  2015 1435499291.R865.merkaba
-rw-r--r-- 1 martin martin 7910 Jun 28  2015 1435499291.R886.merkaba:2,S

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

[Akonadi] [Bug 389606] New: akonadictl fsck: do not show missing RID warning for search and invitation folders

2018-01-29 Thread Martin Steigerwald
https://bugs.kde.org/show_bug.cgi?id=389606

Bug ID: 389606
   Summary: akonadictl fsck: do not show missing RID warning for
search and invitation folders
   Product: Akonadi
   Version: unspecified
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: mar...@lichtvoll.de
  Target Milestone: ---

Akonadi version: 4:17.08.3-2

akonadictl shows a warning that is not needed and could confuse the user

# Actual results
akonadictl fsck output:

Collection "Search" (id: 1) has no RID.
Collection "OpenInvitations" (id: 395) has no RID.
Collection "DeclinedInvitations" (id: 396) has no RID.
Found 3 collections without RID.

# Expected results
It is probably good not so show a warning for these:

Re: akonadictl fsck: What messages indicate real issues and what to do about
them?
From: Daniel Vrátil
> # Collections without RID
> 
> > Looking for dirty objects...
> > Collection "Search" (id: 1) has no RID.
> > Collection "OpenInvitations" (id: 395) has no RID.
> > Collection "DeclinedInvitations" (id: 396) has no RID.
> > Found 3 collections without RID.
> 
> I think at least for "Search" this is expected. I am not sure about the
> other two, but it may be expected for them as well.

The OpenInvitations and DeclinedInvitations collections are virtual search 
Collections too, so they don't have RID.

We should probably not warn about those

https://marc.info/?l=kdepim-users&m=149431413904927&w=2

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

[kaddressbook] [Bug 389589] Crash when adding a new contact

2018-01-29 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=389589

Laurent Montel  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||mon...@kde.org
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Laurent Montel  ---
No backtrace no fix :)
Sorry :)

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

[kmail2] [Bug 389592] New: KMail2 View "disable Emoticons" option is not permanent

2018-01-29 Thread Don Curtis
https://bugs.kde.org/show_bug.cgi?id=389592

Bug ID: 389592
   Summary: KMail2 View "disable Emoticons" option is not
permanent
   Product: kmail2
   Version: 5.5.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: commands and actions
  Assignee: kdepim-bugs@kde.org
  Reporter: bugrprt21...@online.de
  Target Milestone: ---

The View option of KMail2 to "disable Emoticons" is not permanent.

When KMail2 is restarted the enabled option reverts to disabled and has to be
manually re-enabled -- each time.

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

[kontact] [Bug 352408] KMail crashes wheh searching inbox.

2018-01-29 Thread Wolfgang Schindler
https://bugs.kde.org/show_bug.cgi?id=352408

--- Comment #3 from Wolfgang Schindler  ---
Forgot: Opensuse 42.3

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

[kontact] [Bug 352408] KMail crashes wheh searching inbox.

2018-01-29 Thread Wolfgang Schindler
https://bugs.kde.org/show_bug.cgi?id=352408

Wolfgang Schindler  changed:

   What|Removed |Added

 CC||schind...@schintech.net

--- Comment #2 from Wolfgang Schindler  ---
Same here with kmail2 5.7.1 / kontact 5.7.1

terminate called after throwing an instance of 'std::logic_error'
  what():  basic_string::_S_construct null not valid
Received signal 6
#0 0x7f33ceb5fcb7 
#1 0x7f33cd90c49e 
#2 0x7f33ceb6004d 
#3 0x7f33dd4db940 
#4 0x7f33dd4db8c7 __GI_raise
#5 0x7f33dd4dcc9a __GI_abort
#6 0x7f33ddaf82e5 __gnu_cxx::__verbose_terminate_handler()
#7 0x7f33ddaf60d6 
#8 0x7f33ddaf6121 std::terminate()
#9 0x7f33ddaf6363 __cxa_throw
#10 0x7f33ddb1eb6f std::__throw_logic_error()
#11 0x7f33ddb38c69 std::string::_S_construct<>()
#12 0x7f33ddb3900c std::string::string()
#13 0x7f333e493e31 
#14 0x7f333cc97586 
#15 0x7f333cce366f 
#16 0x7f33de087a83 QMetaObject::activate()
#17 0x7f33de094ad7 QTimer::timeout()
#18 0x7f33de094db2 QTimer::timerEvent()
#19 0x7f33de088af4 QObject::event()
#20 0x7f33ded6a71c QApplicationPrivate::notify_helper()
#21 0x7f33ded71500 QApplication::notify()
#22 0x7f33de05d115 QCoreApplication::notifyInternal2()
#23 0x7f33de0af41e QTimerInfoList::activateTimers()
#24 0x7f33de0afa61 
#25 0x7f33d740d134 g_main_context_dispatch
#26 0x7f33d740d388 
#27 0x7f33d740d42c g_main_context_iteration
#28 0x7f33de0afd8c QEventDispatcherGlib::processEvents()
#29 0x7f33badc4c91 
#30 0x7f33de05b83b QEventLoop::exec()
#31 0x7f33de063ef4 QCoreApplication::exec()
#32 0x00404718 
#33 0x7f33dd4c76d5 __libc_start_main
#34 0x00404c99 _start
  r8: 000a  r9: 7f33e0b22780 r10: 0008 r11:
0202
 r12: 073c3c90 r13: 7fff7ff6e810 r14: 7fff7ff6e7f0 r15:
7fff7ff6e830
  di: 173b  si: 173b  bp: 7f33dd8436d8  bx:
08499f38
  dx: 0006  ax:   cx: 7f33dd4db8c7  sp:
7fff7ff6df98
  ip: 7f33dd4db8c7 efl: 0202 cgf: 0033 erf:

 trp:  msk:  cr2: 
[end of stack trace]
Calling _exit(1). Core file will not be generated.


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

[akregator] [Bug 389463] scrollbars are using a completely different style

2018-01-29 Thread LtWorf
https://bugs.kde.org/show_bug.cgi?id=389463

--- Comment #3 from Salvo "LtWorf" Tomaselli  ---
Oh sorry,seems that I failed to attach it.

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

[akregator] [Bug 389463] scrollbars are using a completely different style

2018-01-29 Thread LtWorf
https://bugs.kde.org/show_bug.cgi?id=389463

--- Comment #2 from Salvo "LtWorf" Tomaselli  ---
Created attachment 110200
  --> https://bugs.kde.org/attachment.cgi?id=110200&action=edit
screenshot of the issue

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

[kaddressbook] [Bug 389589] New: Crash when adding a new contact

2018-01-29 Thread redtide
https://bugs.kde.org/show_bug.cgi?id=389589

Bug ID: 389589
   Summary: Crash when adding a new contact
   Product: kaddressbook
   Version: 5.7.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: redt...@gmail.com
CC: to...@kde.org
  Target Milestone: ---

After adding a name and a number and then clicking the OK button on the add
contact window the application crashes.
My DE is XFCE, I don't have a debug version so I can't provide a backtrace,
just the following terminal log:

** (kaddressbook:1587): WARNING **: Couldn't register with accessibility bus:
Did not receive a reply. Possible causes include: the remote application did
not send a reply, the message bus security policy blocked the reply, the reply
timeout expired, or the network connection was broken.
kf5.kwidgetsaddons: Invalid pixmap specified.
kf5.kwidgetsaddons: Invalid pixmap specified.
kf5.kwidgetsaddons: No frame loaded
kf5.kwidgetsaddons: No frame loaded
kf5.kwidgetsaddons: No frame loaded
org.kde.pim.contacteditor:  error during loading contacteditor plugin :  "The
shared library was not found."
Error loading text-to-speech plug-in "flite"
Errore di segmentazione (core dump creato)

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

[kmail2] [Bug 389588] New: Message tags no longer appear in main toolbar

2018-01-29 Thread Sirshen
https://bugs.kde.org/show_bug.cgi?id=389588

Bug ID: 389588
   Summary: Message tags no longer appear in main toolbar
   Product: kmail2
   Version: 5.7.1
  Platform: Manjaro
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-bugs@kde.org
  Reporter: sigma...@gmail.com
  Target Milestone: ---

Created attachment 110198
  --> https://bugs.kde.org/attachment.cgi?id=110198&action=edit
Screenshot of toolbar and toolbar config menu

In kmail I can create message tags through the "configure kmail" menu in
settings (appearance / message tags).

These message tags then appear in the selection list for inclusion on the main
toolbar as seperate line items (right click the toolbar and select "configure
toolbars"). But when you add the message tags to the toolbar and click on ok,
they never appear on the actual toolbar. There seems to be a bug in actually
making this happen.

The tags do remain in the "configure toolbars" list of active items but not on
the actual toolbar.

In the attached screenshot, you will see I have two message tags in the menu
list (processing and ready to dispatch) but they dont show up on my toolbar.

Can anyone fix this in the next kmail release?

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