[krita] [Bug 363779] Undo applies at beginning of stroke

[Jelena via KDE Bugzilla]

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

--- Comment #3 from Jelena  ---
Good news. I discovered that you can workaround this bug by disabling
Preferences - Display - OpenGL. This might have other side effects but at least
now we can draw again using Mac OS X.

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

[krita] [Bug 364173] Tablet proximity events zoom out image to the smallest size

[Jelena via KDE Bugzilla]

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

Jelena  changed:

   What|Removed |Added

 CC||jelen...@t-online.de

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

[palapeli] [Bug 366796] Ctrl-click should never, ever deselect all pieces

[Ian Wadham via KDE Bugzilla]

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

--- Comment #2 from Ian Wadham  ---
(In reply to Matthew Woehlke from comment #0)
> I'm not familiar enough with how palapeli is implemented, but it occurs to
> me the problem might be in the QGV frameworks? (In which case I'm happy to
> punt this to Qt...)

I have not checked the code, but I am pretty sure this behavior is nothing to
do
with Qt or QGraphicsView.

There are some other mouse operations I am not happy about in Palapeli, such
as the possibility of crashing Palapeli when dragging and joining pieces. 

Unfortunately I am not in a position to do any serious maintenance, due to my
advanced age and the fact that I am on an Apple computer and do not yet have
KF5.  I last worked on Palapeli about a year ago.

If you are interested in fixing Palapeli, I could help you find the pieces of
code
that need work and perhaps suggest some patches.

The position of maintainer is also vacant and porting to Frameworks is
incomplete.

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

[palapeli] [Bug 366796] Ctrl-click should never, ever deselect all pieces

[Ian Wadham via KDE Bugzilla]

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

Ian Wadham  changed:

   What|Removed |Added

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

--- Comment #1 from Ian Wadham  ---
(In reply to Matthew Woehlke from comment #0)
> It is very, very frustrating when I am trying to select a bunch of pieces by
> clicking on them individually while holding ctrl that palapeli drops my
> entire selection if the mouse is over the wrong pixel when I click.
> 
I agree, but perhaps not with a second "very"... :-)  Also the procedures for
deselecting a whole group of selected pieces or just one piece from such a
group should be clearer and more intuitive.

> Multi-select behavior should work like it does in every other application.
> Specifically:
> 
> - A ctrl-click on empty space DOES NOTHING. It absolutely, positively should
> not deselect every piece I've worked hard to select.
> - A ctrl-click-and-drag should ADD to the selection, not replace it.
> 
Is there a standard on this?  If so, Palapeli should follow it.

> (It would also help if there was a little fudge factor for clicking on
> pieces, but that probably deserves a separate report.)
> 
Agreed, but the little hand that appears is a reliable indicator, even
for pieces that are currently too small to see properly.

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

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

[via KDE Bugzilla]

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

gur...@gmail.com changed:

   What|Removed |Added

 CC||gur...@gmail.com

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

[QtCurve] [Bug 366802] Systemsettings crashes when reopening

[via KDE Bugzilla]

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

edisonalvari...@bol.com.br changed:

   What|Removed |Added

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

--- Comment #9 from edisonalvari...@bol.com.br ---
fixed ! the git version I was using was old sorry!

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

[QtCurve] [Bug 366802] Systemsettings crashes when reopening

[via KDE Bugzilla]

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

edisonalvari...@bol.com.br changed:

   What|Removed |Added

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

--- Comment #8 from edisonalvari...@bol.com.br ---
sorry reopening , reassigning to  Qtcurve.  I didn't knew qtcurve was still
supported.

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

[QtCurve] [Bug 366802] Systemsettings crashes when reopening

[via KDE Bugzilla]

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

edisonalvari...@bol.com.br changed:

   What|Removed |Added

 CC||h...@kde.org
  Component|general |qt5
Version|5.7.3   |git
Product|systemsettings  |QtCurve

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

[systemsettings] [Bug 366802] Systemsettings crashes when reopening

[via KDE Bugzilla]

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

edisonalvari...@bol.com.br changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
Summary|Systemsettings crashes when |Systemsettings crashes when
   |opening second instance |reopening

--- Comment #7 from edisonalvari...@bol.com.br ---
the problem is qtcurve style I installed from a unsupported repo. I'm closing
it.

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

[plasmashell] [Bug 366813] New: Plasma crashed while I was reading a page in Firefox

[Tom via KDE Bugzilla]

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

Bug ID: 366813
   Summary: Plasma crashed while I was reading a page in Firefox
   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: tsgue...@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.27-27-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:  
I was reading an article in a tab of Firefox.  The Firefox window was
maximized.  Pandora.com was playing music via adobe flash in a separate Firefox
window "behind" my primary Firefox window, which had about 12 tabs open.

- Unusual behavior I noticed:
The taskbar and other windows don't look "pretty" -- the borders are weird and
text is difficult to read.  (I usually use lightweight desktops like lxde).  I
assume the problem is mostly my very old video card and rather old
motherboard/CPU/maximum 2GB system RAM).
MB: MSI MS-7142 
CPU:  AMD 3400+
Video card: nVidia FX5200 using nouveau driver distributed with (or updated by)
openSUSE Leap 42.1

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

Thread 7 (Thread 0x7feb6a0a4700 (LWP 1766)):
#0  0x7feb79b72bfd in poll () at /lib64/libc.so.6
#1  0x7feb7eac6422 in  () at /usr/lib64/libxcb.so.1
#2  0x7feb7eac800f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7feb6c1f53c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7feb7a26d32f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7feb7937c0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7feb79b7b02d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7feb633ea700 (LWP 1922)):
#0  0x7ffe15dd99a2 in clock_gettime ()
#1  0x7feb79b87c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7feb7a31e7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7feb7a49e3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7feb7a49e945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7feb7a49fb5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7feb7624f4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7feb7624fd80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7feb7624ff7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7feb7a49fd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7feb7a446d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7feb7a26861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7feb7d57ce18 in  () at /usr/lib64/libQt5Qml.so.5
#13 0x7feb7a26d32f in  () at /usr/lib64/libQt5Core.so.5
#14 0x7feb7937c0a4 in start_thread () at /lib64/libpthread.so.0
#15 0x7feb79b7b02d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7feb4f4fa700 (LWP 1939)):
#0  0x7ffe15dd99a2 in clock_gettime ()
#1  0x7feb79b87c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7feb7a31e7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7feb7a49e3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7feb7a49e945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7feb7a49fb5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7feb7624f4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7feb7624fd80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7feb7624ff7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7feb7a49fd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7feb7a446d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7feb7a26861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7feb7d57ce18 in  () at /usr/lib64/libQt5Qml.so.5
#13 0x7feb7a26d32f in  () at /usr/lib64/libQt5Core.so.5
#14 0x7feb7937c0a4 in start_thread () at /lib64/libpthread.so.0
#15 0x7feb79b7b02d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7feb4e0e8700 (LWP 1940)):
#0  0x7feb7938003f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7feb7fd4b86b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7feb7fd4b899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7feb7937c0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7feb79b7b02d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7feb4cfd7700 (LWP 1941)):
#0  0x7feb79b72bfd in poll () at /lib64/libc.so.6
#1  0x7feb7624fe64 in  () at 

[systemsettings] [Bug 366802] Systemsettings crashes when opening second instance

[via KDE Bugzilla]

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

edisonalvari...@bol.com.br changed:

   What|Removed |Added

Summary|Systemsettings crash when   |Systemsettings crashes when
   |opening second instance |opening second instance

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

[konsole] [Bug 366793] Regression in Konsole's handling of command line parameters

[via KDE Bugzilla]

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

edisonalvari...@bol.com.br changed:

   What|Removed |Added

 CC||edisonalvari...@bol.com.br

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

[systemsettings] [Bug 366802] Systemsettings crash when opening second instance

[via KDE Bugzilla]

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

--- Comment #6 from edisonalvari...@bol.com.br ---
Application: systemsettings5 (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0ec621a780 (LWP 9689))]

Thread 2 (Thread 0x7f0eb34cc700 (LWP 9690)):
#0  0x7f0ec1f7649d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f0ebe8ea3c2 in poll (__timeout=-1, __nfds=1, __fds=0x7f0eb34cbd40)
at /usr/include/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0x1bf88e0, cond=cond@entry=0x1bf8920,
vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:479
#3  0x7f0ebe8ec10f in xcb_wait_for_event (c=0x1bf88e0) at xcb_in.c:693
#4  0x7f0eb5a57389 in QXcbEventReader::run (this=0x1c0ba00) at
qxcbconnection.cpp:1337
#5  0x7f0ec2675859 in QThreadPrivate::start (arg=0x1c0ba00) at
thread/qthread_unix.cpp:344
#6  0x7f0ebe05d734 in start_thread (arg=0x7f0eb34cc700) at
pthread_create.c:334
#7  0x7f0ec1f7ed3d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f0ec621a780 (LWP 9689)):
[KCrash Handler]
#6  compare_exchange_strong (__m2=std::memory_order_acquire,
__m1=std::memory_order_acquire, __p2=0x1, __p1=@0x7ffe8ec20cd0: 0x0,
this=) at /usr/include/c++/4.8/bits/atomic_base.h:844
#7  compare_exchange_strong (__p2=0x1, __m=std::memory_order_acquire,
__p1=@0x7ffe8ec20cd0: 0x0, this=) at
/usr/include/c++/4.8/atomic:445
#8  testAndSetAcquire (currentValue=,
newValue=0x1, expectedValue=0x0, _q_value=...) at
../../src/corelib/arch/qatomic_cxx11.h:165
#9  testAndSetAcquire (currentValue=, newValue=0x1,
expectedValue=0x0, this=this@entry=0x20) at
../../src/corelib/thread/qbasicatomic.h:259
#10 fastTryLock (current=, this=this@entry=0x20) at
thread/qmutex.h:89
#11 QMutex::lock (this=this@entry=0x20) at thread/qmutex.cpp:225
#12 0x7f0ec318c9ff in QMutexLocker (m=0x20, this=) at
../../src/corelib/thread/qmutex.h:137
#13 QDBusConnectionManager::busConnection (this=0x0,
type=type@entry=QDBusConnection::SessionBus) at qdbusconnection.cpp:127
#14 0x7f0ec318d95a in QDBusConnection::sessionBus () at
qdbusconnection.cpp:1195
#15 0x7f0eae12963d in QtCurve::Style::disconnectDBus (this=0x1c7e6c0) at
/usr/src/debug/qtcurve-1.8.40git/qt5/style/qtcurve.cpp:694
#16 0x7f0eae163ae6 in runAllCleanups () at
/usr/src/debug/qtcurve-1.8.40git/qt5/style/qtcurve_plugin.cpp:86
#17 QtCurve::StylePlugin::~StylePlugin (this=0x1c49450, __in_chrg=) at /usr/src/debug/qtcurve-1.8.40git/qt5/style/qtcurve_plugin.cpp:167
#18 0x7f0eae163b19 in QtCurve::StylePlugin::~StylePlugin (this=0x1c49450,
__in_chrg=) at
/usr/src/debug/qtcurve-1.8.40git/qt5/style/qtcurve_plugin.cpp:170
#19 0x7f0ec28213f1 in QLibraryPrivate::unload (this=this@entry=0x1c4d2b0,
flag=flag@entry=QLibraryPrivate::UnloadSys) at plugin/qlibrary.cpp:557
#20 0x7f0ec281a6e3 in QFactoryLoaderPrivate::~QFactoryLoaderPrivate
(this=0x1c4b660, __in_chrg=) at plugin/qfactoryloader.cpp:86
#21 0x7f0ec281a859 in QFactoryLoaderPrivate::~QFactoryLoaderPrivate
(this=0x1c4b660, __in_chrg=) at plugin/qfactoryloader.cpp:89
#22 0x7f0ec285ca66 in cleanup (pointer=) at
../../src/corelib/tools/qscopedpointer.h:60
#23 ~QScopedPointer (this=0x7f0ec4a597d8 <(anonymous
namespace)::Q_QGS_loader::innerFunction()::holder+8>, __in_chrg=) at ../../src/corelib/tools/qscopedpointer.h:107
#24 QObject::~QObject (this=, __in_chrg=) at
kernel/qobject.cpp:900
#25 0x7f0ec2819d52 in QFactoryLoader::~QFactoryLoader (this=0x7f0ec4a597d0
<(anonymous namespace)::Q_QGS_loader::innerFunction()::holder>,
__in_chrg=) at plugin/qfactoryloader.cpp:205
#26 0x7f0ec43d9db9 in (anonymous namespace)::Q_QGS_loader::Holder::~Holder
(this=, __in_chrg=) at
styles/qstylefactory.cpp:72
#27 0x7f0ec43d9db9 in operator() (this=) from
/usr/lib64/libQt5Widgets.so.5
#28 (anonymous namespace)::Q_QGS_loader::innerFunction()::Holder::~Holder() ()
at styles/qstylefactory.cpp:158
#29 0x7f0ec1ecc139 in __run_exit_handlers (status=0, listp=0x7f0ec22325a0
<__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#30 0x7f0ec1ecc185 in __GI_exit (status=) at exit.c:104
#31 0x7f0ec34067f8 in KDBusService::KDBusService (this=,
options=..., parent=) at
/usr/src/debug/kdbusaddons-5.25.0/src/kdbusservice.cpp:129
#32 0x0040cca0 in SystemSettingsApp::SystemSettingsApp
(this=0x7ffe8ec212b0, argc=, argv=) at
/usr/src/debug/systemsettings-5.7.3/app/SystemSettingsApp.cpp:28
#33 0x0040c6ef in main (argc=1, argv=) at
/usr/src/debug/systemsettings-5.7.3/app/main.cpp:32

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

[systemsettings] [Bug 366802] Systemsettings crash when opening second instance

[via KDE Bugzilla]

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

--- Comment #5 from edisonalvari...@bol.com.br ---
sorry for the debugging garbage maybe I should open a bug at opensuse it 's not
so obvious that you need to install some packages like debugsource and headers.

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

[systemsettings] [Bug 366802] Systemsettings crash when opening second instance

[via KDE Bugzilla]

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

edisonalvari...@bol.com.br changed:

   What|Removed |Added

   Severity|normal  |crash

--- Comment #4 from edisonalvari...@bol.com.br ---
sorry for the debuging gar

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

[kdenlive] [Bug 351381] Video preview of clips with transitions in project monitor area is extremely slow

[via KDE Bugzilla]

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

--- Comment #15 from h.k.gh...@gmail.com ---
I changed the repos and replaced kdenlive as follows:

