[systemsettings] [Bug 363389] New: Plasma System Settings crash on Confirming Changes

[Aniket Bhattacharyea via KDE Bugzilla]

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

Bug ID: 363389
   Summary: Plasma System Settings crash on Confirming Changes
   Product: systemsettings
   Version: 5.6.2
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: aniketmail...@gmail.com

Application: systemsettings5 (5.6.2)
 (Compiled from sources)
Qt Version: 5.6.0
Frameworks Version: 5.21.0
Operating System: Linux 4.5.2-papiya-linux x86_64
Distribution: "Papiya GNU/Linux Beta"

-- Information about the crash:
- What I was doing when the application crashed:
Went to Desktop theme. Select "Breeze Dark" and pressed back. The confirmation
dialog appeared and crashed

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f22ad4ea840 (LWP 15154))]

Thread 6 (Thread 0x7f229bae8700 (LWP 15155)):
#0  0x7f22a7657c7d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f22a41f30b2 in _xcb_conn_wait (c=c@entry=0xd99ef0,
cond=cond@entry=0xd99f30, vector=vector@entry=0x0, count=count@entry=0x0) at
xcb_conn.c:459
#2  0x7f22a41f4c47 in xcb_wait_for_event (c=0xd99ef0) at xcb_in.c:693
#3  0x7f229d6173d9 in  () at /opt/qt5/lib/libQt5XcbQpa.so.5
#4  0x7f22a8258f79 in  () at /opt/qt5/lib/libQt5Core.so.5
#5  0x7f22a39b03e4 in start_thread (arg=0x7f229bae8700) at
pthread_create.c:333
#6  0x7f22a7660cfd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f2299017700 (LWP 15156)):
#0  0x7f22a7657c7d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f22a22f5974 in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f228c003020, timeout=, context=0x7f228c000990) at
gmain.c:4135
#2  0x7f22a22f5974 in g_main_context_iterate
(context=context@entry=0x7f228c000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3835
#3  0x7f22a22f5a7c in g_main_context_iteration (context=0x7f228c000990,
may_block=1) at gmain.c:3901
#4  0x7f22a846bdbb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /opt/qt5/lib/libQt5Core.so.5
#5  0x7f22a8417b8a in
QEventLoop::exec(QFlags) () at
/opt/qt5/lib/libQt5Core.so.5
#6  0x7f22a82543cc in QThread::exec() () at /opt/qt5/lib/libQt5Core.so.5
#7  0x7f22a907d035 in  () at /opt/qt5/lib/libQt5DBus.so.5
#8  0x7f22a8258f79 in  () at /opt/qt5/lib/libQt5Core.so.5
#9  0x7f22a39b03e4 in start_thread (arg=0x7f2299017700) at
pthread_create.c:333
#10 0x7f22a7660cfd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f2284d4e700 (LWP 15159)):
#0  0x7f22a39b5fff in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f22909c4603 in thread_function () at /usr/lib/dri/swrast_dri.so
#2  0x7f22909c4497 in impl_thrd_routine () at /usr/lib/dri/swrast_dri.so
#3  0x7f22a39b03e4 in start_thread (arg=0x7f2284d4e700) at
pthread_create.c:333
#4  0x7f22a7660cfd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f228454d700 (LWP 15160)):
#0  0x7f22a39b5fff in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f22909c4603 in thread_function () at /usr/lib/dri/swrast_dri.so
#2  0x7f22909c4497 in impl_thrd_routine () at /usr/lib/dri/swrast_dri.so
#3  0x7f22a39b03e4 in start_thread (arg=0x7f228454d700) at
pthread_create.c:333
#4  0x7f22a7660cfd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f22802ee700 (LWP 15162)):
#0  0x7f22a23389c9 in g_mutex_lock (mutex=mutex@entry=0x7f2278000990) at
gthread-posix.c:1338
#1  0x7f22a22f53fc in g_main_context_check
(context=context@entry=0x7f2278000990, max_priority=2147483647,
fds=fds@entry=0x7f227800af40, n_fds=n_fds@entry=1) at gmain.c:3683
#2  0x7f22a22f5918 in g_main_context_iterate
(context=context@entry=0x7f2278000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3837
#3  0x7f22a22f5a7c in g_main_context_iteration (context=0x7f2278000990,
may_block=1) at gmain.c:3901
#4  0x7f22a846bdbb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /opt/qt5/lib/libQt5Core.so.5
#5  0x7f22a8417b8a in
QEventLoop::exec(QFlags) () at
/opt/qt5/lib/libQt5Core.so.5
#6  0x7f22a82543cc in QThread::exec() () at /opt/qt5/lib/libQt5Core.so.5
#7  0x7f22a6a6aa05 in  () at /opt/qt5/lib/libQt5Qml.so.5
#8  0x7f22a8258f79 in  () at /opt/qt5/lib/libQt5Core.so.5
#9  0x7f22a39b03e4 in start_thread (arg=0x7f22802ee700) at
pthread_create.c:333
#10 0x7f22a7660cfd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 

[kio] [Bug 179289] Improve dolphin behaviour in situations when user "doesn't have enough permission".

[via KDE Bugzilla]

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

bluescreenaven...@gmail.com changed:

   What|Removed |Added

 CC||bluescreenaven...@gmail.com

--- Comment #22 from bluescreenaven...@gmail.com ---
Can this be moved to frameworks-kio, if this is still possible?

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

[konsole] [Bug 362644] reset does not clear the screen in konsole

[Kurt Hindenburg via KDE Bugzilla]

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

--- Comment #3 from Kurt Hindenburg  ---
Strange, I'm basically running the same as you.  I'll see what differences
there might be.

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

[krita] [Bug 360601] [INTEL] Canvas doesn't update but is not black either

[via KDE Bugzilla]

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

sinkuup...@gmail.com changed:

   What|Removed |Added

 CC||sinkuup...@gmail.com

--- Comment #8 from sinkuup...@gmail.com ---
https://www.kickstarter.com/projects/krita/krita-2016-lets-make-text-and-vector-art-awesome/posts/1582415
This problem still occurs with the latest x64 build on my Windows10 machine.

# krita-opengl.txt
Intel, Intel(R) HD Graphics 3000, 3.1.0 - Build 9.17.10.4229

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

[plasmashell] [Bug 348812] Crash in __strstr_sse2 after QSGRenderContext::initialize(QOpenGLContext*)

[Rex Dieter via KDE Bugzilla]

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

--- Comment #45 from Rex Dieter  ---
*** Bug 362742 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 362742] Crash on returning to locked separate session

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@math.unl.edu
 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #4 from Rex Dieter  ---


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

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

[plasmashell] [Bug 363388] New: Crash when minimising notifications popup

[Con Kolivas via KDE Bugzilla]

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

Bug ID: 363388
   Summary: Crash when minimising notifications popup
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: k...@kolivas.org
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.5.0-ck1 x86_64
Distribution: Ubuntu 16.04 LTS

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

I had clicked on the notifications icon in the system tray which was displaying
a network transfer. When I clicked on it to minimise the window the panel
crashed.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7fe4551f4900 (LWP 7434))]

Thread 17 (Thread 0x7fe43fb83700 (LWP 7435)):
#0  0x7fe44f904e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fe4539c9c62 in _xcb_conn_wait (__timeout=-1, __nfds=1,
__fds=0x7fe43fb82bc0) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  0x7fe4539c9c62 in _xcb_conn_wait (c=c@entry=0x21237c0,
cond=cond@entry=0x2123800, vector=vector@entry=0x0, count=count@entry=0x0) at
../../src/xcb_conn.c:459
#3  0x7fe4539cb8d7 in xcb_wait_for_event (c=0x21237c0) at
../../src/xcb_in.c:693
#4  0x7fe442303629 in QXcbEventReader::run() (this=0x2131920) at
qxcbconnection.cpp:1253
#5  0x7fe44fffa84e in QThreadPrivate::start(void*) (arg=0x2131920) at
thread/qthread_unix.cpp:331
#6  0x7fe44f0e76fa in start_thread (arg=0x7fe43fb83700) at
pthread_create.c:333
#7  0x7fe44f910b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 16 (Thread 0x7fe43cb25700 (LWP 7436)):
#0  0x7fe44f904e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fe44c69a31c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7fe430003070, timeout=, context=0x7fe439b0) at
/build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gmain.c:4135
#2  0x7fe44c69a31c in g_main_context_iterate
(context=context@entry=0x7fe439b0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gmain.c:3835
#3  0x7fe44c69a42c in g_main_context_iteration (context=0x7fe439b0,
may_block=may_block@entry=1) at
/build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gmain.c:3901
#4  0x7fe450231a9b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fe438e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7fe4501d8dea in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fe43cb24ca0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7fe44fff58a4 in QThread::exec() (this=) at
thread/qthread.cpp:503
#7  0x7fe45289d3c5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7fe44fffa84e in QThreadPrivate::start(void*) (arg=0x223f0e0) at
thread/qthread_unix.cpp:331
#9  0x7fe44f0e76fa in start_thread (arg=0x7fe43cb25700) at
pthread_create.c:333
#10 0x7fe44f910b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7fe42df86700 (LWP 7437)):
#0  0x7fe44f904e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fe44c69a31c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7fe428002e70, timeout=, context=0x7fe428000990) at
/build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gmain.c:4135
#2  0x7fe44c69a31c in g_main_context_iterate
(context=context@entry=0x7fe428000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gmain.c:3835
#3  0x7fe44c69a42c in g_main_context_iteration (context=0x7fe428000990,
may_block=may_block@entry=1) at
/build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gmain.c:3901
#4  0x7fe450231a9b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fe4280008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7fe4501d8dea in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fe42df85ca0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7fe44fff58a4 in QThread::exec() (this=) at
thread/qthread.cpp:503
#7  0x7fe45289d3c5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7fe44fffa84e in QThreadPrivate::start(void*) (arg=0x255e850) at
thread/qthread_unix.cpp:331
#9  0x7fe44f0e76fa in start_thread (arg=0x7fe42df86700) at
pthread_create.c:333
#10 0x7fe44f910b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7fe427dc9700 (LWP 7438)):
#0  0x7fe44c6dea49 in g_mutex_lock (mutex=mutex@entry=0x7fe42990) at

[plasmashell] [Bug 363035] Plasma crashed while switching back to mu user session

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@math.unl.edu
 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Rex Dieter  ---


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

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

