[korganizer] [Bug 410863] New: Incidence is automatically selected in reminder window, allowing for accidental postponing and dismissal

2019-08-12 Thread Filipus Klutiero
https://bugs.kde.org/show_bug.cgi?id=410863

Bug ID: 410863
   Summary: Incidence is automatically selected in reminder
window, allowing for accidental postponing and
dismissal
   Product: korganizer
   Version: 5.10.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: reminder daemon (korgac)
  Assignee: kdepim-bugs@kde.org
  Reporter: chea...@gmail.com
  Target Milestone: ---

When a reminder is triggered, its incidence is automatically selected in the
reminder window. This means that if a reminder triggers while the reminder
window is already showing, several incidences can become selected, so that
actions (postponing and dismissal) will affect all.

One particularly likely scenario is the following.
A user arrives to his PC after 2 reminders triggered. He selects the first
incidence, postpones by a duration of x. He then postpones the second incidence
by the same duration of x.

x time after he postponed the first reminder, the reminder for that same
incidence triggers again. The user moves the cursor over the Dismiss button.
Just before the user presses the button, x time after the second reminder was
postponed, the reminder for the second incidence triggers again. The user
pushes the Dismiss button while both incidences are selected, accidentally
dismissing the second incidence's reminder.

Not selecting incidences by default would already solve most of this bug, but
ticket #188848 covers a different scenario which is worth considering when
solving is best.

SOFTWARE/OS VERSIONS

Linux: 5.0.0
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.2

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

[korganizer] [Bug 188848] the reminder popup should have a timeout before accepting keystrokes

2019-08-12 Thread Filipus Klutiero
https://bugs.kde.org/show_bug.cgi?id=188848

Filipus Klutiero  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=410863

-- 
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-12 Thread Ovidiu-Florin BOGDAN
https://bugs.kde.org/show_bug.cgi?id=404990

Ovidiu-Florin BOGDAN  changed:

   What|Removed |Added

 CC||ovidiu@gmail.com

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

[Akonadi] [Bug 410860] New: Kmail is dropping receive account settings.

2019-08-12 Thread Chris
https://bugs.kde.org/show_bug.cgi?id=410860

Bug ID: 410860
   Summary: Kmail is dropping receive account settings.
   Product: Akonadi
   Version: 5.11.90
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: IMAP resource
  Assignee: kdepim-bugs@kde.org
  Reporter: crgla...@gmail.com
  Target Milestone: ---

Application: akonadi_imap_resource (5.11.90)

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

-- Information about the crash:
Kmail has been dropping receive account settings for Gmail accounts (to mme
this random as to which account gets dropped)  The net result is that when I
try to re-eneter credentials the message the "Sign in with Google temporaily
disabled for this app  This app has not been verified by Google in order to use
Google Sign In.

I have five other email accounts all IMAP on Gmail.  Only one is having this
problem.

The crash can be reproduced every time.

-- Backtrace:
Application: akonadi_imap_resource_11 (akonadi_imap_resource), signal:
Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f151b023940 (LWP 1501))]

Thread 21 (Thread 0x7f14b6ffd700 (LWP 1923)):
#0  0x7f1511db3bdb in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f1509787376 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127
#2  0x7f1509787d07 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:230
#3  0x7f1509787e72 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:162
#4  0x7f150973f2f1 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:37
#5  0x7f150974231d in base::internal::SchedulerWorker::RunWorker() () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:303
#6  0x7f1509742a14 in base::internal::SchedulerWorker::RunPooledWorker() ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:229
#7  0x7f1509789f65 in ThreadFunc() () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81
#8  0x7f1511dad569 in start_thread () at /lib64/libpthread.so.0
#9  0x7f15151169ef in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7f1487fff700 (LWP 1922)):
#0  0x7f1511db3bdb in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f1509787376 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127
#2  0x7f1509787d07 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:230
#3  0x7f1509787e72 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:162
#4  0x7f150973f2f1 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:37
#5  0x7f150974231d in base::internal::SchedulerWorker::RunWorker() () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:303
#6  0x7f1509742a14 in base::internal::SchedulerWorker::RunPooledWorker() ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:229
#7  0x7f1509789f65 in ThreadFunc() () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81
#8  0x7f1511dad569 in start_thread () at /lib64/libpthread.so.0
#9  0x7f15151169ef in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7f1450ecf700 (LWP 1586)):
#0  0x7f1511db38ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f150978728a in base::ConditionVariable::Wait() () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:75
#2  0x7f1509787d1c in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:232
#3  0x7f1509787e2f in base::WaitableEvent::Wait() () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:155
#4  0x7f150973f2c5 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:35
#5  0x7f150974231d in base::internal::SchedulerWorker::RunWorker() () at

