[korgac] [Bug 379026] reminder shows dialog for past events

2019-08-20 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=379026

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #7 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.

[kmail2] [Bug 409301] not possible to customize pop account

2019-08-20 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=409301

--- Comment #3 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be 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

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

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.

[kontact] [Bug 411125] New: Kontact: the akonadi PIM service is not operational

2019-08-20 Thread evan
https://bugs.kde.org/show_bug.cgi?id=411125

Bug ID: 411125
   Summary: Kontact: the akonadi PIM service is not operational
   Product: kontact
   Version: 5.12.0
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: evan...@protonmail.com
  Target Milestone: ---

Application: kontact (5.12.0)

Qt Version: 5.12.3
Frameworks Version: 5.61.0
Operating System: Linux 4.15.0-45-generic x86_64
Distribution: KDE neon User Edition 5.16

-- Information about the crash:
- What I was doing when the application crashed:
I opened Kontact and clicked on "to-do list" in the side bar, then it
crashed.
if I click on something else like task lists or journal it doesn't crash
but the error message is still there and I can't use the component.
feeds work fine thought, I assume it is because it doesn't use the pim
service.

- Unusual behavior I noticed:
the Akonadi service failed to start, this is what it says when i try to
start it manually from terminal:
===
ev@potato-E6400:~$ akonadictl start
ev@potato-E6400:~$ Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
org.kde.pim.akonadiserver: database server stopped unexpectedly
org.kde.pim.akonadiserver: Database process exited unexpectedly during initial
connection!
org.kde.pim.akonadiserver: executable: "/usr/sbin/mysqld-akonadi"
org.kde.pim.akonadiserver: arguments:
("--defaults-file=/home/ev/.local/share/akonadi/mysql.conf",
"--datadir=/home/ev/.local/share/akonadi/db_data/",
"--socket=/run/user/1000/akonadi/mysql.socket",
"--pid-file=/run/user/1000/akonadi/mysql.pid")
org.kde.pim.akonadiserver: stdout: ""
org.kde.pim.akonadiserver: stderr: "mysqld-akonadi: [ERROR] Could not open
required defaults file:
/home/ev/.local/share/akonadi/mysql.conf\nmysqld-akonadi: [ERROR] Fatal error
in defaults handling. Program aborted!\n"
org.kde.pim.akonadiserver: exit code: 1
org.kde.pim.akonadiserver: process error: "Unknown error"
org.kde.pim.akonadiserver: Failed to remove runtime connection config file
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited
normally...
QFileSystemWatcher::removePaths: list is empty
QFileSystemWatcher::removePaths: list is empty

(the programm does not end unless i press ctrl+c)
===
Kontact shows an error message that says "the akonadi personal information
management service is not operational."
also when I click on the "details..." button below that message it doesn't
do anything.

i've tried removing my Akonadi config folder but it still won't work.

this is my first time reporting a bug, so sorry if the info i provided is not
so usefull, please guide me.
also sorry if this is a duplicate report

The crash can be reproduced every time.

-- 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 0x7f81ef7aebc0 (LWP 442))]

Thread 27 (Thread 0x7f80c8722700 (LWP 537)):
#0  0x7f81ec0c0bb9 in __GI___poll (fds=0x7f81b004d120, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f81e5af05c9 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f81e5af06dc in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f81ecc1bdcb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f81ecbbd03a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f81ec9e44ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f81ec9e5c72 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f81e79bd6db in start_thread (arg=0x7f80c8722700) at
pthread_create.c:463
#8  0x7f81ec0cd88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 26 (Thread 0x7f80c8f23700 (LWP 533)):
#0  0x7f81ec0c0bf9 in __GI___poll (fds=0x7f81ac003de0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f81e5af05c9 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f81e5af06dc in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f81ecc1bdcb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f81ecbbd03a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f81ec9e44

