[kwin] [Bug 344326] Buffer objects (VBO, FBO) need remapping after suspend/vt switch with NVIDIA

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

Chris  changed:

   What|Removed |Added

  Attachment #99461|0   |1
is obsolete||

--- Comment #119 from Chris  ---
Created attachment 101458
  --> https://bugs.kde.org/attachment.cgi?id=101458&action=edit
Still happening in 5.8

I don't think the lock screen is affected by this anymore, at least for me. The
only thing I see affected anymore are the desktop labels.

Using Plasma 5.8 with the latest nvidia (370.28), GTX 980.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Planet KDE] [Bug 359327] Exiting game a in Steam Big Picture Mode gets semi-windowed BPM

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359327

Chris  changed:

   What|Removed |Added

 CC||emailofch...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[www.kde.org] [Bug 354585] IPv6 connections to https://dot.kde.org fail

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354585

--- Comment #11 from Chris  ---
Hi

I can confirm that I am now able to connect to https://dot.kde.org/ and
https://cdn.kde.org/css/bootstrap.css via IPv6.

I had previously blocked 2a02:e980::/29 at my firewall to force IPv4 while this
issue existed, but removing the block now allows IPv6 connectivity.

Thanks

-- 
You are receiving this mail because:
You are watching all bug changes.

[kontact] [Bug 371114] New: Kontact Crash on email filter edit

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=371114

Bug ID: 371114
   Summary: Kontact Crash on email filter edit
   Product: kontact
   Version: 5.2.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: crgla...@gmail.com

Application: kontact (5.2.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.31-30-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
I am trying to edit and existing filter to move the results to a new and
different folder on the first attempt.  When hitting OK oonthe filter window
Kontact crashes.  Upon restarting Kontact and going back to configure filters
the new folder is present.  Kontact crashed again though when I try to change
the destination to that folder.

The crash can be reproduced every time.

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

Thread 21 (Thread 0x7f0361ca7700 (LWP 16128)):
#0  0x7f0417023ccd in read () at /lib64/libc.so.6
#1  0x7f040631d073 in  () at /usr/lib64/tls/libnvidia-tls.so.367.57
#2  0x7f040fbc2b60 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f040fb81999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f040fb81df8 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f040fb81f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#6  0x7f0417b6bd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#7  0x7f0417b12d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#8  0x7f041793461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#9  0x7f041793932f in  () at /usr/lib64/libQt5Core.so.5
#10 0x7f041039f0a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7f041703002d in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7f03624a8700 (LWP 16125)):
#0  0x7f041703c5ff in __libc_enable_asynccancel () at /lib64/libc.so.6
#1  0x7f0417027bf2 in poll () at /lib64/libc.so.6
#2  0x7f040fb81e64 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f040fb81f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f0417b6bd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f0417b12d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f041793461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f041793932f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f041039f0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f041703002d in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7f03637fe700 (LWP 16112)):
#0  0x7f04103a579c in __lll_lock_wait () at /lib64/libpthread.so.0
#1  0x7f04103a14a4 in _L_lock_986 () at /lib64/libpthread.so.0
#2  0x7f04103a1306 in pthread_mutex_lock () at /lib64/libpthread.so.0
#3  0x7f040f1f881c in  () at /usr/X11R6/lib64/libGL.so.1
#4  0x7f040f1fd741 in  () at /usr/X11R6/lib64/libGL.so.1
#5  0x7f040f1fdc58 in  () at /usr/X11R6/lib64/libGL.so.1
#6  0x7f040631d102 in  () at /usr/lib64/tls/libnvidia-tls.so.367.57
#7  0x7f040fbc2b60 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f040fb81999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f040fb81df8 in  () at /usr/lib64/libglib-2.0.so.0
#10 0x7f040fb81f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#11 0x7f0417b6bd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#12 0x7f0417b12d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#13 0x7f041793461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#14 0x7f041793932f in  () at /usr/lib64/libQt5Core.so.5
#15 0x7f041039f0a4 in start_thread () at /lib64/libpthread.so.0
#16 0x7f041703002d in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7f0363fff700 (LWP 16110)):
#0  0x7f0417027bfd in poll () at /lib64/libc.so.6
#1  0x7f040fb81e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f040fb81f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f0417b6bd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f0417b12d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f041793461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f041793932f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f041039f0a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f041703002d in clone () at /lib64/libc.so.6

Thread 17 (Thread 0x7f03718b2700 (LWP 16108)):
#0  0x7f0417027bfd in poll () at /lib64/libc.so.6
#1  0x7f040fb81e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f040fb81f7c in g

[okular] [Bug 357526] Annotation can not be saved automatically for a specific PDF file.

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357526

--- Comment #4 from Chris  ---
(In reply to Steven Roose from comment #3)
> Should be solved by this issue: https://bugs.kde.org/show_bug.cgi?id=350991

It wouldn't to me, because the "annotations" which are not saved here (I mean
bug 357536) are stored externally, which is a behavior more convenient in many
cases because it does not modify the original document neither does it create
copies of it...

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 357526] Annotation can not be saved automatically for a specific PDF file.

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357526

--- Comment #5 from Chris  ---
Here is a workaround, from #ghostscript irc channel:

gs -dBATCH -dNOPAUSE -sDEVICE=pdfwrite -dShowAnnots=false
-sOutputFile=stripped.pdf input.pdf

(refer to http://ghostscript.com/irclogs/ at date 2016-06-30 for caveat; as
expressed it might modify the original file during the process of removing the
annotations; and cleaner solution should be attained using "mutool run".)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kontact] [Bug 365167] New: Kmail hangs on spell check

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365167

Bug ID: 365167
   Summary: Kmail hangs on spell check
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: crgla...@gmail.com

Application: kontact (5.2.2)

Qt Version: 5.5.1
Operating System: Linux 4.1.26-21-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
I have tried 3 times to send an email that has a unique spelling to a name.  I
would choose the option to add to dictionary but Kmail is hanging and then
generates this crash.

The crash can be reproduced every time.

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

Thread 18 (Thread 0x7fc340a7a700 (LWP 9180)):
#0  0x7fc359f2ebbd in poll () from /lib64/libc.so.6
#1  0x7fc3536c8422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7fc3536ca00f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7fc3431fc3c9 in QXcbEventReader::run (this=0x1344500) at
qxcbconnection.cpp:1229
#4  0x7fc35a84032f in QThreadPrivate::start (arg=0x1344500) at
thread/qthread_unix.cpp:331
#5  0x7fc3532a50a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7fc359f36fed in clone () from /lib64/libc.so.6

Thread 17 (Thread 0x7fc337460700 (LWP 9181)):
#0  0x7fc3532a903f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fc357843733 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7fc357843759 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7fc3532a50a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7fc359f36fed in clone () from /lib64/libc.so.6

Thread 16 (Thread 0x7fc2ee16b700 (LWP 9191)):
#0  0x7fc359f2ac8d in read () from /lib64/libc.so.6
#1  0x7fc34950f073 in ?? () from /usr/lib64/tls/libnvidia-tls.so.367.27
#2  0x7fc352ac8b60 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7fc352a87999 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#4  0x7fc352a87df8 in ?? () from /usr/lib64/libglib-2.0.so.0
#5  0x7fc352a87f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#6  0x7fc35aa72d8b in QEventDispatcherGlib::processEvents
(this=0x7fc2e80008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#7  0x7fc35aa19d53 in QEventLoop::exec (this=this@entry=0x7fc2ee16ae10,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#8  0x7fc35a83b61a in QThread::exec (this=) at
thread/qthread.cpp:503
#9  0x7fc35a84032f in QThreadPrivate::start (arg=0x1490fe0) at
thread/qthread_unix.cpp:331
#10 0x7fc3532a50a4 in start_thread () from /lib64/libpthread.so.0
#11 0x7fc359f36fed in clone () from /lib64/libc.so.6

Thread 15 (Thread 0x7fc2e7fff700 (LWP 9192)):
#0  0x7fc3532a903f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fc35754f75d in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7fc357872031 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7fc3532a50a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7fc359f36fed in clone () from /lib64/libc.so.6

Thread 14 (Thread 0x7fc2e77fe700 (LWP 9193)):
#0  0x7fc3532a903f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fc357550733 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7fc357872031 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7fc3532a50a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7fc359f36fed in clone () from /lib64/libc.so.6

Thread 13 (Thread 0x7fc2e6ffd700 (LWP 9194)):
#0  0x7fc3532a903f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fc357550733 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7fc357872031 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7fc3532a50a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7fc359f36fed in clone () from /lib64/libc.so.6

Thread 12 (Thread 0x7fc2e67fc700 (LWP 9195)):
#0  0x7fc3532a903f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fc357550733 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7fc357872031 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7fc3532a50a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7fc359f36fed in clone () from /lib64/libc.so.6

Thread 11 (Thread 0x7fc2cd2c6700 (LWP 9200)):
#0  0x7fc359f2ac8d in read () from /lib64/libc.so.6
#1  0x7fc34950f073 in ?? () from /usr/lib64/tls/libnvidia-tls.so.367.27
#2  0x7fc352ac8b60 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7fc352a87999 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#4  0x7fc352a87df8 in ?? () from /usr/lib64/libglib-2.0.so.0
#5 

[kontact] [Bug 365489] New: Unknown cause of crash

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365489

Bug ID: 365489
   Summary: Unknown cause of crash
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: crgla...@gmail.com

Application: kontact (5.2.2)

Qt Version: 5.5.1
Operating System: Linux 4.1.26-21-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
I have been having trouble with Akonadi server stopping on one of 5 imap
accounts.  My work arund is to start "akonadiconsole" then do a stop server and
start server.  This usually brings back the errant impa account.  However today
this crash has been occuring when I open Kontact and review email.  It has
happend three times consecutivly.  I'm sorry I cannot tell you more.

The crash can be reproduced every time.

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

Thread 17 (Thread 0x7fab25b21700 (LWP 3727)):
#0  0x7fab3efd9bfd in poll () at /lib64/libc.so.6
#1  0x7fab38773422 in  () at /usr/lib64/libxcb.so.1
#2  0x7fab3877500f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fab282a33c9 in QXcbEventReader::run() (this=0x15d60f0) at
qxcbconnection.cpp:1229
#4  0x7fab3f8eb32f in QThreadPrivate::start(void*) (arg=0x15d60f0) at
thread/qthread_unix.cpp:331
#5  0x7fab383500a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7fab3efe202d in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7fab1c421700 (LWP 3728)):
#0  0x7fab3835403f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fab3c8ee733 in WTF::TCMalloc_PageHeap::scavengerThread() () at
/usr/lib64/libQt5WebKit.so.5
#2  0x7fab3c8ee759 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) ()
at /usr/lib64/libQt5WebKit.so.5
#3  0x7fab383500a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fab3efe202d in clone () at /lib64/libc.so.6

Thread 15 (Thread 0x7faad3225700 (LWP 3729)):
#0  0x7fab3835679c in __lll_lock_wait () at /lib64/libpthread.so.0
#1  0x7fab383524a4 in _L_lock_986 () at /lib64/libpthread.so.0
#2  0x7fab38352306 in pthread_mutex_lock () at /lib64/libpthread.so.0
#3  0x7fab371aa77c in  () at /usr/X11R6/lib64/libGL.so.1
#4  0x7fab371af651 in  () at /usr/X11R6/lib64/libGL.so.1
#5  0x7fab371afb58 in  () at /usr/X11R6/lib64/libGL.so.1
#6  0x7fab2e5ba102 in  () at /usr/lib64/tls/libnvidia-tls.so.367.27
#7  0x7fab37b73b60 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fab37b32999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#9  0x7fab37b32df8 in  () at /usr/lib64/libglib-2.0.so.0
#10 0x7fab37b32f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#11 0x7fab3fb1dd8b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7faacc0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#12 0x7fab3fac4d53 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7faad3224e10, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#13 0x7fab3f8e661a in QThread::exec() (this=) at
thread/qthread.cpp:503
#14 0x7fab3f8eb32f in QThreadPrivate::start(void*) (arg=0x1729310) at
thread/qthread_unix.cpp:331
#15 0x7fab383500a4 in start_thread () at /lib64/libpthread.so.0
#16 0x7fab3efe202d in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7faad188e700 (LWP 3730)):
#0  0x7fab3835403f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fab3c5fa75d in JSC::BlockAllocator::blockFreeingThreadMain() () at
/usr/lib64/libQt5WebKit.so.5
#2  0x7fab3c91d031 in wtfThreadEntryPoint() () at
/usr/lib64/libQt5WebKit.so.5
#3  0x7fab383500a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fab3efe202d in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7faad105e700 (LWP 3731)):
#0  0x7fab3835403f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fab3c5fb733 in JSC::GCThread::gcThreadMain() () at
/usr/lib64/libQt5WebKit.so.5
#2  0x7fab3c91d031 in wtfThreadEntryPoint() () at
/usr/lib64/libQt5WebKit.so.5
#3  0x7fab383500a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fab3efe202d in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7faad085d700 (LWP 3732)):
#0  0x7fab3835403f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fab3c5fb733 in JSC::GCThread::gcThreadMain() () at
/usr/lib64/libQt5WebKit.so.5
#2  0x7fab3c91d031 in wtfThreadEntryPoint() () at
/usr/lib64/libQt5WebKit.so.5
#3  0x7fab383500a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fab3efe202d in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7faac3fff700 (LWP 3733)):
#0  0x7fab3

[kwin] [Bug 344326] Buffer objects (VBO, FBO) need remapping after suspend/vt switch with NVIDIA

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

--- Comment #116 from Chris  ---
Created attachment 100142
  --> https://bugs.kde.org/attachment.cgi?id=100142&action=edit
Labels of desktop items in Folder View now have various glitches after wake.

We got new Nvidia drivers this weekend, but after an update, reboot, suspend
and wake, I see there's very much still issues here, at least for me. The
corruption is actually more "diverse" this time.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdesu] [Bug 349668] kdesu freeze if two-factor authentication pam is set

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=349668

