[okular] [Bug 361538] Text selection misses some characters

[Jonathan via KDE Bugzilla]

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

--- Comment #3 from Jonathan  ---
Created attachment 98954
  --> https://bugs.kde.org/attachment.cgi?id=98954=edit
Problem doesn't happen with PDF.

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

[kdf] [Bug 361723] kdf in kf5 does not show all mounted compared to kdf in kde4

[Burkhard Lueck via KDE Bugzilla]

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

--- Comment #11 from Burkhard Lueck  ---
Created attachment 98953
  --> https://bugs.kde.org/attachment.cgi?id=98953=edit
output of df -h  with sdc1 + lexar unmounted

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

[okular] [Bug 361538] Text selection misses some characters

[Jonathan via KDE Bugzilla]

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

--- Comment #2 from Jonathan  ---
Created attachment 98952
  --> https://bugs.kde.org/attachment.cgi?id=98952=edit
A trivial test file where the issue can be reproduced.

I notice that the problem does not happen with PDF files.

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

[kmymoney4] [Bug 361906] Kmymoney crashed when updating currencies

[Thomas Baumgart via KDE Bugzilla]

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

--- Comment #2 from Thomas Baumgart  ---
I tried hard to duplicate the problem to no avail. From the analysis of the
crash information the cause might be tied to your datafile. Can you please
provide me with an anonymized version of your data file? See
https://docs.kde.org/stable4/de/extragear-office/kmymoney/details.formats.anonymous.html
(or likewise the english version on
https://docs.kde.org/stable4/en/extragear-office/kmymoney/details.formats.anonymous.html).
The mail address would be kmymoney-de...@kde.org or likewise my personal one.

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

[amarok] [Bug 363054] Building amarok-2.8.90 with GCC-6.1.0 fails with "error: 'Playlists::Playlist::ModelStack' has not been declared"

[via KDE Bugzilla]

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

nsane...@gmail.com changed:

   What|Removed |Added

 CC||nsane...@gmail.com

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

[amarok] [Bug 363054] New: Building amarok-2.8.90 with GCC-6.1.0 fails with "error: 'Playlists::Playlist::ModelStack' has not been declared"

[via KDE Bugzilla]

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

Bug ID: 363054
   Summary: Building amarok-2.8.90 with GCC-6.1.0 fails with
"error: 'Playlists::Playlist::ModelStack' has not been
declared"
   Product: amarok
   Version: 2.8.90 (2.9 beta)
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: amarok-bugs-d...@kde.org
  Reporter: nsane...@gmail.com

Building amarok-2.8.90 with GCC-6.1.0 fails with:

>/var/tmp/portage/media-sound/amarok-2.8.90-r1/work/amarok-2.8.90/src/core-impl/playlists/types/file/xspf/XSPFPlaylist.cpp:
> In member function 'void Playlists::XSPFPlaylist::load()':
>/var/tmp/portage/media-sound/amarok-2.8.90-r1/work/amarok-2.8.90/src/core-impl/playlists/types/file/xspf/XSPFPlaylist.cpp:104:33:
> error: 'Playlists::Playlist::ModelStack' has not been declared
> ::Playlist::ModelStack::instance()->bottom()->rowCount(),



Reproducible: Always

Steps to Reproduce:
1. emerge -1 =amarok-2.8.90-r1

Actual Results:  
/var/tmp/portage/media-sound/amarok-2.8.90-r1/work/amarok-2.8.90/src/core-impl/playlists/types/file/xspf/XSPFPlaylist.cpp:104:33:
error: 'Playlists::Playlist::ModelStack' has not been declared

Expected Results:  
Successful merge

KDE Frameworks 5.21.0
Qt 5.6.0

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

[kopete] [Bug 363053] Building kopete-16.04.0 with GCC-6.1.0 fails with "error: could not convert 'false' from 'bool' to 'const Kopete::MetaContact*'"

[via KDE Bugzilla]

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

--- Comment #1 from nsane...@gmail.com ---
Created attachment 98951
  --> https://bugs.kde.org/attachment.cgi?id=98951=edit
kopete-16.04.0-gcc6.patch

Changes "const Kopete::MetaContact *c=false" to "const Kopete::MetaContact
*c=nullptr".

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

[kopete] [Bug 363053] Building kopete-16.04.0 with GCC-6.1.0 fails with "error: could not convert 'false' from 'bool' to 'const Kopete::MetaContact*'"

[via KDE Bugzilla]

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

nsane...@gmail.com changed:

   What|Removed |Added

 CC||nsane...@gmail.com

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

[kopete] [Bug 363053] New: Building kopete-16.04.0 with GCC-6.1.0 fails with "error: could not convert 'false' from 'bool' to 'const Kopete::MetaContact*'"

[via KDE Bugzilla]

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

Bug ID: 363053
   Summary: Building kopete-16.04.0 with GCC-6.1.0 fails with
"error: could not convert 'false' from 'bool' to
'const Kopete::MetaContact*'"
   Product: kopete
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: History Plugin
  Assignee: kopete-bugs-n...@kde.org
  Reporter: nsane...@gmail.com

Building kopete-16.04.0 with GCC-6.1.0 fails with:

In file included from
/var/tmp/portage/kde-apps/kopete-16.04.0/work/kopete-16.04.0/plugins/history2/history2logger.cpp:19:0:
/var/tmp/portage/kde-apps/kopete-16.04.0/work/kopete-16.04.0/plugins/history2/history2logger.h:97:81:
error: could not convert 'false' from 'bool' to 'const Kopete::MetaContact*'
  int offset=0, const Kopete::MetaContact
*c=false, bool reverseOrder=true);


With gcc-6, only integer literals can be used as null pointer constants (see
https://gcc.gnu.org/gcc-6/porting_to.html).

Reproducible: Always

Steps to Reproduce:
1. emerge -p =kde-apps/kopete-16.04.0


Actual Results:  
In file included from
/var/tmp/portage/kde-apps/kopete-16.04.0/work/kopete-16.04.0/plugins/history2/history2logger.cpp:19:0:
/var/tmp/portage/kde-apps/kopete-16.04.0/work/kopete-16.04.0/plugins/history2/history2logger.h:97:81:
error: could not convert 'false' from 'bool' to 'const Kopete::MetaContact*'
  int offset=0, const Kopete::MetaContact
*c=false, bool reverseOrder=true);

Expected Results:  
Successful merge

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

[phonon-backend-gstreamer] [Bug 334421] amarok will increase the memory usage after long time music switch

[TOM Harrison via KDE Bugzilla]

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

--- Comment #11 from TOM Harrison  ---
by the way, after I update to 4.8.3. it still happened.

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

[plasmashell] [Bug 358719] fcitx creates blank unusable xembed icon in systray

[Arfrever Frehtes Taifersar Arahesis via KDE Bugzilla]

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

--- Comment #11 from Arfrever Frehtes Taifersar Arahesis 
 ---
(In reply to Sergio from comment #10)
> Similar issue on Kubuntu 16.04, that ships with plasma 5.5.5. Hence plasma
> 5.5 does not solve the issue.

Fix is in plasma-workspace >=5.6.0 and was never backported to "Plasma/5.5"
branch in plasma-workspace repository.

Upgrade to KDE Plasma 5.6.*. If KDE Plasma 5.6.* is not yet available in
Kubuntu, then ask KDE maintainers in Kubuntu to add KDE Plasma 5.6.* or to
backport this fix to 5.5.*:
https://quickgit.kde.org/?p=plasma-workspace.git=commit=829158f830555c031755c6d4348e684779264342

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

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Ben Cooksley via KDE Bugzilla]

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

--- Comment #41 from Ben Cooksley  ---
Adding custom code will still add a maintenance burden, especially as our
database schema will differ from upstream. It will also create unexpected
behaviour and create a support burden.

We won't be changing the behaviour of Bugzilla in this regard.

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

[frameworks-kconfig] [Bug 363052] New: while compiling with cmake ARM version of kconfig_compiler is executed instead of the one built for the host platform

[Artem Fedoskin via KDE Bugzilla]

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

Bug ID: 363052
   Summary: while compiling with cmake ARM version of
kconfig_compiler is executed instead of the one built
for the host platform
   Product: frameworks-kconfig
   Version: unspecified
  Platform: Android
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matt...@mjdsystems.ca
  Reporter: afedosk...@gmail.com
CC: kdelibs-b...@kde.org

I don't know whether this is a problem or a feature - When I compile
my app for Android and use KConfig compiled for Android the ARM version
of kconfig_compiler is executed to build options class. I had to change
kconfig_compiler executable compiled for Android with the one compiled for
my system to build options class. Can I somehow specify to CMake that I
need kconfig_compiler built for my system, not Android one and at the same time
use Android version of KConfig?

Reproducible: Always

Steps to Reproduce:
1. Compile KF5 for Android
2. Link KConfig in your CMakeText.txt

Actual Results:  
While compiling the options class ARM version of kconfig_compiler will be
called

Expected Results:  
kconfig_compiler version for host platform should be called

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

[kde] [Bug 363051] New: Kcolorchooser freeze DE

[varlesh via KDE Bugzilla]

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

Bug ID: 363051
   Summary: Kcolorchooser freeze DE
   Product: kde
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: varl...@gmail.com

New KF5-version kcolorchooser freeze plasmashell or krunner.
Only xkill to kcolorchooser temporary solved problem.
archlinux x86_64
kcolorchooser 16.04.1
plasma-desktop 5.6.4

Reproducible: Always

Steps to Reproduce:
Krunner
1. run kcolorchooser from krunner
2. krunner freezed

Plasmashell
1. run kcolorchooser from task widgets (icons only)
2. plasmashell freezed

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

[partitionmanager] [Bug 363050] New: Respect minCapacity when creating new filesystems in small unformatted partitions

[Andrius Štikonas via KDE Bugzilla]

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

Bug ID: 363050
   Summary: Respect minCapacity when creating new filesystems in
small unformatted partitions
   Product: partitionmanager
   Version: Git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: andr...@stikonas.eu
  Reporter: andr...@stikonas.eu

