[kdevelop] [Bug 371645] "Program received signal SIGSEGV, Segmentation fault" while idle

2016-11-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=371645

--- Comment #5 from red...@cox.net ---
Something changed in my environment that prevents me from running the AppImage
now so I think it will be best to close this as I can't reproduce it either. 

I will work on the issue eventually probably but it will be at least a few
weeks until I get around to it. 

kdevelop: symbol lookup error: /usr/lib64/libGL.so.1: undefined symbol:
_glapi_Dispatch

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

[kate] [Bug 372129] Kate opens at the center of 2 monitors

2016-11-05 Thread Sergei Danilov
https://bugs.kde.org/show_bug.cgi?id=372129

--- Comment #1 from Sergei Danilov  ---
KDE Frameworks 5.27.0
Qt 5.6.2 (built against 5.6.1)
plasma version: 5.8.2

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

[kate] [Bug 372129] New: Kate opens at the center of 2 monitors

2016-11-05 Thread Sergei Danilov
https://bugs.kde.org/show_bug.cgi?id=372129

Bug ID: 372129
   Summary: Kate opens at the center of 2 monitors
   Product: kate
   Version: 16.08
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: sergeidani...@gmail.com
  Target Milestone: ---

Created attachment 102062
  --> https://bugs.kde.org/attachment.cgi?id=102062=edit
Kate when I open it

1. Setup 2 monitors with a main screen as a left monitor.
2. Open kate
-> instead of opening on the main screen kate opens in the center of 2
monitors.
See attached screenshot and video: https://goo.gl/photos/pgCg7e7LB1BuKQNR6

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

[plasmashell] [Bug 372128] New: KDE crash when switching desktops and clicking Firefox launcher.

2016-11-05 Thread Mitch
https://bugs.kde.org/show_bug.cgi?id=372128

Bug ID: 372128
   Summary: KDE crash when switching desktops and clicking Firefox
launcher.
   Product: plasmashell
   Version: 5.8.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: mitchell.s.cr...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.2)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.7.10-1-MANJARO x86_64
Distribution: "Manjaro Linux"

-- Information about the crash:
- What I was doing when the application crashed:
I pressed a shortcut to switch from Desktop 2 to Desktop 1. Sometime near the
end of the Desktop Cube animation I clicked Firefox Launcher and KDE crashed.
- Custom settings of the application:
I use default KDE (Manjaro settings). I changed the Desktop switch animation
style to the Desktop Cube animation.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4c74b24800 (LWP 732))]

Thread 21 (Thread 0x7f0b53d4e700 (LWP 6566)):
#0  0x7f4c69541dd4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7f4c694fbc7c in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7f4c694fc6ab in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f4c694fc89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f4c6eb5672b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f4c6eb0023a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f4c6e9230f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f4c71c862d5 in  () at /usr/lib/libQt5Qml.so.5
#8  0x7f4c6e927d78 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f4c6da37454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f4c6e23d7df in clone () at /usr/lib/libc.so.6

Thread 20 (Thread 0x7f0b61336700 (LWP 4174)):
#0  0x7f4c6e23448d in poll () at /usr/lib/libc.so.6
#1  0x7f4c694fc786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f4c694fc89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f4c6eb5672b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f4c6eb0023a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f4c6e9230f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f4c71c862d5 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f4c6e927d78 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f4c6da37454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f4c6e23d7df in clone () at /usr/lib/libc.so.6

Thread 19 (Thread 0x7f0b62597700 (LWP 4076)):
#0  0x7f4c694fc13a in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#1  0x7f4c694fc724 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f4c694fc89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f4c6eb5672b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f4c6eb0023a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f4c6e9230f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f4c71c862d5 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f4c6e927d78 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f4c6da37454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f4c6e23d7df in clone () at /usr/lib/libc.so.6

Thread 18 (Thread 0x7f4b84d5a700 (LWP 2236)):
#0  0x7f4c6e23448d in poll () at /usr/lib/libc.so.6
#1  0x7f4c61bb6121 in  () at /usr/lib/libpulse.so.0
#2  0x7f4c61ba78f1 in pa_mainloop_poll () at /usr/lib/libpulse.so.0
#3  0x7f4c61ba7f8e in pa_mainloop_iterate () at /usr/lib/libpulse.so.0
#4  0x7f4c61ba8040 in pa_mainloop_run () at /usr/lib/libpulse.so.0
#5  0x7f4c61bb6069 in  () at /usr/lib/libpulse.so.0
#6  0x7f4c61546ed8 in  () at /usr/lib/pulseaudio/libpulsecommon-9.0.so
#7  0x7f4c6da37454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f4c6e23d7df in clone () at /usr/lib/libc.so.6

Thread 17 (Thread 0x7f4b867fc700 (LWP 1337)):
#0  0x7f4c6da3d10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f4c6e928c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f4bb5f5f1c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f4bb5f63988 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f4bb5f5e263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  

[krita] [Bug 361923] Inconsistencies of rendering (brush stroke) depending viewport zoom

2016-11-05 Thread amanda
https://bugs.kde.org/show_bug.cgi?id=361923

amanda  changed:

   What|Removed |Added

 CC||sanusiharia...@gmail.com

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

[dolphin] [Bug 372127] New: Dolphin crashes during symlink creation

2016-11-05 Thread Fritigern
https://bugs.kde.org/show_bug.cgi?id=372127

Bug ID: 372127
   Summary: Dolphin crashes during symlink creation
   Product: dolphin
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: fritigerngot...@gmail.com
  Target Milestone: ---

Application: dolphin (16.04.3)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.8.0-26-generic x86_64
Distribution: Ubuntu 16.10

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

I was dragging multiple folders (less than 10) to another tab in dolphin with
the intention to create symlinks to these folders, and upon choosing the option
to create the links Dolphin crashed.
This does not happen every time, I have not yet determined what it is exactly
that causes this procedure to crash dolphin.

Hopefully the backtrace (which to me reads as Chinese :-) ) can be more helpful
than I am.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f45941468c0 (LWP 11184))]

