[konsole] [Bug 343938] Konsole handles dead keys and Compose incorrectly

[Ph . Marek via KDE Bugzilla]

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

Ph. Marek  changed:

   What|Removed |Added

 CC||phil...@marek.priv.at

--- Comment #2 from Ph. Marek  ---
With konsole "Version 15.08.0" pressing the Compose key gives two inverse
question marks; an xterm in the same X11 session works.

"dead_Greek" seems to be simply ignored.

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

[korganizer] [Bug 361652] New: korganizer crashes while creating a new task

[via KDE Bugzilla]

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

Bug ID: 361652
   Summary: korganizer crashes while creating a new task
   Product: korganizer
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: korganizer-de...@kde.org
  Reporter: user1...@web.de

Application: korganizer (5.1.3)

Qt Version: 5.5.1
Frameworks Version: 5.20.0
Operating System: Linux 4.5.0-3-pae i686
Distribution: "openSUSE Tumbleweed (20160408) (i586)"

-- Information about the crash:
- What I was doing when the application crashed:
I wanted to create a new task in the korganizer and after left clicking in the
calendar and selecting new task ("Neue Aufgabe") the application crashed with a
segmentation fault.

- Unusual behavior I noticed:
The crash is at the same location as in bug #361651. I guess the root cause of
this bug is fixed by fixing bug #361651.

The crash can be reproduced every time.

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

Thread 13 (Thread 0xac652b40 (LWP 11388)):
#0  0x in __kernel_vsyscall ()
#1  0x in poll () at /lib/libc.so.6
#2  0x in  () at /usr/lib/libxcb.so.1
#3  0x in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#4  0x in  () at /usr/lib/libQt5XcbQpa.so.5
#5  0x in  () at /usr/lib/sse2/libQt5Core.so.5
#6  0x in start_thread () at /lib/libpthread.so.0
#7  0x in clone () at /lib/libc.so.6

Thread 12 (Thread 0xab234b40 (LWP 11389)):
#0  0x in __kernel_vsyscall ()
#1  0x in read () at /lib/libc.so.6
#2  0x in  () at /usr/lib/libglib-2.0.so.0
#3  0x in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#4  0x in  () at /usr/lib/libglib-2.0.so.0
#5  0x in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#6  0x in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/sse2/libQt5Core.so.5
#7  0x in
QEventLoop::processEvents(QFlags) () at
/usr/lib/sse2/libQt5Core.so.5
#8  0x in QEventLoop::exec(QFlags) () at
/usr/lib/sse2/libQt5Core.so.5
#9  0x in QThread::exec() () at /usr/lib/sse2/libQt5Core.so.5
#10 0x in QThread::run() () at /usr/lib/sse2/libQt5Core.so.5
#11 0x in  () at /usr/lib/sse2/libQt5Core.so.5
#12 0x in start_thread () at /lib/libpthread.so.0
#13 0x in clone () at /lib/libc.so.6

Thread 11 (Thread 0xaa8ffb40 (LWP 11391)):
#0  0x in __kernel_vsyscall ()
#1  0x in poll () at /lib/libc.so.6
#2  0x in g_poll () at /usr/lib/libglib-2.0.so.0
#3  0x in  () at /usr/lib/libglib-2.0.so.0
#4  0x in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#5  0x in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/sse2/libQt5Core.so.5
#6  0x in
QEventLoop::processEvents(QFlags) () at
/usr/lib/sse2/libQt5Core.so.5
#7  0x in QEventLoop::exec(QFlags) () at
/usr/lib/sse2/libQt5Core.so.5
#8  0x in QThread::exec() () at /usr/lib/sse2/libQt5Core.so.5
#9  0x in QThread::run() () at /usr/lib/sse2/libQt5Core.so.5
#10 0x in  () at /usr/lib/sse2/libQt5Core.so.5
#11 0x in start_thread () at /lib/libpthread.so.0
#12 0x in clone () at /lib/libc.so.6

Thread 10 (Thread 0xa9effb40 (LWP 11393)):
#0  0x in __kernel_vsyscall ()
#1  0x in poll () at /lib/libc.so.6
#2  0x in g_poll () at /usr/lib/libglib-2.0.so.0
#3  0x in  () at /usr/lib/libglib-2.0.so.0
#4  0x in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#5  0x in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/sse2/libQt5Core.so.5
#6  0x in
QEventLoop::processEvents(QFlags) () at
/usr/lib/sse2/libQt5Core.so.5
#7  0x in QEventLoop::exec(QFlags) () at
/usr/lib/sse2/libQt5Core.so.5
#8  0x in QThread::exec() () at /usr/lib/sse2/libQt5Core.so.5
#9  0x in QThread::run() () at /usr/lib/sse2/libQt5Core.so.5
#10 0x in  () at /usr/lib/sse2/libQt5Core.so.5
#11 0x in start_thread () at /lib/libpthread.so.0
#12 0x in clone () at /lib/libc.so.6

Thread 9 (Thread 0xa94ffb40 (LWP 11395)):
#0  0x in __libc_disable_asynccancel () at /lib/libc.so.6
#1  0x in read () at /lib/libc.so.6
#2  0x in  () at /usr/lib/libglib-2.0.so.0
#3  0x in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#4  0x in  () at /usr/lib/libglib-2.0.so.0
#5  0x in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#6  0x in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/sse2/libQt5Core.so.5
#7  0x in
QEventLoop::processEvents(QFlags) () at

[Breeze] [Bug 361066] [Feature Request] GTK+ 3.20 support

[Willem via KDE Bugzilla]

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

Willem  changed:

   What|Removed |Added

 CC||willem...@gmail.com

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

[kontact] [Bug 361651] New: kaddressbook crashes continuously after importing a vcf card

[via KDE Bugzilla]

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

Bug ID: 361651
   Summary: kaddressbook crashes continuously after importing a
vcf card
   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: user1...@web.de

Application: kontact (5.1.3)

Qt Version: 5.5.1
Frameworks Version: 5.20.0
Operating System: Linux 4.5.0-3-pae i686
Distribution: "openSUSE Tumbleweed (20160408) (i586)"

-- Information about the crash:
I imported a vcf card into kaddressbook and immediately kaddressbook crashed
with a segmentation fault. Now kaddressbook crashes everytime it is started. 

Based on the backtrace I would say, that the root cause is within the call or
the arguments passed to the call Akonadi::Tag::isValid().

The crash can be reproduced every time.

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

Thread 25 (Thread 0xade8fb40 (LWP 5466)):
#0  0x in __kernel_vsyscall ()
#1  0x in poll () at /lib/libc.so.6
#2  0x in  () at /usr/lib/libxcb.so.1
#3  0x in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#4  0x in  () at /usr/lib/libQt5XcbQpa.so.5
#5  0x in  () at /usr/lib/sse2/libQt5Core.so.5
#6  0x in start_thread () at /lib/libpthread.so.0
#7  0x in clone () at /lib/libc.so.6

Thread 24 (Thread 0xac7e0b40 (LWP 5467)):
#0  0x in __kernel_vsyscall ()
#1  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0
#2  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libc.so.6
#3  0x in  () at /usr/lib/libQt5WebKit.so.5
#4  0x in  () at /usr/lib/libQt5WebKit.so.5
#5  0x in start_thread () at /lib/libpthread.so.0
#6  0x in clone () at /lib/libc.so.6

Thread 23 (Thread 0xab621b40 (LWP 5468)):
#0  0x in __kernel_vsyscall ()
#1  0x in read () at /lib/libc.so.6
#2  0x in  () at /usr/lib/libglib-2.0.so.0
#3  0x in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#4  0x in  () at /usr/lib/libglib-2.0.so.0
#5  0x in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#6  0x in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/sse2/libQt5Core.so.5
#7  0x in
QEventLoop::processEvents(QFlags) () at
/usr/lib/sse2/libQt5Core.so.5
#8  0x in QEventLoop::exec(QFlags) () at
/usr/lib/sse2/libQt5Core.so.5
#9  0x in QThread::exec() () at /usr/lib/sse2/libQt5Core.so.5
#10 0x in QThread::run() () at /usr/lib/sse2/libQt5Core.so.5
#11 0x in  () at /usr/lib/sse2/libQt5Core.so.5
#12 0x in start_thread () at /lib/libpthread.so.0
#13 0x in clone () at /lib/libc.so.6

Thread 22 (Thread 0xab40 (LWP 5469)):
#0  0x in __kernel_vsyscall ()
#1  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0
#2  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libc.so.6
#3  0x in  () at /usr/lib/dri/r600_dri.so
#4  0x in  () at /usr/lib/dri/r600_dri.so
#5  0x in start_thread () at /lib/libpthread.so.0
#6  0x in clone () at /lib/libc.so.6

Thread 21 (Thread 0xa7f23b40 (LWP 5470)):
#0  0x in __kernel_vsyscall ()
#1  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0
#2  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libc.so.6
#3  0x in WTF::ThreadCondition::wait(WTF::Mutex&) () at
/usr/lib/libQt5WebKit.so.5
#4  0x in  () at /usr/lib/libQt5WebKit.so.5
#5  0x in  () at /usr/lib/libQt5WebKit.so.5
#6  0x in  () at /usr/lib/libQt5WebKit.so.5
#7  0x in start_thread () at /lib/libpthread.so.0
#8  0x in clone () at /lib/libc.so.6

Thread 20 (Thread 0xa75ffb40 (LWP 5471)):
#0  0x in __kernel_vsyscall ()
#1  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0
#2  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libc.so.6
#3  0x in WTF::ThreadCondition::wait(WTF::Mutex&) () at
/usr/lib/libQt5WebKit.so.5
#4  0x in  () at /usr/lib/libQt5WebKit.so.5
#5  0x in  () at /usr/lib/libQt5WebKit.so.5
#6  0x in  () at /usr/lib/libQt5WebKit.so.5
#7  0x in start_thread () at /lib/libpthread.so.0
#8  0x in clone () at /lib/libc.so.6

Thread 19 (Thread 0xa6dfeb40 (LWP 5472)):
#0  0x in __kernel_vsyscall ()
#1  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0
#2  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libc.so.6
#3  0x in WTF::ThreadCondition::wait(WTF::Mutex&) () at
/usr/lib/libQt5WebKit.so.5
#4  0x in  () at 

[krita] [Bug 361648] Bottom half of new document window missing off screen

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||b...@valdyas.org
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Boudewijn Rempt  ---
We fixed that in the 3.0 alpha.

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

[dolphin] [Bug 205157] two clicks on file to rename

[via KDE Bugzilla]

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

--- Comment #12 from funkybom...@gmail.com ---
Do I have to apply the patch manually or should I wait for it to become
available through the regular updates of my distribution? (that might take a
while I suppose)

If it's the former, then could you please describe the proper steps to apply
the patch?

Either way, thanks for your effort!

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

[Spectacle] [Bug 361650] New: Add a Plasma notification once a screenshot has been taken

[Sudhir Khanger via KDE Bugzilla]

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

Bug ID: 361650
   Summary: Add a Plasma notification once a screenshot has been
taken
   Product: Spectacle
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: sud...@sudhirkhanger.com

When I take a screenshot via shortcut the image gets saved in the designated
folder. I have to then browse to the folder location to open the file. Instead
Spectacle should create a Plasma notification that a screenshot has been taken
and an option to open it.

