[KScreen] [Bug 378136] New: Issues having monitors arranged up and down

[Ural]

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

Bug ID: 378136
   Summary: Issues having monitors arranged up and down
   Product: KScreen
   Version: 5.9.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: se...@kde.org
  Reporter: uralz...@autistici.org
  Target Milestone: ---

Hello. I use 4 monitors. All was fine, I used it in one row.
When I moved my computer to another place, there was lesser space, so I
arranged them 2 up and 2 down.
Issues:
1. Yakuake stopped working. No activation on F12. It keeps running. Guake not
working as well.
2. Moving windows became hard. It is not following your mouse immediately when
picked. 
3. Random bugs and issues. 

After moving them back in one row, yakuake immediately opened, issues
disappeared.

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

[Akonadi] [Bug 378135] akonadiserver crashes everytime it gets stopped (MuQSS enabled)

[bugzilla_noreply]

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

thurs...@gmx.de changed:

   What|Removed |Added

Summary|akonadiserver crashes   |akonadiserver crashes
   |everytime it gets stopped   |everytime it gets stopped
   |(MuQQS enabled) |(MuQSS enabled)

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

[plasma-nm] [Bug 378101] nm-editor password unhide button isn't there

[Jan Grulich]

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

Jan Grulich  changed:

   What|Removed |Added

 CC||jgrul...@redhat.com
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #1 from Jan Grulich  ---
This was a bug in Qt back in the day, I remember patching Qt in Fedora to fix
this issue. Also in the latest Plasma release this has been changed and both
icons are not part of the password field.

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

[frameworks-networkmanager-qt] [Bug 378109] signals in glib2 was defined by QT

[Jan Grulich]

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

Jan Grulich  changed:

   What|Removed |Added

 CC||jgrul...@redhat.com
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #1 from Jan Grulich  ---
You have to use add_definitions(-DQT_NO_KEYWORDS) in your CMake, otherwise you
won't be able to use nm-qt. This is due to glib using signals as a name for a
variable, while signals is a keyword for us.

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

[Akonadi] [Bug 378135] New: akonadiserver crashes everytime it gets stopped (MuQQS enabled)

[bugzilla_noreply]

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

Bug ID: 378135
   Summary: akonadiserver crashes everytime it gets stopped (MuQQS
enabled)
   Product: Akonadi
   Version: 5.4.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-b...@kde.org
  Reporter: thurs...@gmx.de
  Target Milestone: ---

Application: akonadiserver (5.4.3)

Qt Version: 5.8.0
Frameworks Version: 5.32.0
Operating System: Linux 4.10.5-1-ck-ivybridge x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
(I'm on Arch Linux running the 4.10.5-linux-ck-ivybridge kernel from the
repo-ck user repo)

What has to be done to recreate the behavior:
Using any akonadi-related application after KDE startup (preferably KMail),
then stopping akonadi via "akonadictl stop" or shutting down the system. It
happens ONLY when booting with linux-ck kernel with the MuQQS-Scheduler
enabled.

Corresponding forum thread: https://bbs.archlinux.org/viewtopic.php?id=224465

The crash can be reproduced every time.

-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f73629afc40 (LWP 6218))]

Thread 17 (Thread 0x7f72de7fc700 (LWP 6317)):
#0  0x7f735b8cbf57 in g_main_context_query () from
/usr/lib/libglib-2.0.so.0
#1  0x7f735b8cc718 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f735b8cc8bc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f73612a910b in QEventDispatcherGlib::processEvents
(this=0x7f72c80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f736125293a in QEventLoop::exec (this=this@entry=0x7f72de7fbdf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f7361074ae3 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f7361079748 in QThreadPrivate::start (arg=0x8dea30) at
thread/qthread_unix.cpp:368
#7  0x7f735f59d2e7 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7f736077354f in clone () from /usr/lib/libc.so.6

Thread 16 (Thread 0x7f72d700 (LWP 6306)):
#0  0x7f735f5a3b63 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f736107a536 in QWaitConditionPrivate::wait_relative (time=3,
this=0x7f7348081080) at thread/qwaitcondition_unix.cpp:133
#2  QWaitConditionPrivate::wait (time=3, this=0x7f7348081080) at
thread/qwaitcondition_unix.cpp:141
#3  QWaitCondition::wait (this=this@entry=0x7f7348080ec0,
mutex=mutex@entry=0x7f73480035a0, time=3) at
thread/qwaitcondition_unix.cpp:215
#4  0x7f7361075c34 in QThreadPoolThread::run (this=0x7f7348080eb0) at
thread/qthreadpool.cpp:133
#5  0x7f7361079748 in QThreadPrivate::start (arg=0x7f7348080eb0) at
thread/qthread_unix.cpp:368
#6  0x7f735f59d2e7 in start_thread () from /usr/lib/libpthread.so.0
#7  0x7f736077354f in clone () from /usr/lib/libc.so.6

Thread 15 (Thread 0x7f72fcff9700 (LWP 6305)):
#0  0x7f735f5a3b63 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f736107a536 in QWaitConditionPrivate::wait_relative (time=3,
this=0x7f7348080c30) at thread/qwaitcondition_unix.cpp:133
#2  QWaitConditionPrivate::wait (time=3, this=0x7f7348080c30) at
thread/qwaitcondition_unix.cpp:141
#3  QWaitCondition::wait (this=this@entry=0x7f7348068990,
mutex=mutex@entry=0x7f73480035a0, time=3) at
thread/qwaitcondition_unix.cpp:215
#4  0x7f7361075c34 in QThreadPoolThread::run (this=0x7f7348068980) at
thread/qthreadpool.cpp:133
#5  0x7f7361079748 in QThreadPrivate::start (arg=0x7f7348068980) at
thread/qthread_unix.cpp:368
#6  0x7f735f59d2e7 in start_thread () from /usr/lib/libpthread.so.0
#7  0x7f736077354f in clone () from /usr/lib/libc.so.6

Thread 14 (Thread 0x7f72fd7fa700 (LWP 6304)):
#0  0x7f735f5a3b63 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f736107a536 in QWaitConditionPrivate::wait_relative (time=3,
this=0x7f7348068740) at thread/qwaitcondition_unix.cpp:133
#2  QWaitConditionPrivate::wait (time=3, this=0x7f7348068740) at
thread/qwaitcondition_unix.cpp:141
#3  QWaitCondition::wait (this=this@entry=0x7f7348068580,
mutex=mutex@entry=0x7f73480035a0, time=3) at
thread/qwaitcondition_unix.cpp:215
#4  0x7f7361075c34 in QThreadPoolThread::run (this=0x7f7348068570) at
thread/qthreadpool.cpp:133
#5  0x7f7361079748 in QThreadPrivate::start (arg=0x7f7348068570) at
thread/qthread_unix.cpp:368
#6  0x7f735f59d2e7 in start_thread () from /usr/lib/libpthread.so.0
#7  0x7f736077354f in clone () from /usr/lib/libc.so.6

Thread 13 (Thread 0x7f731f7fe700 (LWP 6260)):
#0  0x7f735f5a3b63 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  

[kwin] [Bug 377847] Blender menus flicker when you navigate them

[bugzilla_noreply]

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

--- Comment #10 from sun...@hotmail.ru ---
I've recorded a video with OpenGL option(the regular gave out black screen with
only mouse pointer visible) in SimplesScreenRecorder. But in the video
everything is smooth and no flickering is happening.

At the same time i saw some critical bug. I don't know if KDE bug tracker is
the right place to post.
If i play video(smplayer/clean mpv):
1) video is separated from controls
2) if i grab the video with mouse pointer and move it until video finishes
everything crashes, not even console(ALt+F1 etc) is available.

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

[kwin] [Bug 274931] Windows with no border (decoration) are visible on all activities

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 CC||amittim...@gmail.com

--- Comment #44 from Martin Gräßlin  ---
*** Bug 378132 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 378132] Allow applications with titlebar and frame disabled to be restricted to a single activity

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---


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

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

[kwin] [Bug 378123] GTK3 applications make problem on Wayland in normal user mode.

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

   Assignee|mgraess...@kde.org  |kwin-bugs-n...@kde.org
Product|kwayland-integration|kwin
  Component|general |wayland-generic

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

[kwin] [Bug 374867] Impossible to reach screen edge if mouse cursor is moving fast

[Martin Gräßlin]

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

--- Comment #7 from Martin Gräßlin  ---
Git commit 0bb587dcb9de0a3bc688019fd66b224e713b3501 by Martin Gräßlin.
Committed on 27/03/2017 at 05:08.
Pushed by graesslin into branch 'master'.

Ensure PointerInputRedirection::processMotion finishes prior to warping

Summary:
Consider the following situation: we have three InputEventFilter linked
in the sequence A - B - C.

The input filters are processing pointer motion events. The expected
behavior is that the new motion is processed in the sequence
   A -> B -> C

So far this did not work correctly if the pointer gets warped during the
processing. If e.g. filter B warps the pointer we get a motion sequence:
   A (1) -> B (1) -> A (2) -> B (2) -> C (2) -> C (1)

The filters following the one warping the pointer get first the newer
than the older position. This is obviously wrong. Unfortunately it is not
just a theoretical condition, but a condition happening when interacting
with the screenedges, which warp the pointer.

This change introduces a PositionUpdateBlocker in
PointerInputRedirection::processMotion to ensure that a processMotion
call finishes prior to the next update. If the PositionUpdateBlocker is
blocked the new position gets scheduled and processed once the
PositionUpdateBlocker gets destroyed.

With this we get the expected sequence for B warping pointer:
   A (1) -> B (1) -> C (1) -> A (2) -> B (2) -> C (2)

This should hopefully improve the interaction with screen edges on
Wayland.

Test Plan:
Added an auto test demonstrating the issue of incorrect
ordering caused by screenedges. Prior to the change the test is failing.

Reviewers: #kwin, #plasma

Subscribers: plasma-devel, kwin

Tags: #kwin

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

M  +46   -0autotests/integration/pointer_input.cpp
M  +49   -0pointer_input.cpp

https://commits.kde.org/kwin/0bb587dcb9de0a3bc688019fd66b224e713b3501

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