Respect minCapacity when creating new filesystems in small unformatted
partitions.

E.g. similar checks to ones for reformating partitions should be made.

Reproducible: Always

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

[Baloo] [Bug 363049] New: Baloo Crash

[Marcelo Zoel via KDE Bugzilla]

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

Bug ID: 363049
   Summary: Baloo Crash
   Product: Baloo
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: m...@vhanda.in
  Reporter: marcelo.z...@gmail.com
CC: pinak.ah...@gmail.com

Application: baloo_file (5.18.0)

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

-- Information about the crash:
I use Insync to syncs my local folders to google drive, after stop of program,
the baloo crashed too.

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

Thread 2 (Thread 0x7fb5899a6700 (LWP 15566)):
[KCrash Handler]
#6  QVector::reallocData (this=0x7fb5899a5aa0,
asize=-93309732, aalloc=, options=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:514
#7  0x7fb6d3c50896 in QVector::resize (asize=, this=0x7fb5899a5aa0) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:386
#8  Baloo::PostingCodec::decode (this=this@entry=0x7fb5899a59ef, arr=...) at
../../../src/codecs/postingcodec.cpp:40
#9  0x7fb6d3c3c814 in Baloo::PostingDB::get
(this=this@entry=0x7fb5899a5ad0, term=...) at
../../../src/engine/postingdb.cpp:100
#10 0x7fb6d3c4d3c6 in Baloo::WriteTransaction::commit (this=) at ../../../src/engine/writetransaction.cpp:277
#11 0x7fb6d3c45032 in Baloo::Transaction::commit
(this=this@entry=0x7fb5899a5bd0) at ../../../src/engine/transaction.cpp:262
#12 0x0041c8e0 in Baloo::NewFileIndexer::run (this=0x1598240) at
../../../src/file/newfileindexer.cpp:75
#13 0x7fb6d3563343 in QThreadPoolThread::run (this=0x1591e40) at
thread/qthreadpool.cpp:93
#14 0x7fb6d356684e in QThreadPrivate::start (arg=0x1591e40) at
thread/qthread_unix.cpp:331
#15 0x7fb6d21ca6fa in start_thread (arg=0x7fb5899a6700) at
pthread_create.c:333
#16 0x7fb6d2b73b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fb6d4a618c0 (LWP 7012)):
#0  0x7fb6d2b639cd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fb6cfd7c6c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb6cfd38e04 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb6cfd392c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fb6cfd3942c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fb6d379da9b in QEventDispatcherGlib::processEvents (this=0x149b790,
flags=...) at kernel/qeventdispatcher_glib.cpp:420
#6  0x7fb6d3744dea in QEventLoop::exec (this=this@entry=0x7ffdf5d5e950,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7fb6d374ce8c in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1229
#8  0x0041698c in main (argc=1, argv=) at
../../../src/file/main.cpp:88

Possible duplicates by query: bug 356445.

Reported using DrKonqi

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

[kscreenlocker] [Bug 353440] Can't unlock session - password is always wrong

[David Faure via KDE Bugzilla]

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

David Faure  changed:

   What|Removed |Added

 CC||fa...@kde.org

--- Comment #3 from David Faure  ---
For the record, on OpenSuSE, making kcheckpass suid root is not enough, one
should also make sure to compile kscreenlocker and plasma-workspace with the
cmake options
-DKDE4_COMMON_PAM_SERVICE=xdm -DKDE4_KCHECKPASS_PAM_SERVICE=xdm
(yes, "KDE4", even in the KF5 version)

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

[kopete] [Bug 356326] Code in kdenetwork is licensed under the non-free ARTISTIC license.

[Dennis Worthem via KDE Bugzilla]

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

--- Comment #15 from Dennis Worthem  ---
So what exactly was the change?

Thanks

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

[kio-extras] [Bug 363048] New: transaction error while updating kio-extras with apper

[Phil via KDE Bugzilla]

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

Bug ID: 363048
   Summary: transaction error while updating kio-extras with apper
   Product: kio-extras
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: default
  Assignee: plasma-de...@kde.org
  Reporter: val...@astro.umontreal.ca

Below is the message displayed by apper.  

Error running transaction: file
/usr/lib64/qt5/plugins/kactivitymanagerd_fileitem_linking_plugin.so from
install of kio-extras-16.04.0-1.fc23.x86_64 conflicts with file from
kactivities-workspace-5.5.0-3.fc23.x86_64
file /usr/lib64/qt5/plugins/kio_activities.so from install of
kio-extras-16.04.0-1.fc23.x86_64 conflicts with file from
kactivities-workspace-5.5.0-3.fc23.x86_64
file /usr/share/kservices5/kactivitymanagerd_fileitem_linking_plugin.desktop
from install of kio-extras-16.04.0-1.fc23.x86_64 conflicts with file from
kactivities-workspace-5.5.0-3.fc23.x86_64

Reproducible: Always

Steps to Reproduce:
1.Run apper
2.Select to update kio-extras  
3.fail and return error message

Actual Results:  
Failed

Expected Results:  
should succeed !

Using fedora 23

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

[kwin] [Bug 322975] desktop render will twisted when the opengl application is closed.

[Rick W . Chen via KDE Bugzilla]

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

Rick W. Chen  changed:

   What|Removed |Added

 CC|stuffcor...@archlinux.us|

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

[kdenlive] [Bug 362918] Timeline - Track mismatch when moving selected clips

[Daniel Klein via KDE Bugzilla]

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

Daniel Klein  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #6 from Daniel Klein  ---
The fix has also resolved some other issues, with dragging several selected
clips (had some "track mismatch" crushes sometimes). Nice. Much appreciated.

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

[plasmashell] [Bug 363047] New: Crash on login

[Kevin Coonan via KDE Bugzilla]

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

Bug ID: 363047
   Summary: Crash on login
   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: kevin.coo...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

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

-- Information about the crash:
- What I was doing when the application crashed: Just logged in to system.  Has
been doing this since installation.  Have tried to consolidate KDE applications
into a single repo, but there is no clear guidance on which version of KDE
applications should be installed.  The transition KDE4-KDE5 is NOT GOING WELL
from a user perspective.  Where is the documentation that would tell me which
packages should be installed to create a working desktop w/ Plasma5, etc.?  Why
is the menu structure (when it actually shows up, rather than blank black
screen) all messed up?  Why is it so hard to actually run KDE?!?

The crash can be reproduced every time.

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

Thread 9 (Thread 0x7f514a5ca700 (LWP 2730)):
#0  0x7f515b2cdbbd in poll () at /lib64/libc.so.6
#1  0x7f5160221422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f516022300f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f514cd4d3c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f515b9c832f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f5156df0754 in  () at /usr/X11R6/lib64/libGL.so.1
#6  0x7f515aad70a4 in start_thread () at /lib64/libpthread.so.0
#7  0x7f515b2d5fed in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f51433ea700 (LWP 2737)):
#0  0x7f515b2cdbbd in poll () at /lib64/libc.so.6
#1  0x7f51579a8e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f51579a8f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f515bbfad8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f515bba1d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f515b9c361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f515ecd7e18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f515b9c832f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f5156df0754 in  () at /usr/X11R6/lib64/libGL.so.1
#9  0x7f515aad70a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f515b2d5fed in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f513635e700 (LWP 2738)):
#0  0x7f515b2cdbbd in poll () at /lib64/libc.so.6
#1  0x7f51579a8e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f51579a8f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f515bbfad8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f515bba1d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f515b9c361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f515ecd7e18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f515b9c832f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f5156df0754 in  () at /usr/X11R6/lib64/libGL.so.1
#9  0x7f515aad70a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f515b2d5fed in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f5134bb2700 (LWP 2739)):
#0  0x7f515b2cdbbd in poll () at /lib64/libc.so.6
#1  0x7f51579a8e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f51579a8f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f515bbfad8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f515bba1d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f515b9c361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f515ecd7e18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f515b9c832f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f5156df0754 in  () at /usr/X11R6/lib64/libGL.so.1
#9  0x7f515aad70a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f515b2d5fed in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f512f1cf700 (LWP 2740)):
#0  0x7f515aadb03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f51614a686b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f51614a6899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f5156df0754 in  () at /usr/X11R6/lib64/libGL.so.1
#4  0x7f515aad70a4 in start_thread () at /lib64/libpthread.so.0
#5  0x7f515b2d5fed in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f50a7fff700 (LWP 2757)):
#0  

[frameworks-kdeclarative] [Bug 337579] QMLObject::createObjectFromComponent leaks when parent is set in properties.

[harun via KDE Bugzilla]

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

harun  changed:

   What|Removed |Added

 CC||ipekha...@hotmail.com

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

[kwin] [Bug 361236] Kwin crashes when trying to open configurations of the system tray

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

 CC||7x2p...@gmail.com

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

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

[ksplash] [Bug 357170] plasmashell loaded longer than ksplash

[harun via KDE Bugzilla]

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