Thread 4 (Thread 0x7f456ee42700 (LWP 11187)):
#0  0x7f458a1a28b8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f458a1a2aec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f458e8564ab in QEventDispatcherGlib::processEvents
(this=0x7f45680008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#3  0x7f458e7fe0fa in QEventLoop::exec (this=this@entry=0x7f456ee41d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#4  0x7f458e623d43 in QThread::exec (this=) at
thread/qthread.cpp:500
#5  0x7f458e628c68 in QThreadPrivate::start (arg=0x555787806b00) at
thread/qthread_unix.cpp:341
#6  0x7f458ad3170a in start_thread (arg=0x7f456ee42700) at
pthread_create.c:333
#7  0x7f4593b810af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7f457d579700 (LWP 11186)):
#0  0x7f4593b750bd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f458a1a29d6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f458a1a2aec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f458e8564ab in QEventDispatcherGlib::processEvents
(this=0x7f4578c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7f458e7fe0fa in QEventLoop::exec (this=this@entry=0x7f457d578cd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f458e623d43 in QThread::exec (this=this@entry=0x7f45942a3d60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:500
#6  0x7f459422f575 in QDBusConnectionManager::run (this=0x7f45942a3d60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:171
#7  0x7f458e628c68 in QThreadPrivate::start (arg=0x7f45942a3d60 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:341
#8  0x7f458ad3170a in start_thread (arg=0x7f457d579700) at
pthread_create.c:333
#9  0x7f4593b810af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7f457f115700 (LWP 11185)):
#0  0x7f4593b750bd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f45880acc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f45880ae8d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f4581c9f299 in QXcbEventReader::run (this=0x55578729f090) at
qxcbconnection.cpp:1325
#4  0x7f458e628c68 in QThreadPrivate::start (arg=0x55578729f090) at
thread/qthread_unix.cpp:341
#5  0x7f458ad3170a in start_thread (arg=0x7f457f115700) at
pthread_create.c:333
#6  0x7f4593b810af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x7f45941468c0 (LWP 11184)):
[KCrash Handler]
#6  QScopedPointer::data
(this=0x55570009) at
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:135
#7  qGetPtrHelper (p=...) at
global/qglobal.h:1014
#8  QObject::d_func (this=0x55570001) at
../../include/QtCore/../../src/corelib/kernel/qobject.h:110
#9  QCoreApplication::notifyInternal2 (receiver=0x55570001,
event=event@entry=0x7fff554fbf70) at kernel/qcoreapplication.cpp:1010
#10 0x7f458e8553ae in QCoreApplication::sendEvent (event=0x7fff554fbf70,
receiver=) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:225
#11 QTimerInfoList::activateTimers (this=0x5557872c9f60) at
kernel/qtimerinfo_unix.cpp:637
#12 0x7f458e855909 in timerSourceDispatch (source=) at
kernel/qeventdispatcher_glib.cpp:176
#13 

[kfile] [Bug 372126] New: file open/save dialog for kde4 applications does not respect single-click to open

2016-11-05 Thread David Rankin
https://bugs.kde.org/show_bug.cgi?id=372126

Bug ID: 372126
   Summary: file open/save dialog for kde4 applications does not
respect single-click to open
   Product: kfile
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: drankina...@suddenlinkmail.com
  Target Milestone: ---

Created attachment 102061
  --> https://bugs.kde.org/attachment.cgi?id=102061=edit
File open dialog frok kde4 konqueror

When using the file/open saved dailog in:

 KDE Frameworks 5.27.0
 Qt 5.7.0 (built against 5.7.0)
 The xcb windowing system

If the dialog is called from a kde4 application, e.g. basket, konqueror,
etc..., the file open/save action requires a double-click to actually open a
directory or open a file. A single-click seems to load the file or directory
name into the filename edit widget, but does not actually change directory or
open the file. For example, open your favorite kde4 app, (e.g. konqueror
--profile filemanagement) and the press 'ctrl+o' or choose 'File -> Open'. The
dialog that is presented does not work on a single-click basis.

However, if you do the same with a kde5 app (e.g. kwrite, kate, etc..) the
single-click to change directory, open a file, works as it should.

A screenshot of the dialog at issue is provided in case it helps with
identifying which dialog is at issue. This may be a regression as it seems that
this has been marked fixed related to a couple of individual apps or non-kde
apps, but it is not fixed now regarding kde apps (see, e.g. Bugs
https://bugs.kde.org/show_bug.cgi?id=181017,
https://bugs.kde.org/show_bug.cgi?id=235159)

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

[Discover] [Bug 372087] climbs description

2016-11-05 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=372087

Aleix Pol  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DOWNSTREAM

--- Comment #1 from Aleix Pol  ---
Yes, Kubuntu decided to stay with a broken version despite being offered a
patch and other fixed versions. There's not much I can do.

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

[plasma-pa] [Bug 372125] New: Volume changing time inconsistent

2016-11-05 Thread Max Schettler
https://bugs.kde.org/show_bug.cgi?id=372125

Bug ID: 372125
   Summary: Volume changing time inconsistent
   Product: plasma-pa
   Version: 5.8.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: max.schett...@posteo.de
CC: plasma-b...@kde.org
  Target Milestone: ---

Hi,

when using the global in-/decrease volume hotkeys to change the volume
drastically, i.e. holding the hotkeys, the time it takes until the volume is
changed for the next time is very inconsistent. This makes the reaction feel
slugish to the user, and the audio-feedback is also disrupting the user because
of the delays being unpredictable.

If necessary I can create a screencast showcasing the issue.

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

[plasmashell] [Bug 372124] New: crash when closing window

2016-11-05 Thread cailtin lopez
https://bugs.kde.org/show_bug.cgi?id=372124

Bug ID: 372124
   Summary: crash when closing window
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: cail...@satellitedna.org
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.5.5)

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

-- Information about the crash:
- What I was doing when the application crashed:
this happens several times, close any window and I get the crash report

The crash can be reproduced sometimes.

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

Thread 25 (Thread 0x7fe0f700 (LWP 6322)):
#0  0x7fe215c74d14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fe215c32a5a in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fe215c32ed8 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fe215c32f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fe219ef4d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fe219e9bd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fe219cbd61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fe219cc232f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fe218dbf0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fe2195cc02d in clone () at /lib64/libc.so.6

Thread 24 (Thread 0x7fe125ffa700 (LWP 5964)):
#0  0x7fe218dc303f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fe219cc334b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fe15a27c65f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7fe15a28043a in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7fe15a27a6cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7fe15a280481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7fe15a27a6cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7fe15a280481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7fe15a27a6cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7fe15a280481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7fe15a27a6cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#11 0x7fe15a280481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#12 0x7fe15a27a6cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#13 0x7fe15a27e005 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#14 0x7fe219cc232f in  () at /usr/lib64/libQt5Core.so.5
#15 0x7fe218dbf0a4 in start_thread () at /lib64/libpthread.so.0
#16 0x7fe2195cc02d in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7fe1267fb700 (LWP 5963)):
#0  0x7fe218dc303f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fe219cc334b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fe15a27c65f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7fe15a28043a in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7fe15a27a6cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7fe15a280481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7fe15a27a6cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7fe15a280481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7fe15a27a6cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7fe15a280481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7fe15a27a6cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#11 0x7fe15a280481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#12 0x7fe15a27a6cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#13 0x7fe15a280481 in  () at 

[krita] [Bug 372123] New: When saving a large document, the saving dialog sometimes never goes away, prevents saving

2016-11-05 Thread Andy Statia
https://bugs.kde.org/show_bug.cgi?id=372123

Bug ID: 372123
   Summary: When saving a large document, the saving dialog
sometimes never goes away, prevents saving
   Product: krita
   Version: 3.0.1.1
  Platform: Windows CE
OS: MS Windows
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: asta...@neverdot.com
  Target Milestone: ---

Replication steps which mimic the test file (too large to attach):

1. Create a file with canvas size 5175x2625, 300ppi
2. Add many layers (15 including the background)
3. Draw some strokes using any brush on a layer
4. Save (this save works, takes about 7 seconds)
5. Draw a high number of strokes (about 20-40)
6. Save again

This time the save dialog will remain and never complete.  The file is not
saved and the dialog must be closed to regain control.  The app cursor stays in
the "busy" state after this, allowing menu usage, but not tool use.  The
application may be quit normally, but the document cannot be saved.

Performance settings were:
Memory available: 8079MiB
Memory Limit: 4039MiB
Internal Pool: 199MiB
Swap Undo After: 237MiB
File Size Limit: 4GB
Progress reporting enabled

Tests showed that increasing the internal pool value allowed saving to
complete.

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

[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget

2016-11-05 Thread Benedikt Geißler
https://bugs.kde.org/show_bug.cgi?id=367541

--- Comment #14 from Benedikt Geißler  ---
Created attachment 102060
  --> https://bugs.kde.org/attachment.cgi?id=102060=edit
Backtrace when I clicked on "next month"

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

[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget

2016-11-05 Thread Benedikt Geißler
https://bugs.kde.org/show_bug.cgi?id=367541

--- Comment #13 from Benedikt Geißler  ---
I just noticed that the same things happen when I click on the "next month"
button in the digital clock applet. Here is a backtrace:

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

[konsole] [Bug 370971] Application Crash when spliting and closing panes

2016-11-05 Thread Martin Sandsmark
https://bugs.kde.org/show_bug.cgi?id=370971

Martin Sandsmark  changed:

   What|Removed |Added

 CC||martin.sandsm...@kde.org
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Martin Sandsmark  ---
Fixed by David:
https://quickgit.kde.org/?p=konsole.git=commit=ec172b8f6b39a056326751f26ce81af664f0837f

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

[konsole] [Bug 371863] starting konsole with KDE exec is broken

2016-11-05 Thread Martin Sandsmark
https://bugs.kde.org/show_bug.cgi?id=371863

Martin Sandsmark  changed:

   What|Removed |Added

 CC||martin.sandsm...@kde.org

--- Comment #1 from Martin Sandsmark  ---
I think this could fix what you describe:
https://quickgit.kde.org/?p=konsole.git=commit=4ec9b565800b9e9bdbf45dbb5983530fb95791e7

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

[dolphin] [Bug 306257] Add a feature so that we can save and restore a dolphin session

2016-11-05 Thread Diego Agulló
https://bugs.kde.org/show_bug.cgi?id=306257

Diego Agulló  changed:

   What|Removed |Added

 CC||aeo...@gmail.com

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

[konsole] [Bug 369050] Konsole crashs randomly.

2016-11-05 Thread Martin Sandsmark
https://bugs.kde.org/show_bug.cgi?id=369050

Martin Sandsmark  changed:

   What|Removed |Added

 CC||martin.sandsm...@kde.org

--- Comment #17 from Martin Sandsmark  ---
Can someone see if they can find the actual error message that should be
displayed when Qt aborts Konsole when this happens? Either in the journal (with
«journalctl») or in .xsession-errors?

The message should be something with «Internal error: got invalid meta type
[...]», the interesting thing is the rest of the message indicating the invalid
values.

IMHO, Qt shouldn't abort on this kind of error at all. Unfortunately there's
nothing Konsole or other applications can do about it.

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

[plasmashell] [Bug 372046] plasma5 show tiny icons in HiDPI screens

2016-11-05 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=372046

--- Comment #4 from David Edmundson  ---
Plasma already has a system for allowing you to set env vars between that part
of startkde and kdeinit launching.

Any autostart scripts set as pre-startup are sourced and env vars can be
modified.

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

[frameworks-kwidgetsaddons] [Bug 372058] Konsole crashes when attempting to save output to a file

2016-11-05 Thread Martin Sandsmark
https://bugs.kde.org/show_bug.cgi?id=372058

Martin Sandsmark  changed:

   What|Removed |Added

 CC||kdelibs-b...@kde.org,
   ||martin.sandsm...@kde.org
  Component|general |general
Product|konsole |frameworks-kwidgetsaddons
   Assignee|konsole-de...@kde.org   |cf...@kde.org
Version|16.08.1 |unspecified

--- Comment #1 from Martin Sandsmark  ---
Re-assigning to KWidgetsAddons, which the crash is in. Potentially it is in the
KDE platform plugin file dialog code.

It's very unlikely that it is a Konsole bug, however. The only unusual thing
Konsole does is re-use the QDialog instance.

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

[konsole] [Bug 372065] Konsole crashes on average once a day

2016-11-05 Thread Martin Sandsmark
https://bugs.kde.org/show_bug.cgi?id=372065

Martin Sandsmark  changed:

   What|Removed |Added

 CC||martin.sandsm...@kde.org

--- Comment #1 from Martin Sandsmark  ---
Long shot, but a couple of commits recently fixed some signal connection stuff
in TerminalDisplay (ec172b8f6b39a056326751f26ce81af664f0837f), could you try
with the latest git master and see if it still happens?

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

[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)

2016-11-05 Thread Martin Sandsmark
https://bugs.kde.org/show_bug.cgi?id=372116

Martin Sandsmark  changed:

   What|Removed |Added

 CC||martin.sandsm...@kde.org
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Martin Sandsmark  ---
Should be fairly trivial to implement, look at
https://quickgit.kde.org/?p=konsole.git=commit=bb6abc0bc8a23f46752f7341d43e4275e9085fa9
for inspiration.

The question is if this could have security implications.

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

[kwin] [Bug 372122] New: Kwin window-specific settings dialog window is too large for 1366x768

2016-11-05 Thread AppAraat
https://bugs.kde.org/show_bug.cgi?id=372122

Bug ID: 372122
   Summary: Kwin window-specific settings dialog window is too
large for 1366x768
   Product: kwin
   Version: 5.8.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: 4xr6ah+4wznsmksoi...@sharklasers.com
  Target Milestone: ---

Created attachment 102059
  --> https://bugs.kde.org/attachment.cgi?id=102059=edit
screenshot of the desktop with affected windows open

Overview:
On a resolution of 1366x768 I can not see the bottom buttons of the "Displays"
dialog window.

Steps to reproduce:
1) Set your resolution to 1366x768
2) Open Firefox (or any other GUI program).
3) Left-click the title bar
4) Select "More actions" ---> Window Manager Settings