1. uninstalled kdenlive
2. removed the kdenlive-master PPA
3. apt-get update
4. add the kdenlive-testing PPA
5. apt-get update
6. apt-get install kdenlive

Checked the installed version and it was down to 16.08.0... which looks like
it's behind the kdenlive-master PPA. I had the same (lack of) timeline behavior
I reported above. If this behavior is really there, I think kdenlive's feedback
to the user about that being there and working should be made significantly
more visible/obvious, because I just don't see it. To the best of my knowledge,
there's no behavior bound to the timeline preview options. (And it's also not
in the timeline settings option).

Any ideas of what you think I might be doing wrong here? Are you really sure
the info you have on which repository I should be using, and the content in
them, is accurate and correct? This is looking like strike 2.. :/

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

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

[Chris via KDE Bugzilla]

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

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

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

[drkonqi] [Bug 366811] New: unexpected error code from bugzilla

[Miroslav Puda via KDE Bugzilla]

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

Bug ID: 366811
   Summary: unexpected error code from bugzilla
   Product: drkonqi
   Version: 5.5.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: paka...@gmail.com

After segfault in plasma drkonqi tried to send bug report but failed with error

Error sending the crash report: /Received unexpected error code 50 from
bugzilla.
Error message was: You must select/enter a product../

Reproducible: Always

Steps to Reproduce:
1. File bug report with help of drkonqi.
2. Try to send it.
3. Error is received, retry does not help.



For a reference, this is bug report I tried to send:

Application:  (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.14 x86_64

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

I opened main KDE menu from main panel and typed "chromium". As I typed I got
segfault.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Plasma (), signal: Segmentation fault
Using host libthread_db library
"/nix/store/gwl3ppqj4i730nhd4f50ncl5jc4n97ks-glibc-2.23/lib/libthread_db.so.1".
To enable execution of this file add
add-auto-load-safe-path
/nix/store/c7ipds48nb7sfzhb7vqp26rrllirxwxv-gcc-5.3.0/lib/libstdc++.so.6.0.21-gdb.py
line to your configuration file "/home/mirpa/.gdbinit".
To completely disable this security protection add
set auto-load safe-path /
line to your configuration file "/home/mirpa/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
info "(gdb)Auto-loading safe path"
[Current thread is 1 (Thread 0x7f2c868087c0 (LWP 1209))]

Thread 20 (Thread 0x7f2b9f7fe700 (LWP 1576)):
#0  0x7f2c7ec1b05f in pthread_cond_wait@@GLIBC_2.3.2 () from
/nix/store/gwl3ppqj4i730nhd4f50ncl5jc4n97ks-glibc-2.23/lib/libpthread.so.0
#1  0x7f2c8049971b in QWaitCondition::wait(QMutex*, unsigned long) () from
/nix/store/3k7p0szmsnvhwsiz2a80a4jfxffyzcwn-qtbase-5.5.1/lib/libQt5Core.so.5
#2  0x7f2bcc1ef99f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from
/nix/store/ll9x8x5psn4cv4f613crym17xny7j0mf-threadweaver-5.19.0/lib/libKF5ThreadWeaver.so.5
#3  0x7f2bcc1f3ed8 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) ()
from
/nix/store/ll9x8x5psn4cv4f613crym17xny7j0mf-threadweaver-5.19.0/lib/libKF5ThreadWeaver.so.5
#4  0x7f2bcc1eeacf in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/nix/store/ll9x8x5psn4cv4f613crym17xny7j0mf-threadweaver-5.19.0/lib/libKF5ThreadWeaver.so.5
#5  0x7f2bcc1f1923 in ThreadWeaver::Thread::run() () from
/nix/store/ll9x8x5psn4cv4f613crym17xny7j0mf-threadweaver-5.19.0/lib/libKF5ThreadWeaver.so.5
#6  0x7f2c8049859f in ?? () from
/nix/store/3k7p0szmsnvhwsiz2a80a4jfxffyzcwn-qtbase-5.5.1/lib/libQt5Core.so.5
#7  0x7f2c7ec166e4 in start_thread () from
/nix/store/gwl3ppqj4i730nhd4f50ncl5jc4n97ks-glibc-2.23/lib/libpthread.so.0
#8  0x7f2c7f8aa25d in clone () from
/nix/store/gwl3ppqj4i730nhd4f50ncl5jc4n97ks-glibc-2.23/lib/libc.so.6

Thread 19 (Thread 0x7f2ba4c8f700 (LWP 1575)):
[KCrash Handler]
#5  0x7f2ba7498ed8 in mdb_txn_renew0 () from
/nix/store/yizrfxlh2n6b33jk1pdmirqgvniwl14l-lmdb-0.9.16/lib/liblmdb.so
#6  0x7f2ba749a2c4 in mdb_txn_begin () from
/nix/store/yizrfxlh2n6b33jk1pdmirqgvniwl14l-lmdb-0.9.16/lib/liblmdb.so
#7  0x7f2ba7b21cdb in Baloo::SearchStore::exec(Baloo::Term const&, unsigned
int, int, bool) () from
/nix/store/d4qpq6lm0p3vm1cpcc4m57y6g3c22ng8-baloo-5.19.0/lib/libKF5Baloo.so.5
#8  0x7f2ba7b0be02 in Baloo::Query::exec() () from
/nix/store/d4qpq6lm0p3vm1cpcc4m57y6g3c22ng8-baloo-5.19.0/lib/libKF5Baloo.so.5
#9  0x7f2bb80688f0 in SearchRunner::match(Plasma::RunnerContext&, QString
const&, QString const&) () from
/nix/store/3gl3145mfcg2k916apxa9yd0q8shillz-plasma-workspace-5.5.5.2/lib/qt5/plugins/krunner_baloosearchrunner.so
#10 0x7f2bb8069259 in SearchRunner::match(Plasma::RunnerContext&) () from
/nix/store/3gl3145mfcg2k916apxa9yd0q8shillz-plasma-workspace-5.5.5.2/lib/qt5/plugins/krunner_baloosearchrunner.so
#11 0x7f2bcccff038 in
Plasma::AbstractRunner::performMatch(Plasma::RunnerContext&) () from
/nix/store/g3fr92bls34a2hdhp65fma0kadk0l3dj-krunner-5.19.0/lib/libKF5Runner.so.5
#12 0x7f2bcc1f3150 in
ThreadWeaver::Executor::run(QSharedPointer const&,
ThreadWeaver::Thread*) () from
/nix/store/ll9x8x5psn4cv4f613crym17xny7j0mf-threadweaver-5.19.0/lib/libKF5ThreadWeaver.so.5
#13 0x7f2bcc1f20fa in
ThreadWeaver::Job::execute(QSharedPointer const&,
ThreadWeaver::Thread*) () from
/nix/store/ll9x8x5psn4cv4f613crym17xny7j0mf-threadweaver-5.19.0/lib/libKF5ThreadWeaver.so.5
#14 0x7f2bcc1f185a in 

[plasmashell] [Bug 358990] Make possible to move desktop icons freely again

[Roman Bysh via KDE Bugzilla]

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

--- Comment #31 from Roman Bysh  ---
Follow Up

Can you please bring back the features that we had in KDE4? Now that was a
user-friendly plasmoid - without the bugs.

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

[plasmashell] [Bug 358990] Make possible to move desktop icons freely again

[Roman Bysh via KDE Bugzilla]

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

--- Comment #30 from Roman Bysh  ---
Eike,

Any chance you can add back all of the features when Plasma 6 comes out? ;->

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

[plasmashell] [Bug 359570] Icons cannot be positioned freely on desktop (folder view), snap to grid instead

[Roman Bysh via KDE Bugzilla]

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

--- Comment #6 from Roman Bysh  ---
After speaking with Eike I'm getting the impression that she does not plan on
changing anything.
Maybe in Plasma 6, when the flat view can have an improved look as previously
available in KDE4 ;-)

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

[konqueror] [Bug 366810] New: Crash by Start. I'm using openSuse 42.1 Leap KDE

[Christian Seipel via KDE Bugzilla]

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

Bug ID: 366810
   Summary: Crash by Start. I'm using openSuse 42.1 Leap KDE
   Product: konqueror
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: c.sei...@gmx.de

Application: konqueror (4.14.18)
KDE Platform Version: 4.14.18
Qt Version: 4.8.6
Operating System: Linux 4.1.27-27-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:I start my browser and it
crashes :). Maybe http://www.wieistmeineip.de/ makes Problems.

- Custom settings of the application:I use Socks Proxy

The crash can be reproduced sometimes.

-- Backtrace:
Application: Konqueror (konqueror), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb6a2971780 (LWP 6123))]

Thread 8 (Thread 0x7fb689ab1700 (LWP 6124)):
#0  0x7fb6a123803f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fb68ea88eb6 in WTF::TCMalloc_PageHeap::scavengerThread() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7fb68ea88ee9 in  () at /usr/lib64/libQtWebKit.so.4
#3  0x7fb6a12340a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fb69ff2502d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7fb64855d700 (LWP 6125)):
#0  0x7fb69ff1cbfd in poll () at /lib64/libc.so.6
#1  0x7fb69d02ce64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fb69d02cf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fb6a15f8fde in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7fb6a15cad4f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7fb6a15cb045 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7fb6a14c84df in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7fb6a14cabbf in  () at /usr/lib64/libQtCore.so.4
#8  0x7fb6a12340a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fb69ff2502d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7fb647332700 (LWP 6127)):
#0  0x7fb6a12383e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fb68eab0fe6 in WTF::ThreadCondition::timedWait(WTF::Mutex&, double)
() at /usr/lib64/libQtWebKit.so.4
#2  0x7fb68e7fba3c in JSC::BlockAllocator::waitForRelativeTime(double) ()
at /usr/lib64/libQtWebKit.so.4
#3  0x7fb68e7fbaa8 in JSC::BlockAllocator::blockFreeingThreadMain() () at
/usr/lib64/libQtWebKit.so.4
#4  0x7fb68eab0a06 in WTF::wtfThreadEntryPoint(void*) () at
/usr/lib64/libQtWebKit.so.4
#5  0x7fb6a12340a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7fb69ff2502d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7fb63df7b700 (LWP 6134)):
#0  0x7fb6a123803f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fb63dfe2d79 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#2  0x7fb63dfe3819 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#3  0x7fb6a12340a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fb69ff2502d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fb63d77a700 (LWP 6135)):
#0  0x7fb6a123803f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fb63dfe2d79 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#2  0x7fb63dfe3819 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#3  0x7fb6a12340a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fb69ff2502d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fb63cf79700 (LWP 6136)):
#0  0x7fb6a123803f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fb63dfe2d79 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#2  0x7fb63dfe3819 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#3  0x7fb6a12340a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fb69ff2502d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fb61a133700 (LWP 6193)):
#0  0x7fb69ff1cbfd in poll () at /lib64/libc.so.6
#1  0x7fb69d02ce64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fb69d02cf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fb6a15f8fde in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7fb6a15cad4f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7fb6a15cb045 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7fb6a14c84df in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7fb697216e7e in  () at /usr/lib64/libkio.so.5
#8  0x7fb6a14cabbf in  () at 

[kdenlive] [Bug 351381] Video preview of clips with transitions in project monitor area is extremely slow

[via KDE Bugzilla]

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

