[frameworks-kwidgetsaddons] [Bug 413181] Account Assistant UI is missing margins

2019-10-23 Thread Raphael Kubo da Costa
https://bugs.kde.org/show_bug.cgi?id=413181

Raphael Kubo da Costa  changed:

   What|Removed |Added

  Component|UI  |general
 CC||kdelibs-b...@kde.org
Version|5.12.2  |5.63.0
   Assignee|kdepim-bugs@kde.org |cf...@kde.org
Product|kmail2  |frameworks-kwidgetsaddons

--- Comment #3 from Raphael Kubo da Costa  ---
I've tried changing the theme and still had the same results. Changing
component to kwidgetaddons since this is also affecting kassistantdialogtest.

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

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

2019-10-23 Thread Martin van Es
https://bugs.kde.org/show_bug.cgi?id=407797

Martin van Es  changed:

   What|Removed |Added

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

--- Comment #7 from Martin van Es  ---
I can confirm that 5.11.3 doesn't exhibit the problem anymore, for me.

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

[korganizer] [Bug 413316] Can't see the contents of my Nextcloud calendar

2019-10-23 Thread Matthias Fehring
https://bugs.kde.org/show_bug.cgi?id=413316

--- Comment #5 from Matthias Fehring  ---
Hey David Faure, your fix works for me. :) With the changes applied, the
calendar data is visible and Nextcloud stops throwing the exception about a bad
request.

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

[korganizer] [Bug 413316] Can't see the contents of my Nextcloud calendar

2019-10-23 Thread David de Cos
https://bugs.kde.org/show_bug.cgi?id=413316

--- Comment #4 from David de Cos  ---
I can confirm that downgrading to kio 5.62 fixes my problem. Thanks!

If you can mail me some instructions on how to apply the kio fix, I'd be
willing to try it. It may take me a few days, though, since I don't want to do
it on my work computer, so I'll have to install a working system on some other
machine.

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

[korganizer] [Bug 413316] Can't see the contents of my Nextcloud calendar

2019-10-23 Thread David Faure
https://bugs.kde.org/show_bug.cgi?id=413316

--- Comment #3 from David Faure  ---
BTW if you want to downgrade anything, short term, it's kio that you should
downgrade (or all of KF5) from 5.63 to 5.62.

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

[korganizer] [Bug 413316] Can't see the contents of my Nextcloud calendar

2019-10-23 Thread David Faure
https://bugs.kde.org/show_bug.cgi?id=413316

David Faure  changed:

   What|Removed |Added

 CC||fa...@kde.org,
   ||vkra...@kde.org

--- Comment #2 from David Faure  ---
I just fixed a regression in kio_http which led to a similar issue for me.
https://cgit.kde.org/kio.git/commit/?id=02a8d3deb4f97046da4a0bb79abf9510d2d1c0a2

However that last comment makes me wonder. If Depth:0 came from kio_http and
Depth:1 came from kdav, then things might still be wrong, since my patch
ignores the kdav-provided depth.

Any chance you can try the above kio fix and let us know if it works for you?

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

[korganizer] [Bug 413316] Can't see the contents of my Nextcloud calendar

2019-10-23 Thread Matthias Fehring
https://bugs.kde.org/show_bug.cgi?id=413316

Matthias Fehring  changed:

   What|Removed |Added

 CC||buschmann@huessenbergnetz.d
   ||e

--- Comment #1 from Matthias Fehring  ---
I have the same issue since upgrading my Nextcloud to version 17. At least I
think that started after the upgrade as I only recognized the issue with
Kontact/Korganizer today as it is working on my phone as expected.

Nextcloud throws an exception about a bad request with the following message:

"A calendar-query REPORT on a calendar with a Depth: 0 is undefined. Set Depth
to 1"

My system:
- openSUSE Tumbleweed
- Qt 5.13.1
- KDE Frameworks: 5.63.0
- KDE Plasma: 5.17
- KDE Applications: 19.08.2
- Kontact: 5.12.2

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

[Akonadi] [Bug 413201] Kmail crashes after check email

2019-10-23 Thread Norbert Blobel
https://bugs.kde.org/show_bug.cgi?id=413201

Norbert Blobel  changed:

   What|Removed |Added

 CC||m...@blobel.com

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

[kontact] [Bug 413355] New: Random Crash of Kontact

2019-10-23 Thread Paśnikowski Marek
https://bugs.kde.org/show_bug.cgi?id=413355

Bug ID: 413355
   Summary: Random Crash of Kontact
   Product: kontact
   Version: 5.12.2
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: m...@marekpasnikowski.name
  Target Milestone: ---

Application: kontact (5.12.2)

