[korganizer] [Bug 344679] All event reminders fail to trigger alerts/popups/notifications

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #14 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 410963] New: akonadi crash

2019-08-15 Thread Teddy
https://bugs.kde.org/show_bug.cgi?id=410963

Bug ID: 410963
   Summary: akonadi crash
   Product: Akonadi
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: report...@mailna.biz
  Target Milestone: ---

log attached.

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

[Akonadi] [Bug 410963] akonadi crash

2019-08-15 Thread Teddy
https://bugs.kde.org/show_bug.cgi?id=410963

--- Comment #1 from Teddy  ---
Created attachment 122156
  --> https://bugs.kde.org/attachment.cgi?id=122156=edit
crash log

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

[Akonadi] [Bug 410841] IMAP folders are Offline

2019-08-15 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=410841

matkaz1...@gmail.com changed:

   What|Removed |Added

 CC||matkaz1...@gmail.com

--- Comment #1 from matkaz1...@gmail.com ---
Also occurred on:
Kubuntu 18.04.3
KDE Plasma Version:5.12.8 
KDE Frameworks Version: 5.44.0
Qt Version: 5.9.5

Happens since 2019-08-08. When I tried to recreate Gmail resource I run into
Bug 404990.

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

[kontact] [Bug 410956] New: Kontact crashed upon sending SMS

2019-08-15 Thread Robby Engelmann
https://bugs.kde.org/show_bug.cgi?id=410956

Bug ID: 410956
   Summary: Kontact crashed upon sending SMS
   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: robby.engelm...@r-engelmann.de
  Target Milestone: ---

Application: kontact (5.12.0)

Qt Version: 5.13.0
Frameworks Version: 5.61.0
Operating System: Linux 5.2.8-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
I tried the new feature of sending SMS out of the Addressbook

The crash can be reproduced sometimes.

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

Thread 28 (Thread 0x7f3169397700 (LWP 7978)):
#0  0x7f319219b16c in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f318b7ec546 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127
#2  0x7f318b7ecf13 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:230
#3  0x7f318b7ed091 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:162
#4  0x7f318b7a51f1 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:37
#5  0x7f318b7a808d in base::internal::SchedulerWorker::RunWorker() () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:303
#6  0x7f318b7a8784 in base::internal::SchedulerWorker::RunPooledWorker() ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:229
#7  0x7f318b7ef385 in ThreadFunc() () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81
#8  0x7f3192194faa in start_thread () at /lib64/libpthread.so.0
#9  0x7f319470473f in clone () at /lib64/libc.so.6

Thread 27 (Thread 0x7f3168b96700 (LWP 7977)):
#0  0x7f319219b16c in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f318b7ec546 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127
#2  0x7f318b7ecf13 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:230
#3  0x7f318b7ed091 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:162
#4  0x7f318b7a51f1 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:37
#5  0x7f318b7a83db in base::internal::SchedulerWorker::RunWorker() () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:331
#6  0x7f318b7a8784 in base::internal::SchedulerWorker::RunPooledWorker() ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:229
#7  0x7f318b7ef385 in ThreadFunc() () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81
#8  0x7f3192194faa in start_thread () at /lib64/libpthread.so.0
#9  0x7f319470473f in clone () at /lib64/libc.so.6

Thread 26 (Thread 0x7f309700 (LWP 7974)):
#0  0x7f319219b16c in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f318b7ec546 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127
#2  0x7f318b7ecf13 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:230
#3  0x7f318b7ed091 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:162
#4  0x7f318b7a51f1 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:37
#5  0x7f318b7a808d in base::internal::SchedulerWorker::RunWorker() () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:303
#6  0x7f318b7a8784 in base::internal::SchedulerWorker::RunPooledWorker() ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:229
#7  0x7f318b7ef385 in ThreadFunc() () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81
#8  

[kmail2] [Bug 409289] The akonadi information management service is not working

2019-08-15 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=409289

Christoph Feck  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |WORKSFORME

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

[kaddressbook] [Bug 410933] "Tags" label is present, but inoperative

2019-08-15 Thread David C. Bryant
https://bugs.kde.org/show_bug.cgi?id=410933

David C. Bryant  changed:

   What|Removed |Added

 CC||davidbry...@gvtc.com

--- Comment #1 from David C. Bryant  ---
Created attachment 122147
  --> https://bugs.kde.org/attachment.cgi?id=122147=edit
Same dialog in release 5.7.3

Here's the screenshot from the older version of KAddressBook. The "Tags"
function used to actually do something!

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

[kmail2] [Bug 409289] The akonadi information management service is not working

2019-08-15 Thread Eduardo
https://bugs.kde.org/show_bug.cgi?id=409289

Eduardo  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |BACKTRACE

--- Comment #4 from Eduardo  ---
hi
i resolved the proble with create file mysql-local.conf

touch $HOME/.config/akonadi/mysql-local.conf

its work for me

regreads

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

[kontact] [Bug 75446] Unified Tray Icon / Functionality for Kontact