--- Comment #14 from h.k.gh...@gmail.com ---
(In reply to Wegwerf from comment #13)
> The testing ppa would be better suited, but master is within one commit
> behind testing. Blog post and video are of an earlier development versions,
> with some usability optimizations having landed only afterwards.

I used the master ppa because, when I asked about it, you suggested I use that
one, saying

> The new features are in the beta branch (which is rougly the same as the 
> master branch
> at his time.

I'll try the testing one soon and hope your info is accurate this time, as I
spent quite a bit trying to make this work yesterday...


> Anyway, did you start with a fresh project or did you load an existing
> project?

Started a new project.

> Usually, unless disable preview is set in the timeline preview menu in the
> timeline toolbar

The disable preview option was not set. I did play around with that, too.

> then adding the current timeline selection/region should
> result in a red bar appearing in the timeline. 

But it didn't. I'll remove the master repo, add the testing one, and see if I
got accurate info this time.

> You should find a preview profile both (!) in the project settings for your
> current project, as well as in the configuration dialog. They look a little
> bit different from the early dev versions.

We'll see.

> However, if you don't see them, are you sure the update after adding the ppa 
> did correctly
> update your installation?

Kdenlive had a visible message on the lower left stating that it was a beta
version, so it definitely worked. I also specified the version number in my
previous post, which I thought would answer this question from the outset.
Wondering whether apt-get update/install/etc is suddenly not working seems like
an odd thing to suggest.

I'll post again after I've tried this again.

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

[krita] [Bug 366770] Can't see my marks on the canvas until I click outside of the canvas.

[via KDE Bugzilla]

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

--- Comment #4 from aeare...@gmail.com ---
Turning off openGL worked, thank you!

On Aug 15, 2016 3:32 PM, "wolthera via KDE Bugzilla" <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=366770
>
> --- Comment #3 from wolthera  ---
> sorry, I mistyped, I asked if turning  instant preview or
> settings->configure
> Krita->display->openGL off helps?
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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

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

[RussianNeuroMancer via KDE Bugzilla]

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

RussianNeuroMancer  changed:

   What|Removed |Added

 CC||russianneuroman...@ya.ru

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

[neon] [Bug 366722] sddm fails to start after kernel upgrade

[Bernhard Scheirle via KDE Bugzilla]

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

--- Comment #4 from Bernhard Scheirle  ---
Ok, the problem was that the kernel upgrade did not upgrade my nvidia kernel
module and therefore said module failed to load (reported in
`/var/log/Xorg.0.log`).

Fix/Workaround:
$ sudo aptitude purge nvidia-361
$ sudo shutdown -r now
$ sudo ubuntu-drivers autoinstall

I hope I don't have to do this every kernel upgrade.

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

[drkonqi] [Bug 366792] trying to report a crash, drkonqi needs to install debug packages, which takes too long, cancel causes the crash

[Wolfgang Bauer via KDE Bugzilla]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||wba...@tmo.at

--- Comment #1 from Wolfgang Bauer  ---
Well, the installing doesn't take too long, it just doesn't work at all.
That's caused by a regression in konsole, see
http://bugzilla.opensuse.org/show_bug.cgi?id=990353 and bug#366793.

Cancel shouldn't cause a crash though, it doesn't here.
Can you provide a backtrace please?

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

[KScreen] [Bug 365353] kscreen snaps to top of monitors, prevents alignment to bottom of each screen

[Bernhard Scheirle via KDE Bugzilla]

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

Bernhard Scheirle  changed:

   What|Removed |Added

 CC||bernhard+...@scheirle.de

--- Comment #1 from Bernhard Scheirle  ---
I'm also affected by this bug.

And thanks for the xrandr command workaround.

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

[konsole] [Bug 345712] Closing last tab results in a crash

[Simon Andric via KDE Bugzilla]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[konsole] [Bug 342201] Crash on Konsole exit when using proprietary nvidia drivers

[Simon Andric via KDE Bugzilla]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[krita] [Bug 363779] Undo applies at beginning of stroke

[Jelena via KDE Bugzilla]

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

Jelena  changed:

   What|Removed |Added

 CC||jelen...@t-online.de

--- Comment #2 from Jelena  ---
Same here. Mac OS X 10.11.6, Krita 3.0.
After Stroke and Undo and Starting a new stroke the previous stroke gets
removed - but even then it doesn't get removed completely but a light shadow
remains. This shadow only disappears if you paint something else close to the
previous shape (you see that rectangle parts of the screen get refreshed step
by step).

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

[kopete] [Bug 225747] kopete does not encode utf xml properly when sending to jabber (xmpp) server

[Pali Rohár via KDE Bugzilla]

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

Pali Rohár  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
   Version Fixed In||16.08.1
  Latest Commit||http://commits.kde.org/kope
   ||te/f23d6ccc7a7f542059c3956d
   ||64d912a34584723e

--- Comment #8 from Pali Rohár  ---
Git commit f23d6ccc7a7f542059c3956d64d912a34584723e by Pali Rohár.
Committed on 15/08/2016 at 15:58.
Pushed by pali into branch 'Applications/16.08'.

jabber: Workaround bug in QtXML: Fix xmlToString when QDomElement contains
Unicode characters above 0x

Upstream:
https://github.com/psi-im/iris/commit/8612bc340421087cf0ebfd426661ff22f7351270

See also discussion:
https://github.com/psi-im/iris/pull/44
https://github.com/psi-im/iris/pull/43
https://github.com/psi-im/iris/issues/42
https://github.com/psi-im/iris/issues/13
https://bugreports.qt.io/browse/QTBUG-25291
Related: bug 314272
FIXED-IN: 16.08.1

A  +19   -0protocols/jabber/libiris/patches/01_qtxml_unicode.patch
M  +8-0protocols/jabber/libiris/src/xmpp/xmpp-core/xmlprotocol.cpp

http://commits.kde.org/kopete/f23d6ccc7a7f542059c3956d64d912a34584723e

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

[kopete] [Bug 314272] Kopete disconnects from Jabber when sending text outside of BOM

[Pali Rohár via KDE Bugzilla]

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

Pali Rohár  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kope
   ||te/f23d6ccc7a7f542059c3956d
   ||64d912a34584723e
   Version Fixed In||16.08.1
 Resolution|DUPLICATE   |FIXED

--- Comment #11 from Pali Rohár  ---
Git commit f23d6ccc7a7f542059c3956d64d912a34584723e by Pali Rohár.
Committed on 15/08/2016 at 15:58.
Pushed by pali into branch 'Applications/16.08'.

jabber: Workaround bug in QtXML: Fix xmlToString when QDomElement contains
Unicode characters above 0x

Upstream:
https://github.com/psi-im/iris/commit/8612bc340421087cf0ebfd426661ff22f7351270

See also discussion:
https://github.com/psi-im/iris/pull/44
https://github.com/psi-im/iris/pull/43
https://github.com/psi-im/iris/issues/42
https://github.com/psi-im/iris/issues/13
https://bugreports.qt.io/browse/QTBUG-25291
Related: bug 225747
FIXED-IN: 16.08.1

A  +19   -0protocols/jabber/libiris/patches/01_qtxml_unicode.patch
M  +8-0protocols/jabber/libiris/src/xmpp/xmpp-core/xmlprotocol.cpp

http://commits.kde.org/kopete/f23d6ccc7a7f542059c3956d64d912a34584723e

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

[krita] [Bug 366757] Tags for extra brushes don't seem to be loaded.

[north w via KDE Bugzilla]

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

--- Comment #2 from north w  ---
I have standard brushes in Dockers(right-click ui) but as there are NO tags
listed in the drop-down box I can't change brush-sets...
On Aug 15, 2016 6:45 AM, "wolthera via KDE Bugzilla" <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=366757
>
> wolthera  changed:
>
>What|Removed |Added
> 
> 
> Summary|hey... Default builtin FX   |Tags for extra brushes
>|brushes dont show up in the |don't seem to be loaded.
>|app...  |
>  Status|UNCONFIRMED |NEEDSINFO
>  Resolution|--- |WAITINGFORINFO
>  CC||griffinval...@gmail.com
>
> --- Comment #1 from wolthera  ---
> So what you are trying to say is that your tags aren't being loaded? The
> brushes themselves should be in the brush preset docker still. Are there
> still
> tags inside the brush-preset docker?
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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

[valgrind] [Bug 199468] Suppressions: stack size limited to 25 while --num-callers allows up to 50 frames

[Robin Kuzmin via KDE Bugzilla]

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

--- Comment #6 from Robin Kuzmin  ---
Makes sense for me.

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

[krita] [Bug 366741] Krita crashes with segmentation fault if all gradients are removed

[Bruno P . Kinoshita via KDE Bugzilla]

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

--- Comment #4 from Bruno P. Kinoshita  ---
> KoResourceServer does notify all the observers with notifyRemovingResource.

Oh, maybe calling connectToServer in the Item Chooser would fix that too. 

>Beside that there appears to be at least another bug as the first two 
>gradients should not be removeable.

True. Noticed that every time I restarted Krita there would always be two
gradients there.

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

[kmix] [Bug 366533] No icon for clementine in kmix

[LtWorf]

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

--- Comment #5 from Salvo "LtWorf" Tomaselli  ---
I reassigned to kmix then.

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

[kmix] [Bug 366533] No icon for clementine in kmix

[LtWorf]

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

Salvo "LtWorf" Tomaselli  changed:

   What|Removed |Added

Version|5.5.5   |4.5
Product|Oxygen  |kmix
  Component|icons   |Visual: Layout and GUI

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

[kate] [Bug 366809] New: undelete "Display Prefix", "Display Arguments" and "Display Postfix"

[zmi via KDE Bugzilla]

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

Bug ID: 366809
   Summary: undelete "Display Prefix", "Display Arguments" and
"Display Postfix"
   Product: kate
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: plugin-snippets
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: zmi...@gmail.com

I am missing additional meta fields in current snippets plug-in.

Deletion of additional  meta fields "Display Prefix", "Display Arguments" and
"Display Postfix" is a HUGE step backward in the functionality.  In previous
version of snippets plug-in it was possible to create groups of similar
snippets with single name "class" and additional comments  using  "Display
Prefix", "Display Arguments" and "Display Postfix" meta fields (if one has
snippets with similar keyword name but with slightly different functional
purpose), e.g. :
class X
class X // but with my default constructor
enhanced class X // but using inheritance from Y

where class is in name, X is in arguments, enhanced is in prefix and comments
are in postfix fields (or any other combination) and I used them intensively to
add explanations what each snippet does exactly.

Such named fields were visible in the code completion preview mode during
typing in the name "class" and one was able to select readily the right one
from the sublist.

Now this all is gone and there is no way to add any visible comment to snippet.
Moreover, one is forced to write such_ugly_and _different_names of snippets,
because the only "name" field doesn't allow to add even spaces! 

class_X
class_X_with_default_constructor
enhanced_class_X_with_default_constructor

Snippets plug-in should give overview of snippets and not only create a list of
names. I agree that this is ok if you have about 20 snippets, you can overview
all of them.  But if one has a library with about 1000 snippets with many
groups of  5-20 snippets with the same keyword name?

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

[trojita] [Bug 366498] InvalidResponseCode due to a 64bit UIDNEXT

[Paul D Mallett via KDE Bugzilla]

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

--- Comment #9 from Paul D Mallett  ---
   Jan

   Just to complete this one; usa.net got back to me

   "Good Day, we already received an answer from our Systems Engineer and
   they already created a "Jira Ticket - HCMS-699" meaning that this is a
   known issue and they already on the process of fixing this specific
   issue."

   No time scale but good news, once again thanks for your help.

   Paul

   Paul D. Mallett
   Sandbach, Seale Lane, Seale, Farnham, Surrey. GU10 1PR
   United Kingdom
   PHN:  +44 (0)1252 782084
   MBL:  +44 (0)7836 273377
   SKP:   pauldmallett
   NET: pauldmall...@usa.net [1]   

   On 12/08/16 11:42, Jan Kundrát via KDE Bugzilla wrote:

 https://bugs.kde.org/show_bug.cgi?id=366498  
 --- Comment #8 from Jan Kundrát   [2]  ---
 Yes, telling them that the following line violates
https://tools.ietf.org/html/rfc3501#section-2.3.1.1  might help them fix
their
 software.

   * OK [UIDVALIDITY 42036101441452023] UIDs valid␍␊





   1. mailto:pauldmall...@usa.net
   2. mailto:j...@kde.org

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

[gwenview] [Bug 366808] Gwenview

[Emilijan Abraham via KDE Bugzilla]

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

Emilijan Abraham  changed:

   What|Removed |Added

Version|unspecified |5.0.0

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

[gwenview] [Bug 366808] New: Gwenview

[Emilijan Abraham via KDE Bugzilla]

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

Bug ID: 366808
   Summary: Gwenview
   Product: gwenview
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: abre...@gmail.com
CC: myr...@kde.org

Application: gwenview (4.14.0 pre)
KDE Platform Version: 4.14.18 (Compiled from sources)
Qt Version: 4.8.6
Operating System: Linux 4.1.27-27-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
Application: Gwenview (gwenview), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f57168e9840 (LWP 15897))]

Thread 3 (Thread 0x7f56fe4cb700 (LWP 15901)):
[KCrash Handler]
#6  0x7f57129e38c2 in Exiv2::Exifdatum::Exifdatum(Exiv2::Exifdatum const&)
() at /usr/lib64/libexiv2.so.14
#7  0x7f57164be82a in  () at /usr/lib64/libgwenviewlib.so.4
#8  0x7f57164bd46c in Gwenview::JpegContent::loadFromData(QByteArray
const&, Exiv2::Image*) () at /usr/lib64/libgwenviewlib.so.4
#9  0x7f5716489bf5 in  () at /usr/lib64/libgwenviewlib.so.4
#10 0x7f57164876ae in  () at /usr/lib64/libgwenviewlib.so.4
#11 0x7f5716488901 in  () at /usr/lib64/libgwenviewlib.so.4
#12 0x7f5715d52ace in  () at /usr/lib64/libQtCore.so.4
#13 0x7f5715d5ebbf in  () at /usr/lib64/libQtCore.so.4
#14 0x7f57106790a4 in start_thread () at /lib64/libpthread.so.0
#15 0x7f571332402d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f56ff3d9700 (LWP 15899)):
#0  0x7f571331bbfd in poll () at /lib64/libc.so.6
#1  0x7f57101a9e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f57101a9f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f5715e8cfde in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7f5715e5ed4f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7f5715e5f045 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7f5715d5c4df in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7f5715e40653 in  () at /usr/lib64/libQtCore.so.4
#8  0x7f5715d5ebbf in  () at /usr/lib64/libQtCore.so.4
#9  0x7f57106790a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f571332402d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f57168e9840 (LWP 15897)):
#0  0x7f571067d03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5715d5f0a6 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQtCore.so.4
#2  0x7f5715d51d32 in  () at /usr/lib64/libQtCore.so.4
#3  0x7f5715d53195 in QThreadPool::~QThreadPool() () at
/usr/lib64/libQtCore.so.4
#4  0x7f5715d531c9 in QThreadPool::~QThreadPool() () at
/usr/lib64/libQtCore.so.4
#5  0x7f5715d53995 in  () at /usr/lib64/libQtCore.so.4
#6  0x7f5713276b39 in __run_exit_handlers () at /lib64/libc.so.6
#7  0x7f5713276b85 in  () at /lib64/libc.so.6
#8  0x7f5714074028 in  () at /usr/lib64/libQtGui.so.4
#9  0x7f5714d23a50 in KApplication::xioErrhandler(_XDisplay*) () at
/usr/lib64/libkdeui.so.5
#10 0x7f571226b37e in _XIOError () at /usr/lib64/libX11.so.6
#11 0x7f57122694ca in _XReply () at /usr/lib64/libX11.so.6
#12 0x7f571225f855 in XQueryPointer () at /usr/lib64/libX11.so.6
#13 0x7f571408c708 in QCursor::pos() () at /usr/lib64/libQtGui.so.4
#14 0x7f5714508f72 in QAbstractItemView::verticalScrollbarValueChanged(int)
() at /usr/lib64/libQtGui.so.4
#15 0x7f5715e740fa in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#16 0x7f57146568ce in QAbstractSlider::valueChanged(int) () at
/usr/lib64/libQtGui.so.4
#17 0x7f571452322c in QListView::scrollTo(QModelIndex const&,
QAbstractItemView::ScrollHint) () at /usr/lib64/libQtGui.so.4
#18 0x7f57164dfa5d in Gwenview::ThumbnailView::scrollToSelectedIndex() ()
at /usr/lib64/libgwenviewlib.so.4
#19 0x004493e4 in _start ()

The crash can be reproduced every time.

-- Backtrace:
Application: Gwenview (gwenview), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f57168e9840 (LWP 15897))]

Thread 3 (Thread 0x7f56fe4cb700 (LWP 15901)):
[KCrash Handler]
#6  0x7f57129e38c2 in Exiv2::Exifdatum::Exifdatum(Exiv2::Exifdatum const&)
() at /usr/lib64/libexiv2.so.14
#7  0x7f57164be82a in  () at /usr/lib64/libgwenviewlib.so.4
#8  0x7f57164bd46c in Gwenview::JpegContent::loadFromData(QByteArray
const&, Exiv2::Image*) () at /usr/lib64/libgwenviewlib.so.4
#9  0x7f5716489bf5 in  () at /usr/lib64/libgwenviewlib.so.4
#10 0x7f57164876ae in  () at /usr/lib64/libgwenviewlib.so.4
#11 0x7f5716488901 in  () at 

[KScreen] [Bug 366721] Connecting an external monitor causes the laptop screen to go black with only the mouse cursor visible

[Sebastian Kügler via KDE Bugzilla]

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

Sebastian Kügler  changed:

   What|Removed |Added

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

--- Comment #4 from Sebastian Kügler  ---
> Other minor bug: If a screen is attached or detached when "Display 
> configuration" is open the screen positions in the config dialog are messed 
> up.