Qt Version: 5.13.1
Frameworks Version: 5.63.0
Operating System: Linux 5.3.6-1-default x86_64
Distribution: "openSUSE Tumbleweed"

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

I pressed the button to delete a journal entry. After restarting Kontact the
same action resulted in no crash.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
29return SYSCALL_CANCEL (poll, fds, nfds, timeout);
[Current thread is 1 (Thread 0x7fa47cf5af80 (LWP 3162))]

Thread 30 (Thread 0x7fa3e7853700 (LWP 7048)):
#0  __GI___libc_read (nbytes=10, buf=0x7fa3e785295e, fd=112) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=fd@entry=112, buf=buf@entry=0x7fa3e785295e,
nbytes=nbytes@entry=10) at ../sysdeps/unix/sysv/linux/read.c:24
#2  0x7fa4700f60f1 in read (__nbytes=10, __buf=0x7fa3e785295e, __fd=112) at
/usr/include/bits/unistd.h:44
#3  pa_read (fd=112, buf=buf@entry=0x7fa3e785295e, count=count@entry=10,
type=type@entry=0x55d721acc458) at pulsecore/core-util.c:422
#4  0x7fa471c4aa0e in clear_wakeup (m=) at
pulse/mainloop.c:782
#5  pa_mainloop_prepare (m=m@entry=0x55d721acc380, timeout=-1) at
pulse/mainloop.c:789
#6  0x7fa471c4b4b0 in pa_mainloop_iterate (m=0x55d721acc380,
block=, retval=0x0) at pulse/mainloop.c:923
#7  0x7fa471c4b570 in pa_mainloop_run (m=0x55d721acc380,
retval=retval@entry=0x0) at pulse/mainloop.c:945
#8  0x7fa471c59439 in thread (userdata=0x55d721a1f6f0) at
pulse/thread-mainloop.c:101
#9  0x7fa470123c78 in internal_thread_func (userdata=0x55d720c38860) at
pulsecore/thread-posix.c:81
#10 0x7fa47c79cf2a in start_thread (arg=) at
pthread_create.c:479
#11 0x7fa47d8034af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 29 (Thread 0x7fa3454d2700 (LWP 7047)):
#0  futex_abstimed_wait_cancelable (private=0, abstime=0x7fa3454d18e0,
clockid=, expected=0, futex_word=0x7fa3454d1a08) at
../sysdeps/unix/sysv/linux/futex-internal.h:208
#1  __pthread_cond_wait_common (abstime=0x7fa3454d18e0, clockid=, mutex=0x7fa3454d19b8, cond=0x7fa3454d19e0) at pthread_cond_wait.c:520
#2  __pthread_cond_timedwait (cond=0x7fa3454d19e0, mutex=0x7fa3454d19b8,
abstime=0x7fa3454d18e0) at pthread_cond_wait.c:656
#3  0x7fa475c4c486 in base::ConditionVariable::TimedWait () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127
#4  0x7fa475c4ce53 in base::WaitableEvent::TimedWaitUntil () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:230
#5  0x7fa475c4cfd1 in base::WaitableEvent::TimedWait () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:162
#6  0x7fa475c05141 in
base::internal::SchedulerWorker::Delegate::WaitForWork () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:37
#7  0x7fa475c07fdd in base::internal::SchedulerWorker::RunWorker () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:303
#8  0x7fa475c086d4 in base::internal::SchedulerWorker::RunPooledWorker ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:229
#9  0x7fa475c4f2c5 in ThreadFunc () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81
#10 0x7fa47c79cf2a in start_thread (arg=) at
pthread_create.c:479
#11 0x7fa47d8034af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 28 (Thread 0x7fa344cd1700 (LWP 6715)):
#0  0x7fa47d7f8bdf in __GI___poll (fds=0x7fa3f8002fe0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fa47bd3e2ae in g_main_context_poll (priority=,
n_fds=1, fds=0x7fa3f8002fe0, timeout=, context=0x7fa3f8000bf0)
at ../glib/gmain.c:4216
#2  g_main_context_iterate (context=context@entry=0x7fa3f8000bf0,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
../glib/gmain.c:3912
#3  0x7fa47bd3e3cf in g_main_context_iteration (context=0x7fa3f8000bf0,
may_block=may_block@entry=1) at ../glib/gmain.c:3978
#4  0x7fa47ddbf99b in QEventDispatcherGlib::processEvents
(this=0x7fa3f8002000, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7fa47dd680db in QEventLoop::exec (this=this@entry=0x7fa344cd0b20,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#6  0x7fa47dba0021 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#7  0x7fa47dba11a2 in