Reproducible: Always

Steps to Reproduce:
1. Take a screenshot via shortcut
2.
3.

Actual Results:  
Notification is not persistent and there is no way to open image from the
notification

Expected Results:  
1. The bubble notification should have an open button to open the screenshot.
2. Spectacle should create a persistent notification.

Just to clarify myself I would like to see following changes.

1. Notification is more descriptive. For example, "Active window screenshot was
captured and saved to xyz/folder."
2. Bubble notification has a button to open the screenshot.
3. The notification stays in the Status & Notifications unless dismissed.

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

[plasmashell] [Bug 345544] krunner and plasma crash opening System Settings

[Konrad Michelson via KDE Bugzilla]

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

Konrad Michelson  changed:

   What|Removed |Added

 CC||transitpassenge...@gmail.co
   ||m

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

[plasmashell] [Bug 361649] New: Crashing Plasma

[Tweak via KDE Bugzilla]

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

Bug ID: 361649
   Summary: Crashing Plasma
   Product: plasmashell
   Version: 5.5.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: bloodleg...@hotmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.4)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-18-generic x86_64
Distribution: Ubuntu Xenial Xerus (development branch)

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

Mostly just using email, but also using emulation software and Konversation.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f59164438c0 (LWP 3127))]

Thread 15 (Thread 0x7f5901763700 (LWP 3130)):
#0  0x7f5910b5e5ad in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f5914c23c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f5914c258d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f59038b14a9 in QXcbEventReader::run (this=0x1beb270) at
qxcbconnection.cpp:1253
#4  0x7f59112547fe in QThreadPrivate::start (arg=0x1beb270) at
thread/qthread_unix.cpp:331
#5  0x7f59103406fa in start_thread (arg=0x7f5901763700) at
pthread_create.c:333
#6  0x7f5910b6a2dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7f58f7914700 (LWP 3167)):
#0  0x7f5910b5e5ad in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f590d8f332c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f590d8f343c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x0001 in ?? ()
#4  0x7f591148ba7b in QEventDispatcherGlib::processEvents
(this=0x7f58f8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f5911432d8a in QEventLoop::exec (this=this@entry=0x7f58f7913ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f591124f854 in QThread::exec (this=this@entry=0x1ce9bf0) at
thread/qthread.cpp:503
#7  0x7f5913af73b5 in QQmlThreadPrivate::run (this=0x1ce9bf0) at
qml/ftw/qqmlthread.cpp:141
#8  0x7f59112547fe in QThreadPrivate::start (arg=0x1ce9bf0) at
thread/qthread_unix.cpp:331
#9  0x7f59103406fa in start_thread (arg=0x7f58f7914700) at
pthread_create.c:333
#10 0x7f5910b6a2dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7f58ecfb6700 (LWP 3171)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f58f4fea5d3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2  0x7f58f4fe9cf7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3  0x7f59103406fa in start_thread (arg=0x7f58ecfb6700) at
pthread_create.c:333
#4  0x7f5910b6a2dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7f58eb564700 (LWP 3176)):
#0  QBasicAtomicOps<8>::testAndSetRelaxed (currentValue=, newValue=0x0, expectedValue=0x1, _q_value=@0x1ce9f48: 0x0) at
../../include/QtCore/../../src/corelib/arch/qatomic_x86.h:259
#1  QGenericAtomicOps >::testAndSetRelease (currentValue=, newValue=0x0,
expectedValue=, _q_value=@0x1ce9f48: 0x0) at
../../include/QtCore/../../src/corelib/thread/qgenericatomic.h:175
#2  QBasicAtomicPointer::testAndSetRelease (currentValue=, newValue=0x0, expectedValue=,
this=this@entry=0x1ce9f48) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:278
#3  QBasicMutex::fastTryUnlock (current=,
this=this@entry=0x1ce9f48) at thread/qmutex.h:85
#4  QMutex::unlock (this=this@entry=0x1ce9f48) at thread/qmutex.cpp:264
#5  0x7f591148b2e5 in QMutexLocker::unlock (this=) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:138
#6  QMutexLocker::~QMutexLocker (this=, __in_chrg=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:132
#7  QThreadData::canWaitLocked (this=) at
../../include/QtCore/5.5.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:240
#8  postEventSourcePrepare (timeout=, s=0x7f58e40012d0) at
kernel/qeventdispatcher_glib.cpp:254
#9  postEventSourceCheck (source=0x7f58e40012d0) at
kernel/qeventdispatcher_glib.cpp:264
#10 0x7f590d8f2d61 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7f590d8f32d0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7f590d8f343c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x0001 in ?? ()
#14 0x7f591148ba7b in QEventDispatcherGlib::processEvents
(this=0x7f58e40008c0, flags=...) at 

[krita] [Bug 361648] New: Bottom half of new document window missing off screen

[Gwarbleh via KDE Bugzilla]

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

Bug ID: 361648
   Summary: Bottom half of new document window missing off screen
   Product: krita
   Version: 2.9.11
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: hvr...@gmail.com

Whenever I try to open a new document (after the first initial one), the window
for the new document is too large for my screen without being able to resize
it. 

Reproducible: Sometimes

Steps to Reproduce:
1. Open Krita after first initial use
2. Click file+new
3. Cry

Actual Results:  
The bottom half of the window is off the screen.

Expected Results:  
Let me click open new document or something

Is it possible to make the window able to resize?

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

[Breeze] [Bug 361066] [Feature Request] GTK+ 3.20 support

[Juan Francisco Cantero Hurtado via KDE Bugzilla]

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

Juan Francisco Cantero Hurtado  changed:

   What|Removed |Added

 CC||juanfra...@gmail.com

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

[krita] [Bug 332386] transform tool preview breaks when toggling layer visibility

[Chris Jones via KDE Bugzilla]

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

--- Comment #7 from Chris Jones  ---
Repeating the steps in my original post, the problem appears resolved.  I
couldn't reproduce rebuilders...@gmail.com's error, although I'm not certain
I'm replicating the steps in exactly the same way.  2.x often exhibits strange
behaviour on a second open document - could it be related to this?  I haven't
tested 3.0 enough to encounter issues with a second document yet.

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

[krita] [Bug 361577] Clone tool brush stroke causes crash

[ocumo via KDE Bugzilla]

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

ocumo  changed:

   What|Removed |Added

 CC||yhcdr-devst...@yahoo.com

--- Comment #1 from ocumo  ---
I can confirm this bug in Kubuntu 15.04 - 64bit.  It is not only in Windows.
Krita version used:   Krita-3.0-Alpha-master-e5109c2-x86_64.AppImage

Steps to reproduce the problem in Kubuntu 15.04:
1. From the command line, launch
Krita-3.0-Alpha-master-e5109c2-x86_64.AppImage.
2. Open a krita supported format file like .kra or .jpg.
3. On the Brush Presets tab, select the Clone_tool brush.
4. Try to use the tool on the image, e.g. left-click on it a couple of times.
The application crashes and the GUI closes (Segmentation fault).
5. In the terminal, the last few stdout/stderr lines are these:


krita.lib.flake: "InteractionTool" : action "object_order_lower" conflicts with
canvas action "rotate_canvas_left" shortcut: "Ctrl+["
krita.lib.flake: "InteractionTool" : action "object_order_raise" conflicts with
canvas action "rotate_canvas_right" shortcut: "Ctrl+]"
krita.lib.flake: "InteractionTool" : action "object_order_lower" conflicts with
canvas action "rotate_canvas_left" shortcut: "Ctrl+["
krita.lib.flake: "InteractionTool" : action "object_order_raise" conflicts with
canvas action "rotate_canvas_right" shortcut: "Ctrl+]"
Segmentation fault (core dumped)

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

[plasmashell] [Bug 361566] Panel auto-hide is completely broken

[Stephen Kraemer via KDE Bugzilla]

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

--- Comment #5 from Stephen Kraemer  ---
Tried removing my ~/.config/plasmashellrc and rebooting as suggested by
ro...@i.ua, but did not work.

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

[krita] [Bug 361619] Input event lag/drop-out when OpenGL is ON with large window

[Tyson Tan via KDE Bugzilla]

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

--- Comment #11 from Tyson Tan  ---
Hi Boud, that option has no effect either. As long as OpenGL is ON, I can't
find any options that can alleviate the problem. If there is more test I can
do, please tell me how to.

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

[kscreenlocker] [Bug 360396] kscreenlocker-greet ignores KB and Mouse after screen energy saving activates

[PhillB via KDE Bugzilla]

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

--- Comment #24 from PhillB  ---
Had a segfault window on plasma-desktop this morning after unlocking. Very
unusual. That window might have been there for some time. I just closed it and
everything seems to work OK (probz bad things going on I can't see though).

Using latest drv-intel and old kscreenlock_greet binary.

Seems to indicate:
1) latest drv-intel and latest kscreenlock_greet don't like each other.
2) Old drv-intel and latest kscreenlock_greet do like each other.
3) Latest drv-intel and old kscreenlock_greet mostly like each other.

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

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[rооt via KDE Bugzilla]

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

--- Comment #39 from rооt  ---
Xapient Try this ppa
https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-plasma
it works for me
and may help you

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

[plasmashell] [Bug 359127] Desktop theme KCM 'details' and editing tab no longer present/functional

[Wulf via KDE Bugzilla]

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