[plasmashell] [Bug 348812] Crash in __strstr_sse2 after QSGRenderContext::initialize(QOpenGLContext*)

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

 CC||ale...@cuenca.me

--- Comment #44 from Rex Dieter  ---
*** Bug 363035 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 348812] Crash in __strstr_sse2 after QSGRenderContext::initialize(QOpenGLContext*)

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

 CC||fthiag...@gmail.com

--- Comment #43 from Rex Dieter  ---
*** Bug 363386 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 363386] Plasma crashs when install AMD drivers fglrx

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE
 CC||rdie...@math.unl.edu

--- Comment #1 from Rex Dieter  ---


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

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

[plasmashell] [Bug 363387] New: Desktop Configuration

[Bon Scott via KDE Bugzilla]

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

Bug ID: 363387
   Summary: Desktop Configuration
   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: philhower.sc...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

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

-- Information about the crash:
- What I was doing when the application crashed:I was going back and forth
between different styles of icons, backgrounds,colors,etc.. when it ceashed.

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 0x7f8f733bd7c0 (LWP 1877))]

Thread 15 (Thread 0x7f8f5cded700 (LWP 1878)):
#0  0x7f8f6c8c9bbd in poll () at /lib64/libc.so.6
#1  0x7f8f7181d422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f8f7181f00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f8f5ef3e3c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f8f6cfc432f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f8f6c0d30a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f8f6c8d1fed in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7f8f55fe3700 (LWP 1960)):
#0  0x7f8f6c8c9bbd in poll () at /lib64/libc.so.6
#1  0x7f8f68fa4e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f8f68fa4f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f8f6d1f6d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f8f6d19dd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f8f6cfbf61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f8f702d3e18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f8f6cfc432f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f8f6c0d30a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f8f6c8d1fed in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7f8f48dff700 (LWP 1972)):
#0  0x7f8f6c8c5c8d in read () at /lib64/libc.so.6
#1  0x7f8f68fe5b60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f8f68fa4999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f8f68fa4df8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f8f68fa4f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f8f6d1f6d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f8f6d19dd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f8f6cfbf61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f8f702d3e18 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7f8f6cfc432f in  () at /usr/lib64/libQt5Core.so.5
#10 0x7f8f6c0d30a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7f8f6c8d1fed in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7f8f43458700 (LWP 1976)):
#0  0x7f8f6c8c9bbd in poll () at /lib64/libc.so.6
#1  0x7f8f68fa4e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f8f68fa4f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f8f6d1f6d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f8f6d19dd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f8f6cfbf61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f8f702d3e18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f8f6cfc432f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f8f6c0d30a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f8f6c8d1fed in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7f8f41bda700 (LWP 1980)):
#0  0x7f8f6c0d703f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8f72aa286b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f8f72aa2899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f8f6c0d30a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f8f6c8d1fed in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7f8eba352700 (LWP 1990)):
#0  0x7f8f68fa2210 in  () at /usr/lib64/libglib-2.0.so.0
#1  0x7f8f68fa444b in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f8f68fa4d80 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f8f68fa4f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f8f6d1f6d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f8f6d19dd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f8f6cfbf61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f8f70e6f282 in  () at /usr/lib64/libQt5Quick.so.5

[krita] [Bug 363310] User inteface font size is too small

[via KDE Bugzilla]

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

--- Comment #3 from mug...@naver.com ---
Comment on attachment 99127
  --> https://bugs.kde.org/attachment.cgi?id=99127
I have added a screenshot that can compare two version

My screen resolution is 1366 X 768.
I don't know about display scaling.

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

[krita] [Bug 363310] User inteface font size is too small

[via KDE Bugzilla]

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

--- Comment #2 from mug...@naver.com ---
Created attachment 99127
  --> https://bugs.kde.org/attachment.cgi?id=99127=edit
I have added a screenshot that can compare two version

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

[kdenlive] [Bug 362902] Kdenlive crashes when adding volume effect from audio and preview it

[via KDE Bugzilla]

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

xin...@protonmail.ch changed:

   What|Removed |Added

 CC||bug...@landfill.bugzilla.or
   ||g

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

[kdenlive] [Bug 362902] Kdenlive crashes when adding volume effect from audio and preview it

[via KDE Bugzilla]

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

xin...@protonmail.ch changed:

   What|Removed |Added

 CC||xin...@protonmail.ch

--- Comment #1 from xin...@protonmail.ch ---
(In reply to quiwy from comment #0)
> After editing video and adding an volume effect kdenlive crashed.
> 
> Reproducible: Always
> 
> Steps to Reproduce:
> 1. Open Kdenlive
> 2. Add a clip or an audio clip
> 3. Put an effect on it from "audio" category
> 3. Play the preview, when cursor reach the clip with effet
> 
> Actual Results:  
> Kdenlives crashes
> 
> Expected Results:  
> Continue playing preview
> 
> [volume @ 0x7fff7bdd23e0] [Eval @ 0x7fffa891d380] Undefined constant or
> missing '(' in ''
> [volume @ 0x7fff7bdd23e0] Unable to parse option value ""
> [volume @ 0x7fff7bdd23e0] [Eval @ 0x7fffa891d380] Undefined constant or
> missing '(' in ''
> [volume @ 0x7fff7bdd23e0] Unable to parse option value ""
> [volume @ 0x7fff7bdd23e0] [Eval @ 0x7fffa891d380] Undefined constant or
> missing '(' in ''
> [volume @ 0x7fff7bdd23e0] Unable to parse option value ""
> [filt @ 0x7fff3a6cf180] [Eval @ 0x7fffa891d9b0] Undefined constant or
> missing '(' in ''1.0''
> [filt @ 0x7fff3a6cf180] Error when evaluating the volume expression ''1.0''
> [filter avfilter.volume] Cannot init filter
> 
> Thread 32 "RenderThread" received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fffa891e700 (LWP 3327)]
> 0x7fffc97bc7bb in av_expr_eval () from /usr/lib/libavutil.so.55
> (gdb) thread apply all bt
> 
> Thread 55 (Thread 0x7fff0b7fe700 (LWP 3355)):
> #0  0x7fffee0fb09f in pthread_cond_wait@@GLIBC_2.3.2 () from
> /usr/lib/libpthread.so.0
> #1  0x7fffc8b12cfb in ?? () from /usr/lib/libavfilter.so.6
> #2  0x7fffee0f5474 in start_thread () from /usr/lib/libpthread.so.0
> #3  0x7fffef946acd in clone () from /usr/lib/libc.so.6
> 
> Thread 54 (Thread 0x7fff0bfff700 (LWP 3354)):
> #0  0x7fffee0fb09f in pthread_cond_wait@@GLIBC_2.3.2 () from
> /usr/lib/libpthread.so.0
> #1  0x7fffc8b12cfb in ?? () from /usr/lib/libavfilter.so.6
> #2  0x7fffee0f5474 in start_thread () from /usr/lib/libpthread.so.0
> #3  0x7fffef946acd in clone () from /usr/lib/libc.so.6
> 
> Thread 53 (Thread 0x7fff28ff8700 (LWP 3353)):
> #0  0x7fffee0fb09f in pthread_cond_wait@@GLIBC_2.3.2 () from
> /usr/lib/libpthread.so.0
> #1  0x7fffc8b12cfb in ?? () from /usr/lib/libavfilter.so.6
> #2  0x7fffee0f5474 in start_thread () from /usr/lib/libpthread.so.0
> #3  0x7fffef946acd in clone () from /usr/lib/libc.so.6
> 
> Thread 52 (Thread 0x7fff297f9700 (LWP 3352)):
> #0  0x7fffee0fb09f in pthread_cond_wait@@GLIBC_2.3.2 () from
> /usr/lib/libpthread.so.0
> #1  0x7fffc8b12cfb in ?? () from /usr/lib/libavfilter.so.6
> #2  0x7fffee0f5474 in start_thread () from /usr/lib/libpthread.so.0
> #3  0x7fffef946acd in clone () from /usr/lib/libc.so.6
> 
> Thread 51 (Thread 0x7fff29ffa700 (LWP 3351)):
> #0  0x7fffee0fb09f in pthread_cond_wait@@GLIBC_2.3.2 () from
> /usr/lib/libpthread.so.0
> #1  0x7fffc8b12cfb in ?? () from /usr/lib/libavfilter.so.6
> #2  0x7fffee0f5474 in start_thread () from /usr/lib/libpthread.so.0
> #3  0x7fffef946acd in clone () from /usr/lib/libc.so.6
> 
> Thread 50 (Thread 0x7fff2a7fb700 (LWP 3350)):
> #0  0x7fffee0fb09f in pthread_cond_wait@@GLIBC_2.3.2 () from
> /usr/lib/libpthread.so.0
> #1  0x7fffca0ad4ae in ?? () from /usr/lib/libavcodec.so.57
> #2  0x7fffee0f5474 in start_thread () from /usr/lib/libpthread.so.0
> #3  0x7fffef946acd in clone () from /usr/lib/libc.so.6
> 
> Thread 49 (Thread 0x7fff2affc700 (LWP 3349)):
> #0  0x7fffee0fb09f in pthread_cond_wait@@GLIBC_2.3.2 () from
> /usr/lib/libpthread.so.0
> #1  0x7fffca0ad4ae in ?? () from /usr/lib/libavcodec.so.57
> #2  0x7fffee0f5474 in start_thread () from /usr/lib/libpthread.so.0
> #3  0x7fffef946acd in clone () from /usr/lib/libc.so.6
> 
> Thread 48 (Thread 0x7fff2b7fd700 (LWP 3348)):
> #0  0x7fffee0fb09f in pthread_cond_wait@@GLIBC_2.3.2 () from
> /usr/lib/libpthread.so.0
> #1  0x7fffca0ad4ae in ?? () from /usr/lib/libavcodec.so.57
> #2  0x7fffee0f5474 in start_thread () from /usr/lib/libpthread.so.0
> #3  0x7fffef946acd in clone () from /usr/lib/libc.so.6
> 
> Thread 47 (Thread 0x7fff2bffe700 (LWP 3347)):
> #0  0x7fffee0fb09f in pthread_cond_wait@@GLIBC_2.3.2 () from
> /usr/lib/libpthread.so.0
> #1  0x7fffca0ad4ae in ?? () from /usr/lib/libavcodec.so.57
> #2  0x7fffee0f5474 in start_thread () from /usr/lib/libpthread.so.0
> #3  0x7fffef946acd in clone () from /usr/lib/libc.so.6
> 
> Thread 46 (Thread 0x7fff64ff8700 (LWP 3346)):
> #0  0x7fffee0fb09f in pthread_cond_wait@@GLIBC_2.3.2 () from
> /usr/lib/libpthread.so.0
> #1  0x7fffca0ad4ae in ?? () from /usr/lib/libavcodec.so.57
> #2  0x7fffee0f5474 in start_thread 