--- Comment #1 from harun  ---
(In reply to Roman from comment #0)
> When I start plasma, I see ksplash, but when it dissapear I see that plasma
> still downloading(black screen, then wallpaper and widgets). When I start
> plasma with openbox, I have another issue - ksplash loading is longer than
> should be.
> 
> Reproducible: Always
> 
> 
> 
> 
> .xserver-errors
> startkde: Starting up...
> Service started, version: 6.2.0
> Baloo File Indexing has been disabled
> Не вдається відкрити бібліотеку «/usr/lib/libkdeinit5_lib/kdeconnectd».
> Cannot load library /usr/lib/libkdeinit5_lib/kdeconnectd:
> (/usr/lib/libkdeinit5_lib/libkdeconnectd.so: не вдалося відкрити файл
> об’єктів спільного використання: Немає такого файла або каталогу)
> OpenGL vendor string:   NVIDIA Corporation
> OpenGL renderer string: GeForce GT 740/PCIe/SSE2
> OpenGL version string:  4.5.0 NVIDIA 358.16
> OpenGL shading language version string: 4.50 NVIDIA
> Driver: NVIDIA
> Driver version: 358.16
> GPU class:  Unknown
> OpenGL version: 4.5
> GLSL version:   4.50
> X server version:   1.18
> Linux kernel version:   4.2.5
> Requires strict binding:no
> GLSL shaders:   yes
> Texture NPOT support:   yes
> Virtual Machine:no
> kscreen: Primary output changed from KScreen::Output(Id: 638 , Name: "VGA-0"
> ) ( "VGA-0" ) to KScreen::Output(Id: 638 , Name: "VGA-0" ) ( "VGA-0" )
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> unversioned plugin detected, may result in instability
> last screen is < 0 so putting containment on screen  0
> QDBusConnection: session D-Bus connection created before QCoreApplication.
> Application may misbehave.
> QDBusConnection: session D-Bus connection created before QCoreApplication.
> Application may misbehave.
> No metadata file in the package, expected it at:
> "/home/bugworm/Картинки//metadata.desktop"
> No metadata file in the package, expected it at:
> "/home/bugworm/Картинки//metadata.desktop"
> No metadata file in the package, expected it at:
> "/home/bugworm/Картинки//metadata.desktop"
> kscreen: Primary output changed from KScreen::Output(Id: 638 , Name: "VGA-0"
> ) ( "VGA-0" ) to KScreen::Output(Id: 638 , Name: "VGA-0" ) ( "VGA-0" )
> Connecting to deprecated signal
> QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
> QDBusConnection: session D-Bus connection created before QCoreApplication.
> Application may misbehave.
> QDBusConnection: session D-Bus connection created before QCoreApplication.
> Application may misbehave.
> kbuildsycoca4 running...
> yakuake(2611)/kdecore (KLibrary) findLibraryInternal: plugins should not
> have a 'lib' prefix: "libkonsolepart.so"
> qml: Reading townStrings from configuration:
> [{"placeAlias":"Dniprodzerzhyns’k","townString":"Ukraina/Dnipropetrovsk/
> Dniprodzerzhyns’k"}]
> QDBusConnection: session D-Bus connection created before QCoreApplication.
> Application may misbehave.
> yakuake(2611)/konsole Konsole::Session::run: Attempted to re-run an already
> running session. 
> QDBusConnection: session D-Bus connection created before QCoreApplication.
> Application may 

[ksplash] [Bug 357170] plasmashell loaded longer than ksplash

[harun via KDE Bugzilla]

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

harun  changed:

   What|Removed |Added

 CC||ipekha...@hotmail.com

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

[kmail2] [Bug 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook

[Gerhard Lehnhoff via KDE Bugzilla]

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

--- Comment #39 from Gerhard Lehnhoff  ---
I installed "libkf5akonadisearch-bin" on Kubuntu 15.10. Address Completion
works, also after upgrade to 16.04.



I installed "libkf5akonadisearch-bin" on Kubuntu 15.10. Address Completion
works now! Success. Thanks to Andreas T. . (In reply to Andreas T from comment
#30) > I'm on a Kubuntu 16.04 installation (upgraded from 15.04)
> 
> I can confirm that installing libkf5akonadisearch-bin brings back the
> auto-completion for contacts in KAdressbook; the completion of recent
> addresses also works. For the completion to start, it is required to enter
> something in the recipient field and backspace to the beginning.
> 
> In my case, it was not required to uninstall baloo or trigger a reindex of
> PIM data.
> 
> Is someone else affected by this bug, ...
> a) who is not using Kubuntu.
> b) for whom installing libkf5akonadisearch-bin does not bring back the
> autocompletion?

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

[kshisen] [Bug 363038] create solvable games only causes crash

[Frederik Schwarzer via KDE Bugzilla]

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

Frederik Schwarzer  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kshi
   ||sen/0ab163a847db3b37b983f93
   ||41cccaf243acfd95c
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Frederik Schwarzer  ---
Git commit 0ab163a847db3b37b983f9341cccaf243acfd95c by Frederik Schwarzer.
Committed on 13/05/2016 at 21:04.
Pushed by schwarzer into branch 'Applications/16.04'.

Initialize vectors with correct size.

M  +2-2src/board.cpp
M  +1-1src/main.cpp

http://commits.kde.org/kshisen/0ab163a847db3b37b983f9341cccaf243acfd95c

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

[kshisen] [Bug 363038] create solvable games only causes crash

[Frederik Schwarzer via KDE Bugzilla]

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

--- Comment #2 from Frederik Schwarzer  ---
Found the issue, hopefully fixed the issue. :)

Thanks for the report.

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

[kdevelop] [Bug 363044] New: Crash when parsing javascript/python files

[Jonathan Verner via KDE Bugzilla]

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

Bug ID: 363044
   Summary: Crash when parsing javascript/python files
   Product: kdevelop
   Version: 4.7.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: jonathan.ver...@gmail.com

Application: kdevelop (4.7.0)
KDE Platform Version: 4.14.13
Qt Version: 4.8.6
Operating System: Linux 3.16.0-70-generic x86_64
Distribution: Ubuntu 14.04.4 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Editing a project including Brython and several other javascript libraries
(Angular 2, Prime NG, ...)

The crash can be reproduced every time.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f232d0037c0 (LWP 30216))]

Thread 24 (Thread 0x7f231041c700 (LWP 30217)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f2325f47ffb in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x7f2325f48039 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x7f2328b2a182 in start_thread (arg=0x7f231041c700) at
pthread_create.c:312
#4  0x7f23297cd47d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 23 (Thread 0x7f228f018700 (LWP 30218)):
#0  __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:63
#1  0x7f232395d981 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f232391b1f8 in g_main_context_release () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f232391bf91 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f232391c0ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f2329f467be in QEventDispatcherGlib::processEvents
(this=0x7f22880008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#6  0x7f2329f180af in QEventLoop::processEvents
(this=this@entry=0x7f228f017de0, flags=...) at kernel/qeventloop.cpp:149
#7  0x7f2329f183a5 in QEventLoop::exec (this=this@entry=0x7f228f017de0,
flags=...) at kernel/qeventloop.cpp:204
#8  0x7f2329e14c5f in QThread::exec (this=this@entry=0x16c6a00) at
thread/qthread.cpp:537
#9  0x7f2329ef9823 in QInotifyFileSystemWatcherEngine::run (this=0x16c6a00)
at io/qfilesystemwatcher_inotify.cpp:265
#10 0x7f2329e1732f in QThreadPrivate::start (arg=0x16c6a00) at
thread/qthread_unix.cpp:349
#11 0x7f2328b2a182 in start_thread (arg=0x7f228f018700) at
pthread_create.c:312
#12 0x7f23297cd47d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 22 (Thread 0x7f227fe64700 (LWP 30219)):
#0  0x7f2329793f3d in nanosleep () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f23297c54a4 in usleep (useconds=) at
../sysdeps/unix/sysv/linux/usleep.c:32
#2  0x7f23269e281a in KDevelop::DUChainLock::lockForWrite(unsigned int) ()
from /usr/lib/libkdevplatformlanguage.so.8
#3  0x7f23269e29ec in KDevelop::DUChainWriteLocker::lock() () from
/usr/lib/libkdevplatformlanguage.so.8
#4  0x7f23269a814e in ?? () from /usr/lib/libkdevplatformlanguage.so.8
#5  0x7f23269a9228 in ?? () from /usr/lib/libkdevplatformlanguage.so.8
#6  0x7f2329e1732f in QThreadPrivate::start (arg=0x3234850) at
thread/qthread_unix.cpp:349
#7  0x7f2328b2a182 in start_thread (arg=0x7f227fe64700) at
pthread_create.c:312
#8  0x7f23297cd47d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 21 (Thread 0x7f2277866700 (LWP 30220)):
#0  0x7f2323941390 in g_thread_self () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f232391c0dd in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f2329f467be in QEventDispatcherGlib::processEvents
(this=0x7f2278c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#3  0x7f2329f180af in QEventLoop::processEvents
(this=this@entry=0x7f2277865e20, flags=...) at kernel/qeventloop.cpp:149
#4  0x7f2329f183a5 in QEventLoop::exec (this=this@entry=0x7f2277865e20,
flags=...) at kernel/qeventloop.cpp:204
#5  0x7f2329e14c5f in QThread::exec (this=) at
thread/qthread.cpp:537
#6  0x7f2329e1732f in QThreadPrivate::start (arg=0x3b90bd8) at
thread/qthread_unix.cpp:349
#7  0x7f2328b2a182 in start_thread (arg=0x7f2277866700) at
pthread_create.c:312
#8  0x7f23297cd47d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 20 (Thread 0x7f22650d5700 (LWP 30224)):
#0  0x7f232395d61a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f232395d979 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f232391b699 in g_main_context_prepare () from

[krita] [Bug 363043] Can't use shortcuts for canvas inputs after using the layers docker

[Tricia via KDE Bugzilla]

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

Tricia  changed:

   What|Removed |Added

URL|https://dl.dropboxuserconte |
   |nt.com/u/18554685/TabletLog |
   |.LOG|

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

[krita] [Bug 363043] Can't use shortcuts for canvas inputs after using the layers docker

[Tricia via KDE Bugzilla]

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

--- Comment #1 from Tricia  ---
Created attachment 98950
  --> https://bugs.kde.org/attachment.cgi?id=98950=edit
tabletlog

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

[krita] [Bug 363019] Krita doesn't open Canon raw files (CR2)

[Sven Claussner via KDE Bugzilla]

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

--- Comment #5 from Sven Claussner  ---
I investigated a bit and a look at the console output gave me some insights.
On opening the File/Open dialog, a long list of file format messages is printed
out, among them:

mimeType "image/x-krita-raw" seen false swap extension order false
description: "Camera Raw Files"
patterns: ("*.nef", "*.cr2", "*.sr2", "*.crw", "*.pef", "*.x3f",
"*.kdc", "*.mrw", "*.arw", "*.k25", "*.dcr", "*.orf", "*.raw", "*.raw",
"*.raf", "*.srf", "*.dng")
>>> "Camera Raw Files ( *.nef *.cr2 *.sr2 *.crw *.pef *.x3f 
>>> *.kdc *.mrw *.arw *.k25 *.dcr *.orf *.raw *.raw *.raf *.srf 
>>> *.dng )"