Actual results:
Window went partially under my Task Manager panel.

Expected results:
Window displayed fully, or if not, it could be scaled / resized so that it did.

Additional information:
* I've discovered this bug on Virtualbox Version 5.0.28 r111378, but I don't
think this is very relevant.
* Check the attached screenshot, it should illustrate this bug clearly.

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

[kate] [Bug 366568] when dragging & dropping folders, contained files are opened as blank / new.

2016-11-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=366568

--- Comment #4 from xaxa...@gmail.com ---
I think somehow my status changes weren't applied when I changed it. If someone
just reverted them, sorry - not trying to fight it.

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

[digikam] [Bug 372093] corrupts image file when crashing

2016-11-05 Thread Kai
https://bugs.kde.org/show_bug.cgi?id=372093

--- Comment #3 from Kai  ---
I only worked with JPGs in that case.
It will be a few days before I have access to that computer again. I'm going to
add all the version details then.

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

[kde] [Bug 372054] KDE screen saver not working when VirtualBox guest is running.

2016-11-05 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=372054

--- Comment #3 from Christoph Feck  ---
You could report it to the bug tracker of your distribution to find out if they
still maintain the old version 4 of the KDE workspace.

All major Linux distributions have updated to version 5. It is a bit
unfortunate that you are using a distribution that has not yet updated, despite
our maintaince announcements over three years ago.

The bugs.kde.org bugtracker still accepts reports for recent versions.

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

[kdeconnect] [Bug 367827] Desktop session crash caused by kdeconnect

2016-11-05 Thread Benedikt Geißler
https://bugs.kde.org/show_bug.cgi?id=367827

--- Comment #4 from Benedikt Geißler  ---
Since summer I am using openSUSE Tumbleweed (currently with kdeconnect 1.0.1,
'kdeconnect-cli' says 1.0) now and did not experience this issue during the
last weeks, too.

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

[kdeconnect] [Bug 367827] Desktop session crash caused by kdeconnect

2016-11-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=367827

--- Comment #3 from li...@alaya.net ---
I did not mark status as "resolved" since users on 16.04 LTS release may still
be affected by it.

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

[kdeconnect] [Bug 367827] Desktop session crash caused by kdeconnect

2016-11-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=367827

li...@alaya.net changed:

   What|Removed |Added

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

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

[kdeconnect] [Bug 367827] Desktop session crash caused by kdeconnect

2016-11-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=367827

li...@alaya.net changed:

   What|Removed |Added

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

--- Comment #2 from li...@alaya.net ---
Am now using Ubuntu 16.10 "Yakkety" which has kdeconnect version 0.8-0ubuntu5
and this issue no longer occurs.

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

[kdeconnect] [Bug 367827] Desktop session crash caused by kdeconnect

2016-11-05 Thread Benedikt Geißler
https://bugs.kde.org/show_bug.cgi?id=367827

Benedikt Geißler  changed:

   What|Removed |Added

 CC||bened...@g5r.eu

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

[kate] [Bug 366766] Dragging and dropping the same file multiple times creates duplicate entries.

2016-11-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=366766

xaxa...@gmail.com changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
Version|16.04   |16.08
   Severity|normal  |grave

--- Comment #2 from xaxa...@gmail.com ---
This seems resolved as of 2016-11-06 in Kate 16.08.2, master branch.
I'll close it.

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

[kate] [Bug 366568] when dragging & dropping folders, contained files are opened as blank / new.

2016-11-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=366568

xaxa...@gmail.com changed:

   What|Removed |Added

   Platform|Ubuntu Packages |unspecified
 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED
   Severity|normal  |grave
Version|16.04   |16.08

--- Comment #3 from xaxa...@gmail.com ---
Reopening, sorry.

Still occurs on Kate 16.08.2 - master branch (cloned today, 06/Nov/2016).

Tried twice, once on Mint 18, once on Manjaro 16.10.

Gonna bump this up to 'grave' as it has caused data loss - accidentally saving
all wiped about 10 files.

Initial report is still accurate.

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

[Breeze] [Bug 372119] list-remove-symbolic.svg uses wrong image

2016-11-05 Thread andreas
https://bugs.kde.org/show_bug.cgi?id=372119

andreas  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/bree
   ||ze-icons/78b0964689d5f3aef4
   ||ca0b1b1374ed2ecfb8287b

--- Comment #1 from andreas  ---
Git commit 78b0964689d5f3aef4ca0b1b1374ed2ecfb8287b by andreas kainz.
Committed on 05/11/2016 at 22:04.
Pushed by andreask into branch 'master'.

fix BUG:372119 list-remove-symcolic use wrong image

T  +77   -1icons/actions/symbolic/list-remove-symbolic.svg

http://commits.kde.org/breeze-icons/78b0964689d5f3aef4ca0b1b1374ed2ecfb8287b

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

[kde] [Bug 372121] New: Everything is crashing

2016-11-05 Thread Martin
https://bugs.kde.org/show_bug.cgi?id=372121

Bug ID: 372121
   Summary: Everything is crashing
   Product: kde
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: mrb...@gmail.com
  Target Milestone: ---

Tried live image  neon-useredition-20161103-1018-amd64.iso.
Everything is crashing but the installer.
Installation was worked until grub installation. Grub installation crashed
also.
System completely unusable.

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

[valgrind] [Bug 372120] New: c++ demangler demangles symbols which are not c++

2016-11-05 Thread Philippe Waroquiers
https://bugs.kde.org/show_bug.cgi?id=372120

Bug ID: 372120
   Summary: c++ demangler demangles symbols which are not c++
   Product: valgrind
   Version: 3.12 SVN
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: philippe.waroqui...@skynet.be
  Target Milestone: ---

For the below code, the demanglers demangle a non c++ symbol as if it
would be a mangled c++ name.
This was detected on an Ada program (as gnat mangles Ada names by
replacing . by __) but that equally happens on c symbols having 2 underscores.
To reproduce:
gcc -g -o demang demang.c
./vg-in-place --leak-check=full ./demang
==30660== 90 bytes in 9 blocks are definitely lost in loss record 2 of 2
==30660==at 0x4C27BB5: malloc (vg_replace_malloc.c:299)
==30660==by 0x400515: main__calling__some(...)(long long,...)(char)
(demang.c:7)
==30660==by 0x40052C: main (demang.c:12)


#include 
char *v;
void main__calling__some__exec(void)
{  
   int i;
   for (i = 0; i < 10; i++)
  v = malloc(10);
}

main ()
{
   main__calling__some__exec();
}

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

[Breeze] [Bug 372119] list-remove-symbolic.svg uses wrong image

2016-11-05 Thread DrSlony
https://bugs.kde.org/show_bug.cgi?id=372119

DrSlony  changed:

   What|Removed |Added

 CC||b...@londonlight.org

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

[Breeze] [Bug 372119] New: list-remove-symbolic.svg uses wrong image

2016-11-05 Thread DrSlony
https://bugs.kde.org/show_bug.cgi?id=372119

Bug ID: 372119
   Summary: list-remove-symbolic.svg uses wrong image
   Product: Breeze
   Version: 5.8.3
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: b...@londonlight.org
CC: kain...@gmail.com
  Target Milestone: ---

Hello