--- Comment #31 from Wulf  ---
just for the record:
(In reply to Kai Uwe Broulik from comment #13)
> Panel Background - doesn't work
worked for me in Plasma 5.5 and works in Plasma 5.6 with theme air

> Translucent background - didn't have an applet that uses that
worked for me for me for a simple symbol in Plasma 5.5 with theme air,
unfortunately is does not work anymore in Plasma 5.6

these were the only things I changed from default theme breeze, thankfully I
saved my changed theme before installing Plasma 5.6 and I'm not lucky, that
this feature has gone.

And the themes from kde-look.org .. I don't like them; and it's really
annoying, that Plasma 5.6 offers themes for KDE4

The "

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

[Systemd KCM] [Bug 361637] Systemd KCM crashed when clicking right mouse button

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

   Assignee|unassigned-b...@kde.org |rthoms...@gmail.com
  Component|general |general
Product|kde |Systemd KCM

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

[kcalc] [Bug 360105] Doesn't start with Qt 5.6

[Andreas Eckstein via KDE Bugzilla]

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

--- Comment #13 from Andreas Eckstein  ---
Fix works for me (coming from bug #361594), thanks!

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

[Breeze] [Bug 361066] [Feature Request] GTK+ 3.20 support

[Pavel Bazika via KDE Bugzilla]

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

Pavel Bazika  changed:

   What|Removed |Added

 CC||pavel.baz...@centrum.cz

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

[frameworks-baloo] [Bug 361627] Plasma crash saving a file with LibreOffice

[Alexander Potashev via KDE Bugzilla]

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

Alexander Potashev  changed:

   What|Removed |Added

  Component|General |Baloo File Daemon
 CC||aspotas...@gmail.com
Product|Baloo   |frameworks-baloo
Version|unspecified |5.19.0

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

[krita] [Bug 361645] I can`t use krita at all

[mvowada via KDE Bugzilla]

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

mvowada  changed:

   What|Removed |Added

 CC||freebo...@tiscali.it

--- Comment #1 from mvowada  ---
Hi Ana, here are some informations on how to reset Krita configuration:
https://docs.krita.org/KritaFAQ#Resetting_Krita_configuration

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

[kstars] [Bug 361646] KStars hogs CPU until unusable

[Rob via KDE Bugzilla]

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

--- Comment #2 from Rob  ---
FYI, I've tried disabling all OpenGL items in the NVidia X Server Settings
dialogue and selecting "High Performance" for the image settings rather than
"Quality", then rebooting.  I've also tried switching off stars, planets and
deep-sky objects in the KStars screen so that it is just ground and black sky. 
Nothing makes a difference so far.

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

[Akonadi] [Bug 337585] folders do not get populated after initial fetch.

[Luis Silva via KDE Bugzilla]

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

Luis Silva  changed:

   What|Removed |Added

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

--- Comment #6 from Luis Silva  ---
This bug no longer happens in current master.

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

[kwin] [Bug 361572] desktop cube setting ignored

[illumilore via KDE Bugzilla]

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

--- Comment #10 from illumilore  ---
Cube is always offered in desktop behavior> virtual desktops, even with
xrender.

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

[plasmashell] [Bug 361647] New: Plasma crashed

[via KDE Bugzilla]

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

Bug ID: 361647
   Summary: Plasma crashed
   Product: plasmashell
   Version: 5.4.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: pedron.alexan...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.2)

Qt Version: 5.4.2
Operating System: Linux 4.2.0-35-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
- What I was doing when the application crashed:
I was opening the  activity change menu when plasma crashed. It's the first
time it happens doing that...

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5206740800 (LWP 1553))]

Thread 8 (Thread 0x7f51f1d95700 (LWP 1558)):
#0  0x7f5200ef288d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f5204f39bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f5204f3b74f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f51f40dfa39 in QXcbEventReader::run (this=0x1883810) at
qxcbconnection.cpp:1105
#4  0x7f52015e52be in QThreadPrivate::start (arg=0x1883810) at
thread/qthread_unix.cpp:337
#5  0x7f52006d46aa in start_thread (arg=0x7f51f1d95700) at
pthread_create.c:333
#6  0x7f5200efde9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f51eb5ef700 (LWP 1580)):
#0  0x7f51fdce3884 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f51fdc9ed8a in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f51fdc9f250 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f51fdc9f2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f520181c29b in QEventDispatcherGlib::processEvents
(this=0x7f51e40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f52017c275a in QEventLoop::exec (this=this@entry=0x7f51eb5eeda0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f52015e03d4 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f5203e08f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f52015e52be in QThreadPrivate::start (arg=0x194a7c0) at
thread/qthread_unix.cpp:337
#9  0x7f52006d46aa in start_thread (arg=0x7f51eb5ef700) at
pthread_create.c:333
#10 0x7f5200efde9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f51dffd0700 (LWP 1583)):
#0  0x7f51fdce3884 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f51fdc9ebaa in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f51fdc9f190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f51fdc9f2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f520181c29b in QEventDispatcherGlib::processEvents
(this=0x7f51d80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f52017c275a in QEventLoop::exec (this=this@entry=0x7f51dffcfda0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f52015e03d4 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f5203e08f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f52015e52be in QThreadPrivate::start (arg=0x1d9df10) at
thread/qthread_unix.cpp:337
#9  0x7f52006d46aa in start_thread (arg=0x7f51dffd0700) at
pthread_create.c:333
#10 0x7f5200efde9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f51dd7f9700 (LWP 1587)):
#0  0x7f5200ef288d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f51fdc9f1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f51fdc9f2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f520181c29b in QEventDispatcherGlib::processEvents
(this=0x7f51d40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f52017c275a in QEventLoop::exec (this=this@entry=0x7f51dd7f8da0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f52015e03d4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f5203e08f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f52015e52be in QThreadPrivate::start (arg=0x1e58e40) at
thread/qthread_unix.cpp:337
#8  0x7f52006d46aa in start_thread (arg=0x7f51dd7f9700) at
pthread_create.c:333
#9  0x7f5200efde9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f51cfdf7700 (LWP 1598)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  

[kstars] [Bug 361646] KStars hogs CPU until unusable

[Rob via KDE Bugzilla]

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

Rob  changed:

   What|Removed |Added

   Keywords||reproducible, usability

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

[kstars] [Bug 361646] New: KStars hogs CPU until unusable

[Rob via KDE Bugzilla]

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

Bug ID: 361646
   Summary: KStars hogs CPU until unusable
   Product: kstars
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: kst...@meades.org

I'm running KStars (v.2.5.0 with KDE Frameworks 5.9.0) as a client on Xubuntu
(15.10) on a Dell Latitude D830 laptop.  When KStars is first launched the
kstars process consumes ~15% (according to 'top') and KStars is very usable. 
However, after about 10 minutes of normal operation (doing nothing other than
scrolling around the KStars sky and looking at stuff), KStars starts hogging
CPU, getting to between 60% and 80%; the lag makes it pretty much unusable at
the point.  The laptop has Intel Core 2 Duo T7100/1.8 GHz processors and 4
Gbytes RAM. The RAM is never more than half used, the swap file is unused. I am
running the correct NVIDIA drivers for the graphics card.

When it gets into this state only a reboot will fix it.  If I just close and
restart KStars it takes a very long time to load and the kstars process still
consumes between 60% and 80% of CPU when just sitting there idle.

I'm very happy if there's a workaround or some tuning required for this: I
really want to use KStars!

Reproducible: Always

Steps to Reproduce:
1.  Start kstars.
2.  Scroll around looking at the sky for more than 10 minutes.
3. Wait for things to slow down.

Actual Results:  
The kstars process was using between %60 and %80 of CPU and the lag caused it
to be unusable.

Expected Results:  
The kstars process to consistently consume no more than 20% to 30% CPU when
idle.

The processing system has Intel Core 2 Duo T7100/1.8 GHz processors and 4
Gbytes RAM. The RAM is never more than half used, the swap file is unused. I am
running the correct NVIDIA drivers for the graphics card (nvidia-340).

My intention is to use Ekos as a client with remote Indi but the above happens
without any of that running.

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

[kwin] [Bug 361572] desktop cube setting ignored

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #9 from Thomas Lübking  ---
You probably had a broken GL setup due to a partial update (MESA overriding the
nvidia libs and you're not using th distro provided nvidia driver or your
distro is stupid or you did a partial update or all of it ;-) causing kwin
segfaults (what should have disabled, but not altered the compositor)

The only possible bug here is the offer of the cube effect while xrender being
configured (no matter how the config took place)
=> configured from effects or desktop kcm?

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

[kwin] [Bug 343844] Kwin makes unconditional access to randr extension in (at least) XRandRScreens::update()

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #66 from Thomas Lübking  ---
*** Bug 361643 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 361645] New: I can`t use krita at all

[Ana via KDE Bugzilla]

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

Bug ID: 361645
   Summary: I can`t use krita at all
   Product: krita
   Version: 2.9.11
  Platform: Other
OS: other
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: gabimm1...@gmail.com

I don`t know why but the settings are all messed up and i have no idea about
how to get the Factory version again, it just keeps on getting worse. I don`t
know how to configure anything. I tried uninstalling the program and
downloading it again but nothing Works, I just want my original settings back.

Reproducible: Always

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

[kwin] [Bug 361643] kwin_x11 crashes via chrome-remote-desktop

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Thomas Lübking  ---
The remote server does not provide the randr extension which Qt relied hard on
up to Qt 5.5
(The kwin position just aborts because there's an xcb error caused by the bad
Qt call)

*** This bug has been marked as a duplicate of bug 343844 ***

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

[kwin] [Bug 361572] desktop cube setting ignored

[illumilore via KDE Bugzilla]

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

--- Comment #8 from illumilore  ---
The cube started working normally once I manually set the renderer to opengl.

 glxinfo 
name of display: :0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
server glx extensions:
GLX_ARB_context_flush_control, GLX_ARB_create_context, 
GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, 
GLX_ARB_fbconfig_float, GLX_ARB_multisample, GLX_EXT_buffer_age, 
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
GLX_EXT_framebuffer_sRGB, GLX_EXT_stereo_tree, GLX_EXT_swap_control, 
GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, 
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_image, 
GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_SGIX_fbconfig, 
GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync
client glx vendor string: NVIDIA Corporation
client glx version string: 1.4
client glx extensions:
GLX_ARB_context_flush_control, GLX_ARB_create_context, 
GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, 
GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, 
GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, 
GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_stereo_tree, 
GLX_EXT_swap_control, GLX_EXT_swap_control_tear, 
GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
GLX_NV_copy_buffer, GLX_NV_copy_image, GLX_NV_delay_before_swap, 
GLX_NV_float_buffer, GLX_NV_multisample_coverage, GLX_NV_present_video, 
GLX_NV_swap_group, GLX_NV_video_capture, GLX_NV_video_out, 
GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, 
GLX_SGI_video_sync
GLX version: 1.4
GLX extensions:
GLX_ARB_context_flush_control, GLX_ARB_create_context, 
GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, 
GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, 
GLX_EXT_create_context_es_profile, GLX_EXT_framebuffer_sRGB, 
GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, 
GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, 
GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, 
GLX_SGI_video_sync
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 750 Ti/PCIe/SSE2
OpenGL core profile version string: 4.4.0 NVIDIA 361.42
OpenGL core profile shading language version string: 4.40 NVIDIA via Cg
compiler
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
GL_AMD_multi_draw_indirect, GL_AMD_seamless_cubemap_per_texture, 
GL_ARB_ES2_compatibility, GL_ARB_ES3_1_compatibility, 
GL_ARB_ES3_2_compatibility, GL_ARB_ES3_compatibility, 
GL_ARB_arrays_of_arrays, GL_ARB_base_instance, GL_ARB_bindless_texture, 
GL_ARB_blend_func_extended, GL_ARB_buffer_storage, 
GL_ARB_clear_buffer_object, GL_ARB_clear_texture, GL_ARB_clip_control, 
GL_ARB_color_buffer_float, GL_ARB_compressed_texture_pixel_storage, 
GL_ARB_compute_shader, GL_ARB_compute_variable_group_size, 
GL_ARB_conditional_render_inverted, GL_ARB_conservative_depth, 
GL_ARB_copy_buffer, GL_ARB_copy_image, GL_ARB_cull_distance, 
GL_ARB_debug_output, GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, 
GL_ARB_depth_texture, GL_ARB_derivative_control, 
GL_ARB_direct_state_access, GL_ARB_draw_buffers, 
GL_ARB_draw_buffers_blend, GL_ARB_draw_elements_base_vertex, 
GL_ARB_draw_indirect, GL_ARB_draw_instanced, GL_ARB_enhanced_layouts, 
GL_ARB_explicit_attrib_location, GL_ARB_explicit_uniform_location, 
GL_ARB_fragment_coord_conventions, GL_ARB_fragment_layer_viewport, 
GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, 
GL_ARB_fragment_shader, GL_ARB_framebuffer_no_attachments, 
GL_ARB_framebuffer_object, GL_ARB_framebuffer_sRGB, 
GL_ARB_geometry_shader4, GL_ARB_get_program_binary, 
GL_ARB_get_texture_sub_image, GL_ARB_gpu_shader5, GL_ARB_gpu_shader_fp64, 
GL_ARB_gpu_shader_int64, GL_ARB_half_float_pixel, 
GL_ARB_half_float_vertex, GL_ARB_imaging, GL_ARB_indirect_parameters, 
GL_ARB_instanced_arrays, GL_ARB_internalformat_query, 
GL_ARB_internalformat_query2, GL_ARB_invalidate_subdata, 
GL_ARB_map_buffer_alignment, GL_ARB_map_buffer_range, GL_ARB_multi_bind, 
GL_ARB_multi_draw_indirect, GL_ARB_multisample, GL_ARB_multitexture, 
GL_ARB_occlusion_query, GL_ARB_occlusion_query2, 
GL_ARB_parallel_shader_compile, GL_ARB_pipeline_statistics_query, 
GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, 

[Breeze] [Bug 361066] [Feature Request] GTK+ 3.20 support

[Ondrej Machulda via KDE Bugzilla]

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

Ondrej Machulda  changed:

   What|Removed |Added

 CC||ondrej.machu...@seznam.cz

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

[okular] [Bug 361644] New: Improve review workflow

[Jonathan Verner via KDE Bugzilla]

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

Bug ID: 361644
   Summary: Improve review workflow
   Product: okular
   Version: 0.24.0
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: PDF backend
  Assignee: okular-de...@kde.org
  Reporter: jonathan.ver...@gmail.com

One use of annotations is for reviewing draft versions of a document. In this
scenario
a reviewer goes over the document and marks suggested changes. Then he sends
the document with the marked changes back to the author who incorporates them
into the document. Sometimes, there might be several people reviewing a
document; 
in this case it is useful if they are able to 

  1) merge comments from the other reviewers (see bug #361292)
  2) comment on the other reviewer's suggestions
  3) mark changes to indicate whether they agree with them or not

The pdf format allows for this workflow via so called "revisions". Each
annotation can
have several revisions (annotations with the IRT key set pointing to the
original annotation).
These serve two purposes:

  -- lightweight comment threads (see point 2 above)
  -- indicating status of the annotation (accepted/rejected/...) (see point 3
above)

It would be nice if okular allowed for this workflow. Currently if a document
has annotations
with revisions, the revisions are not even displayed (fine if they are only
used for point 3, but
not even annotation status is displayed). Moreover okular does not allow for
their creation.

I started working on implementing the workflow. Currently, the reviewboard
request
here:

https://git.reviewboard.kde.org/r/127636/

implements at least displaying the revisions. The next step will be to allow
creating revisions.
This will, however, need changes to poppler.



Reproducible: Always

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

[kwin] [Bug 361643] New: kwin_x11 crashes via chrome-remote-desktop

[markmcopc via KDE Bugzilla]

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

Bug ID: 361643
   Summary: kwin_x11 crashes  via chrome-remote-desktop
   Product: kwin
   Version: 5.4.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: markd.mcconn...@gmail.com

Application: kwin_x11 (5.4.2)

Qt Version: 5.4.2
Operating System: Linux 4.2.0-35-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
- What I was doing when the application crashed:
running kde in Xvfb launched by chrome-remote-desktop, Power Management
disabled, connection is successful but a dialog is presented "Kwin is
unstable you can choose another window manager", however only kwin_x11 is
offered in the dropdown. 

Kde runs correctly in a hardware display, but not in a frame buffer.

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  xcb_setup_vendor_end (R=R@entry=0x0) at xproto.c:869
#7  0x7f2496ad2419 in xcb_setup_pixmap_formats_iterator (R=R@entry=0x0) at
xproto.c:892
#8  0x7f2496ad2459 in xcb_setup_roots_iterator (R=R@entry=0x0) at
xproto.c:909
#9  0x7f2497d8d22d in NETRootInfo::NETRootInfo (this=0x180eab0,
connection=, supportWindow=4294967295, wmName=0x7f24985dfc70
"KWin", properties=..., windowTypes=..., states=..., properties2=...,
actions=..., screen=0, doActivate=true) at
../../src/platforms/xcb/netwm.cpp:470
#10 0x7f2498493429 in KWin::RootInfo::RootInfo (this=0x180eab0,
w=4294967295, name=0x7f24985dfc70 "KWin", properties=..., types=...,
states=..., properties2=..., actions=..., scr=0) at ../netinfo.cpp:140
#11 0x7f249849365e in KWin::RootInfo::create () at ../netinfo.cpp:125
#12 0x7f2498464a09 in KWin::Workspace::init (this=this@entry=0x16da100) at
../workspace.cpp:256
#13 0x7f2498466417 in KWin::Workspace::Workspace (this=0x16da100,
sessionKey=...) at ../workspace.cpp:223
#14 0x7f24984a0bf0 in KWin::Application::createWorkspace
(this=this@entry=0x7ffcada06680) at ../main.cpp:373
#15 0x7f2498c38f3c in KWin::ApplicationX11::::operator()
(__closure=) at ../main_x11.cpp:178
#16 QtPrivate::FunctorCall, QtPrivate::List<>, void,
KWin::ApplicationX11::performStartup():: >::call (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:494
#17 QtPrivate::Functor,
0>::call, void> (arg=, f=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:551
#18
QtPrivate::QFunctorSlotObject,
0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *,
void **, bool *) (which=, this_=, r=, a=, ret=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject_impl.h:192
#19 0x7f2496f97617 in QtPrivate::QSlotObjectBase::call (a=0x7ffcada05e50,
r=0x164bb90, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#20 QMetaObject::activate (sender=0x164bb90, signalOffset=,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at
kernel/qobject.cpp:3702
#21 0x7f2496f97f87 in QMetaObject::activate (sender=,
m=m@entry=0x7f2497fa1b20 ,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at
kernel/qobject.cpp:3582
#22 0x7f2497d94663 in KSelectionOwner::claimedOwnership (this=) at moc_kselectionowner.cpp:150
#23 0x7f2497d8034b in KSelectionOwner::Private::claimSucceeded
(this=0x16626e0) at ../../src/platforms/xcb/kselectionowner.cpp:206
#24 0x7f2497d80ac1 in KSelectionOwner::filterEvent (this=0x164bb90,
ev_P=) at ../../src/platforms/xcb/kselectionowner.cpp:424
#25 0x7f2496f638ef in QAbstractEventDispatcher::filterNativeEvent
(this=this@entry=0x1635340, eventType=...,
message=message@entry=0x7f247c001a80, result=result@entry=0x7ffcada05f98) at
kernel/qabstracteventdispatcher.cpp:460
#26 0x7f2482aeb35e in QXcbConnection::handleXcbEvent
(this=this@entry=0x15fa740, event=event@entry=0x7f247c001a80) at
qxcbconnection.cpp:863
#27 0x7f2482aec3b3 in QXcbConnection::processXcbEvents (this=0x15fa740) at
qxcbconnection.cpp:1303
#28 0x7f2496f98651 in QObject::event (this=0x15fa740, e=) at
kernel/qobject.cpp:1245
#29 0x7f2497834b8c in QApplicationPrivate::notify_helper
(this=this@entry=0x15f3650, receiver=receiver@entry=0x15fa740,
e=e@entry=0x7f247c0012f0) at kernel/qapplication.cpp:3720
#30 0x7f249783a230 in QApplication::notify (this=0x7ffcada06680,
receiver=0x15fa740, e=0x7f247c0012f0) at kernel/qapplication.cpp:3503
#31 0x7f2496f66f1b in QCoreApplication::notifyInternal
(this=0x7ffcada06680, receiver=0x15fa740, 

Re: [choqok] [Bug 360790] New: Error on launch: Unknown host api.longurl.org: Host not found

[Jonathan Dlouhy]

via KDE Bugzilla  kde.org> writes:

> 
> https://bugs.kde.org/show_bug.cgi?id=360790
 
> On launching Choqok I am greeted with the following error: Unknown host
> api.longurl.org: Host not found
> 
> Actual Results:  
> Popup error message: Unknown host api.longurl.org: Host not found
> 

> 
> Expected Results:  
> Should not show a popup error message on launch
> 

This error can be remediated by disabling the Expand URLs via longurl.org
plugin via plugins

[Spectacle] [Bug 361640] Option to default to JPG on save & exit

[Janet via KDE Bugzilla]

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

--- Comment #2 from Janet  ---
Thanks :)

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

[plasmashell] [Bug 361567] task bar icon for multiple window grouping obscures application icons

[Eric S via KDE Bugzilla]

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

--- Comment #1 from Eric S  ---
It would be wonderful if there were some way to simply turn off this feature.
This is a new feature that, in my opinion, is really not in any way useful,
even if it worked properly. One only looks at the Task bar if one is about to
use it, and by using it immediately finds out how many windows the icon is
grouping. Knowing ahead of that click is not really of any benefit that I can
see.

I really cannot imagine a case where I would glance at the bar to find out how
many windows an application has open. And if there is such a use case it is
rare enough that it does not warrant having this icon present all the time. So
actually a good fix for this would be to simply remove this feature entirely.

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

[bugs.kde.org] [Bug 361641] Versions creation for Minuet in bugs.kde.org

[Sandro Andrade via KDE Bugzilla]

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

--- Comment #2 from Sandro Andrade  ---
Thanks, Christophe!

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

[Spectacle] [Bug 361640] Option to default to JPG on save & exit

[Boudhayan Gupta via KDE Bugzilla]

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

Boudhayan Gupta  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Boudhayan Gupta  ---
I can see that this is a valid use-case.

Unfortunately it's too late to do such a feature for the 16.04 release because
the release candidates have already been tagged. I'm going to target this for
the 16.10 release.

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

[kmines] [Bug 361642] Kmines generates very similar boards

[Jonathan Ryshpan via KDE Bugzilla]

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

--- Comment #3 from Jonathan Ryshpan  ---
The best way to see difference is to display the two boards in windows one
above the other and to alternate between one board and the other.

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

[bugs.kde.org] [Bug 361641] Versions creation for Minuet in bugs.kde.org

[Christophe Giboudeaux via KDE Bugzilla]

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

Christophe Giboudeaux  changed:

   What|Removed |Added

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

--- Comment #1 from Christophe Giboudeaux  ---
done

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

[kmines] [Bug 361642] New: Kmines generates very similar boards

[Jonathan Ryshpan via KDE Bugzilla]

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

Bug ID: 361642
   Summary: Kmines generates very similar boards
   Product: kmines
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dim...@gmail.com
  Reporter: jonr...@pacbell.net
CC: kde-games-b...@kde.org

Playing Version 4.0 (29 Jan 2015)

I get boards that are extremely similar.

Reproducible: Always

Steps to Reproduce:
1. Run kmines by clicking start->All Applications->Games->Tactics &
Strategy->kmines
2. Run again same way


Actual Results:  
Random boards

Expected Results:  
Boards very much alike

Snapshots of two such boards will be in a comment.

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

[kmines] [Bug 361642] Kmines generates very similar boards

[Jonathan Ryshpan via KDE Bugzilla]

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

--- Comment #2 from Jonathan Ryshpan  ---
Created attachment 98347
  --> https://bugs.kde.org/attachment.cgi?id=98347=edit
Another snapshot

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

[kmines] [Bug 361642] Kmines generates very similar boards

[Jonathan Ryshpan via KDE Bugzilla]

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

Jonathan Ryshpan  changed:

   What|Removed |Added

 CC||jonr...@pacbell.net

--- Comment #1 from Jonathan Ryshpan  ---
Created attachment 98346
  --> https://bugs.kde.org/attachment.cgi?id=98346=edit
Snapshot of kmines board

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

[bugs.kde.org] [Bug 361641] New: Versions creation for Minuet in bugs.kde.org

[Sandro Andrade via KDE Bugzilla]

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

Bug ID: 361641
   Summary: Versions creation for Minuet in bugs.kde.org
   Product: bugs.kde.org
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: product/component changes
  Assignee: sysad...@kde.org
  Reporter: sandroandr...@kde.org
CC: cgiboude...@gmx.com

Hi,

I'd like the following versions would be available when filing bugs for Minuet
in bugs.kde.org:

0.1.0
0.1.1
0.1.2
0.1.3

These are the correspondents for the KDE Applications 2016.04 release.

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

[okular] [Bug 359932] Okular is very slow at opening some EPUB's

[layus]

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

Guillaume Maudoux (layus)  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #14 from Guillaume Maudoux (layus)  ---
After many bissecting builds, my feeling is that there is not a single commit
to blame, but a set of changes that decrease paerformance on the underlying
QTextDocument.
QTextDocument is quite bloated and, most probably, received extra features (or
even bugfixes) at the cost of efficiency.
If you want an efficient epub reader, use calibre's document viewer.

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

[Spectacle] [Bug 361640] New: Option to default to JPG on save & exit

[Janet via KDE Bugzilla]

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

Bug ID: 361640
   Summary: Option to default to JPG on save & exit
   Product: Spectacle
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: bugzi...@kerridis.de

Can you please add an option to have JPG as the default save format? When I hit
save & exit it always saves as PNG. 99% of my screenshots are for showing in a
forum or the like and PNG is too huge - so I always have to convert the file
after taking the screenshot. More comportable would be if one could choose to
default to a certain format, either JPG or PNG (of course keeping the option to
use the other format when you don't use save & exit but save as). I don't use
PNG at all for screenshots because of the file size, others won't use JPG
because of the quality. It depends on the use case.

Reproducible: Always

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

[okular] [Bug 233806] I can't verify digital signature(s) in PDF files

[Ctibor Brančík via KDE Bugzilla]

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

Ctibor Brančík  changed:

   What|Removed |Added

 CC||ctibor.bran...@gmail.com

--- Comment #4 from Ctibor Brančík  ---
With poppler 0.42.0 it is now possible to verify PDF signatures with pdfsig
command. Upstream bug was closed as fixed, but further development is
apparently needed:
https://bugs.freedesktop.org/show_bug.cgi?id=94376
https://bugs.freedesktop.org/show_bug.cgi?id=94377
https://bugs.freedesktop.org/show_bug.cgi?id=94378

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

[kalarm] [Bug 336738] time zone is miscalculated by 1 hour or ignored

[David Jarvie via KDE Bugzilla]

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

David Jarvie  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/kcal
   ||core/9800fca3b44300828a8b7d
   ||23ae962f01e47ac5ff
   Version Fixed In||16.04
 Resolution|--- |FIXED

--- Comment #18 from David Jarvie  ---
Git commit 9800fca3b44300828a8b7d23ae962f01e47ac5ff by David Jarvie.
Committed on 11/04/2016 at 19:35.
Pushed by djarvie into branch 'Applications/16.04'.

Fix timesInInterval() when parsing VTIMEZONE RRULE components

KDateTime::isValid() (KF5 <= 5.21) wrongly returns invalid for an instance
which is specified in ClockTime, if the date/time is invalid in LocalTime,
resulting in timesInInterval() returning no values when parsing a VTIMEZONE
RRULE component in ICalTimeZones.

This is a workaround for backwards compatibility with KF5 <= 5.21.

Differential Revision: https://phabricator.kde.org/D1375
FIXED-IN: 16.04

M +2 -1 src/recurrencerule.cpp

http://commits.kde.org/kcalcore/9800fca3b44300828a8b7d23ae962f01e47ac5ff

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

[kdelibs] [Bug 309193] Keyboard shortcuts doesn't work if non-english keyboard layout is set before english one

[Frederik Schwarzer via KDE Bugzilla]

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

--- Comment #59 from Frederik Schwarzer  ---
... Forgot to mention that those shortcuts in KDevelop actually do work once
every few weeks but the next reboot they are gone again.

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

[kalarm] [Bug 360674] Post-daylight savings time, kalarm records alarms 1 hour later than it should

[David Jarvie via KDE Bugzilla]

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

David Jarvie  changed:

   What|Removed |Added

   Version Fixed In||16.04
 Resolution|DUPLICATE   |FIXED
  Latest Commit||http://commits.kde.org/kcal
   ||core/9800fca3b44300828a8b7d
   ||23ae962f01e47ac5ff

--- Comment #7 from David Jarvie  ---
Git commit 9800fca3b44300828a8b7d23ae962f01e47ac5ff by David Jarvie.
Committed on 11/04/2016 at 19:35.
Pushed by djarvie into branch 'Applications/16.04'.

Fix timesInInterval() when parsing VTIMEZONE RRULE components

KDateTime::isValid() (KF5 <= 5.21) wrongly returns invalid for an
instance which is specified in ClockTime, if the date/time is invalid
in LocalTime, resulting in timesInInterval() returning no values when
parsing a VTIMEZONE RRULE component in ICalTimeZones.

This is a workaround for backwards compatibility with KF5 <= 5.21.

Differential Revision: https://phabricator.kde.org/D1375
FIXED-IN: 16.04

M  +2-1src/recurrencerule.cpp

http://commits.kde.org/kcalcore/9800fca3b44300828a8b7d23ae962f01e47ac5ff

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

[Breeze] [Bug 361066] [Feature Request] GTK+ 3.20 support

[via KDE Bugzilla]

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

darkosm...@gmail.com changed:

   What|Removed |Added

 CC||darkosm...@gmail.com

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

[kdelibs] [Bug 309193] Keyboard shortcuts doesn't work if non-english keyboard layout is set before english one

[Frederik Schwarzer via KDE Bugzilla]

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

Frederik Schwarzer  changed:

   What|Removed |Added

 CC||schwar...@kde.org

--- Comment #58 from Frederik Schwarzer  ---
I have this problem for a long time now.
Shortcuts like Ctrl+S for Saving do work in Kate but not in KDevelop for
instance.
My intuition told me that the KF5 versions work but the KDE4 versions don't,
but I did not check this properly.

Qt 4.8.7 and 5.5.1 installed.
My keyboard layout is US with some custom mappings with xmodmap.

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Christoph via KDE Bugzilla]

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

Christoph  changed:

   What|Removed |Added

 CC||ilove...@mojo.cc

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

[krita] [Bug 361619] Input event lag/drop-out when OpenGL is ON with large window

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org

--- Comment #10 from Boudewijn Rempt  ---
Hm... Both graphics cards are amd's. Could you check what happens if you
disable "Use Texture Buffer"? We added that option because on AMD gpu's that
often improves performance.

It's really provoking... Here on an Nvidia card, I _cannot_ get bended lines
anymore. If I start Krita under valgrind, I can draw spirals, and it takes ages
before they pop up on the screen, but when they do, they're perfectly round :-(

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

[Artikulate] [Bug 361571] Artikulate crashes on Start up

[Andreas Cord-Landwehr via KDE Bugzilla]

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

--- Comment #3 from Andreas Cord-Landwehr  ---
Ubuntu packaging bug is now reported here:
https://bugs.launchpad.net/ubuntu/+source/artikulate/+bug/1569006

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

[plasmashell] [Bug 359109] ibus terminated when switching back from virtual terminal

[via KDE Bugzilla]

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

--- Comment #2 from spa...@modanese.net ---
Still present in 5.6.2.

Journalctl:
 kdeinit5[1167]: org.kde.kcm_keyboard: ibus successfully stopped

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

[krita] [Bug 332386] transform tool preview breaks when toggling layer visibility

[Dmitry Kazakov via KDE Bugzilla]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 Resolution|FIXED   |WAITINGFORINFO

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

[krita] [Bug 332386] transform tool preview breaks when toggling layer visibility

[Dmitry Kazakov via KDE Bugzilla]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 Status|CONFIRMED   |NEEDSINFO
 Resolution|--- |FIXED
 CC||dimul...@gmail.com

--- Comment #6 from Dmitry Kazakov  ---
Hm, I cannot reproduce it here. I think I have fixed this bug during the Krita
3.0 release cycle.
Could you please check with Krita 3.0?

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

[krita] [Bug 349821] File layers do not support transformations or transform masks.

[Dmitry Kazakov via KDE Bugzilla]

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

Dmitry Kazakov  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/krit
   ||a/caeff5a4dc1e16e2e5cb1c664
   ||372018ea3f7dd73
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #5 from Dmitry Kazakov  ---
Git commit caeff5a4dc1e16e2e5cb1c664372018ea3f7dd73 by Dmitry Kazakov.
Committed on 11/04/2016 at 18:34.
Pushed by dkazakov into branch 'master'.

Fix transforming layers bigger than the image in size
Related: bug 350510
Ref T2081

M  +38   -17   libs/image/kis_safe_transform.cpp
M  +0-2libs/ui/kis_file_layer.cpp

http://commits.kde.org/krita/caeff5a4dc1e16e2e5cb1c664372018ea3f7dd73

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

[krita] [Bug 357020] Crash in transform mask

[Dmitry Kazakov via KDE Bugzilla]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/krit
   ||a/695cc85ebc95f0c1e40024105
   ||172016e37148c6f

--- Comment #2 from Dmitry Kazakov  ---
Git commit 695cc85ebc95f0c1e40024105172016e37148c6f by Dmitry Kazakov.
Committed on 11/04/2016 at 18:34.
Pushed by dkazakov into branch 'master'.

Fix crash when switching transformation type in Transformation Masks

We shouldn't try to fetch the transform args from the masks when
resetting the transformation mask.
Related: bug 352724

M  +12   -8plugins/tools/tool_transform2/kis_tool_transform.cc
M  +1-1plugins/tools/tool_transform2/kis_tool_transform.h

http://commits.kde.org/krita/695cc85ebc95f0c1e40024105172016e37148c6f

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

[krita] [Bug 352724] Crashes during Transform

[Dmitry Kazakov via KDE Bugzilla]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/krit
   ||a/695cc85ebc95f0c1e40024105
   ||172016e37148c6f
 Status|CONFIRMED   |RESOLVED

--- Comment #3 from Dmitry Kazakov  ---
Git commit 695cc85ebc95f0c1e40024105172016e37148c6f by Dmitry Kazakov.
Committed on 11/04/2016 at 18:34.
Pushed by dkazakov into branch 'master'.

Fix crash when switching transformation type in Transformation Masks

We shouldn't try to fetch the transform args from the masks when
resetting the transformation mask.
Related: bug 357020

M  +12   -8plugins/tools/tool_transform2/kis_tool_transform.cc
M  +1-1plugins/tools/tool_transform2/kis_tool_transform.h

http://commits.kde.org/krita/695cc85ebc95f0c1e40024105172016e37148c6f

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

[krita] [Bug 350510] Transform Mask only transforms a portion of layer

[Dmitry Kazakov via KDE Bugzilla]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/krit
   ||a/caeff5a4dc1e16e2e5cb1c664
   ||372018ea3f7dd73

--- Comment #4 from Dmitry Kazakov  ---
Git commit caeff5a4dc1e16e2e5cb1c664372018ea3f7dd73 by Dmitry Kazakov.
Committed on 11/04/2016 at 18:34.
Pushed by dkazakov into branch 'master'.

Fix transforming layers bigger than the image in size
Related: bug 349821
Ref T2081

M  +38   -17   libs/image/kis_safe_transform.cpp
M  +0-2libs/ui/kis_file_layer.cpp

http://commits.kde.org/krita/caeff5a4dc1e16e2e5cb1c664372018ea3f7dd73

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

[krita] [Bug 361635] Deleted workspace returns on restart

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Boudewijn Rempt  ---
Hm, I couldn't reproduce on OSX, but I can reproduce on Linux, where Krita
says:

krita.lib.widgets: Cannot write meta information to '
"/home/boud/.local/share/krita/krita/kis_workspaces.blacklist" '.

Which shows we've got yet another resource paths bug here.

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

[plasmashell] [Bug 336274] "Connecting…" status causes high plasmashell CPU usage

[Vasishath Kaushal via KDE Bugzilla]

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

Vasishath Kaushal  changed:

   What|Removed |Added

 CC||vasish...@gmail.com

--- Comment #34 from Vasishath Kaushal  ---
I have observed it too on my arch linux laptop. plasmashell process starts
eating 100 percent cpu whenever that spinning animation is running in the
taskbar. Happens during file operations and network connect/disconnect.

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

[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations

[Steffen Klee via KDE Bugzilla]

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

--- Comment #32 from Steffen Klee  ---
Created attachment 98344
  --> https://bugs.kde.org/attachment.cgi?id=98344=edit
log: xev -root

Logged while:
- run game
- close it
- experience window decoration glitch

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

[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations

[Steffen Klee via KDE Bugzilla]

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

--- Comment #31 from Steffen Klee  ---
Created attachment 98343
  --> https://bugs.kde.org/attachment.cgi?id=98343=edit
log: xev

xev -event randr
Does not output anything (tried running game, dis/enabling compositor
manually). Therefore I removed the event mask, hopefully it's useful.

I'll upload "xev -root" also (no output with randr event filter, too).

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

[kio] [Bug 269370] ftp network folder in dolphin does not honor codepage for filenames

[Eric S via KDE Bugzilla]

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

--- Comment #11 from Eric S  ---
(In reply to Eric S from comment #10)
> I'm going to open(In reply to Jan Dosoudil from comment #9)
> > (In reply to Eric S from comment #7)
> > > I find there are other problems with beyond-ASCII characters in dolphin 
> > > over
> > > fish. I have a file with the registered trademark symbol in the name (®). 
> > > It
> > > appears correctly in dolphin over fish, however I cannot open in Dolphin,
> > > nor can I copy it from dolphin. It does not matter if I explicitly Select
> > > UTF-8 as the remote charset. 
> > > 
> > > Note that this worked fine with the version of Dolphin under plasma 4.
> > 
> > I have exactly same problem -- files with Czech characters (UTF-8 encoding)
> > doesn't open in Dolphin 5.x over fish.
> 
> I'm going to open another issue for this. I'm guessing this is not being
> seen because it is v4.9.4 issue.

Actually, there are no 5.x version offered for kio when reporting a bug here.
WTF? Is the system just out of date or kio considered part of some other
component now in Plasma 5?

Also I'm not sure this issue (at least going by the title) is the right one for
my and Jan Dosoudil's problem, that fish: cannot open, copy, rename, etc files
with non-latin characters in their name. Searching in the bug system for
characters under kio there are a whole host of problems with characters beyond
ascii but the bugs all seem to be specific in ways that don't necessarily
encompass this problem. So I still suspect we need to file another bug, but
it's not entirely clear where.

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

[kmail2] [Bug 361639] New: Kmail Crashes when double clicking on message in the message list

[Mark Gannon via KDE Bugzilla]

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

Bug ID: 361639
   Summary: Kmail Crashes when double clicking on message in the
message list
   Product: kmail2
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: m...@truenorth.nu

Application: kmail (5.1.90 rc)
 (Compiled from sources)
Qt Version: 5.5.1
Frameworks Version: 5.21.0
Operating System: Linux 4.3.3-gentoo x86_64
Distribution: "Gentoo Base System release 2.2"

-- Information about the crash:
- What I was doing when the application crashed:
Open kmail.
Double click on a message in the message list to open it as its own window.
Kmail crashes and this dialog appears

The crash can be reproduced every time.

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

Thread 21 (Thread 0x7f34cc406700 (LWP 6895)):
#0  0x7f34e78ecc8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f34dbc77b12 in poll (__timeout=-1, __nfds=1, __fds=0x7f34cc405d00)
at /usr/include/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0xf1aea0, cond=cond@entry=0xf1aee0,
vector=vector@entry=0x0, count=count@entry=0x0) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_conn.c:459
#3  0x7f34dbc798f7 in xcb_wait_for_event (c=0xf1aea0) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_in.c:693
#4  0x7f34ce76dce9 in QXcbEventReader::run (this=0xf25850) at
qxcbconnection.cpp:1229
#5  0x7f34e81eb632 in QThreadPrivate::start (arg=0xf25850) at
thread/qthread_unix.cpp:331
#6  0x7f34de6475c6 in start_thread (arg=0x7f34cc406700) at
pthread_create.c:334
#7  0x7f34e78f60cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 20 (Thread 0x7f34ca30d700 (LWP 6896)):
#0  0x7f34e78ecc8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f34dcaedf1c in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7f34bc003070, timeout=, context=0x7f34bc000990) at
/var/tmp/portage/dev-libs/glib-2.48.0/work/glib-2.48.0/glib/gmain.c:4135
#2  g_main_context_iterate (context=context@entry=0x7f34bc000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.48.0/work/glib-2.48.0/glib/gmain.c:3835
#3  0x7f34dcaee04c in g_main_context_iteration (context=0x7f34bc000990,
may_block=may_block@entry=1) at
/var/tmp/portage/dev-libs/glib-2.48.0/work/glib-2.48.0/glib/gmain.c:3901
#4  0x7f34e83e226b in QEventDispatcherGlib::processEvents
(this=0x7f34bc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f34e8392e0a in QEventLoop::exec (this=this@entry=0x7f34ca30ce00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f34e81e6e96 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f34e81eb632 in QThreadPrivate::start (arg=0xff8b30) at
thread/qthread_unix.cpp:331
#8  0x7f34de6475c6 in start_thread (arg=0x7f34ca30d700) at
pthread_create.c:334
#9  0x7f34e78f60cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 19 (Thread 0x7f34c9b0c700 (LWP 6897)):
#0  0x7f34e78ecc8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f34dcaedf1c in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7f34c0002e20, timeout=, context=0x7f34c990) at
/var/tmp/portage/dev-libs/glib-2.48.0/work/glib-2.48.0/glib/gmain.c:4135
#2  g_main_context_iterate (context=context@entry=0x7f34c990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.48.0/work/glib-2.48.0/glib/gmain.c:3835
#3  0x7f34dcaee04c in g_main_context_iteration (context=0x7f34c990,
may_block=may_block@entry=1) at
/var/tmp/portage/dev-libs/glib-2.48.0/work/glib-2.48.0/glib/gmain.c:3901
#4  0x7f34e83e226b in QEventDispatcherGlib::processEvents
(this=0x7f34c8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f34e8392e0a in QEventLoop::exec (this=this@entry=0x7f34c9b0be00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f34e81e6e96 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f34e81eb632 in QThreadPrivate::start (arg=0x106d390) at
thread/qthread_unix.cpp:331
#8  0x7f34de6475c6 in start_thread (arg=0x7f34c9b0c700) at
pthread_create.c:334
#9  0x7f34e78f60cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 18 (Thread 0x7f34c930b700 (LWP 6898)):
#0  g_source_iter_next (iter=iter@entry=0x7f34c930ac30,
source=source@entry=0x7f34c930ac28) at
/var/tmp/portage/dev-libs/glib-2.48.0/work/glib-2.48.0/glib/gmain.c:933
#1  0x7f34dcaed42b in g_main_context_prepare
(context=context@entry=0x7f34b4000990, 

[Akonadi] [Bug 361638] New: Google imap inbox crash.

[Brad via KDE Bugzilla]

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

Bug ID: 361638
   Summary: Google imap inbox crash.
   Product: Akonadi
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: IMAP resource
  Assignee: chrig...@fastmail.fm
  Reporter: bba...@gmail.com
CC: kdepim-b...@kde.org, vkra...@kde.org

Application: akonadi_imap_resource (4.14)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.16.0-4-amd64 x86_64
Distribution: Debian GNU/Linux 8.4 (jessie)

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

Nothing just started the application. This issue has just shown up in the last
update.

The crash can be reproduced every time.

-- Backtrace:
Application: Google Mail (bbaago) of type IMAP E-Mail Server
(akonadi_imap_resource), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa363c98780 (LWP 1377))]

Thread 3 (Thread 0x7fa34f3af700 (LWP 1593)):
#0  0x7fa35f4d0d3d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fa35e45aee4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa35e45affc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa3632a8d37 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x7fa363278271 in
QEventLoop::processEvents(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5  0x7fa3632785d5 in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x7fa36316ce99 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x7fa36316f70f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x7fa35eb470a4 in start_thread (arg=0x7fa34f3af700) at
pthread_create.c:309
#9  0x7fa35f4d987d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7fa34dfa4700 (LWP 1877)):
#0  0x7fa35f4cce0d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fa35e49de50 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa35e45a96c in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa35e45ae83 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fa35e45affc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fa3632a8d37 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x7fa363278271 in
QEventLoop::processEvents(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x7fa3632785d5 in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x7fa36316ce99 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x7fa36316f70f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#10 0x7fa35eb470a4 in start_thread (arg=0x7fa34dfa4700) at
pthread_create.c:309
#11 0x7fa35f4d987d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7fa363c98780 (LWP 1377)):
[KCrash Handler]
#6  0x7fa360e629bd in KIMAP::SearchJob::handleResponse(KIMAP::Message
const&) () from /usr/lib/libkimap.so.4
#7  0x7fa360e5394b in
KIMAP::SessionPrivate::responseReceived(KIMAP::Message const&) () from
/usr/lib/libkimap.so.4
#8  0x7fa363292e11 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x7fa3625ca48c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#10 0x7fa3625d0fa8 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#11 0x7fa3606781aa in KApplication::notify(QObject*, QEvent*) () from
/usr/lib/libkdeui.so.5
#12 0x7fa36327971d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#13 0x7fa36327cfc1 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#14 0x7fa3632a8bd3 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#15 0x7fa35e45ac5d in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x7fa35e45af48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x7fa35e45affc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x7fa3632a8d1d in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#19 0x7fa36266ef96 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#20 0x7fa363278271 in
QEventLoop::processEvents(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#21 0x7fa3632785d5 in
QEventLoop::exec(QFlags) () from

[plasmashell] [Bug 353975] Black screen on second display.

[Bernd Steinhauser via KDE Bugzilla]

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

--- Comment #22 from Bernd Steinhauser  ---
I have only "external" screens (not everybody's using a laptop :P). And they
have a resolution of 1920x1200.

I'd say: Wait for Plasma 5.7 and see if it's still there, because it was said
that when they can depend on Qt 5.6 (thus the next version) the multiscreen
handling should improve.

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

[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #30 from Thomas Lübking  ---
xev -event randr

should log randr events (inc. res changes)

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

[kwin] [Bug 361500] kwin crashes in "O2ES" mode while click on task-manager entry with multible instances

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #4 from Thomas Lübking  ---
sorry, i'm stupid.
ldd /usr/lib/libQt5Gui.so.5
but it will be libGL - it's rather stunning that gles compositing works at all?

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

[Breeze] [Bug 361066] [Feature Request] GTK+ 3.20 support

[Steffen Klee via KDE Bugzilla]

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

Steffen Klee  changed:

   What|Removed |Added

 CC||stkl.m...@gmail.com

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

[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations

[Steffen Klee via KDE Bugzilla]

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

--- Comment #29 from Steffen Klee  ---
Created attachment 98342
  --> https://bugs.kde.org/attachment.cgi?id=98342=edit
screenshot: w/o plasmashell

System information:
OpenGL vendor string:   X.Org
OpenGL renderer string: Gallium 0.4 on AMD HAWAII (DRM 2.43.0,
LLVM 3.7.1)
OpenGL version string:  3.0 Mesa 11.2.0
OpenGL shading language version string: 1.30
Driver: Unknown
GPU class:  Unknown
OpenGL version: 3.0
GLSL version:   1.30
Mesa version:   11.2
X server version:   1.18.3
Linux kernel version:   4.4.5
Requires strict binding:yes
GLSL shaders:   yes
Texture NPOT support:   yes
Virtual Machine:no


So the bug is not limited to the nvidia driver.


(In reply to Thomas Lübking from comment #28)
> the shadow textures seem to pick the wallpaper?
> does it also happen w/o plasmashell? (pkill plasmashell from konsole)
> what does it look like when restarting plasmashell afterwards?
> 
> another thing: do those "games" perhaps alter the screen resolution?
Not running/restarting plasmashell does not change anything.

Yes, screen resolution might be altered ("game's" resolution is the same as
desktop resolution though). The bug does not appear when running the "game" in
windowed mode; this mode disables compositor.

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

[kde] [Bug 361637] New: Systemd KCM crashed when clicking right mouse button

[Alexander Potashev via KDE Bugzilla]

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

Bug ID: 361637
   Summary: Systemd KCM crashed when clicking right mouse button
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: aspotas...@gmail.com

Application: kcmshell5 (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.3-300.fc23.x86_64 x86_64
Distribution: "Fedora release 23 (Twenty Three)"

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

1. Type in some text in the filter textedit, so that the majority of systemd
units hide from the list;
2. Click in the empty space in the list widget with right mouse button.

The crash can be reproduced every time.

-- Backtrace:
Application: Модуль настройки KDE (kcmshell5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
84T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f4e0f1fd8c0 (LWP 10925))]

Thread 3 (Thread 0x7f4de7ca2700 (LWP 10927)):
#0  0x7f4e0ad15bcd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f4e073e2390 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x7f4e0739ec64 in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7f4e0739f110 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7f4e0739f27c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7f4e0739f2b9 in glib_worker_main () at /lib64/libglib-2.0.so.0
#6  0x7f4e073c5835 in g_thread_proxy () at /lib64/libglib-2.0.so.0
#7  0x7f4e08ac360a in start_thread (arg=0x7f4de7ca2700) at
pthread_create.c:334
#8  0x7f4e0ad25a4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f4de74a1700 (LWP 10928)):
#0  0x7f4e0ad15bcd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f4e073e2390 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x7f4e0739ec64 in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7f4e0739f110 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7f4e0739f4f2 in g_main_loop_run () at /lib64/libglib-2.0.so.0
#5  0x7f4df2592336 in gdbus_shared_thread_func () at /lib64/libgio-2.0.so.0
#6  0x7f4e073c5835 in g_thread_proxy () at /lib64/libglib-2.0.so.0
#7  0x7f4e08ac360a in start_thread (arg=0x7f4de74a1700) at
pthread_create.c:334
#8  0x7f4e0ad25a4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f4e0f1fd8c0 (LWP 10925)):
[KCrash Handler]
#5  0x7f4de8f831f8 in kcmsystemd::slotUnitContextMenu(QPoint const&) () at
/usr/lib64/qt5/plugins/kcm_systemd.so
#6  0x7f4de8fc1489 in kcmsystemd::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () at /usr/lib64/qt5/plugins/kcm_systemd.so
#7  0x7f4e0bb3229a in QMetaObject::activate(QObject*, int, int, void**) ()
at /lib64/libQt5Core.so.5
#8  0x7f4e0c812005 in QWidget::customContextMenuRequested(QPoint const&) ()
at /lib64/libQt5Widgets.so.5
#9  0x7f4e0c82be0e in QWidget::event(QEvent*) () at
/lib64/libQt5Widgets.so.5
#10 0x7f4e0c92a20e in QFrame::event(QEvent*) () at
/lib64/libQt5Widgets.so.5
#11 0x7f4e0ca4fe2b in QAbstractItemView::viewportEvent(QEvent*) () at
/lib64/libQt5Widgets.so.5
#12 0x7f4e0bb0352c in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at
/lib64/libQt5Core.so.5
#13 0x7f4e0c7e83fc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#14 0x7f4e0c7ef279 in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQt5Widgets.so.5
#15 0x7f4e0bb0373b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#16 0x7f4e0c845ab2 in QWidgetWindow::handleMouseEvent(QMouseEvent*) () at
/lib64/libQt5Widgets.so.5
#17 0x7f4e0c847f3b in QWidgetWindow::event(QEvent*) () at
/lib64/libQt5Widgets.so.5
#18 0x7f4e0c7e841c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#19 0x7f4e0c7ed8e6 in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQt5Widgets.so.5
#20 0x7f4e0bb0373b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#21 0x7f4e0c03feb1 in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() at /lib64/libQt5Gui.so.5
#22 0x7f4e0c041b75 in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() at /lib64/libQt5Gui.so.5
#23 0x7f4e0c025918 in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() at /lib64/libQt5Gui.so.5
#24 0x7f4df56510b0 in userEventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQt5XcbQpa.so.5
#25 

[kwin] [Bug 361500] kwin crashes in "O2ES" mode while click on task-manager entry with multible instances

[FabiB via KDE Bugzilla]

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

--- Comment #3 from FabiB  ---
ldd /usr/lib/libQt5Core.so.5
linux-vdso.so.1 (0x7ffe5a39e000)
libpthread.so.0 => /usr/lib/libpthread.so.0 (0x7fda41263000)
libz.so.1 => /usr/lib/libz.so.1 (0x7fda4104b000)
libicui18n.so.56 => /usr/lib/libicui18n.so.56 (0x7fda40bcb000)
libicuuc.so.56 => /usr/lib/libicuuc.so.56 (0x7fda40833000)
libpcre16.so.0 => /usr/lib/libpcre16.so.0 (0x7fda405cb000)
libdl.so.2 => /usr/lib/libdl.so.2 (0x7fda403c3000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x7fda400b3000)
librt.so.1 => /usr/lib/librt.so.1 (0x7fda3feab000)
libsystemd.so.0 => /usr/lib/libsystemd.so.0 (0x7fda415d3000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x7fda3fb23000)
libm.so.6 => /usr/lib/libm.so.6 (0x7fda3f81b000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7fda3f603000)
libc.so.6 => /usr/lib/libc.so.6 (0x7fda3f25b000)
/lib64/ld-linux-x86-64.so.2 (0x7fda41483000)
libicudata.so.56 => /usr/lib/libicudata.so.56 (0x7fda3d873000)
libpcre.so.1 => /usr/lib/libpcre.so.1 (0x7fda3d603000)
libcap.so.2 => /usr/lib/libcap.so.2 (0x7fda3d3fb000)
libresolv.so.2 => /usr/lib/libresolv.so.2 (0x7fda3d1e3000)
liblzma.so.5 => /usr/lib/liblzma.so.5 (0x7fda3cfbb000)
liblz4.so.1 => /usr/lib/liblz4.so.1 (0x7fda3cda3000)
libgcrypt.so.20 => /usr/lib/libgcrypt.so.20 (0x7fda3cabb000)
libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0x7fda3c8a3000)


ldd `which kwin_x11`
linux-vdso.so.1 (0x7ffd59156000)
libkdeinit5_kwin_x11.so => /usr/lib/libkdeinit5_kwin_x11.so
(0x7f49918d3000)
libpthread.so.0 => /usr/lib/libpthread.so.0 (0x7f49916b3000)
libc.so.6 => /usr/lib/libc.so.6 (0x7f499130b000)
libkwin.so.5 => /usr/lib/libkwin.so.5 (0x7f4990e33000)
libKF5I18n.so.5 => /usr/lib/libKF5I18n.so.5 (0x7f4990bdb000)
libKF5WindowSystem.so.5 => /usr/lib/libKF5WindowSystem.so.5
(0x7f4990983000)
libQt5X11Extras.so.5 => /usr/lib/libQt5X11Extras.so.5
(0x7f499077b000)
libQt5Widgets.so.5 => /usr/lib/libQt5Widgets.so.5 (0x7f498fefb000)
libQt5Gui.so.5 => /usr/lib/libQt5Gui.so.5 (0x7f498f773000)
libQt5Core.so.5 => /usr/lib/libQt5Core.so.5 (0x7f498f0a3000)
libxcb.so.1 => /usr/lib/libxcb.so.1 (0x7f498ee7b000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x7f498eaf3000)
/lib64/ld-linux-x86-64.so.2 (0x7f4991ae3000)
libkwineffects.so.8 => /usr/lib/libkwineffects.so.8
(0x7f498e8bb000)
libkwinxrenderutils.so.8 => /usr/lib/libkwinxrenderutils.so.8
(0x7f498e6b3000)
libkwin4_effect_builtins.so.1 => /usr/lib/libkwin4_effect_builtins.so.1
(0x7f498e3a3000)
libQt5Script.so.5 => /usr/lib/libQt5Script.so.5 (0x7f498df0b000)
libKF5GlobalAccelPrivate.so.5 => /usr/lib/libKF5GlobalAccelPrivate.so.5
(0x7f498dce3000)
libKF5Plasma.so.5 => /usr/lib/libKF5Plasma.so.5 (0x7f498da0b000)
libkdecorations2.so.5 => /usr/lib/libkdecorations2.so.5
(0x7f498d7e3000)
libkdecorations2private.so.5 => /usr/lib/libkdecorations2private.so.5
(0x7f498d5db000)
libKScreenLocker.so.5 => /usr/lib/libKScreenLocker.so.5
(0x7f498d39b000)
libKF5Activities.so.5 => /usr/lib/libKF5Activities.so.5
(0x7f498d153000)
libX11.so.6 => /usr/lib/libX11.so.6 (0x7f498ce0b000)
libICE.so.6 => /usr/lib/libICE.so.6 (0x7f498cbeb000)
libSM.so.6 => /usr/lib/libSM.so.6 (0x7f498c9e3000)
libXi.so.6 => /usr/lib/libXi.so.6 (0x7f498c7d3000)
libxcb-xfixes.so.0 => /usr/lib/libxcb-xfixes.so.0 (0x7f498c5cb000)
libxcb-damage.so.0 => /usr/lib/libxcb-damage.so.0 (0x7f498c3c3000)
libxcb-composite.so.0 => /usr/lib/libxcb-composite.so.0
(0x7f498c1bb000)
libxcb-shape.so.0 => /usr/lib/libxcb-shape.so.0 (0x7f498bfb3000)
libxcb-sync.so.1 => /usr/lib/libxcb-sync.so.1 (0x7f498bdab000)
libxcb-render.so.0 => /usr/lib/libxcb-render.so.0 (0x7f498bb9b000)
libxcb-randr.so.0 => /usr/lib/libxcb-randr.so.0 (0x7f498b98b000)
libxcb-keysyms.so.1 => /usr/lib/libxcb-keysyms.so.1
(0x7f498b783000)
libxcb-shm.so.0 => /usr/lib/libxcb-shm.so.0 (0x7f498b57b000)
libxcb-glx.so.0 => /usr/lib/libxcb-glx.so.0 (0x7f498b35b000)
libxcb-cursor.so.0 => /usr/lib/libxcb-cursor.so.0 (0x7f498b153000)
libxkbcommon.so.0 => /usr/lib/libxkbcommon.so.0 (0x7f498af13000)
libKF5WaylandClient.so.5 => /usr/lib/libKF5WaylandClient.so.5
(0x7f498ac93000)
libKF5WaylandServer.so.5 => /usr/lib/libKF5WaylandServer.so.5
(0x7f498a9fb000)
libwayland-cursor.so.0 => 

[Breeze] [Bug 361066] [Feature Request] GTK+ 3.20 support

[Martin Kostolný via KDE Bugzilla]

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

Martin Kostolný  changed:

   What|Removed |Added

 CC||clearmar...@zoho.com

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

[plasmashell] [Bug 353975] Black screen on second display.

[Alexander Schlarb via KDE Bugzilla]

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

--- Comment #21 from Alexander Schlarb  ---
Created attachment 98341
  --> https://bugs.kde.org/attachment.cgi?id=98341=edit
xrandr --current --verbose (Alexander Schlarb)

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

[plasmashell] [Bug 353975] Black screen on second display.

[Alexander Schlarb via KDE Bugzilla]

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

--- Comment #20 from Alexander Schlarb  ---
That's too bad. :-(
Have you verified that this is this still the case on the same-resolution
external monitors, Bernd?

It could be something else screen-configuration related through. We should
collect a list of affected and non-affected screen configurations. I'll attach
my `xrandr --current --verbose` when using my affected external screen.

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

[plasmashell] [Bug 360137] Low performance when moving mouse cursor over task manager tabs in panel

[Bernd Steinhauser via KDE Bugzilla]

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

--- Comment #24 from Bernd Steinhauser  ---
For testing purposes, I downgraded Plasma to 5.5.5. I do still see the same
behavior.
I'm pretty sure that I didn't see it previously when I ran 5.5.x, because a
laggy behavior like this I would've noticed.

As I upgraded to Plasma 5.6 together with Qt (to 5.6 as well), I guess this is
a bug that was triggered by a change in Qt, since I'm now running Plasma 5.5 on
top of Qt 5.6.

I'm not sure if I'm going to test that, though, since downgrading Qt on a
source-based distro is really really painful.

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

[yakuake] [Bug 356853] Wrong split is focused when showing/hiding the terminal.

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

 CC||juha.p.musto...@gmail.com

--- Comment #22 from Eike Hein  ---
*** Bug 361618 has been marked as a duplicate of this bug. ***

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

[yakuake] [Bug 361618] Yakuake does not restore the focus in same terminal pane on open/retract

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Eike Hein  ---


*** This bug has been marked as a duplicate of bug 356853 ***

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

[frameworks-plasma] [Bug 355592] IconItem does not support non-square icons

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

 CC||jive...@gmail.com

--- Comment #8 from Eike Hein  ---
*** Bug 361634 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 361634] Graphic errors for previews in Folder View applet

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Eike Hein  ---


*** This bug has been marked as a duplicate of bug 355592 ***

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

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Xapient via KDE Bugzilla]

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

--- Comment #38 from Xapient  ---
i have to correct myself...  in my case it absolutely doesn't matter if i
disconnect(poweroff) a DVI or HDMI or DisplayPort screen.. plasma crashes
everytime!

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

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Xapient via KDE Bugzilla]

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

Xapient  changed:

   What|Removed |Added

 CC||xapi...@gmx.net

--- Comment #37 from Xapient  ---
plasma 5.5.4 (kubuntu 16.04) 
qt 5.5.1

everytime one of the two monitors goes to sleep plasma crashes..  kwin is still
working so i'm able to continue with my work but plasma is not respawning and
i'm not able to restart it..  
no error message whatsoever.


if this is resolved in upstream (as mentioned in the description)  i really
hope they will somehow backport the bugfix otherwise kubuntu 16.04 will not
support displayport monitors at all..  this is an absolut no-go

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

[plasmashell] [Bug 353975] Black screen on second display.

[Bernd Steinhauser via KDE Bugzilla]

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

--- Comment #19 from Bernd Steinhauser  ---
You can have the bug with other resolutions as well and also if the screens
have the same resolution.
The resolution doesn't matter as far as I can tell.

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

[krita] [Bug 360786] Krita randomly crashes when applying a transformation

[Dmitry Kazakov via KDE Bugzilla]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 CC||dimul...@gmail.com

--- Comment #3 from Dmitry Kazakov  ---
The crash looks really weird. What size of the image you have?

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

[akregator] [Bug 336417] Akregator crashes when being closed

[Mauro47 via KDE Bugzilla]

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

Mauro47  changed:

   What|Removed |Added

 CC||msovr...@yahoo.it

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

[akregator] [Bug 336417] Akregator crashes when being closed

[Mauro47 via KDE Bugzilla]

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

--- Comment #37 from Mauro47  ---
Created attachment 98340
  --> https://bugs.kde.org/attachment.cgi?id=98340=edit
New crash information added by DrKonqi

akregator (4.14.1) on KDE Platform 4.14.2 using Qt 4.8.6

- What I was doing when the application crashed: 
I simply closed the application. No problem when the application was open and
running

-- Backtrace (Reduced):
#7  0x7fb63503ff62 in Akregator::Frame::signalCompleted(Akregator::Frame*)
() from /usr/lib/libakregatorprivate.so.4
#8  0x7fb63503581b in
Akregator::Frame::slotSetState(Akregator::Frame::State) () from
/usr/lib/libakregatorprivate.so.4
#9  0x7fb61a38f3c7 in Akregator::MainWidget::slotFetchingStopped() () from
/usr/lib/kde4/akregatorpart.so
[...]
#11 0x7fb635035449 in Akregator::FetchQueue::slotAbort() () from
/usr/lib/libakregatorprivate.so.4
#12 0x7fb6350354ca in Akregator::FetchQueue::~FetchQueue() () from
/usr/lib/libakregatorprivate.so.4

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

[plasmashell] [Bug 359611] Plasmashell loads itself incompletely and with long delays

[Martin Kyral via KDE Bugzilla]

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

--- Comment #41 from Martin Kyral  ---
Are the blocking calls in the device manager widget going to be fixed, too? I
sometimes mount nfs drive and when I'm out of the connection and need to
restart plasma (or plasma crashes), it won't come up because of it. I know the
workaround (umount -l and restart plasmashell once more), but still.. it's
annoying... 

Thanks!

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

[tellico] [Bug 361622] Tellico ("Video Collection") crashes if there is a blank line in "Cast"

[via KDE Bugzilla]

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

--- Comment #2 from ejr2...@mybtinternet.com ---
Hi Robby,

Thanks for investigating.

I don't know what to say. The steps you are describing are exactly what I do
(except that I use "Delete" instead of Backspace! :-)
The main thing is to get to an empty row, as per that attached
Bug_Crash-Step_2.png
I have tried it again in version 2.3.11 just in case, and it still crashes, as
soon as I click on "Save Entry".
Every single time on my machine - it's not random at all.
I have actually been using Tellico for a while, and it used to crash also on a
previous Kubuntu installation on a different laptop - so it does not seem to be
hardware dependent.

Maybe the trace in the file "tellico-20160411-100326.kcrash.txt" might provide
some clue as to what is happening, if you get a chance to look at it?
If there is anything I can do to help investigate on my machine, please let me
know.
Otherwise, it's not a major inconvenience, I know what to do to avoid it
crashing - maybe, some day, something will happen that will trigger a "haha!"
moment, and you will find what may go wrong.

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

[kio] [Bug 269370] ftp network folder in dolphin does not honor codepage for filenames

[Jan Dosoudil via KDE Bugzilla]

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

Jan Dosoudil  changed:

   What|Removed |Added

 CC||czd...@gmail.com

--- Comment #9 from Jan Dosoudil  ---
(In reply to Eric S from comment #7)
> I find there are other problems with beyond-ASCII characters in dolphin over
> fish. I have a file with the registered trademark symbol in the name (®). It
> appears correctly in dolphin over fish, however I cannot open in Dolphin,
> nor can I copy it from dolphin. It does not matter if I explicitly Select
> UTF-8 as the remote charset. 
> 
> Note that this worked fine with the version of Dolphin under plasma 4.

I have exactly same problem -- files with Czech characters (UTF-8 encoding)
doesn't open in Dolphin 5.x over fish.

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

[kwin] [Bug 361500] kwin crashes in "O2ES" mode while click on task-manager entry with multible instances

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #2 from Thomas Lübking  ---
It's enforced GLES ...

@FabiB, check the outputs of
  ldd /usr/lib/libQt5Core.so.5
and
  ldd `which kwin_x11`

If they say something like libGLX.so and or libEGL or libGL.so, afaik that
won't work, because you cannot intermix a Qt5 libGL build with libGLES.

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

[kwin] [Bug 360841] Unable to unshow/unpresent windows using the same keyboard shortcut

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #6 from Thomas Lübking  ---
please run "sleep 20; qdbus org.kde.KWin /KWin supportInformation >
kwin.support.info" and trigger the dysfunctional effect (DG or PW) within the
next 20 seconds, wait until the timeout hit (so you'll have gotten the debug
info), maybe ensure that the effect (notably filtering) really didn't work and
then attach the gathered information.

KWin might hold the grab, but some other effect (or the tabbox???) could
receive it.

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

[krita] [Bug 361333] Configure toolbar dialog is empty and all previous configurations are lost

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/krit
   ||a/4308f313c9240712c2feb0569
   ||4ab9d57b7f2be1a

--- Comment #2 from Boudewijn Rempt  ---
Git commit 4308f313c9240712c2feb05694ab9d57b7f2be1a by Boudewijn Rempt.
Committed on 11/04/2016 at 15:29.
Pushed by rempt into branch 'master'.

This needs a real file, for some reason, not an xml document.

Fixes task T2204

M  +2-3libs/ui/KisMainWindow.cpp

http://commits.kde.org/krita/4308f313c9240712c2feb05694ab9d57b7f2be1a

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