Chris  changed:

   What|Removed |Added

 CC||riddo...@gmail.com

--- Comment #1 from Chris  ---
I have the same issue, also with the same configuration line.  If I had the
time, I'd try to fix this, but right now all I can do is confirm the problem. 
It appears to time out, given a couple minutes, to return a 'permission
denied'.

In case someone has doubts about it, ordinary sudo in my terminal works, as
does my ssh configuration.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365918] New: Severe flickering when interacting with some windows

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365918

Bug ID: 365918
   Summary: Severe flickering when interacting with some windows
   Product: kwin
   Version: 5.7.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: scene-opengl
  Assignee: kwin-bugs-n...@kde.org
  Reporter: emailofch...@gmail.com

When I use GLX as my backend, everything works fine (though I do experience
tearing sometimes, though that's a separate issue that's partly thanks to
Nvidia). And as of a recent update that included xorg-server and some others,
using OpenGL as the backend causes severe flickering on the desktop or entire
screen.

Since this can't be captured with a screenshot, I'm going to capture a video of
it. This will take a bit more time, so I'll be linking that in a while.

Reproducible: Always

Steps to Reproduce:
1. Switch to one of the two OpenGL backends.
2. Open one or a few new Dolphin windows, for example.
3. Move the cursor around on top of it.

Actual Results:  
Flickering in areas of the screen.

Expected Results:  
Nothing out of the ordinary should happen.

Using Nvidia might or might not be a factor.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365918] Severe flickering when interacting with some windows

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365918

--- Comment #1 from Chris  ---
Well, now I can't duplicate what was happening. Well, I'll post another comment
here when it starts happening again...

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 366053] New: Let me rearrange launchers on the task manager panel

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366053

Bug ID: 366053
   Summary: Let me rearrange launchers on the task manager panel
   Product: plasmashell
   Version: master
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: emailofch...@gmail.com
CC: plasma-b...@kde.org

I can't tell what sorting method is used for the launchers on the panel, and I
see no option to change it. It would be nice if I could choose the order
myself, as you can on the Windows taskbar or on the OS X dock.

Reproducible: Always

Steps to Reproduce:
1. Unlock widgets?
2. Try to click and drag a launcher to a different spot within the group of
launchers.

Actual Results:  
Nothing happens.

Expected Results:  
I should be able to swap their positions and/or move one between two others.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365918] Severe flickering when interacting with some windows

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365918

Chris  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Chris  ---
Not sure why but I wasn't emailed for this. Strange. Anyway, I'll go ahead and
close this bug - whatever glitch I was experiencing, I wasn't able to reproduce
it for long after I wrote the report, and it had stopped happening by the time
I tried capturing it with OBS.

I don't remember exactly, but I do remember that it wasn't happening with
XRender, but I don't know why I was referring to GLX as "working" but "OpenGL"
as not working. Maybe I meant EGL? Well, regardless, it's back to normal now.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 366239] New: Feature Request: Missing features found in KSnapshot

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366239

Bug ID: 366239
   Summary: Feature Request: Missing features found in KSnapshot
   Product: Spectacle
   Version: unspecified
  Platform: Slackware Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: chrisret...@gmx.com

Spectacle Version 16.04.3 using KDE 5_16.07 for Slackware, consisting of the
KDE Frameworks 5.24.0, Plasma 5.7.2 and Applications 16.04.3 on top of Qt
5.6.1.

Spectacle looks to be a good replacement for KSnapshot. One of the things
KSnapshot had that Spectacle does not is the Section of Windows and Freehand
Region mode of taking a screenshot. Section of Windows is really handy for
capturing sections of windows such an the section inside the window. It would
be awesome if these two mode with added to Spectacle.




Reproducible: Always

Steps to Reproduce:
NA: Feature Request

Actual Results:  
NA: Feature Request

Expected Results:  
NA: Feature Request

NA: Feature Request

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 366239] Feature Request: Missing features found in KSnapshot

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366239

--- Comment #3 from Chris  ---
I used freehand selection, so at least one person used it. Bet there was a few
more than no one. ;-) Looking forward to the image editor is completion.

To bad about the Section of Windows being dropped it was a great feature (in my
opinion at least). I used the Section of Window a lot, never had program that
it failed to work with. At any rate, Rectangular Region can substitute for
Section of Window, but it is not as convenient since you have to make
adjustments to get the section you want in the screenshot. No adjustment needed
with Section of Window. Thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 354550] Tracks shorten themselves upon re-opening the project

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354550

Chris  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Chris  ---
I did try this with the most recent stable version of kdenlive and it seems to
me that the bug is now fixed. Could not reproduce this effect anymore. Thanks
:)

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 366325] New: Crash after update Aug 1, 2016

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366325

Bug ID: 366325
   Summary: Crash after update Aug 1, 2016
   Product: ksmserver
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: l.lu...@kde.org
  Reporter: crgla...@gmail.com

Application: ksmserver ()

Qt Version: 5.5.1
Operating System: Linux 4.1.27-27-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
System updated and on  a re-boot Plasma crashed for the OpenSuSE LEAP 42.1
distribution.  Dumbing down kernel to see if it works.  This has been the
typical workaround until someone relaizes the mistake in packaging.

The crash can be reproduced every time.

-- Backtrace:
Application: ksmserver (ksmserver), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa2c9d0e800 (LWP 3912))]

Thread 2 (Thread 0x7fa28d1a9700 (LWP 4765)):
#0  0x7fa2c9648ccd in read () at /lib64/libc.so.6
#1  0x7fa2b9a33073 in  () at /usr/lib64/tls/libnvidia-tls.so.367.35
#2  0x7fa2bdbb3b60 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fa2bdb72999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fa2bdb72df8 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7fa2bdb72f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#6  0x7fa2c4212d8b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fa264001600, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#7  0x7fa2c41b9d53 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fa28d1a8db0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#8  0x7fa2c3fdb61a in QThread::exec() (this=this@entry=0xbbf260) at
thread/qthread.cpp:503
#9  0x7fa2c7805e18 in QQmlThreadPrivate::run() (this=0xbbf260) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#10 0x7fa2c3fe032f in QThreadPrivate::start(void*) (arg=0xbbf260) at
thread/qthread_unix.cpp:331
#11 0x7fa2bf4c50a4 in start_thread () at /lib64/libpthread.so.0
#12 0x7fa2c965502d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fa2c9d0e800 (LWP 3912)):
[KCrash Handler]
#6  0x7fa2c95a50c7 in raise () at /lib64/libc.so.6
#7  0x7fa2c95a6478 in abort () at /lib64/libc.so.6
#8  0x7fa2c3fce7ce in QMessageLogger::fatal(char const*, ...) const
(context=..., message=) at global/qlogging.cpp:1578
#9  0x7fa2c3fce7ce in QMessageLogger::fatal(char const*, ...) const
(this=this@entry=0x7ffc86287700, msg=msg@entry=0x7fa2c7e500aa "%s") at
global/qlogging.cpp:781
#10 0x7fa2c7ccbe71 in
QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool)
(this=this@entry=0xbc8480, window=0xaadb60, isEs=isEs@entry=false) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/quick/scenegraph/qsgrenderloop.cpp:244
#11 0x7fa2c7cccdf5 in QSGGuiThreadRenderLoop::renderWindow(QQuickWindow*)
(this=this@entry=0xbc8480, window=0xaadb60) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/quick/scenegraph/qsgrenderloop.cpp:333
#12 0x7fa2c7ccdb5e in
QSGGuiThreadRenderLoop::exposureChanged(QQuickWindow*) (this=0xbc8480,
window=0xaadb60) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/quick/scenegraph/qsgrenderloop.cpp:422
#13 0x7fa2c4715b69 in QWindow::event(QEvent*) (this=this@entry=0xaadb60,
ev=ev@entry=0x7ffc86287ba0) at kernel/qwindow.cpp:2028
#14 0x7fa2c7d060d1 in QQuickWindow::event(QEvent*) (this=0xaadb60,
e=0x7ffc86287ba0) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/quick/items/qquickwindow.cpp:1413
#15 0x7fa2c4e9fe7c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=this@entry=0x9cb8c0, receiver=receiver@entry=0xaadb60,
e=e@entry=0x7ffc86287ba0) at kernel/qapplication.cpp:3716
#16 0x7fa2c4ea4cc8 in QApplication::notify(QObject*, QEvent*)
(this=0x9cb8a0, receiver=0xaadb60, e=0x7ffc86287ba0) at
kernel/qapplication.cpp:3499
#17 0x7fa2c41bbe95 in QCoreApplication::notifyInternal(QObject*, QEvent*)
(this=0x9cb8a0, receiver=receiver@entry=0xaadb60,
event=event@entry=0x7ffc86287ba0) at kernel/qcoreapplication.cpp:965
#18 0x7fa2c470e5d4 in
QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*)
(event=0x7ffc86287ba0, receiver=0xaadb60) at
../../src/corelib/kernel/qcoreapplication.h:227
#19 0x7fa2c470e5d4 in
QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*)
(e=0xc164b0) at kernel/qguiapplication.cpp:2650
#20 0x7fa2c470f1ed in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
(e=e@entry=0xc164b0) at kernel/qguiapplication.cpp:1645
#21 0x7fa2c46f4268 in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
(flags=...) at kernel/qwindowsysteminterface.cpp:625
#22 0x7fa2b3e6d

[kdenlive] [Bug 354549] Audio tracks auto-mute depending on their order

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354549

Chris  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED

--- Comment #3 from Chris  ---
Hello Wegwerf,

Sorry for the late post but unfortunately I didn't have an old project
available anymore so I created one using the current 16.04 and loaded it up in
16.07.90. And it behaved as you described. So until something new pops up, I'll
mark this bug as fixed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 348985] Clips with speed effect break if video properties altered

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=348985

Chris  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Chris  ---
I can confirm that with the new Speed Effect (which I really like, Thank you
:)) this problem is fixed. 

I did notice however in the new version that if you make a clip so slow that it
would overlap another one on the same track, this clip seems to be pushed back
upon reloading the project.
I need to investigate this more however and write up the exact steps to
reproduce this. 

But this bug in particular is fixed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 366416] New: Speed Effect on cropped clip can mess up the timeline

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366416

Bug ID: 366416
   Summary: Speed Effect on cropped clip can mess up the timeline
   Product: kdenlive
   Version: 16.04.0
  Platform: Other
   URL: https://www.youtube.com/watch?v=ElvrAlIOEHQ
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: ch...@8bit-memories.com

If you have a CROPPED video clip (i.e. cut part of the ending) and apply the
speed effect to it, depending on the setting of the speed, this clip may
overlap another clip on the same video track. 
Saving and Reloading the project in this state will mess up the timeline.
However even working on the project as this overlap happens can yield some
rather random results (and/or a crash).

Reproducible: Always

Steps to Reproduce:
1. Make a new project with at least two video clips of any length.
2. Add the first clip to VIDEO 1 and crop part of its end.
3. Add the second clip on the same track (VIDEO 1) right after the first
4. Apply a SPEED EFFECT to the first video track.
5. Drag the speed slider around until the video clip will eventually overlap
the following one. This may be tricky and requires some playing around with the
speed slider.
6. After both clips overlap each other, save the project (the project is
already messed up at this point and kdenlive may not play the second clip if
playing the project or even crash)
7. Load your project again and see how the second video clip is pushed back.

Actual Results:  
The second video clip is pushed back in the timeline. But only after the
project reloads.

Expected Results:  
As it happend if the first video clip is NOT cropped, kdenlive will
automatically crop it so it cannot overlap the following clip.

This bug ONLY WORKS if you crop the end of the clip BEFORE you apply the speed
effect to it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 348985] Clips with speed effect break if video properties altered

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=348985

--- Comment #5 from Chris  ---
No problem. Already did that. :)
https://bugs.kde.org/show_bug.cgi?id=366416
I have also recorded a small video to demonstrate the bug (it's linked in the
report).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kontact] [Bug 366417] New: Crashed while deleting trash

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366417

Bug ID: 366417
   Summary: Crashed while deleting trash
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: crgla...@gmail.com

Application: kontact (5.2.3)

Qt Version: 5.7.0
Frameworks Version: 5.24.0
Operating System: Linux 4.1.27-24-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
I was manually deleting the local trash folder when Kontact crashed today.

The crash can be reproduced every time.

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

Thread 23 (Thread 0x7ff529789700 (LWP 3215)):
#0  0x7ff5436abbfd in poll () at /lib64/libc.so.6
#1  0x7ff53ce35422 in  () at /usr/lib64/libxcb.so.1
#2  0x7ff53ce3700f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7ff52c1103e9 in QXcbEventReader::run() (this=0xc5db10) at
qxcbconnection.cpp:1337
#4  0x7ff543fc2899 in QThreadPrivate::start(void*) (arg=0xc5db10) at
thread/qthread_unix.cpp:344
#5  0x7ff53ca120a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7ff5436b402d in clone () at /lib64/libc.so.6