I noticed that Gtk::SpinButton's minus button lacked an icon and instead of
showing a minus it showed a generic "missing-image" image:
https://i.imgur.com/UD6OaUH.png

Turns out that the image was not missing, that IS the image.
/usr/share/icons/breeze/actions/symbolic/list-remove-symbolic.svg

Please fix the icon so that it looks like "-" to match the "+".

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

[kate] [Bug 369008] Kate crashes when doing lookoup

2016-11-05 Thread Tore Havn
https://bugs.kde.org/show_bug.cgi?id=369008

Tore Havn  changed:

   What|Removed |Added

 CC||tore.h...@gmail.com

--- Comment #1 from Tore Havn  ---
I am noticing the same behaviour. Trying to do Lookup segfaults Kate. I'm on
Frameworks 5.27.

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

[digikam] [Bug 285683] Already imported pictures not recognized after daylight savings time

2016-11-05 Thread Nicofo
https://bugs.kde.org/show_bug.cgi?id=285683

Nicofo  changed:

   What|Removed |Added

   Version Fixed In|5.1.0   |

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

[digikam] [Bug 285683] Already imported pictures not recognized after daylight savings time

2016-11-05 Thread Nicofo
https://bugs.kde.org/show_bug.cgi?id=285683

Nicofo  changed:

   What|Removed |Added

Version|4.4.0   |5.1.0

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

[digikam] [Bug 285683] Already imported pictures not recognized after daylight savings time

2016-11-05 Thread Nicofo
https://bugs.kde.org/show_bug.cgi?id=285683

--- Comment #11 from Nicofo  ---
Created attachment 102058
  --> https://bugs.kde.org/attachment.cgi?id=102058=edit
Same picture undully imported twice

Hi,
I reopen this bug because, unlike I thought, it is actually not solved.

Last DST was last weekend (30 Oct): all the pictures I made before (and that I
had already imported) are not recognized anymore as already imported: if I
import "New items" in Digikam, all my pictures imported before DST are
re-imported again :(

See picture attached (file digikam4.db), with the example of one picture taken
before DST (25 Sept 18h35) but now recognized one hour later (25 Sept 19h35) so
re-imported by digikam.

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

[digikam] [Bug 285683] Already imported pictures not recognized after daylight savings time

2016-11-05 Thread Nicofo
https://bugs.kde.org/show_bug.cgi?id=285683

Nicofo  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

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

[ark] [Bug 160570] Provide more wizard-like creation tool

2016-11-05 Thread Ragnar Thomsen
https://bugs.kde.org/show_bug.cgi?id=160570

Ragnar Thomsen  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 CC||rthoms...@gmail.com
 Status|CONFIRMED   |RESOLVED

--- Comment #4 from Ragnar Thomsen  ---
We now have the new CreateDialog so closing as wontfix.

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

[kwin] [Bug 372114] Kwin crashed unexpectedly

2016-11-05 Thread Martin Gräßlin
https://bugs.kde.org/show_bug.cgi?id=372114

Martin Gräßlin  changed:

   What|Removed |Added

 CC||larr...@kde.org

--- Comment #1 from Martin Gräßlin  ---
@Antonio: we might have a problem here with the new threaded safety check.
Unfortunately Arch, so no debug symbols and I don't really understand what's
going on.

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

[valgrind] [Bug 371916] execution tree xtree concept

2016-11-05 Thread Philippe Waroquiers
https://bugs.kde.org/show_bug.cgi?id=371916

--- Comment #14 from Philippe Waroquiers  ---
(In reply to Ivo Raisr from comment #13)
> Thanks for addressing my comments. Especially for providing hints on Xtree
> usage!
> I am happy with the documentation and pub_tool_xtree.h interface.
> However note I have not reviewed any implementation files.
> 
> The last remark I have: have you considered naming the xtree output file
> based on the executed program name, such as .kcg? Currently the
> default xtmemory.kcg will get overwritten every time, even for different
> profiled programs.
For the xtmemory gdbserver command: the user can give a different name if
desired, but the default is to overwrite. This is also the case
for other gdbserver commands producing files, e.g. massif snapshots.

For xtree memory files produced due to command line, the default is similar
to e.g. log files or callgrind output files, or ...:
filename includes %p expanded as pid, to avoid overwriting.
(this %p is needed in particular for forking programs).

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

[plasmashell] [Bug 372118] New: plasmashell crash on startup

2016-11-05 Thread Tim Small
https://bugs.kde.org/show_bug.cgi?id=372118

Bug ID: 372118
   Summary: plasmashell crash on startup
   Product: plasmashell
   Version: 5.8.2
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: t...@buttersideup.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.2)

Qt Version: 5.7.1
Frameworks Version: 5.27.0
Operating System: Linux 4.8.0-1-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

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

Crash during login after package upgrade on Debian sid.  The same problem
recurrs when manually starting plasmashell after startup.

- Unusual behavior I noticed:

Debug messages from starting manually on console:

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-tim'
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/ScrollView.qml:198:
TypeError: Property 'hasOwnProperty' of object QQuickListView_QML_99(0x29f6f80)
is not a function
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Styles/Plasma/ScrollViewStyle.qml:71:
TypeError: Cannot read property 'atYBeginning' of null
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Styles/Plasma/ScrollViewStyle.qml:90:
TypeError: Cannot read property 'atYEnd' of null
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Styles/Plasma/ScrollViewStyle.qml:108:
TypeError: Cannot read property 'atXBeginning' of null
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Styles/Plasma/ScrollViewStyle.qml:126:
TypeError: Cannot read property 'atXEnd' of null
No metadata file in the package, expected it at:
"/usr/share/wallpapers/Castilla_Sky/contents/images/"
No metadata file in the package, expected it at:
"/usr/share/wallpapers/Castilla_Sky/contents/images/"
No metadata file in the package, expected it at:
"/usr/share/wallpapers/Castilla_Sky/contents/images/"
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:83:
TypeError: Cannot read property 'Layout' of null
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/ScrollView.qml:198:
TypeError: Property 'hasOwnProperty' of object QQuickRow(0x46d46b0) is not a
function
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipDelegate.qml:131:
TypeError: Type error
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Styles/Plasma/ScrollViewStyle.qml:71:
TypeError: Cannot read property 'atYBeginning' of null
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Styles/Plasma/ScrollViewStyle.qml:90:
TypeError: Cannot read property 'atYEnd' of null
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Styles/Plasma/ScrollViewStyle.qml:108:
TypeError: Cannot read property 'atXBeginning' of null
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Styles/Plasma/ScrollViewStyle.qml:126:
TypeError: Cannot read property 'atXEnd' of null
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:99:
TypeError: Cannot read property of null
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/ScrollView.qml:198:
TypeError: Property 'hasOwnProperty' of object QQuickRow(0x4baaa50) is not a
function
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipDelegate.qml:131:
TypeError: Type error
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Styles/Plasma/ScrollViewStyle.qml:71:
TypeError: Cannot read property 'atYBeginning' of null
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Styles/Plasma/ScrollViewStyle.qml:90:
TypeError: Cannot read property 'atYEnd' of null
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Styles/Plasma/ScrollViewStyle.qml:108:
TypeError: Cannot read property 'atXBeginning' of null
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Styles/Plasma/ScrollViewStyle.qml:126:
TypeError: Cannot read property 'atXEnd' of null
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:99:
TypeError: Cannot read property of null
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:99:
TypeError: Cannot read property of null
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:99:
TypeError: Cannot read property of null
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:99:
TypeError: Cannot read property of null
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:83:
TypeError: Cannot read property 'Layout' of null
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/ScrollView.qml:198:
TypeError: Property 'hasOwnProperty' of object 

[valgrind] [Bug 371916] execution tree xtree concept

2016-11-05 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=371916

--- Comment #13 from Ivo Raisr  ---
Thanks for addressing my comments. Especially for providing hints on Xtree
usage!
I am happy with the documentation and pub_tool_xtree.h interface.
However note I have not reviewed any implementation files.

The last remark I have: have you considered naming the xtree output file based
on the executed program name, such as .kcg? Currently the default
xtmemory.kcg will get overwritten every time, even for different profiled
programs.

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

[kwin] [Bug 372109] kwin_x11 crashes while minimizing/maximizing Firefox window

2016-11-05 Thread Eugene
https://bugs.kde.org/show_bug.cgi?id=372109

--- Comment #3 from Eugene  ---
Update. I've been configuring a 'Hide Caption Titlebar Plus' Firefox plugin
which hides title bar for it and ca add some additional options. May it caused
the crash?

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

[kwin] [Bug 372109] kwin_x11 crashes while minimizing/maximizing Firefox window

2016-11-05 Thread Eugene
https://bugs.kde.org/show_bug.cgi?id=372109

--- Comment #2 from Eugene  ---
I don't know, Martin, may be it's some kind of coincidence. But today kwin
crashed several times in a row and then it stops. I don't know really by what
it was really caused. When It happened first time I've been working with
firefox. When it crashed I've pushed  firefox button on kickoff panel to
minimize it to button but then it crashed again. And so on several times.

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

[kdenlive] [Bug 372020] Ungrouped clips don't stay ungrouped.

2016-11-05 Thread Edward
https://bugs.kde.org/show_bug.cgi?id=372020

--- Comment #3 from Edward  ---
Created attachment 102057
  --> https://bugs.kde.org/attachment.cgi?id=102057=edit
The file I was working on when discovering the problem.

Here is the file I was working on. I just now loaded the project, ungrouped,
and resaved. Still grouped. And yes, this is 16.08.2 as set at the very top of
this page.

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

[kwin] [Bug 372083] Task Switcher visualization stuck on "Breeze"

2016-11-05 Thread anewuser
https://bugs.kde.org/show_bug.cgi?id=372083

anewuser  changed:

   What|Removed |Added

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

--- Comment #7 from anewuser  ---
I found the configuration file at ~/.config/kwinrc . Its ownership had been
indeed transferred to root. I didn't change any settings or mess up with system
files over the last weeks, so I still think it was caused by some buggy update.

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

[plasmashell] [Bug 366298] widgets remain locked after selecting the "unlock widgets" option from the desktop context menu

2016-11-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=366298

alexandre.skobin...@gmail.com changed:

   What|Removed |Added

 Status|NEEDSINFO   |UNCONFIRMED
 Resolution|WAITINGFORINFO  |---

--- Comment #5 from alexandre.skobin...@gmail.com ---
Haven't found another solution to this issue than resetting my plasma
installed, so I can't confirm. I'll try it on a vm when I have the time, but if
anyone can reproduce it before that, I'd be very grateful.

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

[krita] [Bug 372117] New: hand shortcut issue

2016-11-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=372117

Bug ID: 372117
   Summary: hand shortcut issue
   Product: krita
   Version: 3.0.1
  Platform: Homebrew (Mac OS X)
OS: other
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: tablet support
  Assignee: krita-bugs-n...@kde.org
  Reporter: kspcoo...@gmail.com
  Target Milestone: ---

So when I first open Krita i can use my shortcut button for the hand right away
but once I use another shortcut I can no longer use the hand, UNLESS I go to
the hand and change it to default but again every time I use a different
shortcut button it stops working. It's getting pretty annoying and interrupts
my flow of work.

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

[kwin] [Bug 372083] Task Switcher visualization stuck on "Breeze"

2016-11-05 Thread anewuser
https://bugs.kde.org/show_bug.cgi?id=372083

--- Comment #6 from anewuser  ---
Created attachment 102056
  --> https://bugs.kde.org/attachment.cgi?id=102056=edit
task switcher options

(In reply to Martin Gräßlin from comment #5)
> > All switchers.
> 
> Could you define that in a better way. I don't know which switchers are
> installed on your system.

The ones provided by default. I didn't install any new one.

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

[plasmashell] [Bug 367627] Missing systray icon from application

2016-11-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=367627

--- Comment #7 from alex0n...@gmail.com ---
I`m updated to 5.8.2, 
- error message in .xsession-errors is gone
- No steam and firetray icons
- "invisible" icons not touchable (you cant open thunderbird from system tray
by click on)

Skype icon is shown in systray, so xembedsniproxy runs 

My system:
-Gentoo linux x86_64
-Qt 5.6.2
-kde-frameworks 5.27.0
-kde-plasma 5.8.2
-no systemd (unsing openrc + consolikit)


(In reply to David Edmundson from comment #6)
> If possible can you revert 749f60b89f4a166833fb64a5b593a801f63f9615 and see
> if that fixes it?
I`m noob, but I can try, if you give me link on
749f60b89f4a166833fb64a5b593a801f63f9615 (I could not find it).

sorry for my "perfect" English

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

[konsole] [Bug 372116] New: Feature Request: Support OSC 52 (copy to clipboard)

2016-11-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=372116

Bug ID: 372116
   Summary: Feature Request: Support OSC 52 (copy to clipboard)
   Product: konsole
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: copy-paste
  Assignee: konsole-de...@kde.org
  Reporter: xiaqq...@gmail.com
  Target Milestone: ---

OSC 52 is a escape sequence that allows terminal applications to manipulate the
system clipboard. For instance, tmux will write such sequences when copying
text, if the set-clipboard option is on.

The following description is copied from
https://github.com/mintty/mintty/issues/258:

small rfe, add support for xterm's clipboard OSC

paraphrasing from http://invisible-island.net/xterm/ctlseqs/ctlseqs.html

Operating System Controls
OSC 52 ; Pc ; Pd ST
OSC 52 ; Pc ; Pd BEL

-> Manipulate Selection Data.

The first parameter, Pc, is used to construct a list of selection parameters 
for clipboard, primary, select, or cut buffers (not important at all).  If the 
parameter is empty, xterm uses s 0 , to specify the configurable 
primary/clipboard selection and cut buffer 0. (Would be enough to always 
default to clipboard)

The second parameter, Pd, gives the selection data.  Normally this is a string 
encoded in base64.  The data becomes the new selection, which is then available 
for pasting by other applications. (This is important, base64 encoded data 
should be decoded and saved in the clipboard)

If the second parameter is a ? , xterm replies to the host with the selection 
data encoded using the same protocol.

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

[krita] [Bug 371124] Frequent crash without apparent common cause, I have the reports from drmingw

2016-11-05 Thread María
https://bugs.kde.org/show_bug.cgi?id=371124

--- Comment #35 from María  ---
but I'm noticing that in 3.0.91 not always appear that small window of "saving
document'

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

[kscreenlocker] [Bug 364915] After a suspend/resume cycle, desktop is shown for a moment before locker hides it

2016-11-05 Thread Jakub Gocoł
https://bugs.kde.org/show_bug.cgi?id=364915

Jakub Gocoł  changed:

   What|Removed |Added

 CC||jakub.go...@gmail.com

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

[KScreen] [Bug 372115] "Displays" settings window too large for 1366x768

2016-11-05 Thread AppAraat
https://bugs.kde.org/show_bug.cgi?id=372115

AppAraat <4xr6ah+4wznsmksoi...@sharklasers.com> changed:

   What|Removed |Added

Summary|Display settings window too |"Displays" settings window
   |large for 1366x768  |too large for 1366x768

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

[KScreen] [Bug 372115] New: Display settings window too large for 1366x768

2016-11-05 Thread AppAraat
https://bugs.kde.org/show_bug.cgi?id=372115

Bug ID: 372115
   Summary: Display settings window too large for 1366x768
   Product: KScreen
   Version: 5.8.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: se...@kde.org
  Reporter: 4xr6ah+4wznsmksoi...@sharklasers.com
  Target Milestone: ---

Created attachment 102055
  --> https://bugs.kde.org/attachment.cgi?id=102055=edit
screenshot of the desktop with affected windows open

Overview:
On a resolution of 1366x768 I can not see the bottom buttons of the "Displays"
dialog window.

Steps to reproduce:
1) Set your resolution to 1366x768
2) Open the "Displays" dialog window.