[plasmashell] [Bug 363386] New: Plasma crashs when install AMD drivers fglrx

[via KDE Bugzilla]

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

Bug ID: 363386
   Summary: Plasma crashs when install AMD drivers fglrx
   Product: plasmashell
   Version: 5.5.5
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: fthiag...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.1.20-11-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

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

I installed amd driver fglrx. After reboot, as recommended, the plasma
crashing.

- Unusual behavior I noticed:

Plasma does not start with AMD drivers fglrx. Was necessary remove fglrx for it
back to work.

The crash can be reproduced every time.

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

Thread 8 (Thread 0x7f8b5d274700 (LWP 2019)):
#0  0x7f8b6b812bbd in poll () from /lib64/libc.so.6
#1  0x7f8b70766422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f8b7076800f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f8b5f9f73c9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f8b6bf0d32f in QThreadPrivate::start (arg=0x25dea70) at
thread/qthread_unix.cpp:331
#5  0x7f8b6b01c0a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7f8b6b81afed in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7f8b54139700 (LWP 2026)):
#0  0x7f8b6b812bbd in poll () from /lib64/libc.so.6
#1  0x7f8b67eede64 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f8b67eedf7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f8b6c13fd8b in QEventDispatcherGlib::processEvents
(this=0x7f8b4c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f8b6c0e6d53 in QEventLoop::exec (this=this@entry=0x7f8b54138df0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f8b6bf0861a in QThread::exec (this=this@entry=0x27de760) at
thread/qthread.cpp:503
#6  0x7f8b6f21ce18 in QQmlThreadPrivate::run (this=0x27de760) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#7  0x7f8b6bf0d32f in QThreadPrivate::start (arg=0x27de760) at
thread/qthread_unix.cpp:331
#8  0x7f8b6b01c0a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7f8b6b81afed in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f8b48520700 (LWP 2027)):
#0  0x7f8b6b80ec8d in read () from /lib64/libc.so.6
#1  0x7f8b67f2eb60 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f8b67eed999 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f8b67eeddf8 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f8b67eedf7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f8b6c13fd8b in QEventDispatcherGlib::processEvents
(this=0x7f8b48c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#6  0x7f8b6c0e6d53 in QEventLoop::exec (this=this@entry=0x7f8b4851fdf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7f8b6bf0861a in QThread::exec (this=this@entry=0x292dca0) at
thread/qthread.cpp:503
#8  0x7f8b6f21ce18 in QQmlThreadPrivate::run (this=0x292dca0) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#9  0x7f8b6bf0d32f in QThreadPrivate::start (arg=0x292dca0) at
thread/qthread_unix.cpp:331
#10 0x7f8b6b01c0a4 in start_thread () from /lib64/libpthread.so.0
#11 0x7f8b6b81afed in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f8b46d14700 (LWP 2028)):
#0  0x7f8b67f2fcf9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f8b67eed4b9 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f8b67eedd80 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f8b67eedf7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f8b6c13fd8b in QEventDispatcherGlib::processEvents
(this=0x7f8b380008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f8b6c0e6d53 in QEventLoop::exec (this=this@entry=0x7f8b46d13df0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f8b6bf0861a in QThread::exec (this=this@entry=0x29aa6d0) at
thread/qthread.cpp:503
#7  0x7f8b6f21ce18 in QQmlThreadPrivate::run (this=0x29aa6d0) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#8  0x7f8b6bf0d32f in QThreadPrivate::start (arg=0x29aa6d0) at
thread/qthread_unix.cpp:331
#9  0x7f8b6b01c0a4 in start_thread () from /lib64/libpthread.so.0
#10 0x7f8b6b81afed in clone () from /lib64/libc.so.6

Thread 

[krita] [Bug 363257] Color-picker tool (Ctrl+click) not available after selecting a layer

[Scott Petrovic via KDE Bugzilla]

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

Scott Petrovic  changed:

   What|Removed |Added

 CC||scottpetro...@gmail.com
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Scott Petrovic  ---
I can confirm that there is something going on with changing layers an how it
affects the canvas cursor.

It seems like the bug has to do something with changing layers and a delay that
is created with that. You don't need a bigger document for this to happen. It
can just be a small one.

Just create a new document and a new layer. Switch layers and try to hold a key
like Control. You will see the cursor doesn't update for about a second or two.

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

[krita] [Bug 363096] Free transform after a perspective transform

[Scott Petrovic via KDE Bugzilla]

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

Scott Petrovic  changed:

   What|Removed |Added

 CC||scottpetro...@gmail.com

--- Comment #1 from Scott Petrovic  ---
I am testing this on the the Krita RC1 and cannot get this problem on my
Windows 10 machine. Is it still happening for you?

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

[krita] [Bug 362942] For 3.0, it's possible to try and generate a canvas from an empty clipboard.

[Scott Petrovic via KDE Bugzilla]

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

Scott Petrovic  changed:

   What|Removed |Added

 CC||scottpetro...@gmail.com

--- Comment #2 from Scott Petrovic  ---
I tried to create a new image from the clipboard and couldn't get it to crash.
I tried it from Edit > Paste into new image.  I also tried it from the File >
new dialog.

Is it still acting this way when you try it now Wolthera?

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

[kmymoney4] [Bug 351874] QIF import of investment buys and sells mishandles commissions

[Jeff via KDE Bugzilla]

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

--- Comment #15 from Jeff  ---
With my testing, the combination described in comment #14 seems to work.

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

[krita] [Bug 340948] Crash when undoing a 16 bits float to 8 bits color space conversion

[Scott Petrovic via KDE Bugzilla]

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

Scott Petrovic  changed:

   What|Removed |Added

 CC||scottpetro...@gmail.com

--- Comment #7 from Scott Petrovic  ---
I am on the RC1 on Windows 10 that was released on 5/21/16. 

I tried doing a few tests to undo color space changes. I couldn't get any
crashes happening. I tried a few different configurations of converting and
undoing, but couldn't get any crashes. It might be linux specific though.

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

[KScreen] [Bug 360430] kscreen randomly rewrites screen configuration

[Jimmy Berry via KDE Bugzilla]

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

Jimmy Berry  changed:

   What|Removed |Added

 CC||ji...@boombatower.com

--- Comment #6 from Jimmy Berry  ---
Not sure if related although it seems likely, but my 3 screen config seems to
be lost each login (since qt 5.6) and is a joke to setup again with kscreen5.
Video demonstration: https://www.youtube.com/watch?v=GWC_SrE9cco.

Let me know if I should file separate bug.

My 3 screens are correct at login manager, but on login the left and right
(identical screens) are cloned and center screen is disabled.

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

[kmail2] [Bug 363085] kmail window fails to display/load on second start

[Ryein Goddard via KDE Bugzilla]

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

--- Comment #12 from Ryein Goddard  ---
The only other option is to do it asynchronously if that is what you mean.  I
think it is discouraged because it is a blocking operation.  This wouldn't only
be a problem if the gui was still active, but it isn't.  Either the operation
thread is broken off, or the operation never completes.  I think the error
might be further down the line.

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

[krita] [Bug 363319] Auto-Update

[Scott Petrovic via KDE Bugzilla]

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

Scott Petrovic  changed:

   What|Removed |Added

 CC||scottpetro...@gmail.com

--- Comment #1 from Scott Petrovic  ---
Over IRC we discussed this a bit. It might be a good idea to make this an
opt-in to even check. Some people seemed a bit worried that Krita might be
spying on everyone if we do this.

Two ways we could do this is to just alert the person when there is a new
version available and give them a link. This would take a little time. The
second solution would be to auto-update kind of like how Google Chrome does it
without needing to manually go to the site. This would take longer to do.

The one negative potential for this background update is if we introduce a
build that would have bugs that would break things. We don't have much of a QA
team, so this could potentially give people problems. They could always opt-out
if they don't want to be on it.

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

[krita] [Bug 363295] Crash when creating document with OCIO config loaded

[Scott Petrovic via KDE Bugzilla]

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

--- Comment #4 from Scott Petrovic  ---
I grabbed the build that was just updated  with the 20,000 kickstarter post.

It is still doing the crash. It is not every time, so maybe there is some race
condition going on. If someone is trying to reproduce this, if the last step
doesn't produce a crash with the new document, try to close the document and
create another one. 

It coul take up to a few tries to experience it. It may also be Windows
specific.

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

[krita] [Bug 363385] New: Assistant tool doesn't turn invisible, calculates incorrectly.

[Lake via KDE Bugzilla]

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

Bug ID: 363385
   Summary: Assistant tool doesn't turn invisible, calculates
incorrectly.
   Product: krita
   Version: 3.0 Beta
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tools
  Assignee: krita-bugs-n...@kde.org
  Reporter: winter.w...@yahoo.com

I'm getting an issue where trying to turn off the visibility on my perspective
assistants is just making more new assistants. This doesn't happen all the
time, but very, very often, resulting in having to delete a swarm of new
assistants while trying to turn the one under it off - resulting in my
sometimes (accidently) deleting the original. This issue in turn spawns
another, where the perspective assistants stop calculating properly.

It took some playing around to figure out approximately what was going on, but
instead of speculating I will just give a list of what I did to reproduce it:

Reproducible: Always

Steps to Reproduce:
1. Make a new clear layer
2. Make five perspective points - left, right of canvas, then above and below,
and finally one beneath at the lower right hand corner.
3. Turn on assistant snapping and make some lines.
4. Turn off the visibility on the drawing layer we just used.
5. Go back to the assistant tool, make a new assistant and turn them all off.
6. Make a new layer and notice how the perspective lines are coming out all
wrong.

7. (optional) After this, I normally turn off the drawing layer and then delete
all but the first assistant I made, at which point the angle will come from the
wrong side (one of the deleted assistants?), but this step shouldn't be
necessary.



Using Windows 7, no OpenGL support.

On second note, I though that turning the visibility off on the assistants was
supposed to disable them for use later, but it doesn't seem to actually do
this. If this is not the case, is this a feature that will be added (it's handy
for things like drawing pictures in pictures, detail work, lettering, inking,
ext...)? 

Thank you for your work so far on the Krita project; I hope this report helps
you create your next stable release.

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

[dolphin] [Bug 360206] Dolphin crash while moving a file

[Matthieu Vergne via KDE Bugzilla]

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

Matthieu Vergne  changed:

   What|Removed |Added

 CC||matthieu.ver...@gmail.com

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

[print-manager] [Bug 363383] Unable to install printer driver on latest version of Kubunu 16.04

[Awan via KDE Bugzilla]

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

--- Comment #1 from Awan  ---
Installed latest version of Kubuntu 16.04 (after upgrade from 15.10 failed
half-way through and I could not log back in).

Have 64-bit Siemens Celsius PC  Epson WF-2660 printer.

Tried all the suggestions and websites here:

http://download.ebz.epson.net/dsc/search/01/search/?OSC=LX

http://download.ebz.epson.net/dsc/search/01/search/searchModule

https://wiki.linuxfoundation.org/en/OpenPrinting/Database/DriverPackages

sudo alien -ck 

sudo alien -ck epson-inkjet-printer-escpr-1.6.5-1lsb3.2.src.rpm

sudo alien -ck epson-inkjet-printer-escpr-1.6.5-1lsb3.2.x86_64.rpm

sudo rpm -Uvh epson-inkjet-printer-escpr-1.6.5-1lsb3.2.x86_64.rpm

sudo dpkg -i 

sudo dpkg -i epson-inkjet-printer-escpr_1.6.5-1lsb3.2_amd64.deb
sudo dpkg -i epson-inkjet-printer-escpr_1.6.5-1lsb3.2_amd64.deb

sudo dpkg -i  epson-inkjet-printer-escpr_1.6.5-1lsb3.2_amd64.deb


sudo dpkg -i  epson-inkjet-printer-escpr_1.6.5-1lsb3.2_i386.deb

sudo apt-get install lsb

https://wiki.linuxfoundation.org/en/OpenPrinting/Database/DriverPackages

deb http://www.openprinting.org/download/printdriver/debian/ lsb3.2 main
to your /etc/apt/sources.list file and run 

sudo apt-get update

How to edit /etc/apt/sources.list

http://askubuntu.com/questions/332669/unable-to-edit-etc-apt-sources-list-file

Use the terminal text editor program nano instead of gedit to edit
/etc/apt/sources.list. Open the terminal and type:

sudo nano /etc/apt/sources.list

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

[plasmashell] [Bug 355587] Manually control number of rows/columns in system tray

[Bob Wya via KDE Bugzilla]

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

Bob Wya  changed:

   What|Removed |Added

 CC||bob.mt@gmail.com

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

[konsole] [Bug 356286] Allow scrollback buffer to be greater than 100000 lines

[Kurt Hindenburg via KDE Bugzilla]

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

Kurt Hindenburg  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kons
   ||ole/44d4ed047c58cf636c3df31
   ||7551cacf1d6b99e48

--- Comment #1 from Kurt Hindenburg  ---
Git commit 44d4ed047c58cf636c3df317551cacf1d6b99e48 by Kurt Hindenburg.
Committed on 21/05/2016 at 22:32.
Pushed by hindenburg into branch 'master'.

Set maximum buffer scrollback to 1,000,000

Perhaps a note mentioning that this type of scrollback is held in
memory.  Regardless, allow up to 1 million lines.

M  +1-1src/HistorySizeWidget.ui

http://commits.kde.org/konsole/44d4ed047c58cf636c3df317551cacf1d6b99e48

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

[frameworks-baloo] [Bug 363384] New: Baloo file extractor process uses up nearly 100% of CPU

[Awan via KDE Bugzilla]

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

Bug ID: 363384
   Summary: Baloo file extractor process uses up nearly 100% of
CPU
   Product: frameworks-baloo
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Baloo File Daemon
  Assignee: m...@vhanda.in
  Reporter: nasima...@hotmail.com
CC: pinak.ah...@gmail.com

Installed KUbuntu 16.04 from scratch.

Editing the configuration file made no difference.

To resolve the problem had to move / rename Baloo file extractor.



Reproducible: Always

Steps to Reproduce:
1. Happened after copying over my backup files / directories to new
installation
2.
3.

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

[print-manager] [Bug 363383] New: Unable to install printer driver on latest version of Kubunu 16.04

[Awan via KDE Bugzilla]

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

Bug ID: 363383
   Summary: Unable to install printer driver on latest version of
Kubunu 16.04
   Product: print-manager
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dantt...@gmail.com
  Reporter: nasima...@hotmail.com

Get status failed message.

Reproducible: Always

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

[kwin] [Bug 363079] artifacts, mostly seen with firefox and eclipse

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #14 from Thomas Lübking  ---
Windows loose shadows and transparency (won't fade in), effects like "present
windows" or "desktop grid" don't work w/o compositing; such things.

UXA is the least efficient driver, SNA is much better. So you're still seeing
artifacts despite SNA and UXA (and ensured the intel driver isn't unloaded)?

Do you think you can make a screenshot or video of the issue?

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

[krita] [Bug 361061] Drawing assistant partially not working

[Lake via KDE Bugzilla]

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

Lake  changed:

   What|Removed |Added

 CC||winter.w...@yahoo.com

--- Comment #3 from Lake  ---
I do a lot of perspective work, but my tablet PC doesn't support OpenGL in
Krita, so I would love to see this fixed. The guide positions are calculated
correctly inside of the brush outline (cursor image), though it leaves a large
mess around the screen when the cursor is moved (as if a somewhat bigger brush
is painting the screen with little broken bits of perspective line). When
dragging the scroll bar, the guide lines are calculated correctly across the
screen, but they stop updating the moment you let go of the slider. This shows
that the lines *can* be drawn correctly without OpenGL, though I don't know how
much work it would be to actually fix it.

Thank you for your time and keep up the good work!

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

[kwin] [Bug 363079] artifacts, mostly seen with firefox and eclipse

[via KDE Bugzilla]

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

--- Comment #13 from je.joa...@yahoo.se ---
I don't see a visible difference when using SHIFT + ALT + F12, what should I
look for?

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

[kwin] [Bug 363079] artifacts, mostly seen with firefox and eclipse

[via KDE Bugzilla]

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

--- Comment #12 from je.joa...@yahoo.se ---
It could have been GLX as default in the beginning and I just remember it
wrong. :) 
It is OpenSuse Tumbleweed.

Think there is less artifacts yet using "uxa". But the touchpad is very
unsensitive instead, and scrolling in webpages is not so smooth as previously
and fans are spinning more often.

Maybe it is related to drivers?

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

[krita] [Bug 363153] Layer set to burn creates large grey artifacts; crashes

[Lake via KDE Bugzilla]

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

--- Comment #3 from Lake  ---
Created attachment 99126
  --> https://bugs.kde.org/attachment.cgi?id=99126=edit
The buggy file

Hello,

I installed the 3.0 beta and opened the file. It is still messed up, but on
playing with it, I noticed some interesting behavior:

Painting over the buggy area of the canvas (even on a different layer as long
as it is either the glitched layer or above it) is fine as long as you are
painting at 100% opacity - if it is anything less, the area will remain
untouched.

If you paint over the area with 100% opacity, you can then paint over it with
any opacity - but if you erase the area, the bug will return.

If the Layer is set to anything less than 100% opacity, the buggy area will
remain buggy (or become buggy) no matter what opacity the brush is set to. But
setting it to 100% will cause any 100% opaque to suddenly be recalculated
"correctly".

I also managed to paint over the buggy area with red and then erase over top of
it, removing all the paint *except* the paint in the bugged area. I was able to
do this repeatedly, but it was a few hours ago and I have since re-booted Krita
and forgot how I managed to do it.

I have attached a copy of the file, so you may play around with it, if you
would like.

Good luck!

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

[plasmashell] [Bug 363382] New: Plasma crashed when searching in Klauncher

[via KDE Bugzilla]

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

Bug ID: 363382
   Summary: Plasma crashed when searching in Klauncher
   Product: plasmashell
   Version: 5.5.5
  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.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-22-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I was typing a search in the search field of the KLauncher when Plasma crashed.
Screen went black for a while before wallpaper and widgets came back.

-- 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 0x7fdd7c12e8c0 (LWP 1729))]

Thread 16 (Thread 0x7fdd6744b700 (LWP 1742)):
#0  0x7fdd76840e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fdd7a905c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fdd7a9078d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fdd69599629 in QXcbEventReader::run (this=0x1a4a810) at
qxcbconnection.cpp:1253
#4  0x7fdd76f3684e in QThreadPrivate::start (arg=0x1a4a810) at
thread/qthread_unix.cpp:331
#5  0x7fdd760236fa in start_thread (arg=0x7fdd6744b700) at
pthread_create.c:333
#6  0x7fdd7684cb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7fdd64be4700 (LWP 1777)):
#0  0x7fdd7683c9cd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fdd736196c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fdd735d5e04 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fdd735d62c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fdd735d642c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fdd7716da9b in QEventDispatcherGlib::processEvents
(this=0x7fdd580008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#6  0x7fdd77114dea in QEventLoop::exec (this=this@entry=0x7fdd64be3ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7fdd76f318a4 in QThread::exec (this=this@entry=0x1b17de0) at
thread/qthread.cpp:503
#8  0x7fdd797d93c5 in QQmlThreadPrivate::run (this=0x1b17de0) at
qml/ftw/qqmlthread.cpp:141
#9  0x7fdd76f3684e in QThreadPrivate::start (arg=0x1b17de0) at
thread/qthread_unix.cpp:331
#10 0x7fdd760236fa in start_thread (arg=0x7fdd64be4700) at
pthread_create.c:333
#11 0x7fdd7684cb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7fdd55352700 (LWP 1778)):
#0  0x7fdd76840e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fdd735d631c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fdd735d642c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fdd7716da9b in QEventDispatcherGlib::processEvents
(this=0x7fdd58c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fdd77114dea in QEventLoop::exec (this=this@entry=0x7fdd55351ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7fdd76f318a4 in QThread::exec (this=this@entry=0x1e46670) at
thread/qthread.cpp:503
#6  0x7fdd797d93c5 in QQmlThreadPrivate::run (this=0x1e46670) at
qml/ftw/qqmlthread.cpp:141
#7  0x7fdd76f3684e in QThreadPrivate::start (arg=0x1e46670) at
thread/qthread_unix.cpp:331
#8  0x7fdd760236fa in start_thread (arg=0x7fdd55352700) at
pthread_create.c:333
#9  0x7fdd7684cb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7fdd4f422700 (LWP 1800)):
#0  0x7fdd76840e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fdd735d631c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fdd735d642c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fdd7716da9b in QEventDispatcherGlib::processEvents
(this=0x7fdd480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fdd77114dea in QEventLoop::exec (this=this@entry=0x7fdd4f421ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7fdd76f318a4 in QThread::exec (this=this@entry=0x1f70bd0) at
thread/qthread.cpp:503
#6  0x7fdd797d93c5 in QQmlThreadPrivate::run (this=0x1f70bd0) at
qml/ftw/qqmlthread.cpp:141
#7  0x7fdd76f3684e in QThreadPrivate::start (arg=0x1f70bd0) at
thread/qthread_unix.cpp:331
#8  0x7fdd760236fa in start_thread (arg=0x7fdd4f422700) at
pthread_create.c:333
#9  0x7fdd7684cb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 

[dolphin] [Bug 356098] feauture request: move *.slave-socket files to tmp folder...

[via KDE Bugzilla]

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

--- Comment #10 from nsane...@gmail.com ---
I'm also using KDE Plasma: 5.6.4, Qt Version: 5.6.0, Frameworks Version: 5.22.0
but have noticed no change.

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

[kwin] [Bug 363079] artifacts, mostly seen with firefox and eclipse

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #11 from Thomas Lübking  ---
There're several reports about GLX clients not painting correctly when using
EGL compositing, I'd suggest to switch to GLX (and somehow doubt EGL would have
been the default? Distro deviation?)

Please check the behavior w/ the compositor suspended (SHIFT+Alt+F12, *SHIFT* -
the thing to type upcase chars ;-) to rule in or out the compositor.

According to the glxinfo, the GL installation is ok, but you explained the
xrender setting anyway.

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

[plasmashell] [Bug 363337] Recent docs/history shortcuts in kicker/kickoff fail when clicked with "Could not find any application or handler..." error

[David Faure via KDE Bugzilla]

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

--- Comment #4 from David Faure  ---
Try porting to KProtocolInfo::isKnownProtocol, which will return true for
mailto as soon as one mail client is installed.

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

[frameworks-kinit] [Bug 358813] kdeinit5 crash after logout

[David Faure via KDE Bugzilla]

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

--- Comment #10 from David Faure  ---
Can you confirm my hypothesis by doing echo $DISPLAY in an xterm?

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

[kwin] [Bug 363079] artifacts, mostly seen with firefox and eclipse

[via KDE Bugzilla]

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

--- Comment #10 from je.joa...@yahoo.se ---
XRender in compositor is because I must have left it in that setting while
trying different combinations. The default was set to OpenGL 3.1, EGL and
Automatic vsync. Have not found a combination that for sure do any visible
difference to the artifacts. Have set it back to OpenGL 3.1 now.

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

[kwin] [Bug 363079] artifacts, mostly seen with firefox and eclipse

[via KDE Bugzilla]

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

--- Comment #9 from je.joa...@yahoo.se ---
Created attachment 99125
  --> https://bugs.kde.org/attachment.cgi?id=99125=edit
glxinfo

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

[dolphin] [Bug 269367] There is no way to search in hidden folders now.

[via KDE Bugzilla]

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

--- Comment #16 from haoxian.z...@gmail.com ---
Sorry, it seems to be only partially fixed. I can search unhidden files in a
hidden folder if I'm currently in that folder. But if I'm in the unhidden
folder that one level higher than this hidden folder, I cannot find the file
then.

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

[kaffeine] [Bug 363381] New: Crash of Kaffeine with any MPEG file

[Andreas via KDE Bugzilla]

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

Bug ID: 363381
   Summary: Crash of Kaffeine with any MPEG file
   Product: kaffeine
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: christophpfis...@gmail.com
  Reporter: anvo...@iway.na

Application: kaffeine-xbu (1.2.2 1.2.6)
KDE Platform Version: 4.14.9
Qt Version: 4.8.6
Operating System: Linux 3.16.7-35-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:


The crash can be reproduced every time.

-- Backtrace:
Application: Kaffeine (kaffeine-xbu), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8ea2242780 (LWP 20407))]

Thread 9 (Thread 0x7f8e90e3e700 (LWP 20409)):
#0  0x7f8ea08953e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8ea1ac6701 in  () at /usr/lib64/libxine.so.2
#2  0x7f8ea08910a4 in start_thread () at /lib64/libpthread.so.0
#3  0x7f8e9f5fd00d in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f8e8a15c700 (LWP 20410)):
#0  0x7f8e9f5f4bdd in poll () at /lib64/libc.so.6
#1  0x7f8e8b458a41 in  () at /usr/lib64/libpulse.so.0
#2  0x7f8e8b44a2ec in pa_mainloop_poll () at /usr/lib64/libpulse.so.0
#3  0x7f8e8b44a95e in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0
#4  0x7f8e8b44aa10 in pa_mainloop_run () at /usr/lib64/libpulse.so.0
#5  0x7f8e8b4589f3 in  () at /usr/lib64/libpulse.so.0
#6  0x7f8e8b201808 in  () at /usr/lib64/pulseaudio/libpulsecommon-5.0.so
#7  0x7f8ea08910a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f8e9f5fd00d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f8e8595a700 (LWP 20411)):
#0  0x7f8ea089503f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8ea1ad8753 in  () at /usr/lib64/libxine.so.2
#2  0x7f8ea08910a4 in start_thread () at /lib64/libpthread.so.0
#3  0x7f8e9f5fd00d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f8e7e9b4700 (LWP 20412)):
#0  0x7f8ea08953e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8ea1ad221b in  () at /usr/lib64/libxine.so.2
#2  0x7f8ea1ad4a44 in  () at /usr/lib64/libxine.so.2
#3  0x7f8ea08910a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f8e9f5fd00d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f8e7ddca700 (LWP 20413)):
[KCrash Handler]
#5  0x7f8e76d1e6ab in init_postprocess () at
/usr/lib64/xine/plugins/2.5/xineplug_decode_ff.so
#6  0x7f8e76d1f223 in ff_handle_preview_buffer () at
/usr/lib64/xine/plugins/2.5/xineplug_decode_ff.so
#7  0x7f8e76d1ff7b in ff_decode_data () at
/usr/lib64/xine/plugins/2.5/xineplug_decode_ff.so
#8  0x7f8ea1ad0a87 in  () at /usr/lib64/libxine.so.2
#9  0x7f8ea08910a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f8e9f5fd00d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f8e7d3fc700 (LWP 20414)):
#0  0x7f8ea0895027 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8e8b459080 in pa_threaded_mainloop_wait () at
/usr/lib64/libpulse.so.0
#2  0x7f8e8b6759ed in  () at
/usr/lib64/xine/plugins/2.5/xineplug_ao_out_pulseaudio.so
#3  0x7f8ea1ad77ac in  () at /usr/lib64/libxine.so.2
#4  0x7f8ea1ad7a42 in  () at /usr/lib64/libxine.so.2
#5  0x7f8e768f52d0 in faad_open_output () at
/usr/lib64/xine/plugins/2.5/xineplug_decode_faad.so
#6  0x7f8e768f58bc in faad_decode_data () at
/usr/lib64/xine/plugins/2.5/xineplug_decode_faad.so
#7  0x7f8ea1ad1c8f in  () at /usr/lib64/libxine.so.2
#8  0x7f8ea08910a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f8e9f5fd00d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f8e7cbfb700 (LWP 20415)):
#0  0x7f8ea089503f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8ea1ada5fb in xine_event_wait () at /usr/lib64/libxine.so.2
#2  0x7f8ea1ada69e in  () at /usr/lib64/libxine.so.2
#3  0x7f8ea08910a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f8e9f5fd00d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f8e766b2700 (LWP 20416)):
#0  0x7f8ea089503f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8ea1aca363 in  () at /usr/lib64/libxine.so.2
#2  0x7f8e8db89dfd in  () at /usr/lib64/xine/plugins/2.5/xineplug_dmx_qt.so
#3  0x7f8ea1adf9e8 in  () at /usr/lib64/libxine.so.2
#4  0x7f8ea08910a4 in start_thread () at /lib64/libpthread.so.0
#5  0x7f8e9f5fd00d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f8ea2242780 (LWP 20407)):
#0  0x7f8ea08953e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8ea1ac2f4f in xine_play () at 

[kwin] [Bug 363079] artifacts, mostly seen with firefox and eclipse

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #8 from Thomas Lübking  ---
PS: if things fail badly afterwards and you're presented with a textshell, just
remove /etc/X11/xorg.conf.d/20-intel.conf again

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

[kwin] [Bug 363079] artifacts, mostly seen with firefox and eclipse

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #7 from Thomas Lübking  ---
The intel driver is unloaded (you're on the modesetting driver alongside
glamor) and you're on xrender compositing. (But I do not understand why, your
IGP seems supported by the intel driver version and it should™ take precedence
on autoconfiguration if available)

Can you please also attach the output of
   glxinfo > ~/glx.info

I assume you'll encounter the same problems with suspended compositor (so not a
kwin issue at all) and suspect a driver bug, triggered by firefox et al. (they
still operate on OpenGL) directly.

I's propose to try to enforce intel and disable glamor for a beginning.

add a file /etc/X11/xorg.conf.d/20-intel.conf (requires root permissions) with
the content:

Section "Device"
   Identifier  "Intel Graphics"
   Driver  "intel"
   Option  "AccelMethod"  "sna"
EndSection

respecitvely alter any present file itr.

If this doesn't help, try to even fallback to

Section "Device"
   Identifier  "Intel Graphics"
   Driver  "intel"
   Option  "AccelMethod"  "uxa"
EndSection

Then restart X11 (logging out and back in should be sufficient, in doubt reboot
;-)

Ensure that the intel driver doesn't get unloaded in /var/log/Xorg.0.log after
those changes.

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

[dolphin] [Bug 269367] There is no way to search in hidden folders now.

[via KDE Bugzilla]

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

--- Comment #15 from haoxian.z...@gmail.com ---
This bug seems to have been fixed in recent updates:
KDE Plasma: 5.6.4
Qt Version: 5.6.0
Frameworks Version: 5.22.0
Operating System: Linux 4.5.4-1-default x86_64
Distribution: "openSUSE Tumbleweed (20160520) (x86_64)"

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

[konsole] [Bug 358115] Konsole does not reflow text on the screen when the terminal window is resized

[Kurt Hindenburg via KDE Bugzilla]

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

Kurt Hindenburg  changed:

   What|Removed |Added

   Severity|normal  |wishlist

--- Comment #2 from Kurt Hindenburg  ---
This has been asked for years - not a high priority ATM - I would look at
patches

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

[konsole] [Bug 362644] reset does not clear the screen in konsole

[Rajinder Yadav via KDE Bugzilla]

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

--- Comment #2 from Rajinder Yadav  ---
I am using Kubuntu 16.04 LTS

$ which $SHELL
/bin/bash

$ uname -a
Linux flow 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 x86_64
x86_64 x86_64 GNU/Linux

Take a look, I type reset and then type random keys which you see on the top
row!
https://youtu.be/_wd2OxDI2TQ

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

[konsole] [Bug 357937] Cursor turns invisible when hovering tab

[Kurt Hindenburg via KDE Bugzilla]

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

--- Comment #4 from Kurt Hindenburg  ---
can't reproduce here - I'd like to know what triggers this

https://www.youtube.com/watch?v=3snx18IjnvA

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

[konsole] [Bug 358343] Konsole's tabbar completely obscures/hides mouse cursor

[Kurt Hindenburg via KDE Bugzilla]

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

Kurt Hindenburg  changed:

   What|Removed |Added

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

--- Comment #4 from Kurt Hindenburg  ---


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

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

[konsole] [Bug 357937] Cursor turns invisible when hovering tab

[Kurt Hindenburg via KDE Bugzilla]

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

Kurt Hindenburg  changed:

   What|Removed |Added

 CC||a687...@trbvn.com

--- Comment #3 from Kurt Hindenburg  ---
*** Bug 358343 has been marked as a duplicate of this bug. ***

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

[Phonon] [Bug 363355] volume settings for event sounds ignored

[David Rosca via KDE Bugzilla]

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

David Rosca  changed:

   What|Removed |Added

   Assignee|now...@gmail.com|sit...@kde.org
  Component|general |general
Product|plasma-pa   |Phonon
 CC||myr...@kde.org,
   ||romain.per...@gmail.com

--- Comment #5 from David Rosca  ---
Try switching to Gstreamer. In any case, this has nothing to do with plasma-pa.
Reassigning.

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

[kwin] [Bug 363079] artifacts, mostly seen with firefox and eclipse

[via KDE Bugzilla]

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

--- Comment #6 from je.joa...@yahoo.se ---
If tearing is a specific type of error, then this is more general, like quick
flickering distortions. Please update this as well if needed.

User activity in for example Firefox, like hitting ctrl+o, then cancel and
switching between tabs, surfing in on news sites increases the distortions and
it goes a bit crazy for a while. It calms down after ~10 +/- 5secs seconds into
the usual sporadic distortions which there can be minutes between.

Thanks for looking into this,
Regards

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

[konsole] [Bug 359662] Terminal Rows are miscalculated if Menu Bar is turned off

[Kurt Hindenburg via KDE Bugzilla]

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

Kurt Hindenburg  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #2 from Kurt Hindenburg  ---
Yes this has always been an issue - I thought there was another old report for
this.

The patch does appear to fix it.

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

[plasma-pa] [Bug 363355] volume settings for event sounds ignored

[illumilore via KDE Bugzilla]

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

--- Comment #4 from illumilore  ---
phonon-vlc

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

[plasma-pa] [Bug 363355] volume settings for event sounds ignored

[David Rosca via KDE Bugzilla]

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

--- Comment #3 from David Rosca  ---
It's either GStreamer or VLC, you can see it in System Settings -> Multimedia
-> Audio and Video -> Backend tab

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

[plasma-pa] [Bug 363355] volume settings for event sounds ignored

[illumilore via KDE Bugzilla]

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

--- Comment #2 from illumilore  ---
libphonon4, or whatevers default in opensuse

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

[frameworks-kinit] [Bug 358813] kdeinit5 crash after logout

[Alexander Miroshnichenko via KDE Bugzilla]

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

--- Comment #9 from Alexander Miroshnichenko  ---
(In reply to David Faure from comment #8)
> This says that you don't have the variable $DISPLAY set.
> Just to be sure -- is this on X11? You have X running, right?
X11. You are right.

> I have no idea why your setup doesn't set $DISPLAY, but that's definitely a
> setup bug.
I start Plasma session from sddm. I don't know why and how the variable
$DISPLAY does not exists at the starting session.

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

[kwin] [Bug 363079] artifacts, mostly seen with firefox and eclipse

[via KDE Bugzilla]

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

--- Comment #5 from je.joa...@yahoo.se ---
Created attachment 99124
  --> https://bugs.kde.org/attachment.cgi?id=99124=edit
xorg

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

[kwin] [Bug 363079] artifacts, mostly seen with firefox and eclipse

[via KDE Bugzilla]

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

--- Comment #4 from je.joa...@yahoo.se ---
Created attachment 99123
  --> https://bugs.kde.org/attachment.cgi?id=99123=edit
kwin support

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

[ksecretsservice] [Bug 313216] Release a working version of KSecretService

[Rex Dieter via KDE Bugzilla]

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

--- Comment #11 from Rex Dieter  ---
kwallet can use login credentials, if you have pam-kwallet installed/enabled

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

[dolphin] [Bug 356098] feauture request: move *.slave-socket files to tmp folder...

[André Verwijs via KDE Bugzilla]

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

--- Comment #9 from André Verwijs  ---
maybe

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

[kwin] [Bug 363079] artifacts, mostly seen with firefox and eclipse

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

Summary|screen tearing, mostly seen |artifacts, mostly seen with
   |with firefox and eclipse|firefox and eclipse

--- Comment #3 from Thomas Lübking  ---
> shift+alt+f12 closes all windows
No, that sounds more like you pressed CTRL+Alt+F12, CTRL+Alt+F jump to the
kernels virtual terminal x - X11 nowadays usually runs on VT1, so CTRL+Alt+F1
would bring you back.

The problem you describe is by no means "tearing", please run
   qdbus org.kde.KWin /KWin supportInformation > ~/kwin.support
and attach the resulting kwin.support file as well as /var/log/Xorg.0.log

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

[ksecretsservice] [Bug 313216] Release a working version of KSecretService

[Syiad via KDE Bugzilla]

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

Syiad  changed:

   What|Removed |Added

 CC||syiad.al-d...@web.de

--- Comment #10 from Syiad  ---
kwallet repeatedly asks for the password, e.g. when another program starts.
ksecretservice as replacement will hopefully use the login credentials. When
can we poor ordinary users have it? It would be great, if you could release a
working version and improve it later. User feedback should then help guide your
improvement efforts, once we have a chance to actually use it.

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

[dolphin] [Bug 356098] feauture request: move *.slave-socket files to tmp folder...

[via KDE Bugzilla]

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

haoxian.z...@gmail.com changed:

   What|Removed |Added

 CC||haoxian.z...@gmail.com

--- Comment #8 from haoxian.z...@gmail.com ---
This bug seems to have been fixed in recent updates:
KDE Plasma: 5.6.4
Qt Version: 5.6.0
Frameworks Version: 5.22.0
Operating System: Linux 4.5.4-1-default x86_64
Distribution: "openSUSE Tumbleweed (20160520) (x86_64)"

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

[krita] [Bug 363373] bezier curve selection tool in release v3.0

[cheteron via KDE Bugzilla]

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

--- Comment #2 from cheteron  ---
But in old version vectors was normal, and without problem with zooming

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

[kinfocenter] [Bug 347344] KInfoCenter crashes after click Energy Information

[via KDE Bugzilla]

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

--- Comment #31 from haoxian.z...@gmail.com ---
This bug seems to be fixed in recent updates:
KDE Plasma: 5.6.4
Qt Version: 5.6.0
Frameworks Version: 5.22.0
Operating System: Linux 4.5.4-1-default x86_64
Distribution: "openSUSE Tumbleweed (20160520) (x86_64)"

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

[kwin] [Bug 363079] screen tearing, mostly seen with firefox and eclipse

[via KDE Bugzilla]

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

--- Comment #2 from je.joa...@yahoo.se ---
Hi,

Sorry for late response. Best text example I can think of is: CRT monitor or TV
with an in-cable that got a slight intermittent loose connection. Then if the
cable is moved just a little it causes distortions in the image. Did run the
same laptop with win10 and didn't see the it.

It is not periodic, but it looks like it gets a little worse over time. It can
be seen when applications like firefox, eclipse and even "configure desktop
window" is open. Not seen when it is only the desktop background showing or
terminal. Once when new plasma/kernel packets were installed, something seem to
be reset and for a while it looked to be fixed, then gradually it started
again.

It should probably not be a blocker, please change to a suitable priority. It
is a bit troublesome but it doesn't block usage that much.

shit+alt+f12 closes all windows, graphics and, screen goes black with an
underscore in the upper left corner and computer becomes unresponsive. Reboot
is needed.

Regards

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

[krita] [Bug 363374] Save formats

[wolthera via KDE Bugzilla]

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

wolthera  changed:

   What|Removed |Added

 CC||griffinval...@gmail.com
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from wolthera  ---
People have been saying this here and there. Proly the save menu hating us and
treating windows like it's osx/linux, and windows just being windows about it.

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

[krita] [Bug 363373] bezier curve selection tool in release v3.0

[wolthera via KDE Bugzilla]

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

wolthera  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
 CC||griffinval...@gmail.com

--- Comment #1 from wolthera  ---
The manipulators are tied to document dpi, might get fixed once we overhaul
vectors.

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

[plasmashell] [Bug 363380] New: Plasma crashes randomlywhen clicking between different apps

[Slaughter via KDE Bugzilla]

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

Bug ID: 363380
   Summary: Plasma crashes randomlywhen clicking between different
apps
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: slaughterho...@hotmail.ca
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-22-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Closed a tab in a chrome browser. Went to task bar and right clicked and plasma
instantly crashed

-- 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 0x7fce6fb528c0 (LWP 22605))]

Thread 12 (Thread 0x7fce5ae74700 (LWP 22607)):
#0  0x7fce6a263e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fce6e328c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fce6e32a8d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fce5cfc2629 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7fce6a95984e in QThreadPrivate::start (arg=0xc078a0) at
thread/qthread_unix.cpp:331
#5  0x7fce69a466fa in start_thread (arg=0x7fce5ae74700) at
pthread_create.c:333
#6  0x7fce6a26fb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7fce53fff700 (LWP 22610)):
#0  0x7fce6703da64 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fce66ff8cda in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fce66ff92c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fce66ff942c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fce6ab90a9b in QEventDispatcherGlib::processEvents
(this=0x7fce4c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7fce6ab37dea in QEventLoop::exec (this=this@entry=0x7fce53ffece0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7fce6a9548a4 in QThread::exec (this=this@entry=0xce8770) at
thread/qthread.cpp:503
#7  0x7fce6d1fc3c5 in QQmlThreadPrivate::run (this=0xce8770) at
qml/ftw/qqmlthread.cpp:141
#8  0x7fce6a95984e in QThreadPrivate::start (arg=0xce8770) at
thread/qthread_unix.cpp:331
#9  0x7fce69a466fa in start_thread (arg=0x7fce53fff700) at
pthread_create.c:333
#10 0x7fce6a26fb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7fce4962c700 (LWP 22615)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fce51c08aa3 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#2  0x7fce51c08907 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#3  0x7fce69a466fa in start_thread (arg=0x7fce4962c700) at
pthread_create.c:333
#4  0x7fce6a26fb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7fce48e2b700 (LWP 22616)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fce51c08aa3 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#2  0x7fce51c08907 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#3  0x7fce69a466fa in start_thread (arg=0x7fce48e2b700) at
pthread_create.c:333
#4  0x7fce6a26fb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7fce4862a700 (LWP 22617)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fce51c08aa3 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#2  0x7fce51c08907 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#3  0x7fce69a466fa in start_thread (arg=0x7fce4862a700) at
pthread_create.c:333
#4  0x7fce6a26fb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7fce47e29700 (LWP 22618)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fce51c08aa3 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#2  0x7fce51c08907 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#3  0x7fce69a466fa in start_thread (arg=0x7fce47e29700) at
pthread_create.c:333
#4  0x7fce6a26fb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7fce43be8700 (LWP 22619)):
#0  0x7fce6a25f9cd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fce6703c6c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fce66ff8e04 in 

[krita] [Bug 358147] Crash when trying to open or create a file

[via KDE Bugzilla]

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

--- Comment #8 from winter.w...@yahoo.com ---
I spent a good few days trying to get version 3.0 working, talking to different
people who had Krita installed on their computer, installing and reinstalling
and finagling the files every which way I could think of... so, naturally, I
over looked the Open GL check box every single time I went into the preferences
looking for it (even though I could find it on the old version)! You'd think
that since it's at the very top of the "display" section, it would be easy to
notice, but apparently it's not. If you can't auto detect that OpenGL won't
work on the computer (I think I read somewhere that there were some
difficulties with that.), you may want to put some sort of big, shiny arrow
pointing at it and an explanation of why you would want to disable it for
people like me who can't find their... checkbox with both hands and wonder why
the program doesn't work. Or better yet, have a pop up box for windows 7 that
launches on boot up until the user has successfully opened/created 1 new image.

Thanks for the help! Now time to try and get the Windows Shell Extension  (
http://files.kde.org/krita/3/windows/kritashellex_1.1.0.1_setup.exe ) package
to work -  la la! I've wanted one for so long I had started researching how
to make one myself - but now I don't have to! Happy birthday, me!

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

[Touchpad-KCM] [Bug 362800] Touchpad setting "Disable taps and scrolling only" ignored

[Rajeesh K V via KDE Bugzilla]

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

--- Comment #3 from Rajeesh K V  ---
Okay, thanks for confirmation.
You could indeed switch to synaptics driver - simply uninstall
xorg-x11-drv-libinput and install xorg-x11-drv-synaptics and see if that helps.

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

[konsole] [Bug 363379] New: when using a dark on light background profile, foreground colors all need to be dark

[Adam Felson via KDE Bugzilla]

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

Bug ID: 363379
   Summary: when using a dark on light background profile,
foreground colors all need to be dark
   Product: konsole
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: font
  Assignee: konsole-de...@kde.org
  Reporter: adam.bugzi...@thefelsons.us

When a dark on light background profile is selected, too many of the "color N"
colors are also light.  Having, for example, bright pink characters on a yellow
background results in print that is nearly unreadable.  When a "reversed" (dark
on a light background) profile is selected, all the colors also need to be
reset to have approximately the same brightness (dark) as the default color
scheme.

Reproducible: Always

Steps to Reproduce:
1.  select a light on dark profile such as "black on light yellow"
2. use an application that uses color coding such as ls --color
3.

Actual Results:  
unreadable text

Expected Results:  
readable text

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

[kdenlive] [Bug 361978] git master - composite and other track buttons are missing from layout with default timeline track size - they show when the tracks are larger size

[Jesse via KDE Bugzilla]

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

--- Comment #12 from Jesse  ---
UPDATE: When I add a clip into the Project Bin, the icons appear in the
timeline tracks, even at the smaller scale. However, the icons themselves are
too big for the timeline track headers.

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

[Touchpad-KCM] [Bug 362800] Touchpad setting "Disable taps and scrolling only" ignored

[Mark via KDE Bugzilla]

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

--- Comment #2 from Mark  ---
Thank you for your response Rajeesh.  Here is the output you requested:

272 libinput Tapping Enabled
273 libinput Tapping Enabled Default
274 libinput Tapping Drag Lock Enabled
275 libinput Tapping Drag Lock Enabled Default

It seems I am in fact using libinput.  I suppose I can try and switch back to
using Synaptics as the driver to see if it works.  Let me know if there's
anything else you would like to provide.

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

[kdenlive] [Bug 360084] 15.13.0 git master - Audio is not synced with 4k UHD video during playback -- video plays faster (sample clip included)

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

Summary|15.13.0 git master - Audio  |15.13.0 git master - Audio
   |is not synced with video|is not synced with 4k UHD
   |during playback -- video|video during playback --
   |plays faster (sample clip   |video plays faster (sample
   |included)   |clip included)

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

[konqueror] [Bug 363378] New: css background shorthand parser error

[Andrea Iacovitti via KDE Bugzilla]

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

Bug ID: 363378
   Summary: css background shorthand parser error
   Product: konqueror
   Version: Git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: khtml parsing
  Assignee: konq-b...@kde.org
  Reporter: aiacovi...@libero.it

Example:{background: none left left red no-repeat;}
The declaration is invalid because it specifies two horizontal value for
background-position (left left) then should be discarded. 

Reproducible: Always

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

[Baloo] [Bug 363377] New: baloo_file segmentation fault since upgrade to Kubuntu 16.04

[Lisa Miller via KDE Bugzilla]

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

Bug ID: 363377
   Summary: baloo_file segmentation fault since upgrade to Kubuntu
16.04
   Product: Baloo
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: m...@vhanda.in
  Reporter: lizajane...@gmail.com
CC: pinak.ah...@gmail.com

Application: baloo_file (5.18.0)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-22-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed: this crash seems not to be
related to anything I am doing. I usually see it when I am on the Internet
using Firefox. It doesn't seem to be connected to any file saving or opening of
Plasma.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation
fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5d9c0ef8c0 (LWP 1809))]

Thread 2 (Thread 0x7f5c5103b700 (LWP 2196)):
#0  0x7f5d9a1fbe8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f5d973cc31c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f5d973cc42c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5d9ae31a9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f5d9add8dea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00420cd8 in Baloo::FileContentIndexer::run() ()
#6  0x7f5d9abf7343 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f5d9abfa84e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f5d9985e6fa in start_thread (arg=0x7f5c5103b700) at
pthread_create.c:333
#9  0x7f5d9a207b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f5d9c0ef8c0 (LWP 1809)):
[KCrash Handler]
#6  __memcpy_sse2_unaligned () at
../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:38
#7  0x7f5d9b2e48da in Baloo::PostingCodec::decode(QByteArray const&) ()
from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#8  0x7f5d9b2d0814 in Baloo::PostingDB::get(QByteArray const&) () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#9  0x7f5d9b2e13c6 in Baloo::WriteTransaction::commit() () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#10 0x7f5d9b2d9032 in Baloo::Transaction::commit() () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#11 0x0042a02b in Baloo::MetadataMover::moveFileMetadata(QString
const&, QString const&) ()
#12 0x7f5d9ae09e4f in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x0042aaba in KInotify::moved(QString const&, QString const&) ()
#14 0x0042cbff in KInotify::slotEvent(int) ()
#15 0x7f5d9ae09e4f in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7f5d9ae8951e in QSocketNotifier::activated(int,
QSocketNotifier::QPrivateSignal) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7f5d9ae1647b in QSocketNotifier::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x7f5d9addb60c in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x7f5d9ae31f45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7f5d973cc127 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7f5d973cc380 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7f5d973cc42c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7f5d9ae31a7f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x7f5d9add8dea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x7f5d9ade0e8c in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x0041698c in main ()

Possible duplicates by query: bug 363342, bug 356445.

Reported using DrKonqi

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

[kdenlive] [Bug 361978] git master - composite and other track buttons are missing from layout with default timeline track size - they show when the tracks are larger size

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

   Platform|Ubuntu Packages |Kubuntu Packages

--- Comment #11 from Jesse  ---
I just tested with Kubuntu 16.04 and KDE Frameworks 5.22 (I think) using the
kubunt-ppa/backports ppa. This issue is still present when with the small
tracks. Original track size from previous builds show the icons just fine.

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

[ksshaskpass] [Bug 356632] ksshaskpass showing password field while asking for username

[Carlos via KDE Bugzilla]

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

Carlos  changed:

   What|Removed |Added

 CC||csanchezredo...@gmail.com

--- Comment #2 from Carlos  ---
The same happens to me. I'm on plasma 5.6.3, on openSUSE Tumbleweed.

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

[kde-windows] [Bug 363369] QtWebKit removed in Qt 5.6 but emerge still attempts to build kdewebkit

[Jasem Mutlaq via KDE Bugzilla]

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

Jasem Mutlaq  changed:

   What|Removed |Added

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

--- Comment #1 from Jasem Mutlaq  ---
Ok, problem is that I was using stock Qt which has GenericDataLocation set to
standard directories and not the ones used by KDE emerge environment. 

You don't have the same problem if you emerge Qt since it is patched. Perhaps
kdesettings.ini should mention this blocker issue to the user.

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

[konsole] [Bug 362171] Patch review requested for implementation SGR 2/8/9/53 (dim/conceal/strikeout/overline)

[Antonio Russo via KDE Bugzilla]

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

--- Comment #3 from Antonio Russo  ---
The attachment should be a tar.gz with 7 patches. On my debian machine it
extracts with tar -xf .

I've been using a version of konsole with these patches applied for about a
month now, and haven't hit any bugs.

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

[kdevelop] [Bug 363376] New: KDevelop crashes on valgrind debug launch

[Aleksei via KDE Bugzilla]

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

Bug ID: 363376
   Summary: KDevelop crashes on valgrind debug launch
   Product: kdevelop
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: alexeyponomarenk...@gmail.com

Application: kdevelop (4.90.92)
 (Compiled from sources)
Qt Version: 5.6.0
Frameworks Version: 5.22.0
Operating System: Linux 4.5.3-gentoo x86_64
Distribution: "NAME=Gentoo"

-- Information about the crash:
- What I was doing when the application crashed:
I was launching valgrind debug session. Valgrind version is 3.11.0

The crash can be reproduced every time.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6243c93800 (LWP 8706))]