[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app

2019-08-20 Thread Andras
https://bugs.kde.org/show_bug.cgi?id=404990

--- Comment #59 from Andras  ---
(In reply to Kishore Gopalakrishnan from comment #58)
Oh my I just didn't noticed this cuz so obvious I'd love to use Google's
supervision for login lol. Anyways thanks it works for me. Probably I've to use
this option for now hm.
Also correction, I meant it's not possible to turn on less secure app when
there is 2 step verification is used and in this case Google gives the option
for app password what should work for less secure apps too, well it doesn't
work either. I used my accounts in Kontact with app pw for years and now I had
to reconfigure Akonandi for whatever misbehaving after some upgrade and this
message just started appearing for all of my setup. Anyways, I hope it'll be
solved somehow soon.

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

[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app

2019-08-20 Thread Kishore Gopalakrishnan
https://bugs.kde.org/show_bug.cgi?id=404990

--- Comment #58 from Kishore Gopalakrishnan  ---
(In reply to Andras from comment #57)
> What plain authentication you guys are talking about? It's only for outgoing
> setup, incoming has to be configured in a way it's asked by Google anyway
> and basically that's where this problem is happening at least for me. I have
> a bunch, around 10 account setup in the right way in Kontact, I have 2 step
> auth.. so there is no option to set less secure app in Google account but in
> that case it won't be necessary in theory. It doesn't work for me either,
> same message appears for all of my account so I just wait.

You can do the same for incoming mail by going to the 'connection settings'
section of the 'advanced' tab in the dialog that opens when you click 'modify'
on an incoming account.

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

[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app

2019-08-20 Thread Andras
https://bugs.kde.org/show_bug.cgi?id=404990

--- Comment #57 from Andras  ---
What plain authentication you guys are talking about? It's only for outgoing
setup, incoming has to be configured in a way it's asked by Google anyway and
basically that's where this problem is happening at least for me. I have a
bunch, around 10 account setup in the right way in Kontact, I have 2 step
auth.. so there is no option to set less secure app in Google account but in
that case it won't be necessary in theory. It doesn't work for me either, same
message appears for all of my account so I just wait.

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

[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app

2019-08-20 Thread Nick
https://bugs.kde.org/show_bug.cgi?id=404990

--- Comment #56 from Nick  ---
(In reply to Brendon Higgins from comment #54)
> For the record (because Daniel's blog post claims otherwise), existing users
> can indeed be affected by this: I've had two GMail accounts accessed from
> three serparate machines all start refusing logins over the last few weeks,
> at different times. It seems like some kind of expiry happens, at which
> point logins start failing. PLAIN works for me, fortunately.
> 
> Feels like Google's really skirting anticompetitive/antitrust territory
> here. But maybe I'd have a different opinion given a bit more transparency
> on what they were actually asking for. Either way, thanks for going to bat
> for us, Daniel!

I can also confirm that existing accounts definitely can be affected. Mine has
been configured for a long time and only about 3 weeks ago it started denying
me access. I was able to switch to PLAIN authentication using an app specific
password though.

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

[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app

2019-08-20 Thread Andras
https://bugs.kde.org/show_bug.cgi?id=404990

Andras  changed:

   What|Removed |Added

 CC||andrasszerencs...@gmail.com

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

[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app

2019-08-20 Thread Dennis Schridde
https://bugs.kde.org/show_bug.cgi?id=404990

--- Comment #55 from Dennis Schridde  ---
(In reply to Brendon Higgins from comment #54)
> For the record (because Daniel's blog post claims otherwise), existing users
> [...]

In case someone else also wonders what blog post Brendon talks about:
https://www.dvratil.cz/2019/08/kontact-google-integration-issue/

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

[korganizer] [Bug 387598] Send As ICalendar Address Selection has problems

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

Laurent Montel  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/kde
   ||pim-addons/a6921af76dc0222b
   ||c6bf63c071a9b6b79c3afc5c
 Resolution|--- |FIXED
   Version Fixed In||5.13.0

--- Comment #4 from Laurent Montel  ---
Git commit a6921af76dc0222bc6bf63c071a9b6b79c3afc5c by Laurent Montel.
Committed on 20/08/2019 at 20:28.
Pushed by mlaurent into branch 'master'.

Fix Bug 387598 - Send As ICalendar Address Selection has problems

FIXED-IN: 5.13.0

M  +1-1korganizer/emailaddressselectionldapdialog/CMakeLists.txt
M  +72   -5   
korganizer/emailaddressselectionldapdialog/emailaddressselectionldapdialog.cpp
M  +13   -1   
korganizer/emailaddressselectionldapdialog/emailaddressselectionldapdialog.h
M  +9-2sieveeditor/emaillineedit/emaillineedit.cpp

https://commits.kde.org/kdepim-addons/a6921af76dc0222bc6bf63c071a9b6b79c3afc5c

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

[kmail2] [Bug 408354] If default maildir folder is changed a new set of folders are stored under "/home/$user/file:"

2019-08-20 Thread keitalbame
https://bugs.kde.org/show_bug.cgi?id=408354

keitalbame  changed:

   What|Removed |Added

 CC||keitalb...@posteo.net

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

[Akonadi] [Bug 411093] Unable to start Akonadi: Could not open required defaults file

2019-08-20 Thread Daniel Kraus
https://bugs.kde.org/show_bug.cgi?id=411093

--- Comment #4 from Daniel Kraus  ---
I `tail -f`ed /var/syslog and issued akonadictl start:

Aug 20 21:34:26 localhost kernel: [63166.278573] audit: type=1400
audit(1566329666.867:197): apparmor="DENIED" operation="open"
profile="/usr/sbin/mysqld" name="/sys/devices/system/node/" pid=22974
comm="mysqld-akonadi" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Aug 20 21:34:26 localhost kernel: [63166.295499] audit: type=1400
audit(1566329666.883:198): apparmor="DENIED" operation="open"
profile="/usr/sbin/mysqld" name="/sys/devices/system/node/" pid=22975
comm="mysqld-akonadi" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Aug 20 21:34:26 localhost kernel: [63166.297604] audit: type=1400
audit(1566329666.883:199): apparmor="DENIED" operation="open"
profile="/usr/sbin/mysqld" name="/home/$(USER)/.local/share/akonadi/mysql.conf"
pid=22975 comm="mysqld-akonadi" requested_mask="r" denied_mask="r" fsuid=1000
ouid=1000

As mentioned above, I did try to relax AppArmor rules as per forum suggestions.
Possibly the solution is very simple, but I'm not familiar with the AppArmor
DSL. Any help would be appreciated.

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

[Akonadi] [Bug 411093] Unable to start Akonadi: Could not open required defaults file

2019-08-20 Thread Raphael Posmyk
https://bugs.kde.org/show_bug.cgi?id=411093

Raphael Posmyk  changed:

   What|Removed |Added

 CC||duzy.trzm...@web.de

--- Comment #3 from Raphael Posmyk  ---
I think the second error message about connection via socket to local server
results from a fallback after start of a local instance of mysql failed. The
main problem is access to /home/${USER}/.local/share/akonadi/mysql.conf.

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

[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app

2019-08-20 Thread Brendon Higgins
https://bugs.kde.org/show_bug.cgi?id=404990

Brendon Higgins  changed:

   What|Removed |Added

 CC||bren...@quantumfurball.net

--- Comment #54 from Brendon Higgins  ---
For the record (because Daniel's blog post claims otherwise), existing users
can indeed be affected by this: I've had two GMail accounts accessed from three
serparate machines all start refusing logins over the last few weeks, at
different times. It seems like some kind of expiry happens, at which point
logins start failing. PLAIN works for me, fortunately.

Feels like Google's really skirting anticompetitive/antitrust territory here.
But maybe I'd have a different opinion given a bit more transparency on what
they were actually asking for. Either way, thanks for going to bat for us,
Daniel!

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

[Akonadi] [Bug 411093] Unable to start Akonadi: Could not open required defaults file

2019-08-20 Thread Dan
https://bugs.kde.org/show_bug.cgi?id=411093

Dan  changed:

   What|Removed |Added

 CC||k...@foskett.org

--- Comment #2 from Dan  ---
Same error (and same system info), and would just like to add an observation or
two, in case they're helpful.

First, when following these directions:

https://docs.kde.org/stable5/en/pim/kmail2/clean-start-after-a-failed-migration.html

the process fails with the same error report, and only creates some of the
files it should.

/etc/apparmor.d/usr.sbin.mysqld-akonadi features a line added in a previous
bugfix to allow for creation of mysql lockfile (i think?):

 owner /run/user/*/akonadi/default/* wr,

but my output shows an argument using a different directory:

"--socket=/run/user/1000/akonadi/mysql.socket" 

and akonadiserverrc uses the same directory:

[QMYSQL]
Host=
Name=akonadi
Options="UNIX_SOCKET=/run/user/1000/akonadi/mysql.socket"
ServerPath=/usr/sbin/mysqld-akonadi
StartServer=true

...after the clean start process, /run/user/1000/akonadi/ is empty.

Thanks!

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

[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app

2019-08-20 Thread Nicholas Sushkin
https://bugs.kde.org/show_bug.cgi?id=404990

Nicholas Sushkin  changed:

   What|Removed |Added

 CC||nsush...@sushkins.net

--- Comment #53 from Nicholas Sushkin  ---
(In reply to Daniel Vrátil from comment #50)
> I've now did the necessary changes and filed a request to have the login
> enabled again.

Hi, Daniel,

Are you expecting that Google will notify when your request has been processed?

I am still seeing "Sign in with Google temporarily disabled for this app" when
Akonadi is trying to log into my MFA enabled GMail account.

Thanks

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

[kontact] [Bug 411102] New: selecting new mail => kontact crash

2019-08-20 Thread Philippe ROUBACH
https://bugs.kde.org/show_bug.cgi?id=411102

Bug ID: 411102
   Summary: selecting new mail => kontact crash
   Product: kontact
   Version: 5.12.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: philippe.roub...@free.fr
  Target Milestone: ---

Application: kontact (5.12.0)

Qt Version: 5.13.0
Frameworks Version: 5.61.0
Operating System: Linux 4.12.14-lp151.28.13-default x86_64
Distribution: "openSUSE Leap 15.1"

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

in kde notifier i right click on mail icon then select "new mail" then kontact
disappears and dr konqui dispaly an error message about a crash.

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

Thread 35 (Thread 0x7f00c08eb700 (LWP 24461)):
#0  0x7f02411cabdb in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0235c22376 in base::ConditionVariable::TimedWait () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127
#2  0x7f0235c22d07 in base::WaitableEvent::TimedWaitUntil () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:230
#3  0x7f0235c22e72 in base::WaitableEvent::TimedWait () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:162
#4  0x7f0235bda2f1 in
base::internal::SchedulerWorker::Delegate::WaitForWork () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:37
#5  0x7f0235bdd31d in base::internal::SchedulerWorker::RunWorker () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:303
#6  0x7f0235bdda14 in base::internal::SchedulerWorker::RunPooledWorker ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:229
#7  0x7f0235c24f65 in ThreadFunc () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81
#8  0x7f02411c4569 in start_thread () from /lib64/libpthread.so.0
#9  0x7f02456e09ef in clone () from /lib64/libc.so.6

Thread 34 (Thread 0x7f00a5906700 (LWP 24449)):
#0  0x7f02411cabdb in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0235c22376 in base::ConditionVariable::TimedWait () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127
#2  0x7f0235c22d07 in base::WaitableEvent::TimedWaitUntil () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:230
#3  0x7f0235c22e72 in base::WaitableEvent::TimedWait () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:162
#4  0x7f0235bda2f1 in
base::internal::SchedulerWorker::Delegate::WaitForWork () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:37
#5  0x7f0235bdd66b in base::internal::SchedulerWorker::RunWorker () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:331
#6  0x7f0235bdda14 in base::internal::SchedulerWorker::RunPooledWorker ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:229
#7  0x7f0235c24f65 in ThreadFunc () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81
#8  0x7f02411c4569 in start_thread () from /lib64/libpthread.so.0
#9  0x7f02456e09ef in clone () from /lib64/libc.so.6

Thread 33 (Thread 0x7f00c30f9700 (LWP 24445)):
#0  0x7f02411cabdb in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0235c22376 in base::ConditionVariable::TimedWait () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127
#2  0x7f0235c22d07 in base::WaitableEvent::TimedWaitUntil () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:230
#3  0x7f0235c22e72 in base::WaitableEvent::TimedWait () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:162
#4  0x7f0235bda2f1 in
base::internal::SchedulerWorker::Delegate::WaitForWork () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:37
#5  0x7f0235bdd31d in base::internal::SchedulerWorker::RunWorker () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:303
#6  0x7f0235bdda14 in base::internal::SchedulerWorker::RunPooledWorker ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:229
#7  0x7f0235c24f65 in ThreadFunc () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81
#8  0x7f02411c4569 in start_thread () from /lib64/libpthread.so.0
#9  0x7f02456e09ef in clone () from /lib64/libc.so.6

Thread 32 (Thread 0x7f00c38fa700 (LWP 24390)):
#0  0x7f02411cabdb in pthread_cond_timedwait@@GL

[Akonadi] [Bug 411093] Unable to start Akonadi: Could not open required defaults file

2019-08-20 Thread Daniel Kraus
https://bugs.kde.org/show_bug.cgi?id=411093

--- Comment #1 from Daniel Kraus  ---
NB: I replaced my original user name with 'USER' in this report (albeit not in
all places...).

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

[kmail2] [Bug 411091] KMail doesn't send email

2019-08-20 Thread Thomas Tanghus
https://bugs.kde.org/show_bug.cgi?id=411091

--- Comment #1 from Thomas Tanghus  ---
BTW: Also during the past days I began getting popups asking if I trusted some
certificate ultimately; I think it was Comodo? I should have investigated it,
as I have heard of problems with certificate issuers, but was busy, so I
probably just clicked yes or cancel :(

No idea what-so-ever if it's relevant, but you never no ;) I do usually sign
messages.

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

[Akonadi] [Bug 411093] New: Unable to start Akonadi: Could not open required defaults file

2019-08-20 Thread Daniel Kraus
https://bugs.kde.org/show_bug.cgi?id=411093

Bug ID: 411093
   Summary: Unable to start Akonadi: Could not open required
defaults file
   Product: Akonadi
   Version: 5.12.0
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: boven...@bovender.de
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Upgrade KDE neon 5.16 with KDE Applications 19.08
2. Attempt to start Akonadi

OBSERVED RESULT

Akonadi will not start.

```
$ akonadictl start
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
org.kde.pim.akonadiserver: database server stopped unexpectedly
org.kde.pim.akonadiserver: Database process exited unexpectedly during initial
connection!
org.kde.pim.akonadiserver: executable: "/usr/sbin/mysqld-akonadi"
org.kde.pim.akonadiserver: arguments:
("--defaults-file=/home/USER/.local/share/akonadi/mysql.conf",
"--datadir=/home/daniel/.local/share/akonadi/db_data/",
"--socket=/run/user/1000/akonadi/mysql.socket",
"--pid-file=/run/user/1000/akonadi/mysql.pid")
org.kde.pim.akonadiserver: stdout: ""
org.kde.pim.akonadiserver: stderr: "mysqld-akonadi: [ERROR] Could not open
required defaults file:
/home/USER/.local/share/akonadi/mysql.conf\nmysqld-akonadi: [ERROR] Fatal error
in defaults handling. Program aborted!\n"
org.kde.pim.akonadiserver: exit code: 1
org.kde.pim.akonadiserver: process error: "Unknown error"
mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket
'/run/user/1000/akonadi/mysql.socket' (2)'
Check that mysqld is running and that the socket:
'/run/user/1000/akonadi/mysql.socket' exists!
org.kde.pim.akonadiserver: Failed to remove runtime connection config file
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited
normally...
```

What I already attempted to do: Uninstall/reinstall Akonadi; move
/home/USER/.local/share/akonadi out of the way; change AppArmor settings (see
forum thread linked below).


EXPECTED RESULT

Akonadi should just start (as it did for years prior to upgrading to KDE
Applications 19.08).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE neon 5.16 User Edition
(available in About System)
KDE Plasma Version: 5.16.4
KDE Frameworks Version: 5.61.0
Qt Version: 5.12.3

ADDITIONAL INFORMATION

See related forum thread: https://forum.kde.org/viewtopic.php?f=215&t=162053

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

[kmail2] [Bug 411091] New: KMail doesn't send email

2019-08-20 Thread Thomas Tanghus
https://bugs.kde.org/show_bug.cgi?id=411091

Bug ID: 411091
   Summary: KMail doesn't send email
   Product: kmail2
   Version: 5.10.3
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: tho...@tanghus.net
  Target Milestone: ---

SUMMARY
The last couple of days I noticed that the emails I send weren't delivered. I
tested back and forth, and could only point the finger at kmail (or akonadi?),
as it works fine with my Nextcloud webmail client.

STEPS TO REPRODUCE
1. Compose a mail
2. Try to send it

OBSERVED RESULT
Nothing. No notifications or error messages.


EXPECTED RESULT
The mail was sent with a confirmation notification.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
Operating System: Kubuntu 19.04
KDE Plasma Version: 5.16.4
KDE Frameworks Version: 5.61.0
Qt Version: 5.12.2
Kernel Version: 5.0.0-23-generic
OS Type: 64-bit
Processors: 4 × AMD Athlon(tm) 5350 APU with Radeon(tm) R3
Memory: 15,6 GiB of RAM

ADDITIONAL INFORMATION

I first tried to open kmail from cli. Nothing when sending. Then I restarted
akonadi from cli:

org.kde.pim.akonadiserver: Subscriber
Akonadi::Server::NotificationSubscriber(0x7f01e42a1dc0) identified as
"MessageListTagCacheMonitor - 140276584709584"
org.kde.pim.akonadiserver.search: Executing search "kmail2-48271-SearchSession"
org.kde.pim.akonadiserver.search: Search  "kmail2-48271-SearchSession" done
(without remote search)
org.kde.pim.akonadiserver.search: Executing search "kmail2-48271-SearchSession"
org.kde.pim.akonadiserver.search: Search  "kmail2-48271-SearchSession" done
(without remote search)
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7f01e425e5b0) )
org.kde.pim.akonadiserver: Subscriber
Akonadi::Server::NotificationSubscriber(0x7f01e425e5b0) identified as
"SpecialCollectionsMonitor - 93908266813616"
Qt WebEngine seems to be initialized from a plugin. Please set
Qt::AA_ShareOpenGLContexts using QCoreApplication::setAttribute before
constructing QGuiApplication.
qt.network.ssl: QSslSocket::startClientEncryption: cannot start handshake on
non-plain connection
org.kde.pim.akonadiserver.search: Executing search "searchUpdate-1566288213"
org.kde.pim.akonadiserver.search: Search  "searchUpdate-1566288213" done
(without remote search)
org.kde.pim.akonadiserver.search: Search update for collection
"DeclinedInvitations" ( 41 ) finished: all results:  0 , removed results: 0
org.kde.pim.akonadiserver.search: Executing search "searchUpdate-1566288213"
org.kde.pim.akonadiserver.search: Search  "searchUpdate-1566288213" done
(without remote search)
org.kde.pim.akonadiserver.search: Search update for collection
"OpenInvitations" ( 40 ) finished: all results:  0 , removed results: 0


Where the interesting line is:

  qt.network.ssl: QSslSocket::startClientEncryption: cannot start handshake on
non-plain connection

The smtp setting is set to use STARTTLS with PLAIN authentication. But maybe
that's another kinda 'plain'? ;)

Also:

- I tried restarting 'Mail dispatcher Agent'. 'No items in queue' or something
like that.

- The composed email is copied to the 'Sent' folder, but of course there are no
delivery headers.
- And it isn't in the outbox (local folder).

So it doesn't look like #192046


Oh btw: There was a large update a couple of days ago, with what looked like
KDE Frameworks.

A couple of years ago I had to ditch kdepim for Thunderbird, and now after a
reinstall I was so glad to be back, as everything seemed to work ok. 
I had used kmail since it started and loved it very much, but I have to say
after a couple of years using Thunderbird I never had reasons to file a bug
report. Now after max a couple of weeks kmail/akonadi is basically useless to
me. So sad :(

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