On trying to open a CR2 file, Krita prints: 
krita.file: Couldn't create a valid graph for this source mimetype: 
"image/x-canon-cr2"

Checking at system level (at least in KDE), the CR2 files are associated to
another mime type than Krita expects.
To prove this I added the new mime type "image/x-krita-raw" at system level and
assigned the imaginary CR3 file extension to it. Then I renamed a CR2 file to
CR3 and opened it in Dolphin with the Krita AppImage - et voila: Krita opens it
in full size!

Here are the correct mime types I got from the KDE file association tool:
NEF: image/x-nikon-nef
CR2: image/x-canon-cr2 
SR2: image/x-sony-sr2
CRW: image/x-canon-crw
x3f: image/x-sigma-x3f
kdc:image/x-kodak-kdc
mrw:image/x-minolta-mrw
arw:image/x-sony-arw
k25:image/x-kodak-k25
dcr:image/x-kodak-dcr 
orf:image/x-olympus-orf
raw:image/x-panasonic-raw
*.raw is a duplicate. Perhaps you meant *.rw2, which is image/x-panasonic-raw2
?
raf:image/x-fuji-raf
srf:image/x-sony-srf
dng:image/x-adobe-dng

Tldr; : assigning the raw formats properly to their corresponding mime type
should fix it.

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

[krita] [Bug 363043] New: Can't use shortcuts for canvas inputs after using the layers docker

[Tricia via KDE Bugzilla]

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

Bug ID: 363043
   Summary: Can't use shortcuts for canvas inputs after using the
layers docker
   Product: krita
   Version: 3.0 Beta
  Platform: Windows CE
   URL: https://dl.dropboxusercontent.com/u/18554685/TabletLog
.LOG
OS: MS Windows
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: shortcuts
  Assignee: krita-bugs-n...@kde.org
  Reporter: triciacunning...@live.com

After using the layers docker to switch layers, hide layers, or anything like
that, I can't use any canvas input shortcuts such as pan, rotate, or zoom
without first clicking into the canvas or using the scroll bars. 

Reproducible: Always

Steps to Reproduce:
1. Create new canvas
2. Select a different layer
3. Try to zoom or pan

Actual Results:  
Canvas won't react. If trying to pan, I'll just draw a stroke on the canvas,
need to undo, and then be able to pan using my shortcut. 


I am running Windows 7 and using a Wacom Cintiq 24 HD. I was not having this
behavior in the last release.

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

[kdenlive] [Bug 363036] git master: Timeline zone bar issues

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #1 from Jean-Baptiste Mardelle  ---
Git commit 34ebac2d1864596480d99f786be9ecf1b53f83c2 by Jean-Baptiste Mardelle.
Committed on 13/05/2016 at 20:25.
Pushed by mardelle into branch 'master'.

Fix unable to select 1 frame in timeline zone

M  +1-1src/monitor/smallruler.cpp
M  +5-5src/timeline/customruler.cpp
M  +6-2src/timeline/customtrackview.cpp

http://commits.kde.org/kdenlive/34ebac2d1864596480d99f786be9ecf1b53f83c2

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

[plasmashell] [Bug 362105] Taskbar options 'autohide'/'windows can cover' not functional

[Daniel via KDE Bugzilla]

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

Daniel  changed:

   What|Removed |Added

 CC||dpcas...@gmail.com

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

[ksplash] [Bug 363042] New: Splash screen frozen for ~20-30 seconds

[Natenom via KDE Bugzilla]

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

Bug ID: 363042
   Summary: Splash screen frozen for ~20-30 seconds
   Product: ksplash
   Version: 5.6.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: l.lu...@kde.org
  Reporter: nate...@googlemail.com

When the default splash screen "Breeze" is chosen in systemsettings and you
login the progress bar in the splash screen loads to 100% and then freezes for
~20-30 seconds before you can see the desktop.

In the error log when starting KDE plasma 5 from the console you can see:
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/splash/Splash.qml:
50:13: QML Image: Binding loop detected for property „sourceSize.width“.

Removing the line does not help.

Setting the splash screen to "None" solves this issue.

Reproducible: Always

Steps to Reproduce:
1. Select "Breeze" splash screen (which is default)
2. Logout.
3. Login or start it with startkde

Actual Results:  
Hangs at 100%.

Expected Results:  
Splash screen should disappear when progress bar reached 100%.

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

[kdenlive] [Bug 363033] git master: double clicking a track title does not set input focus to title input field, only selects it.

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #1 from Jean-Baptiste Mardelle  ---
Git commit 8a8a4edf2d08730a9285322b7fa67e97cc328d20 by Jean-Baptiste Mardelle.
Committed on 13/05/2016 at 19:32.
Pushed by mardelle into branch 'master'.

Properly focus track name on double click

M  +2-0src/timeline/headertrack.cpp

http://commits.kde.org/kdenlive/8a8a4edf2d08730a9285322b7fa67e97cc328d20

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

[kwin] [Bug 362994] middle click to close, in titlebar -passes click to whatever below

[Allan via KDE Bugzilla]

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

--- Comment #12 from Allan  ---
(In reply to Thomas Lübking from comment #11)
> You cam make xev listen to other windows (just won't help in case this is
> related to some pointer grab):
> 
>xev -event mouse -id 

You're right - that gave nothing.

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

[kwin] [Bug 362994] middle click to close, in titlebar -passes click to whatever below

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #11 from Thomas Lübking  ---
You cam make xev listen to other windows (just won't help in case this is
related to some pointer grab):

   xev -event mouse -id 

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

[kmail2] [Bug 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook

[Gerhard Lehnhoff via KDE Bugzilla]

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

--- Comment #38 from Gerhard Lehnhoff  ---
I installed "libkf5akonadisearch-bin" on Kubuntu 15.10. Address Completion
works now!

Success. Thanks to Andreas T.




. (In reply to Andreas T from comment #30)
> I'm on a Kubuntu 16.04 installation (upgraded from 15.04)
> 
> I can confirm that installing libkf5akonadisearch-bin brings back the
> auto-completion for contacts in KAdressbook; the completion of recent
> addresses also works. For the completion to start, it is required to enter
> something in the recipient field and backspace to the beginning.
> 
> In my case, it was not required to uninstall baloo or trigger a reindex of
> PIM data.
> 
> Is someone else affected by this bug, ...
> a) who is not using Kubuntu.
> b) for whom installing libkf5akonadisearch-bin does not bring back the
> autocompletion?

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

[krita] [Bug 363039] Clicking on the import resource (folder icon) button to import a palette crashes Krita

[wolthera via KDE Bugzilla]

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

--- Comment #4 from wolthera  ---
On top of that, the Brush-tips can only import SVGs and the pattern docker only
BMPs.

paintoppresets is fine.

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

[kdenlive] [Bug 358185] Kdenlive-git - Title editor, shows greenish overlay after clicking "Show Background", but only the first time.

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #6 from Jean-Baptiste Mardelle  ---
Git commit c7cb56eb5192d230de6b4bcb7d21346f7c0ae4e4 by Jean-Baptiste Mardelle.
Committed on 13/05/2016 at 19:19.
Pushed by mardelle into branch 'master'.

Fix green background image in titler

M  +1-1src/monitor/glwidget.cpp

http://commits.kde.org/kdenlive/c7cb56eb5192d230de6b4bcb7d21346f7c0ae4e4

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

[krita] [Bug 363039] Clicking on the import resource (folder icon) button to import a palette crashes Krita

[wolthera via KDE Bugzilla]

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

--- Comment #3 from wolthera  ---
This also happens with the Gradient and Workspace dockers. Brush-tips, patterns
and paintoppresets work fine.

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

[krita] [Bug 363039] opening a palette crashes the program

[Raghavendra kamath via KDE Bugzilla]

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

Raghavendra kamath  changed:

   What|Removed |Added

 CC||raghavendr.ra...@gmail.com

--- Comment #2 from Raghavendra kamath  ---
I can reproduce this too on arch linux.

pressing the file browsing icon in the palette import section crashes krita.

I got the following back-trace from Dr. konqi


Application: krita (krita), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5f554c1840 (LWP 13087))]