[valgrind] [Bug 377930] fcntl syscall wrapper is missing flock structure check

[Ivo Raisr]

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

Ivo Raisr  changed:

   What|Removed |Added

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

--- Comment #3 from Ivo Raisr  ---
Fixed in SVN r16287.

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

[krita] [Bug 378134] New: Crash on exit of document (mostly after exporting)

[Raghavendra kamath]

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

Bug ID: 378134
   Summary: Crash on exit of document (mostly after exporting)
   Product: krita
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: raghavendr.ra...@gmail.com
  Target Milestone: ---

Application: krita (3.1.88 (git cb56566))
 (Compiled from sources)
Qt Version: 5.8.0
Frameworks Version: 5.32.0
Operating System: Linux 4.10.5-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
Krita crashed after I exported a png to jpg and closed the document.
I have seen this random crash on document close at other times too. But if my
observation is correct it happens mostly after doing export and close. I may be
wrong in this assumption though.

The crash can be reproduced every time.

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

Thread 7 (Thread 0x7fefd3fff700 (LWP 9457)):
#0  0x7ff02fcb1756 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7ff031eff58b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7ff0331e4a71 in ?? () from /usr/lib/libQt5Widgets.so.5
#3  0x7ff031efe6d8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7ff02fcab2e7 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7ff0312e754f in clone () from /usr/lib/libc.so.6

Thread 6 (Thread 0x7fefdcf31700 (LWP 9456)):
#0  0x7ff02fcb1756 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7ff031eff58b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7ff031ef87c6 in QSemaphore::tryAcquire(int, int) () from
/usr/lib/libQt5Core.so.5
#3  0x7ff03add0e73 in KisTileDataSwapper::waitForWork (this=) at
/run/media/raghu/Data/krita-build/src/krita/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:86
#4  0x7ff03add107a in KisTileDataSwapper::run (this=0x7ff03b2868e0
<_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder+64>) at
/run/media/raghu/Data/krita-build/src/krita/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:92
#5  0x7ff031efe6d8 in ?? () from /usr/lib/libQt5Core.so.5
#6  0x7ff02fcab2e7 in start_thread () from /usr/lib/libpthread.so.0
#7  0x7ff0312e754f in clone () from /usr/lib/libc.so.6

Thread 5 (Thread 0x7fefdd732700 (LWP 9455)):
#0  0x7ff02fcb1756 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7ff031eff58b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7ff031ef84d3 in QSemaphore::acquire(int) () from
/usr/lib/libQt5Core.so.5
#3  0x7ff03adb71be in KisTileDataPooler::waitForWork (this=0x7ff03b2868a0
<_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder>) at
/run/media/raghu/Data/krita-build/src/krita/libs/image/tiles3/kis_tile_data_pooler.cc:165
#4  0x7ff03adb790a in KisTileDataPooler::run (this=0x7ff03b2868a0
<_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder>) at
/run/media/raghu/Data/krita-build/src/krita/libs/image/tiles3/kis_tile_data_pooler.cc:187
#5  0x7ff031efe6d8 in ?? () from /usr/lib/libQt5Core.so.5
#6  0x7ff02fcab2e7 in start_thread () from /usr/lib/libpthread.so.0
#7  0x7ff0312e754f in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7ff019577700 (LWP 9440)):
#0  0x7ff0312dd67d in poll () from /usr/lib/libc.so.6
#1  0x7ff02d24f7a6 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7ff02d24f8bc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7ff03212e06b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7ff0320d789a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7ff031ef9a73 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7ff035884125 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x7ff031efe6d8 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7ff02fcab2e7 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7ff0312e754f in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7ff01b210700 (LWP 9439)):
#0  0x7ff02fcb1ca6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7ff01d2bee44 in ?? () from /usr/lib/libGLX_nvidia.so.0
#2  0x7ff01bfdc394 in ?? () from /usr/lib/libnvidia-glcore.so.378.13
#3  0x7ff01d2be12c in ?? () from /usr/lib/libGLX_nvidia.so.0
#4  0x7ff02fcab2e7 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7ff0312e754f in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7ff026574700 (LWP 9437)):
#0  0x7ff0312dd67d in 

[ktouch] [Bug 378118] ktouch is unusable slow at older system (ThinkPad T61)

[bugzilla_noreply]

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

ulr_bugs_kde_...@moehrkevielfalt.de changed:

   What|Removed |Added

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

--- Comment #2 from ulr_bugs_kde_...@moehrkevielfalt.de ---
Hi,

now I know, that I have the older version 2.3.0. The patch from bug 346248
solves the problem.

Thanks a lot.

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

[krita] [Bug 378065] This program isn't letting me make smooth lines

[Literally Satan]

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

--- Comment #4 from Literally Satan  ---
(In reply to Boudewijn Rempt from comment #3)
> The difference between you and me is that I am the maintainer of this
> project.

well then your project suksss, fuck uuu :

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

[Spectacle] [Bug 378133] New: Print screen means you save the screenshot not as if work of art was produced

[bugzilla_noreply]

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

Bug ID: 378133
   Summary: Print screen means you save the screenshot not as if
work of art was produced
   Product: Spectacle
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: jey.and@gmail.com
  Target Milestone: ---

I need to document buggy behaviour and I have no use case for instance where
print screen will fire up application that will eventually "enable" me to save
the print of screen. gtfo

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

[kwin] [Bug 378132] New: Allow applications with titlebar and frame disabled to be restricted to a single activity

[Amit]

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

Bug ID: 378132
   Summary: Allow applications with titlebar and frame disabled to
be restricted to a single activity
   Product: kwin
   Version: 5.8.5
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: activities
  Assignee: kwin-bugs-n...@kde.org
  Reporter: amittim...@gmail.com
  Target Milestone: ---

Applications for which the default KWin titlebar and frame are disabled
(through Window Rules) show by default on all desktops, and there is no way to
change this behaviour besides by adding back the titlebar. However, for a web
browser (such as Chromium or Vivaldi, my current browser), with tabs at the
top, this appearance does not make sense. There should be a setting that allows
users to hide the titlebar and frame of a particular application while still
maintaining KWin handling so as to let these windows be restricted to the
activity on which they were launched, like all other KWin-handled apps. Users
would still be able to change the activity on which the window is displayed
using alt-F3 to bring up the menu.

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

[plasmashell] [Bug 378131] New: Plasma crashes after right clicking on dolphin file manager and closing

[AJ Fite]

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

Bug ID: 378131
   Summary: Plasma crashes after right clicking on dolphin file
manager and closing
   Product: plasmashell
   Version: 5.9.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: goldma...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.9.4)

Qt Version: 5.8.0
Frameworks Version: 5.32.0
Operating System: Linux 4.10.5-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

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

I right clicked on the dolphin file manager in the icon-only task manager on my
bottom panel and selected "close".  There were multiple dolphin windows open at
the time.  This caused plasma to restart and dolphin was closed upon plasma
re-appearing.

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

Thread 16 (Thread 0x7f0b4affd700 (LWP 16736)):
#0  0x7f0c34ab8756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f0c35bfe58b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f0b7cfaf1d0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f0b7cfb39d8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f0b7cfae263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f0b7cfb3a32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f0b7cfae263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f0b7cfb1249 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f0c35bfd6d8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f0c34ab22e7 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f0c3551054f in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7f0b4b7fe700 (LWP 16735)):
#0  0x7f0c34ab8756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f0c35bfe58b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f0b7cfaf1d0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f0b7cfb39d8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f0b7cfae263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f0b7cfb3a32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f0b7cfae263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f0b7cfb1249 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f0c35bfd6d8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f0c34ab22e7 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f0c3551054f in clone () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7f0b42ffd700 (LWP 16734)):
#0  0x7f0c34ab8756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f0c35bfe58b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f0b7cfaf1d0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f0b7cfb39d8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f0b7cfae263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f0b7cfb3a32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f0b7cfae263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f0b7cfb1249 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f0c35bfd6d8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f0c34ab22e7 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f0c3551054f in clone () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7f0b437fe700 (LWP 16733)):
#0  0x7f0c34ab8756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f0c35bfe58b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f0b7cfaf1d0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f0b7cfb39d8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  

[kwin] [Bug 377847] Blender menus flicker when you navigate them

[Matthew Trescott]

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

--- Comment #9 from Matthew Trescott  ---
I didn't record on Wayland; this happens for me on both Wayland (XWayland since
Blender doesn't support Wayland) and X.Org. I just used SimpleScreenRecorder.

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

[plasmashell] [Bug 363800] Can't preview windows on the task manager that are minimized

[Fincer]

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

Fincer  changed:

   What|Removed |Added

 CC||fince...@hotmail.com

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

[okular] [Bug 378130] New: Okular snap package fails to find libKF5Parts.so.5

[bugzilla_noreply]

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

Bug ID: 378130
   Summary: Okular snap package fails to find libKF5Parts.so.5
   Product: okular
   Version: 1.0.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: gn.prp.gabr...@gmail.com
  Target Milestone: ---

Recentely i installed Okular in Ubuntu 16.04 via snap using

"sudo snap install okular"

But when I try to open Okular through the icon in the menu nothing happens, so
I try in the terminal and I get this message:

"okular: error while loading shared libraries: libKF5Parts.so.5: cannot open
shared object file: No such file or directory"

I already installed libKF5Parts5 through

"sudo apt install libkf5parts5"

But nothing happened.

Thanks for the attention, and sorry for the not so good English.

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

[plasmashell] [Bug 368386] [Feature Request] - Do not remove Launchers for the tasks model for the sake of windows

[Fincer]

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

Fincer  changed:

   What|Removed |Added

 CC||fince...@hotmail.com

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

[krita] [Bug 378129] New: brush impossibly slow, updating strokes after 5+ seconds

[bugzilla_noreply]

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

Bug ID: 378129
   Summary: brush impossibly slow, updating strokes after 5+
seconds
   Product: krita
   Version: 3.1.2
  Platform: unspecified
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: taylorlocket0ast...@gmail.com
  Target Milestone: ---