Thread 22 (Thread 0x7ff520dad700 (LWP 3216)):
#0  0x7ff53ac91cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7ff53ac4f4b9 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7ff53ac4fd80 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7ff53ac4ff7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7ff5441c7f7b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7ff51c0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7ff5441778cb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7ff520dacde0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#6  0x7ff543fbe06a in QThread::exec() (this=) at
thread/qthread.cpp:507
#7  0x7ff5428f44b5 in  () at /usr/lib64/libQt5DBus.so.5
#8  0x7ff543fc2899 in QThreadPrivate::start(void*) (arg=0x7ff542b5dd00) at
thread/qthread_unix.cpp:344
#9  0x7ff53ca120a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7ff5436b402d in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7ff51b5ef700 (LWP 3217)):
#0  0x7ff53ca1603f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff540fb25d3 in WTF::TCMalloc_PageHeap::scavengerThread() () at
/usr/lib64/libQt5WebKit.so.5
#2  0x7ff540fb25f9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) ()
at /usr/lib64/libQt5WebKit.so.5
#3  0x7ff53ca120a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7ff5436b402d in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7ff4d2429700 (LWP 3219)):
#0  0x7ff5436abbfd in poll () at /lib64/libc.so.6
#1  0x7ff53ac4fe64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7ff53ac4ff7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ff5441c7f7b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7ff4cc0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7ff5441778cb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7ff4d2428e10, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#5  0x7ff543fbe06a in QThread::exec() (this=) at
thread/qthread.cpp:507
#6  0x7ff543fc2899 in QThreadPrivate::start(void*) (arg=0xe1e900) at
thread/qthread_unix.cpp:344
#7  0x7ff53ca120a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7ff5436b402d in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7ff4d0aa7700 (LWP 3220)):
#0  0x7ff53ca1603f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff540cbe46d in JSC::BlockAllocator::blockFreeingThreadMain() () at
/usr/lib64/libQt5WebKit.so.5
#2  0x7ff540fe10a1 in wtfThreadEntryPoint() () at
/usr/lib64/libQt5WebKit.so.5
#3  0x7ff53ca120a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7ff5436b402d in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7ff4cbfff700 (LWP 3221)):
#0  0x7ff53ca1603f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff540cbf443 in JSC::GCThread::gcThreadMain() () at
/usr/lib64/libQt5WebKit.so.5
#2  0x7ff540fe10a1 in wtfThreadEntryPoint() () at
/usr/lib64/libQt5WebKit.so.5
#3  0x7ff53ca120a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7ff5436b402d in clone () at /lib64/libc.so.6

Thread 17 (Thread 0x7ff4cb7fe700 (LWP 3222)):
#0  0x7ff53ca1603f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff540cbf443 in JSC::GCThread::gcThreadMain() () at
/usr/lib64/libQt5WebKit.so.5
#2  0x7ff540fe10a1 in wtfThreadEntryPoint() () at
/usr/lib64/libQt5WebKit.so.5
#3

[plasmashell] [Bug 366053] Let me rearrange launchers on the task manager panel

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366053

--- Comment #2 from Chris  ---
Oops, I didn't see that. Thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365918] Severe flickering when interacting with some windows

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365918

Chris  changed:

   What|Removed |Added

 Resolution|INVALID |---
 Status|RESOLVED|UNCONFIRMED

--- Comment #4 from Chris  ---
It's back! And I managed to capture it this time - OBS couldn't catch it, so I
used a camera instead. I have a feeling this could be difficult to reproduce
after I boot up again. I don't know what started this.

https://www.youtube.com/watch?v=_FVmg6IqMtw

Here's it not flickering with XRender:

https://www.youtube.com/watch?v=b2dKgvjV41k

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365918] Severe flickering when interacting with some windows

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365918

--- Comment #5 from Chris  ---
And a little more testing with a properly focused camera, back to OpenGL:
https://www.youtube.com/watch?v=VfavT_a6U-M

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365918] Sometimes flickering when interacting with windows

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365918

Chris  changed:

   What|Removed |Added

Summary|Severe flickering when  |Sometimes flickering when
   |interacting with some   |interacting with windows
   |windows |

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365918] Sometimes flickering when interacting with windows

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365918

--- Comment #7 from Chris  ---
Created attachment 100499
  --> https://bugs.kde.org/attachment.cgi?id=100499&action=edit
KWin Support Information

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365918] Sometimes flickering when interacting with windows

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365918

--- Comment #8 from Chris  ---
I should also mention: this doesn't happen if a window has no titlebar/frame as
set in Window Rules. The flickering doesn't happen when I open Firefox, because
I got rid of the titlebar/frame for it (I use Tree Style Tabs) and I just
tested that with Dolphin, and the flickering doesn't happen when opening a
Dolphin window now either.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365918] Sometimes flickering when interacting with windows

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365918

--- Comment #10 from Chris  ---
I did try that ("Switch to one of the two OpenGL backends") and it didn't work,
unfortunately.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365918] Sometimes flickering when interacting with windows

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365918

--- Comment #13 from Chris  ---
I actually still can't figure out how to trigger that behavior when I want to.
It just seems to happen randomly. I've since rebooted, which gets rid of the
issue indefinitely. It may crop up again, as it did before. Should I go ahead
and disable those effects anyway (and change the buffer method too?) and see if
it comes back?

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 369195] New: Consider Djvu files as documents

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369195

Bug ID: 369195
   Summary: Consider Djvu files as documents
   Product: frameworks-baloo
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: pinak.ah...@gmail.com
  Reporter: inkbottle...@gmail.com

When I do "find" in Dolphin and then select "Documents", I've got Pdf files but
not Djvu files. Djvu files might nowadays be considered as some sort of
alternative for pdf files; they might be searchable, or not, but so are pdf
files.

I wish djvu files could be considered as documents.

I suppose it is the right product to fill the bug because in the past the
request "search:/documents" was transmitted to Nepomuk which functionalities
should now be in Baloo.

Also there is a commit from 2013:
http://quickgit.kde.org/?p=baloo.git&a=commitdiff&h=2e3076f8094b6fe7dce2077033698847a709bb80
"Consider text files as documents", which is a hint in this direction.

(kw: kde plasma dolphin find search document pdf djvu nepomuk baloo file)

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365918] Sometimes flickering when interacting with windows

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365918

Chris  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #17 from Chris  ---
Hasn't happened for a good while. I'll go ahead and say this was probably
fixed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 365742] Individual Settings for different Versions of Kate and Katepart

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365742

Chris  changed:

   What|Removed |Added

 CC||k...@ontoemail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 365742] Individual Settings for different Versions of Kate and Katepart

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365742

--- Comment #1 from Chris  ---
I am also affected by this bug after switching from KDE 4. I use Kate as a
plain text editor (no line numbers, etc.), and use KDevelop for programming
(show line numbers, etc.). Being forced to use the same editor settings means I
am forced to choose between Kate and KDevelop. It appears that the only way to
get my previous setup would be to use a GTK based text editor to replace Kate.

For me, the best solution would be if I could setup my "global" settings in
Kate, then tick a box in KDevelop editor settings saying "program specific
settings" and setup my programming environment.

My System: Linux Mint 18 with Kate 15.12.3 (from packages) and KDevelop 5.0.1
(compiled from source).

-- 
You are receiving this mail because:
You are watching all bug changes.

[QtCurve] [Bug 363703] Popup Menu shadows not configurable

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363703

Chris  changed:

   What|Removed |Added

 CC||k...@ontoemail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kontact] [Bug 369798] New: Exziting Kontact

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369798

Bug ID: 369798
   Summary: Exziting Kontact
   Product: kontact
   Version: 5.2.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: crgla...@gmail.com

Application: kontact (5.2.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.31-30-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
All I am doing is exiting Kontact and this carsh occurs.  Am I missing
something? Meaning have I some dependency issue?

The crash can be reproduced every time.

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

Thread 6 (Thread 0x7ffa567fc700 (LWP 5064)):
#0  0x7ffac272803f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ffac69cf733 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7ffac6cf1031 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7ffac27240a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7ffac93b502d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7ffa56ffd700 (LWP 5063)):
#0  0x7ffac272803f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ffac69cf733 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7ffac6cf1031 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7ffac27240a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7ffac93b502d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7ffa577fe700 (LWP 5062)):
#0  0x7ffac272803f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ffac69cf733 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7ffac6cf1031 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7ffac27240a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7ffac93b502d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7ffa57fff700 (LWP 5061)):
#0  0x7ffac272803f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ffac69ce75d in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7ffac6cf1031 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7ffac27240a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7ffac93b502d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7ffaa687f700 (LWP 5059)):
#0  0x7ffac272803f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ffac6cc2733 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7ffac6cc2759 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7ffac27240a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7ffac93b502d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7ffacc767800 (LWP 5057)):
[KCrash Handler]
#6  0x7ffac93050c7 in raise () at /lib64/libc.so.6
#7  0x7ffac9306478 in abort () at /lib64/libc.so.6
#8  0x7ffac9342784 in  () at /lib64/libc.so.6
#9  0x7ffac9348026 in malloc_printerr () at /lib64/libc.so.6
#10 0x7ffac9348d53 in _int_free () at /lib64/libc.so.6
#11 0x7ffac503c1e7 in KIconTheme::~KIconTheme() () at
/usr/lib64/libKF5IconThemes.so.5
#12 0x7ffac502fb31 in  () at /usr/lib64/libKF5IconThemes.so.5
#13 0x7ffac5036e39 in KIconLoader::~KIconLoader() () at
/usr/lib64/libKF5IconThemes.so.5
#14 0x7ffac50371e9 in  () at /usr/lib64/libKF5IconThemes.so.5
#15 0x7ffac9307b39 in __run_exit_handlers () at /lib64/libc.so.6
#16 0x7ffac9307b85 in  () at /lib64/libc.so.6
#17 0x7ffac92f1b2c in __libc_start_main () at /lib64/libc.so.6
#18 0x00404ca7 in _start ()

Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 371413] New: I don't know what happened after an update of the Kernel and possibly Virtualbox

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=371413

Bug ID: 371413
   Summary: I don't know what happened after an update of the
Kernel and possibly Virtualbox
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: crgla...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.1.31-30-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
I am osrry to be vague in the title but I  really don't know what has happened.
 Yesterday I received a notice from ORacle that a new versionof VirtualBox was
available.  I downloaded and installed it.  I also had an automatic update from
through for security issues (cannot remember the details) from OpenSuSE.  They
may not be related. But now Plasma is not working.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f99830ad7c0 (LWP 3116))]

Thread 7 (Thread 0x7f98c3fff700 (LWP 3149)):
#0  0x7f9978c921d7 in  () at /usr/lib64/libglib-2.0.so.0
#1  0x7f9978c9483f in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f9978c94df8 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f9978c94f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f997cee5d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f997ce8cd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f997ccae61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f9980b5e282 in  () at /usr/lib64/libQt5Quick.so.5
#8  0x7f997ccb332f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f997bdc20a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f997c5c102d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f994f1c2700 (LWP 3147)):
#0  0x7f997bdc603f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f998279186b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f9982791899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f997bdc20a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f997c5c102d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f9954b80700 (LWP 3146)):
#0  0x7f9978cd6cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f9978c948fc in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f9978c94df8 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f9978c94f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f997cee5d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f997ce8cd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f997ccae61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f997ffc2e18 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7f997ccb332f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f997bdc20a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f997c5c102d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f995647a700 (LWP 3145)):
#0  0x7f9978c944f1 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#1  0x7f9978c94d80 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f9978c94f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f997cee5d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f997ce8cd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f997ccae61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f997ffc2e18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f997ccb332f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f997bdc20a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f997c5c102d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f996205e700 (LWP 3135)):
#0  0x7f997c5b4ccd in read () at /lib64/libc.so.6
#1  0x7f9974756073 in  () at /usr/lib64/tls/libnvidia-tls.so.367.57
#2  0x7f9978cd5b60 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f9978c94999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f9978c94df8 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f9978c94f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#6  0x7f997cee5d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#7  0x7f997ce8cd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#8  0x7f997ccae61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#9  0x7f997ffc2e18 in  () at /usr/lib64/libQt5Qml.so.5
#10 0

[plasmashell] [Bug 362941] Java Process Is Unresponsive In System Tray - Jitsi

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362941

Chris  changed:

   What|Removed |Added

 CC||altpap...@gmx.net

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdemultimedia] [Bug 368472] New: PulseAudio streams are moved to KDE's preferred audio device for certain non-KDE apps that try to use a specific device

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368472

Bug ID: 368472
   Summary: PulseAudio streams are moved to KDE's preferred audio
device for certain non-KDE apps that try to use a
specific device
   Product: kdemultimedia
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kde-multime...@kde.org
  Reporter: chris.k...@gmail.com

Using KDE Platform Version 4.14.2.

When OpenAL Soft  is set to use PulseAudio for output,
and is configured to allow output streams to be moved during playback, KDE will
see the stream it creates and forcefully move it to the preferred audio device
as set in the System Settings. This occurs even when the stream is explicitly
connected to a specific device by the app, and even if the app was previously
moved to a different device through kmix or pavucontrol. This effectively makes
it impossible for any OpenAL app to open a specific device when playback is
movable, and instead has to be moved onto the desired device after starting.

Other applications, such as Firefox, do not exhibit this behavior. They will
use the device that they were last set to use through pavucontrol. Unloading
module-device-manager from PulseAudio works around the problem by preventing
KDE from handling specific devices, though is obviously less than ideal.

Ideally, what I'd like to see happen, is that if an app has OpenAL Soft connect
to the default device, KDE can manage it and keep it on the preferred audio
device as the device list changes, but when it connects to a specific device,
it leaves it on that device. Or failing that, to simply not ever move it on its
own.

Reproducible: Always