Thread 5 (Thread 0x7f5f33af3700 (LWP 13089)):
#0  0x7f5f4da27339 in QMutex::unlock() () from /usr/lib/libQt5Core.so.5
#1  0x7f5f4dc5ad91 in ?? () from /usr/lib/libQt5Core.so.5
#2  0x7f5f4824b68d in g_main_context_prepare () from
/usr/lib/libglib-2.0.so.0
#3  0x7f5f4824c02b in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x7f5f4824c20c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#5  0x7f5f4dc5b6eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#6  0x7f5f4dc0346a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#7  0x7f5f4da2a2f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#8  0x7f5f49068a65 in ?? () from /usr/lib/libQt5DBus.so.5
#9  0x7f5f4da2f1d8 in ?? () from /usr/lib/libQt5Core.so.5
#10 0x7f5f4971a474 in start_thread () from /usr/lib/libpthread.so.0
#11 0x7f5f4ce2969d in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7f5f1e2a2700 (LWP 13090)):
#0  0x7f5f4972009f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f5f4da3008b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f5f4da28d53 in QSemaphore::acquire(int) () from
/usr/lib/libQt5Core.so.5
#3  0x7f5f540549fd in KisTileDataPooler::waitForWork (this=0x7f5f54530b60
<(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>) at
/home/raghu/kf5/src/krita/libs/image/tiles3/kis_tile_data_pooler.cc:165
#4  KisTileDataPooler::run (this=0x7f5f54530b60 <(anonymous
namespace)::Q_QGS_s_instance::innerFunction()::holder>) at
/home/raghu/kf5/src/krita/libs/image/tiles3/kis_tile_data_pooler.cc:187
#5  0x7f5f4da2f1d8 in ?? () from /usr/lib/libQt5Core.so.5
#6  0x7f5f4971a474 in start_thread () from /usr/lib/libpthread.so.0
#7  0x7f5f4ce2969d in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7f5f1daa1700 (LWP 13091)):
#0  0x7f5f4972009f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f5f4da3008b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f5f4da29046 in QSemaphore::tryAcquire(int, int) () from
/usr/lib/libQt5Core.so.5
#3  0x7f5f54070023 in KisTileDataSwapper::waitForWork (this=) at
/home/raghu/kf5/src/krita/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:86
#4  0x7f5f5407022a in KisTileDataSwapper::run (this=0x7f5f54530ba0
<(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder+64>) at
/home/raghu/kf5/src/krita/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:92
#5  0x7f5f4da2f1d8 in ?? () from /usr/lib/libQt5Core.so.5
#6  0x7f5f4971a474 in start_thread () from /usr/lib/libpthread.so.0
#7  0x7f5f4ce2969d in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f5f1d2a0700 (LWP 13092)):
#0  0x7f5f4972009f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f5f4da3008b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f5f4eb5f139 in ?? () from /usr/lib/libQt5Widgets.so.5
#3  0x7f5f4da2f1d8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7f5f4971a474 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f5f4ce2969d in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f5f554c1840 (LWP 13087)):
[KCrash Handler]
#5  0x7f5f4db16739 in QDebug::putString(QChar const*, unsigned long) ()
from /usr/lib/libQt5Core.so.5
#6  0x7f5f5102f94c in QDebug::operator<< (t=..., this=0x7ffcaa5ad410) at
/usr/include/qt/QtCore/qdebug.h:140
#7  KoFileDialog::getFilterStringListFromMime (this=this@entry=0x7ffcaa5ad850,
mimeList=..., withAllSupportedEntry=withAllSupportedEntry@entry=true) at
/home/raghu/kf5/src/krita/libs/widgetutils/KoFileDialog.cpp:406
#8  0x7f5f51031d2a in KoFileDialog::setMimeTypeFilters
(this=this@entry=0x7ffcaa5ad850, filterList=..., defaultFilter=...) at
/home/raghu/kf5/src/krita/libs/widgetutils/KoFileDialog.cpp:150
#9  0x7f5f5386ce26 in KoResourceItemChooser::slotButtonClicked
(this=0xa597970, button=) at
/home/raghu/kf5/src/krita/libs/widgets/KoResourceItemChooser.cpp:205
#10 0x7f5f4dc32679 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#11 0x7f5f4ecbb461 in 

[frameworks-kconfig] [Bug 340691] system-wide kdeglobals "overwrite" local ones

[David Faure via KDE Bugzilla]

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

David Faure  changed:

   What|Removed |Added

 CC||fa...@kde.org

--- Comment #9 from David Faure  ---
I can't select another webbrowser than firefox on OpenSuSE because
/etc/xdg/kdeglobals says BrowserApplication=firefox. The use of SimpleConfig
when saving means that writeEntry() with an empty QString does nothing, because
KConfig doesn't see that there is a more-global value to override explicitly.

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

[kdenlive] [Bug 362732] [icon/theme] Missing alignement icons in 'Title Clip' creator

[David REVOY via KDE Bugzilla]

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

David REVOY  changed:

   What|Removed |Added

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

--- Comment #4 from David REVOY  ---
@wegwerf-1-2-3 : thank you for the reminder.

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

[krita] [Bug 363039] Clicking on the import resource (folder icon) button to import a palette crashes Krita

[Raghavendra kamath via KDE Bugzilla]

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

Raghavendra kamath  changed:

   What|Removed |Added

Summary|Clicking one the import |Clicking on the import
   |resource (folder icon)  |resource (folder icon)
   |button to import a palette  |button to import a palette
   |crashes Krita   |crashes Krita

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

[kde] [Bug 363041] New: DBUS system DisplayManager Lock does not work

[via KDE Bugzilla]

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

Bug ID: 363041
   Summary: DBUS system DisplayManager Lock does not work
   Product: kde
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: koffeinfried...@gmail.com

qdbus --system org.freedesktop.DisplayManager
/org/freedesktop/DisplayManager/Seat0 org.freedesktop.DisplayManager.Seat.Lock

This doesn't work in Kubuntu 16.04 as it does in 14.04. It just does nothing.
Not manually triggered nor using QtDbus in C++/Qt-Programs.

I know, the display can be locked with Screensaver-DBUS-Commands, but if
DisplayManager-Lock is not supported, it should just tell it.

Reproducible: Always

Steps to Reproduce:
1. Open terminal
2. enter "qdbus --system org.freedesktop.DisplayManager
/org/freedesktop/DisplayManager/Seat0 org.freedesktop.DisplayManager.Seat.Lock"
3. look sadly :)

Actual Results:  
nothing

Expected Results:  
Expected to lock screen.

I'm using sddm as it is in Kubuntu as default.

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

[krita] [Bug 363019] Krita doesn't open Canon raw files (CR2)

[scl via KDE Bugzilla]

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

scl  changed:

   What|Removed |Added

 OS|OS X|All
   Platform|Mac OS X Disk Images|unspecified

--- Comment #4 from scl  ---
I just tried on Linux (Debian Testing) with the AppImage
(krita-3.0-Beta-master-562442e-x86_64.appimage) and opening CR2 files fails
here, too. Therefore changing the platform values for this report.

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

[krita] [Bug 361709] With more than 1 curve based assistant, zooming in will black screen part or all of the drawing window

[wolthera via KDE Bugzilla]

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

wolthera  changed:

   What|Removed |Added

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

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

[krita] [Bug 363039] opening a palette crashes the program

[wolthera via KDE Bugzilla]

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

wolthera  changed:

   What|Removed |Added

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

--- Comment #1 from wolthera  ---
I can reproduce this, but gdb backtrace it, because of the modal window making
it impossible for me to switch away.

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

[Breeze] [Bug 363040] Requesting icons for Go, Lua, Rust, and Scala

[Justin via KDE Bugzilla]

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

Justin  changed:

   What|Removed |Added

Version|unspecified |5.6.4
   Severity|normal  |wishlist
   Platform|Other   |unspecified
 OS|Linux   |All

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

[Breeze] [Bug 363040] New: Requesting icons for Go, Lua, Rust, and Scala

[Justin via KDE Bugzilla]

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

Bug ID: 363040
   Summary: Requesting icons for Go, Lua, Rust, and Scala
   Product: Breeze
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: mayh...@live.com
CC: kain...@gmail.com

Created attachment 98949
  --> https://bugs.kde.org/attachment.cgi?id=98949=edit
Icons in Dolphin

Breeze currently has icons for most of the popular programming languages, but
there's a few missing that I know would be much appreciated by many developers.

- Go
- Lua
- Rust
- Scala

Additionally, curly-braced CSS preprocessors like Less and SCSS could perhaps
use the CSS icon until one is specifically designed for them. Typescript could
also use JavaScript's icon. They're generic enough to be suitable IMO, and look
better than the default T icon.

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

[kdenlive] [Bug 363036] git master: Timeline zone bar issues

[Massimo Stella via KDE Bugzilla]

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

Massimo Stella  changed:

   What|Removed |Added

Summary|Timeline zone bar issues|git master: Timeline zone
   ||bar issues

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

[kshisen] [Bug 363038] New: create solvable games only causes crash

[Peter Gückel via KDE Bugzilla]

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

Bug ID: 363038
   Summary: create solvable games only causes crash
   Product: kshisen
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: schwar...@kde.org
  Reporter: pguec...@gmail.com
CC: kde-games-b...@kde.org

Version 1.10: kshisen-16.04.1-1.fc24.x86_64

In the program settings, selecting 'create solvable games only' causes program
to crash and it will not restart. The only way to get the program to start
again is to edit out the offending line in ~/.config/kshisenrc.

Reproducible: Always

Steps to Reproduce:
1. select solvable games only
2.
3.

Actual Results:  
crash!

Expected Results:  
previous result: a running program that creates solvable games only

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

[plasma-nm] [Bug 357816] NM applet icon when connected to WiFi & VPN is the same as disconnected

[Abderrahman Najjar via KDE Bugzilla]

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

Abderrahman Najjar  changed:

   What|Removed |Added

   Version Fixed In||5.5.4

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

[plasmashell] [Bug 360293] Improve Task Manager context menu

[Eike Hein via KDE Bugzilla]

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

--- Comment #7 from Eike Hein  ---
Just a heads-up: I'm very reluctant to make any feature/design changes to the
Task Managers in this dev cycle because we're swapping out the entire code (for
the first time in more than a decade), and it's more important to be
regression-free for the moment. Trying to redesign something while you're
rewriting it usually leads to disastrous instability.

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

[plasma-nm] [Bug 363037] New: NM applet icon when connected to WiFi & VPN is the same as disconnected

[Abderrahman Najjar via KDE Bugzilla]

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

Bug ID: 363037
   Summary: NM applet icon when connected to WiFi & VPN is the
same as disconnected
   Product: plasma-nm
   Version: 5.6.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: jgrul...@redhat.com
  Reporter: abderrahman.naj...@gmail.com
CC: lu...@kde.org

This is a regression, same as bug 357816 that I filed a few months ago and was
resolved.

It's the same bug

Reproducible: Always

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

[kdenlive] [Bug 363036] New: Timeline zone bar issues

[Massimo Stella via KDE Bugzilla]

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

Bug ID: 363036
   Summary: Timeline zone bar issues
   Product: kdenlive
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: maxs...@tin.it

You can't just select one frame only as zone length, by the keyboard or by the
mouse, and if you drag the blue bar, for changing its length or for moving it
to another zone of the timeline, this is not correctly shown.

Reproducible: Always

Steps to Reproduce:
1. Set an In point on the timeline then move the editline cursor forward of one
frame and set the Out point.
2.Shrink the timeline zone bar by the mouse.
3.Drag the timeline zone bar by the mouse.

Actual Results:  
You can't create a one frame long  timeline zone bar by the keyboard or by the
mouse.
If you drag or shrink the timeline zone bar by the mouse it's wrongly
represented.