Actual results:
Window went partially under my Task Manager panel.

Expected results:
Window displayed fully, or if not, it could be scaled / resized so that it did.

Additional information:
* I've discovered this bug on Virtualbox Version 5.0.28 r111378, but I don't
think this is very relevant.
* Check the attached screenshot, it should illustrate this bug clearly.

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

[dolphin] [Bug 362899] dolphin crashed when I tried to delete file

2016-11-05 Thread RJ
https://bugs.kde.org/show_bug.cgi?id=362899

RJ  changed:

   What|Removed |Added

 CC||ogldel...@mail.ru

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

[kontact] [Bug 372034] Kontact crashes with segmentation fault when a mail from the message list is selected

2016-11-05 Thread Matthias Nagel
https://bugs.kde.org/show_bug.cgi?id=372034

--- Comment #2 from Matthias Nagel  ---
Some snippet from .xsession-error:

kontact:
/var/tmp/portage/x11-libs/libdrm-2.4.70/work/libdrm-2.4.70/nouveau/pushbuf.c:727:
nouveau_pushbuf_data: Assertion »kref« failed.
*** KMail got signal 6 (Exiting)
*** Dead letters dumped.
[1105/184917:ERROR:gles2_cmd_decoder.cc(2109)]
[.CommandBufferContext.RenderWorker-0x1a44370]GL ERROR :GL_OUT_OF_MEMORY :
ScopedTextureBinder::dtor: <- error from previous GL command
[1105/184917:ERROR:gles2_cmd_decoder.cc(4471)] Error: 5 for Command
kCopySubTextureCHROMIUM
[1105/184917:ERROR:gles2_cmd_decoder.cc(3579)]   GLES2DecoderImpl: Trying to
make lost context current.
KCrash: Application 'kontact' crashing...

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

[kdeplasma-addons] [Bug 364309] don't work in breeze dark

2016-11-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=364309

dzert...@o2.pl changed:

   What|Removed |Added

 CC||dzert...@o2.pl

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

[Breeze] [Bug 371913] icon request: KeepassX

2016-11-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=371913

--- Comment #1 from t...@gmx.com ---
There is no breeze application icon, therefore KeepassX defaults to its
standard icon.

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

[Breeze] [Bug 371914] Icon request: Claws-mail

2016-11-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=371914