[Akonadi] [Bug 410841] IMAP folders are Offline

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

Juraj  changed:

   What|Removed |Added

 CC||sgd.or...@gmail.com

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

[kmail2] [Bug 407797] Unseting act un new/unread crashes kmail

2019-08-12 Thread Kamil Dudka
https://bugs.kde.org/show_bug.cgi?id=407797

--- Comment #6 from Kamil Dudka  ---
(In reply to Kamil Dudka from comment #5)
The same scenario worked fine for me now with kmail 5.11.3 but I am not sure
whether it was upgrade of kmail or something else that fixed it for me...

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

[korganizer] [Bug 410752] korganizer should use "better" intervals for reminders

2019-08-12 Thread Mathias Homann
https://bugs.kde.org/show_bug.cgi?id=410752

--- Comment #6 from Mathias Homann  ---
(In reply to Laurent Montel from comment #5)
> Do you think that it's ok for you to use same combobox in reminder dialog
> box ?

that would in my eyes be the perfect solution: why present the user with two
different versions of the same question...?

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

[kmail2] [Bug 410850] KMail hangs when retreiving messages, then crashes on "Quit"

2019-08-12 Thread Jason Franklin
https://bugs.kde.org/show_bug.cgi?id=410850

--- Comment #1 from Jason Franklin  ---
Created attachment 122084
  --> https://bugs.kde.org/attachment.cgi?id=122084=edit
New crash information added by DrKonqi

kmail (5.9.3) using Qt 5.11.3

- What I was doing when the application crashed:

This is the same as my earlier report.  I was reading email from my linked
Gmail account, and KMail
stopped in the middle of retreiving messages.

- Unusual behavior I noticed:

KMail showed a message that it was retreiving messages and then did nothing. 
With File >Quit
KMail generated a crash report.

- Custom settings of the application:

Encrypted/signed email for most communication and a local mail setup that
stores most of my
deleted/archived email.

-- Backtrace (Reduced):
#6  0x7f5d5d95ecd4 in QWebEngineView::page() const () from
/lib/x86_64-linux-gnu/libQt5WebEngineWidgets.so.5
#7  0x7f5d5d95edf1 in QWebEngineView::setHtml(QString const&, QUrl const&)
() from /lib/x86_64-linux-gnu/libQt5WebEngineWidgets.so.5
#8  0x7f5d60ff9dcf in MessageViewer::ViewerPrivate::displaySplashPage
(this=0x56325c318750, templateName=..., data=..., domain=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qchar.h:88
#9  0x7f5d60ffa21f in MessageViewer::ViewerPrivate::displaySplashPage
(this=0x56325c318750, message=...) at
./messageviewer/src/viewer/viewer_p.cpp:839
#10 0x7f5d60ffdb53 in MessageViewer::ViewerPrivate::itemFetchResult
(this=0x56325c318750, job=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qchar.h:88

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

[kmail2] [Bug 410850] KMail hangs when retreiving messages, then crashes on "Quit"

2019-08-12 Thread Jason Franklin
https://bugs.kde.org/show_bug.cgi?id=410850

Jason Franklin  changed:

   What|Removed |Added

 CC||jason.frank...@quoininc.com

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

[kmail2] [Bug 410850] New: KMail hangs when retreiving messages, then crashes on "Quit"

2019-08-12 Thread Jason Franklin
https://bugs.kde.org/show_bug.cgi?id=410850

Bug ID: 410850
   Summary: KMail hangs when retreiving messages, then crashes on
"Quit"
   Product: kmail2
   Version: 5.9.3
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: jason.frank...@quoininc.com
  Target Milestone: ---

Application: kmail (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:

My KMail set up connects to a Gmail account, and I was just checking my mail. 
I switched folders
a couple of times as usual.

- Unusual behavior I noticed:

I saw a multi-colored message that read "KMail is retreiving messages" or
something to that effect.
Then, it just sat there and did nothing.

I then went to File > Quit to stop the application, and the crash report was
generated.

- Custom settings of the application:

I use encrypted/signed mail for most of my communication. I also have a local
mail folder that stores most
mail when it's been archived or deleted.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5c1cd7ef00 (LWP 1473))]

Thread 28 (Thread 0x7f5bfca49700 (LWP 2345)):
#0  futex_reltimed_wait_cancelable (private=0, reltime=0x7f5bfca48400,
expected=0, futex_word=0x7f5bfca485e8) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7f5bfca484a0, mutex=0x7f5bfca48598,
cond=0x7f5bfca485c0) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x7f5bfca485c0, mutex=0x7f5bfca48598,
abstime=0x7f5bfca484a0) at pthread_cond_wait.c:667
#3  0x7f5c2aea2a37 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f5c2aea530a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f5c2aea53f2 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f5c2aea9981 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f5c2aeaae61 in base::internal::SchedulerWorker::Thread::ThreadMain()
() from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7f5c2aeb3c81 in base::(anonymous namespace)::ThreadFunc(void*) ()
from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7f5c31451fa3 in start_thread (arg=) at
pthread_create.c:486
#10 0x7f5c33a1d4cf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 27 (Thread 0x7f5be37fe700 (LWP 2343)):
#0  futex_reltimed_wait_cancelable (private=0, reltime=0x7f5be37fd400,
expected=0, futex_word=0x7f5be37fd5e8) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7f5be37fd4a0, mutex=0x7f5be37fd598,
cond=0x7f5be37fd5c0) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x7f5be37fd5c0, mutex=0x7f5be37fd598,
abstime=0x7f5be37fd4a0) at pthread_cond_wait.c:667
#3  0x7f5c2aea2a37 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f5c2aea530a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f5c2aea53f2 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f5c2aea9981 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f5c2aeaae61 in base::internal::SchedulerWorker::Thread::ThreadMain()
() from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7f5c2aeb3c81 in base::(anonymous namespace)::ThreadFunc(void*) ()
from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7f5c31451fa3 in start_thread (arg=) at
pthread_create.c:486
#10 0x7f5c33a1d4cf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 26 (Thread 0x7f5b7bfff700 (LWP 1703)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x7f5c28a0afb8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x7f5c28a0af68,
cond=0x7f5c28a0af90) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x7f5c28a0af90, mutex=0x7f5c28a0af68) at
pthread_cond_wait.c:655
#3  0x7f5c28914e6a in ?? () from /lib/x86_64-linux-gnu/libQt5Script.so.5
#4  0x7f5c28914e89 in ?? () from 