I actually fixed this last week (in master).

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

[Oxygen] [Bug 366533] No icon for clementine in kmix

[pinheiro via KDE Bugzilla]

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

--- Comment #4 from pinheiro  ---
The main criteria used to be apps that are part of KDE, and a few other I did
for fun, its debatable if we should do app icons for apps outside the KDE
space, mostly because its might be a violation of the individual apps "brand"
say for Gnome file manager we would do an ugly icon that looked like a banana,
in that case the app developers in gnome would think with good reason that we
were being rude and going out of our way to make their app look bad in a
KDEPLasmaDesktop space.

I'm sure this is not the case with clementine nor will it be, in the cases were
I did make an icon for an non KDE app I tried to be respectful of the app core
brand values...

having said that there might be a bug in kmix as if there is no icon it should
use the one the app ships by itself in I think highcolor folder

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

[krita] [Bug 363924] [Huion 610] Losing pressure sensitiveness when opening other softwares

[via KDE Bugzilla]

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

--- Comment #3 from zeuse...@gmail.com ---
No it's only with the v7, and I'm still using it because the buttons bug of v12
is more annoying to me.
But I guess it makes more sense to fix the latest driver's bug.

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

[digikam] [Bug 366095] Raw files not (always) properly decoded when using "raw data in half size" option for preview

[via KDE Bugzilla]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/digi
   ||kam/d0a60f5f02890de9e5a5a3e
   ||312511930f3cf72a5
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||5.2.0

--- Comment #5 from caulier.gil...@gmail.com ---
Just tested under Windows. The dysfunction cannot be reproduced. 

I close this file now. Don't hesitate to re-open if necessary.

Gilles Caulier

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

[krita] [Bug 362487] [Huion 610] Cursor is misaligned with brush/tools

[via KDE Bugzilla]

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

--- Comment #18 from zeuse...@gmail.com ---
Hello,
yes that's it.

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

[kwin] [Bug 358369] Plasma crashed after opening an HTML5 video in Chrome

[via KDE Bugzilla]

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

_...@ukr.net changed:

   What|Removed |Added

 CC|_...@ukr.net|

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

[krita] [Bug 366737] layer lock at selection, unlock button not present

[via KDE Bugzilla]

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

stephanh...@posteo.de changed:

   What|Removed |Added

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

--- Comment #7 from stephanh...@posteo.de ---
It worked! All the icons are there now and the app works finde. 
Thanks guys!

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

[krita] [Bug 366770] Can't see my marks on the canvas until I click outside of the canvas.

[wolthera via KDE Bugzilla]

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

--- Comment #3 from wolthera  ---
sorry, I mistyped, I asked if turning  instant preview or settings->configure
Krita->display->openGL off helps?

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

[plasmashell] [Bug 366690] klipper shortcut for open clipboard at mouse point

[Thomas Pfeiffer via KDE Bugzilla]

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

Thomas Pfeiffer  changed:

   What|Removed |Added

 CC||thomas.pfeif...@kde.org

--- Comment #3 from Thomas Pfeiffer  ---
There was a misunderstanding: Andreas meant that there should be a default
shortcut set for the action because it's a quite useful one.

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

[krita] [Bug 366770] Can't see my marks on the canvas until I click outside of the canvas.

[via KDE Bugzilla]

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

--- Comment #2 from aeare...@gmail.com ---
I have an Intel(R) HD Graphics card. Instant preview was already turned on.

I just installed Krita. This has been an issue since it started running for
me.

On Aug 15, 2016 6:47 AM, "wolthera via KDE Bugzilla" <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=366770
>
> wolthera  changed:
>
>What|Removed |Added
> 
> 
>  Status|UNCONFIRMED |NEEDSINFO
>  Resolution|--- |WAITINGFORINFO
>  CC||griffinval...@gmail.com
>
> --- Comment #1 from wolthera  ---
> Which graphics card+driver do you have? And does turning view->instant
> preview
> help?
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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

[krita] [Bug 366741] Krita crashes with segmentation fault if all gradients are removed

[Sven Langkamp via KDE Bugzilla]

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

Sven Langkamp  changed:

   What|Removed |Added

 CC||sven.langk...@gmail.com

--- Comment #3 from Sven Langkamp  ---
It should work with several adapters. KoResourceServer does notify all the
observers with notifyRemovingResource.

Beside that there appears to be at least another bug as the first two gradients
should not be removeable.

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

[plasmashell] [Bug 366807] New: panel crashed after mouse click on searched application

[Pali via KDE Bugzilla]

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

Bug ID: 366807
   Summary: panel crashed after mouse click on searched
application
   Product: plasmashell
   Version: 5.7.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: pstr...@pobox.sk
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.7.0)

Qt Version: 5.6.1
Frameworks Version: 5.24.0
Operating System: Linux 4.6.2-1-default x86_64
Distribution: "openSUSE Tumbleweed (20160805) (x86_64)"

-- Information about the crash:
panel crashed after mouse click on searched application

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 0x7fe388ef88c0 (LWP 2031))]

Thread 24 (Thread 0x7fe288ff9700 (LWP 11748)):
#0  0x7fe381d3809f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fe382c2e18b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fe2cce55ec0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7fe2cce5a068 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7fe2cce5503d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7fe2cce5a0c2 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7fe2cce5503d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7fe2cce57f09 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7fe382c2d2d8 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fe381d32474 in start_thread () at /lib64/libpthread.so.0
#10 0x7fe3825383ed in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7fe2897fa700 (LWP 11747)):
#0  0x7fe381d3809f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fe382c2e18b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fe2cce55ec0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7fe2cce5a068 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7fe2cce5503d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7fe2cce5a0c2 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7fe2cce5503d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7fe2cce57f09 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7fe382c2d2d8 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fe381d32474 in start_thread () at /lib64/libpthread.so.0
#10 0x7fe3825383ed in clone () at /lib64/libc.so.6

Thread 22 (Thread 0x7fe289ffb700 (LWP 11746)):
#0  0x7fe381d3809f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fe382c2e18b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fe2cce55ec0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7fe2cce5a068 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7fe2cce5503d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7fe2cce5a0c2 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7fe2cce5503d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7fe2cce5a0c2 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7fe2cce5503d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7fe2cce5a0c2 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7fe2cce5503d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#11 0x7fe2cce57f09 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#12 0x7fe382c2d2d8 in  () at /usr/lib64/libQt5Core.so.5
#13 0x7fe381d32474 in start_thread () at /lib64/libpthread.so.0
#14 0x7fe3825383ed in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7fe28a7fc700 (LWP 11745)):
#0  0x7fe381d3809f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fe382c2e18b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fe2cce55ec0 in

[Breeze] [Bug 353496] Breeze Icons in emacs toolbar: Dired icon too big

[Uri Herrera via KDE Bugzilla]

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

Uri Herrera  changed:

   What|Removed |Added

   Assignee|uri_herr...@nitrux.in   |visual-des...@kde.org

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

[kdenlive] [Bug 366806] New: In 16.08.0 the project monitor remains blank (gray) while clips are playing

[via KDE Bugzilla]

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

Bug ID: 366806
   Summary: In 16.08.0 the project monitor remains blank (gray)
while clips are playing
   Product: kdenlive
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: robil...@gmail.com

Whenever I try to play a clip (either from the project bin or from the tracks)
the project monitor remains blank (gray). There is sound, the overlays work. I
can even edit the video (blindly) but I can't seem to turn on motion picture in
the project monitor. 

Probably related: For "extract frame", the save dialogue appears, but after
hitting okay, nothing happens. No new file is created (not even a blank gray
one).

Reproducible: Always

Steps to Reproduce:
1. Add video clip.
2. Play it.
3. No picture. 

Actual Results:  
No video is seen in the project monitor.

Expected Results:  
There should be a video instead of the gray area.

Previous versions worked fine.

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

[kdenlive] [Bug 364857] sudo port install kdenlive ==> Error: org.macports.archivefetch for port

[Todd via KDE Bugzilla]

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

--- Comment #2 from Todd  ---
No joy. Same problem:

…
receiving file list ... done
PortIndex.rmd160

sent 44 bytes  received 626 bytes  268.00 bytes/sec
total size is 512  speedup is 0.76
DEBUG: successful verification with key
/opt/local/share/macports/macports-pubkey.pem
--->  MacPorts base is already the latest version
DEBUG: Setting MacPorts sources ownership to root

The ports tree has been updated. To upgrade your installed ports, you should
run
  port upgrade outdated
BRiX2:~ Todd$ sudo port -u upgrade outdated
Nothing to upgrade.
BRiX2:~ Todd$ sudo port intsall kdenlive
Error: Unrecognized action "port intsall"
BRiX2:~ Todd$ sudo port install kdenlive
--->  Computing dependencies for kdenlive
--->  Dependencies to be installed: automoc qt4-mac dbus expat jpeg libmng
lcms2 tiff xz gettext libiconv ncurses zlib libpng openssl cdrtools smake
clang-3.4 cctools llvm-3.8 libcxx libedit libffi llvm_select clang-3.3
clang_select ld64 ld64-latest llvm-3.3 perl5 perl5.22 gdbm python27 bzip2 db48
python2_select python_select sqlite3 libxml2 llvm-3.4 cmake curl curl-ca-bundle
libarchive lzo2 dvdauthor ImageMagick autoconf automake djvulibre fftw-3
fontconfig freetype ghostscript jbig2dec libidn libpaper libtool pkgconfig
xorg-libXext xorg-libX11 xorg-kbproto xorg-libXau xorg-xproto xorg-libXdmcp
xorg-libxcb xorg-libpthread-stubs xorg-xcb-proto xorg-xextproto xorg-libXt
xorg-libsm xorg-libice jbigkit openexr ilmbase openjpeg urw-fonts webp
libdvdread libdvdcss kde4-runtime attica phonon bison bison-runtime m4 exiv2
gpgme gnupg2 gpg-agent libassuan libgpg-error pth libgcrypt libksba
pinentry-mac libusb-compat libusb openldap cyrus-sasl2 kerberos5 libcomerr db46
icu tcp_wrappers readline hicolor-icon-theme kactivities kdelibs4 aspell
texinfo aspell-dict-en avahi dbus-python27 dbus-glib glib2 pcre
gobject-introspection cairo libpixman xorg-xcb-util xrender xorg-renderproto
py27-mako py27-beaker py27-setuptools py27-markupsafe gtk3 at-spi2-atk
at-spi2-core xorg-libXi xorg-inputproto xorg-libXfixes xorg-fixesproto
xorg-libXtst xorg-recordproto atk gdk-pixbuf2 jasper shared-mime-info libepoxy
python34 python3_select mesa xorg-dri2proto xorg-glproto xorg-libXdamage
xorg-damageproto xorg-libXmu xorg-libXxf86vm xorg-xf86vidmodeproto pango Xft2
harfbuzz graphite2 xorg-libXcomposite xorg-compositeproto xorg-libXcursor
xorg-libXinerama xorg-xineramaproto xorg-libXrandr xorg-randrproto libdaemon
libglade2 gtk2 py27-gdbm py27-pygtk py27-cairo py27-gobject py27-numpy libgcc
gmp isl libmpc mpfr py27-cython cython_select py27-nose nosetests_select
dbusmenu-qt qjson docbook-xml docbook-xml-4.1.2 docbook-xml-4.2 xmlcatmgr
docbook-xml-4.3 docbook-xml-4.4 docbook-xml-4.5 docbook-xml-5.0 docbook-xsl
enchant giflib grantlee libxslt qca shared-desktop-ontologies docbook-xsl-ns
soprano libiodbc raptor2 redland rasqal mhash strigi boost clucene ffmpeg XviD
fribidi gmake gnutls libtasn1 nettle p11-kit desktop-file-utils popt lame
libass libbluray libmodplug libogg libopus libsdl libtheora libvorbis libvpx
schroedinger orc soxr speex x264 yasm virtuoso virtuoso-7 gawk nepomuk-core
ebook-tools convertlit libtommath libzip coreutils kfilemetadata mobipocket
poppler-qt4-mac git p5.22-authen-sasl p5.22-digest-hmac p5.22-digest-sha1
p5.22-gssapi p5.22-cgi p5.22-html-parser p5.22-html-tagset p5.22-error
p5.22-net-smtp-ssl p5.22-io-socket-ssl p5.22-net-libidn p5.22-net-ssleay
p5.22-test-exception p5.22-sub-uplevel p5.22-test-nowarnings p5.22-test-warn
p5.22-term-readkey rsync openjpeg15 poppler poppler-data taglib kdepimlibs4
akonadi mariadb-server mariadb mysql_select qt4-mac-mariadb-plugin libical
prison libdmtx qrencode libssh openslp oxygen-icons qimageblitz samba3 mlt
doxygen flex frei0r-plugins libexif libsamplerate libsndfile flac libsdl_image
sox libid3tag libmad libmagic opencore-amr opusfile twolame wavpack
--->  Fetching archive for expat
--->  Attempting to fetch expat-2.2.0_0.darwin_15.x86_64.tbz2 from
https://packages.macports.org/expat
--->  Attempting to fetch expat-2.2.0_0.darwin_15.x86_64.tbz2 from
http://fco.it.packages.macports.org/mirrors/macports-packages/expat/expat
--->  Attempting to fetch expat-2.2.0_0.darwin_15.x86_64.tbz2 from
http://her.gr.packages.macports.org/expat
--->  Attempting to fetch expat-2.2.0_0.darwin_15.x86_64.tbz2 from
http://jnb.za.packages.macports.org/packages/expat
--->  Attempting to fetch expat-2.2.0_0.darwin_15.x86_64.tbz2 from
http://lil.fr.packages.macports.org/expat
--->  Attempting to fetch expat-2.2.0_0.darwin_15.x86_64.tbz2 from
http://nou.nc.packages.macports.org/pub/macports/packages.macports.org/expat
--->  Attempting to fetch expat-2.2.0_0.darwin_15.x86_64.tbz2 from
http://nue.de.packages.macports.org/expat
--->  Attempting to fetch expat-2.2.0_0.darwin_15.x86_64.tbz2 from
http://mse.uk.packages.macports.org/sites/packages.macports.org/expat
--->  Attempting to fetch expat-2.2.0_0.darwin_15.x86_64.tbz2 from

[systemsettings] [Bug 366802] Systemsettings crash when opening second instance

[via KDE Bugzilla]

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