At the moment, the canvas only updates brush strokes after more than 5 seconds,
sometimes longer. I have done multiple quality reductions, and this has done
nothing to speed up reaction times. I have also tried closing and reopening the
program and creating smaller canvases and trying smaller brushes, and have also
increased the maximum memory for the program. So far, nothing I have done has
created an impact. Everything worked fine when I had version 2.9.11, and this
bug has persisted since I downloaded version 3.1.2

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

[kmail2] [Bug 376202] Emails are moved to folders on read, without explanation

[Łukasz]

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

--- Comment #10 from Łukasz  ---
> So far I haven't seen this bug in 5.4.3 Kmail version, though it happens
> that filters don't move the messages to their destination folders.
> 
> I noticed that in some cases the destination folder fields are empty in
> filter settings, but after restarting kmail and akonadi they're back.

Additionally, I noticed that when the messages that undergo filter rules appear
inside Inbox directory and are almost immediately moved to their folders
through the filter rules, I get the infamous "Retrieving Folder Contents"
message, as described in bug 297930, however, after some time I can read the
e-mails again.

Here is journalctl log excerpt:

Mar 27 01:50:30 ll akonadiserver[22466]: org.kde.pim.akonadiplugin_indexer:
invalid query  "{\n\"cond\": 0,\n\"key\": \"\",\n\"limit\": -1,\n  
 \"negated\": false,\n\"value\": null\n}\n"
Mar 27 01:50:30 ll akonadiserver[22466]: org.kde.pim.akonadiplugin_indexer:
invalid query  "{\n\"cond\": 0,\n\"key\": \"\",\n\"limit\": -1,\n  
 \"negated\": false,\n\"value\": null\n}\n"
Mar 27 01:50:15 ll akonadi_archivemail_agent[22478]: org.kde.pim.akonadicore:
Got a stale notification for an item which was already removed. 33978 ""
Mar 27 01:50:15 ll akonadi_mailfilter_agent[22486]: org.kde.pim.akonadicore:
Got a stale notification for an item which was already removed. 33978 ""
Mar 27 01:50:15 ll akonadi_indexing_agent[22483]: "Unable to fetch item from
backend (collection -1) : Unable to retrieve item from resource: Did not
receive a reply. Possible causes include: the remote application did not send a
reply, the message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken."
Mar 27 01:45:29 ll akonadiserver[22466]: org.kde.pim.akonadiplugin_indexer:
invalid query  "{\n\"cond\": 0,\n\"key\": \"\",\n\"limit\": -1,\n  
 \"negated\": false,\n\"value\": null\n}\n"
Mar 27 01:45:29 ll akonadiserver[22466]: org.kde.pim.akonadiplugin_indexer:
invalid query  "{\n\"cond\": 0,\n\"key\": \"\",\n\"limit\": -1,\n  
 \"negated\": false,\n\"value\": null\n}\n"
Mar 27 01:45:15 ll kontact[22528]: org.kde.pim.akonadicore: Got a stale
notification for an item which was already removed. 34908 ""
Mar 27 01:45:15 ll kontact[22528]: org.kde.pim.akonadicore: Got a stale
notification for an item which was already removed. 34907 ""
Mar 27 01:45:15 ll akonadi_mailfilter_agent[22486]: org.kde.pim.akonadicore:
Got a stale notification for an item which was already removed. 34908 ""

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

[kolourpaint] [Bug 378128] Diffused line when stretched

[bugzilla_noreply]

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

i...@hotmail.es changed:

   What|Removed |Added

   Keywords||reproducible, usability

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

[kolourpaint] [Bug 378128] New: Diffused line when stretched

[bugzilla_noreply]

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

Bug ID: 378128
   Summary: Diffused line when stretched
   Product: kolourpaint
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kolourpaint-supp...@lists.sourceforge.net
  Reporter: i...@hotmail.es
  Target Milestone: ---

Created attachment 104752
  --> https://bugs.kde.org/attachment.cgi?id=104752=edit
enlarged line showing the problem

When I stretch a selected part of a line, it shows an ugly blur. My father uses
KolourPaint to draw electrical components and it's kinda problematic to have
that modification in the lines because it makes you loose time fixing it in
order to get uniformity.

I've tested this on Linux Mint 18.1 Mate and Cinnamon (Kolourpaint v4.14.16),
and in Fedora 25 KDE, XFCE (Kolourpaint v16.12.2)

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

[ksirk] [Bug 378127] New: Doesn't load custom maps correctly, no indication is given of what the issue is.

[Sebastian Audet]

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

Bug ID: 378127
   Summary: Doesn't load custom maps correctly, no indication is
given of what the issue is.
   Product: ksirk
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: nemhi...@gmail.com
  Reporter: smau...@my.trine.edu
CC: kde-games-b...@kde.org
  Target Milestone: ---

Version 4.14.30

- Expects that all maps will use the same world image, and must load out of
default rather than scanning the directory
- When using a custom map, it appears regions are not honored. There is little
explanation in the documentation about how to make sure these are setup
correctly.

Since I'm using a large map file, I suspect there is another bug here where
ksirk expects all maps to be of the same size.

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

[ksirkskineditor] [Bug 378126] New: Ksirk Skin Editor doesn't save correctly.

[Sebastian Audet]

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

Bug ID: 378126
   Summary: Ksirk Skin Editor doesn't save correctly.
   Product: ksirkskineditor
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kl...@free.fr
  Reporter: smau...@my.trine.edu
CC: kde-games-b...@kde.org
  Target Milestone: ---

Application: ksirkskineditor (4.14.30)
KDE Platform Version: 4.14.30
Qt Version: 4.8.7
Operating System: Linux 4.9.13-101.fc24.x86_64 x86_64
Distribution: "Fedora release 24 (Twenty Four)"

-- Information about the crash:
- When removing countries/nations and saving, the application crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: KsirK Skin Editor (ksirkskineditor), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
84  T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#6  0x0043a963 in QList::append(QString const&) (this=0xa) at
/usr/include/QtCore/qatomic_x86_64.h:121
#7  0x0043a963 in QList::append(QString const&) (other=...,
this=) at /usr/include/QtCore/qstring.h:726
#8  0x0043a963 in QList::append(QString const&)
(this=0x7ffd2c3d63c0, t=..., n=) at
/usr/include/QtCore/qlist.h:373
#9  0x0043a963 in QList::append(QString const&)
(this=this@entry=0x7ffd2c3d63c0, t=...) at /usr/include/QtCore/qlist.h:528
#10 0x00446b88 in KsirkSkinEditor::ONU::saveConfig(QString const&)
(t=..., this=0x7ffd2c3d63c0) at /usr/include/QtCore/qlist.h:296
#11 0x00446b88 in KsirkSkinEditor::ONU::saveConfig(QString const&)
(this=0x29ab4d0, configFileName=...) at
/home/smaudet/development/ksirk/ksirkskineditor/onu.cpp:544
#12 0x00425e5d in KsirkSkinEditor::MainWindow::slotSaveSkin()
(this=0x25447a0) at
/home/smaudet/development/ksirk/ksirkskineditor/mainwindow.cpp:526
#13 0x0042b223 in
KsirkSkinEditor::MainWindow::qt_static_metacall(QObject*, QMetaObject::Call,
int, void**) (_o=, _c=, _id=,
_a=) at
/home/smaudet/development/ksirk/ksirkskineditor/mainwindow.moc:231
#14 0x7f758817f090 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /lib64/libQtCore.so.4
#15 0x7f7588e37072 in QAction::triggered(bool) () at /lib64/libQtGui.so.4
#16 0x7f7588e383d3 in QAction::activate(QAction::ActionEvent) () at
/lib64/libQtGui.so.4
#17 0x7f75892124d3 in QAbstractButtonPrivate::click() () at
/lib64/libQtGui.so.4
#18 0x7f7589212624 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) ()
at /lib64/libQtGui.so.4
#19 0x7f75892d7b6a in QToolButton::mouseReleaseEvent(QMouseEvent*) () at
/lib64/libQtGui.so.4
#20 0x7f7588e93720 in QWidget::event(QEvent*) () at /lib64/libQtGui.so.4
#21 0x7f7588e3cedc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQtGui.so.4
#22 0x7f7588e45557 in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQtGui.so.4
#23 0x7f7589bb8cda in KApplication::notify(QObject*, QEvent*) () at
/lib64/libkdeui.so.5
#24 0x7f758816aeed in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /lib64/libQtCore.so.4
#25 0x7f7588e4357b in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at
/lib64/libQtGui.so.4
#26 0x7f7588ebdff9 in QETWidget::translateMouseEvent(_XEvent const*) () at
/lib64/libQtGui.so.4
#27 0x7f7588ebc9ac in QApplication::x11ProcessEvent(_XEvent*) () at
/lib64/libQtGui.so.4
#28 0x7f7588ee5419 in x11EventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQtGui.so.4
#29 0x7f75822116ba in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#30 0x7f7582211a70 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#31 0x7f7582211b1c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#32 0x7f758819b45e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#33 0x7f7588ee55b6 in
QGuiEventDispatcherGlib::processEvents(QFlags)
() at /lib64/libQtGui.so.4
#34 0x7f75881697bf in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#35 0x7f7588169b25 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#36 0x7f758816f779 in QCoreApplication::exec() () at /lib64/libQtCore.so.4
#37 0x004130d1 in main(int, char**) (argc=,
argv=) at
/home/smaudet/development/ksirk/ksirkskineditor/main.cpp:75

Reported using DrKonqi

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

[konsole] [Bug 372991] Terminal gets stuck on interrupting a program that is outputting, preventing further output from being shown

[Peter Wu]

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

--- Comment #17 from Peter Wu  ---
Created attachment 104751
  --> https://bugs.kde.org/attachment.cgi?id=104751=edit
smaller kernel config that is able to boot archiso

(In reply to Martin Sandsmark from comment #15)
> Well, it wasn't that commit, managed to reproduce it with that reverted.

What about testing the previous commit? Simply reverting might not work as
there can be other patches that cause this issue.

> Running an arch install pretty similar to your setup but with virtualbox.
> Also made an unholy mess of shell scripts that seems to trigger it more
> consistently, only problem is that it takes forever to build the kernel (I'm
> too lazy to modify the config to trim it down).

I am attaching a kernel config from which I based my test kernels (the kernel
config I used for bisection got lost). It also has ACPI debugging features
enabled (remainder of some other bughunt), you could disable that if you want.
What do you use for "quickly" triggering the issue? Something automated would
be awesome :)