Expected Results:  
The option to select a zone which is one frame long (useful when you works with
still image sequences)
Correct representation of the timeline zone bar when you drag or resize it by
the mouse

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

[plasmashell] [Bug 360297] task manager right click more actions from window decoration

[Eike Hein via KDE Bugzilla]

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

--- Comment #5 from Eike Hein  ---
I actually don't entirely agree with the code comment. Based on a couple of
years of maintaining the Task Manager, I've come to the conclusion that tasks
are not windows, they're an abstraction that is sometimes based on window data
(and in fact based on user demand it's moved more and more away from naively
listing windows and showing window data). As such it's okay for the windows not
to be identical, since they're for different kinds of things. On the other hand
it's of course ok to show some window actions in the menu when a task happens
to relate to a window.

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

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

[alexandre via KDE Bugzilla]

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

Bug ID: 363035
   Summary: Plasma crashed while switching back to mu user session
   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: ale...@cuenca.me
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

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

-- Information about the crash:
- Plasma crashes whenever I switch back to an existing session
- This only happen when I use nvidia G04 drivers. When using G02 drivers, I get
a black screen (only cursor is visible) when switching back to an existing
session. Opensource drivers aren't working for me...

The crash can be reproduced every time.

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

Thread 22 (Thread 0x7fdc237a0700 (LWP 6929)):
#0  0x7fdc33d44bbd in poll () at /lib64/libc.so.6
#1  0x7fdc38c98422 in  () at /usr/lib64/libxcb.so.1
#2  0x7fdc38c9a00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fdc25f233c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fdc3443f32f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fdc3354e0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7fdc33d4cfed in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7fdc1bfff700 (LWP 6930)):
#0  0x7fdc30461d14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fdc3041ef20 in g_main_context_acquire () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fdc3041fd25 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fdc3041ff7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fdc34671d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fdc34618d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fdc3443a61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fdc3774ee18 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7fdc3443f32f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fdc3354e0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7fdc33d4cfed in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7fdc0fd03700 (LWP 6931)):
#0  0x7fdc30461cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fdc3041f028 in g_main_context_release () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fdc3041fe0e in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fdc3041ff7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fdc34671d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fdc34618d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fdc3443a61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fdc3774ee18 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7fdc3443f32f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fdc3354e0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7fdc33d4cfed in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7fdc0dc11700 (LWP 6932)):
#0  0x7fdc30461d14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fdc3041f8e9 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fdc3041fdf8 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fdc3041ff7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fdc34671d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fdc34618d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fdc3443a61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fdc3774ee18 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7fdc3443f32f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fdc3354e0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7fdc33d4cfed in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7fdc07fff700 (LWP 6933)):
#0  0x7fdc3355203f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fdc39f1d86b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7fdc39f1d899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7fdc3354e0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fdc33d4cfed in clone () at /lib64/libc.so.6

Thread 17 (Thread 0x7fdb7700 (LWP 6950)):
#0  0x7fdc33d40c8d in read () at /lib64/libc.so.6
#1  0x7fdc2bee6073 in  () at /usr/lib64/tls/libnvidia-tls.so.361.42
#2  0x7fdc30460b60 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fdc3041f999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fdc3041fdf8 in  () at 

[kdevelop] [Bug 355241] KDevelop crashes when rebuilding project (git clean followed by make) [KDevelop::Path::Path, KDevelop::ProjectBaseItem::path, KDevelop::FileManagerListJob::startNextJob]

[Simon Andric via KDE Bugzilla]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[kde] [Bug 363034] New: Switching activities using keyboard shortcuts

[Alexandre Pereira via KDE Bugzilla]

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

Bug ID: 363034
   Summary: Switching activities using keyboard shortcuts
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: pereira.a...@gmail.com

Application: plasmashell (5.6.90)

Qt Version: 5.6.1
Frameworks Version: 5.22.0
Operating System: Linux 4.5.3-1-default x86_64
Distribution: "openSUSE Tumbleweed (20160511) (x86_64)"

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

I was simply switching activities with keyboard shortcuts ( next activity
shortcut ). The activity switcher sidebar appeared and i noticed that an
activity was missing. Right away plasma crashed.
When restarted, it showed all activities and didn't crashed again.

The crash does not seem to be reproducible.

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

Thread 8 (Thread 0x7ff6e9f37700 (LWP 1803)):
#0  0x7ff6fa0bc07d in poll () at /lib64/libc.so.6
#1  0x7ff6ff0513f2 in  () at /usr/lib64/libxcb.so.1
#2  0x7ff6ff052fc7 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7ff6ec28c559 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7ff6fa7b2f18 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7ff6f98bd424 in start_thread () at /lib64/libpthread.so.0
#6  0x7ff6fa0c4add in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7ff6e3fff700 (LWP 1805)):
#0  0x7ff6fa0b804d in read () at /lib64/libc.so.6
#1  0x7ff6f67a0400 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7ff6f675de94 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ff6f675e308 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7ff6f675e46c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7ff6fa9dc9cb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7ff6fa98534a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7ff6fa7ae104 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7ff6fb7809a5 in  () at /usr/lib64/libQt5DBus.so.5
#9  0x7ff6fa7b2f18 in  () at /usr/lib64/libQt5Core.so.5
#10 0x7ff6f98bd424 in start_thread () at /lib64/libpthread.so.0
#11 0x7ff6fa0c4add in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7ff6e29cb700 (LWP 1835)):
#0  0x7ff6fa0bc07d in poll () at /lib64/libc.so.6
#1  0x7ff6f675e364 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7ff6f675e46c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ff6fa9dc9cb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7ff6fa98534a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7ff6fa7ae104 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7ff6fdb19dc5 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7ff6fa7b2f18 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7ff6f98bd424 in start_thread () at /lib64/libpthread.so.0
#9  0x7ff6fa0c4add in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7ff6e0fc2700 (LWP 1889)):
#0  0x7ff6fa0bc07d in poll () at /lib64/libc.so.6
#1  0x7ff6f675e364 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7ff6f675e46c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ff6fa9dc9cb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7ff6fa98534a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7ff6fa7ae104 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7ff6fdb19dc5 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7ff6fa7b2f18 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7ff6f98bd424 in start_thread () at /lib64/libpthread.so.0
#9  0x7ff6fa0c4add in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7ff6d2992700 (LWP 1993)):
#0  0x7ff6f98c303f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff70031a484 in  () at /usr/lib64/libQt5Script.so.5
#2  0x7ff70031a4c9 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7ff6f98bd424 in start_thread () at /lib64/libpthread.so.0
#4  0x7ff6fa0c4add in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7ff64a4d4700 (LWP 2001)):
#0  0x7ff6f98c303f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff651424d23 in  () at /usr/lib64/dri/radeonsi_dri.so
#2  0x7ff651424537 in  () at /usr/lib64/dri/radeonsi_dri.so
#3  0x7ff6f98bd424 in start_thread () at /lib64/libpthread.so.0
#4  0x7ff6fa0c4add in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7ff63fdb1700 (LWP 2148)):
#0  0x7ff6fa0bc07d in poll () at /lib64/libc.so.6
#1  0x7ff6f675e364 

[kdenlive] [Bug 361396] Splitting audio allows timeline corruption

[via KDE Bugzilla]

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

wegwerf-1-...@gmx.de changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #2 from wegwerf-1-...@gmx.de ---
Is this fixed satisfyingly? If yes, can you please be so kind as to close this
bug as RESOLVED FIXED? Thank you very much!

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

[kdenlive] [Bug 357397] Image Sequence (with period in filename) missing upon re-opening project

[Sam Muirhead via KDE Bugzilla]

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

Sam Muirhead  changed:

   What|Removed |Added

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

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

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

[Justin Phelps via KDE Bugzilla]

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

Justin Phelps  changed:

   What|Removed |Added

 CC|linut...@onitato.com|

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

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

[via KDE Bugzilla]

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

wegwerf-1-...@gmx.de changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #9 from wegwerf-1-...@gmx.de ---
Is this issue fixed satisfyingly? If so, please close it as RESOLVED FIXED.
Thank you!

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

[plasmashell] [Bug 358827] Switching between Alternatives on Desktop loses / breaks applet geometry

[David Rosca via KDE Bugzilla]

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

--- Comment #1 from David Rosca  ---
Git commit 4c6707dbed37b1e1ba845f1dc190f2c324e1e071 by David Rosca.
Committed on 13/05/2016 at 15:53.
Pushed by drosca into branch 'master'.

Alternatives: Add new applet only after the old one was removed

New applet is now added at the same position as the old one.

Differential Revision: https://phabricator.kde.org/D1134

M  +10   -7shell/alternativeshelper.cpp

http://commits.kde.org/plasma-workspace/4c6707dbed37b1e1ba845f1dc190f2c324e1e071

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

[kdenlive] [Bug 357397] Image Sequence (with period in filename) missing upon re-opening project

[via KDE Bugzilla]

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

wegwerf-1-...@gmx.de changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #8 from wegwerf-1-...@gmx.de ---
Is this bug fixed to your satisfaction? If yes, can you please be so kind as to
close this bug as RESOLVED FIXED? Thank you very much!

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

[kdenlive] [Bug 360174] Segmentation fault when using title clips

[via KDE Bugzilla]

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

wegwerf-1-...@gmx.de changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #9 from wegwerf-1-...@gmx.de ---
If there is no reason to keep this bug report open, could you please so kind as
to close it as RESOLVED FIXED? Thank you very much!

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

[kdenlive] [Bug 362630] when you insert a clip in the timeline, by the mouse in insert mode, all the clips in the timeline move forward

[via KDE Bugzilla]

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

wegwerf-1-...@gmx.de changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #2 from wegwerf-1-...@gmx.de ---
Seems to be fixed; I tried with one of my own test projects and everything
seems to work now as expected. The fix is ten days old. If this is really
fixed, please close this bug as RESOLVED FIXED. Thank you very much!

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

[kscreenlocker] [Bug 360489] kscreenlocker suggests running "loginctl unlock-sessions" even though I don't use systemd