--- Comment #3 from edisonalvari...@bol.com.br ---
gdb systemsettings5
GNU gdb (GDB; openSUSE Leap 42.2) 7.9.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from systemsettings5...Reading symbols from
/usr/lib/debug/usr/bin/systemsettings5.debug...done.
done.
(gdb) start
Temporary breakpoint 1 at 0x40c6a0: file
/usr/src/debug/systemsettings-5.7.3/app/main.cpp, line 31.
Starting program: /usr/bin/systemsettings5 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".

Temporary breakpoint 1, main (argc=1, argv=0x7fffdc68) at
/usr/src/debug/systemsettings-5.7.3/app/main.cpp:31
31  {
(gdb) continue
Continuing.
[New Thread 0x7fffe53ba700 (LWP 15170)]

Program received signal SIGSEGV, Segmentation fault.
QMutex::lock (this=this@entry=0x20) at thread/qmutex.cpp:225
225 if (fastTryLock(current))
(gdb)

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

[systemsettings] [Bug 366802] Systemsettings crash when opening second instance

[via KDE Bugzilla]

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

--- Comment #2 from edisonalvari...@bol.com.br ---

gdb systemsettings5
GNU gdb (GDB; openSUSE Leap 42.2) 7.9.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from systemsettings5...Reading symbols from
/usr/lib/debug/usr/bin/systemsettings5.debug...done.
done.
(gdb) start
Temporary breakpoint 1 at 0x40c6a0: file
/usr/src/debug/systemsettings-5.7.3/app/main.cpp, line 31.
Starting program: /usr/bin/systemsettings5 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".

Temporary breakpoint 1, main (argc=1, argv=0x7fffdc68) at
/usr/src/debug/systemsettings-5.7.3/app/main.cpp:31
31  {
(gdb) continue
Continuing.
[New Thread 0x7fffe53ba700 (LWP 15170)]

Program received signal SIGSEGV, Segmentation fault.
QMutex::lock (this=this@entry=0x20) at thread/qmutex.cpp:225
225 if (fastTryLock(current))
(gdb) 


Temporary breakpoint 1, main (argc=1, argv=0x7fffdce8) at
/usr/src/debug/systemsettings-5.7.3/app/main.cpp:31 
31  {   
(gdb) continue  
Continuing. 
[New Thread 0x7fffe53ba700 (LWP 14483)] 

Program received signal SIGSEGV, Segmentation fault.
QMutex::lock (this=this@entry=0x20) at thread/qmutex.cpp:225
225 thread/qmutex.cpp: No such file or directory.   
(gdb)

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

[krita] [Bug 366737] layer lock at selection, unlock button not present

[Sven Langkamp via KDE Bugzilla]

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

--- Comment #6 from Sven Langkamp  ---
Yes, try the appimage version (no installation required) and check if the icons
show up with that.

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

[frameworks-baloo] [Bug 353342] Crash - mdb_txn_begin (m_env=0)

[Tom Chiverton via KDE Bugzilla]

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

--- Comment #30 from Tom Chiverton  ---
Given the well defined exception, and recovery steps, why doesn't Baloo do
disable /enable automatically when it occurs? 
Overhead of a rescan less bad than no indexing

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

[Baloo] [Bug 366805] New: baloo crashed unexpectedly

[stewart via KDE Bugzilla]

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

Bug ID: 366805
   Summary: baloo crashed unexpectedly
   Product: Baloo
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: pinak.ah...@gmail.com
  Reporter: stewart_robert...@sky.com

Application: baloo_file (5.18.0)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-34-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

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

I was changing the settings in a virtualbox vm using the Oracle VM VirtualBox
Manager (V5.1). Specifically i changed the monitor count from 1 to 2...

Suspect VirtualBox activity is unrelated but crash was instanteneous after this
action & made me suspicious they were related so I include the info in case
there is some possible reason why one would cause the other. May well just be a
coincidence.

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

Thread 2 (Thread 0x7f6e2a845700 (LWP 5313)):
#0  0x7f6f73ab8e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6f70c5839c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6f70c584ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6f74702a9b in QEventDispatcherGlib::processEvents
(this=0x7f6e240008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f6f746a9dea in QEventLoop::exec (this=this@entry=0x7f6e2a844bc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x00420cd8 in Baloo::FileContentIndexer::run (this=0x17aab80) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/filecontentindexer.cpp:71
#6  0x7f6f744c8343 in QThreadPoolThread::run (this=0x189a590) at
thread/qthreadpool.cpp:93
#7  0x7f6f744cb84e in QThreadPrivate::start (arg=0x189a590) at
thread/qthread_unix.cpp:331
#8  0x7f6f731156fa in start_thread (arg=0x7f6e2a845700) at
pthread_create.c:333
#9  0x7f6f73ac4b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f6f759e18c0 (LWP 4614)):
[KCrash Handler]
#6  0x7f6f739f3418 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f6f739f501a in __GI_abort () at abort.c:89
#8  0x7f6f721e5002 in mdb_assert_fail (env=0x17aadd0,
expr_txt=expr_txt@entry=0x7f6f721e6a5f "rc == 0",
func=func@entry=0x7f6f721e7398 <__func__.7098> "mdb_page_dirty",
line=line@entry=2065, file=0x7f6f721e6a40 "mdb.c") at mdb.c:1481
#9  0x7f6f721da6a5 in mdb_page_dirty (txn=0x1763c60, mp=) at
mdb.c:2065
#10 0x7f6f721db863 in mdb_page_alloc (num=num@entry=1,
mp=mp@entry=0x7ffc1cfd0908, mc=0x7ffc1cfd0e40) at mdb.c:2246
#11 0x7f6f721dbac9 in mdb_page_touch (mc=mc@entry=0x7ffc1cfd0e40) at
mdb.c:2364
#12 0x7f6f721dd704 in mdb_cursor_touch (mc=mc@entry=0x7ffc1cfd0e40) at
mdb.c:6267
#13 0x7f6f721e0805 in mdb_cursor_put (mc=0x7ffc1cfd0e40,
key=0x7ffc1cfd1220, data=0x7ffc1cfd1230, flags=) at mdb.c:6401
#14 0x7f6f721e3260 in mdb_put (txn=0x1763c60, dbi=3,
key=key@entry=0x7ffc1cfd1220, data=data@entry=0x7ffc1cfd1230,
flags=flags@entry=0) at mdb.c:8759
#15 0x7f6f74ba3eba in Baloo::PositionDB::put
(this=this@entry=0x7ffc1cfd1310, term=..., list=...) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/positiondb.cpp:79
#16 0x7f6f74bb6b5a in Baloo::WriteTransaction::commit (this=) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/writetransaction.cpp:314
#17 0x7f6f74bae032 in Baloo::Transaction::commit
(this=this@entry=0x7ffc1cfd13a0) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/transaction.cpp:262
#18 0x0042a02b in Baloo::MetadataMover::moveFileMetadata
(this=0x1781f80, from=..., to=...) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/metadatamover.cpp:58
#19 0x7f6f746dae4f in QtPrivate::QSlotObjectBase::call (a=0x7ffc1cfd1500,
r=0x7ffc1cfd1bc0, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#20 QMetaObject::activate (sender=sender@entry=0x17373f0,
signalOffset=, local_signal_index=local_signal_index@entry=7,
argv=argv@entry=0x7ffc1cfd1500) at kernel/qobject.cpp:3698
#21 0x7f6f746db7d7 in QMetaObject::activate (sender=sender@entry=0x17373f0,
m=m@entry=0x644cc0 ,
local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x7ffc1cfd1500)
at kernel/qobject.cpp:3578
#22 0x0042aaba in KInotify::moved (this=this@entry=0x17373f0, _t1=...,
_t2=...) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/obj-x86_64-linux-gnu/src/file/moc_kinotify.cpp:330
#23 0x0042cbff in KInotify::slotEvent (this=,
socket=) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/kinotify.cpp:421

[krita] [Bug 366737] layer lock at selection, unlock button not present

[via KDE Bugzilla]

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

--- Comment #5 from stephanh...@posteo.de ---
It's the version from the Linux Mint package. Shall I try to download it
directly from your site?

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

[krita] [Bug 366737] layer lock at selection, unlock button not present

[Sven Langkamp via KDE Bugzilla]

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

Sven Langkamp  changed:

   What|Removed |Added

 CC||sven.langk...@gmail.com

--- Comment #4 from Sven Langkamp  ---
Maybe the icons are missing in the distribution package. As you can see there
are also icons missing in the top right button.

Are you using the package from your distribution or the appimage?

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

[kdevelop] [Bug 366804] New: Crash while editing

[Leozito via KDE Bugzilla]

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

Bug ID: 366804
   Summary: Crash while editing
   Product: kdevelop
   Version: 4.7.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: independent.scient...@gmail.com

Application: kdevelop (4.7.3)
KDE Platform Version: 4.14.22
Qt Version: 4.8.7
Operating System: Linux 4.7.0-2-default x86_64
Distribution: "openSUSE Tumbleweed (20160812) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Crashes everytime while im editing a particular line on a particular cpp file.

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 0x7fbf7bd76940 (LWP 19594))]

Thread 10 (Thread 0x7fbeb8be4700 (LWP 19776)):
#0  0x7fbf782c7bcd in nanosleep () at /lib64/libc.so.6
#1  0x7fbf782f0864 in usleep () at /lib64/libc.so.6
#2  0x7fbf772dd65a in KDevelop::DUChainLock::lockForWrite(unsigned int) ()
at /usr/lib64/libkdevplatformlanguage.so.8
#3  0x7fbf772dd83c in KDevelop::DUChainWriteLocker::lock() () at
/usr/lib64/libkdevplatformlanguage.so.8
#4  0x7fbec17971e6 in DeclarationBuilder::visitDeclarator(DeclaratorAST*)
() at /usr/lib64/libkdev4cppduchain.so
#5  0x7fbec1794cb4 in
DeclarationBuilder::visitFunctionDeclaration(FunctionDefinitionAST*) () at
/usr/lib64/libkdev4cppduchain.so
#6  0x7fbec178551c in
ContextBuilder::visitFunctionDefinition(FunctionDefinitionAST*) () at
/usr/lib64/libkdev4cppduchain.so
#7  0x7fbec14c2359 in void visitNodes(Visitor*,
ListNode const*) () at /usr/lib64/libkdev4cppparser.so
#8  0x7fbec1785082 in
ContextBuilder::visitClassSpecifier(ClassSpecifierAST*) () at
/usr/lib64/libkdev4cppduchain.so
#9  0x7fbec17b5ac0 in TypeBuilder::visitClassSpecifier(ClassSpecifierAST*)
() at /usr/lib64/libkdev4cppduchain.so
#10 0x7fbec179604e in
DeclarationBuilder::visitClassSpecifier(ClassSpecifierAST*) () at
/usr/lib64/libkdev4cppduchain.so
#11 0x7fbec17b3303 in
TypeBuilder::visitSimpleDeclaration(SimpleDeclarationAST*) () at
/usr/lib64/libkdev4cppduchain.so
#12 0x7fbec1794e05 in
DeclarationBuilder::visitSimpleDeclaration(SimpleDeclarationAST*) () at
/usr/lib64/libkdev4cppduchain.so
#13 0x7fbec1784534 in
ContextBuilder::visitTemplateDeclaration(TemplateDeclarationAST*) () at
/usr/lib64/libkdev4cppduchain.so
#14 0x7fbec14c2359 in void visitNodes(Visitor*,
ListNode const*) () at /usr/lib64/libkdev4cppparser.so
#15 0x7fbec178442b in ContextBuilder::visitNamespace(NamespaceAST*) () at
/usr/lib64/libkdev4cppduchain.so
#16 0x7fbec17973c0 in DeclarationBuilder::visitNamespace(NamespaceAST*) ()
at /usr/lib64/libkdev4cppduchain.so
#17 0x7fbec14c2359 in void visitNodes(Visitor*,
ListNode const*) () at /usr/lib64/libkdev4cppparser.so
#18 0x7fbec1789e9d in KDevelop::AbstractContextBuilder::supportBuild(AST*, KDevelop::DUContext*) () at
/usr/lib64/libkdev4cppduchain.so
#19 0x7fbec1787183 in
ContextBuilder::buildContexts(KSharedPtr, AST*,
QList*, KDevelop::ReferencedTopDUContext const&, bool) () at
/usr/lib64/libkdev4cppduchain.so
#20 0x7fbec17910c1 in
DeclarationBuilder::buildDeclarations(KSharedPtr, AST*,
QList*, KDevelop::ReferencedTopDUContext const&, bool) () at
/usr/lib64/libkdev4cppduchain.so
#21 0x7fbec1aa7ecd in CPPInternalParseJob::run() () at
/usr/lib64/kde4/kdevcpplanguagesupport.so
#22 0x7fbec1aae046 in PreprocessJob::sourceNeeded(QString&,
rpp::Preprocessor::IncludeType, int, bool) () at
/usr/lib64/kde4/kdevcpplanguagesupport.so
#23 0x7fbec12996df in rpp::pp::handle_include(bool, rpp::Stream&,
rpp::Stream&) () at /usr/lib64/libkdev4cpprpp.so
#24 0x7fbec129d9cf in rpp::pp::handle_directive(unsigned int, rpp::Stream&,
rpp::Stream&) () at /usr/lib64/libkdev4cpprpp.so
#25 0x7fbec129e0ae in rpp::pp::operator()(rpp::Stream&, rpp::Stream&) () at
/usr/lib64/libkdev4cpprpp.so
#26 0x7fbec129e427 in rpp::pp::processFileInternal(QString const&,
QByteArray const&, QVector&) () at /usr/lib64/libkdev4cpprpp.so
#27 0x7fbec129e805 in rpp::pp::processFile(QString const&, QByteArray
const&) () at /usr/lib64/libkdev4cpprpp.so
#28 0x7fbec1aaff54 in PreprocessJob::run() () at
/usr/lib64/kde4/kdevcpplanguagesupport.so
#29 0x7fbec1aa49ee in CPPParseJob::parseForeground() () at
/usr/lib64/kde4/kdevcpplanguagesupport.so
#30 0x7fbec1aae046 in PreprocessJob::sourceNeeded(QString&,
rpp::Preprocessor::IncludeType, int, bool) () at
/usr/lib64/kde4/kdevcpplanguagesupport.so
#31 0x7fbec12996df in rpp::pp::handle_include(bool, 

[plasmashell] [Bug 365970] Demanding attention tasks are not shown on all desktops

[via KDE Bugzilla]

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

--- Comment #5 from kdde@porcupinefactory.org ---
The windows demanding attention are still not shown when they are in separate
activities - this is a departure from the previous behaviour.
Unfortunately, I can't reopen this bug, so I'll describe the bug again:

Reproducible: always