2019-08-15 Thread Thiago Sueto
https://bugs.kde.org/show_bug.cgi?id=75446

Thiago Sueto  changed:

   What|Removed |Added

 CC||herzensch...@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-15 Thread Mark Stanton
https://bugs.kde.org/show_bug.cgi?id=404990

--- Comment #39 from Mark Stanton  ---
It's "simply" Google's new API implementation, but no, I don't know why access
hasn't been organised for KMail. Evolution has access to GMail.

an ex-KMail user, due to this issue being the final straw.

-- 
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-15 Thread Cherkah
https://bugs.kde.org/show_bug.cgi?id=404990

--- Comment #38 from Cherkah  ---
realy who is in charge to this issue?
there are 3 weeks that i can not use my gooogle account with kmail!!

does kmail is a bad spyware that google reveal? should i stop use it? what
about my others accounts?

a kde/kmail user!

-- 
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-15 Thread Sergey V Turchin
https://bugs.kde.org/show_bug.cgi?id=404990

Sergey V Turchin  changed:

   What|Removed |Added

 CC||z...@altlinux.org

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

[kaddressbook] [Bug 410936] New: Google account address book synchronisation issues

2019-08-15 Thread Hans-Peter Jansen
https://bugs.kde.org/show_bug.cgi?id=410936

Bug ID: 410936
   Summary: Google account address book synchronisation issues
   Product: kaddressbook
   Version: 5.11.3
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: h...@urpla.net
CC: to...@kde.org
  Target Milestone: ---

SUMMARY

* KAddressBook doesn't show (sync) new entries, most (old) contact entries are
available, although an attempt to re-login to the google account seems to be
successful.

* Some contact groups show up multiple times (one contains items, the other is
empty). 

* Having selected the address book and all sub-folders (address groups),
combining contacts attempts to combine all contacts, that appear in more than
one group. Combining does work, if no sub-folders (address groups) are
selected, and the selected contacts are limited to exactly this google account
with sub-folders disabled.

STEPS TO REPRODUCE
Add Google account
Create a new contact
Sync address book
Query new contact

check google address sub-folders (address groups)

select google address book and all sub-folders (address groups) and combine
similar contacts.

OBSERVED RESULT
no new contact found
some address groups appear twice
combining contacts show too many entries

EXPECTED RESULT
new contact show up after sync
every contact group should appear only once
combining contacts should ignore group membership

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE TW 20190810
KDE Plasma Version: 5.16.4
KDE Frameworks Version: 5.60.0
Qt Version: 5.13.0

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

[Akonadi] [Bug 410935] New: akonady _ews_ressource crashes when setting office365 account

2019-08-15 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=410935

Bug ID: 410935
   Summary: akonady _ews_ressource crashes when setting office365
account
   Product: Akonadi
   Version: 5.12.0
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: EWS Resource
  Assignee: kdepim-bugs@kde.org
  Reporter: julien_palmi...@hotmail.fr
CC: kri...@op.pl
  Target Milestone: ---

Created attachment 122136
  --> https://bugs.kde.org/attachment.cgi?id=122136=edit
bug report

SUMMARY

everytime i try to set up my company's office365 account using windows exchange
server, akonady crashes when all is done, after signing up the company's loggin
page. then it is impossible to modify the ews account settings on kmail,
akonady crashes everytime it tries to connect to the account.
i don't have this problem with non office365  microsoft email account (like
hotmail)

STEPS TO REPRODUCE
1. create a new kmail receiving account - using a microsoft EWS tyte account
2. enter the email, loggin, passwd, and select Oauth2 account.
3. check for server autodiscovery - if mail loggin and passwd are ok, it finds
the right server.
4. click OK
5. the company loggin page appears. fill loggin and passwd, and click OK.
6. Then Akonady_ews_ressourses crashes,  and it is impossible to re-open the
kmail ews account to modify or complete it (subscriptions; advances,...), and
akonady will crash everytime it tries to reconnect to the server with the
attached bug report.

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

[kaddressbook] [Bug 409998] Documentation does not exist

2019-08-15 Thread David C. Bryant
https://bugs.kde.org/show_bug.cgi?id=409998

David C. Bryant  changed:

   What|Removed |Added

 CC||davidbry...@gvtc.com

--- Comment #6 from David C. Bryant  ---
I'm writing new documentation ... D22799 in Phabricator, if anybody's
interested. I'm aiming to be done in about one more month (mid-September).

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

[kaddressbook] [Bug 410933] New: "Tags" label is present, but inoperative

2019-08-15 Thread David C. Bryant
https://bugs.kde.org/show_bug.cgi?id=410933

Bug ID: 410933
   Summary: "Tags" label is present, but inoperative
   Product: kaddressbook
   Version: 5.11.3
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: davidbry...@gvtc.com
CC: to...@kde.org
  Target Milestone: ---

Created attachment 122135
  --> https://bugs.kde.org/attachment.cgi?id=122135=edit
