[korganizer] [Bug 94010] Show todo events, that have no dates set

2020-07-05 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=94010

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #5 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[Akonadi] [Bug 423672] org.kde.pim.imapresource: Failed to create folder on server: "Create failed, server replied: ... NO Mailbox already exists ... [ ALREADYEXISTS ]"

2020-07-05 Thread Dennis Schridde
https://bugs.kde.org/show_bug.cgi?id=423672

--- Comment #4 from Dennis Schridde  ---
(In reply to Christophe Giboudeaux from comment #3)
> Please create a merge request: https://invent.kde.org/pim/kimap

https://invent.kde.org/pim/kimap/-/merge_requests/3

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

[kmail2] [Bug 423912] New: Change email background to white when using dark mode

2020-07-05 Thread Marco Albanese
https://bugs.kde.org/show_bug.cgi?id=423912

Bug ID: 423912
   Summary: Change email background to white when using dark mode
   Product: kmail2
   Version: 5.14.1
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: UI
  Assignee: kdepim-bugs@kde.org
  Reporter: deli...@gmail.com
  Target Milestone: ---

Created attachment 129922
  --> https://bugs.kde.org/attachment.cgi?id=129922=edit
Example of a background-less html email on a dark theme

It would be really helpful to have a switch per email to temporary change the
background to white when using a dark theme, since some email are designed (
wrongly ) assuming the background is white and they are difficult to read in
this way.


STEPS TO REPRODUCE
1. Set a "dark" theme
2. Open an HTML email with trasparent (or no ) background which assume a white
default background

OBSERVED RESULT
The background of the email is the one from the dark theme, but the email is
not designed for it

EXPECTED RESULT
There is an option to temporary set the email background to white ( IIRC I've
seen something similar in the gmail android app ).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Archlinux
(available in About System)
KDE Plasma Version: 5.19.0
KDE Frameworks Version: 5.70.0
Qt Version: 5.15.0

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

[korganizer] [Bug 423121] Adding complete task event in journal doesn't work if task completed via "completed" slider

2020-07-05 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=423121

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

--- Comment #3 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/pim/incidenceeditor/-/merge_requests/1

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

[korganizer] [Bug 423121] Adding complete task event in journal doesn't work if task completed via "completed" slider

2020-07-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=423121

gjditchfi...@acm.org changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||gjditchfi...@acm.org
 Ever confirmed|0   |1

--- Comment #2 from gjditchfi...@acm.org ---
The situation described in comment 1 is quite different from the main
description, and I'm not sure KOrganizer should generate a journal entry then.
(Who marked the to-do as complete?)  I suggest that you enter a new "wish list"
bug for the CalDAV case, if you want that behavior, so we can close this bug
report when the "slider" problem is fixed.

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

[Akonadi] [Bug 423672] org.kde.pim.imapresource: Failed to create folder on server: "Create failed, server replied: ... NO Mailbox already exists ... [ ALREADYEXISTS ]"

2020-07-05 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=423672

--- Comment #3 from Christophe Giboudeaux  ---
Please create a merge request: https://invent.kde.org/pim/kimap

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

[kmail2] [Bug 423909] KMail perceives cursor location to be vertically offset from where Wacom Bamboo graphic tablet's cursor is visible

2020-07-05 Thread Markus
https://bugs.kde.org/show_bug.cgi?id=423909

--- Comment #1 from Markus  ---
Created attachment 129921
  --> https://bugs.kde.org/attachment.cgi?id=129921=edit
Screenshot of KMail offset behavior showing highlighted message NOT under Wacom
Bamboo graphic tablet cursor

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

[kmail2] [Bug 423909] New: KMail perceives cursor location to be vertically offset from where Wacom Bamboo graphic tablet's cursor is visible

2020-07-05 Thread Markus
https://bugs.kde.org/show_bug.cgi?id=423909

Bug ID: 423909
   Summary: KMail perceives cursor location to be vertically
offset from where Wacom Bamboo graphic tablet's cursor
is visible
   Product: kmail2
   Version: 5.14.2
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: UI
  Assignee: kdepim-bugs@kde.org
  Reporter: no-spam-...@q.com
  Target Milestone: ---

SUMMARY
KMail perceives cursor location to be vertically offset by one inch from where
Wacom Bamboo graphic tablet's cursor is visible.


STEPS TO REPRODUCE
1. Start Kmail
2. Move the graphic tablet's cursor into the KMail window

Reproducible 100% of the time.


OBSERVED RESULT
KMail perceives cursor location to be vertically offset by one inch from where
Wacom Bamboo graphic tablet's cursor is visible.


EXPECTED RESULT
The area where KMail perceives the cursor to be should be exactly the same as
where the graphic tablet's cursor is visible.


SOFTWARE/OS VERSIONS
KMail2 Version 5.14.2 (20.04.2)
Linux Kernel Version: 5.3.18-lp152.19-default
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.71.0
Qt Version: 5.12.7
xf86-input-wacom Version: 0.34.2-lp152.4.6
libwacom2 Version: 1.1-lp152.2.5
libwacom-data Version: 1.1-lp152.2.5
Distro: openSUSE Leap 15.2 for X86_64


WACOM GRAPIC TABLET DETAILS
Wacom Bamboo Pen Model MTE-450A set to Absolute Mode (problem also happens in
Relative mode)
Wacom Bamboo USB Vendor ID: 0x56a
Wacom Bamboo USB Product ID: 0x65
Wacom Bamboo USB Revision: 0.00


ADDITIONAL INFORMATION
I did a fresh install of openSUSE Leap 15.2 on 2020-Jul-04 (the latest and most
current openSUSE version as of this report) and discovered there is a problem
using a Wacom Bamboo tablet with KMail Version 5.14.2 (20.04.2).

Whenever the graphic tablet's cursor is in the KMail window, the area where
KMail perceives I am pointing is vertically offset by one inch below where the
graphic tablet's cursor is visible on my 23 inch screen.

For example, when I see my tablet's cursor hovering over the topmost message in
the Message List, KMail highlights the message 3 rows below, showing KMail
perceives I am pointing at the forth row from the top in the Message List,
instead of perceiving I am pointing at the topmost message as it should. The
same behavior presents in the Folders column. This makes KMail unusable with
the graphic tablet, as I can not select any email message higher than the forth
row. The icons in the toolbar are completely inaccessible by the graphic
tablet's pointer and can not be activated.  The menu bar is completely
inaccessible by the graphic tablet's pointer and can not be activated. The same
offset behavior happens when using the scroll bar button (thumb bar).

The graphic tablet's pointer offset behavior is not presenting in any other
application I used. This behavior was not present in any version of KMail from
openSUSE Leap 15.0 or older.

When I connect a mouse to my system, the area where KMail perceives the mouse
is pointing is the same as where the mouse cursor is visible, as it should be,
and all functionality is accessible.

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

[Akonadi] [Bug 423672] org.kde.pim.imapresource: Failed to create folder on server: "Create failed, server replied: ... NO Mailbox already exists ... [ ALREADYEXISTS ]"

2020-07-05 Thread Dennis Schridde
https://bugs.kde.org/show_bug.cgi?id=423672

--- Comment #2 from Dennis Schridde  ---
Created attachment 129920
  --> https://bugs.kde.org/attachment.cgi?id=129920=edit
kimap-20.04.2-create-alreadyexists-is-not-an-error.patch

Attached patch fixes the issue in in KIMAP 20.04.2 by making CREATE and DELETE
idempotent.

If CREATE fails with an ALREADYEXISTS response code, that is not an error since
the intended result (the object existing at the target location) has been
achieved.

Likewise, if DELETE fails with an NONEXISTENT response code, that is not an
error since the intended result (the object being gone from the target
location) has been achieved.

Please note that for RENAME response code ALREADYEXISTS *is* an error since the
content of the source folder was not moved as intended.

cf. https://tools.ietf.org/html/rfc5530#section-3

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

[kmail2] [Bug 423904] New: KMail crashes while gmail-sync

2020-07-05 Thread Peter Huyoff
https://bugs.kde.org/show_bug.cgi?id=423904

Bug ID: 423904
   Summary: KMail crashes while gmail-sync
   Product: kmail2
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: peter.huy...@gmx.de
  Target Milestone: ---

Application: kmail (5.14.2 (20.04.2))

Qt Version: 5.15.0
Frameworks Version: 5.71.0
Operating System: Linux 5.7.5-1-default x86_64
Windowing system: X11
Distribution: "openSUSE Tumbleweed"

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

Before this crash, akonadi crashes multiple times. KMail runned then with empty
Screen and aconadictl -fsck has corrected a lot of issuses.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault

[KCrash Handler]
#4  std::__atomic_base::load (__m=std::memory_order_relaxed, this=) at
/usr/include/c++/10/bits/atomic_base.h:420
#5  QAtomicOps::loadRelaxed (_q_value=) at
../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#6  QBasicAtomicInteger::loadRelaxed (this=) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107
#7  QtPrivate::RefCount::isShared (this=) at
../../include/QtCore/../../src/corelib/tools/qrefcount.h:101
#8  QList::append (this=0x100, t=@0x7ffe166e43a0: 0x55a57f76ff70) at
../../include/QtCore/../../src/corelib/tools/qlist.h:622
#9  0x7ff70b3aeba0 in QWidget::insertAction
(this=this@entry=0x55a57f76ff70, before=, before@entry=0x0,
action=0x55a57f6352b0) at kernel/qwidget.cpp:3130
#10 0x7ff70a12c35b in KXMLGUI::ActionList::plug (index=,
container=0x55a57f76ff70, this=0x55a57f6868a0) at
/usr/src/debug/kxmlgui-5.71.0-1.1.x86_64/src/kxmlguifactory_p.cpp:45
#11 KXMLGUI::ContainerNode::plugActionList (mergingIdxIt=..., mergingIdxIt=..., state=...,
this=0x55a57f7185b0) at
/usr/src/debug/kxmlgui-5.71.0-1.1.x86_64/src/kxmlguifactory_p.cpp:234
#12 KXMLGUI::ContainerNode::plugActionList (this=0x55a57f7185b0, state=...) at
/usr/src/debug/kxmlgui-5.71.0-1.1.x86_64/src/kxmlguifactory_p.cpp:204
#13 0x7ff70a12c3e1 in KXMLGUI::ContainerNode::plugActionList
(this=0x55a57f640700, state=...) at
/usr/src/debug/kxmlgui-5.71.0-1.1.x86_64/src/kxmlguifactory_p.cpp:208
#14 0x7ff70a12c3e1 in KXMLGUI::ContainerNode::plugActionList
(this=0x55a57f686630, state=...) at
/usr/src/debug/kxmlgui-5.71.0-1.1.x86_64/src/kxmlguifactory_p.cpp:208
#15 0x7ff70a133721 in KXMLGUIFactory::plugActionList (this=0x55a57f8d8c80,
client=0x7ff6f0008110, name=..., actionList=...) at
/usr/src/debug/kxmlgui-5.71.0-1.1.x86_64/src/kxmlguifactory.cpp:574
#16 0x7ff7091ecf50 in PimCommon::PluginInterface::initializePluginActions
(this=0x7ffe166e46f0, prefix=..., guiClient=0x7ff6f0008110) at
/usr/src/debug/pimcommon-20.04.2-1.1.x86_64/src/pimcommonakonadi/genericplugins/plugininterface.cpp:168
#17 0x7ff70bb65900 in KMMainWidget::initializePluginActions
(this=0x55a5830f7b30) at
/usr/src/debug/kmail-20.04.2-1.1.x86_64/src/kmmainwidget.cpp:4217
#18 0x7ff70bb6c574 in KMMainWidget::slotShowStartupFolder
(this=0x55a5830f7b30) at
/usr/src/debug/kmail-20.04.2-1.1.x86_64/src/kmmainwidget.cpp:4121
#19 0x7ff70a84da31 in QObject::event (this=0x55a5830f7b30,
e=0x55a57f7d5220) at kernel/qobject.cpp:1314
#20 0x7ff70b3780cf in QApplicationPrivate::notify_helper (this=, receiver=0x55a5830f7b30, e=0x55a57f7d5220) at
kernel/qapplication.cpp:3671
#21 0x7ff70a821b0a in QCoreApplication::notifyInternal2
(receiver=0x55a5830f7b30, event=0x55a57f7d5220) at
../../include/QtCore/5.15.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:325
#22 0x7ff70a824531 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x55a57ee1a510) at
kernel/qcoreapplication.cpp:1815
#23 0x7ff70a8798c3 in postEventSourceDispatch (s=0x55a57ef37e70) at
kernel/qeventdispatcher_glib.cpp:277
#24 0x7ff70755f2c7 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#25 0x7ff70755f648 in ?? () from /usr/lib64/libglib-2.0.so.0
#26 0x7ff70755f6ff in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#27 0x7ff70a878f4f in QEventDispatcherGlib::processEvents
(this=0x55a57ef3f840, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#28 0x7ff70a8204cb in QEventLoop::exec (this=this@entry=0x7ffe166e4b90,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#29 0x7ff70a828730 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#30 0x55a57ec92386 in main (argc=, argv=) at
/usr/include/qt5/QtCore/qcoreapplication.h:116
[Inferior 1 (process 12275) detached]

Possible duplicates by query: bug 422092, bug 421432, bug 420495, bug 419785,
bug 418784.

Reported using DrKonqi

-- 
You are receiving this mail because:
You are the 

[Akonadi] [Bug 422962] Akonadi indexing agent crashes time and again

2020-07-05 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=422962

Christoph Feck  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |BACKTRACE

--- Comment #1 from Christoph Feck  ---
Please add the backtrace from the crash dialog. For more information, please
see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

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

[Akonadi] [Bug 334209] synchronizes folder contents during runtime needlessly when switching between different folders

2020-07-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=334209

bugs.kde.or...@gcth.net changed:

   What|Removed |Added

 CC||bugs.kde.or...@gcth.net

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

[Akonadi] [Bug 423222] Akonadi crashes while importing mails into KMail

2020-07-05 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=423222

--- Comment #1 from Christoph Feck  ---
So unfortunately, these qTerminate() issues are not yet resolved.

If this is reproducible, could you please run the akonadiserver in a terminal
and show its output? The message displayed could help understanding the issue.

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