Steps to reproduce:
1. Open a Konsole window
2. Switch to another activity
3. Open a terminal window
4. Issue "wall" command

Actual:
A message appears in the current terminal.

Expected:
A message appears in the current terminal and the Konsole task manager entry
appears in the "demands attention" mode.

Additional info:
My task manager has the following options checked: "Show only tasks from
current desktop" and Show only tasks from current activity".
Plasma version 5.7.3-2.fc23

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

[kdeplasma-addons] [Bug 366803] New: Show desktop grid button

[Josef Kufner via KDE Bugzilla]

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

Bug ID: 366803
   Summary: Show desktop grid button
   Product: kdeplasma-addons
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: General
  Assignee: plasma-b...@kde.org
  Reporter: j...@frozen-doe.net

I find very useful a button which shows desktop grid effect using following
command:

qdbus org.kde.kglobalaccel /component/kwin
org.kde.kglobalaccel.Component.invokeShortcut ShowDesktopGrid

I think it would be nice to have widget which implements this and maybe other
similar features, so other users can have such button too without experimenting
with DBUS.

It should be same as "Show Desktop" widget, but with different effect.

Reproducible: Always

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

[systemsettings] [Bug 366802] Systemsettings crash when opening second instance

[via KDE Bugzilla]

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

--- Comment #1 from edisonalvari...@bol.com.br ---
 ok seems that I need more debuginfos 

gdb systemsettings5 
GNU gdb (GDB; openSUSE Leap 42.2) 7.9.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from systemsettings5...Reading symbols from
/usr/lib/debug/usr/bin/systemsettings5.debug...done.
done.
(gdb) start
Temporary breakpoint 1 at 0x40c6a0: file
/usr/src/debug/systemsettings-5.7.3/app/main.cpp, line 31.
Starting program: /usr/bin/systemsettings5 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".

Temporary breakpoint 1, main (argc=1, argv=0x7fffdc68) at
/usr/src/debug/systemsettings-5.7.3/app/main.cpp:31
31  /usr/src/debug/systemsettings-5.7.3/app/main.cpp: No such file or
directory.
(gdb) continue
Continuing.
[New Thread 0x7fffe53ba700 (LWP 12661)]

Program received signal SIGSEGV, Segmentation fault.
QMutex::lock (this=this@entry=0x20) at thread/qmutex.cpp:225
225 thread/qmutex.cpp: No such file or directory.
Missing separate debuginfos, use: zypper install
kimageformats-debuginfo-5.25.0-93.1.x86_64 libHalf11-debuginfo-2.1.0-5.2.x86_64
libIex-2_1-11-debuginfo-2.1.0-5.2.x86_64
libIlmImf-Imf_2_1-21-debuginfo-2.1.0-7.3.x86_64
libIlmThread-2_1-11-debuginfo-2.1.0-5.2.x86_64
libjasper1-debuginfo-1.900.1-165.3.x86_64 libjbig2-debuginfo-2.0-4.3.x86_64
libjpeg8-debuginfo-8.0.2-32.8.x86_64 liblcms1-debuginfo-1.19-20.3.x86_64
libmng1-debuginfo-1.0.10-4.3.x86_64
libqt5-qtimageformats-debuginfo-5.7.0-67.1.x86_64
libtiff5-debuginfo-4.0.6-1.4.x86_64 libwebp5-debuginfo-0.4.3-7.3.x86_64
libwebpdemux1-debuginfo-0.4.3-7.3.x86_64
(gdb)

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

[systemsettings] [Bug 366802] New: Systemsettings crash when opening second instance

[via KDE Bugzilla]

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

Bug ID: 366802
   Summary: Systemsettings crash when opening second instance
   Product: systemsettings
   Version: 5.7.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: edisonalvari...@bol.com.br

systemsettings crash when opening a second instance.

Reproducible: Always

Steps to Reproduce:
1. Just open a second instance.
2.
3.

Actual Results:  
crash


Opensuse 42.2 Alpha - Qt5 development repository (openSUSE_Leap_42.2)
xorg and related from the X11 pontostroy repos.

I can't debug it I don't know if I am missing some library. It seems that not
here is what happens when I try to debug. 

GNU gdb (GDB; openSUSE Leap 42.2) 7.9.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/systemsettings5...Reading symbols from
/usr/lib/debug/usr/bin/systemsettings5.debug...done.
done.
Attaching to program: /usr/bin/systemsettings5, process 10406
Reading symbols from /usr/lib64/libsystemsettingsview.so.3...Reading symbols
from /usr/lib/debug/usr/lib64/libsystemsettingsview.so.3.debug...done.
done.
Reading symbols from /usr/lib64/libKF5KCMUtils.so.5...Reading symbols from
/usr/lib/debug/usr/lib64/libKF5KCMUtils.so.5.25.0.debug...done.
done.
Reading symbols from /usr/lib64/libKF5XmlGui.so.5...Reading symbols from
/usr/lib/debug/usr/lib64/libKF5XmlGui.so.5.25.0.debug...done.
done.
Reading symbols from /usr/lib64/libKF5IconThemes.so.5...Reading symbols from
/usr/lib/debug/usr/lib64/libKF5IconThemes.so.5.25.0.debug...done.
done.
Reading symbols from /usr/lib64/libKF5WindowSystem.so.5...Reading symbols from
/usr/lib/debug/usr/lib64/libKF5WindowSystem.so.5.25.0.debug...done.
done.
Reading symbols from /usr/lib64/libKF5ConfigWidgets.so.5...Reading symbols from
/usr/lib/debug/usr/lib64/libKF5ConfigWidgets.so.5.25.0.debug...done.
done.
Reading symbols from /usr/lib64/libKF5Completion.so.5...Reading symbols from
/usr/lib/debug/usr/lib64/libKF5Completion.so.5.25.0.debug...done.
done.
Reading symbols from /usr/lib64/libKF5ConfigGui.so.5...Reading symbols from
/usr/lib/debug/usr/lib64/libKF5ConfigGui.so.5.25.0.debug...done.
done.
Reading symbols from /usr/lib64/libKF5WidgetsAddons.so.5...Reading symbols from
/usr/lib/debug/usr/lib64/libKF5WidgetsAddons.so.5.25.0.debug...done.
done.
Reading symbols from /usr/lib64/libQt5Widgets.so.5...Reading symbols from
/usr/lib/debug/usr/lib64/libQt5Widgets.so.5.7.0.debug...done.
done.
Reading symbols from /usr/lib64/libQt5Gui.so.5...Reading symbols from
/usr/lib/debug/usr/lib64/libQt5Gui.so.5.7.0.debug...done.
done.
Reading symbols from /usr/lib64/libKF5Service.so.5...Reading symbols from
/usr/lib/debug/usr/lib64/libKF5Service.so.5.25.0.debug...done.
done.   
Reading symbols from /usr/lib64/libKF5I18n.so.5...Reading symbols from
/usr/lib/debug/usr/lib64/libKF5I18n.so.5.25.0.debug...done. 
done.   
Reading symbols from /usr/lib64/libKF5DBusAddons.so.5...Reading symbols from
/usr/lib/debug/usr/lib64/libKF5DBusAddons.so.5.25.0.debug...done.   
done.   
Reading symbols from /usr/lib64/libQt5DBus.so.5...Reading symbols from
/usr/lib/debug/usr/lib64/libQt5DBus.so.5.7.0.debug...done.  
done.   
Reading symbols from /usr/lib64/libKF5ConfigCore.so.5...Reading symbols from
/usr/lib/debug/usr/lib64/libKF5ConfigCore.so.5.25.0.debug...done.   
done.   
Reading symbols from /usr/lib64/libKF5CoreAddons.so.5...Reading symbols from
/usr/lib/debug/usr/lib64/libKF5CoreAddons.so.5.25.0.debug...done.   
done.   
Reading symbols from /usr/lib64/libQt5Core.so.5...Reading symbols from
/usr/lib/debug/usr/lib64/libQt5Core.so.5.7.0.debug...done.  
done.

[kwin] [Bug 366742] Qbitorrent Xorg/kwin_x11 high cpu usage while adding more than 1 torrent at the same time.

[Tony via KDE Bugzilla]

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

--- Comment #3 from Tony  ---
Sadly can't provide a proper backtrace

When i try to do it as non-root i get "ptrace: Operation not permitted."
Using sudo + having the compositor on, gdb won't even open on the terminal and
the desktop locks.
Tried to cancel the command ctrl+c, no go, i killed x to regain control

I tried again with compositor off, .It works but  while gdb is running i can't
click on anything, i mean i can, but there is no response, can't drag windows,
right click menus etc.  so cannot switch to it.

Tried to open it from the terminal and i got this error:
"Could not resolve property : linearGradient4566"

I ran "bt" before closing gdb, this is what i got:

Attaching to process 3820
[New LWP 3825]
[New LWP 3827]
[New LWP 3854]
[New LWP 3915]
[New LWP 6011]
[New LWP 6012]
[New LWP 6013]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f5378455e8d in poll () at ../sysdeps/unix/syscall-template.S:84
84  ../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) bt
#0  0x7f5378455e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f5376328614 in poll (__timeout=, __nfds=5,
__fds=0x1906118)
at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  qt_ppoll (timeout_ts=, nfds=5, fds=0x1906118) at
kernel/qcore_unix.cpp:93
#3  qt_safe_poll (fds=0x1906118, nfds=nfds@entry=5,
timeout_ts=timeout_ts@entry=0x7ffee2132320)
at kernel/qcore_unix.cpp:121
#4  0x7f5376329fb8 in QEventDispatcherUNIX::processEvents (this=, flags=..., 
flags@entry=...) at kernel/qeventdispatcher_unix.cpp:495
#5  0x7f536255e87d in QUnixEventDispatcherQPA::processEvents
(this=, flags=...)
at eventdispatchers/qunixeventdispatcher.cpp:68
#6  0x7f53762d7d9a in QEventLoop::exec (this=this@entry=0x7ffee2132460,
flags=..., 
flags@entry=...) at kernel/qeventloop.cpp:210
#7  0x7f53762e03ac in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1261
#8  0x7f5376622dbc in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1639
#9  0x7f5376bc57f5 in QApplication::exec () at kernel/qapplication.cpp:2975
#10 0x7f5378734206 in kdemain (argc=1, argv=0x7ffee21326f8) at
/workspace/build/main_x11.cpp:466
#11 0x7f537837b830 in __libc_start_main (main=0x400710 ,
argc=1, 
argv=0x7ffee21326f8, init=, fini=,
rtld_fini=, 
stack_end=0x7ffee21326e8) at ../csu/libc-start.c:291
#12 0x00400749 in _start ()
(gdb) quit
A debugging session is active.

Inferior 1 [process 3820] will be detached.

Quit anyway? (y or n) y
Detaching from program: /usr/bin/kwin_x11, process 3820


At this point i gave up installed ktorrent, not a single issue, so this is on
qbitorrent if you ask me.

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

[kmail2] [Bug 366801] New: kmail crash during mail encryption

[Tom Mittelstädt via KDE Bugzilla]

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

Bug ID: 366801
   Summary: kmail crash during mail encryption
   Product: kmail2
   Version: 5.1.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: tom-kde.b...@monster-box.de

Application: kmail (5.1.3)

Qt Version: 5.5.1
Frameworks Version: 5.23.0
Operating System: Linux 4.4.0-35-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

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

After writing an email kmail asked if i want to encrypt the message as the gpg
key is known. during this process kmail crashed.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fbc7f130980 (LWP 25999))]