--- Comment #4 from t...@gmx.com ---
I set a GTK theme normally, otherwise the breeze-gtk theme is applied. In the
application menu and task manager the app-icon is using the application default
and not a breeze style icon.

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

[plasmashell] [Bug 372079] Animation performance decrease as time goes on

2016-11-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=372079

--- Comment #3 from cristian...@gmail.com ---
(In reply to David Edmundson from comment #1)
> Thanks, but this is too vague to be a bug report.

Alright, I'll try to provide more info:
:Occurs regardless of rendering backend (currently using 3.1 however) and scale
method (currently using smooth)
:Vsync is automatic and no applications can block compositing (although this
used to be on for mpv, but I unchecked that box for testing purposes

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

[plasmashell] [Bug 372079] Animation performance decrease as time goes on

2016-11-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=372079

cristian...@gmail.com changed:

   What|Removed |Added

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

--- Comment #2 from cristian...@gmail.com ---
(In reply to David Edmundson from comment #1)
> Thanks, but this is too vague to be a bug report.

I am aware, but what else am I supposed to provide? The bug itself happens
consistently after using the computer for a few hours (browsing, media
watching, some programming).

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

[kwin] [Bug 372114] New: Kwin crashed unexpectedly

2016-11-05 Thread Sam
https://bugs.kde.org/show_bug.cgi?id=372114

Bug ID: 372114
   Summary: Kwin crashed unexpectedly
   Product: kwin
   Version: 5.8.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: sammerc...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.8.3)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.7.5-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
I was starting KDE through startx from the terminal when I recived an error
saying "Kwin crashed unexpectedly".

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3362444840 (LWP 724))]

Thread 7 (Thread 0x7f3327a46700 (LWP 888)):
#0  0x7f335b0b410f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f335e43fac4 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f335e43fb09 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f335b0ae454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f3361e877df in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f33290ce700 (LWP 804)):
#0  0x7f335b0b410f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f333d14988b in  () at /usr/lib/xorg/modules/dri/r600_dri.so
#2  0x7f333d1496e7 in  () at /usr/lib/xorg/modules/dri/r600_dri.so
#3  0x7f335b0ae454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f3361e877df in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f333e305700 (LWP 801)):
[KCrash Handler]
#6  0x7f335f4412d2 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f335f3de856 in QLockFile::tryLock(int) () at
/usr/lib/libQt5Core.so.5
#8  0x7f33612092d9 in  () at /usr/lib/libKF5ConfigCore.so.5
#9  0x7f33611ed2b0 in KConfig::sync() () at /usr/lib/libKF5ConfigCore.so.5
#10 0x7f3344fdfdf5 in  () at
/usr/lib/qt/plugins/org.kde.kwin.platforms/KWinX11Platform.so
#11 0x7f335f4d99ce in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/libQt5Core.so.5
#12 0x7f335f4e66d8 in QTimer::timerEvent(QTimerEvent*) () at
/usr/lib/libQt5Core.so.5
#13 0x7f335f4da473 in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#14 0x7f3360192e0c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#15 0x7f336019a581 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#16 0x7f335f4adde0 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#17 0x7f335f5016ae in QTimerInfoList::activateTimers() () at
/usr/lib/libQt5Core.so.5
#18 0x7f335f4ff618 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#19 0x7f335f4ac23a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#20 0x7f335f2cf0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#21 0x7f335f2d3d78 in  () at /usr/lib/libQt5Core.so.5
#22 0x7f335b0ae454 in start_thread () at /usr/lib/libpthread.so.0
#23 0x7f3361e877df in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f333f356700 (LWP 796)):
#0  0x7f3361e7e551 in ppoll () at /usr/lib/libc.so.6
#1  0x7f335f4fdac9 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f335f4ff3b8 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f335f4ac23a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f335f2cf0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f3359dfc2d5 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f335f2d3d78 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f335b0ae454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f3361e877df in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f3345a06700 (LWP 750)):
#0  0x7ffdfbba1959 in  ()
#1  0x7ffdfbba1c2d in clock_gettime ()
#2  0x7f3361e946b6 in clock_gettime () at /usr/lib/libc.so.6
#3  0x7f335f3791a1 in  () at /usr/lib/libQt5Core.so.5
#4  0x7f335f5003a9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib/libQt5Core.so.5
#5  0x7f335f500955 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/libQt5Core.so.5
#6  0x7f335f4ff694 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#7  0x7f335f4ac23a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#8  0x7f335f2cf0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#9  0x7f3358face55 in  () at /usr/lib/libQt5DBus.so.5
#10 0x7f335f2d3d78 in  () at /usr/lib/libQt5Core.so.5
#11 0x7f335b0ae454 in start_thread () at /usr/lib/libpthread.so.0
#12 0x7f3361e877df in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f3347bc6700 (LWP 

[kwin] [Bug 360033] Cannot enable compositing with OpenGL GLX

2016-11-05 Thread Martin Gräßlin
https://bugs.kde.org/show_bug.cgi?id=360033

--- Comment #49 from Martin Gräßlin  ---
@Cedric: you are experiencing a crash which is not the same problem as original
described in this bug report. Please report a new bug with the backtrace of the
crash.

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

[kwin] [Bug 372083] Task Switcher visualization stuck on "Breeze"

2016-11-05 Thread Martin Gräßlin
https://bugs.kde.org/show_bug.cgi?id=372083

--- Comment #5 from Martin Gräßlin  ---
> All switchers.

Could you define that in a better way. I don't know which switchers are
installed on your system.

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

[kwin] [Bug 371537] Temporary freeze when showing multiple tray notifications

2016-11-05 Thread Martin Gräßlin
https://bugs.kde.org/show_bug.cgi?id=371537

--- Comment #16 from Martin Gräßlin  ---
Really difficult. The problem could be anywhere and thus asking for specific
debug info is tricky. I'm kind of lacking ideas where the problem is and what
could cause it. A reliable way to reproduce would be good, but we don't have
that as even for you it only happens from time to time.

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

[plasmashell] [Bug 371699] No system tray after booting with second monitor connected.

2016-11-05 Thread demlak
https://bugs.kde.org/show_bug.cgi?id=371699

--- Comment #2 from demlak  ---
still occur on plasma 5.8.3 for me

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

[plasmashell] [Bug 371699] No system tray after booting with second monitor connected.

2016-11-05 Thread demlak
https://bugs.kde.org/show_bug.cgi?id=371699

demlak  changed:

   What|Removed |Added

 CC||kde-bugtrac...@demlak.de

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

[keditbookmarks] [Bug 372113] New: Regression: in KF5 deletes bookmark without confirmation and with no undo

2016-11-05 Thread Jonathan Marten
https://bugs.kde.org/show_bug.cgi?id=372113

Bug ID: 372113
   Summary: Regression: in KF5 deletes bookmark without
confirmation and with no undo
   Product: keditbookmarks
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: j...@keelhaul.me.uk
  Target Milestone: ---

The KDE4 version of keditbookmarks had Undo and Redo actions (in their expected
place in the "Edit" menu).  This meant that an unintended delete of a bookmark
or folder could be reversed.

Now in the KF5 versions these actions appear to be not present.  This means
that deleting a bookmark happens immediately without confirmation, with no way
of undoing the action or recovering the deleted bookmark.

The delete action should either prompt for confirmation, or it should be able
to be undone.

This is keditbookmarks version 5.0 started standalone (i.e. not from within
Konqueror).

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

[kio-gdrive] [Bug 371954] Gdrive doesn't show all files/folders

2016-11-05 Thread Elvis Angelaccio
https://bugs.kde.org/show_bug.cgi?id=371954

--- Comment #5 from Elvis Angelaccio  ---
(In reply to Michał Dybczak from comment #4)
> Created attachment 102039 [details]
> Output of "journalctl -b | grep kf5.kio.gdrive"

Thanks. Can you also attach the output of "journalctl -b | grep org.kde.kgapi"
?

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

[kwin] [Bug 372083] Task Switcher visualization stuck on "Breeze"

2016-11-05 Thread anewuser
https://bugs.kde.org/show_bug.cgi?id=372083

--- Comment #4 from anewuser  ---
I can't disable the screen edge action either (which I had previously
disabled). Maybe it's a permissions issue after all. How to verify this?

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

[kwin] [Bug 360033] Cannot enable compositing with OpenGL GLX

2016-11-05 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=360033

--- Comment #48 from k...@hottier.com ---
Some additional debug informations with QT_LOGGING_RULES="*.debug=true",
It seems that at a certain moment we loose the X11 connection.

I do not know if I should open a new bug report with this new informations, or
if this thread is the right one.


QT_LOGGING_RULES="*.debug=true" kwin_x11 --replace

