[libkgapi] [Bug 439285] Bad request, Google replied "Contacts API is being deprecated"

2021-08-20 Thread Dirk Tombaugh
https://bugs.kde.org/show_bug.cgi?id=439285

Dirk Tombaugh  changed:

   What|Removed |Added

 CC||dtomba...@gmail.com

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

[Akonadi] [Bug 441214] SMTP passwords aren't being saved

2021-08-20 Thread Caleb Cushing
https://bugs.kde.org/show_bug.cgi?id=441214

--- Comment #3 from Caleb Cushing  ---
Created attachment 140886
  --> https://bugs.kde.org/attachment.cgi?id=140886&action=edit
journalctl just for user

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

[Akonadi] [Bug 441214] SMTP passwords aren't being saved

2021-08-20 Thread Caleb Cushing
https://bugs.kde.org/show_bug.cgi?id=441214

--- Comment #2 from Caleb Cushing  ---
Ok, more weirdness I wiped out the imap and the mailtransports in kwallet
manager after closing kontact first. I came back, and imap is still getting
fetched without those; and saving the password still doesn't take even though
one was added to mailtransports.

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

[Akonadi] [Bug 441214] SMTP passwords aren't being saved

2021-08-20 Thread Caleb Cushing
https://bugs.kde.org/show_bug.cgi?id=441214

Caleb Cushing  changed:

   What|Removed |Added

Summary|App Armor blocking password |SMTP passwords aren't being
   |save|saved

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

[Akonadi] [Bug 441214] App Armor blocking password save

2021-08-20 Thread Caleb Cushing
https://bugs.kde.org/show_bug.cgi?id=441214

--- Comment #1 from Caleb Cushing  ---
I no longer think this is app armor, at least not the source of my problem. I
disabled app armor, rebooted my system and the problem stil exists where it
isn't persisting the smtp password. I've tried editing the sending settings,
and adding it there with the save box checked. I come back there's no ***, when
it asks me on send I make sure the save box is checked. still nothing, still
asks me the next time. I could do with a workaround. I'd save the password
myself if I knew what it was going to look at. I have looked via kwallet
manager and under mailtransports -> passwords it is saved in there, and it's
the same password as under imap -> akonadi... and when I paste it into the
prompt on send it works.

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

[korganizer] [Bug 426082] Calendar schedules all appointments full day

2021-08-20 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=426082

gjditchfi...@acm.org changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

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

[kmail2] [Bug 441260] New: Confusing "Mark Message" menu UX

2021-08-20 Thread Sebastian Krzyszkowiak
https://bugs.kde.org/show_bug.cgi?id=441260

Bug ID: 441260
   Summary: Confusing "Mark Message" menu UX
   Product: kmail2
   Version: Git (master)
  Platform: unspecified
OS: All
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-bugs@kde.org
  Reporter: k...@dosowisko.net
  Target Milestone: ---

Created attachment 140883
  --> https://bugs.kde.org/attachment.cgi?id=140883&action=edit
"Mark Message" menu screenshot