Steps to Reproduce:
1. Install a recent Git version of OpenAL Soft (with PulseAudio support, and
with examples if you don't have another OpenAL app to run). A recent release
may work too, but the examples in those versions don't have an option to play
on a specific device.
2. Configure OpenAL Soft to allow PulseAudio streams to move, by creating or
editing ~/.alsoftrc and adding the lines:
[pulse]
allow-moves = true
3. Run an app using OpenAL Soft, such as the alstream example, using different
output devices.

Actual Results:  
Playback is immediately moved to the preferred audio device set in KDE's System
Settings.

Expected Results:  
Playback stays on the requested device.

I'm the author of OpenAL Soft, and tracked the problem of OpenAL apps not
staying on the devices they were opened on, to KDE, as it only happens when KDE
has the ability to manage PulseAudio app devices (making the stream unmovable,
or unloading module-device-manager, prevents the problem; changing KDE's
preferred audio device while the app is running causes playback to move to the
new preferred device too). I do not see anything on OpenAL Soft's side that
would cause KDE to do this, and can't see any difference between Firefox and
OpenAL Soft apps (as seen by PulseAudio's sink-input properties) that could
trigger this behavior.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kontact] [Bug 368817] New: Opening Configure Kmail

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368817

Bug ID: 368817
   Summary: Opening Configure Kmail
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: crgla...@gmail.com

Application: kontact (5.2.3)

Qt Version: 5.7.0
Frameworks Version: 5.26.0
Operating System: Linux 4.1.31-30-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
I am trying to open configure kmail to add an IMAP email account.  Everytime I
have tried to open the configure kmail I have received this crash.

The crash can be reproduced every time.

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

Thread 20 (Thread 0x7fed95a6b700 (LWP 6150)):
#0  0x7fee47ef303f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fee3a2cd9cb in QTWTF::TCMalloc_PageHeap::scavengerThread()
(this=0x7fee3a5b3ec0 ) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x7fee3a2cd9f9 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
(context=) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x7fee47eef0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fee4eb9a02d in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7fed96d6f700 (LWP 6044)):
#0  0x7fee4eb91bfd in poll () at /lib64/libc.so.6
#1  0x7fee4612be64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fee4612bf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fee4f6adf7b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fed880008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fee4f65d8cb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fed96d6edd0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#5  0x7fee4f4a406a in QThread::exec() (this=) at
thread/qthread.cpp:507
#6  0x7fee4f4a8899 in QThreadPrivate::start(void*) (arg=0x334aae0) at
thread/qthread_unix.cpp:344
#7  0x7fee47eef0a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7fee4eb9a02d in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7fed97570700 (LWP 6041)):
#0  0x7fee4eb8dccd in read () at /lib64/libc.so.6
#1  0x7fee3da5f073 in  () at /usr/lib64/tls/libnvidia-tls.so.367.35
#2  0x7fee4616cb60 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fee4612b999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fee4612bdf8 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7fee4612bf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#6  0x7fee4f6adf7b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fed98e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7  0x7fee4f65d8cb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fed9756fdd0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#8  0x7fee4f4a406a in QThread::exec() (this=) at
thread/qthread.cpp:507
#9  0x7fee4f4a8899 in QThreadPrivate::start(void*) (arg=0x3322120) at
thread/qthread_unix.cpp:344
#10 0x7fee47eef0a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7fee4eb9a02d in clone () at /lib64/libc.so.6

Thread 17 (Thread 0x7fedb4bea700 (LWP 6022)):
#0  0x7fee47ef579c in __lll_lock_wait () at /lib64/libpthread.so.0
#1  0x7fee47ef14a4 in _L_lock_986 () at /lib64/libpthread.so.0
#2  0x7fee47ef1306 in pthread_mutex_lock () at /lib64/libpthread.so.0
#3  0x7fee472a880c in  () at /usr/X11R6/lib64/libGL.so.1
#4  0x7fee472ad731 in  () at /usr/X11R6/lib64/libGL.so.1
#5  0x7fee472adbeb in  () at /usr/X11R6/lib64/libGL.so.1
#6  0x7fee3da5f0f1 in  () at /usr/lib64/tls/libnvidia-tls.so.367.35
#7  0x7fee4616cb60 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fee4612b999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#9  0x7fee4612bdf8 in  () at /usr/lib64/libglib-2.0.so.0
#10 0x7fee4612bf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#11 0x7fee4f6adf7b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fed9c0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#12 0x7fee4f65d8cb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fedb4be9dd0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#13 0x7fee4f4a406a in QThread::exec() (this=) at
thread/qthread.cpp:507
#14 0x7fee4f4a8899 in QThreadPrivate::start(void*) (arg=0x2230fa0) at
thread/qthread_unix.cpp:344
#15 0x7fee47eef0a4 in start_thread () at /lib64/libpthread.so.0
#16 0x7fee4eb9a02d in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7fedb53eb700 (LWP 6020)):
#0  0x7fee4616dd14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fee

[plasmashell] [Bug 368975] New: Small application titles can become glitched, unless cursor is over top item, in which case only that text is glitched

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368975

Bug ID: 368975
   Summary: Small application titles can become glitched, unless
cursor is over top item, in which case only that text
is glitched
   Product: plasmashell
   Version: 5.7.5
  Platform: Archlinux Packages
   URL: https://www.youtube.com/watch?v=shG5tnFh0ws
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: emailofch...@gmail.com
CC: plasma-b...@kde.org

Just now the small title text on applications in the application launcher
became glitched, as well as the section titles (favorites, recent, etc). It
happened on each section except for the applications in Recent (though the
"Recent" text is a gray blocky nothing like the rest).

Reproducible: Didn't try

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 368975] Small application titles can become glitched, unless cursor is over top item, in which case only that text is glitched

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368975

--- Comment #1 from Chris  ---
Created attachment 101159
  --> https://bugs.kde.org/attachment.cgi?id=101159&action=edit
Hold the cursor anywhere within the box except for over the top item, and this
happens.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 368975] Small application titles can become glitched, unless cursor is over top item, in which case only that text is glitched

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368975

--- Comment #2 from Chris  ---
Created attachment 101160
  --> https://bugs.kde.org/attachment.cgi?id=101160&action=edit
If you the cursor goes over the top item, this happens.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 368975] Small application titles can become glitched, unless cursor is over top item, in which case only that text is glitched

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368975

--- Comment #3 from Chris  ---
I logged out and back in just now, and was able to reproduce it once, but I
didn't record it. I logged out and back in again, started OBS first, and then
tried to trigger it again, but now it won't happen.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 342105] [HUION] Cannot right click with the Pen of Huion H610 Pro

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=342105

Chris  changed:

   What|Removed |Added

 CC||chrisbeckwi...@gmail.com

--- Comment #43 from Chris  ---
I have also experienced this problem with the new Huion 1060 plus with the
12.2.16 drivers.

All mouse buttons work outside of Krita, but not inside. However if I were to
use the pen outside of Krita and then "click" back into Krita, Krita seems to
detect the mouse press for the first input only.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365918] Sometimes flickering when interacting with windows

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365918

--- Comment #15 from Chris  ---
Switching the compositor backend to XRender would fix the problem, though
if I switched back to OpenGL during the same session, I think the problem
was still there. Rebooting is not required, I could also log out back to
SDDM, and log back in again. Didn't test restarting kwin without logging
out, didn't know that was an option.

I've definitely noticed it start happening when I wasn't in fullscreen. I
wish I had written down exactly what I was doing when it started happening
those few times it happened.

On Tue, Aug 16, 2016 at 3:58 PM, Thomas Lübking via KDE Bugzilla <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=365918
>
> --- Comment #14 from Thomas Lübking  ---
> Is rebooting required or does switching the compositor backend or
> restarting
> kwin clear the stage as well?
> You could disable the two effects but that would only provide negative
> knowledge, of course (ie. if it still happens, it's not them)
>
> Could it be related to running fullscreen games (steam et al.)?
>
> --
> You are receiving this mail because:
> You reported the bug.
>

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365918] Sometimes flickering when interacting with windows

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365918

--- Comment #16 from Chris  ---
It came back again. (All I did was open a Konsole window.) While the glitching
was happening, I went into Desktop Effects and tried disabling Blur and
Contrast, but the glitching continued. Then I restarted kwin (using `killall
kwin_x11' then `kwin_x11 --replace &') and the glitching was no longer
happening, as expected.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kontact] [Bug 367566] New: Crashed creating filter

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367566

Bug ID: 367566
   Summary: Crashed creating filter
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: crgla...@gmail.com

Application: kontact (5.2.3)

Qt Version: 5.7.0
Frameworks Version: 5.25.0
Operating System: Linux 4.1.27-27-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
I was creating a new email filter.  I had added a sub-folder and was
identifying that folder as the detination. When I hit "OK" the crash occurred.

The crash can be reproduced every time.

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

Thread 19 (Thread 0x7fd2275fa700 (LWP 22675)):
#0  0x7fd2d881279c in __lll_lock_wait () at /lib64/libpthread.so.0
#1  0x7fd2d880e4a4 in _L_lock_986 () at /lib64/libpthread.so.0
#2  0x7fd2d880e306 in pthread_mutex_lock () at /lib64/libpthread.so.0
#3  0x7fd2d7bc580c in  () at /usr/X11R6/lib64/libGL.so.1
#4  0x7fd2d7bca731 in  () at /usr/X11R6/lib64/libGL.so.1
#5  0x7fd2d7bcabeb in  () at /usr/X11R6/lib64/libGL.so.1
#6  0x7fd2ce5fe0f1 in  () at /usr/lib64/tls/libnvidia-tls.so.367.35
#7  0x7fd2d6a89b60 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fd2d6a48999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#9  0x7fd2d6a48df8 in  () at /usr/lib64/libglib-2.0.so.0
#10 0x7fd2d6a48f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#11 0x7fd2dffc6f7b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fd2180008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#12 0x7fd2dff768cb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fd2275f9e10, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#13 0x7fd2dfdbd06a in QThread::exec() (this=) at
thread/qthread.cpp:507
#14 0x7fd2dfdc1899 in QThreadPrivate::start(void*) (arg=0x1971bd0) at
thread/qthread_unix.cpp:344
#15 0x7fd2d880c0a4 in start_thread () at /lib64/libpthread.so.0
#16 0x7fd2df4b302d in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7fd227fff700 (LWP 22671)):
#0  0x7fd2d881279c in __lll_lock_wait () at /lib64/libpthread.so.0
#1  0x7fd2d880e4a4 in _L_lock_986 () at /lib64/libpthread.so.0
#2  0x7fd2d880e306 in pthread_mutex_lock () at /lib64/libpthread.so.0
#3  0x7fd2d7bc580c in  () at /usr/X11R6/lib64/libGL.so.1
#4  0x7fd2d7bca731 in  () at /usr/X11R6/lib64/libGL.so.1
#5  0x7fd2d7bcac48 in  () at /usr/X11R6/lib64/libGL.so.1
#6  0x7fd2ce5fe102 in  () at /usr/lib64/tls/libnvidia-tls.so.367.35
#7  0x7fd2d6a89b60 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fd2d6a48999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#9  0x7fd2d6a48df8 in  () at /usr/lib64/libglib-2.0.so.0
#10 0x7fd2d6a48f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#11 0x7fd2dffc6f7b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fd228e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#12 0x7fd2dff768cb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fd227ffee10, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#13 0x7fd2dfdbd06a in QThread::exec() (this=) at
thread/qthread.cpp:507
#14 0x7fd2dfdc1899 in QThreadPrivate::start(void*) (arg=0x23a5d30) at
thread/qthread_unix.cpp:344
#15 0x7fd2d880c0a4 in start_thread () at /lib64/libpthread.so.0
#16 0x7fd2df4b302d in clone () at /lib64/libc.so.6

Thread 17 (Thread 0x7fd23d58c700 (LWP 22649)):
#0  0x7fd2df4aabfd in poll () at /lib64/libc.so.6
#1  0x7fd2d6a48e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fd2d6a48f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fd2dffc6f7b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fd22c0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fd2dff768cb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fd23d58be10, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#5  0x7fd2dfdbd06a in QThread::exec() (this=) at
thread/qthread.cpp:507
#6  0x7fd2dfdc1899 in QThreadPrivate::start(void*) (arg=0x21a40f0) at
thread/qthread_unix.cpp:344
#7  0x7fd2d880c0a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7fd2df4b302d in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7fd23dd8d700 (LWP 22647)):
#0  0x7ffedd5fed35 in clock_gettime ()
#1  0x7fd2df4bfc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7fd2dfe658f1 in qt_gettime() (ts=0x7fd23dd8cba0, clock=1) at
tools/qelapsedtimer_unix.cpp:109
#3  0x7fd2dfe658f1 in qt_gettime() (frac=,
sec=) at tools/qelapsedtimer_unix.cpp:164
#4  0x7fd2dfe6

[kontact] [Bug 367857] New: Crash on exit

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367857

Bug ID: 367857
   Summary: Crash on exit
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: crgla...@gmail.com

Application: kontact (5.2.3)

Qt Version: 5.7.0
Frameworks Version: 5.25.0
Operating System: Linux 4.1.27-27-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
This crash has been happening for the past 3 days everytime I exit Kontact.

The crash can be reproduced every time.

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

Thread 31 (Thread 0x7fc2977fe700 (LWP 6348)):
#0  0x7fc38698579c in __lll_lock_wait () at /lib64/libpthread.so.0
#1  0x7fc3869814a4 in _L_lock_986 () at /lib64/libpthread.so.0
#2  0x7fc386981306 in pthread_mutex_lock () at /lib64/libpthread.so.0
#3  0x7fc385d3880c in  () at /usr/X11R6/lib64/libGL.so.1
#4  0x7fc385d3d731 in  () at /usr/X11R6/lib64/libGL.so.1
#5  0x7fc385d3dbeb in  () at /usr/X11R6/lib64/libGL.so.1
#6  0x7fc37c7710f1 in  () at /usr/lib64/tls/libnvidia-tls.so.367.35
#7  0x7fc384bfcb60 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fc384bbb999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#9  0x7fc384bbbdf8 in  () at /usr/lib64/libglib-2.0.so.0
#10 0x7fc384bbbf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#11 0x7fc38e135f7b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fc288002a20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#12 0x7fc38e0e58cb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fc2977fde10, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#13 0x7fc38df2c06a in QThread::exec() (this=) at
thread/qthread.cpp:507
#14 0x7fc38df30899 in QThreadPrivate::start(void*) (arg=0x6cd7fc0) at
thread/qthread_unix.cpp:344
#15 0x7fc38697f0a4 in start_thread () at /lib64/libpthread.so.0
#16 0x7fc38d62202d in clone () at /lib64/libc.so.6