[Simon Andric via KDE Bugzilla]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[kdenlive] [Bug 362732] [icon/theme] Missing alignement icons in 'Title Clip' creator

[via KDE Bugzilla]

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

wegwerf-1-...@gmx.de changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #3 from wegwerf-1-...@gmx.de ---
Is this fixed? If yes, can you please be so kind as to close this bug by
setting it to RESOLVED FIXED? Thank you very much!

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

[kdenlive] [Bug 363000] speed effect missing

[via KDE Bugzilla]

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

wegwerf-1-...@gmx.de changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #1 from wegwerf-1-...@gmx.de ---
Did you check that you are on latest MLT version? The implementation of the
speed effect has been changed and needs a very recent MLT version.

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

[kdenlive] [Bug 363033] New: git master: double clicking a track title does not set input focus to title input field, only selects it.

[via KDE Bugzilla]

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

Bug ID: 363033
   Summary: git master: double clicking a track title does not set
input focus to title input field, only selects it.
   Product: kdenlive
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: wegwerf-1-...@gmx.de

When double clicking the title of a track, the title gets properly selected.
However, keyboard input focus isn't set to the title input box. In consequence,
any further typing gets up interpreted as timeline input or whatever element
had keyboard focus at the time of double clicking the title. Depending on what
you type without noticing the UI glitch, you end up damaging your project in
subtle or not-to-subtle ways.

Reproducible: Always

Steps to Reproduce:
1. Create a new project or open an existing project.
2. Double click a title in any of your tracks.
3. Input new title text.

Actual Results:  
Title isn't changed; instead, keyboard input is interpreted as timeline
actions, et cetera.

Expected Results:  
Input changes title field of track header that had been double clicked on.

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

[kdenlive] [Bug 358185] Kdenlive-git - Title editor, shows greenish overlay after clicking "Show Background", but only the first time.

[via KDE Bugzilla]

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

--- Comment #5 from wegwerf-1-...@gmx.de ---
Still seeing this on a regular basis. It's really getting annoying when you do
a lot of title editing...

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

[kdenlive] [Bug 360266] git master - Trying to select another item in Kdenlive after editing a track title leaves interface focused on track title field

[via KDE Bugzilla]

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

wegwerf-1-...@gmx.de changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #2 from wegwerf-1-...@gmx.de ---
Jesse, this seems to be fixed since some time. With the most recent git master
I could not reproduce your bug anymore. If this bug should be fixed also for
you too, then please close this bug as RESOLVED FIXED. Thank you!

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

[frameworks-knotifications] [Bug 348414] Crash in KNotification::flags() (NotifyByAudio::onAudioFinished)

[Simon Andric via KDE Bugzilla]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[kwin] [Bug 362898] KWin Zoom seems to "forget" settings

[Daniel via KDE Bugzilla]

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

--- Comment #14 from Daniel <86d...@gmail.com> ---
I am unfortunately not able to replicate the issue consistently. I can get it
to happen frequently with the following procedure, but it's definitely not
always the case:

1. I move the pointer to the bottom left corner of the screen, where the menu
button is.
2. Sometimes the above is enough to trigger the problem. If not, it can happen
if I then move the pointer along the bottom of the screen towards the bottom
right corner.

I can say there is definitely something going on with the cursor image though,
as after playing around for awhile, the defalt cursor changed to the
"up-and-down scrolling" cursor. In that case, when I turned off Zoom the cursor
image reverted to the proper arrow. I then went ahead and changed the desktop
theme to Breeze Dark and that caused a dark strip to appear at the bottom of
the zoomed-in view.

I would really like to help debug this more properly, but since I need a usable
screen magnifier all the time to use the computer, it becomes quite the
challenge.

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

[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup

[Orbmiser via KDE Bugzilla]

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

--- Comment #55 from Orbmiser  ---
Is Daniel Vrátil dvra...@kde.org still on this? As haven't seen a post from him
in a year?
New to this so don't know how it all works. Like he is the only one and now
ignoring?
Others? How to get more info on it being addressed or not?

Thanks!

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

[phonon-backend-gstreamer] [Bug 334421] amarok will increase the memory usage after long time music switch

[Myriam Schweingruber via KDE Bugzilla]

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

Myriam Schweingruber  changed:

   What|Removed |Added

Version|unspecified |4.8.0
   Target Milestone|4.8 |---
 Status|NEEDSINFO   |UNCONFIRMED
 Resolution|WAITINGFORINFO  |---

--- Comment #10 from Myriam Schweingruber  ---
Thank you for the feedback.

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

[kdenlive] [Bug 354052] Applications/15.08: audio tracks do not mix in converted project

[via KDE Bugzilla]

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

wegwerf-1-...@gmx.de changed:

   What|Removed |Added

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

--- Comment #3 from wegwerf-1-...@gmx.de ---
I've given my old existing project another try and now loaded it into recent
git master (16.04+). I've added new audio-only tracks, then moved the existing
audio clips onto these audio-only tracks, and deleted the old audio/video
tracks originally containing the audio. Mixing works now as expected. It looks
like this issue has somehow been fixed as either the side effect of another
fix, or there was another bug report tracking this issue and we never
identified these bugs as duplicates of each other. Alas, I'm moving this to
RESOLVED FIXED. One bug report less... :)

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

[krita] [Bug 361709] With more than 1 curve based assistant, zooming in will black screen part or all of the drawing window

[via KDE Bugzilla]

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

--- Comment #18 from elk...@yahoo.com ---
My krita-opengl.txt only has the single line with the card & driver info.

I've tried running krita in debug mode on the linux side, with dbgOpenGL set to
true, but the issue doesn't to seem cause any hiccups in the log.

As far as I know, I've never had this issue cause a crash.

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

[kdenlive] [Bug 363032] New: git master: volume effect looses its setting when applied to track

[via KDE Bugzilla]

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

Bug ID: 363032
   Summary: git master: volume effect looses its setting when
applied to track
   Product: kdenlive
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: wegwerf-1-...@gmx.de

When applying the volume (keyframable) effect to a track its properties are not
recalled when reselecting the track header but instead always reset to 0db. 

Reproducible: Always

Steps to Reproduce:
1. Create new Kdenlive project with at least one audio track.
2. Add volume effect to audio track.
3. Set volume effect to -10db.
4. Select something else/another track/clip.
5. Select audio track header again.

Actual Results:  
Volume effect is reset to 0db.

Expected Results:  
Volume effect should retain its -10db setting.

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

[kdenlive] [Bug 362784] git master: deselecting split audio/video config option does not deselect target track(s)

[via KDE Bugzilla]

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

wegwerf-1-...@gmx.de changed:

   What|Removed |Added

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

--- Comment #1 from wegwerf-1-...@gmx.de ---
This is now fixed in recent git master, so I'm closing this as RESOLVED FIXED.

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

[kdenlive] [Bug 362900] git master: dropping clip in insert mode at the exact beginning of a clip causes alert "Cannot find clip to cut"

[via KDE Bugzilla]

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

wegwerf-1-...@gmx.de changed:

   What|Removed |Added

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

--- Comment #3 from wegwerf-1-...@gmx.de ---
Thank you very much, Jean-Baptiste! Works like a charm, so I can close this bug
as RESOLVED FIXED.

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

[kdenlive] [Bug 362253] git master: deleting bottommost video track leaves next higher track with opaque/transparent button

[via KDE Bugzilla]

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

wegwerf-1-...@gmx.de changed:

   What|Removed |Added

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

--- Comment #6 from wegwerf-1-...@gmx.de ---
Thank you very much Jean-Baptiste! This is now fixed, so I close this bug
report as RESOLVED FIXED.

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

[krita] [Bug 363031] New: [Huion] Moving From Driver to Krita to make right clicking work causes the cursor to vanish over the working area

[via KDE Bugzilla]

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

Bug ID: 363031
   Summary: [Huion] Moving From Driver to Krita to make right
clicking work causes the cursor to vanish over the
working area
   Product: krita
   Version: 3.0 Beta
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: thenineri...@yahoo.com

In order to get the right click to work with my Huion 1060 Plus on Windows 7
Professional, 64 bit using the Krita 3.0 beta build d33a4a-x64, I have to open
the driver for the tablet, and right click onto the Krita working area.
However, this time when I clicked off of the right click function, my cursor
vanished, yet only on the working area. Elsewhere it functions properly.

Reproducible: Couldn't Reproduce


Actual Results:  
The cursor vanishes over the working area.

Expected Results:  
The cursor should have brought up just the right click palette, then functioned
normally when clicking on the working area.

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

[krita] [Bug 361709] With more than 1 curve based assistant, zooming in will black screen part or all of the drawing window

[David REVOY via KDE Bugzilla]

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

David REVOY  changed:

   What|Removed |Added

 CC||i...@davidrevoy.com

--- Comment #20 from David REVOY  ---
Created attachment 98948
  --> https://bugs.kde.org/attachment.cgi?id=98948=edit
[ ^ short video of the bug ]

Hi, reproduced on Ubuntu 16.04 Git~master, nvidia graphic too. GeForce GTX 650
Ti. I attach a short video.

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

[Akonadi] [Bug 354056] Deleted emails stay, but greyed out

[Kim Lilliestierna via KDE Bugzilla]

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

--- Comment #38 from Kim Lilliestierna  ---
This has been resolved in the latest kmail version (5.1.3) and  kde framework
(5.18.0)

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

[krita] [Bug 361709] With more than 1 curve based assistant, zooming in will black screen part or all of the drawing window

[Quiralta via KDE Bugzilla]

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

Quiralta  changed:

   What|Removed |Added

 CC||rjquira...@gmail.com

--- Comment #19 from Quiralta  ---
I can actually reproduce this on Archlinux right now. zooming turns the screen
black (at some point)

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

[krita] [Bug 360560] [HUION] setting pen second button as right mouse button won't work

[via KDE Bugzilla]

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

thenineri...@yahoo.com changed:

   What|Removed |Added

 CC||thenineri...@yahoo.com