(In reply to Martin Sandsmark from comment #16)
> also, I'm not sure if I'm somehow triggering this bug instead sometimes (or
> if these are related): https://bugs.kde.org/show_bug.cgi?id=230184

It looks unrelated, that seems to be an issue with firing the timer, the issue
in this bug is caused by a watcher that is removed.

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

[plasma4] [Bug 312919] high CPU usage for copying notification

[Dreyk]

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

Dreyk  changed:

   What|Removed |Added

 CC||dreyksm...@gmail.com

--- Comment #12 from Dreyk  ---
Moved from https://bugs.kde.org/show_bug.cgi?id=356479#c122

KDE 5.9.4 and all previous.

Plasma uses 100% CPU (Intel Core i7-2670QM) load, when there is an any
animation in the task bar or system tray.

This cause only when i switch to Nvidia Prime card (notebook with Nvidia
Optimus). When I switch back to Intel integrated graphics - everything is fine.
So several years already I can not use Nvidia card with KDE desktop :(

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

[konsole] [Bug 372991] Terminal gets stuck on interrupting a program that is outputting, preventing further output from being shown

[Martin Sandsmark]

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

--- Comment #16 from Martin Sandsmark  ---
also, I'm not sure if I'm somehow triggering this bug instead sometimes (or if
these are related): https://bugs.kde.org/show_bug.cgi?id=230184

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

[Oxygen] [Bug 377448] Fails to build on windows

[bugzilla_noreply]

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

--- Comment #4 from brko...@gmail.com ---
Any progress on this?

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

[konsole] [Bug 372991] Terminal gets stuck on interrupting a program that is outputting, preventing further output from being shown

[Martin Sandsmark]

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

--- Comment #15 from Martin Sandsmark  ---
Well, it wasn't that commit, managed to reproduce it with that reverted.

Running an arch install pretty similar to your setup but with virtualbox. Also
made an unholy mess of shell scripts that seems to trigger it more
consistently, only problem is that it takes forever to build the kernel (I'm
too lazy to modify the config to trim it down).

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

[plasmashell] [Bug 376277] Right clicking on a system tray icon causes keeps focus on the icon even if user has moved elsewhere

[Joost Bremmer]

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

Joost Bremmer  changed:

   What|Removed |Added

 CC||toos...@gmail.com

--- Comment #4 from Joost Bremmer  ---
Also seem to still have this problem (plasma-workspace 5.9.4; Arch Linux).

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

[krita] [Bug 378125] New: Text Not Saving Correctly in Files

[bugzilla_noreply]

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

Bug ID: 378125
   Summary: Text Not Saving Correctly in Files
   Product: krita
   Version: unspecified
  Platform: Windows CE
OS: unspecified
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Text Tool
  Assignee: krita-bugs-n...@kde.org
  Reporter: rabbyr...@gmail.com
  Target Milestone: ---

Created attachment 104750
  --> https://bugs.kde.org/attachment.cgi?id=104750=edit
File on left was saved, file on right is how it saved.

Text isn't saving correctly, moving for no reason during the saving process but
appears fine, comes up moved on the jpeg & krita file.

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

[trojita] [Bug 377734] Failed to Send Mail: Append failed

[Jan Kundrát]

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

Jan Kundrát  changed:

   What|Removed |Added

 Resolution|--- |INVALID
   Severity|critical|normal
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Jan Kundrát  ---
Specify a mailbox that exists in your settings and the message will go away. We
don't do autodetection yet.

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

[kdev-python] [Bug 378083] Variables from parent function in closures are considered undefined

[Diego Garcia]

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

--- Comment #2 from Diego Garcia  ---
The problem is that when you want to call the inner function or return it, it
will also get flagged as an error. And it would be correct since this code
fails.

---
def test_closures():
this = 'that'

return test_inner
# or test_inner()

def test_inner():
print(this)
---

The first snippet is the (AFAIK) only way to do closures or nested functions in
Python.

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

[plasmashell] [Bug 376168] Vertical panels impedes dragging windows in multi-monitor setup

[Jasem Mutlaq]

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

Jasem Mutlaq  changed:

   What|Removed |Added

Version|5.9.0   |master

--- Comment #7 from Jasem Mutlaq  ---
This bug is marked as confirmed now since it affects multiple users. Why isn't
anyone on the CC list acknowledging this bug yet?

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

[plasmashell] [Bug 376168] Vertical panels impedes dragging windows in multi-monitor setup

[Jasem Mutlaq]

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

Jasem Mutlaq  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[digikam] [Bug 377249] Moving a photo to album in different collection deletes its folder

[Robert V .]

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

--- Comment #2 from Robert V.  ---
I have upgraded my Digikam installation to v5.5.0 from an unofficial ebuild and
I am unable to reproduce the issue anymore. Even the moved images that were
missing were now detected (but I have some invalid entries in the database -
the images with null album referrence from v5.3.0). Is there a DB cleanup
procedure? Is it safe to delete them?

Robert

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

[konsole] [Bug 378124] Character width for HIGH VOLTAGE SIGN possibly wrong

[Thomas Luzat]

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

Thomas Luzat  changed:

   What|Removed |Added

 CC||thomas+kdeb...@luzat.com

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

[konsole] [Bug 378124] New: Character width for HIGH VOLTAGE SIGN possibly wrong

[Thomas Luzat]

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

Bug ID: 378124
   Summary: Character width for HIGH VOLTAGE SIGN possibly wrong
   Product: konsole
   Version: 16.12.0
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: font
  Assignee: konsole-de...@kde.org
  Reporter: thomas+kdeb...@luzat.com
  Target Milestone: ---

Created attachment 104749
  --> https://bugs.kde.org/attachment.cgi?id=104749=edit
Third-party terminal screenshot to show the symbol/prompt

I am using konsole with Source Code Pro font, (oh-my-)zsh and agnoster theme.
This looks similar to attached screenshot, taken from
https://gist.github.com/agnoster/3712874 When becoming root the command prompt
contains Unicode character \u26a1 (HIGH VOLTAGE SIGN). The character is
rendered with a 1 character width. Problems with that character are
reproducible with other shells by just copy & pasting the Unicode character
into some konsole. Two symptoms of the problem are:

1. In the configuration above: When using tab completion (e.g.: enter ab, press
TAB), the prompt doesn't show "ab" but becomes "aab". That is, the completion
is inserted with an offset of one character. Trying to backspace 3 times or
delete the line with C-u only the "ab" gets deleted.

2. Easier to reproduce: Copy & paste the character \u26a1 into some shell
running in konsole. Backspace or C-u make konsole move 2 characters backwards
instead of one, deleting parts of the prompt. Cursor movement across the
character moves too far.

xterm and urxvt on the same system with the same font show different behavior:
They render the symbol as a character which is two cells wide (horizontally
centered within that box). All operations (tab completion, character deletion,
cursor movement, linewrapping, ...) work as expected.

Debian is using glibc 2.24-9 with Unicode 9.0 EastAsianWidth.txt; this means
the glibc wcwidth returns 2 for \u26a1. I do not know if older versions of
glibc (<2.24-6) have shown the same behavior. EastAsianWidth.txt of Unicode 8.0
didn't contain \u26a1; it may be that it started when glibc switched to Unicode
9.0 (which it will on all distributions with 2.26).

I patched konsole_wcwidth.cpp to have its wcwidth implementation return 2 for
\u26a1. This fixes the behavior, but the symbol is now rendered left-aligned
within the two cells it's getting (it looks like lightning plus space
character). I do not know if it should be centered or left-aligned, but this
may be another issue (would prefer centered).

There seem to be other problems with konsole's wcwidth, cf.
https://eev.ee/blog/2015/09/12/dark-corners-of-unicode/ Wouldn't using the
system's wcwidth (if available?) be preferable? This might also give more
consistent behavior across the system.

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

[plasmashell] [Bug 378010] Generic High CPU Usage Rendering

[bugzilla_noreply]

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

--- Comment #16 from network...@rkmail.ru ---
I've uploaded output for QSG_INFO=1.
As fps, it's what I see in on-screen fps counter if I run plasmashell with
GALLIUM_HUD=fps variable set. Works only with gallium-based opengl drivers.

Thank you for clarifying which kwindowsystem.cpp should be modified, I'll try
to do it next weekend.

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

[plasmashell] [Bug 378010] Generic High CPU Usage Rendering

[bugzilla_noreply]

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

--- Comment #15 from network...@rkmail.ru ---
Created attachment 104748
  --> https://bugs.kde.org/attachment.cgi?id=104748=edit
QSG_INFO=1 plasmashell

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

[kate] [Bug 369155] Αutomatic spell-check is not working!

[Marcelo Escobal]

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

Marcelo Escobal  changed:

   What|Removed |Added

 CC||marcelo.esco...@gmail.com

--- Comment #1 from Marcelo Escobal  ---
Not fixed (at least in Kubuntu 16.10). I still can't use spell checking. If I
start Kate from command line i get:

> Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes.

I have both aspell and hunspell installed.

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

[kwayland-integration] [Bug 378123] New: GTK3 applications make problem on Wayland in normal user mode.

[Andrew]

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

Bug ID: 378123
   Summary: GTK3 applications make problem on Wayland in normal
user mode.
   Product: kwayland-integration
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mgraess...@kde.org
  Reporter: madbo...@gmail.com
  Target Milestone: ---

I have installed all components for the Wayland and the Wayland almost Heaven
but some GTK3 application made problem. For example: Libreoffice (bad fonts,
window buttons are broken and other problems, Inkscape trunk (freeze at the
start). If I execute them in sudo everything is OK Inkscape can start
libreoffice looks well.
(KDE neon all versions)

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

[ktouch] [Bug 378118] ktouch is unusable slow at older system (ThinkPad T61)

[Sebastian Gottfried]

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

--- Comment #1 from Sebastian Gottfried  ---
Which version are you using? 2.x oder 16.12.x?

The older version has a major performance bug. For this version you have to
apply the patch from Bug 346248 and compile the app yourself. But then you
could also just install or compile the latest version which should have very
little CPU usage. On my system (Intel Sandy Brigde) I can't get over 10 % CPU
usage.

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

[kaffeine] [Bug 378122] New: Kaffeine crashes on playing DVD

[Ivan Stanton]

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

Bug ID: 378122
   Summary: Kaffeine crashes on playing DVD
   Product: kaffeine
   Version: 2.0.1
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: mchehab+...@kernel.org
  Reporter: 2112...@jeffcoschools.us
  Target Milestone: ---

I am using the git master branch of Kaffeine.
Whenever I open a DVD in kaffeine, it crashes. This is reproducible every time.
Backtrace with debug symbols(I think): https://paste.kde.org/ptsvmuim8
Output of kaffeine: https://paste.kde.org/pwmzmjlt7

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

[konsole] [Bug 372991] Terminal gets stuck on interrupting a program that is outputting, preventing further output from being shown

[Peter Wu]

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

--- Comment #14 from Peter Wu  ---
(In reply to Martin Sandsmark from comment #13)
> Are you sure that 4.1 was okay?

Not sure if it was okay, but I wasn't able to reproduce the issue. The
difficult/annoying thing is that some versions easily trigger the problem while
others only show up after trying for some time.

> There is only a single commit to any relevant tty code that I can spot
> between v4.1.1 and v4.1.10-89-g5eb491ba5d06:
> https://www.spinics.net/lists/stable-commits/msg47515.html
> (3b19e032295647b7be2aa3be62510db4aaeda759).

which first ended up in v4.1.5 as ba3961ad681981dc74fcd519b8f98be8bc3ac381

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

[kwin] [Bug 374867] Impossible to reach screen edge if mouse cursor is moving fast

[Igor Poboiko]

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

--- Comment #6 from Igor Poboiko  ---
I rebuilt KWin with that patch. Unfortunately, it didn't help that much: it's
still reproducible.

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

[trojita] [Bug 377734] Failed to Send Mail: Append failed

[Szőgyényi Gábor]

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

Szőgyényi Gábor  changed:

   What|Removed |Added

   Severity|normal  |critical

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

[plasmashell] [Bug 370464] On reboot desktop wallpaper settings are forgotten

[davidblunkett]

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

davidblunkett  changed:

   What|Removed |Added

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

--- Comment #15 from davidblunkett  ---

I don't know what the problem was but after a system reinstall (unrelated
problem) of apparently the same version of everything it works as expected.
Thanks!

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

[Discover] [Bug 378121] New: Kein Update möglich

[bugzilla_noreply]

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

Bug ID: 378121
   Summary: Kein Update möglich
   Product: Discover
   Version: 5.6.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Updater
  Assignee: aleix...@kde.org
  Reporter: j.bur...@gmail.com
  Target Milestone: ---

Hallo,
ich kann mein System nicht mehr updaten.
Ich habe auch keine Ahnung wie ich es genau beschreiben soll. Desweiteren kann
ich den Drucker auch nicht mehr installieren, seit dem letzten Systemupdate.
Es wäre nett, wenn sie mir irgendwie helfen können

Mit freundlichen Grüßen

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

[gwenview] [Bug 362474] Copy To/Move To does not remember path any more

[Daniel Schröter]

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

Daniel Schröter  changed:

   What|Removed |Added

 CC||d.schroe...@gmx.de

--- Comment #9 from Daniel Schröter  ---
No Fix for one year :-(
I touch this bug every week.

Is it a QT problem. Should we report it there?

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

[kaffeine] [Bug 354522] repeated recordings get time-shifted by daylight-saving-time switches

[Nils Kassube]

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

--- Comment #11 from Nils Kassube  ---
Actually the patch was previously made for 1.2.2. Later I checked it with the
current git source and made a new diff with the new line numbers. I have just
tried the patch with the 1.1.2 source and it works directly.

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

[korganizer] [Bug 378120] Missing error message when trying to create an appointment at a non-existent point in time (daylight-saving)

[bugzilla_noreply]

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

mk...@posteo.de changed:

   What|Removed |Added

 CC||mk...@posteo.de

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

[korganizer] [Bug 378120] New: Missing error message when trying to create an appointment at a non-existent point in time (daylight-saving)

[bugzilla_noreply]

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

Bug ID: 378120
   Summary: Missing error message when trying to create an
appointment at a non-existent point in time
(daylight-saving)
   Product: korganizer
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: korganizer-de...@kde.org
  Reporter: mk...@posteo.de
  Target Milestone: ---

I tried to create an appointment in my calendar as a reminder to set some old
clocks manually to daylight-saving time. 
My timezone is CET / CEST or Europe/Berlin.

When setting the start time to 02:00 on the last sunday in march, the end time
fields were empty instead of the expected value start-time +1h ... On another
try the end date suddenly was 01.01.1970... I also couldn't finish the dialog,
klicking the Okay-Button just did nothing.

It took some time until I realized that the point in time I wanted to address
simply doesn't exist: The clock jumps from 01:59 to 03:00 in this night.


---
Expected Behaviour:
When I klicked the Okay-Button, an error message would have been helpful to
explain what I was missing. This might also a nice place to hide an easter egg
;-)
---

P.S.:
I did not check what happens if you try this on the last Sunday in October when
every minute between 02:00 an 03:00 is doubled?

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

[kwin] [Bug 377847] Blender menus flicker when you navigate them

[bugzilla_noreply]

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

--- Comment #8 from sun...@hotmail.ru ---
(In reply to Matthew Trescott from comment #1)
Wow, i actually have it better. In my case only menus flicker. And i'm also
using r600g Mesa drivers, i have HD 5770. Also how did you record a video in
wayland?

MESA_DEBUG gave this:
connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=No such file
or directory)
attempt to connect to server failed
Warning! Unable to find a multisample pixel format that supports exactly 4
samples. Substituting one that uses 0 samples.

But it has nothing to do with OpenGL it seems.

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

[plasmashell] [Bug 378010] Generic High CPU Usage Rendering

[David Edmundson]

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

--- Comment #14 from David Edmundson  ---
What do you mean exactly by "notifications are drawing at 200fps"?

and yes, it should be vsynced, there's code to do it (in Qt)

There's a nice line in the Qt documentation on that:
>Note: The threaded and windows render loops rely on the OpenGL implementation 
>for throttling by requesting a swap interval of 1. Some graphics drivers allow 
>users to override this setting and turn it off, ignoring Qt's request. Without 
>blocking in the swap buffers operation (or elsewhere), the render loop will 
>run animations too fast and spin the CPU at 100%. If a system is known to be 
>unable to provide vsync-based throttling, use the basic render loop instead by 
>setting QSG_RENDER_LOOP=basic in the environment.

Though if you're on intel on X, you should be running on basic anyway.
Can you run QSG_INFO=1 plasmashell

but I also don't want to get distracted from the first thing we were actually
doing:
there are multiple kwindowsystem.cpp files, I meant
./platforms/xcb/kwindowsystem.cpp

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

[amarok] [Bug 378100] Amarok crashes at launch

[Myriam Schweingruber]

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

Myriam Schweingruber  changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Myriam Schweingruber  ---
Sadly your backtrace doesn't have debugging symbols installed, on Arch you need
to recompile Amarok and its dependencies with debugging enabled for that to
work.

A very likely problem with Amarok not starting is a mismatch in Qt4 and Qt5
packages of Phonon and its backends. This is distribution related and should be
reported to your distribution directly, as it has to be addressed by the
packagers.

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

[kwin] [Bug 377847] Blender menus flicker when you navigate them

[bugzilla_noreply]

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

--- Comment #7 from sun...@hotmail.ru ---
Created attachment 104747
  --> https://bugs.kde.org/attachment.cgi?id=104747=edit
qdbus_output

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

[kmix] [Bug 377236] Kmix doesn't start every time

[Bartosz Krzeszewski]

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

--- Comment #2 from Bartosz Krzeszewski  ---
I don't have PulseAudio so I can't use plasma-pa. Even if I had PulseAudio and
I could use this applet it doesn't change that kmix has a problem to start
every time like it should.

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

[Oxygen] [Bug 378113] Continuation on package gtk3-engines-oxygen for current KDE5

[Ruslan Kabatsayev]

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

--- Comment #2 from Ruslan Kabatsayev  ---
> I just set up a KDE dev account and do have some knowledge in CSS, but 
> unfortunately none in creating theme engines or reverse-engineer and convert 
> the to CSS.

Do you realize that maximum what you should expect as achievement is something
more or less similar to "Oxygen Molecule" GTK theme, i.e.
1) No runtime switching of color schemes, since GTK3 themes are now CSS, not
executable code
2) No adjustments of widget sizes (e.g. combobox dropdown, GtkFrame, etc.)
3) No Oxygen shadows, since this requires ability to set X11 properties (not
sure how this is implemented on Wayland)
4) Not even alpha channel for corners of menus, tooltips, combobox dropdowns
(although GTK3 might have implemented this for CSS)
5) No way to use XShape for corners for the cases when compositor is off
(although this is already broken even in KWin's Oxygen window decorations)
6) Probably not even background gradient (although this might be possible now)
7) Window decorations for GTK3 windows won't have background gradient anyway
since X11 properties are impossible to set (again, not sure how this works on
Wayland)
8) Complete inner shadows in e.g. lists are not possible with CSS, since this
required some hacks on GTK-level compositing of widget rendering
9) Some other features lacking