qt.qpa.screen: Output VGA-0 is not connected
qt.qpa.screen: Output DVI-I-0 is not connected
qt.qpa.screen: Output TV-0 is not connected
qt.qpa.screen: adding QXcbScreen(0xc2a240, name="DVI-I-1",
geometry=1280x1024+0+0, availableGeometry=1280x997+0+0, devicePixelRatio=1.0,
logicalDpi=QPair(85.1,86.1), physicalSize=376.0x301.0mm, screenNumber=0,
virtualSize=1280x1024 (1280.0x1024.0mm),
orientation=Qt::ScreenOrientation(LandscapeOrientation), depth=24,
refreshRate=60.0, root=252, windowManagerName="KWin") (Primary: true )
qt.qpa.screen: primary output is "DVI-I-1"
qt.qpa.input.devices: XInput version 2.2 is available and Qt supports 2.2 or
greater
qt.qpa.input.devices: input device  Virtual core XTEST pointer ID 4
qt.qpa.input.devices:has 10 buttons
qt.qpa.input.devices:has valuator "Rel X" recognized? true
qt.qpa.input.devices:has valuator "Rel Y" recognized? true
qt.qpa.input.devices:it's a scrolling device
qt.qpa.input.devices: input device  USB Optical Mouse ID 10
qt.qpa.input.devices:has 7 buttons
qt.qpa.input.devices:has valuator "Rel X" recognized? true
qt.qpa.input.devices:has valuator "Rel Y" recognized? true
qt.qpa.input.devices:has valuator "Rel Horiz Scroll" recognized? true
qt.qpa.input.devices:has valuator "Rel Vert Scroll" recognized? true
qt.qpa.input.devices:it's a scrolling device
qt.xcb.glintegration: Choosing xcb gl-integration based on following priority
 ("xcb_glx", "xcb_egl")
qt.xcb.glintegration: Xcb GLX gl-integration created
qt.xcb.glintegration: Xcb GLX gl-integration successfully initialized
kwin_platform_x11_standalone: Has XInput support 2 . 2
kwin_xkbcommon: XKB: created compose table from locale fr_FR.UTF-8 with path
/usr/share/X11/locale/en_US.UTF-8/Compose
kwin_xkbcommon: XKB: Compiling from RMLVO: rules 'evdev', model 'pc104', layout
'us', variant '(null)', options ''
kwin_xkbcommon: XKB: Compiling from KcCGST: keycodes 'evdev+aliases(qwerty)',
types 'complete', compat 'complete', symbols 'pc+us+inet(evdev)'
kwin_xkbcommon: XKB: Compiling xkb_keycodes "(unnamed)"
kwin_xkbcommon: XKB: Compiling xkb_types "(unnamed)"
kwin_xkbcommon: XKB: Compiling xkb_compatibility "(unnamed)"
kwin_xkbcommon: XKB: The "group" statement in compat is unsupported; Ignored
kwin_xkbcommon: XKB: The "group" statement in compat is unsupported; Ignored
kwin_xkbcommon: XKB: The "group" statement in compat is unsupported; Ignored
kwin_xkbcommon: XKB: The "allowExplicit" field in indicator statements is
unsupported; Ignored   
kwin_xkbcommon: XKB: The "allowExplicit" field in indicator statements is
unsupported; Ignored   
kwin_xkbcommon: XKB: The "allowExplicit" field in indicator statements is
unsupported; Ignored   
kwin_xkbcommon: XKB: The "allowExplicit" field in indicator statements is
unsupported; Ignored   
kwin_xkbcommon: XKB: The "indicatorDrivesKeyboard" field in indicator
statements is unsupported; Ignored 
kwin_xkbcommon: XKB: The "allowExplicit" field in indicator statements is
unsupported; Ignored   
kwin_xkbcommon: XKB: Indicator name "Shift Lock" was not declared in the
keycodes section; Adding new indicator  
kwin_xkbcommon: XKB: Indicator name "Group 2" was not declared in the keycodes
section; Adding new indicator 
kwin_xkbcommon: XKB: Indicator name "Mouse Keys" was not declared in the
keycodes section; Adding new indicator
kwin_xkbcommon: XKB: Compiling xkb_symbols "(unnamed)"

kwin_core: Extensions: shape: 0x "11"  composite: 0x "4"  render: 0x "b" 
fixes: 0x "50"  randr: 0x "14"  sync: 0x "31"  damage: 0x  "11"
kwin_decorations: Trying to load decoration plugin: 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kdecoration2/breezedecoration.so"
org.kde.kwindowsystem: Loaded plugin
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/org.kde.kwindowsystem.platforms/KF5WindowSystemX11Plugin.so"
for platform "xcb"
kwin_core: User timestamp, ASN: 314465
kwin_core: User timestamp, final: 'ID: 52428804 ;WMCLASS: "systemsettings" :
"systemsettings5" ;Caption: "Configuration du système" ' : 314465
kwin_core: User timestamp, ASN: 93001
kwin_core: User timestamp, final: 'ID: 44040196 ;WMCLASS: "kate" : "kate"
;Caption: "kwin_supportInformation.txt  — Kate" ' : 93001
kwin_core: User timestamp, ASN: 

[dolphin] [Bug 362899] dolphin crashed when I tried to delete file

2016-11-05 Thread S . Christian Collins
https://bugs.kde.org/show_bug.cgi?id=362899

S. Christian Collins  changed:

   What|Removed |Added

 CC||s_chriscoll...@hotmail.com

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

[krita] [Bug 352151] edit bundle creates a new bundle

2016-11-05 Thread David REVOY
https://bugs.kde.org/show_bug.cgi?id=352151

--- Comment #2 from David REVOY  ---
I'm testing again this bug on Git~master ( compiled today ).
The 'Edit' button was removed from the bundle resource manager and renamed to
'Create a new bundle from this bundle' but the feature is still broken.

To trigger bug:
===
Create a little bundle:
- Settings > Manage Resources, then 'Create New Bundle' button.
- 'Type' list , select Brush Preset , and add two random brush presets to the
'Selected' Column.
- Give a "Bundle Name"
- Press Save
Now we can select it, and try to "Create a new Bundle from this bundle"

Result:
===
- The dialog is empty, the "...from this bundle" in the button label "Create a
new Bundle from this bundle" doesn't work.

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

[kwin] [Bug 372083] Task Switcher visualization stuck on "Breeze"

2016-11-05 Thread anewuser
https://bugs.kde.org/show_bug.cgi?id=372083

--- Comment #3 from anewuser  ---
All switchers. It keeps using the default one.


I've found out that the compositor options is displaying this error message:
"OpenGL compositing (the default) has crashed KWin in the past. This was most
likely due to a driver bug. If you think that you have meanwhile upgraded to a
stable driver, you can reset this protection but be aware that this might
result in an immediate crash! Alternatively, you might want to use the XRender
backend instead."

The "Re-enable OpenGL detection" button makes kwin crash, and if I manually
change the rendering to XRender, it reverts back to OpenGL 2.0 too once I close
the window.

Some settings do work, like changing the system theme or resolution, so I don't
think this is an issue with permissions.

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

[kwin] [Bug 372083] Task Switcher visualization stuck on "Breeze"

2016-11-05 Thread anewuser
https://bugs.kde.org/show_bug.cgi?id=372083

--- Comment #2 from anewuser  ---
Created attachment 102054
  --> https://bugs.kde.org/attachment.cgi?id=102054=edit
qdbus org.kde.KWin /KWin supportInformation

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

[kgpg] [Bug 369609] shows only white and blue for trust levels

2016-11-05 Thread Rolf Eike Beer
https://bugs.kde.org/show_bug.cgi?id=369609

--- Comment #5 from Rolf Eike Beer  ---
So, is there actually an issue here?

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

[kgpg] [Bug 371410] kgpg crashes on startup and otherwise

2016-11-05 Thread Rolf Eike Beer
https://bugs.kde.org/show_bug.cgi?id=371410

--- Comment #1 from Rolf Eike Beer  ---
There has been a fix for something like this, can you check if this still
happens with the latest git version?

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

[kgpg] [Bug 372063] Unable to create a revocation certificate

2016-11-05 Thread Rolf Eike Beer
https://bugs.kde.org/show_bug.cgi?id=372063

Rolf Eike Beer  changed:

   What|Removed |Added

   Severity|critical|normal

--- Comment #1 from Rolf Eike Beer  ---
Please check if the revocation certificate is there, I've seen this were an
error was raised even if the certificate was created.

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

[plasmashell] [Bug 372112] New: No second row for header

2016-11-05 Thread Christoph
https://bugs.kde.org/show_bug.cgi?id=372112

Bug ID: 372112
   Summary: No second row for header
   Product: plasmashell
   Version: 5.8.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Notifications
  Assignee: k...@privat.broulik.de
  Reporter: christoph.schwi...@tu-ilmenau.de
CC: mklape...@kde.org
  Target Milestone: 1.0

Created attachment 102053
  --> https://bugs.kde.org/attachment.cgi?id=102053=edit
Uncomplete header of notification

It doesn't appear a second row for the header of a notification when the
message is too long for the widget size.

Steps to reproduce:
1.) Run "notify-send -t 0
testtesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttest123
test"
2.) You can't see the whole message. "123" of the string is lost.

Expected results:
Instead of "..." the whole information should appear

I know that a summary isn't often so long but some HTML5 notifications,
forwarded through Firefox' Gnotifier addon, contain long headers instead of a
short summary in the header and a long body... Would be great to read all
information.

Thanks!

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

[kde] [Bug 372054] KDE screen saver not working when VirtualBox guest is running.