--- Comment #3 from thenineri...@yahoo.com ---
I have tested it in the Krita 3.0 Beta bleeding edge, build d330a4a-x64, on
Windows 7 Professional 64 bit, using a Huion 1060 Plus tablet. I can confirm
that neither the middle click or right click work properly, unless I have the
driver open. It does not work in any document size that I open.

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

[krdc] [Bug 363016] KRDC session disconnects after accessing remote host

[Urs Wolfer via KDE Bugzilla]

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

--- Comment #1 from Urs Wolfer  ---
@Jeff Helps: Do you have these issues with RDP or VNC protocol?

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

[krita] [Bug 363021] No pressure sensitivity on Huion 1060 Plus

[Quiralta via KDE Bugzilla]

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

Quiralta  changed:

   What|Removed |Added

 CC||rjquira...@gmail.com

--- Comment #1 from Quiralta  ---
I have a 1060pro, which is very similar, as far as I can tell, there is no need
for the wizardpen driver, the digimend drivers are built in the kernel, that
should work out of the box, now the last  xf86-input-evdev broke my tablet
pressure in all programs, (its been worked out upstream already) thus using the
previous evdev driver version is working for me, I'm also on Archlinux, and
found the same problem in Manjaro and kaOs live images.

I'm thinking that our tablets should work similar if not the same, but don't
take my word for granted, still I think this is a driver problem rather than
Krita's.

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

[krita] [Bug 363030] New: Text cursor can't be placed to the end of text

[via KDE Bugzilla]

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

Bug ID: 363030
   Summary: Text cursor can't be placed to the end of text
   Product: krita
   Version: 3.0 Beta
  Platform: Debian testing
   URL: http://files.kde.org/krita/3/linux/devbuilds/krita-3.0
-Beta-master-562442e-x86_64.appimage
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Text Tool
  Assignee: krita-bugs-n...@kde.org
  Reporter: r...@rkfg.me

You can't set the text cursor position after the last character, only before
it. At the same time it's actually after it so when you press Delete it removes
the character after itself.

1. Add new artistic text.
2. Note that the blinking cursor is located before the last character.
3. Press Backspace and observe the last character being deleted like if you've
pressed Delete.
4. Press Left Arrow and see no difference but the cursor is now logically
before the last character.
5. Press Backspace again, the next-to-last character is deleted now as it
should be.

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

[apper] [Bug 363022] New: No relevant classes found. No output generated for multiple cpp

[Jean-christophe Manciot via KDE Bugzilla]

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

Bug ID: 363022
   Summary: No relevant classes found. No output generated for
multiple cpp
   Product: apper
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: dantt...@gmail.com
  Reporter: actionmysti...@gmail.com

On Ubuntu 16.04 4.4.0-22
>From git://anongit.kde.org/apper.git commit 20160329.ef57b76c



Reproducible: Always

Steps to Reproduce:
1. git reset --hard
git clean -fxd :/
git fetch --progress --prune origin
2. mkdir build && cd build
3. cmake .. -DCMAKE_INSTALL_PREFIX=/usr/
3. make

Actual Results:  
...
Scanning dependencies of target apper_private_automoc
[  0%] Automatic moc for target apper_private
Generating ApplicationLauncher.moc
/home/actionmystique/Program-Files/Ubuntu/Apper/git-apper/libapper/ApplicationLauncher.cpp:0:
Note: No relevant classes found. No output generated.
Generating ApplicationsDelegate.moc
/home/actionmystique/Program-Files/Ubuntu/Apper/git-apper/libapper/ApplicationsDelegate.cpp:0:
Note: No relevant classes found. No output generated.
Generating ChangesDelegate.moc
/home/actionmystique/Program-Files/Ubuntu/Apper/git-apper/libapper/ChangesDelegate.cpp:0:
Note: No relevant classes found. No output generated.
Generating CustomProgressBar.moc
/home/actionmystique/Program-Files/Ubuntu/Apper/git-apper/libapper/CustomProgressBar.cpp:0:
Note: No relevant classes found. No output generated.
Generating InfoWidget.moc
/home/actionmystique/Program-Files/Ubuntu/Apper/git-apper/libapper/InfoWidget.cpp:0:
Note: No relevant classes found. No output generated.
Generating LicenseAgreement.moc
/home/actionmystique/Program-Files/Ubuntu/Apper/git-apper/libapper/LicenseAgreement.cpp:0:
Note: No relevant classes found. No output generated.
Generating PackageModel.moc
/home/actionmystique/Program-Files/Ubuntu/Apper/git-apper/libapper/PackageModel.cpp:0:
Note: No relevant classes found. No output generated.
Generating PkTransaction.moc
/home/actionmystique/Program-Files/Ubuntu/Apper/git-apper/libapper/PkTransaction.cpp:0:
Note: No relevant classes found. No output generated.
Generating PkTransactionWidget.moc
/home/actionmystique/Program-Files/Ubuntu/Apper/git-apper/libapper/PkTransactionWidget.cpp:0:
Note: No relevant classes found. No output generated.
Generating Requirements.moc
/home/actionmystique/Program-Files/Ubuntu/Apper/git-apper/libapper/Requirements.cpp:0:
Note: No relevant classes found. No output generated.
Generating TransactionDelegate.moc
/home/actionmystique/Program-Files/Ubuntu/Apper/git-apper/libapper/TransactionDelegate.cpp:0:
Note: No relevant classes found. No output generated.
Generating moc_ApplicationLauncher.cpp
Generating moc_ApplicationSortFilterModel.cpp
...


The whole build.log is available here:
https://drive.google.com/file/d/0B6XxNd5c3zV_VGZyak80ZEpZaEE/view?usp=sharing

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

[Discover] [Bug 363029] New: Applications in the showcase are not installable

[scl via KDE Bugzilla]

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

Bug ID: 363029
   Summary: Applications in the showcase are not installable
   Product: Discover
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: scl.gp...@gmail.com

The applications in the upper showcase coverflow panel are not installable, for
instance KDevelop, Dolphin, Krita.

Reproducible: Always

Steps to Reproduce:
1. Open Discover.
2. Click one of the application thumbnails in the showcase panel or enter its
name in the search bar.
The application names end with .desktop, e.g. kdevelop.desktop.

Actual Results:  
An empty template window with text labels, but no information opens. There's
only a button 'Start', but nothing to install.

Expected Results:  
The applications are found and installable.
Exception: Krita is not shipped in Debian Testing, so it should not be offered
in the showcase.

Latest Debian testing with KDE Plasma 5.4.3, Qt 5.5.1

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

[krita] [Bug 363025] New: Crash while changing font-type on artistic text.

[wolthera via KDE Bugzilla]

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

Bug ID: 363025
   Summary: Crash while changing font-type on artistic text.
   Product: krita
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Vector Objects and Tools
  Assignee: krita-bugs-n...@kde.org
  Reporter: griffinval...@gmail.com

Artisttic text crashes on font-type change.

Reproducible: Always

Steps to Reproduce:
1. Make artistic text
2. Select some text
3. Change fonttype.
4. crash!



gdb backtrace:

Thread 23 (Thread 0x7fff96ea3700 (LWP 12114)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x75599738 in QWaitCondition::wait(QMutex*, unsigned long) ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#2  0x75595467 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#3  0x75598c89 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#4  0x7fffef1506fa in start_thread (arg=0x7fff96ea3700)
at pthread_create.c:333
#5  0x74c94b5d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 22 (Thread 0x7fff966a2700 (LWP 12113)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x75599738 in QWaitCondition::wait(QMutex*, unsigned long) ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#2  0x75595467 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#3  0x75598c89 in ?? ()
---Type  to continue, or q  to quit---
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#4  0x7fffef1506fa in start_thread (arg=0x7fff966a2700)
at pthread_create.c:333
#5  0x74c94b5d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 21 (Thread 0x7fff95ea1700 (LWP 12112)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x75599738 in QWaitCondition::wait(QMutex*, unsigned long) ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#2  0x75595467 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#3  0x75598c89 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#4  0x7fffef1506fa in start_thread (arg=0x7fff95ea1700)
at pthread_create.c:333
#5  0x74c94b5d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 20 (Thread 0x7fffc0b41700 (LWP 12111)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
---Type  to continue, or q  to quit---
#1  0x75599738 in QWaitCondition::wait(QMutex*, unsigned long) ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#2  0x75595467 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#3  0x75598c89 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#4  0x7fffef1506fa in start_thread (arg=0x7fffc0b41700)
at pthread_create.c:333
#5  0x74c94b5d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7fffa5da4700 (LWP 12099)):
#0  pthread_cond_wait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x755997eb in QWaitCondition::wait(QMutex*, unsigned long) ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#2  0x7676faa2 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Widgets.so.5
#3  0x75598c89 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#4  0x7fffef1506fa in start_thread (arg=0x7fffa5da4700)
at pthread_create.c:333
#5  0x74c94b5d in clone ()
---Type  to continue, or q  to quit---
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7fffa6640700 (LWP 12097)):
#0  pthread_cond_wait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x755997eb in QWaitCondition::wait(QMutex*, unsigned long) ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#2  0x75593116 in QSemaphore::tryAcquire(int, int) ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#3  0x7311d7b3 in KisTileDataSwapper::waitForWork (
this=)
at
/home/krita/kde/src/krita/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:86
#4  0x7311d9aa in KisTileDataSwapper::run (
this=0x7359f440 <(anonymous
namespace)::Q_QGS_s_instance::innerFunction()::holder+64>)
at
/home/krita/kde/src/krita/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:92
#5  0x75598c89 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#6  0x7fffef1506fa in start_thread (arg=0x7fffa6640700)
at pthread_create.c:333
#7  0x74c94b5d in clone ()
---Type  to continue, or q  to quit---
at 

[kwin] [Bug 362898] KWin Zoom seems to "forget" settings

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #13 from Thomas Lübking  ---
We should first ensure this is the cause and ideally figure why the image
request fails (in case) - you could easily run into this as initial case (so
there's no cursorimage to stick with)

Can you spot a pattern?  (like "whenever I hover element foo in application
bar")

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