Thread 29 (Thread 0x7fbbb6a23700 (LWP 20665)):
#0  0x7fbca0965e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fbc9707139c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbc970714ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbca14a8a9b in QEventDispatcherGlib::processEvents
(this=0x7fbbac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fbca144fdea in QEventLoop::exec (this=this@entry=0x7fbbb6a22c40,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7fbca126c8a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7fbca127184e in QThreadPrivate::start (arg=0x53a86b0) at
thread/qthread_unix.cpp:331
#7  0x7fbc975926fa in start_thread (arg=0x7fbbb6a23700) at
pthread_create.c:333
#8  0x7fbca0971b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 28 (Thread 0x7fbbd541d700 (LWP 27499)):
#0  QListData::begin (this=0x7fbbc40030d0) at
../../include/QtCore/../../src/corelib/tools/qlist.h:108
#1  QList::constBegin (this=0x7fbbc40030d0) at
../../include/QtCore/../../src/corelib/tools/qlist.h:302
#2  QTimerInfoList::timerWait (this=0x7fbbc40030d0, tm=...) at
kernel/qtimerinfo_unix.cpp:386
#3  0x7fbca14a7e7e in timerSourcePrepareHelper (timeout=0x7fbbd541ca84,
src=) at kernel/qeventdispatcher_glib.cpp:127
#4  timerSourcePrepare (source=, timeout=0x7fbbd541ca84) at
kernel/qeventdispatcher_glib.cpp:160
#5  0x7fbc9707092d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7fbc970712cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7fbc970714ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7fbca14a8a9b in QEventDispatcherGlib::processEvents
(this=0x7fbbc40034f0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#9  0x7fbca144fdea in QEventLoop::exec (this=this@entry=0x7fbbd541cc40,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#10 0x7fbca126c8a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#11 0x7fbca127184e in QThreadPrivate::start (arg=0x2f05970) at
thread/qthread_unix.cpp:331
#12 0x7fbc975926fa in start_thread (arg=0x7fbbd541d700) at
pthread_create.c:333
#13 0x7fbca0971b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 27 (Thread 0x7fbbbf3cd700 (LWP 26152)):
#0  0x7fbca0965e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fbc9707139c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbc970714ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbca14a8a9b in QEventDispatcherGlib::processEvents
(this=0x7fbbb8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fbca144fdea in QEventLoop::exec (this=this@entry=0x7fbbbf3ccc40,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7fbca126c8a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7fbca127184e in QThreadPrivate::start (arg=0x2e20760) at
thread/qthread_unix.cpp:331
#7  0x7fbc975926fa in start_thread (arg=0x7fbbbf3cd700) at
pthread_create.c:333
#8  0x7fbca0971b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 26 (Thread 0x7fbbb700 (LWP 26149)):
#0  0x7fbca0965e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fbc9707139c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbc970714ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbca14a8a9b in QEventDispatcherGlib::processEvents
(this=0x7fbbb80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fbca144fdea in QEventLoop::exec (this=this@entry=0x7fbbbfffec40,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7fbca126c8a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7fbca127184e 

[kwin] [Bug 366794] kwin or plasma5 crashes often when an sftp:// or a ftp:// location

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

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

--- Comment #1 from Thomas Lübking  ---
for kwin, run "kcmshell5 kwindecoration" and switch to "breeze"
For plasmashell, there's no solution - the bug is QtQuick.

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

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

[kwin] [Bug 358369] Plasma crashed after opening an HTML5 video in Chrome

[Thomas Lübking via KDE Bugzilla]

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

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

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

[kdenlive] [Bug 364428] git master 2016-06-17 - Speed and freeze effects do not work together....

[Wegwerf via KDE Bugzilla]

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

--- Comment #5 from Wegwerf  ---
Evert, imho a short textual description of the steps required to reproduce
would suffice. I didn't tested with a timeline clip with in point other than 0,
so that might be the reason I didn't noticed the bug.

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

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

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #177 from Simone Gaiarin  ---
So I did some quite extensive test today with Neon Dev unstable (KDE 5.7.90) 
and seems that most of the problems are gone. I was suffering ALL the kind of
weird bugs connected to multi monitor.

Test 1:
Boot laptop (LAP)
OK Connect external monitor EX1
OK Switch position of LAP left to right of EX1
OK Set screens vertically misaligned
!! Set external monitor as primary
  -Panel moves to EX1 properly
  - Phantom panel is left on LAP. Impossible to interact with it. Restart
plasma to remove it.
OK Detach EX1
  - Panel moves to LAP
OK Reattach EX1
  Panel moves back to EX1
OK Close lid of LAP
  - Panel stays in place in EX1
  - All windows moved to EX1
OK Open lid of lap
  - Panel stays in place in EX1
  - Only windows originally in LAP move back to LAP
KO Suspend and resume (Intel related bug probably)
  - Monitor doesn't turn on
  - KScreen detects it as active ( I can move the mouse in there and I can see
it active in display configuration)
  - Need to detach and reattach EX1 to wake it up
Disconnect EX1
KO Connect HDMI1. Kernel panic I think. PC reboot. (Reproducible) [Not related
to Kscreen I guess]

Test 2
Boot with HDMI1 connected to avoid kernel panic
OK Tinker configuration of HDMI1 + LAP. 
OK HDMI1 primary. Suspend with HDMI1 connected, detach HDMI1, resume
  - Panel found in LAP after resume
OK Disconnect HDMI1, Connect EX1 and tinker configuration. EX1 primary.
OK Close the lid, suspend, detach EX1, resume
  - Panel found in LAP

So I really hope we solved it for real this time. Great job.

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

[kdenlive] [Bug 351381] Video preview of clips with transitions in project monitor area is extremely slow

[Wegwerf via KDE Bugzilla]

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

--- Comment #13 from Wegwerf  ---
The testing ppa would be better suited, but master is within one commit behind
testing. Blog post and video are of an earlier development versions, with some
usability optimizations having landed only afterwards.

Anyway, did you start with a fresh project or did you load an existing project?

Usually, unless disable preview is set in the timeline preview menu in the
timeline toolbar, then adding the current timeline selection/region should
result in a red bar appearing in the timeline. 

You should find a preview profile both (!) in the project settings for your
current project, as well as in the configuration dialog. They look a little bit
different from the early dev versions. However, if you don't see them, are you
sure the update after adding the ppa did correctly update your installation?

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

[KScreen] [Bug 366721] Connecting an external monitor causes the laptop screen to go black with only the mouse cursor visible

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #3 from Simone Gaiarin  ---
So I did some quite extensive test today with Neon Dev unstable (KDE 5.7.90) 
and seems that most of the problems are gone. I was suffering all the kind of
weird bugs connected to multi monitor.

This bug seems to be gone, though it happened once that the wallpaper was not
shown, but the desktop was in place with icons and the possibility to interact
with it. I couldn't reproduce it.

Other minor bug: If a screen is attached or detached when "Display
configuration" is open the screen positions in the config dialog are messed up.

I'll report the full test in the panel positioning bug, since it's more
relevant for that.

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

[okular] [Bug 366785] Crash while oprning PDF from Google slides.

[Jonathan Verner via KDE Bugzilla]

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

Jonathan Verner  changed:

   What|Removed |Added

 CC||jonathan.ver...@gmail.com

--- Comment #3 from Jonathan Verner  ---
Works for me, Kubuntu 14.04:

Qt 4.8.6
KDE: 4.14.13
Okular: 0.20.3
Poppler: 0.24.5

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

[korganizer] [Bug 366800] New: Crash after disable/enable calendar

[via KDE Bugzilla]

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

Bug ID: 366800
   Summary: Crash after disable/enable calendar
   Product: korganizer
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: korganizer-de...@kde.org
  Reporter: fischer-mich...@cs.yale.edu

Application: korganizer (5.2.3)

Qt Version: 5.6.1
Frameworks Version: 5.25.0
Operating System: Linux 4.6.5-300.fc24.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:I normally have 3 calendars
open.  I close one, everything is fine.  Then I reopen it (by clicking the
box), and it crashes.

The crash can be reproduced every time.

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

Thread 12 (Thread 0x7fb315c39700 (LWP 6748)):
#0  0x7fb35d7acb49 in g_mutex_lock () at /lib64/libglib-2.0.so.0
#1  0x7fb35d767f89 in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#2  0x7fb35d76896b in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7fb35d768b5c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7fb368da524b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5  0x7fb368d545ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6  0x7fb368bb3343 in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x7fb368bb799a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7fb3646585ca in start_thread () at /lib64/libpthread.so.0
#9  0x7fb367faaead in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7fb3168e3700 (LWP 6733)):
#0  0x7fb35d7acb64 in g_mutex_unlock () at /lib64/libglib-2.0.so.0
#1  0x7fb35d76895e in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7fb35d768b5c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7fb368da524b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7fb368d545ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7fb368bb3343 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7fb368bb799a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7fb3646585ca in start_thread () at /lib64/libpthread.so.0
#8  0x7fb367faaead in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7fb331ffb700 (LWP 6710)):
#0  0x7fb367f9f32d in poll () at /lib64/libc.so.6
#1  0x7fb35d768a46 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7fb35d768b5c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7fb368da524b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7fb368d545ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7fb368bb3343 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7fb368bb799a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7fb3646585ca in start_thread () at /lib64/libpthread.so.0
#8  0x7fb367faaead in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7fb3327fc700 (LWP 6708)):
#0  0x7fb367fb8c9f in __libc_enable_asynccancel () at /lib64/libc.so.6
#1  0x7fb367f9f322 in poll () at /lib64/libc.so.6
#2  0x7fb35d768a46 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7fb35d768b5c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7fb368da524b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5  0x7fb368d545ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6  0x7fb368bb3343 in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x7fb368bb799a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7fb3646585ca in start_thread () at /lib64/libpthread.so.0
#9  0x7fb367faaead in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7fb332ffd700 (LWP 6706)):
#0  0x7fb35d7acb49 in g_mutex_lock () at /lib64/libglib-2.0.so.0
#1  0x7fb35d76847c in g_main_context_check () at /lib64/libglib-2.0.so.0
#2  0x7fb35d7689e4 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7fb35d768b5c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7fb368da524b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5  0x7fb368d545ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6  0x7fb368bb3343 in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x7fb368bb799a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7fb3646585ca in start_thread () at /lib64/libpthread.so.0
#9  0x7fb367faaead in clone () at /lib64/libc.so.6

Thread 7 

[krita] [Bug 366765] Exporting a PSD file onto a network drive causes application hang

[Wontoon via KDE Bugzilla]

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

--- Comment #4 from Wontoon  ---
So, here are those test results!

hardware: Surface 4 Pro (Core i5/4 GB Ram/128 GB SSD)
image: edgarref.kra
size: 15.4 MB (6100 x 2500)
export start: 10:25 AM PDT
...10:31 AM: still exporting...
export end: 10:33 AM
Result: Holy cow, an 8 minute export time!? The kra save barely goes over 10
seconds.
Opening the psd did not take long.

image: feeskypokefat.kra
size: 17.8 MB (3400 x 2600)
export start: 10:56 AM
...11:09 AM: still going...
export end: 11:12 AM


As a control, I will export on the Desktop as well. This is saving to another
laptop on the network; I expect a slower time since it's a laptop with a
mechanical drive:
hardware: Core i7 4770k 3.5 ghz, 16gb DDR3 RAM, 128 GB SSD (not used, but
instead the hard drive is a Western Digital Black 1 TB mechanical drive, SATA)
Additional note: I started this while the other export was happening. The CPU
itself hardly was being used so I figure the impact would be minimal.
edgarref.kra
export start: 10:59 AM
11:09 AM...still going
export end: 11:12 AM

Based upon the above results, it appears that it is indeed not an application
hang, but merely a -MASSIVE- performance decrease when a PSD file (and only a
PSD file) has to be exported over the network.

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

[kdenlive] [Bug 366799] New: Loud stutter sound at end of video

[via KDE Bugzilla]

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

Bug ID: 366799
   Summary: Loud stutter sound at end of video
   Product: kdenlive
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: mcst0rmpega...@gmail.com

Version: 0.9.8

Dev. Platform: 4.14.9

Once a video played within the application with any form of audio reaches the
end, timeline and clip monitor stop milliseconds before actual clip ends and
makes loud, horrid stutter sound. After pressing PAUSE via clip monitor, the
sound stops.

When exported / rendered and played back via other video player, this does not
happen.

Reproducible: Always

Steps to Reproduce:
1. Play any video with audio
(Does not matter where you start within the video)
2. Wait until end
3. Listen to sound
4. Press pause to stop


Actual Results:  
Stutter sound effect

Expected Results:  
Once video ends, video should just stop normally.

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

[kdm] [Bug 105631] fully support alternative authentication methods

[Michael via KDE Bugzilla]

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

Michael  changed:

   What|Removed |Added

 CC||kmhess...@web.de

--- Comment #73 from Michael  ---
Same here: Kubuntu 16.04.
Please fix the problem, it's really poor not to have the fingerprint-reader.
Please consider the time used and act soon!

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

[kdenlive] [Bug 366798] New: Timeline cursor and all timeline features not working but clip monitor still functional

[via KDE Bugzilla]

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

Bug ID: 366798
   Summary: Timeline cursor and all timeline features not working
but clip monitor still functional
   Product: kdenlive
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: mcst0rmpega...@gmail.com

I've been using this for a while but my timeline won't work at all anymore,
clip monitor still works. I can't even move the cursor most of the time. If I
do manage to move the cursor it does not effect the clip. Even when I turn
sound or video off via the timeline nothing will happen. I should also mention
it plays the clip I have selected within the project tree tab. Is there a way
to fix this? Having this bug deems Kdenlive useless.

Reproducible: Always

Steps to Reproduce:
1. Edit or operate timeline
2. Examine functionality


Clip Monitor Functionality
(Click on desired clip first in project key tab)
1. Scroll through video time via clip  monitor
2. Examine functionality



Actual Results:  
Timeline deems no functionality and clip monitor tab works as usual.

Expected Results:  
Timeline should work  as usual

Having full functionality besides other small glitches until today. I opened up
my computer, didn't update whatsoever, opened application and timeline
nonfunctional.

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

[Oxygen] [Bug 366533] No icon for clementine in kmix

[LtWorf]

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

--- Comment #3 from Salvo "LtWorf" Tomaselli  ---
I have no idea of clementine's affiliations. I just know there is such an icon
in breeze and breeze-dark

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

[kwin] [Bug 343184] KWin misdetects trimple-buffering (at least on login)

[Shannon via KDE Bugzilla]

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

Shannon  changed:

   What|Removed |Added

 CC||sgbar...@gmail.com

--- Comment #13 from Shannon  ---
I think this remains a problem or there was a regression.

Gentoo
KDE 5.6.5
nVidia proprietary drivers 367.35
nVidia-xconfig xorg.conf

I have to twiddle the Compositor settings for the tearing to stop.

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

[kate] [Bug 366797] New: JavaScript word operators formatted inconsistently

[via KDE Bugzilla]

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

Bug ID: 366797
   Summary: JavaScript word operators formatted inconsistently
   Product: kate
   Version: 3.14.2
  Platform: Debian stable
   URL: https://a.pomf.cat/jsougw.png
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: syntax
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: jec.b...@gmail.com

In JavaScript files, the 'instanceof' and 'in' operators (which normally are
formatted in black boldface font) sometimes appear in a normal weight purple
font like variables/properties. This behavior seems to be caused by a property
access with '.' (never with square bracket property access) in the left-hand
operand. The bug does not seem to occur when the operand with the property
access is surrounded by parentheses (see lines 3 and 7 in attached screenshot).

Reproducible: Always

Steps to Reproduce:
Open a JavaScript file with a line like 'object.property in ...' or
'object.property instanceof ...'. See attached screenshot for more information.

Actual Results:  
The 'in' or 'instanceof' operators are highlighted incorrectly.

Expected Results:  
The operators should have been highlighted in black boldface font.

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

[palapeli] [Bug 366796] New: Ctrl-click should never, ever deselect all pieces

[Matthew Woehlke via KDE Bugzilla]

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

Bug ID: 366796
   Summary: Ctrl-click should never, ever deselect all pieces
   Product: palapeli
   Version: 2.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: majew...@gmx.net
  Reporter: mwoehlke.fl...@gmail.com
CC: kde-games-b...@kde.org

It is very, very frustrating when I am trying to select a bunch of pieces by
clicking on them individually while holding ctrl that palapeli drops my entire
selection if the mouse is over the wrong pixel when I click.

Multi-select behavior should work like it does in every other application.
Specifically:

- A ctrl-click on empty space DOES NOTHING. It absolutely, positively should
not deselect every piece I've worked hard to select.
- A ctrl-click-and-drag should ADD to the selection, not replace it.

(It would also help if there was a little fudge factor for clicking on pieces,
but that probably deserves a separate report.)

Reproducible: Always

Steps to Reproduce:
1. Select a piece.
2. Ctrl-click on an empty area.

Actual Results:  
Selected piece is deselected.

Expected Results:  
Nothing (selection unchanged).

I'm not familiar enough with how palapeli is implemented, but it occurs to me
the problem might be in the QGV frameworks? (In which case I'm happy to punt
this to Qt...)

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

[dolphin] [Bug 366795] New: "Paste one file"/Ctrl-V disabled when copying a local file to an smb share

[Vadym Krevs via KDE Bugzilla]

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

Bug ID: 366795
   Summary: "Paste one file"/Ctrl-V disabled when copying a local
file to an smb share
   Product: dolphin
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: vkr...@yahoo.com

Regression - "Paste one file"/Ctrl-V disabled when copying a local file to an
smb share.

Using:
openSUSE Leap 42.1 with latest KDE rpms from OBS

Dolphin 16.04.3
KDE Frameworks 5.25.0
Qt 5.7.0 (built against 5.7.0)
The xcb windowing system

rpm -qa | egrep "plasma|frameworks" |sort
plasma-framework-5.25.0-134.1.x86_64
plasma-framework-components-5.25.0-134.1.x86_64
plasma-framework-lang-5.25.0-134.1.noarch
plasma-framework-private-5.25.0-134.1.x86_64
plasma-nm5-5.7.3-122.1.x86_64
plasma-nm5-lang-5.7.3-122.1.noarch
plasma-nm5-openconnect-5.7.3-122.1.x86_64
plasma-nm5-openvpn-5.7.3-122.1.x86_64
plasma-nm5-pptp-5.7.3-122.1.x86_64
plasma-nm5-vpnc-5.7.3-122.1.x86_64
plasma-theme-aya-15.08.3-1.6.noarch
plasma-theme-oxygen-16.04.3-1.7.x86_64
plasma5-addons-5.7.3-106.1.x86_64
plasma5-addons-lang-5.7.3-106.1.noarch
plasma5-desktop-5.7.3-184.1.x86_64
plasma5-desktop-branding-upstream-5.7.3-184.1.x86_64
plasma5-desktop-kimpanel-5.7.3-184.1.x86_64
plasma5-desktop-lang-5.7.3-184.1.noarch
plasma5-integration-plugin-5.7.3-18.1.x86_64
plasma5-pa-5.7.3-58.1.x86_64
plasma5-pa-lang-5.7.3-58.1.noarch
plasma5-pk-updates-0.2-18.1.x86_64
plasma5-pk-updates-lang-0.2-18.1.noarch
plasma5-workspace-5.7.3-238.1.x86_64
plasma5-workspace-branding-upstream-5.7.3-238.1.x86_64
plasma5-workspace-debuginfo-5.7.3-238.1.x86_64
plasma5-workspace-lang-5.7.3-238.1.noarch
plasma5-workspace-libs-5.7.3-238.1.x86_64

rpm -q dolphin
dolphin-16.04.3-51.3.x86_64


Reproducible: Always

Steps to Reproduce:
1. Add an SMB share to "Places" in Dolphin.
2. Select any local file in HOME, right-click and select Copy or Cut.
3. Click on the SMB share in "Places" - its contents are displayed
4. Right-click  and attempt to paste the file selected in  step 2 into the
share. 
5. The "Paste one file" menu is disabled. Ctrl-V also does not work.
 This is a regression as compared to the previous plasma/frameworks/dolphin
version

Actual Results:  
5. The "Paste one file" menu is disabled. Ctrl-V also does not work.

Expected Results:  
5. The "Paste one file" menu is not disabled. Ctrl-V  does work.

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

[krita] [Bug 366765] Exporting a PSD file onto a network drive causes application hang

[Wontoon via KDE Bugzilla]

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

--- Comment #3 from Wontoon  ---
It's my main art folder on my desktop, actually. I am not using a Homegroup
(since there was another one on the network already, thus preventing me from
making one...oh, WIndows) so I just used the "Properties -> Sharing -> Share"
option. Could edit and save images just fine but when I try to export PSD
that's when the issue arises.

(Well whaddaya know. Just as I was finishing commenting this, I just did one
more test with a simple image, a 1600x1200 image with a couple scribbles on it
just to confirm the bug with absolute certainty. It hung for a good long minute
and I was going to close Krita but it -actually succeeded-. Opens and closes
just fine. I am going to run a couple of tests with a couple of images that I
know where the issue surfaced. I'll be back with the results.)

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

[konsole] [Bug 366793] Regression in Konsole's handling of command line parameters

[Wolfgang Bauer via KDE Bugzilla]

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

--- Comment #1 from Wolfgang Bauer  ---
I'd like to add that konsole 16.08.0's command line help still says this:
$ konsole --help
Usage: konsole [options] [args]
Terminal emulator

Options:
...
  -eCommand to execute. This option will catch all
 following arguments, so use it as the last option.
...

So according to the documentation, this is supposed to work... ;-)

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

[krita] [Bug 366737] layer lock at selection, unlock button not present

[via KDE Bugzilla]

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

--- Comment #3 from stephanh...@posteo.de ---
Created attachment 100608
  --> https://bugs.kde.org/attachment.cgi?id=100608=edit
Screenshot of layer toolbox, layer 2 unlocked

First I inserted 3 layers, then worked on the second, then the third. When
trying to select the second layer again, it's unlocked!

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

[kwin] [Bug 366794] New: kwin or plasma5 crashes often when an sftp:// or a ftp:// location

[pier andre via KDE Bugzilla]

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

Bug ID: 366794
   Summary: kwin or plasma5 crashes often when an sftp:// or a
ftp:// location
   Product: kwin
   Version: 5.7.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: pier_andr...@yahoo.it

Application: kwin_x11 (5.7.3)

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

-- Information about the crash:
- What I was doing when the application crashed:
navigating or tranferring filel from local to an ftp:// or an sftp:// location

The crash can be reproduced sometimes.

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

Thread 6 (Thread 0x7fdec33b9700 (LWP 3799)):
#0  0x7fdeddff4bfd in poll () from /lib64/libc.so.6
#1  0x7fdedcf84422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7fdedcf8600f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7fdec42913e9 in QXcbEventReader::run (this=0xbbedd0) at
qxcbconnection.cpp:1337
#4  0x7fdedb340899 in QThreadPrivate::start (arg=0xbbedd0) at
thread/qthread_unix.cpp:344
#5  0x7fdedd1a10a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7fdeddffd02d in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7fdec1746700 (LWP 3800)):
#0  0x7fdeddff4bfd in poll () from /lib64/libc.so.6
#1  0x7fdedb541e3a in poll (__timeout=-1, __nfds=1, __fds=0x7fdeb4012248)
at /usr/include/bits/poll2.h:46
#2  qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7fdeb4012248) at
kernel/qcore_unix.cpp:93
#3  qt_safe_poll (fds=0x7fdeb4012248, nfds=nfds@entry=1,
timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:112
#4  0x7fdedb54366b in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:495
#5  0x7fdedb4f58cb in QEventLoop::exec (this=this@entry=0x7fdec1745da0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#6  0x7fdedb33c06a in QThread::exec (this=) at
thread/qthread.cpp:507
#7  0x7fded49dd4b5 in ?? () from /usr/lib64/libQt5DBus.so.5
#8  0x7fdedb340899 in QThreadPrivate::start (arg=0x7fded4c46d00) at
thread/qthread_unix.cpp:344
#9  0x7fdedd1a10a4 in start_thread () from /lib64/libpthread.so.0
#10 0x7fdeddffd02d in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7fdeba932700 (LWP 3819)):
#0  0x7fdeddff4bfd in poll () from /lib64/libc.so.6
#1  0x7fdedb541e3a in poll (__timeout=-1, __nfds=1, __fds=0x7fdea8000ac8)
at /usr/include/bits/poll2.h:46
#2  qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7fdea8000ac8) at
kernel/qcore_unix.cpp:93
#3  qt_safe_poll (fds=0x7fdea8000ac8, nfds=nfds@entry=1,
timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:112
#4  0x7fdedb54366b in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:495
#5  0x7fdedb4f58cb in QEventLoop::exec (this=this@entry=0x7fdeba931db0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#6  0x7fdedb33c06a in QThread::exec (this=this@entry=0x10a8e70) at
thread/qthread.cpp:507
#7  0x7fded57f7918 in QQmlThreadPrivate::run (this=0x10a8e70) at
/usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/qml/ftw/qqmlthread.cpp:147
#8  0x7fdedb340899 in QThreadPrivate::start (arg=0x10a8e70) at
thread/qthread_unix.cpp:344
#9  0x7fdedd1a10a4 in start_thread () from /lib64/libpthread.so.0
#10 0x7fdeddffd02d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fdea6cc5700 (LWP 3820)):
#0  0x7fdeddff4bfd in poll () from /lib64/libc.so.6
#1  0x7fdedb541e3a in poll (__timeout=-1, __nfds=1, __fds=0x7fdeaac8)
at /usr/include/bits/poll2.h:46
#2  qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7fdeaac8) at
kernel/qcore_unix.cpp:93
#3  qt_safe_poll (fds=0x7fdeaac8, nfds=nfds@entry=1,
timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:112
#4  0x7fdedb54366b in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:495
#5  0x7fdedb4f58cb in QEventLoop::exec (this=this@entry=0x7fdea6cc4db0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#6  0x7fdedb33c06a in QThread::exec (this=this@entry=0x198c980) at
thread/qthread.cpp:507
#7  0x7fded57f7918 in QQmlThreadPrivate::run (this=0x198c980) at
/usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/qml/ftw/qqmlthread.cpp:147
#8  0x7fdedb340899 in QThreadPrivate::start (arg=0x198c980) at
thread/qthread_unix.cpp:344
#9  0x7fdedd1a10a4 in start_thread () from /lib64/libpthread.so.0
#10 0x7fdeddffd02d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fde97a2c700 (LWP 3823)):
#0  

[konsole] [Bug 366793] New: Regression in Konsole's handling of command line parameters

[Wolfgang Bauer via KDE Bugzilla]

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

Bug ID: 366793
   Summary: Regression in Konsole's handling of command line
parameters
   Product: konsole
   Version: master
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: wba...@tmo.at

Starting with 16.08.0, starting Konsole with a command line like this doesn't
work any more:
konsole -e sh -c "echo test"

Reproducible: Always

Steps to Reproduce:
1. Run konsole -e sh -c "echo test"


Actual Results:  
konsole: Unknown option 'c'.
konsole: Use --help to get a list of available command line options.
Speicherzugriffsfehler

(as you can see it also crashes with a segmentation fault, but that's not the
topic of this bug report...)

Expected Results:  
A konsole window should pop up, displaying the text "test".
(of course it would close immediately again, adding the "--keep" parameter
should fix that)

The same works fine with konsole 16.04.3.
Therefore it's probably related to the switch to Qt's QCommandLineParser, i.e.
porting away from kdelibs4support (so maybe a bug/limitation in Qt?).

I stumbled over this when investigating why installing debug symbols in drkonqi
doesn't work any more in openSUSE with the latest git packages.
drkonqi's installdbgsymbols.sh script uses a similar construct to actually
install the packages.

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

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

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #12 from Thomas Lübking  ---
The flicker is due to the re-used buffer, the question is why one of them is
invalid but for the newly exposed area and this seems to be related to window
decorations.

Let's start with the obvious: pelase deactivate blur and contrast effects
(kcmshell5 kwineffects) and see whether it's still a problem.

You can also try
  export KWIN_USE_BUFFER_AGE=0
  kwin_x11 --replace &

and see what happens (this will read the old data from the front buffer instead
of relying on the buffer_age extension)

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

[kwin] [Bug 343661] stops drawing window content after some time, likely SyncObject related

[Alexey Sokolov via KDE Bugzilla]

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

--- Comment #66 from Alexey Sokolov  ---
I didn't mention: KDE 4.11.11 and 4.13.3, depending on the package. Not Plasma
5.

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

[kwin] [Bug 343661] stops drawing window content after some time, likely SyncObject related

[Alexey Sokolov via KDE Bugzilla]

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

--- Comment #65 from Alexey Sokolov  ---
Created attachment 100607
  --> https://bugs.kde.org/attachment.cgi?id=100607=edit
glxinfo

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

[kwin] [Bug 343661] stops drawing window content after some time, likely SyncObject related

[Alexey Sokolov via KDE Bugzilla]

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

Alexey Sokolov  changed:

   What|Removed |Added

 CC||alexey+...@asokolov.org

--- Comment #64 from Alexey Sokolov  ---
I've stumbled into an issue very similar to what's described here.

"kwin --replace" crashes for me, so I couldn't test that. However, I tried to
run Openbox instead of KWin, and freezes continued. I tried it with both
"KDE/Openbox" session, and with "openbox --replace".

I managed to fix this issue by switching compositing from OpenGL 2.0 to OpenGL
3.1 in Desktop Effects.

Can the cause be something else, not kwin?

Running ubuntu 14.04 with nvidia blob and two monitors. (I don't know whether
this is relevant or not)

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

[krita] [Bug 363080] scratchpad stops working when clicking right/middle mb while painting

[Dmitry Kazakov via KDE Bugzilla]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/krit
   ||a/596d09a948a3e8a105ee578cd
   ||20fc3dda3dcdf89
 Resolution|--- |FIXED

--- Comment #10 from Dmitry Kazakov  ---
Git commit 596d09a948a3e8a105ee578cd20fc3dda3dcdf89 by Dmitry Kazakov.
Committed on 15/08/2016 at 15:46.
Pushed by dkazakov into branch 'master'.

Fix a hangup in ScratchPad when clicking too many mouse buttons at the same
time

Fixes T3458

M  +18   -6libs/ui/widgets/kis_scratch_pad.cpp
M  +4-0libs/ui/widgets/kis_scratch_pad.h

http://commits.kde.org/krita/596d09a948a3e8a105ee578cd20fc3dda3dcdf89

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

[drkonqi] [Bug 366792] New: trying to report a crash, drkonqi needs to install debug packages, which takes too long, cancel causes the crash

[Freek de Kruijf via KDE Bugzilla]

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

Bug ID: 366792
   Summary: trying to report a crash, drkonqi needs to install
debug packages, which takes too long, cancel causes
the crash
   Product: drkonqi
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: f.de.kru...@gmail.com

After a crash of kontact, drkonqi needs to install debug packages. Trying to do
so takes too long. Pressing Cancel crashes drkonqi.
I did install kontact-debuginfo and libKF5KontactInterface5-debuginfo, but this
was not enough to skip the installation of debug packages.

Reproducible: Always

Steps to Reproduce:
1. Start kontact using kmail and click on a message with a text attachment.
Using Fancy headers, the header is displayed in a flickering way. Showing the
name of the attachment for a while and after that without that name after which
this is repeated. Clicking on the name of the attachment, in order to be able
to save it, causes the crash of kontact.
2. Press to load debuginfo packages and after several minutes, press Cancel.



This is the beta version of the current KF5 applications, together with
Framework and Qt5.7.

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

[okular] [Bug 366785] Crash while oprning PDF from Google slides.

[Oliver Sander via KDE Bugzilla]

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

Oliver Sander  changed:

   What|Removed |Added

 CC||oliver.san...@tu-dresden.de

--- Comment #2 from Oliver Sander  ---
Works for me:  Debian Testing

Qt: 4.8.7
KDE: 4.14.22
Okular: 0.25.0

poppler:  0.44.0-3

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