Thread 30 (Thread 0x7fc2b8d46700 (LWP 6220)):
#0  0x7fc384bfdd14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fc384bbb4a0 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fc384bbbd80 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fc384bbbf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fc38e135f7b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fc29c0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7fc38e0e58cb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fc2b8d45e10, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#6  0x7fc38df2c06a in QThread::exec() (this=) at
thread/qthread.cpp:507
#7  0x7fc38df30899 in QThreadPrivate::start(void*) (arg=0x2314ae0) at
thread/qthread_unix.cpp:344
#8  0x7fc38697f0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fc38d62202d in clone () at /lib64/libc.so.6

Thread 29 (Thread 0x7fc2b9547700 (LWP 6218)):
#0  0x7fc38698579c in __lll_lock_wait () at /lib64/libpthread.so.0
#1  0x7fc3869814a4 in _L_lock_986 () at /lib64/libpthread.so.0
#2  0x7fc386981306 in pthread_mutex_lock () at /lib64/libpthread.so.0
#3  0x7fc385d3880c in  () at /usr/X11R6/lib64/libGL.so.1
#4  0x7fc385d3d731 in  () at /usr/X11R6/lib64/libGL.so.1
#5  0x7fc385d3dc48 in  () at /usr/X11R6/lib64/libGL.so.1
#6  0x7fc37c771102 in  () at /usr/lib64/tls/libnvidia-tls.so.367.35
#7  0x7fc384bfcb60 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fc384bbb999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#9  0x7fc384bbbdf8 in  () at /usr/lib64/libglib-2.0.so.0
#10 0x7fc384bbbf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#11 0x7fc38e135f7b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fc2980008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#12 0x7fc38e0e58cb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fc2b9546e10, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#13 0x7fc38df2c06a in QThread::exec() (this=) at
thread/qthread.cpp:507
#14 0x7fc38df30899 in QThreadPrivate::start(void*) (arg=0x53dbab0) at
thread/qthread_unix.cpp:344
#15 0x7fc38697f0a4 in start_thread () at /lib64/libpthread.so.0
#16 0x7fc38d62202d in clone () at /lib64/libc.so.6

Thread 28 (Thread 0x7fc2b9d48700 (LWP 6216)):
#0  0x7fc384bbb6d2 in g_main_context_query () at
/usr/lib64/libglib-2.0.so.0
#1  0x7fc384bbbdcf in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fc384bbbf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fc38e135f7b in
QEventDispatcherGlib::processEvents(QFlags)
(th

[kwin] [Bug 360673] kwin_x11 not ending properly on call for shutdown / reboot, causes 90 sec stop job delay. Logout is fine.

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360673

Chris  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #5 from Chris  ---
Sorry, forgot I filed this. This isn't happening anymore.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 342263] Deleted custom shortcut is now somehow in Global Keyboard Shortcuts for khotkeys, stuck

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=342263

Chris  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Chris  ---
This doesn't happen anymore.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kontact] [Bug 367955] New: Crash at startup

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367955

Bug ID: 367955
   Summary: Crash at startup
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: crgla...@gmail.com

Application: kontact (5.2.3)

Qt Version: 5.7.0
Frameworks Version: 5.25.0
Operating System: Linux 4.1.27-27-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
Morning power uup of system leads to this crash.  I suspected Kwallet as the
culprit initially as Iwas not asked for the wallet password at powerup of the
system.  However for the last week the wallet passowrd is requested almost
immediately.  My work around has been to restart the system or to go to
terminal and repeatedly enter akonadictl restart.  When I enter akonadictl stop
I am inofrmed that Akonaid is not running.  When i enter akonadictl start I am
informed that Akonadi is already running.  This is confusing.

The crash can be reproduced every time.

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

Thread 11 (Thread 0x7fd5afde2700 (LWP 5385)):
#0  0x7fd6396a2cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fd639660a46 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fd639660ed8 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fd639660f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fd642bdaf7b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fd5a8e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7fd642b8a8cb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fd5afde1e10, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#6  0x7fd6429d106a in QThread::exec() (this=) at
thread/qthread.cpp:507
#7  0x7fd6429d5899 in QThreadPrivate::start(void*) (arg=0x20dfc40) at
thread/qthread_unix.cpp:344
#8  0x7fd63b4240a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fd6420c702d in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7fd5b05e3700 (LWP 5383)):
#0  0x7fd6420baccd in read () at /lib64/libc.so.6
#1  0x7fd631216073 in  () at /usr/lib64/tls/libnvidia-tls.so.367.35
#2  0x7fd6396a1b60 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fd639660999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fd639660df8 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7fd639660f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#6  0x7fd642bdaf7b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fd5a80008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7  0x7fd642b8a8cb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fd5b05e2e10, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#8  0x7fd6429d106a in QThread::exec() (this=) at
thread/qthread.cpp:507
#9  0x7fd6429d5899 in QThreadPrivate::start(void*) (arg=0x2339ba0) at
thread/qthread_unix.cpp:344
#10 0x7fd63b4240a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7fd6420c702d in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7fd5cd6e6700 (LWP 5374)):
#0  0x7fd63b42803f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fd63f6d1443 in JSC::GCThread::gcThreadMain() () at
/usr/lib64/libQt5WebKit.so.5
#2  0x7fd63f9f30a1 in wtfThreadEntryPoint() () at
/usr/lib64/libQt5WebKit.so.5
#3  0x7fd63b4240a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fd6420c702d in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7fd5cdee7700 (LWP 5373)):
#0  0x7fd63b42803f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fd63f6d1443 in JSC::GCThread::gcThreadMain() () at
/usr/lib64/libQt5WebKit.so.5
#2  0x7fd63f9f30a1 in wtfThreadEntryPoint() () at
/usr/lib64/libQt5WebKit.so.5
#3  0x7fd63b4240a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fd6420c702d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7fd5ce6e8700 (LWP 5372)):
#0  0x7fd63b42803f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fd63f6d1443 in JSC::GCThread::gcThreadMain() () at
/usr/lib64/libQt5WebKit.so.5
#2  0x7fd63f9f30a1 in wtfThreadEntryPoint() () at
/usr/lib64/libQt5WebKit.so.5
#3  0x7fd63b4240a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fd6420c702d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7fd5ceee9700 (LWP 5371)):
#0  0x7fd63b42803f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fd63f6d046d in JSC::BlockAllocator::blockFreeingThreadMain() () at
/usr/lib64/libQt5WebKit.so.5
#2  0x7fd63f9f30a1 in wtfThreadEntryPoint() () at
/usr/lib64/libQt5WebKit.so.5
#3  0x7fd63b4

[kontact] [Bug 367958] New: Crash during Kmail configuration

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367958

Bug ID: 367958
   Summary: Crash during Kmail configuration
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: crgla...@gmail.com

Application: kontact (5.2.3)

Qt Version: 5.7.0
Frameworks Version: 5.25.0
Operating System: Linux 4.1.27-27-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
I am trying to change filters and settings on email accounts.  Each time I have
tried either funciton today a window opens that is blank inside.  Within 1 to 5
seconds the windwo closes and reports this crash.

The crash can be reproduced every time.

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

Thread 20 (Thread 0x7f0eb6ada700 (LWP 7366)):
#0  0x7f0f6dbf403f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f0f613269cb in QTWTF::TCMalloc_PageHeap::scavengerThread()
(this=0x7f0f6160cec0 ) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x7f0f613269f9 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
(context=) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x7f0f6dbf00a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f0f7489302d in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7f0ed0a5a700 (LWP 7038)):
#0  0x7f0f74886ccd in read () at /lib64/libc.so.6
#1  0x7f0f639e2073 in  () at /usr/lib64/tls/libnvidia-tls.so.367.35
#2  0x7f0f6be6db60 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f0f6be2c999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f0f6be2cdf8 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f0f6be2cf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#6  0x7f0f753a6f7b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f0eb8e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7  0x7f0f753568cb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f0ed0a59e10, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#8  0x7f0f7519d06a in QThread::exec() (this=) at
thread/qthread.cpp:507
#9  0x7f0f751a1899 in QThreadPrivate::start(void*) (arg=0x38211e0) at
thread/qthread_unix.cpp:344
#10 0x7f0f6dbf00a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7f0f7489302d in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7f0ed125b700 (LWP 7035)):
#0  0x7f0f7488abfd in poll () at /lib64/libc.so.6
#1  0x7f0f6be2ce64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f0f6be2cf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f0f753a6f7b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f0ebc0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f0f753568cb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f0ed125ae10, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#5  0x7f0f7519d06a in QThread::exec() (this=) at
thread/qthread.cpp:507
#6  0x7f0f751a1899 in QThreadPrivate::start(void*) (arg=0x380f7b0) at
thread/qthread_unix.cpp:344
#7  0x7f0f6dbf00a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f0f7489302d in clone () at /lib64/libc.so.6

Thread 17 (Thread 0x7f0ed27fc700 (LWP 6993)):
#0  0x7f0f7488abfd in poll () at /lib64/libc.so.6
#1  0x7f0f6be2ce64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f0f6be2cf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f0f753a6f7b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f0eb80008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f0f753568cb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f0ed27fbe10, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#5  0x7f0f7519d06a in QThread::exec() (this=) at
thread/qthread.cpp:507
#6  0x7f0f751a1899 in QThreadPrivate::start(void*) (arg=0x13e7000) at
thread/qthread_unix.cpp:344
#7  0x7f0f6dbf00a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f0f7489302d in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7f0ed2ffd700 (LWP 6991)):
#0  0x7f0f6dbf4ea6 in pthread_getspecific () at /lib64/libpthread.so.0
#1  0x7f0f6be52400 in g_thread_self () at /usr/lib64/libglib-2.0.so.0
#2  0x7f0f6be2cf6d in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f0f753a6f7b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f0ec40008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f0f753568cb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f0ed2ffce10, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#5  0x7f0f7519d06a in QThread::exec() (this=) at

[kontact] [Bug 368110] New: Crash at shut down

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368110

Bug ID: 368110
   Summary: Crash at shut down
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: crgla...@gmail.com

Application: kontact (5.2.3)

Qt Version: 5.7.0
Frameworks Version: 5.25.0
Operating System: Linux 4.1.27-27-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
This has been happening for the past week.  Exit Kontact or send an email.  A
notifier pops up saying the email sent successfully followed by another
notfication that the application crashed.

The crash can be reproduced every time.

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

Thread 19 (Thread 0x7fb242e84700 (LWP 3595)):
#0  0x7fb2fab33bfd in poll () at /lib64/libc.so.6
#1  0x7fb2f20cee64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fb2f20cef7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fb2fb64ff7b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fb2340008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fb2fb5ff8cb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fb242e83dd0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#5  0x7fb2fb44606a in QThread::exec() (this=) at
thread/qthread.cpp:507
#6  0x7fb2fb44a899 in QThreadPrivate::start(void*) (arg=0x3deadb0) at
thread/qthread_unix.cpp:344
#7  0x7fb2f3e920a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7fb2fab3c02d in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7fb243685700 (LWP 3592)):
#0  0x7fb2fab2fccd in read () at /lib64/libc.so.6
#1  0x7fb2e9a08073 in  () at /usr/lib64/tls/libnvidia-tls.so.367.35
#2  0x7fb2f210fb60 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fb2f20ce999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fb2f20cedf8 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7fb2f20cef7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#6  0x7fb2fb64ff7b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fb23c0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7  0x7fb2fb5ff8cb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fb243684dd0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#8  0x7fb2fb44606a in QThread::exec() (this=) at
thread/qthread.cpp:507
#9  0x7fb2fb44a899 in QThreadPrivate::start(void*) (arg=0x3dc5f30) at
thread/qthread_unix.cpp:344
#10 0x7fb2f3e920a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7fb2fab3c02d in clone () at /lib64/libc.so.6

Thread 17 (Thread 0x7fb260bea700 (LWP 3544)):
#0  0x7fb2f3e9879c in __lll_lock_wait () at /lib64/libpthread.so.0
#1  0x7fb2f3e944a4 in _L_lock_986 () at /lib64/libpthread.so.0
#2  0x7fb2f3e94306 in pthread_mutex_lock () at /lib64/libpthread.so.0
#3  0x7fb2f324b80c in  () at /usr/X11R6/lib64/libGL.so.1
#4  0x7fb2f3250731 in  () at /usr/X11R6/lib64/libGL.so.1
#5  0x7fb2f3250beb in  () at /usr/X11R6/lib64/libGL.so.1
#6  0x7fb2e9a080f1 in  () at /usr/lib64/tls/libnvidia-tls.so.367.35
#7  0x7fb2f210fb60 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fb2f20ce999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#9  0x7fb2f20cedf8 in  () at /usr/lib64/libglib-2.0.so.0
#10 0x7fb2f20cef7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#11 0x7fb2fb64ff7b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fb2480008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#12 0x7fb2fb5ff8cb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fb260be9dd0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#13 0x7fb2fb44606a in QThread::exec() (this=) at
thread/qthread.cpp:507
#14 0x7fb2fb44a899 in QThreadPrivate::start(void*) (arg=0x1ab3230) at
thread/qthread_unix.cpp:344
#15 0x7fb2f3e920a4 in start_thread () at /lib64/libpthread.so.0
#16 0x7fb2fab3c02d in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7fb2613eb700 (LWP 3542)):
#0  0x7fb2f3e9879c in __lll_lock_wait () at /lib64/libpthread.so.0
#1  0x7fb2f3e944a4 in _L_lock_986 () at /lib64/libpthread.so.0
#2  0x7fb2f3e94306 in pthread_mutex_lock () at /lib64/libpthread.so.0
#3  0x7fb2f324b80c in  () at /usr/X11R6/lib64/libGL.so.1
#4  0x7fb2f3250731 in  () at /usr/X11R6/lib64/libGL.so.1
#5  0x7fb2f3250c48 in  () at /usr/X11R6/lib64/libGL.so.1
#6  0x7fb2e9a08102 in  () at /usr/lib64/tls/libnvidia-tls.so.367.35
#7  0x7fb2f210fb60 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fb2f20ce999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#9  0x7fb2f

[kontact] [Bug 360227] New: Crash on Exit

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360227