Screenshot of the "Add New Contact" dialog from version 5.11.3 (newer)

SUMMARY

I'm writing new documentation for KAddressBook. I had been running an older
version (5.7.3) under openSUSE LEAP 15.0, but recently bought a new PC, and put
"Neon" in there. So now I have 5.11.3. I noticed a change that looks like an
oversight to me.

STEPS TO REPRODUCE
1. Compare the screenshots I've attached to this bug report. I'll have to boot
up my old system to retrieve the 5.7.3 screenshot, which will take a few hours.
2. You will see that the "Tags" GUI button was removed from the "Add New
Contact" dialog (1st page), and a new field ("Blog Feed") has been added. But
the label "Tags" remains.

OBSERVED RESULT
There's a label "Tags" in the dialog window that has no associated action.

EXPECTED RESULT
Either the GUI button and display field for "Tags" should be present or, if the
"Tags functionality has been removed as superfluous, the label "Tags" should be
deleted.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: That's me! "Neon"
(available in About System)
KDE Plasma Version: 5.16.4
KDE Frameworks Version: 5.61.0
Qt Version: 5.12.3

ADDITIONAL INFORMATION
See attachments (screenshots)

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

[kmail2] [Bug 311990] Problem connetcing to dovecot-managesieve with STARTTLS and auth=CRAM-MD5 /LOGIN

2019-08-15 Thread aeris
https://bugs.kde.org/show_bug.cgi?id=311990

--- Comment #24 from aeris  ---
Ok, here is the root cause:
https://github.com/KDE/libksieve/blob/master/src/kmanagesieve/session.cpp#L171

With CRAM-MD5, the challenge is on the `response.key()`, not on the `data`
field, which is here empty. Don't know how to fix this without breaking other
auth type…

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

[kmail2] [Bug 311990] Problem connetcing to dovecot-managesieve with STARTTLS and auth=CRAM-MD5 /LOGIN

2019-08-15 Thread aeris
https://bugs.kde.org/show_bug.cgi?id=311990

--- Comment #23 from aeris  ---
Trouble is here:
https://github.com/KDE/libksieve/blob/master/src/kmanagesieve/sessionthread.cpp#L265-L266

Seems strange, the challenge is expected to be read *before* the AUTHENTICATE
command…

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

[kmail2] [Bug 311990] Problem connetcing to dovecot-managesieve with STARTTLS and auth=CRAM-MD5 /LOGIN

2019-08-15 Thread aeris
https://bugs.kde.org/show_bug.cgi?id=311990

--- Comment #22 from aeris  ---
Seems the used challenge is empty string

./gen-auth.pl CRAM-MD5 "aeris" "$PASS" ""
YWVyaXMgMTliMTYxYjNkMGI4YWY3OGRlNjkwNDFkNWQ4Zm=

Which is the same as the always sent token in my case

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

[kmail2] [Bug 311990] Problem connetcing to dovecot-managesieve with STARTTLS and auth=CRAM-MD5 /LOGIN

2019-08-15 Thread aeris
https://bugs.kde.org/show_bug.cgi?id=311990

aeris  changed:

   What|Removed |Added

 CC||ae...@imirhil.fr

--- Comment #21 from aeris  ---
Same here.
When debugging, I notice the returned CRAM-MD5 is always the same, whatever the
challenge the server send.

Aug 15 10:10:49 kamino dovecot[25805]: auth: Debug: client passdb out: CONT
   1PDE2MzYzMDkzMDA4MTM5MTYuMTU2NTg2Mzg0OUBrYW1pbm8+
Aug 15 10:10:49 kamino dovecot[25805]: auth: Debug: client in: CONT1   
YWVyaXMgMTliMTYxYjNkMGI4YWY3OGRlNjkwNDFkNWQ4Zm= (previous base64 data
may contain sensitive data)
Aug 15 10:11:00 kamino dovecot[25805]: auth: Debug: client passdb out: CONT
   1PDU3NjA0MjQyNTkyMzAwMzEuMTU2NTg2Mzg2MEBrYW1pbm8+
Aug 15 10:11:00 kamino dovecot[25805]: auth: Debug: client in: CONT1   
YWVyaXMgMTliMTYxYjNkMGI4YWY3OGRlNjkwNDFkNWQ4Zm= (previous base64 data
may contain sensitive data)

Notice the 2 challenges PDE2MzYzMDkzMDA4MTM5MTYuMTU2NTg2Mzg0OUBrYW1pbm8+ and
PDU3NjA0MjQyNTkyMzAwMzEuMTU2NTg2Mzg2MEBrYW1pbm8+, but the same response
YWVyaXMgMTliMTYxYjNkMGI4YWY3OGRlNjkwNDFkNWQ4Zm

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

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

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

--- Comment #37 from bwl  ---
easylee has asked a valid question.  Has Google/Alphabet been contacted?  By
who, when? If not why not?  Who owns this problem?  Why no recent activity on
this?
No malice intended.
Kind regards,
Barry

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