(version: 5.18.0 [there's no such option in the Version field to choose])

For a message that's marked as important, its "Mark Message" menu presents a
selected checkbox with "Remove Important Mark" label (see the attached
screenshot).

That's... confusing. It suggests that removal of important mark is now being
active, so effectively tells that the message is not marked as important, which
isn't true. Unchecking it makes the label change to "Mark Message as
Important", which makes much more sense.

The confusion comes from the fact that KMail presents an action-based wording
in a context that strongly suggest a state-based one. Possible solutions:

- keep the label as "Mark Message as Important" and don't change it for
messages already marked as such, as the checkbox already tells the user whether
the message is marked or not and what will happen after toggling it

- remove the checkbox; keep the current label's behavior. This will make it
clear that the label represents an action that happens after selecting it and
not the current state.

- split the menu item into two items (mark / unmark) with only one enabled at
once. As a bonus, this would make it consistent with "Mark Message as
Read/Unread" entries right above.

The same issue applies to "Mark Message as Action Item" entry as well.

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

[korganizer] [Bug 426082] Calendar schedules all appointments full day

2021-08-20 Thread Dave Bachmann
https://bugs.kde.org/show_bug.cgi?id=426082

--- Comment #5 from Dave Bachmann  ---
This is no longer a problem. Not sure exactly when it was resolved. Here's my
current config:
Operating System: openSUSE Leap 15.3
KDE Plasma Version: 5.18.6
KDE Frameworks Version: 5.76.0
Qt Version: 5.12.7
Kernel Version: 5.3.18-lp152.78-default
OS Type: 64-bit
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.3 GiB of RAM

Please mark as RESOLVED

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

[Akonadi] [Bug 440387] All open applications of all desktops chrashes ...

2021-08-20 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=440387

--- Comment #1 from paul.pering...@zaclys.net ---
Created attachment 140880
  --> https://bugs.kde.org/attachment.cgi?id=140880&action=edit
New crash information added by DrKonqi

akonadiserver (5.18.0 (21.08.0)) using Qt 5.15.2

- What I was doing when the application crashed:
Playing video with mpv using hardware decoding (same happens with vlc, but
desktop freeze and can't be recovered, forces me to reboot).
It doesn't occur with hardware decoding disabled. GPU: RX 5700XT. Driver: mesa
21.2.1
- Custom settings of the application:
Video played at x2 speed.

-- Backtrace (Reduced):
#5  0x7f15a663c4ff in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#6  0x7f15a660f378 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#7  0x7f15a66124a9 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
[...]
#12 0x7f15a6667fd6 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#13 0x7f15a660dd1c in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5

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

[Akonadi] [Bug 440387] All open applications of all desktops chrashes ...

2021-08-20 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=440387

paul.pering...@zaclys.net changed:

   What|Removed |Added

 CC||paul.pering...@zaclys.net

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

[kldap] [Bug 441230] 21.08.0: no qch documentatio

2021-08-20 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=441230

Laurent Montel  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED
 CC||mon...@kde.org

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

[kldap] [Bug 441230] New: 21.08.0: no qch documentatio

2021-08-20 Thread kloczek
https://bugs.kde.org/show_bug.cgi?id=441230

Bug ID: 441230
   Summary: 21.08.0: no qch documentatio
   Product: kldap
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: kloczko.tom...@gmail.com
  Target Milestone: ---

Looks like cmake does not supprt BUILD_QCH=ON.
It would be good to add support for generate devel documentation.

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

[kmbox] [Bug 441225] 21.08.0: no qch documentatio

2021-08-20 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=441225

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #1 from Laurent Montel  ---
As I wrote in previous report, all was added in master.
Not necessary to open x bug report about it :)
Thanks

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

[kmbox] [Bug 441225] New: 21.08.0: no qch documentatio

2021-08-20 Thread kloczek
https://bugs.kde.org/show_bug.cgi?id=441225

Bug ID: 441225
   Summary: 21.08.0: no qch documentatio
   Product: kmbox
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: kloczko.tom...@gmail.com
  Target Milestone: ---

Looks like cmake does not supprt BUILD_QCH=ON.
It would be good to add support for generate devel documentation.

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

[kmail2] [Bug 441136] encoding changes when replying, displaying wrong special character (in french)

2021-08-20 Thread Peer Frank
https://bugs.kde.org/show_bug.cgi?id=441136

Peer Frank  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Peer Frank  ---
the problem did not occur on another installation: 

de-selecting 
Settings/Configure KMail/Composer/Charset/Keep original charset when
replying... 

fixed the problem.

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

[kmail2] [Bug 441136] encoding changes when replying, displaying wrong special character (in french)

2021-08-20 Thread Peer Frank
https://bugs.kde.org/show_bug.cgi?id=441136

--- Comment #1 from Peer Frank  ---
new details:
I wrote a test mail to myself using é è ê û ô à ...
in the reply these special french character are perfectly quoted.

The problematic messages come from gmail accounts (message OK, but french
character lost in the reply). They have a heavy header and I just compared the
charset lines which are slightly different: 

gmail: 
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

kmail:
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"

No idea if this is the explication.

Also setting encoding to UTF-8 manually (Options/Encoding/Unicode/UTF-8) does
not fix the reply.
And there are no french character problems in the reply with non-gmail
messages.

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

[Akonadi] [Bug 441214] New: App Armor blocking password save

2021-08-20 Thread Caleb Cushing
https://bugs.kde.org/show_bug.cgi?id=441214

Bug ID: 441214
   Summary: App Armor blocking password save
   Product: Akonadi
   Version: unspecified
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: xenoterrac...@gmail.com
  Target Milestone: ---

SUMMARY

I'm getting a log, and my smtp password for google isn't saving, it's super
weird.


STEPS TO REPRODUCE

I'm not 100% on this, I feel like there might be another thing I'm missing

1. enable app armor
2. use gmail settings for kmail
3. send email

OBSERVED RESULT

kmail always asks for the smtp password, for some reason this is only happening
for smtp, and only gmail, so weird. I'm seeing this log

 AVC apparmor="DENIED" operation="open" profile="/usr/bin/akonadiserver"
name="/etc/authselect/nsswitch.conf" pid=31873 comm="0x557056b51380-"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0


EXPECTED RESULT

password should be getting saved, no error

SOFTWARE/OS VERSIONS
apparmor: 3.0.1
Akonadi: 21.0.8
Operating System: Manjaro Linux
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.10.59-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-10610U CPU @ 1.80GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics

ADDITIONAL INFORMATION

here's the additional surrounding logs, they might be relevant, not sure

The reason I think it might be a KDE bug, is because it looks like the last
"arch" bug like this got resolved in KDE. https://bugs.archlinux.org/task/64890

Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.messagecomposer: Impossible to specify TO! It's a bug
snapperd.service: Deactivated successfully.
SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined
msg='unit=snapperd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=?
addr=? terminal=? res=success'
static bool LibSecretKeyring::findPassword(const QString&, const QString&,
QKeychain::JobPrivate*)
static bool LibSecretKeyring::findPassword(const QString&, const QString&,
QKeychain::JobPrivate*)
We have an error during reading password "Entry not found"
static bool LibSecretKeyring::findPassword(const QString&, const QString&,
QKeychain::JobPrivate*)
We have an error during reading password "Entry not found"
static bool LibSecretKeyring::findPassword(const QString&, const QString&,
QKeychain::JobPrivate*)
We have an error during reading password "Entry not found"
We have an error during reading password "Entry not found"
static bool LibSecretKeyring::findPassword(const QString&, const QString&,
QKeychain::JobPrivate*)
We have an error during reading password "Entry not found"
static bool LibSecretKeyring::findPassword(const QString&, const QString&,
QKeychain::JobPrivate*)
We have an error during reading password "Entry not found"
void SendJob::setFrom(const QString &from) "caleb.cush...@people-meeter.com"
d->m_returnPath ""
AVC apparmor="DENIED" operation="open" profile="/usr/bin/akonadiserver"
name="/etc/authselect/nsswitch.conf" pid=31873 comm="0x557056b51380-"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
org.kde.pim.akonadiserver.search: Executing search
"akonadi_newmailnotifier_agent-SearchSession"
org.kde.pim.akonadiserver.search: Search
"akonadi_newmailnotifier_agent-SearchSession" done (without remote search)
app-gnome-org.kde.kwalletmanager5-72003.scope: Consumed 2.949s CPU time.

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