Bug ID: 360227
   Summary: Crash on Exit
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: crgla...@gmail.com

Application: kontact (4.14.10)
KDE Platform Version: 4.14.17
Qt Version: 4.8.6
Operating System: Linux 4.1.15-8-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
Has crashed repeatedly today have hanging on email loads each time resulting in
this crash.

The crash can be reproduced every time.

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

Thread 5 (Thread 0x7f34c4b7c700 (LWP 11132)):
#0  0x7f34d8d8c03f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f34ddf12eb6 in WTF::TCMalloc_PageHeap::scavengerThread() () from
/usr/lib64/libQtWebKit.so.4
#2  0x7f34ddf12ee9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) ()
from /usr/lib64/libQtWebKit.so.4
#3  0x7f34d8d880a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f34ded02fed in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f3484279700 (LWP 11133)):
#0  0x7f34d8d8c03f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f34ddc85b3d in JSC::BlockAllocator::blockFreeingThreadMain() () from
/usr/lib64/libQtWebKit.so.4
#2  0x7f34ddf3aa06 in WTF::wtfThreadEntryPoint(void*) () from
/usr/lib64/libQtWebKit.so.4
#3  0x7f34d8d880a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f34ded02fed in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f3475125700 (LWP 11144)):
#0  0x7f34decf6c8d in read () from /lib64/libc.so.6
#1  0x7f34d87fcb60 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f34d87bb999 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f34d87bbdf8 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f34d87bbf7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f34df4f7fde in QEventDispatcherGlib::processEvents
(this=0x7f3478c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#6  0x7f34df4c9d4f in QEventLoop::processEvents
(this=this@entry=0x7f3475124de0, flags=...) at kernel/qeventloop.cpp:149
#7  0x7f34df4ca045 in QEventLoop::exec (this=this@entry=0x7f3475124de0,
flags=...) at kernel/qeventloop.cpp:204
#8  0x7f34df3c74df in QThread::exec (this=) at
thread/qthread.cpp:538
#9  0x7f34df3c9bbf in QThreadPrivate::start (arg=0x112b7b0) at
thread/qthread_unix.cpp:349
#10 0x7f34d8d880a4 in start_thread () from /lib64/libpthread.so.0
#11 0x7f34ded02fed in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f346e0d1700 (LWP 11395)):
#0  0x7f34d8d8c03f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f347bce086b in QTWTF::TCMalloc_PageHeap::scavengerThread
(this=0x7f347bfdcee0 ) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x7f347bce08a9 in QTWTF::TCMalloc_PageHeap::runScavengerThread
(context=) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x7f34d8d880a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f34ded02fed in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f34e1832800 (LWP 11131)):
[KCrash Handler]
#6  operator QItemSelectionModel* (this=) at ../../src/corelib/kernel/qpointer.h:78
#7  QAbstractItemView::selectionModel (this=0x60001) at
itemviews/qabstractitemview.cpp:766
#8  0x7f347a3468ae in MailCommon::FolderTreeWidget::selectedCollections
(this=) at
/usr/src/debug/kdepim-4.14.10/mailcommon/folder/foldertreewidget.cpp:243
#9  0x7f347a9dcf4d in KMMainWidget::updateFolderMenu (this=0x1423310) at
/usr/src/debug/kdepim-4.14.10/kmail/kmmainwidget.cpp:3928
#10 0x7f347a9de01c in KMMainWidget::slotUpdateActionsAfterMailChecking
(this=) at
/usr/src/debug/kdepim-4.14.10/kmail/kmmainwidget.cpp:429
#11 0x7f347aac433a in KMMainWidget::qt_static_metacall (_o=,
_c=, _id=, _a=) at
/usr/src/debug/kdepim-4.14.10/build/kmail/moc_kmmainwidget.cpp:461
#12 0x7f34df4df0fa in QMetaObject::activate (sender=0x1423550, m=, local_signal_index=, argv=0x0) at kernel/qobject.cpp:3576
#13 0x7f34df4e32b1 in QObject::event (this=0x1423550, e=) at
kernel/qobject.cpp:1193
#14 0x7f34dfed579c in QApplicationPrivate::notify_helper
(this=this@entry=0xd87880, receiver=receiver@entry=0x1423550,
e=e@entry=0x7fff0535daf0) at kernel/qapplication.cpp:4565
#15 0x7f34dfedbcdd in QApplication::notify (this=this@entry=0x7fff0535ee40,
receiver=receiver@entry=0x1423550, e=e@entry=0x7fff0535daf0) at
kernel/qapplication.cpp:4351
#16 0x7f34e0bece1a in KAppl

[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=338658

Chris  changed:

   What|Removed |Added

 CC||crgla...@gmail.com

--- Comment #48 from Chris  ---
(In reply to Paul Eggleton from comment #22)
> I have at least figured out how to fix the database in order to get
> directories syncing again using the Akonadi Console. (Disclaimer: this
> worked for me, may not work for you, you might lose data if you aren't
> careful, etc.)
> 
> First I searched to find the duplicate keys using the "DB Console" tab with
> the following query:
> 
> SELECT pimitemtable.*, collectiontable.name FROM pimitemtable
> INNER JOIN pimitemtable dup ON pimitemtable.id != dup.id and
> pimitemtable.remoteId = dup.remoteId and pimitemtable.collectionId =
> dup.collectionId
> INNER JOIN collectiontable ON pimitemtable.collectionId = collectiontable.id
> ORDER by pimitemtable.remoteId
> 
> Then I looked for the items specifically in the folders that I knew were
> failing to sync with the "Multiple merge candidates, aborting" error, then
> used the Id to track down one of the duplicate items in the "Browser" tab
> and then deleted it there from the context menu. (There are still others
> with duplicate ids, but I have not deleted those since they don't appear to
> be causing any problems.) I then restarted the akonadi server, and then
> reloaded the folder in KMail and voila, the folder now synchronises
> successfully.

This does work in Kmail5.  Has anyone tried the remove duplicate email option
in the folder?

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=338658

--- Comment #49 from Chris  ---
(In reply to Ovidiu-Florin BOGDAN from comment #46)
> I've kind of found a workaround for this issue and I've blogged about it
> here:
> http://ovidiu.geekaliens.com/en/2016/01/05/multiple-merge-candidates-
> aborting-workaround/
> 
> I hope it helps.

This also works in Kmail5.  Paul Eggleton posted a work around using
Akonadiconsole which works as well.  I'll ask the same question here as well. 
Does the remove duplicate emails function in "folders" accomplish the same
result?

I haven't seen this question asked (may have missed it) but, does filtering in
Kmail conflict with filtering in Gmail?

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 317346] Okular overwrites PDF form data without asking

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=317346

Chris  changed:

   What|Removed |Added

 CC||ck...@embl-hamburg.de

--- Comment #2 from Chris  ---
Even worse, if you have two copies of the same PDF file, the edits you make to
fields in one file will overwrite the other one. This happens if the copies are
created by copying the file in the file manager or when using 'save copy as',
but not if 'save as' has been used.

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 306292] Option to clear PDF forms

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=306292

Chris  changed:

   What|Removed |Added

 CC||ck...@embl-hamburg.de

--- Comment #1 from Chris  ---
I think this is a duplicate of #288042

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 364160] New: Plasma crash after update on 6-9-2016 OpenSuSE Leap

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364160

Bug ID: 364160
   Summary: Plasma crash after update on 6-9-2016 OpenSuSE Leap
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: crgla...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.1.21-14-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
I allowed an online update to occur today.  I noticed that there was an Nvidia
update but did not catch the detail.  After install the system crashed with a
message to the effect that the screen locker was no longer functioning.  I
ended the sessions and restarted the system.  I am now experiencing a blank
screen.  Past occurrances were the result of an incorrect Nvidia driver as well
as an incorrect setting in the etc/sys/config desktop display.  Mine was set to
"sddm" I changed to KDM resulting in the XCFE desktop working minimally. 
Minimally in that I can get this far.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe39fa447c0 (LWP 3419))]

Thread 7 (Thread 0x7fe388906700 (LWP 3422)):
#0  0x7fe398f44bbd in poll () from /lib64/libc.so.6
#1  0x7fe39de98422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7fe39de9a00f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7fe38b0893c9 in QXcbEventReader::run (this=0x989160) at
qxcbconnection.cpp:1229
#4  0x7fe39963f32f in QThreadPrivate::start (arg=0x989160) at
thread/qthread_unix.cpp:331
#5  0x7fe39874e0a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7fe398f4cfed in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7fe37e980700 (LWP 3437)):
#0  0x7fe39875483a in __lll_unlock_wake () from /lib64/libpthread.so.0
#1  0x7fe3987515b9 in _L_unlock_554 () from /lib64/libpthread.so.0
#2  0x7fe3987514f6 in __pthread_mutex_unlock_usercnt () from
/lib64/libpthread.so.0
#3  0x7fe394a52455 in ?? () from /usr/X11R6/lib64/libGL.so.1
#4  0x7fe394a57b18 in ?? () from /usr/X11R6/lib64/libGL.so.1
#5  0x7fe3910e4102 in ?? () from /usr/lib64/tls/libnvidia-tls.so.367.18
#6  0x7fe395662b60 in ?? () from /usr/lib64/libglib-2.0.so.0
#7  0x7fe395621999 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#8  0x7fe395621df8 in ?? () from /usr/lib64/libglib-2.0.so.0
#9  0x7fe395621f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#10 0x7fe399871d8b in QEventDispatcherGlib::processEvents
(this=0x7fe3780008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#11 0x7fe399818d53 in QEventLoop::exec (this=this@entry=0x7fe37e97fdf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#12 0x7fe39963a61a in QThread::exec (this=this@entry=0xac8c10) at
thread/qthread.cpp:503
#13 0x7fe39c94ee18 in QQmlThreadPrivate::run (this=0xac8c10) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#14 0x7fe39963f32f in QThreadPrivate::start (arg=0xac8c10) at
thread/qthread_unix.cpp:331
#15 0x7fe39874e0a4 in start_thread () from /lib64/libpthread.so.0
#16 0x7fe398f4cfed in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7fe372b69700 (LWP 3438)):
#0  0x7fe395663d14 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7fe395621a5a in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#2  0x7fe395621ed8 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7fe395621f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7fe399871d8b in QEventDispatcherGlib::processEvents
(this=0x7fe36c0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7fe399818d53 in QEventLoop::exec (this=this@entry=0x7fe372b68df0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7fe39963a61a in QThread::exec (this=this@entry=0xf4c840) at
thread/qthread.cpp:503
#7  0x7fe39c94ee18 in QQmlThreadPrivate::run (this=0xf4c840) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#8  0x7fe39963f32f in QThreadPrivate::start (arg=0xf4c840) at
thread/qthread_unix.cpp:331
#9  0x7fe39874e0a4 in start_thread () from /lib64/libpthread.so.0
#10 0x7fe398f4cfed in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7fe371168700 (LWP 3439)):
#0  0x7fe398f40c8d in read () from /lib64/libc.so.6
#1  0x7fe3910e4073 in ?? () from /usr/lib64/tls/libnvidia-tls.so.367.18
#2  0x7fe395662b60 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7fe395621999 in g_main_context_check () from
/usr/lib

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

Chris  changed:

   What|Removed |Added

 CC||emailofch...@gmail.com

--- Comment #108 from Chris  ---
Created attachment 99461
  --> https://bugs.kde.org/attachment.cgi?id=99461&action=edit
Labels of desktop items in Folder View are replaced with colorful noise.

This is one of only two effects I've noticed on my system, labels of desktop
files replaced with noise. This, and text has at least once been missing on the
lock screen after coming back from standby mode.

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 343518] Plasma doesn't restore everything after a reboot

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=343518

--- Comment #65 from Chris  ---
OK, so this bug is solved because it is duplicate of bug 354724, and I looked
there it's solved too; glade to ear it.
However, Konsole never ever get restored for me.
My system is debian-stretch, upgrade from today; I've waited till I had qt5.6.1
installed to post this comment since it could have solved things: it hasn't.
It might be distro related though since they insist on 354724 that Konsole is
correctly restored: I'll check on that side and keep you informed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340982

Chris  changed:

   What|Removed |Added

 CC||riddo...@gmail.com

--- Comment #70 from Chris  ---
As I look now, this bug has 875 votes. That's just the number of people who
have bothered to find this bug entry and vote on it.  I wonder what proportion
of users actually do that...

Since this is not scheduled to be fixed, I'd like to politely ask why. Is this
not considered a bug? Not an important enough bug?  Are there just Insufficient
resources to deal with it?  Is it believed to be a reasonable compromise in
features?  How open are the devs to the possibility that the locale system
might need another rewrite or reverting a significant amount in order to fix
it?

What's the reasoning here?  This would be very important for an outside
developer to know in evaluating their own level of motivation towards working
on this.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kcharselect] [Bug 298010] Missing Unicode blocks; ordering should be improved

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=298010

Chris  changed:

   What|Removed |Added

 CC||emailofch...@gmail.com

--- Comment #16 from Chris  ---
KCharSelect is pretty out of date, it's too bad. It also needs emoji support,
which GNOME Character Map has. I feel strange using gucharmap on my Plasma
desktop, but it's my only option right now.

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 356698] New: Can't add Google Calendar or Contacts libkgapi5 is not available

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356698

Bug ID: 356698
   Summary: Can't add Google Calendar or Contacts libkgapi5 is not
available
   Product: korganizer
   Version: 15.08.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: import/export
  Assignee: korganizer-de...@kde.org
  Reporter: crgla...@gmail.com

The last update within the Opensuse Leap 42.1 release does not include the
libkgapi5.

There is no way to add Google calendars or contacts.

Reproducible: Always

Steps to Reproduce:
1. add calendar
2. or add addressboook
3.

Actual Results:  
window opens without Google options

Expected Results:  
Should have Google options

libkagpi is available for 4.14 not Plasma 5

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 356779] New: Akonadi crash at power on

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356779