Thread 14 (Thread 0x7f6226774700 (LWP 8707)):
#0  0x7f6240e329dd in poll () from /lib64/libc.so.6
#1  0x7f623547fa72 in _xcb_conn_wait () from /usr/lib64/libxcb.so.1
#2  0x7f6235481667 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f62286cf169 in QXcbEventReader::run() () from
/usr/lib64/libQt5XcbQpa.so.5
#4  0x7f6241588dbb in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f623a4343fc in start_thread () from /lib64/libpthread.so.0
#6  0x7f6240e3b81d in clone () from /lib64/libc.so.6

Thread 13 (Thread 0x7f6225094700 (LWP 8708)):
#0  0x7f6239ac8c4c in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f6239a85d4a in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f6239a86200 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f6239a862ac in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f624176bf6b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7f624171e07a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f6241584a24 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7f6243d92335 in QDBusConnectionManager::run() () from
/usr/lib64/libQt5DBus.so.5
#8  0x7f6241588dbb in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#9  0x7f623a4343fc in start_thread () from /lib64/libpthread.so.0
#10 0x7f6240e3b81d in clone () from /lib64/libc.so.6

Thread 12 (Thread 0x7f621472c700 (LWP 8709)):
#0  0x7f623a439ebf in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f621f9ec8a3 in radeon_drm_cs_emit_ioctl () from
/usr/lib64/dri/r600_dri.so
#2  0x7f621f9ebff7 in impl_thrd_routine () from /usr/lib64/dri/r600_dri.so
#3  0x7f623a4343fc in start_thread () from /lib64/libpthread.so.0
#4  0x7f6240e3b81d in clone () from /lib64/libc.so.6

