[korganizer] [Bug 317656] Korganizer alert reminders are not reliable (they're lost after logout)

2019-07-20 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=317656

--- Comment #9 from BingMyBong  ---
(In reply to Filipus Klutiero from comment #8)
> Having used KOrganizer for 15 years, I can definitely confirm that its
> reminders are unreliable. However, I never understood how to reproduce loss,
> and I could not reproduce with a logout. Both a reminder I set to trigger
> while my session was closed and one set to trigger after I opened a new
> session "popped up" fine, under Kubuntu 19.04 (KOrganizer 5.10.3, KDE
> Frameworks 5.56.0).
> 
> Can one of you still reproduce this, and if so, which distribution do you
> use? And if so, does this affect events only or todo-s too?

It no longer happens for me.  I thought this had been closed. I don't use
To-dos.

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

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

2019-07-20 Thread Filipus Klutiero
https://bugs.kde.org/show_bug.cgi?id=379026

Filipus Klutiero  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #4 from Filipus Klutiero  ---
See comment #3

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

[korganizer] [Bug 317656] Korganizer alert reminders are not reliable (they're lost after logout)

2019-07-20 Thread Filipus Klutiero
https://bugs.kde.org/show_bug.cgi?id=317656

Filipus Klutiero  changed:

   What|Removed |Added

 CC||chea...@gmail.com

--- Comment #8 from Filipus Klutiero  ---
Having used KOrganizer for 15 years, I can definitely confirm that its
reminders are unreliable. However, I never understood how to reproduce loss,
and I could not reproduce with a logout. Both a reminder I set to trigger while
my session was closed and one set to trigger after I opened a new session
"popped up" fine, under Kubuntu 19.04 (KOrganizer 5.10.3, KDE Frameworks
5.56.0).

Can one of you still reproduce this, and if so, which distribution do you use?
And if so, does this affect events only or todo-s too?

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

[korganizer] [Bug 410036] New: KOrganizer closing out of the blue

2019-07-20 Thread André Padilha
https://bugs.kde.org/show_bug.cgi?id=410036

Bug ID: 410036
   Summary: KOrganizer closing out of the blue
   Product: korganizer
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: padilha.an...@gmail.com
  Target Milestone: ---

Application: korganizer (5.9.3)

Qt Version: 5.11.3
Frameworks Version: 5.54.0
Operating System: Linux 4.19.0-5-amd64 x86_64
Distribution: Debian GNU/Linux 10 (buster)

-- Information about the crash:
- What I was doing when the application crashed:
Inserting items in the task list

- Unusual behavior I noticed:
Application closing for the third time during the activity above

- Custom settings of the application:
None, excet using mail config from system settings.

The crash can be reproduced every time.

-- Backtrace:
Application: KOrganizer (korganizer), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3b80aaea80 (LWP 10126))]

Thread 8 (Thread 0x7f3ad2462700 (LWP 10265)):
#0  0x7f3b8642be69 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f3b863e1675 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f3b863e206b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3b863e225c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f3b891dc87b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f3b8918a27b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f3b88fd9ec6 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f3b88fe3aa7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f3b86f66fa3 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#9  0x7f3b88cbb4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 7 (Thread 0x7f3b63fff700 (LWP 10147)):
#0  0x7f3b86f6d00c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/x86_64-linux-gnu/libpthread.so.0
#1  0x7f3b84a72e6a in ?? () from /lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f3b84a72e89 in ?? () from /lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f3b86f66fa3 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#4  0x7f3b88cbb4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 6 (Thread 0x7f3b6d4e1700 (LWP 10141)):
#0  0x7f3b86f6d00c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/x86_64-linux-gnu/libpthread.so.0
#1  0x7f3b6daf5e03 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#2  0x7f3b6daf5b57 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#3  0x7f3b86f66fa3 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#4  0x7f3b88cbb4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 5 (Thread 0x7f3b7d029700 (LWP 10133)):
#0  0x7f3b8642be84 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f3b863e1fed in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f3b863e225c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3b891dc87b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f3b8918a27b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f3b88fd9ec6 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f3b88fe3aa7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f3b86f66fa3 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#8  0x7f3b88cbb4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 4 (Thread 0x7f3b7d879700 (LWP 10130)):
#0  0x7f3b88cb0819 in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7f3b863e2136 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f3b863e225c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3b891dc87b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f3b8918a27b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f3b88fd9ec6 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f3b88fe3aa7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f3b86f66fa3 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#8  0x7f3b88cbb4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 3 (Thread 0x7f3b7eda2700 (LWP 10128)):
#0  0x7f3b8a795320 in ?? () from /lib64/ld-linux-x86-64.so.2
#1  0x7f3b8a79a1f8 in __tls_get_addr () from /lib64/ld-linux-x86-64.so.2
#2  0x7f3b88fe2e26 in ?? () from /lib/x86_64-linux-gnu/libQ

[kontact] [Bug 410030] Tags

2019-07-20 Thread Mark Stanton
https://bugs.kde.org/show_bug.cgi?id=410030

Mark Stanton  changed:

   What|Removed |Added

Product|kmail2  |kontact
  Component|misc|contacts

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

[kmail2] [Bug 410030] New: Tags

2019-07-20 Thread Mark Stanton
https://bugs.kde.org/show_bug.cgi?id=410030

Bug ID: 410030
   Summary: Tags
   Product: kmail2
   Version: 5.11.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: misc
  Assignee: kdepim-bugs@kde.org
  Reporter: m...@stantoncentral.co.uk
  Target Milestone: ---

SUMMARY
Tags are difficult to use! There are several problems.

1. Creating a new tag from the tags dialog on a person's contact dialog. After
creating the tag and returning to the list of tags, the newly created tag is
not present. The dialog must be closed and re-opened to be used.

2. After creating a new tag, it is not present in the dropdown list of tags
available from the tag text box above the list of contacts. Kontact must be
closed and re-opened for the tag to be used.

3. It is difficult to use tags as a filter. On first use, every tag is set in
the dropdown from the tag text box above the list of contacts. Selecting just
one requires clicking every other one to unselect them. 
Although "All" is the initial state, there is no single click way to
re-generate it, nor to "clear all".


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Fedora 30
(available in About System)
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.4

ADDITIONAL INFORMATION

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

[kmail2] [Bug 410028] New: KMail crashes when changing the Folder List Appearence

2019-07-20 Thread Christian Schütze
https://bugs.kde.org/show_bug.cgi?id=410028

Bug ID: 410028
   Summary: KMail crashes when changing the Folder List Appearence
   Product: kmail2
   Version: 5.11.2
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: schuetze.christia...@gmail.com
  Target Milestone: ---

Application: kmail (5.11.2)

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

-- Information about the crash:
- What I was doing when the application crashed:
1. Open Settings > Configure KMail > Appearance > Layout
2. Changing between "Long folder list" and "Short folder list"
3. Clicking  Apply => Application crashes

After restarting the app the setting is applied.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd085471a40 (LWP 32259))]