Bug ID: 356779
   Summary: Akonadi crash at power on
   Product: Akonadi
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: IMAP resource
  Assignee: chrig...@fastmail.fm
  Reporter: crgla...@gmail.com
CC: kdepim-b...@kde.org, vkra...@kde.org

Application: akonadi_imap_resource (4.89.0)

Qt Version: 5.5.0
Operating System: Linux 4.1.13-5-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
This has happened twice this morning.  The first crash locked up the keyboard
and didn't allow me to finish this input.  ctrl, alt, backspace to logout and
log back in lead back tothis crash.  I have also seen Mysql errors that say
someting to the efect that Mysql cannot be reached.  Will try to add that log
to this report.  May not be related except that the log hasn't changed since
the last update.

The crash can be reproduced every time.

-- Backtrace:
Application: Akonadi Resource (akonadi_imap_resource), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f622c9be840 (LWP 3575))]

Thread 4 (Thread 0x7f6213c2e700 (LWP 3599)):
#0  0x7f6226adbc1d in poll () at /lib64/libc.so.6
#1  0x7f6221a45422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f6221a4700f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f6215f8ac29 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f62273e955f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f6221c620a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f6226ae404d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f6211305700 (LWP 3881)):
#0  0x7f6226adbc1d in poll () at /lib64/libc.so.6
#1  0x7f6220ab1e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f6220ab1f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f622761aa5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f62275c1a63 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f62273e484a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f62273e955f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f6221c620a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f6226ae404d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f6210b04700 (LWP 3882)):
#0  0x7f6221c66408 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f62273ea4c8 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f62273e6716 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f62273e955f in  () at /usr/lib64/libQt5Core.so.5
#4  0x7f6221c620a4 in start_thread () at /lib64/libpthread.so.0
#5  0x7f6226ae404d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f622c9be840 (LWP 3575)):
[KCrash Handler]
#6  0x7f6226a34187 in raise () at /lib64/libc.so.6
#7  0x7f6226a35538 in abort () at /lib64/libc.so.6
#8  0x7f6227053b8d in __gnu_cxx::__verbose_terminate_handler() () at
/usr/lib64/libstdc++.so.6
#9  0x7f6227051bf6 in  () at /usr/lib64/libstdc++.so.6
#10 0x7f6227051c41 in  () at /usr/lib64/libstdc++.so.6
#11 0x7f6227051ea6 in __cxa_rethrow () at /usr/lib64/libstdc++.so.6
#12 0x00466a86 in QList::append(long long const&)
(this=this@entry=0x7ffdccaf4290, t=@0x7ffdccaf41f0: 134217470) at
/usr/include/qt5/QtCore/qlist.h:574
#13 0x0046333b in MoveItemsTask::imapSetToList(KIMAP::ImapSet const&)
(t=@0x7ffdccaf41f0: 134217470, this=0x7ffdccaf4290) at
/usr/include/qt5/QtCore/qlist.h:355
#14 0x0046333b in MoveItemsTask::imapSetToList(KIMAP::ImapSet const&)
(this=this@entry=0x21b9b90, set=...) at
/usr/src/debug/kdepim-runtime-15.08.3/resources/imap/moveitemstask.cpp:313
#15 0x004637bd in MoveItemsTask::recordNewUid()
(this=this@entry=0x21b9b90) at
/usr/src/debug/kdepim-runtime-15.08.3/resources/imap/moveitemstask.cpp:255
#16 0x00464902 in MoveItemsTask::onSearchDone(KJob*) (this=0x21b9b90,
job=0x19fef50) at
/usr/src/debug/kdepim-runtime-15.08.3/resources/imap/moveitemstask.cpp:248
#17 0x7f62275f340f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#18 0x7f6229477d32 in KJob::result(KJob*, KJob::QPrivateSignal) () at
/usr/lib64/libKF5CoreAddons.so.5
#19 0x7f622947859f in KJob::finishJob(bool) () at
/usr/lib64/libKF5CoreAddons.so.5
#20 0x7f622b5cbb98 in KIMAP::Job::handleErrorReplies(KIMAP::Message const&)
() at /usr/lib64/libKF5IMAP.so.5
#21 0x7f622b5dd638 in KIMAP::SearchJob::handleResponse(KIMAP::Message
const&) () at /usr/lib64/libKF5IMAP.so.5
#22 0x7f622b5e9eba in
KIMAP::SessionPrivate::responseReceived(KIMAP::Message const&) () at
/usr/lib64/libKF5IMAP.so.5
#23 0x7f62275f4796 

[Akonadi] [Bug 356779] Akonadi crash at power on

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356779

--- Comment #1 from Chris  ---
Mysql server log

2015-12-16 07:32:21 7f2e10859740 InnoDB: Warning: Using
innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in
future releases, together with the option innodb_use_sys_malloc and with the
InnoDB's internal memory allocator.
151216  7:32:21 [Note] InnoDB: Using mutexes to ref count buffer pool pages
151216  7:32:21 [Note] InnoDB: The InnoDB memory heap is disabled
151216  7:32:21 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
151216  7:32:21 [Note] InnoDB: Memory barrier is not used
151216  7:32:21 [Note] InnoDB: Compressed tables use zlib 1.2.8
151216  7:32:21 [Note] InnoDB: Using Linux native AIO
151216  7:32:21 [Note] InnoDB: Using CPU crc32 instructions
151216  7:32:21 [Note] InnoDB: Initializing buffer pool, size = 80.0M
151216  7:32:21 [Note] InnoDB: Completed initialization of buffer pool
151216  7:32:21 [Note] InnoDB: Highest supported file format is Barracuda.
151216  7:32:21 [Note] InnoDB: 128 rollback segment(s) are active.
151216  7:32:21 [Note] InnoDB: Waiting for purge to start
151216  7:32:21 [Note] InnoDB:  Percona XtraDB (http://www.percona.com)
5.6.25-73.1 started; log sequence number 217698344
151216  7:32:21 [Note] Reading of all Master_info entries succeded
151216  7:32:21 [Note] Added new Master_info '' to hash table
151216  7:32:21 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.0.21-MariaDB'  socket: '/tmp/akonadi-chrisg.48NRsQ/mysql.socket' 
port: 0  openSUSE package


Additionally when I enter "akonadictl start" command the following is displayed

 akonadictl start
Starting Akonadi Server...
   done.
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Rex:~ # QCommandLineParser: option not defined: "start-without-control"
search paths:  ("/sbin", "/usr/sbin", "/usr/local/sbin", "/root/bin",
"/usr/local/bin", "/usr/bin", "/bin", "/usr/bin/X11", "/usr/games",
"/usr/sbin", "/usr/local/sbin", "/usr/local/libexec", "/usr/libexec",
"/opt/mysql/libexec", "/opt/local/lib/mysql5/bin", "/opt/mysql/sbin")
Found mysql_install_db:  "/usr/bin/mysql_install_db"
Found mysqlcheck:  "/usr/bin/mysqlcheck"
/usr/bin/mysqlcheck: Got error: 2002: Can't connect to local MySQL server
through socket '/tmp/akonadi-root.qW81wQ/mysql.socket' (2 "No such file or
directory") when trying to connect
Failed to verify database server version
Query error: "MySQL server has gone away QMYSQL: Unable to execute query"
Database error: " "
"[\n0: akonadiserver(_Z11akBacktracev+0x33) [0x5dbaa3]\n1: akonadiserver()
[0x5dbd99]\n2: /lib64/libc.so.6(+0x35200) [0x7f6a94314200]\n3:
/lib64/libc.so.6(gsignal+0x37) [0x7f6a94314187]\n4:
/lib64/libc.so.6(abort+0x118) [0x7f6a94315538]\n5:
/usr/lib64/libQt5Core.so.5(_Z17qt_message_output9QtMsgTypeRK18QMessageLogContextRK7QString+0x165)
[0x7f6a94cb8e45]\n6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xeb)
[0x5de28b]\n7: /usr/lib64/libQt5Core.so.5(_ZN9QIODevice5writeEPKcx+0xe8)
[0x7f6a94dd3468]\n8: /usr/lib64/libQt5Core.so.5(_ZN11QTextStreamD2Ev+0x11c)
[0x7f6a94de409c]\n9: /usr/lib64/libQt5Core.so.5(_ZN6QDebugD2Ev+0x3f)
[0x7f6a94db428f]\n10:
akonadiserver(_ZN7Akonadi6Server13DbConfigMysql19startInternalServerEv+0x2ede)
[0x4f80ae]\n11:
akonadiserver(_ZN7Akonadi6Server13AkonadiServer20startDatabaseProcessEv+0xf1)
[0x482c51]\n12: akonadiserver(_ZN7Akonadi6Server13AkonadiServer4initEv+0x74)
[0x484184]\n13: akonadiserver() [0x565176]\n14:
/usr/lib64/libQt5Core.so.5(_ZN7QObject5eventEP6QEvent+0x276)
[0x7f6a94ed4796]\n15:
/usr/lib64/libQt5Core.so.5(_ZN16QCoreApplication6notifyEP7QObjectP6QEvent+0x3d)
[0x7f6a94ea3e9d]\n16:
/usr/lib64/libQt5Core.so.5(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x65)
[0x7f6a94ea3ba5]\n17:
/usr/lib64/libQt5Core.so.5(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1e7)
[0x7f6a94ea5d67]\n18: /usr/lib64/libQt5Core.so.5(+0x2dc5c3)
[0x7f6a94efb5c3]\n19:
/usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x254)
[0x7f6a92752c84]\n20: /usr/lib64/libglib-2.0.so.0(+0x4bed8)
[0x7f6a92752ed8]\n21:
/usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c)
[0x7f6a92752f7c]\n22:
/usr/lib64/libQt5Core.so.5(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x5c)
[0x7f6a94efaa3c]\n23:
/usr/lib64/libQt5Core.so.5(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x123)
[0x7f6a94ea1a63]\n24:
/usr/lib64/libQt5Core.so.5(_ZN16QCoreApplication4execEv+0x86)
[0x7f6a94ea95d6]\n25: akonadiserver(main+0x127) [0x481dc7]\n26:
/lib64/libc.so.6(__libc_start_main+0xf5) [0x7f6a94300b05]\n27: akonadiserver()
[0x482707]\n]\n"
ProcessControl: Application 'akonadiserver' returned with exit code 255
(Unknown error)
QCommandLineParser: option not defined: "start-without-control"
search paths:  ("/sbin", "/usr/sbin", "/usr/local/sbin", "/root/bin",
"/usr/local/bin", "/usr/bin", "/bin", "/usr/bin/X11", "/usr/games",
"/usr/sbin", "/usr/

[kmail2] [Bug 343795] Accessing S/MIME encrypted attachments fails

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=343795

Chris  changed:

   What|Removed |Added

 CC||ichri...@core-vector.net

--- Comment #4 from Chris  ---
I can confirm this bug /w OpenSUSE 42.1, KMail 4.14.10

The error appears to be only caused by SMIME encrypted Mail sent with MS
Outlook. The mail body contains a link to "attachement:x:y.z?place=body" for
each attachement, with correct names being shown, but clicking them or using
"save attachements" has no effect. The later shows a "No attachements found"
message.

A workaround is to save the message's source, then run
$ openssl smime -decrypt -in mail.raw -inkey path/to/my/crtkey.pem > mail.decr
removing any mail headers, then run
$ base64 -d --ignore-garbage mail.decr > mail.d64
as suggested. Split the Mail's attachement out manually using
$ csplit --prefix mail.d64_part mail.d64 '/--=_NextPart_/' '{*}'
and then decoding individual attachements by removing the header and
subsequently running
$ base64 -d --ignore-garbage mail.d64_partXY > attachment.name

Some base64 attachements do contain non-ASCII sequences, which is clearly a bug
on the sender side, not KDE (maybe these can be "cleaned" by KMail prior to
decoding?).

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 325224] CalDav doesn't read server items

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=325224

--- Comment #41 from Chris  ---
Unfortunately I cannot corroborate  @Metko's last post. Using kdepim
15.12.0-6.1 on OpenSuSE Leap 42.1 still provokes the same error as before.
Syncing with citadel groudav results in the agent getting stuck at "Syncing
Folder Calendar (100%)" with no detectable network traffic when resyncing apart
from getting the directory listing. Cadaver can still list the directory and
retrieve files without any trouble.

When using the citadel .ics link over groupdav (remote ics file agent), the
contents can be retrieved without problems.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 354731] Black or incorrect textures in different places of UI

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354731

Chris  changed:

   What|Removed |Added

 CC||emailofch...@gmail.com

--- Comment #15 from Chris  ---
Created attachment 98486
  --> https://bugs.kde.org/attachment.cgi?id=98486&action=edit
Filenames of desktop items are replaced with colorful noise.

I have nvidia 364.16 installed for my GTX 980 and my desktop files look like
this when I return from suspend. Using Plasma 5.6.3.

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 362302] New: Enable Save As for remotely opened images

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362302

Bug ID: 362302
   Summary: Enable Save As for remotely opened images
   Product: gwenview
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: sithlor...@gmail.com
CC: myr...@kde.org

Anytime you open a remote image in gwenview it downloads the image so you can
view it.. It would be really helpful if you could save the image to your
computer . right now all edit/save options are disabled . the only solution is
to use wget or another program to save the file.

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 347862] To-Do created out of kmail : attached email can't be opened

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=347862

Chris  changed:

   What|Removed |Added

 CC||y...@augmented-reality.eu

--- Comment #1 from Chris  ---
I can confirm the bug on Kubuntu 15.10  with Kontact 5.0.2 (15.08.2-0ubuntu1).

It also affects POP3 accounts. Saving the message inline does not change
anything, the message still cannot be opened.

Trying to save the message via right click -> "Save as" results in an error
message like the following:
"
Malformed URL
UmV0dXJuLVBhdGg6IDxpdWxpYW5hLmJsaWRhcml1QGxpbmdv…oZXIgb24gb3RoZXIgcHJvamVjdHMuCgpXYXJtIHJlZ2FyZHMsCkl1bGlhCg==.
"

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 358941] New: Selected files, if they appear deselected, will still open if Enter pressed

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358941