All that said, I think if you want more or less complete implementation of
Oxygen, you might want to look into implementing it as a plugin similarly to
implementation of overlay-scrollbar-gtk3 in Ubuntu. This will allow to inspect
widget tree as oxygen-gtk2 does (and oxygen-gtk3 did), thus providing a means
of implementing most of (if not all) the hacks needed.

If you don't feel like going this "hacky" way, then you're limited to basic
support via CSS with the limitations listed above.

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

[kdm] [Bug 377238] When you lock your screen it can't be unlocked

[Bartosz Krzeszewski]

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

Bartosz Krzeszewski  changed:

   What|Removed |Added

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

--- Comment #2 from Bartosz Krzeszewski  ---
But I lock screen using KDE. I don't care what KDE is using to lock my screen.

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

[kdevelop] [Bug 378107] Crash while parsing

[Sven Brauch]

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

Sven Brauch  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||m...@svenbrauch.de
 Resolution|--- |UNMAINTAINED

--- Comment #1 from Sven Brauch  ---
This crash is in the old C++ support which is unmaintained, please use KDevelop
5 instead. If your distribution does not provide that, you can use the AppImage
from kdevelop.org/download.

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

[i18n] [Bug 378117] Invalid use of html markup in polkit action file

[Luigi Toscano]

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