Thread 11 (Thread 0x7f6203ff4700 (LWP 8711)):
#0  0x7f623a43a268 in pthread_cond_timedwait () from /lib64/libpthread.so.0
#1  0x7f62415893d8 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib64/libQt5Core.so.5
#2  0x7f623ef3cf70 in KDevelop::DUChainPrivate::CleanupThread::run() ()
from /usr/lib64/libKDevPlatformLanguage.so.10
#3  0x7f6241588dbb in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#4  0x7f623a4343fc in start_thread () from /lib64/libpthread.so.0
#5  0x7f6240e3b81d in clone () from /lib64/libc.so.6

Thread 10 (Thread 0x7f6202034700 (LWP 8713)):
#0  0x7f6239ac8c31 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f6239a86182 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f6239a862ac in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f624176bf6b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f624171e07a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f6241584a24 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f6241588dbb in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#7  0x7f623a4343fc in start_thread () from /lib64/libpthread.so.0
#8  0x7f6240e3b81d in clone () from /lib64/libc.so.6

Thread 9 (Thread 0x7f6201833700 (LWP 8715)):
#0  0x7f623a43a268 in pthread_cond_timedwait () from /lib64/libpthread.so.0
#1  0x7f62415893d8 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib64/libQt5Core.so.5
#2  0x7f6241585ee2 in QThreadPoolThread::run() () from
/usr/lib64/libQt5Core.so.5
#3  0x7f6241588dbb in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#4  0x7f623a4343fc in start_thread () from /lib64/libpthread.so.0
#5  0x7f6240e3b81d in clone () from /lib64/libc.so.6