Thread 26 (Thread 0x7fd04f7fe700 (LWP 4479)):
#0  0x7fd0932b716c in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fd08c9cb836 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7fd08c9cc203 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7fd08c9cc381 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7fd08c984641 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7fd08c9874dd in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7fd08c987bd4 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7fd08c9ce675 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#8  0x7fd0932b0faa in start_thread () from /lib64/libpthread.so.0
#9  0x7fd096cdc73f in clone () from /lib64/libc.so.6

Thread 25 (Thread 0x7fd078bab700 (LWP 1352)):
#0  0x7fd096ccd80c in read () from /lib64/libc.so.6
#1  0x7fd09284570f in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fd092891c8e in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fd092893342 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7fd09289346f in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7fd095894ceb in QEventDispatcherGlib::processEvents
(this=0x7fd0640050b0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7fd09583d2eb in QEventLoop::exec (this=this@entry=0x7fd078baab60,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#7  0x7fd095675f91 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#8  0x7fd095677112 in QThreadPrivate::start (arg=0x55a93cefa130) at
thread/qthread_unix.cpp:360
#9  0x7fd0932b0faa in start_thread () from /lib64/libpthread.so.0
#10 0x7fd096cdc73f in clone () from /lib64/libc.so.6

Thread 24 (Thread 0x7fcf5763f700 (LWP 1348)):
#0  0x7fd0932b716c in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fd08c9cb836 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7fd08c9cc203 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7fd08c9cc381 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7fd08c984641 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7fd08c98782b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7fd08c987bd4 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7fd08c9ce675 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#8  0x7fd0932b0faa in start_thread () from /lib64/libpthread.so.0
#9  0x7fd096cdc73f in clone () from /lib64/libc.so.6

Thread 23 (Thread 0x7fcf57e40700 (LWP 1341)):
#0  0x7fd0932b716c in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fd08c9cb836 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7fd08c9cc203 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7fd08c9cc381 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7fd08c984641 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7fd08c98782b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7fd08c987bd4 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7fd08c9ce675 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#8  0x7fd0932b0faa in start_thread () from /lib64/libpthread.so.0
#9  0x7fd096cdc73f in clone () from /lib64/libc.so.6

Thread 22 (Thread 0x7fd04700 (LWP 783)):
#0  0x7fd09567757c in QMutex::lock (this=this@entry=0x55a93f5039f0) at
/usr/include/c++/9/bits/atomic_base.h:769
#1  0x7fd0958953e5 in QMutexLocker::QMutexLocker (m=0x55a93f5039f0,
this=) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:206
#2  QThreadData::canWaitLocked (this=0x55a93f5039c0) at
../../include/QtCore/5.13.0/QtCore/private/../../../../../src/corelib/

[kmail2] [Bug 410027] Fails to connect to GMail - "disabled for this app"

2019-07-20 Thread Mark Stanton
https://bugs.kde.org/show_bug.cgi?id=410027

Mark Stanton  changed:

   What|Removed |Added

   Platform|Other   |Fedora RPMs

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

[kmail2] [Bug 410027] New: Fails to connect to GMail - "disabled for this app"

2019-07-20 Thread Mark Stanton
https://bugs.kde.org/show_bug.cgi?id=410027

Bug ID: 410027
   Summary: Fails to connect to GMail  - "disabled for this app"
   Product: kmail2
   Version: 5.11.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: misc
  Assignee: kdepim-bugs@kde.org
  Reporter: m...@stantoncentral.co.uk
  Target Milestone: ---

SUMMARY

Kmail (from Kontact) fails to connect to GMail account.
Google reports

Sign in with Google temporarily disabled for this app
This app has not yet been verified by Google in order to use Google Sign in.

STEPS TO REPRODUCE
1. Attempt to connect to GMail account
2. 
3. 

OBSERVED RESULT

Dialog with error message as above.

EXPECTED RESULT
Should connect and show email.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Fedora 30
(available in About System)
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.4

ADDITIONAL INFORMATION
Stopped working 17/7, I believe.

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

[kaddressbook] [Bug 409998] Documentation does not exist

2019-07-20 Thread Burkhard Lueck
https://bugs.kde.org/show_bug.cgi?id=409998

Burkhard Lueck  changed:

   What|Removed |Added

 CC||lu...@hube-lueck.de

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