2016-11-05 Thread Mark Foley
https://bugs.kde.org/show_bug.cgi?id=372054

--- Comment #2 from Mark Foley  ---
Christoph - sorry to hear that. KDE ships with a number of the major Linux
distros and is the default desktop for Slackware. Does that mean it's no longer
maintained by anyone? Is this bugs.kde.org site obsolete or now used for some
other purpose? If not maintained here, is it maintained anywhere that you know
of? I'm posting this question here because I don't know where would be more
appropriate.

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

[kolourpaint] [Bug 229086] Removes JPEG comments when saving jpeg images.

2016-11-05 Thread Martin Koller
https://bugs.kde.org/show_bug.cgi?id=229086

--- Comment #6 from Martin Koller  ---
You're right, it's no perfect solution.
I just described an "improved" behaviour of the underlying Qt library which
kolourpaint uses to read/write image files. There was no change in kolourpaint
itself in this regard.
Note that kolourpaint does not do the read/write of the image data on its own -
it uses the Qt library, which is not perfect in this regard and that is the
reason why the current situation is suboptimal.
I started to see if I could improve the situation for jpeg files to use a
second library, but I have no perfectly working solution right now, sorry.

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

[krita] [Bug 371124] Frequent crash without apparent common cause, I have the reports from drmingw

2016-11-05 Thread María
https://bugs.kde.org/show_bug.cgi?id=371124

--- Comment #34 from María  ---
The difference between 3.0.91 and 3.0.92 is that in 3.0.92 does not appear the
small window "saving document". When there is text in the document and I click
on the save button, the cursor remains spinning and don't stop

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

[plasmashell] [Bug 368160] Panel autohides when context menu is shown

2016-11-05 Thread Christoph
https://bugs.kde.org/show_bug.cgi?id=368160

--- Comment #4 from Christoph  ---
Sonme applets still loose RequiresAttention when modified

Steps to Reproduce:
1. set your panel to auto-hide
2. run "notify-send -t 0 test" and close the message
3. panel will hide

Actual Results:  
Panel hides


Version 5.8.0

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

[plasmashell] [Bug 368160] Panel autohides when context menu is shown

2016-11-05 Thread Christoph
https://bugs.kde.org/show_bug.cgi?id=368160

Christoph  changed:

   What|Removed |Added

 Resolution|FIXED   |LATER

--- Comment #3 from Christoph  ---
Sonme applets still loose RequiresAttention when modified

Steps to Reproduce:
1. set your panel to auto-hide
2. run "notify-send -t 0 test" and close the message
3. panel will hide

Actual Results:  
Panel hides

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

[krita] [Bug 371124] Frequent crash without apparent common cause, I have the reports from drmingw

2016-11-05 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=371124

--- Comment #33 from Boudewijn Rempt  ---
But in 3.0.92, there shouldn't be any hang on saving: the code that can cause
that isn't there anymore, and I stress-tested it just now, and even though I
managed to confuse Krita into running two strokes at the same time, and thus
hanging, it could save.

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

[Breeze] [Bug 372111] New: New icon for Google Drive

2016-11-05 Thread Elvis Angelaccio
https://bugs.kde.org/show_bug.cgi?id=372111

Bug ID: 372111
   Summary: New icon for Google Drive
   Product: Breeze
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: elvis.angelac...@kde.org
CC: kain...@gmail.com
  Target Milestone: ---

Currently kio-gdrive is using 'im-google' as main icon (e.g. see
http://imgur.com/a/z6kAR). It would be nice to have the actual Google Drive
icon available in breeze.

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

[kwin] [Bug 371537] Temporary freeze when showing multiple tray notifications

2016-11-05 Thread Alex Dănilă
https://bugs.kde.org/show_bug.cgi?id=371537

Alex Dănilă  changed:

   What|Removed |Added

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

--- Comment #15 from Alex Dănilă  ---
I confirm this continues to happen. Only twice in some 8 hours, so it's
intruding a lot less. If there's a way to get some debug information, other
than ssh in the precise seconds this happens, I'll gladly do.

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

[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget

2016-11-05 Thread Benedikt Geißler
https://bugs.kde.org/show_bug.cgi?id=367541

--- Comment #12 from Benedikt Geißler  ---
Created attachment 102052
  --> https://bugs.kde.org/attachment.cgi?id=102052=edit
Very quick rise of memory and CPU usage

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

[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget

2016-11-05 Thread Benedikt Geißler
https://bugs.kde.org/show_bug.cgi?id=367541

Benedikt Geißler  changed:

   What|Removed |Added

 CC||bened...@g5r.eu

--- Comment #11 from Benedikt Geißler  ---
Same here.

openSUSE Tumbleweed, Plasma 5.8.2, Frameworks 5.27.0, Qt 5.7.0,
Kontact/KOrganizer 5.3.0.

I select some calendars in the PIM Events Plugin, click on "apply" and the CPU
load as well as the memory usage rise quickly. The whole screen freezes so that
I can not even switch to another terminal (Ctrl+Alt+F1) or stop the desktop
environment with Ctrl+Alt+Del or Ctrl+Alt+Backspace. After a certain time
plasmashell crashes (perhaps because of the OOM killer?) and when I restart
plasmashell (e.g. via krunner which still works) the settings in the PIM Events
Plugin are reset (i.e. no calendars are selected anymore).

In addition to that the font in the PIM Events Plugin tab is kind of blurred in
comparison to the other tabs…

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

[kolourpaint] [Bug 229086] Removes JPEG comments when saving jpeg images.

2016-11-05 Thread Goran Brannstrom
https://bugs.kde.org/show_bug.cgi?id=229086

--- Comment #5 from Goran Brannstrom  ---
Thanks for the update Mr Koller.

I don't wish to sound ungrateful, but I fail to see how this behaviour can be
considered an improvement? The comment should just be left as it is, neither
prefixed, suffixed or changed in any way from the original file. 

What if a database started to prefix the contents in its tables? That would be
disaster. 

In my version it is still just removed. So I can not confirm what you say here.

But is it really so hard for the developers to just let the comment be?
If I could program I would change it myself. But I cant. :-)

/Göran

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

[yakuake] [Bug 343061] Yakuake creates task list entry when being opened

2016-11-05 Thread Rex Dieter
https://bugs.kde.org/show_bug.cgi?id=343061

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@math.unl.edu

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

[krita] [Bug 371124] Frequent crash without apparent common cause, I have the reports from drmingw

2016-11-05 Thread María
https://bugs.kde.org/show_bug.cgi?id=371124

--- Comment #32 from María  ---
In 3.0.91 hang in savings seems more random, it does not depend on whether or
not  there is text

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

[konsole] [Bug 164540] Konsole fails to start a session

2016-11-05 Thread arrowdodger
https://bugs.kde.org/show_bug.cgi?id=164540

arrowdodger <6year...@gmail.com> changed:

   What|Removed |Added

 CC||6year...@gmail.com

--- Comment #18 from arrowdodger <6year...@gmail.com> ---
While Konsole indeed works now, the kpty tests are still failing:

Config: Using QtTest library 5.7.1, Qt 5.7.1 (x86_64-little_endian-lp64 shared
(dynamic) debug build; by Clang 3.8.0 (tags/RELEASE_380/final 262564))
PASS   : KPtyProcessTest::initTestCase()
QDEBUG : KPtyProcessTest::test_pty_basic() 0 bytes available, waiting
FAIL!  : KPtyProcessTest::test_pty_basic() 'p.pty()->waitForReadyRead(5000)'
returned FALSE. ()
   Loc: [/root/kderoot/download/git/kpty/autotests/kptyprocesstest.cpp(132)]
PASS   : KPtyProcessTest::test_pty_signals()
FAIL!  : KPtyProcessTest::test_ctty() Compared values are not the same
   Actual   (output) : ""
   Expected (QLatin1String("this is a test\r\n")): "this is a test\r\n"
   Loc: [/root/kderoot/download/git/kpty/autotests/kptyprocesstest.cpp(219)]
PASS   : KPtyProcessTest::test_shared_pty()
PASS   : KPtyProcessTest::test_suspend_pty()
PASS   : KPtyProcessTest::cleanupTestCase()
Totals: 5 passed, 2 failed, 0 skipped, 0 blacklisted, 2158ms

I dig this out up to KPtyDevicePrivate::_k_canRead() method. When
p.pty()->waitForReadyRead(5000) is called, this function return 0 in available
for ::ioctl(q->masterFd(), PTY_BYTES_AVAILABLE, (char *) ) call.
This, in turn, leads to readBytes = 0 and method returning false.

I haven't yet figured out what to do with this.

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

[yakuake] [Bug 343061] Yakuake creates task list entry when being opened

2016-11-05 Thread Benedikt Geißler
https://bugs.kde.org/show_bug.cgi?id=343061

Benedikt Geißler  changed:

   What|Removed |Added

 CC||bened...@g5r.eu

--- Comment #6 from Benedikt Geißler  ---
I also experience this issue on openSUSE Tumbleweed with Yakuake 3.0.2, Plasma
5.8.2, Frameworks 5.27.0 and Qt 5.7.0. It's the same symptom here as Antonio
Orefice has reported.

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

  1   2   >