Thread 8 (Thread 0x7f61e30e4700 (LWP 8716)):
#0  0x7f6239a8518b in g_main_context_acquire () from

[kdenlive] [Bug 363372] git master: rename "Insert Clip Zone in Timeline (Overwrite)" to "Overwrite Clip Zone in Timeline"

[via KDE Bugzilla]

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

--- Comment #2 from wegwerf-1-...@gmx.de ---
Perfect! Thank you very much, Jean-Baptiste!

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

[kate] [Bug 363375] Spelling call causes drawing over status bar - incorrect words are not highlighted

[Piotr Mierzwinski via KDE Bugzilla]

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 CC||piotr.mierzwin...@gmail.com

--- Comment #1 from Piotr Mierzwinski  ---
Created attachment 99121
  --> https://bugs.kde.org/attachment.cgi?id=99121=edit
status bar after use Spelling option

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

[kate] [Bug 363375] New: Spelling call causes drawing over status bar - incorrect words are not highlighted

[Piotr Mierzwinski via KDE Bugzilla]

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

Bug ID: 363375
   Summary: Spelling call causes drawing over status bar -
incorrect words are not highlighted
   Product: kate
   Version: Git
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

I open kwrite or kate. I have selected default language.
I wrote couple incorrect words and called spelling.
Automatic Spell Checking is turned on and nothing is highlighted.
Calling...
1. Option: Tools -> Spelling -> Spelling... - nothing happened after first use
in case of next is showing dialog "Check spelling" with OK button and on status
bar is drawing message about unknown word overlapping existing information.
Please check attached screen.
2. Option: Tools -> Spelling -> Spelling (from cursor) - message about unknown
word is drawing on status bar overlapping existing information. Please check
attached screen.