[kmail2] [Bug 410848] KMail drops a period in column 1 of HTML content

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

David C. Bryant  changed:

   What|Removed |Added

 CC||davidbry...@gvtc.com

--- Comment #3 from David C. Bryant  ---
Created attachment 122083
  --> https://bugs.kde.org/attachment.cgi?id=122083=edit
Lines 154, 155, & 156 of the message, copied from att.net "Raw Message:
display.

I just put this in for grins. I copied it directly from the att.net web site.

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

[kmail2] [Bug 410848] KMail drops a period in column 1 of HTML content

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

--- Comment #2 from David C. Bryant  ---
Created attachment 122082
  --> https://bugs.kde.org/attachment.cgi?id=122082=edit
Same message, forwarded to GVTC and saved from KMail

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

[kmail2] [Bug 410848] KMail drops a period in column 1 of HTML content

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

--- Comment #1 from David C. Bryant  ---
Created attachment 122081
  --> https://bugs.kde.org/attachment.cgi?id=122081=edit
Same message, as saved from KMail

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

[kmail2] [Bug 410848] New: KMail drops a period in column 1 of HTML content

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

Bug ID: 410848
   Summary: KMail drops a period in column 1 of HTML content
   Product: kmail2
   Version: 5.7.3
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: davidbry...@gvtc.com
  Target Milestone: ---

Created attachment 122080
  --> https://bugs.kde.org/attachment.cgi?id=122080=edit
Raw email message copied from  .local/share/...

SUMMARY

This is an intermittent problem. Once in a while, when the character "." (ascii
code x'2E') falls in column 1 (in an HTML-encoded string that has been broken
into 77-byte chunks), KMail (or Akonadi, or the mail transport mechanism) drops
that character from the file that is saved on disk. I only notice that this has
happened if I actually try to click on the broken link. I get a 404 error in my
browser, which I can usually fix pretty easily by just putting the missing "."
back into the URL. 