Luigi Toscano  changed:

   What|Removed |Added

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

--- Comment #1 from Luigi Toscano  ---
SVN commit 1485913 by ltoscano:

Remove HTML tags where are not allowed (PolicyKit file)

The message modified end up in a PolicyKit action file, where the HTML
tags are not allowed and a warning is printed.



 M  +1 -1 
branches/stable/l10n-kf5-plasma-lts/hr/messages/kde-workspace/desktop_workspace_libksysguard.po
 
 M  +1 -1 
branches/stable/l10n-kf5/hr/messages/kde-workspace/desktop_workspace_libksysguard.po
 
 M  +1 -1 
trunk/l10n-kf5/hr/messages/kde-workspace/desktop_workspace_libksysguard.po  
 M  +1 -1 
trunk/l10n-support/hr/summit/messages/kde-workspace/libksysguard.desktop.po  


WebSVN link: http://websvn.kde.org/?view=rev=1485913

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

[plasmashell] [Bug 377843] [Wayland] next tooltip is shown on the first element you hovered around

[bugzilla_noreply]

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

--- Comment #2 from sun...@hotmail.ru ---
(In reply to Marco Martin from comment #1)
> Qt version?

5.8

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

[kaffeine] [Bug 354522] repeated recordings get time-shifted by daylight-saving-time switches

[Mauro Carvalho Chehab]

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

--- Comment #10 from Mauro Carvalho Chehab  ---
(In reply to Mauro Carvalho Chehab from comment #9)
> (In reply to Nils Kassube from comment #8)
> > The difference to the original patch is only an offset of several lines, so
> > it should be easy to backport. If you are willing to compile from source, I
> > could provide the necessary patch for 1.2.2.
> 
> Yes, the difference on this particular patch is not big. Backporting
> shouldn't be hard. You should take some care, though, as Kaffeine 1.2.x,
> uses Qt4, kile Kaffeine 2.0.x uses Qt5. The Qt5 port had to change calendar

s/kile/while/

> and date handling on several places, due to differences on how Qt5 handle
> locales.

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

[kwin] [Bug 377942] Blender sliders are broken in Wayland session

[bugzilla_noreply]

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

--- Comment #3 from sun...@hotmail.ru ---
I have no idea whether Blender supports one or both. Their toolkit is written
in python.
XWayland version xorg-server-xwayland 1.19.3-1.
I didn't use Gnome in the same distro. To test it in Gnome i've used latest
Fedora's live image. I am using Manjaro and didn't want to screw up my system
with Gnome which is community edition here. But i'll setup some system for
testing soon enough

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

[kaffeine] [Bug 354522] repeated recordings get time-shifted by daylight-saving-time switches

[Mauro Carvalho Chehab]

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

--- Comment #9 from Mauro Carvalho Chehab  ---
(In reply to Nils Kassube from comment #8)
> The difference to the original patch is only an offset of several lines, so
> it should be easy to backport. If you are willing to compile from source, I
> could provide the necessary patch for 1.2.2.

Yes, the difference on this particular patch is not big. Backporting shouldn't
be hard. You should take some care, though, as Kaffeine 1.2.x, uses Qt4, kile
Kaffeine 2.0.x uses Qt5. The Qt5 port had to change calendar and date handling
on several places, due to differences on how Qt5 handle locales.

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

[libalkimia] [Bug 378119] RoundFloor doesn't work as expected with negative numbers

[NSLW]

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

NSLW  changed:

   What|Removed |Added

 CC||onet.crist...@gmail.com,
   ||t...@net-bembel.de

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

[libalkimia] [Bug 378119] New: RoundFloor doesn't work as expected with negative numbers

[NSLW]

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

Bug ID: 378119
   Summary: RoundFloor doesn't work as expected with negative
numbers
   Product: libalkimia
   Version: trunk
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: kmymoney-de...@kde.org
  Reporter: lukasz.wojnilow...@gmail.com
  Target Milestone: ---

Problematic function is convertDenominator which doesn't work as expected with
negative numbers.

case 1:
input = -1.009
output = -1.01
desired output = -1

case 2:
input = 1.009
output = desired output = 1

RoundFloor doesn't work as in LibreOffice.

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

[i18n] [Bug 378117] Invalid use of html markup in polkit action file

[Luigi Toscano]

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

Luigi Toscano  changed:

   What|Removed |Added

   See Also||http://bugs.debian.org/6969
   ||05
 CC||luigi.tosc...@tiscali.it

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

[ktouch] [Bug 378118] New: ktouch is unusable slow at older system (ThinkPad T61)

[bugzilla_noreply]

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

Bug ID: 378118
   Summary: ktouch is unusable slow at older system (ThinkPad T61)
   Product: ktouch
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: sebastian.gottfr...@posteo.de
  Reporter: ulr_bugs_kde_...@moehrkevielfalt.de
  Target Milestone: ---

Hello,

ktouch is the best typing tutor I know. I used it myself and now I wanted it to
help my daughter. But unfortunately it takes a long long time until one can see
the typed letters. This makes it unusable slow. It takes much cpu resource.

I expect: A typing tutor should not be very cpu consuming. It should be usable
also on older machines.

I have a ThinkPad T61 and use debian testing.

I would like to help finding the reason. But therefore I would need some   
instructions. No problem to translate the program (using make) or possibly edit
some cpp files. But I'm not used to work with profilers or something else to
analyze run time behavior.

Best regards,
Ulrich

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

[i18n] [Bug 378117] New: Invalid use of html markup in polkit action file

[Maximiliano Curia]

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

Bug ID: 378117
   Summary: Invalid use of html markup in polkit action file
   Product: i18n
   Version: unspecified
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: hr
  Assignee: zarko.pin...@gmail.com
  Reporter: m...@debian.org
  Target Milestone: ---

This is a forward of the bug reported to the Debian bug tracker: 
 https://bugs.debian.org/696905

The file processcore/actions.actions includes an hr translation for the string 
 "Change the niceness of a given process" that says
 "Promijeni procesorski udio (nice) za dani proces"
and this text ends up in a policykit action file that doesn't allow the use of 
html markups. Please drop the "" and "".

The original report reads:
---
From: Michael Biebl 
Subject: HTML markup not allowed in PolicyKit action file 

Hi,

when running polkitd in debug mode I get
** (polkitd:2714): WARNING **: skipping unknown tag  at line 335

That warning messages comes from
Promijeni procesorski udio (nice) za dani
proces

It looks like HTML markup is not allowed in policy files.

Michael
---

Thanks,

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

[plasmashell] [Bug 376168] Vertical panels impedes dragging windows in multi-monitor setup

[Fritz Schrogl]

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

Fritz Schrogl  changed:

   What|Removed |Added

 CC||fritz.schr...@gmail.com

--- Comment #6 from Fritz Schrogl  ---
I recently bought a second monitor and now run in the excact same issues as
described in this bug report!

When moving windows between monitors, crossing a vertical panel on the way, the
windows get stuck or disappear. If a remove or relocate the vertical panel, so
that windows don't have to cross it, everythin works fine and as expected.

Info: 
OS: Arch Linux 64-bit
KDE Plasma: 5.9.4
KDE Frameworks: 5.32.0
QT: 5.8.0
Kernel: 4.10.5
Video: nvidia 378.13

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

[digikam] [Bug 375886] Search albums, include sub-tree shows all photos

[J-o-h-n-]

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

J-o-h-n-  changed:

   What|Removed |Added

 CC||forgivenb...@gmail.com

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

[digikam] [Bug 375886] Search albums, include sub-tree shows all photos

[J-o-h-n-]

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

J-o-h-n-  changed:

   What|Removed |Added

Version|5.4.0   |5.5.0
   Platform|Other   |Ubuntu Packages

--- Comment #3 from J-o-h-n-  ---
Problem still exists in 5.5 on Ubuntu-Gnome 16.04 x64.

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

[ark] [Bug 377887] Crash when opening file from archive

[Fincer]

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

--- Comment #11 from Fincer  ---
png, jpg and cr2 work without problems. I couldn't test pdf as I use a Windows
version of Adobe Acrobat Pro for that filetype on my Linux system.

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

[ark] [Bug 377887] Crash when opening file from archive

[Elvis Angelaccio]

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

--- Comment #10 from Elvis Angelaccio  ---
@Fincer: what about other file types? Does it also crash if you preview a .png
or a .pdf in the archive?

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

[digikam] [Bug 378116] New: Themes icon washout

[J-o-h-n-]

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

Bug ID: 378116
   Summary: Themes icon washout
   Product: digikam
   Version: 5.5.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: forgivenb...@gmail.com
  Target Milestone: ---

Not sure which component this bug belongs to.
Different themes can washout the icons on the toolbar so they are invisible or
difficult to see.  The effect seems to switch between Linux and Windows.

Icons are invisible on Ubuntu-Gnome 16.04 x64 in these themes:
Default
White Balance

Icons are invisible on Windows 10 x64 in these themes:
Black Body
ColorContrast
DarkRoom
GrayCard
LowKey
ShadeOfGray
SunsetColor

The white color icons on the Linux themes (above) and the gray color icons on
the Windows themes (also above) do not seem to have enough contrast between the
background colors and the icons themselves.

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

[plasmashell] [Bug 376725] Global menu doesn't respond to mouse hover

[Albert]

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

Albert  changed:

   What|Removed |Added

 CC||bla6@gmail.com

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

[plasmashell] [Bug 378080] Screen Locker causes crash

[paul s]

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

paul s  changed:

   What|Removed |Added

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

--- Comment #2 from paul s  ---
yes this can be reproduced on every wakeup.

as for the resolution change, i think it might have to do more with the dual
monitor. my MacBookPro11,3 resolution is 2880x1800 and my monitor is 3840x2160
using the nvidia driver connected via display port.

when the bug was created i thought it had to do with my monitor being set to 2k
instead of 4k. so i just switched last night to 4k to see if that had any
impact and it did not. plasmashell crashes every time the monitors wake.

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

[kaffeine] [Bug 354522] repeated recordings get time-shifted by daylight-saving-time switches

[Nils Kassube]

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

--- Comment #8 from Nils Kassube  ---
The difference to the original patch is only an offset of several lines, so it
should be easy to backport. If you are willing to compile from source, I could
provide the necessary patch for 1.2.2.

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

[kaffeine] [Bug 354522] repeated recordings get time-shifted by daylight-saving-time switches

[Mauro Carvalho Chehab]

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

--- Comment #7 from Mauro Carvalho Chehab  ---
(In reply to Isence XEXEDI from comment #6)
> in which kaffeine release will this fix be available ?
> this bug is still there in the current 1.2.2 version. 

Version 1.2.x are really old (2015)! It is not maintained upstream anymore. You
should either upgrade to a newer version/distribution or request your
distribution maintainers to backport the fixes (with may not be an easy task,
as Kaffeine code changed a lot since version 1.2.x).

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

[digikam] [Bug 378098] update meta data from selected images (generated outside digikam) does not work anymore

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||5.6.0
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/dig
   ||ikam/76060c16c14dabfb4aa7a5
   ||ac956c5292aff810bf
 CC||metzping...@gmail.com
 Resolution|--- |FIXED

--- Comment #1 from Maik Qualmann  ---
Git commit 76060c16c14dabfb4aa7a5ac956c5292aff810bf by Maik Qualmann.
Committed on 15/03/2017 at 19:55.
Pushed by mqualmann into branch 'master'.

fix MetadataSynchronizer and non working lazy sync in digiKam-5.5.0

M  +1-1utilities/maintenance/maintenancedata.cpp

https://commits.kde.org/digikam/76060c16c14dabfb4aa7a5ac956c5292aff810bf

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

[digikam] [Bug 378115] New: Upgrades lose custom toolbars

[J-o-h-n-]

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

Bug ID: 378115
   Summary: Upgrades lose custom toolbars
   Product: digikam
   Version: 5.5.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: setup
  Assignee: digikam-de...@kde.org
  Reporter: forgivenb...@gmail.com
  Target Milestone: ---

The "Configure Toolbars..." settings are lost between upgrades.  The "Text
Position" and "Icon Size" settings transfer.  Using the same database before
and after upgrades.

This happened on Ubuntu-Gnome 16.04 x64 between upgrades from 5.3 to 5.4 and
5.4 to 5.5.  Also happened on Windows 10 x64 from 5.3 to 5.4 and 5.4 to 5.6. 
Yes, I skipped 5.5 on Windows 10 but just for curiosity, not to solve any
problem.

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

[konsole] [Bug 343539] "Draw intense colors in bold font" not respected with a fresh installation

[Roberto Benfatto]

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

Roberto Benfatto  changed:

   What|Removed |Added

 CC||robenfa...@covolunablu.org

--- Comment #16 from Roberto Benfatto  ---
I'm giving a bump on this, I actually triggered this bug today, after a long
time having it work as expected. I'm on Arch Linux, using Konsole 16.12.3

Before today, I was using Fira Code as font in Konsole profile, and Fira mono
in sistem wide settings for monospaced fonts. It's important to say that I set
up my system wide monospace settings when I installed my system, back in august
2016. Since then, I did not change it from there, but I rather changed the font
from the specific application I wanted the font on.

Today I changed the font to Fira Mono in the konsole profile settings, and
suddendly the "bold on intense" functionality broke. I changed it back to fira
Code, but I had to restart konsole to have it working again, all of these
changes where made from Konsole profile settings.

Then, out of curiosity, I changed the monospaced font system wide in system
settings from Fira Mono to Fira Code, and that was the thing that made
everything stop working and unable to get it working again. After that I tried
restarting konsole, reverting system wide settings for monospaced fonts,
reinstalled fira fonts, but nothing worked.

It's a thing that I can effectively get the bold on intense functionality
working only when I'm using the "monospace" family fonts, wich I think uses
Dejavu Sans Mono as standard font. But if I specify Dejavu Sans Mono instead,
bold on intense stops working again, even if it was previously working when
used with monospace family.

I hope this helps somehow.

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

[systemsettings] [Bug 378092] Installed VLC Backend not Visible in Settings

[Harald Sitter]

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

Harald Sitter  changed:

   What|Removed |Added

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

--- Comment #2 from Harald Sitter  ---
The package you are looking at is the Qt4 version, systemsettings however is
Qt5 and thus only show the Qt5 backends.

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[bugzilla_noreply]

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

--- Comment #39 from stefanfr...@gmx.net ---
Maybe my problem is exactly the filtering bug. I am using Pop3 and filters in
Kmail. What is the link to that Bugreport?
To complete your request I attached the crashreport:

Application: Kontact (kontact), signal: Segmentation fault

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

[Oxygen] [Bug 378113] Continuation on package gtk3-engines-oxygen for current KDE5

[Nikolai Försterling]

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

--- Comment #1 from Nikolai Försterling  ---
It seems this bug is basically close to Bug 340288.
I just set up a KDE dev account and do have some knowledge in CSS, but
unfortunately none in creating theme engines or reverse-engineer and convert
the to CSS.
I do have the same opinion as Hussam (Oxygen was the face of KDE applications
for long years) and would like to try to keep this alive even with the damaged
relationship to GTK developers.
If Darktable and Firefox were QT, who'd use GNOME?

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

[kwin] [Bug 378114] New: After trying kde with wayland, compositor on xorg is broken with opengl, have to use xrender to see the effects

[Keziolio]

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

Bug ID: 378114
   Summary: After trying kde with wayland, compositor on xorg is
broken with opengl, have to use xrender to see the
effects
   Product: kwin
   Version: 5.9.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: platform-wayland
  Assignee: kwin-bugs-n...@kde.org
  Reporter: keziolio...@gmail.com
  Target Milestone: ---

On an intel laptop with mesa drivers.

Only xrender shows the effects (blur around windows, transparency, animations,
etc)
With opengl, both 2.0 and 3.1, it doesn't, used to work before i tried to open
wayland, it's broken in xorg now.

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

[Oxygen] [Bug 378113] New: Continuation on package gtk3-engines-oxygen for current KDE5

[Nikolai Försterling]

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

Bug ID: 378113
   Summary: Continuation on package gtk3-engines-oxygen for
current KDE5
   Product: Oxygen
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: gtk3-engine
  Assignee: hugo.pereira.da.co...@gmail.com
  Reporter: nospam.fos...@web.de
CC: b7.10110...@gmail.com,
hugo.pereira.da.co...@gmail.com, w...@adishatz.org
  Target Milestone: ---

After migration to Kubuntu 16.10 (old 14.04 still running) i encountered that
the package "gtk3-engines-oxygen" won't install anymore in KDE5 (Kubuntu
Yakkety and KDE Backports) because of unresolved/broken dependencies to
likgtk3.
What i've read so far, the major issue should be that "engines" are no longer
allowed within GTK3 themes and that all themes have to be pure css.
Is there a chance to get the package gtk3-engines-oxygen continued for current
KDE releases?
I'd really like to get this back as it it the only theme beside Breeze (which i
don't like) that lets the user keep QT and GTK3 applications have a consistent
look and willing to spend time on this if there'd be a solution.

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

[digikam] [Bug 378112] New: No progress bar while maint initializes

[J-o-h-n-]

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

Bug ID: 378112
   Summary: No progress bar while maint initializes
   Product: digikam
   Version: 5.5.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Maintenance
  Assignee: digikam-de...@kde.org
  Reporter: forgivenb...@gmail.com
  Target Milestone: ---

Opening digikam5 from the command-line to see output.  When running maintenance
on a large number of albums, digikam seems to "hang" either at:
digikam.general: Using  1  CPU core to run threads
or
digikam.general: Creating a fingerprints task for generating fingerprints

Last time this took 00:36:35 for 2635 albums.

There is no feedback on the command-line and no visual feedback (progress bar)
in the GUI, also there is no HDD activity nor CPU activity.  I realize digikam
is probably doing something, but there is no indication of it.  Is there a cli
switch to see more output?

My suggestion would be to include whatever digikam does to initialize
maintenance within the progress bar or as a separate task on the progress bar
before the intended maintenance-to-be-performed's task.

Too, digikam is sluggish and unresponsive during this initialization process.

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

[kdevelop] [Bug 378111] New: Fix error source for a program abort

[Markus Elfring]

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

Bug ID: 378111
   Summary: Fix error source for a program abort
   Product: kdevelop
   Version: 5.1.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Build tools: Make
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: markus.elfr...@web.de
  Target Milestone: ---

Created attachment 104746
  --> https://bugs.kde.org/attachment.cgi?id=104746=edit
Backtrace for a program abort while opening a Linux make project

I would like to reopen a make-based project for a Linux directory with the
application “KDevelop 5.1.0-24.2”. The program needs a while to present a bit
of desired project data until it aborts shortly thereafter.

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

[kate] [Bug 378110] New: 16.12.3 - Save icon does not work

[Axel Braun]

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

Bug ID: 378110
   Summary: 16.12.3 - Save icon does not work
   Product: kate
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: axel.br...@gmx.de
  Target Milestone: ---

Kate seems to be the new default app for Text files in Tumbleweed.
When changing a text, a disk icon appears on the tab.
Clicking on it does not save the file

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

[ark] [Bug 377887] Crash when opening file from archive

[Fincer]

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

--- Comment #9 from Fincer  ---
Created attachment 104745
  --> https://bugs.kde.org/attachment.cgi?id=104745=edit
Ark (16.12.3) output log with debug symbols

May do in some day. 

For the meanwhile, I compiled Ark with debug symbols
(https://community.kde.org/KDE_Utils/Ark#Build_with_debug_symbols) and ran the
program. Output...well..says nothing new but just for the sake of information,
I've attached the log here.

As a workaround for now, I tell Ark to open all files in external applications
(kate in this case, obviously). Settings -> Configure Ark

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

[frameworks-networkmanager-qt] [Bug 378109] New: signals in glib2 was defined by QT

[Robert Lu]

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

Bug ID: 378109
   Summary: signals in glib2 was defined by QT
   Product: frameworks-networkmanager-qt
   Version: 5.27.0
  Platform: RedHat RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: jgrul...@redhat.com
  Reporter: robberp...@gmail.com
CC: lamar...@kde.org, lukas.ti...@merlin.cz
  Target Milestone: ---

Created attachment 104744
  --> https://bugs.kde.org/attachment.cgi?id=104744=edit
the file that cannot compile

When I compile nm_conn in attachment, I met the error:

$ make  
Scanning dependencies of target nm_conn
[ 50%] Building CXX object CMakeFiles/nm_conn.dir/nm_conn.o
In file included from /usr/include/qt5/QtCore/qobject.h:46:0,
 from /usr/include/qt5/QtCore/qabstractanimation.h:43,
 from /usr/include/qt5/QtCore/QtCore:4,
 from /usr/include/qt5/QtDBus/QtDBusDepends:3,
 from /usr/include/qt5/QtDBus/QtDBus:3,
 from
/usr/include/KF5/NetworkManagerQt/networkmanagerqt/manager.h:29,
 from
/usr/include/KF5/NetworkManagerQt/NetworkManagerQt/Manager:1,
 from /home/rlu/nm-connectivity/nm_conn.cpp:1:
/usr/include/glib-2.0/gio/gdbusintrospection.h:155:25: error: expected
unqualified-id before ‘public’
   GDBusSignalInfo **signals;
 ^
In file included from /usr/include/glib-2.0/gio/gio.h:54:0,
 from /usr/include/libnm/nm-types.h:24,
 from /usr/include/libnm/nm-object.h:29,
 from /usr/include/libnm/nm-access-point.h:29,
 from /usr/include/libnm/NetworkManager.h:26,
 from
/usr/include/KF5/NetworkManagerQt/networkmanagerqt/ipconfig.h:31,
 from
/usr/include/KF5/NetworkManagerQt/networkmanagerqt/device.h:33,
 from
/usr/include/KF5/NetworkManagerQt/networkmanagerqt/manager.h:31,
 from
/usr/include/KF5/NetworkManagerQt/NetworkManagerQt/Manager:1,
 from /home/rlu/nm-connectivity/nm_conn.cpp:1:
/usr/include/glib-2.0/gio/gdbusintrospection.h:155:24: error: expected ‘;’ at
end of member declaration
   GDBusSignalInfo **signals;
^
/usr/include/glib-2.0/gio/gdbusintrospection.h:155:32: error: expected ‘:’
before ‘;’ token
   GDBusSignalInfo **signals;
^
CMakeFiles/nm_conn.dir/build.make:62: recipe for target
'CMakeFiles/nm_conn.dir/nm_conn.o' failed
make[2]: *** [CMakeFiles/nm_conn.dir/nm_conn.o] Error 1
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/nm_conn.dir/all' failed
make[1]: *** [CMakeFiles/nm_conn.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2

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

[kdenlive] [Bug 378108] New: Generate audio thumbnail if music file contains cover image

[Ashark]

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

Bug ID: 378108
   Summary: Generate audio thumbnail if music file contains cover
image
   Product: kdenlive
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: ash...@linuxcomp.ru
  Target Milestone: ---

Some audio files may contain album art inside, but kdenlive always shows
generic audio icon for imported sound clip.

In Dolphin file manager it is possible to turn on previews for such files. It
is done with audiothumbs-frameworks plugin.

I think it will be better if we make the same behavior. And I think it is not
difficult to implement. At least, I can provide link to how it is done in
audiothumbs-framework in just one file:
https://github.com/eplightning/audiothumbs-frameworks/blob/master/src/AudioThumbs.cpp

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

[digikam] [Bug 351518] Show current album in "Common options"

[J-o-h-n-]

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

J-o-h-n-  changed:

   What|Removed |Added

 CC||forgivenb...@gmail.com

--- Comment #1 from J-o-h-n-  ---
This is confirmed on Ubuntu-Gnome 16.04 x64 and Windows 10 x64.  Perhaps a
button to just goto current album and leave the selecting or deselecting up to
the user?

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

[kdevelop] [Bug 378107] New: Crash while parsing

[bugzilla_noreply]

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

Bug ID: 378107
   Summary: Crash while parsing
   Product: kdevelop
   Version: 4.7.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: velor...@gmail.com
  Target Milestone: ---

Application: kdevelop (4.7.3)
KDE Platform Version: 4.14.16
Qt Version: 4.8.7
Operating System: Linux 4.4.0-67-generic x86_64
Distribution: Ubuntu 16.04.2 LTS

-- Information about the crash:
Got this project:
https://github.com/SFTtech/openage/pull/756/commits/b9d15b7146708c824fc3647028b1df91e314081a

Added include paths:

/usr/include/x86_64-linux-gnu/qt5/QtQuick/

/usr/include/x86_64-linux-gnu/qt5/QtGui/

/usr/include/x86_64-linux-gnu/qt5/QtCore/

Crashes every time while parsing.

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 0x7ffa422ca900 (LWP 12579))]

Thread 12 (Thread 0x7ff970fa6700 (LWP 12804)):
#0  0x7ffa3aecd360 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7ffa3f0a03a6 in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x2c80b10) at
thread/qwaitcondition_unix.cpp:86
#2  0x7ffa3f0a03a6 in QWaitCondition::wait(QMutex*, unsigned long)
(this=this@entry=0x2c809e8, mutex=0x2c80c90,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x7ffa34e37c9c in
ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned(ThreadWeaver::Thread*)
(this=0x2c809c0, th=0x7ff954003270) at
/build/kde4libs-oFCmS0/kde4libs-4.14.16/threadweaver/Weaver/WeaverImpl.cpp:370
#4  0x7ffa34e3a993 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*,
ThreadWeaver::Job*) (this=0x2c80d60, th=0x7ff954003270, previous=0x0) at
/build/kde4libs-oFCmS0/kde4libs-4.14.16/threadweaver/Weaver/WorkingHardState.cpp:68
#5  0x7ffa34e3a9ac in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*,
ThreadWeaver::Job*) (this=0x2c80d60, th=0x7ff954003270, previous=0x0) at
/build/kde4libs-oFCmS0/kde4libs-4.14.16/threadweaver/Weaver/WorkingHardState.cpp:71
#6  0x7ffa34e3a9ac in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*,
ThreadWeaver::Job*) (this=0x2c80d60, th=0x7ff954003270, previous=0x61fe680) at
/build/kde4libs-oFCmS0/kde4libs-4.14.16/threadweaver/Weaver/WorkingHardState.cpp:71
#7  0x7ffa34e394ef in ThreadWeaver::Thread::run() (this=0x7ff954003270) at
/build/kde4libs-oFCmS0/kde4libs-4.14.16/threadweaver/Weaver/Thread.cpp:98
#8  0x7ffa3f09fe3c in QThreadPrivate::start(void*) (arg=0x7ff954003270) at
thread/qthread_unix.cpp:352
#9  0x7ffa3aec76ba in start_thread (arg=0x7ff970fa6700) at
pthread_create.c:333
#10 0x7ffa3e9e082d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7ff9717a7700 (LWP 12803)):
[KCrash Handler]
#6  0x in  ()
#7  0x7ff972877710 in DeclarationBuilder::closeDeclaration(bool)
(this=0x7ff97179df00, forceInstance=) at
/build/kdevelop-jGcNEc/kdevelop-4.7.3/languages/cpp/cppduchain/declarationbuilder.cpp:865
#8  0x7ff97287906b in DeclarationBuilder::visitDeclarator(DeclaratorAST*)
(this=0x7ff97179df00, node=0x7ff9558c5b68) at
/build/kdevelop-jGcNEc/kdevelop-4.7.3/languages/cpp/cppduchain/declarationbuilder.cpp:475
#9  0x7ff97286899f in
ContextBuilder::visitInitDeclarator(InitDeclaratorAST*)
(this=this@entry=0x7ff97179df00, node=node@entry=0x7ff9558c62d0) at
/build/kdevelop-jGcNEc/kdevelop-4.7.3/languages/cpp/cppduchain/contextbuilder.cpp:911
#10 0x7ff97287467c in
DeclarationBuilder::visitInitDeclarator(InitDeclaratorAST*)
(this=0x7ff97179df00, node=0x7ff9558c62d0) at
/build/kdevelop-jGcNEc/kdevelop-4.7.3/languages/cpp/cppduchain/declarationbuilder.cpp:255
#11 0x7ff97289589c in
TypeBuilder::visitSimpleDeclaration(SimpleDeclarationAST*)
(this=this@entry=0x7ff97179df00, node=node@entry=0x7ff9558c6310) at
/build/kdevelop-jGcNEc/kdevelop-4.7.3/languages/cpp/cppduchain/typebuilder.cpp:690
#12 0x7ff972876f75 in
DeclarationBuilder::visitSimpleDeclaration(SimpleDeclarationAST*)
(this=0x7ff97179df00, node=0x7ff9558c6310) at
/build/kdevelop-jGcNEc/kdevelop-4.7.3/languages/cpp/cppduchain/declarationbuilder.cpp:349
#13 0x7ff9725cad49 in visitNodes(Visitor*,
ListNode const*) (v=v@entry=0x7ff97179df58, nodes=) at
/build/kdevelop-jGcNEc/kdevelop-4.7.3/languages/cpp/parser/visitor.h:139
#14 0x7ff9725ca912 in
DefaultVisitor::visitClassSpecifier(ClassSpecifierAST*)
(this=this@entry=0x7ff97179df58, node=node@entry=0x7ff954a69328) at