Change of dictionary doesn't help at all.


Reproducible: Always

Steps to Reproduce:
1. run kate/kwrite
2. write something incorrect in editor
3. call any Spelling option

Actual Results:  
drawing error messages over statusbar

Expected Results:  
incorrect words should be highlighted and in moment of calling Spelling should
be appeared some helper dialog

KWrite/Kate ver. 16.04.1;  KFrameworks 5.22; Plasma 5.6.4

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

[krita] [Bug 360785] Fill layers not updating

[caetano via KDE Bugzilla]

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

--- Comment #6 from caetano  ---
Tried with Linux Mint Rosa (Krita 2.9.11) and it gets better, the strokes
update at about half of each LMB release and when it doesn't, I can update by
clicking twice on the eye. This doesn't happen with windows.
But still impossible to decently work with.

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

[konsole] [Bug 360732] OK / Cancel button actions when closing a tab are wrongly interchanged when clicked via keyboard

[Kurt Hindenburg via KDE Bugzilla]

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

Kurt Hindenburg  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Kurt Hindenburg  ---
This is strange, I notice on 2 of my systems the first time I do it.  But as
soon as I close that tab, I can't reproduce it.

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

[krita] [Bug 363374] Save formats

[cheteron via KDE Bugzilla]

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

--- Comment #1 from cheteron  ---
Created attachment 99120
  --> https://bugs.kde.org/attachment.cgi?id=99120=edit