STEPS TO REPRODUCE
1. Wait a while.
2. On average, 1 in 77 HTML-encoded links will be broken in this manner -- it
only happens when X'2E' should appear right after a \n character, which tends
to happen about 1/77th of the time (77-byte chunks).
3. When it happens, it's pretty obvious.

OBSERVED RESULT
I happened to catch this error red-handed today, so I'm filing this report
while I have the evidence at hand. I have attached three files to this report.
File "1565606331.R463.linux-f0mccolon2commas.txt" is the raw data from my
...akonadi_maildir_resource_1/inbox/cur folder. File "V E R I F Y.mbox" is the
same thing, except that I saved it from the KMail File menu, so it has one
extra line appended at the top of the file. File "V E R I F Y 2.mbox" is a copy
of the same message that was forwarded from att.net to gvtc.com -- it has 24
extra header records because of the forwarding process. You can see that the
"." is missing in the first two files (see lines 155 and 156, respectively),
but present (for some odd reason) in the third one (see line 180). For what
it's worth, I viewed the "Raw Message" in my browser at the att.net web site,
and the "." is present. So it seems that the period got dropped during the SMTP
transport step somehow -- it's at the server, but not in the local disk image.

EXPECTED RESULT
The "." should be present without fail.

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

ADDITIONAL INFORMATION
See the attachments.

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

[korganizer] [Bug 410752] korganizer should use "better" intervals for reminders

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

--- Comment #5 from Laurent Montel  ---
Do you think that it's ok for you to use same combobox in reminder dialog box ?

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

[korganizer] [Bug 410752] korganizer should use "better" intervals for reminders

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

--- Comment #4 from Laurent Montel  ---
Created attachment 122079
  --> https://bugs.kde.org/attachment.cgi?id=122079=edit
screenshot

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

[kmail2] [Bug 410846] New: KMail still loses mail from my inbox

2019-08-12 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=410846

Bug ID: 410846
   Summary: KMail still loses mail from my inbox
   Product: kmail2
   Version: 5.10.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: folders
  Assignee: kdepim-bugs@kde.org
  Reporter: b...@valdyas.org
  Target Milestone: ---

Randomly, mails go missing from my inbox. Obviously, I have no way to reproduce
that reliably, and I don't know whether there are any logs that can be used to
figure out what might have happened and when...

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

[Akonadi] [Bug 410841] IMAP folders are Offline

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

bwl  changed:

   What|Removed |Added

 CC||xt1068...@gmail.com

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

[Akonadi] [Bug 410841] New: IMAP folders are Offline

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

Bug ID: 410841
   Summary: IMAP folders are Offline
   Product: Akonadi
   Version: 5.11.3
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: Gmail resource
  Assignee: dvra...@kde.org
  Reporter: xt1068...@gmail.com
CC: kdepim-bugs@kde.org
  Target Milestone: ---

SUMMARY
IMAP folders are Offline 

STEPS TO REPRODUCE
1. Update This Folder and All its Subfolders
2. Go Online 

OBSERVED RESULT
message from Kmail "Resource Gmail is broken"

EXPECTED RESULT
folder goes online and email is retrieved/sync'd

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: openSUSE Tumbleweed 20190809
KDE Plasma Version:5.16.4 
KDE Frameworks Version: 5.60.0
Qt Version: 5.13.0

ADDITIONAL INFORMATION
OS Type 32-bit
Processors: 2 × Intel® Core™2 Duo CPU E4500 @ 2.20GHz
Memory: 1.9 GiB of RAM

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

[kmail2] [Bug 341909] Reply and Print time is in UTC, not in locale

2019-08-12 Thread rawi
https://bugs.kde.org/show_bug.cgi?id=341909

rawi  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #21 from rawi  ---
Dear KDE-Team

thank you for following this issue attentive until it's resolve.
Sorry for my late reaction.
My bad, that I still use the same Version as 5 years ago on one legacy
installation.
I am sure, that both gjditchfi...@acm.org and Martin Steigerwald correctly
realized, that this bug doesn't affect any more the newer versions. A quickly
check on an fresh install let me see the same

So please close this bug report as fixed, with a big thanks

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