Bug ID: 358941
   Summary: Selected files, if they appear deselected, will still
open if Enter pressed
   Product: plasmashell
   Version: 5.5.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Folder
  Assignee: h...@kde.org
  Reporter: emailofch...@gmail.com
CC: plasma-b...@kde.org

If I click on a file or folder in the Folder View on the desktop, then click
somewhere else on the desktop, the file appears to be deselected. However, with
no windows active, and I hit Enter, the file or folder I thought was deselected
will open.

Reproducible: Always

Steps to Reproduce:
1. Click a folder or file in the folder view on the desktop.
2. Click an empty space on the desktop to "deselect" it.
3. Press enter.

Actual Results:  
File or folder will be opened.

Expected Results:  
File or folder should not open.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 358954] New: Dolphin crash changing permissions

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358954

Bug ID: 358954
   Summary: Dolphin crash changing permissions
   Product: dolphin
   Version: 15.12.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: crgla...@gmail.com

Application: dolphin (15.12.1)

Qt Version: 5.5.1
Operating System: Linux 4.1.15-8-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
attempting to change premsissions on linked folder to allow virtualbox access.

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f51a23eb800 (LWP 5177))]

Thread 2 (Thread 0x7f517ea50700 (LWP 5179)):
#0  0x7f51a1c97c1d in poll () at /lib64/libc.so.6
#1  0x7f5196ce4e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f5196ce4f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f519bfead8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f519bf91d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f519bdb361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f519bdb832f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f519786a0a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f51a1ca004d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f51a23eb800 (LWP 5177)):
[KCrash Handler]
#6  0x7f519bfa450b in QMetaObject::invokeMethod(QObject*, char const*,
Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f51a02a8724 in KDialogJobUiDelegate::Private::next() () at
/usr/lib64/libKF5JobWidgets.so.5
#8  0x7f519bfc4ac6 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#9  0x7f519d108e7c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#10 0x7f519d10dcc8 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#11 0x7f519bf93e95 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#12 0x7f519bf96057 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#13 0x7f519bfeb8f3 in  () at /usr/lib64/libQt5Core.so.5
#14 0x7f5196ce4c84 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#15 0x7f5196ce4ed8 in  () at /usr/lib64/libglib-2.0.so.0
#16 0x7f5196ce4f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#17 0x7f519bfead6c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#18 0x7f519bf91d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#19 0x7f519bf998f6 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#20 0x7f51a1fc2311 in kdemain () at /usr/lib64/libkdeinit5_dolphin.so
#21 0x7f51a1bdcb05 in __libc_start_main () at /lib64/libc.so.6
#22 0x004007ee in _start ()

Possible duplicates by query: bug 358693, bug 358509, bug 358406, bug 358404,
bug 352141.

Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.

[kfile] [Bug 361216] New: If one share that uses autofs is browsed all others from that server are mounted.

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361216

Bug ID: 361216
   Summary: If one share that uses autofs is browsed all others
from that server are mounted.
   Product: kfile
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: sithlor...@gmail.com

After browing one share that is set in autofs all other shares set up in autofs
on the same server are mounted. 



Reproducible: Always

Steps to Reproduce:
1. Set your machine up to mount several different shares from the same host
using autofs 
2.open dolphin 
3.browse one of the shares to make it mount

Actual Results:  
the share will be mounted along will all other shares on that server.

Expected Results:  
The browsed share (and only the browsed share) is mounted

1. Autofs using NFS v4 shares. 
2. not all the mounted shares are in my places sidebar 
3. seams to happen with the filedialog too.

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 357526] Annotation can not be saved automatically for a specific PDF file.

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357526

Chris  changed:

   What|Removed |Added

 CC||inkbottle...@gmail.com

--- Comment #2 from Chris  ---
I've got the same problem with this file:
https://www.adobe.com/products/postscript/pdfs/PLRM.pdf

The problem might be related to that comment:
https://bugs.kde.org/show_bug.cgi?id=151614#c168

We still autosave annotations internally as usual, unless the PDF document
contains existing embedded annotations and it's not encrypted. In this case,
you'll be shown a warning ("Your annotation changes will not be saved
automatically. Use File -> Save As... or your changes will be lost once the
document is closed") and a "Do you want to save your annotation changes or
discard them?" prompt on document close.


If it were the case, I have no way to know if the file does have embedded
annotations, it wouldn't actually be a bug.

However this saving of annotations in external XML files is very, very
convenient because it provides both persistent annotations and unmodified
original file, and the fact that it's not possible for some files is a
hindrance.

The status could be changed to confirmed and the importance to wishlist (if
it's actually the non buggy behavior described above).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kontact] [Bug 361664] New: Korganizer Crashes Kontact when refreshing Google Calendars

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361664

Bug ID: 361664
   Summary: Korganizer Crashes Kontact when refreshing Google
Calendars
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: crgla...@gmail.com

Application: kontact (5.1.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.15-8-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
Akonadi has added mutiple instances of Google Calendars.  I am attempting to
delete events by unchecking the box for an email within a duplicated calendar. 
The crash occurs when I have unchecked more than one email address under two or
more calendars and then gone back to recheck only one email instance.  I have
not as yet deleted all calendars and then tried to reinstall.

The crash can be reproduced every time.

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

Thread 32 (Thread 0x7f2b205e7700 (LWP 3396)):
#0  0x7f2b3bc14bbd in poll () from /lib64/libc.so.6
#1  0x7f2b353b3422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f2b353b500f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f2b22d693c9 in QXcbEventReader::run (this=0x23331a0) at
qxcbconnection.cpp:1229
#4  0x7f2b3c52432f in QThreadPrivate::start (arg=0x23331a0) at
thread/qthread_unix.cpp:331
#5  0x7f2b34f900a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7f2b3bc1cfed in clone () from /lib64/libc.so.6

Thread 31 (Thread 0x7f2b1d269700 (LWP 3397)):
#0  0x7f2b34f9403f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f2b39773733 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f2b39773759 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f2b34f900a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f2b3bc1cfed in clone () from /lib64/libc.so.6

Thread 30 (Thread 0x7f2acfdf6700 (LWP 3398)):
#0  0x7f2b347701eb in ?? () from /usr/lib64/libglib-2.0.so.0
#1  0x7f2b3477244b in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f2b34772d80 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f2b34772f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f2b3c756d8b in QEventDispatcherGlib::processEvents
(this=0x7f2ac80008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f2b3c6fdd53 in QEventLoop::exec (this=this@entry=0x7f2acfdf5d90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f2b3c51f61a in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f2b3c52432f in QThreadPrivate::start (arg=0x2468f30) at
thread/qthread_unix.cpp:331
#8  0x7f2b34f900a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7f2b3bc1cfed in clone () from /lib64/libc.so.6

Thread 29 (Thread 0x7f2ace4e6700 (LWP 3399)):
#0  0x7f2b34f9403f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f2b3947f75d in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f2b397a2031 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f2b34f900a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f2b3bc1cfed in clone () from /lib64/libc.so.6

Thread 28 (Thread 0x7f2acdce5700 (LWP 3400)):
#0  0x7f2b34f9403f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f2b39480733 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f2b397a2031 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f2b34f900a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f2b3bc1cfed in clone () from /lib64/libc.so.6

Thread 27 (Thread 0x7f2acd4e4700 (LWP 3401)):
#0  0x7f2b34f9403f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f2b39480733 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f2b397a2031 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f2b34f900a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f2b3bc1cfed in clone () from /lib64/libc.so.6

Thread 26 (Thread 0x7f2accce3700 (LWP 3402)):
#0  0x7f2b34f9403f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f2b39480733 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f2b397a2031 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f2b34f900a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f2b3bc1cfed in clone () from /lib64/libc.so.6

Thread 25 (Thread 0x7f2aaf609700 (LWP 3403)):
#0  0x7f2b33de9709 in ?? () from /usr/X11R6/lib64/libGL.so.1
#1  0x7f2b33df1f35 in ?? () from /usr/X11R6/lib64/libGL.so.1
#2  0x7f2b33df23cb in ?? () from /usr/X11R6/lib64/libGL.so.1
#3  0x7f2b2af870f1 in ?? (

[kontact] [Bug 361714] New: Kontact/Korganizer crashes when changing email link

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361714

Bug ID: 361714
   Summary: Kontact/Korganizer crashes when changing email link
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: crgla...@gmail.com

Application: kontact (5.1.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.20-11-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
I have two instances of a Google calendar showing.  Not sure why as I only
added one calendar.  When trying to unselect one copy infavor of the other
events will temporarily show but then Korganizer produces this crash.  Has been
happening repeatedly for three days.  I have used Akonadiconnsole to remove the
calendars, rebooted, and tried to instal only one calendar.  However two
instances show.

The crash can be reproduced every time.

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

Thread 33 (Thread 0x7f54dd9ce700 (LWP 3856)):
#0  0x7f54f8ffbbbd in poll () from /lib64/libc.so.6
#1  0x7f54f279a422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f54f279c00f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f54e01503c9 in QXcbEventReader::run (this=0x1b7d1a0) at
qxcbconnection.cpp:1229
#4  0x7f54f990b32f in QThreadPrivate::start (arg=0x1b7d1a0) at
thread/qthread_unix.cpp:331
#5  0x7f54f23770a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7f54f9003fed in clone () from /lib64/libc.so.6

Thread 32 (Thread 0x7f54d664d700 (LWP 3858)):
#0  0x7f54f237b03f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f54f6b5a733 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f54f6b5a759 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f54f23770a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f54f9003fed in clone () from /lib64/libc.so.6

Thread 31 (Thread 0x7f548d30d700 (LWP 3862)):
#0  0x7f54f8ffbbbd in poll () from /lib64/libc.so.6
#1  0x7f54f1b59e64 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f54f1b59f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f54f9b3dd8b in QEventDispatcherGlib::processEvents
(this=0x7f54880008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f54f9ae4d53 in QEventLoop::exec (this=this@entry=0x7f548d30cd90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f54f990661a in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f54f990b32f in QThreadPrivate::start (arg=0x1ca6a90) at
thread/qthread_unix.cpp:331
#7  0x7f54f23770a4 in start_thread () from /lib64/libpthread.so.0
#8  0x7f54f9003fed in clone () from /lib64/libc.so.6

Thread 30 (Thread 0x7f54877a4700 (LWP 3863)):
#0  0x7f54f237b03f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f54f686675d in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f54f6b89031 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f54f23770a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f54f9003fed in clone () from /lib64/libc.so.6

Thread 29 (Thread 0x7f5486fa3700 (LWP 3864)):
#0  0x7f54f237b03f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f54f6867733 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f54f6b89031 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f54f23770a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f54f9003fed in clone () from /lib64/libc.so.6

Thread 28 (Thread 0x7f54867a2700 (LWP 3865)):
#0  0x7f54f237b03f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f54f6867733 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f54f6b89031 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f54f23770a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f54f9003fed in clone () from /lib64/libc.so.6

Thread 27 (Thread 0x7f5485fa1700 (LWP 3866)):
#0  0x7f54f237b03f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f54f6867733 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f54f6b89031 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f54f23770a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f54f9003fed in clone () from /lib64/libc.so.6

Thread 26 (Thread 0x7f546c795700 (LWP 3867)):
#0  0x7f54f237d79c in __lll_lock_wait () from /lib64/libpthread.so.0
#1  0x7f54f23794a4 in _L_lock_986 () from /lib64/libpthread.so.0
#2  0x7f54f2379306 in pthread_mutex_lock () from /lib64/libpthread.so.0
#3  0x7f54f11d404c in ?? () from /usr/X11R6/lib64/libGL.so.1
#4  0x7f54f11d8f21 in ?? () from /usr

[kontact] [Bug 361714] Kontact/Korganizer crashes when changing email link

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361714

Chris  changed:

   What|Removed |Added

 CC||crgla...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kontact] [Bug 361714] Kontact/Korganizer crashes when changing email link

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361714

--- Comment #1 from Chris  ---
Created attachment 98373
  --> https://bugs.kde.org/attachment.cgi?id=98373&action=edit
New crash information added by DrKonqi

kontact (5.1.3) using Qt 5.5.1

I removed all instances of Google calendars using Akonadiconsole.  However the
calendars still appear in Korganizer.  Any attempt to unselect an email address
within the calendar in Korganizer causes this crash.  

Re-establishing an agent in Akonadiconsole creates a second instance of the
calendar in KOrganizer.  There is noway to tell which calendar is from
Akonadiconsole though.  And deleting within KOrganizer does not work on either
calendar.

-- Backtrace (Reduced):
#7  0x7f3d4b33c16f in KCalCore::Calendar::notifyIncidenceDeleted
(this=this@entry=0x24324f0, incidence=...) at
/usr/src/debug/kcalcore-16.03.90/src/calendar.cpp:1346
#8  0x7f3d4b381fcc in KCalCore::MemoryCalendar::deleteIncidence
(this=0x24324f0, incidence=...) at
/usr/src/debug/kcalcore-16.03.90/src/memorycalendar.cpp:196
[...]
#12 0x7f3dd0a4f73f in call (a=0x7ffca51d7110, r=0x242af30, this=0x2456c70)
at ../../src/corelib/kernel/qobject_impl.h:124
[...]
#15 0x7f3dd0acea04 in QAbstractItemModel::rowsAboutToBeRemoved
(this=this@entry=0x213e3f0, _t1=..., _t2=_t2@entry=0, _t3=_t3@entry=145) at
.moc/moc_qabstractitemmodel.cpp:590
#16 0x7f3dd09cc044 in QAbstractItemModel::beginRemoveRows (this=0x213e3f0,
parent=..., first=0, last=145) at itemmodels/qabstractitemmodel.cpp:2656

-- 
You are receiving this mail because:
You are watching all bug changes.