tiff

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

[krita] [Bug 363374] New: Save formats

[cheteron via KDE Bugzilla]

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

Bug ID: 363374
   Summary: Save formats
   Product: krita
   Version: 3.0 Release Candidate
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: chete...@gmail.com

Created attachment 99119
  --> https://bugs.kde.org/attachment.cgi?id=99119=edit
formats

If use in krita .jpg format for save, by default krita save random in .jpE or
.jpEG, but only not .jpG.
Same problem with other formats .tif and .tiff. By default krita save in .tiFF,
not in .tiF.

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

[krita] [Bug 363373] New: bezier curve selection tool in release v3.0

[cheteron via KDE Bugzilla]

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

Bug ID: 363373
   Summary: bezier curve selection tool in release v3.0
   Product: krita
   Version: 3.0 Release Candidate
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: chete...@gmail.com

Created attachment 99118
  --> https://bugs.kde.org/attachment.cgi?id=99118=edit
bezier curve selection tool

bezier curve selection tool
when use this tool and zooming picture manipulators becoming very big (see
attach)

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

[konversation] [Bug 345574] Konversation segfault upon changing widget style

[Paulo Lieuthier via KDE Bugzilla]

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

Paulo Lieuthier  changed:

   What|Removed |Added

 CC||paulolieuth...@gmail.com

--- Comment #4 from Paulo Lieuthier  ---
*** Bug 351451 has been marked as a duplicate of this bug. ***

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

[konversation] [Bug 351451] Crash when changing Qt widget theme with at least one active channel

[Paulo Lieuthier via KDE Bugzilla]

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

Paulo Lieuthier  changed:

   What|Removed |Added

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

--- Comment #3 from Paulo Lieuthier  ---


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

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

[dolphin] [Bug 357479] crash if I close the splitscreen while focused on it and then change the view

[Emmanuel Pescosta via KDE Bugzilla]

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

--- Comment #34 from Emmanuel Pescosta  ---
(In reply to Martin Sandsmark from comment #32)
> Do you have any other plugins installed?

No I don't have any plugins installed that are KOverlayIconPlugin based.

Also the backtraces above don't mention anything related to KOverlayIconPlugin.
I think that killing the preview job triggers the crash, because the job emits
a signal although kill should not emit anything.

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

[kdenlive] [Bug 363372] git master: rename "Insert Clip Zone in Timeline (Overwrite)" to "Overwrite Clip Zone in Timeline"

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kden
   ||live/91b043103e88af3408f076
   ||81fee6ae080d1a62b9

--- Comment #1 from Jean-Baptiste Mardelle  ---
Git commit 91b043103e88af3408f07681fee6ae080d1a62b9 by Jean-Baptiste Mardelle.
Committed on 21/05/2016 at 16:54.
Pushed by mardelle into branch 'master'.

Rename insert actions

M  +2-2src/mainwindow.cpp

http://commits.kde.org/kdenlive/91b043103e88af3408f07681fee6ae080d1a62b9

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